SQL Server Q&A

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries Tagged ‘article number’

FIX: Extended Stored Procedure “xp_logevent” Generates an Access Violation When Given Too Large a Parameter

Symptoms
Any string that is longer than 8000 bytes that is given as a second parameter to the xp_logevent stored procedure, causes the following error message to occur:

ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 51 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
ODBC: Msg 0, Level 20, State 1
Stored function ‘xp_logevent’ in the library ‘xplog70.dll’ generated an
access violation. SQL Server is terminating process 51.
Resolution
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
290211?(http://support.microsoft.com/kb/290211/EN-US/) INF: How to Obtain the Latest SQL Server 2000 Service Pack

FIX: DBCC CHECKDB May Produce an Access Violation When Database Is in Use

Symptoms
The DBCC CHECKDB command may produce an access violation (AV) when run on a database while other users are actively accessing the database.
Resolution
To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
290211?(http://support.microsoft.com/kb/290211/EN-US/) INF: How to Obtain the Latest SQL Server 2000 Service Pack

FIX: You receive an error message when you click the View Single Column Profile By Column button in the Data Profile Viewer in SQL Server 2008: “Unhandled Exception”

Symptoms
In Microsoft SQL Server 2008, when you click the View Single Column Profile By Column buttonin the Data Profile Viewer (DataProfileViewer.exe), you receive the following error message:

Unhandled Exception
Resolution
The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
956717?(http://support.microsoft.com/kb/956717/) Cumulative update package 1 for SQL Server 2008Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
956909?(http://support.microsoft.com/kb/956909/) The SQL Server 2008 builds that were released after SQL Server 2008 was released

FIX: The Shared Memory protocol for an instance of SQL Server 2008 is always enabled and the VIA protocol for the instance is always disabled after you repair the instance

Symptoms
After you repair an instance of Microsoft SQL Server 2008, the Shared Memory protocol for the instance is always enabled. Additionally, the VIA protocol for the instance is always disabled.
You can use several methods to run the repair operation. For example, you can repair an instance by using theAdd or Remove Programs item in Control Panel.
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for SQL Server 2008. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
968382?(http://support.microsoft.com/kb/968382/) How to obtain the latest service pack for SQL Server 2008