C:\Program Files\Microsoft SQL
Tried to start SQLdiag and got pop-up error "Buffer overrun detected! ... The program cannot safely continue execution and must now be terminated" [Header on pop-up "Microsoft Visual C++ Runtime Library"]
========== CLI output
Server\MSSQL\Binn>sqldiag
Connecting to server RED70
Getting file d:\mssql_data\MSSQL\log\ERRORLOG
Getting file d:\mssql_data\MSSQL\log\ERRORLOG.1
Getting file d:\mssql_data\MSSQL\log\ERRORLOG.2
Getting file d:\mssql_data\MSSQL\log\ERRORLOG.3
Getting file d:\mssql_data\MSSQL\log\ERRORLOG.4
Getting file d:\mssql_data\MSSQL\log\ERRORLOG.5
Getting file d:\mssql_data\MSSQL\log\ERRORLOG.6
Getting registry information
=============
Using MS SQL 2000 SP4 v.8.00.2040, on Windows 2000 AdvServ SP4 5.00.2195
Am I only one who is unlucky?
Discussion on:
View:
Show:
detected a stop (I did nothing) and shut down before I could 'generate' the issue.
This was XP SP2 , detected both my 2000 server (SP4) and 2005 Express, on my development workstation.
Didn't even now this was there, tend to use an error logging extension in my apps coupled with either application knowledge or the profiler to find these.
Can you replicate the error or are you fishing for an intermittant error?
This was XP SP2 , detected both my 2000 server (SP4) and 2005 Express, on my development workstation.
Didn't even now this was there, tend to use an error logging extension in my apps coupled with either application knowledge or the profiler to find these.
Can you replicate the error or are you fishing for an intermittant error?
I've had a problem before with this utility one time before, and I believe it had to do with the SP that I was running on SQL. I think that either SP3 or SP4 had a problem installing this utility. If you have an install of sql with sp2 or before, you can copy the executable from that install, or perhaps from the sql cd. That should solve your issue.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
