I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
(Active/ Passive), and have started to get Buffer Overrun errors on running
SQLDiag - as follows :
/********************************
Event ID: 26
User: N/A
Description:
Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
detected!
Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
A buffer overrun has been detected which has corrupted the program's
internal state. The program cannot safely continue execution and must
now be terminated.
/********************************
SQLDiag is being run by an SQL job running an OS command as follows :
SQLDiag -O Z:\Outputsqldiag.txt -E -C
This was always successful prior to the installation of SP4. There seems to
be nothing about this on the web...
Any thoughts or comments gratefully received.This is a known bug... I don't think there is anything you can do about it
until it is fixed, but it has been reported...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"BarryC" <BarryC@.discussions.microsoft.com> wrote in message
news:45D5EBF1-0642-46D9-A3A0-696FBC1C2650@.microsoft.com...
>I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> (Active/ Passive), and have started to get Buffer Overrun errors on
> running
> SQLDiag - as follows :
> /********************************
> Event ID: 26
> User: N/A
> Description:
> Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> detected!
> Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> A buffer overrun has been detected which has corrupted the program's
> internal state. The program cannot safely continue execution and must
> now be terminated.
> /********************************
> SQLDiag is being run by an SQL job running an OS command as follows :
> SQLDiag -O Z:\Outputsqldiag.txt -E -C
> This was always successful prior to the installation of SP4. There seems
> to
> be nothing about this on the web...
> Any thoughts or comments gratefully received.|||SQLDiag.exe upgraded by SP4 has this Buffer overrun issue. Follow this work
around for an immediate solution
Rename the existing SQLDiag.exe (SP4)
Copy the SQLDiag.exe from the SQL Server Setup CD (Version 2000.80.194.0) to
the Binn folder
This old version SQLDiag works fine with the SP4. I tested this solution
and it works fine.
"BarryC" wrote:
> I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> (Active/ Passive), and have started to get Buffer Overrun errors on running
> SQLDiag - as follows :
> /********************************
> Event ID: 26
> User: N/A
> Description:
> Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> detected!
> Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> A buffer overrun has been detected which has corrupted the program's
> internal state. The program cannot safely continue execution and must
> now be terminated.
> /********************************
> SQLDiag is being run by an SQL job running an OS command as follows :
> SQLDiag -O Z:\Outputsqldiag.txt -E -C
> This was always successful prior to the installation of SP4. There seems to
> be nothing about this on the web...
> Any thoughts or comments gratefully received.|||Thanks for that - in testing at the moment, but its looking good. Have MS
got an official line on this one yet?
"M. S. Reddy" wrote:
> SQLDiag.exe upgraded by SP4 has this Buffer overrun issue. Follow this work
> around for an immediate solution
> Rename the existing SQLDiag.exe (SP4)
> Copy the SQLDiag.exe from the SQL Server Setup CD (Version 2000.80.194.0) to
> the Binn folder
> This old version SQLDiag works fine with the SP4. I tested this solution
> and it works fine.
>
>
>
> "BarryC" wrote:
> > I have applied SQL SP4 to a SQL Server running on a Windows 2000 Cluster
> > (Active/ Passive), and have started to get Buffer Overrun errors on running
> > SQLDiag - as follows :
> >
> > /********************************
> > Event ID: 26
> > User: N/A
> > Description:
> > Application popup: Microsoft Visual C++ Runtime Library : Buffer overrun
> > detected!
> >
> > Program: C:\PROGRA~1\MICROS~3\MSSQL\binn\SQLDiag.exe
> >
> > A buffer overrun has been detected which has corrupted the program's
> > internal state. The program cannot safely continue execution and must
> > now be terminated.
> > /********************************
> >
> > SQLDiag is being run by an SQL job running an OS command as follows :
> >
> > SQLDiag -O Z:\Outputsqldiag.txt -E -C
> >
> > This was always successful prior to the installation of SP4. There seems to
> > be nothing about this on the web...
> >
> > Any thoughts or comments gratefully received.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment