.NET Questions and Solutions

Symptoms
After you upgrade a Microsoft SQL Server 2000-based computer to Microsoft SQL Server 2000 Service Pack 4 (SP4), a SQL Server query that calls a registry extended stored procedure may fail, and you receive the following error message:

Access is denied.You receive the error message when you use any one of the registry extended stored procedures in the following list: xp_regreadxp_instance_regreadxp_regenumkeysxp_instance_regenumkeysxp_regenumvaluesxp_instance_regenumvaluesxp_regwritexp_instance_regwritexp_regaddmultistringxp_instance_regaddmultistringxp_regremovemultistringxp_instance_regremovemultistringxp_regdeletevaluexp_instance_regdeletevaluexp_regdeletekeyxp_instance_regdeletekey
Resolution
This problem occurs because SQL Server 2000 SP4 implements a restriction on which registry paths the registry extended stored procedures can access. When a query calls a registry extended stored procedure, the registry extended stored procedure examines the requested registry subkey against a control list of registry hives. If the registry subkey that the query requests is not in the control list, you receive the following error message:

‘Access is denied.’ This error message has nothing to do with the permissions of the SQL Server user account in the context of which one of these registry extended stored procedures is called. The error message occurs even if the user has Administrator permissions.
Note When you receive the error message, the registry extended stored procedure returns no results.

Symptoms
An INSERT, UPDATE, or DELETE query that operates on a table that is referenced by an indexed view may encounter a floating point exception during optimization. The batch and transaction is aborted, and you receive the following error message:

