Re: Exception in ntdll.dll after MS Security update KB832483

From: carl lorentson (clorentson_at_reninfosys.com)
Date: 05/13/04 

Date: Thu, 13 May 2004 15:56:09 -0400

Hi All,

I am getting exactly the same error message on a client's machine. I've
installed the application on two systems on site - one running Windows 2000,
SP2 and one running Windows 2000 SP4. It works fine on the SP2 machine but
not the SP4. I'm assuming that he has KB832483 installed but have not been
able to get onsite yet to verify that.

Has anybody identified a work around?

The application also works fine on my development machine (Win 2k Server,
SP3 which does not have KB832483 installed) and on my laptop, Win XP, SP 1.

Additional information:
 - Developed using Delphi 4, SP3 on a windows 2000 server, sp 3
 - Uses Paradox tables
 - throws exception on start up:

Exception EOleSysError in Module VtDocketAppl.exe at 00092EAD.
Class not registered

Followed by:

Access violation at address 77F92373 in module 'ntdll.dll'. Write address
of 00000010.

Any insights, workarounds, or corrections most appreciated.

Thank you,
Carl Lorentson
Renaissance Information Systems.

"Cord Schneider" <7j2er2p02@sneakemail.com> wrote in message
news:4005372e@newsgroups.borland.com...
>
> Hi all!
>
> I have a rather urgent situation! An application that was working fine
yesterday (on my production server) now generates the following error on
start-up after applying a "critical" MS Security update
(http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security
/Bulletin/MS04-003.asp):
>
> "Access violation at address 77F92373 in module 'ntdll.dll'. Write of
address 00000010."
>
> The exception occurs when making a direct connection to an Interbase
6.0.1.0 database using InterbaseExpress v5.03 components. The application
was written and compiled in Delphi 5.0 SP1 on a WinNT4 server, and is
running on a Win2K server (both with latest updates and service packs).
>
> From what I can gather, the MS security update patches a buffer overflow
vulnerability in the MDAC components, and cannot be uninstalled.
>
> Does anyone have a clue what's happening and how I can fix this? Even a
workaround will be good right now....
>
> Thanking you in advance,
> Cord Schneider
>

Relevant Pages