Server Becomes unresponsive

[Guest]

I do not know if the following occurs becuase of SQL 2005 or it Win2k
related, but here goes...

O/S = Windows 2000 Server SP4, PDC with AD 2003 extensions, DNS, DHCP

SQL Server 9.00.1399.06

The problem starts with an event logged as Source = Application Popup Event
= 26 Description = Application popup: vsjitdebugger.exe - Application Error :
The application failed to initialize properly (0xc0000142). Click on OK to
terminate the application.

After this error starts it continues for 5 or 6 times within a couple of
minutes during which time other services start logging errors and the server
becomes unresponsive to requests. Netlogon starts throwing errors, Server
errors with unable to map error code 1453 start showing up, MS SQL Server
errors start with unable to load SSL provider library, Userenv errors
start,Windows cannot connect to msm.local with (0x2747) , AD becomes
unresposive with inability to contact global catalog (which is on the same
machine), and eventually terminates with a Journal Wrap Error.

All of the above occurs on a random basis, but always with the same pattern
once it starts, this has happend a dozen times since SQL was installed in
November, but never before.

Any and all help on this is appreciated.



Thanks...

 

[John John]

Sounds like a problem with Visual Studio debugger. Try the OPPOSITE of
what is explained here:
http://windowssdk.msdn.microsoft.co...html/65850ac2-84d0-4762-a657-91134dba2858.asp

In other words, delete the vsjitdebugger.exe key in the registry.

DISCLAIMER: Improperly editing the registry may cause your system not
to boot... yada, yada, yada. Export and save the key before you delete it.

John

 

[Guest]

The problem is not the debugger it is the app that is failing and causing the
debugger to launch, but I have no way of knowing what application that is.
That's why I think it has something to do with SQL 2005; I'm sure there are
som components written in CLR.