Server: Msg 3628, Level 16, State 1, Line 1
A floating point exception occurred in the user process. Current transaction is canceled.
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290211?(http://support.microsoft.com/kb/290211/) How to obtain the latest SQL Server 2000 service pack
Hotfix informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

DateTimeVersionSizeFile name——————————————————————-31-May-200317:452000.80.818.078,400Console.exe25-Jun-200300:012000.80.818.033,340Dbmslpcn.dll25-Apr-200301:12786,432Distmdl.ldf25-Apr-200301:122,359,296Distmdl.mdf30-Jan-200300:55180Drop_repl_hotfix.sql12-Sep-200302:262000.80.859.01,905,216Dtspkg.dll26-Aug-200319:162000.80.854.0528,960Dtspump.dll23-Jun-200321:402000.80.837.01,557,052Dtsui.dll23-Jun-200321:402000.80.837.0639,552Dtswiz.dll24-Apr-200301:51747,927Instdist.sql03-May-200300:561,581Inst_repl_hotfix.sql08-Feb-200305:402000.80.765.090,692Msgprox.dll01-Apr-200301:071,873Odsole.sql05-Apr-200300:462000.80.800.062,024Odsole70.dll07-May-200319:412000.80.819.025,144Opends60.dll02-Apr-200320:482000.80.796.057,904Osql.exe02-Apr-200322:152000.80.797.0279,104Pfutil80.dll04-Aug-200317:17550,780Procsyst.sql11-Sep-200323:3712,305Qfe469315.sql22-May-200321:5719,195Qfe469571.sql06-Sep-200300:361,090,932Replmerg.sql06-Sep-200306:182000.80.858.0221,768Replprov.dll06-Sep-200306:182000.80.858.0307,784Replrec.dll05-Sep-200323:001,087,150Replsys.sql13-Aug-200315:28986,603Repltran.sql29-Jul-200319:132000.80.819.0492,096Semobj.dll31-May-200317:272000.80.818.0172,032Semobj.rll05-Aug-200320:06127,884Sp3_serv_uni.sql01-Jun-200300:012000.80.818.04,215,360Sqldmo.dll07-Apr-200316:4425,172Sqldumper.exe19-Mar-200317:202000.80.789.028,672Sqlevn70.rll01-Jul-200323:182000.80.834.0180,736Sqlmap70.dll03-Sep-200301:562000.80.857.0188,992Sqlmmc.dll02-Sep-200322:032000.80.857.0479,232Sqlmmc.rll08-Feb-200305:402000.80.765.057,920Sqlrepss.dll23-Sep-200300:032000.80.863.07,614,545Sqlservr.exe25-Jul-200320:442000.80.845.0590,396Sqlsort.dll08-Feb-200305:402000.80.765.045,644Sqlvdi.dll25-Jun-200300:012000.80.818.033,340Ssmslpcn.dll01-Jun-200300:012000.80.818.082,492Ssnetlib.dll01-Jun-200300:012000.80.818.025,148Ssnmpn70.dll01-Jun-200300:012000.80.818.0158,240Svrnetcn.dll31-May-200317:592000.80.818.076,416Svrnetcn.exe30-Apr-200322:522000.80.816.045,132Ums.dll01-Jul-200323:192000.80.834.098,816Xpweb70.dll Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Symptoms
This article describes the following about this hotfix release: The issues that are fixed by this hotfix packageThe prerequisites for installing this hotfix packageWhether you must restart the computer after you apply this hotfix packageWhether this hotfix package is replaced by any other hotfix packageWhether you must make any registry changes after you apply this hotfix packageThe files that are contained in this hotfix package
Resolution
When you try to create a snapshot report in Microsoft SQL Server 2005 Reporting Services, the following exception may be logged in the Reporting Services log:

System.NullReferenceException Additionally, you may experience the following problems: You may notice that mini-dump files have been created in the LogFiles folder for Reporting Services. By default, the path of the LogFiles folder is as follows:
C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFilesNote The folder name MSSQL.3 is a placeholder because this folder name may vary, depending on which SQL Server services you have installed.The mini-dump files are created at a fixed interval.Note You may also experience these problems in Microsoft SQL Server 2000 Reporting Services.

Symptoms
In Microsoft SQL Server 2000, when you run a query that contains a RIGHT OUTER JOIN clause, you may receive an error message that is similar to the following:

ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 52 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Connection Broken
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290211?(http://support.microsoft.com/kb/290211/) How to obtain the latest SQL Server 2000 service pack

Symptoms
Although the MSSQLServer service does not stop, the Microsoft Operations Manager (MOM) 2005 Operator Console contains a Critical Error severity alert that is similar to the following alert:

Name: The MSSQLServer service terminated unexpectedlySeverity: Critical ErrorResolution State: NewDomain: WORKGROUPComputer: ComputerNameTime of First Event: TimeTime of Last Event: TimeAlert latency: 1 secProblem State: InvestigateRepeat Count: 3Age:Source: MSSQLSERVERAlert Id: 390da845-d0c7-4570-b895-cb265d13addaRule (enabled): Microsoft SQL Server\SQL Server 2000\SQL Server 2000 Event Collection\SQL Server General\The MSSQLServer service terminated unexpectedlyDescription: SqlDumpExceptionHandler: Process 56 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Resolution
This issue occurs when the following conditions are true: You enable the The MSSQLServer service terminated unexpectedly event rule. This event rule has the following criteria in the MOM 2005 Administrator Console: The Event Number event property matches the following code:

regex ^(17052|17055)$The Source Name event property matches the following code:

wildcard MSSQL*The Description event property matches the following code:

substring Error: 0, Severity: 19, State: 0You receive an error message that has a severity level 19 in Microsoft SQL Server 2000 that is similar to the following error message:

ODBC: Msg 0. Level 19, State 1SqlDumpExceptionHandler: Process 56 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.Connection Broken

Symptoms
You may find that you cannot create a portal site in Microsoft Office SharePoint Portal Server 2003.When you try to create a portal site, you may experience one or more of the following symptoms: You receive an error message that is similar to the following:

System.NullReferenceException: Object reference not set to an instance of an objectEntries that are similar to the following are logged to the log file:

Time Start- Add custom roles to fine-grained lists
Time End- Add custom roles to fine-grained lists
Time Exit InitCategories()
Time Failed to create portal successfully
Time cmd.CommandText set as: Update dbo.orgle_errormsg set LocalizedMsg = N’User’ where ErrorID=’-1′ Update dbo.orgle_errormsg set LocalizedMsg = N’Target Audiences’ where ErrorID=’-2′ Update dbo.orgle_errormsg set LocalizedMsg = N’Select Audience’ where ErrorID=’-3′ Update dbo.orgle_errormsg set LocalizedMsg = N’Select’ where ErrorID=’-4′ Update dbo.orgle_errormsg set LocalizedMsg = N’Compilation failed to start due to an error connecting to the database. Please check the AudienceJob log file for details.’ where ErrorID=’1′ Update dbo.orgle_errormsg s
Resolution
This issue may occur in situations when there arenetwork connectivity problems that prevent you from connecting to the server that is running Microsoft SQL Server 2000, and the server that is running SQL Server 2000 uses the following configuration:The server is configured to use named pipes.The server is not configured to use TCP/IP.