How to resolve SQLDiag issue

[nessty]

thread962-1401307

Hi I noticed SQLBill had a similar problem way back in 2007 which was posted on this site. We have a Honeywell Experion 2003 Server whose sqldiag.txt grows very large and eats up all the space in the hard drive. In January of this year it grew to 170GB and we were unable to open it because it is always in use and too large. We deleted it then and referred the case to Honeywell. It is growing again and at 2GB right now. Does anyone know of this problem? What is causing it? And how to resolve it?
The SQL Error logs also show Error 9002 Severity 17 State 6 and for waht its worth this server has shutdown (on its own) 4 times in the last 7 months.

 

[ousoonerjoe]

I can tell you that Severity 17 means "Indicates that the statement caused SQL Server to run out of resources (such as memory, locks, or disk space for the database) or to exceed some limit set by the system administrator."

--------------------------------------------------
“Crash programs fail because they are based on the theory that, with nine women pregnant, you can get a baby a month.” --Wernher von Braun
--------------------------------------------------

 

[nessty]

Thanks, appreciate it. Anyone else?

 

[SQLBill]

We narrowed it down to two possibilities...

1. Another process accessing the sqldiag.txt file while it is being written to.
--check when your anti-virus program runs. Is it accessing the sqldiag.txt file? Try setting up the av program to ignore that file.
--is there a backup (SQL or OS) copying that file at the same time it is being written to?

2. Is sqldiag being run manually or from a scheduled job?
--if a buffer overrun check happens, sqldiag will pop up a dialog box for the user to respond to. If you are running it via a job, you won't see the pop up box and can't respond to it.

Microsoft says that SQLDiag will return a Buffer Overrun check if “compilation code detected the presence of the potential for a buffer overrun condition and trapped this to a dialog box. The dialog box allows the user to accept or to deny and thus prevent any malicious attempts to compromise system integrity.”

Ref:

http://support.microsoft.com/kb/902955

It’s not really a security issue (per Microsoft) since SQLDiag has to be run via admin access. However, the error returns a dialog box that requires a response from the person running SQLDiag.

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875