Novell Error 8819
Asset Management ZENworks Configuration Management ZENworks Endpoint Security Management ZENworks Full Disk Encryption ZENworks Patch Management ZENworks Virtual Appliance Learn more about ZENworks File & Networking Services + File Management Suite Business Continuity Clustering Dynamic File Services File Reporter Filr Micro Focus iPrint Open Enterprise Server Storage Manager Looking for Linux? See our new home at SUSE.com Services & Support + Services Overview Help Yourself Knowledgebase Support Forums Documentation Product Support Lifecycle Let Us Help Open Service Request Entitlement & Access Premium Support Technical Support Handbook Download Patches Drivers Contribute Participate in Beta Report Bug Report Software Vulnerability Share a Tip, Trick, etc. Cool Solutions Consulting Customer Center My Profile My Products My Support My Training Partners Communities + Communities Blog—Expert Views Blog—Technical Free Tools Support Forums About Us + About Us Contact Us Our Customers Executive Management Job Search Events Media Gallery Industry Analysts Press Releases Subscribe How to Buy + How to Buy Overview Request a Call Find a Partner Shop for Training Volume Licensing & Buying Programs > cool solutions home Error -8819 Novell Cool Solutions: Question & Answer Posted: 25 May 2005 Q:When users try to browse a context, they get the error -8819. The DS is healthy. Our servers are NetWare 6.5 SP2 or SP3 with eDirectory 8.7.3.4. A:Error -8819 normally means "server connection lost". There is a long- standing client bug where connections can be lost when the workstation is sending a sustained stream of requests to the server. ConsoleOne is inefficient in terms of the network traffic generated so you might be encountering this client bug. Try running it from a local machine instead of over the network. This will eliminate the traffic generated from loading and reading snaps-ins, which may help. Also, the '88' prefix indicates a client issue, not a server issue. A '89' prefix indicates a server issue. Novell Cool Solutions (corporate web communities) a
Favorite Rating: Intermittent login and drive mapping problemsThis document (3445831) is provided subject to the disclaimer at http://www.novell.com/support/kb/doc.php?id=3445831 the end of this document. Environment Novell NetWare 6.5 Novell Client http://marc.info/?l=patchmanagement&m=115168451509110 for Windows 2000/XP/2003 4.91 Support Pack 2 TrendMicro OfficeScan Corporate Edition (OSCE) 7.3 Support Pack 1 Situation Symptoms:LOGIN-LGNWNT32.DLL-470: The Specified drive mapping is an invalid path.LOGIN-LGNWNT32.DLL-923: An unexpected error has occurred: 15 (8819). LOGIN-LGNWNT32.DLL-870: An unknown error was returned during LOGIN's attempt to attach. Error novell error Code: 8819 LOGIN-LGNWNT32.DLL-440: The operation was attempted on an invalid drive. LOGIN-LGNWNT32.DLL-430: The following drive mapping operation could not be completed. [...] The error code was 8819. LOGIN-LGNWNT32.DLL-740: This utility could not execute external program [...]Changes:After the installation, or an update, of the TrendMicro OfficeScan Corporate Edition (OSCE) 7.3 client for Windows, the workstations starts to experience novell error 8819 intermittent login problems.The login process fails or does not complete properly giving errors on drive mapping operations and/or other login script commands. Resolution None, the problem was reported to Trendmicro. Please verify that uninstalling the TrendMicro OSCE 7.3 client fix the issue, and if so, then contact Trendmicro to report the symptoms you are experiencing and asking for support.Workarounds:- Uninstall the TrendMicro OSCE 7.3 client; - In some cases roll back the last TrendMicro OSCE update installed was enough to fix the issue. Additional Information Capturing and analyzing a lan trace of the communications occurring between the workstation and the NetWare server the following pattern was found:[...] Client PC ‑‑ TCP SYN ‑‑> Server Client PC <‑‑ TCP ACK ‑‑ Server ... Approximately 3 second time delay ... Client PC ‑‑ TCP SYN ‑‑> Server Client PC <‑‑ TCP ACK ‑‑ Server ... Approximately 6 second time delay ... Client PC ‑‑ TCP SYN ‑‑> Server Client PC <‑‑ TCP ACK ‑‑ Server [...]The root cause is the
GW-FS1 ! SHANDS ! UFL ! EDU [Download message RAW] We are running 4.91. I'm not sure if the issue with the drive mappings just appeared at the exact same time as I was deploying (Don't you love that?) or if it was actually patch related. The techs in the field found something that apparently worked for them on this issue: "Go to the Novell Client Configuration screen (right click your red N in your system tray, go to Novell Client Properties). Go into Advanced Settings and change Bad Address Cache Timeout from 300 to 0. You may also need to change Bad Server Name Cache Timeout from 300 to 0 as well. This worked for me. However, you may need to go a tad further and completely disable the timeout on the clients that are not 4.91SP2. Well, time to visit the registry, then. Go to HKLM\System\CurrentControlSet\Services\Netware Workstation\Parameters and create a Dword value called BadAddressCacheTimeout and set the value to 0." So, I have not been able to identify the root of the problem as of yet..I'll give an update if I do. Glenn > > > mgoodnow@crhc.org 6/29/2006 2:51:35 PM >>> We are primarily XP SP1 (some XP2) at the desktops - utilizing Big Fix for deployments (3000+ PCs and Servers). Novell clients are a mix of 4.9.0 and 4.9.1.1. We don't typically force reboots of our workstations right after a deployment - so we may not find any additional problems right away. The one instance we had with this error was on a client running 4.9.0. I'm hoping our one issue is all we will see. I wonder if the individual who originated this post could let us know which version(s) of clients they saw this issue on. Thanks, Mike > > > On 6/29/2006 at 9:15 AM, in message <062920061315.26513.44A3D28E00021A90000067912213484373970A9C020E08@comcast.net>, \