835732 and Novell KeyAccess

  • Thread starter Thread starter Lance
  • Start date Start date
L

Lance

For the benefit of others that are struggling with Win2k and 835732.

My IT department here at work has determined that Novell's KeyAccess
software is causing our problems with 835732 (IE won't start, can't retrieve
email). We use Novell to distribute software to clients.

We will be updating tomorrow with a new version of KeyAccess that will - I
hope - fix things.

Lance
*****
 
Lance, in all wisdom, typed:
For the benefit of others that are struggling with Win2k and 835732.

My IT department here at work has determined that Novell's KeyAccess
software is causing our problems with 835732 (IE won't start, can't
retrieve email). We use Novell to distribute software to clients.

We will be updating tomorrow with a new version of KeyAccess that
will - I hope - fix things.
Click to expand...

Update - this worked just fine. Our KeyAccess is now called KeyAccess 6000.
The following note from an IT guy explains the details, but it's over my
head.

Lance

*****
The long-time suspicion was that this error was caused solely by the 4.83
client. I spent forever on the phone with Microsoft today to discover that
it was Sassafras libs that preventing IE from launching. It turns out that
the Application Object for KeyAccess that was created a long long time ago
didn't place all the files in the correct locations. Normally, this doesn't
matter, since the excutable is directly run when nal.exe launches and pulls
all the libraries from the launch directory on L drive. After KB835732 had
been applied, dw15.exe (an exec that supposedly kicks off IE 6.0) was unable
to find DLLs it should have. Instead of reporting a useful error, it just
bailed.
*****
 
Back
Top