Thursday, March 29, 2012

Dr Watson error after writing to SQL Server

I have a VB6 program that receives data using socket and save the data to a
SQL Server 2000 database.
It has Windows 2000 SP4 with all hot patches in it. It has 2 gig of RAM.
The program had been running for years with no problem, but for the last 3
days it had died exactly at 3 AM, right after it finished writing the data
to SQL Server.
No error on the screen, but there is Dr.
Watson error (it is in drwtsn32.log).
The error in drwtsn32.log is:
Exception number: c0000005 (access violation) --> this is on this VB
program.
I do not know how to read Dr Watson log, but the "Raw Stack Dump" contains
c:\winnt\system32\comsvcs.dll.
I searched on the internet and found that there was an Access Violation
error with comsvcs.dll, and the fix is to install the latest Windows
patches, which we already did. We also increased the memory from 1 gig RAM
to 2 gig. The program still happens.
There is no scheduled task running at 3 AM.
Does anybody know how to read Dr Watson log ?
How can I fix this problem ?
Thank you very much.The previous 2 days when the program did not write to the SQL Server
database, the program did not die.
But today, it starts writing to the database again, and it again died at 3
am. The program writes to the database every minute every day without any
problem, except after it finishes writing to the database at 3 am.
I found this article that talks about Access Violation error and SQL Server
(but it is with Windows 2003, and I am using Windows 2000)
http://ask.support.microsoft.com/kb/910471
Symptoms
An access violation occurs in Microsoft Distributed Transaction Coordinator
(MS DTC) when a client that is connected to an MS DTC clustered resource
tries to create an enlistment in MS DTC. For example, this problem may occur
if a computer where Microsoft SQL Server is installed loses synchronization
with an MS DTC server and then tries to enlist a transaction in MS DTC.
Cause
This problem occurs because of two race conditions in the MS DTC code. In
one race condition, the transaction manager (TM) tries to create a trace
before an interface pointer to perform that trace exists. A second race
condition exists when the MS DTC proxy sends TMDown notifications to
enlistments and resource managers.
Could that problem related to my problem, even though for different Windows
version ? What does it mean by "Microsoft SQL Server is installed loses
synchronization with an MS DTC server and then tries to enlist a transaction
in MS DTC" ?
Thanks.
"fniles" <fniles@.pfmail.com> wrote in message
news:uW9dGglNHHA.1872@.TK2MSFTNGP04.phx.gbl...
>I have a VB6 program that receives data using socket and save the data to a
> SQL Server 2000 database.
> It has Windows 2000 SP4 with all hot patches in it. It has 2 gig of RAM.
> The program had been running for years with no problem, but for the last 3
> days it had died exactly at 3 AM, right after it finished writing the data
> to SQL Server.
> No error on the screen, but there is Dr.
> Watson error (it is in drwtsn32.log).
> The error in drwtsn32.log is:
> Exception number: c0000005 (access violation) --> this is on this VB
> program.
> I do not know how to read Dr Watson log, but the "Raw Stack Dump" contains
> c:\winnt\system32\comsvcs.dll.
> I searched on the internet and found that there was an Access Violation
> error with comsvcs.dll, and the fix is to install the latest Windows
> patches, which we already did. We also increased the memory from 1 gig RAM
> to 2 gig. The program still happens.
> There is no scheduled task running at 3 AM.
> Does anybody know how to read Dr Watson log ?
> How can I fix this problem ?
> Thank you very much.
>
>

No comments:

Post a Comment