Novell Client for Windows (32-bit) Internal Error 0x00008993
This is an interesting one, and apparently either not documented at MicroFocus or not very findable. Perhaps I should comb through Cool Solutions for it.
The problem system is a Windows XP SP3 VM running under VBox on Linux. The VM has terminal services components installed to make it behave similarly (i.e., simultaneous logins allowed with independent desktops).
The VM is running Novell Client for Windows 4.91 SP5 IR2, logging into eDirectory 8.8.
For seemingly no reason this morning, a user reported an inability to log in. Upon entering his password and clicking OK, he received the following popup:
Novell Security Message
Internal error 0x00008993 occurred. Try again.
If the error occurs again, restart your workstation and try again.
If the error persists, contact your network administrator.
Select the Workstation Only checkbox to log in to the local workstation.
There are three Novell login profiles on the system:
- Unaffected
- Could not log in (either initially or if workstation only, from the N, after)
- Could log in, but script results reported a similar 8993 error
Searching MicroFocus support (I miss Novell's old site so much!), the closest I could come was:
https://support.microfocus.com/kb/doc.php?id=7024100
which mentioned rolling back to NICI 2.x.
Meanwhile, I tried the following in sequence:
- Deleted the login profile from the Client properties and recreated
- Changed NMAS sequence from <DEFAULT> to NDS; this allowed login one time only, and setting this as the default for the new profile did not work (same 8993 error)
- Reinstalled the 4.91 SP5 IR2 Client (on top of what was there)
- Repaired NMAS
(with intermediate reboots to ensure that I was getting the registry read), all to no (or varying) avail.
Finally, I uninstalled NICI and reinstalled the Client (thus reinstalling NICI).
This resolved the issue for both ailing profiles, leaving the working one still working.
Go figure.
The VM is restarted every day at 4am (of course; it's Windows, and leaks memory like a sieve, so without a daily restart, it's practically unusable by day 2 of uptime). It was working fine yesterday (and for the past decade or so). I have no idea what broke it. I also have not looked at the event log for clues. I'll update this post if there is anything relevant there.
Related posts:
- Broken Windows updates for .NET Why should applying patches be so difficult? Why does Microsoft...
- Why there’s nothing wrong with NetWare There are tons of scam artists...er...consulting firms out there who...
- Installing Windows Server 2008 R2 x64 on the HP Proliant DL380 G4 Even "supported hardware" can be a bear sometimes. Hopefully, these...
- Ramdom thoughts on the 2011 (and beyond?) Firefox release schedule Why is it that all major design decisions seem to...
- Migrating a bare-metal Windows 2000 install to a VirtualBox guest Virtualization has made it possible for us to maintain...
Enjoy this article?
Recent Posts
- Novell Client for Windows (32-bit) Internal Error 0x00008993
- Noisy utility company email
- The importance of Common User Access design guidelines in 2018
- Navigating Coinbase’s customer support
- Configuring the IOGEAR GWU627 wireless ethernet bridge device under ArcaOS (and OS/2)
Categories
Support Pages
Posts by Date
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
« Jun | ||||||
1 | 2 | |||||
3 | 4 | 5 | 6 | 7 | 8 | 9 |
10 | 11 | 12 | 13 | 14 | 15 | 16 |
17 | 18 | 19 | 20 | 21 | 22 | 23 |
24 | 25 | 26 | 27 | 28 | 29 | 30 |
Log In
Email Notifications
RSS Feeds
Recent Comments
- LewisR on Installing Windows Server 2008 R2 x64 on the HP Proliant DL380 G4
- LewisR on Installing Windows Server 2008 R2 x64 on the HP Proliant DL380 G4
- justintd on Installing Windows Server 2008 R2 x64 on the HP Proliant DL380 G4
- LewisR on WP Post to PDF Enhanced
- pdfsc on WP Post to PDF Enhanced
Leave a comment
You must be logged in to post a comment.