If yes, could you please try to enable "Always wait for the network at computer startup and logon" and then try it again? If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate? If someone ever reads this and needs a data driven logon script to map drives based on group membership or user object OU with logic to handle the errors/ retries then Environment Novell NetWare 5.0 SP6a Situation Error 8804 mapping drives via login script Error: "Login-4.21.15-430: The following drive mapping operation could not be completed [ROOT H:=SERVER/VOLUME:HOME\D] 8804" MAP ROOT H:=[SERVER/VOLUME:PATH\ no https://www.novell.com/documentation/nwec/
An example of an error reported is:LOGIN-LGNWNT32-430: The following drive mapping operation could not be completed. [INS ROOT S1:=
I can't find the cause but only know I have 24 drive mapping GPO's. Give it some time. 3. eDirectory or NDS Agent Error Codes Error codes numbered -601 through -799 (or FDA7 through F9FE) and -6001 or higher represent errors that originated in the eDirectory or NDS Agent software The NCP name service should never be deselected.
Consequently, these functions can result in client-specific error codes being returned to the eDirectory or NDS background processes and operations. 0x800789ff Generally, all operating system error codes that are generated by eDirectory or NDS have a negative numerical representation while all other operating system error codes have a positive numerical representation. Document ID:7016890Creation Date:08-OCT-15Modified Date:08-OCT-15NovellClient Did this document solve your problem? https://www.novell.com/documentation/nwec/?page=/documentation/nwec/nwec/data/al29t23.html Bookmark Email Document Printer Friendly Favorite Rating: Error 8804 mapping drives via login scriptThis document (3074628) is provided subject to the disclaimer at the end of this document.
Drive Mapping during GPO Preferences are causing a delay indicated by the EventID 4098 in the event viewer. Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS Novell is Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. Generated Sun, 30 Oct 2016 13:18:54 GMT by s_mf18 (squid/3.5.20) Windows Client Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية
In this specific environment, SLP was the only configured name service. https://www.novell.com/support/kb/doc.php?id=7007909 Please try the request again. Novell Error Code C000000f Event ID 4098 The user 'S:' preference item in the 'GPO NAME' Group Policy object did not apply because it failed with error code '0x800704d0 The network location cannot be reached. Error Novell Edirectory You can use SkyDrive to upload the log for troubleshooting.
Unicode* and other errors in this category range from -400 to -599. More about the author For information about network troubleshooting, see Windows Help.' This error was suppressed. In some cases, this allows the drive mapping statements to succeed. The most common case of which is when a USB drive takes an additional "local" drive letter, although in modern computers even normal peripherals such as the optical drive might be
Or, try setting "First Network Drive" in Novell Client Properties to that known available drive letter, so that "*1" will now be an implicit reference to that same starting drive letter. These error codes are then passed on to the eDirectory or NDS background process or operation that initiated a request. DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. http://linuxprofilm.com/error-code/error-code-0-mac.html DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another.
eDirectory or NDS error codes are usually displayed in decimal numbers. However, some errors might persist until the error condition is resolved. Resolution Use the Windows "Run logon scripts synchronously" policy to force Windows to completely finish running the loginscript(s) before proceeding with starting the user's desktop.See the Novell Client readme section 4.16
If any of these modules encounter an error, it can be passed on to the ds.nlm. Wait for obituary to clear for the object. This forced the client to go through SLP for all name resolution and in this specific case there were servers not registered in SLP which ultimately caused the drive mappings to Drive Mapping during GPO Preferences are causing a delay indicated by the EventID 4098 in the event viewer.
I've enabled 'always wait for network' and no changeRob Szarszewski Saturday, September 08, 2012 3:56 PM Reply | Quote 0 Sign in to vote Hi, Does this occur on some specical MAP ROOT H:=%"HOME DIRECTORY" works for one server but not another. This can be accomplished by right clicking the red N in the system tray, select Novell Client Properties, click on the Name Services tab, make sure DNS, SLP and NCP are news I'm running windows 7 on the clients, windows 2008 on the servers, not r2 I've tried the local admin, uac, reconnect and no change options, nothing works...
Cause The computers experiencing the issue had the NCP name service deselected. Often a number code is truncated to two digits, so it is not the actual decimal equivalent of the hexadecimal code. These error codes are generated by the eDirectory or NDS client that is built into eDirectory or NDS (ds.nlm). These functions, such as communication and transaction servers, can return operating system specific error codes to eDirectory or NDS.
Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. what I did was disabled the 24 GPO's and created a logon script to map the drives, the script runs after the desktop loads so users are not delayed at logon. Because the eDirectory or NDS database is designed as a loosely consistent database, temporary errors are normal. Resolution 1.
You should not be alarmed if eDirectory or NDS error conditions exist temporarily. Right click on "Group Policy Result" and choose "Group Policy Results Wizard" to generate a report by specifying the problematic computer and user account. Delete the volume in question using NWAdmin (affecting the eDirectory object only and not the physical volume). 2. Resolution Try using either a literal drive letter known to be available, to see if that avoids the error.
If no, how about access the share folder by IP address? what I did was disabled the 24 GPO's and created a logon script to map the drives, the script runs after the desktop loads so users are not delayed at logon. This will ensure that the SHELL32/user's desktop is initialized only afterthe login script results window is closed. I can't find the cause but only know I have 24 drive mapping GPO's.
Therefore, any occurrence of an error code within the range of 1 to 255 or -1 to -255 should be treated as the same error.