A severe error occurred on the current command message when you run a query against a table that does not have a clustered index in SQL Server 2005

FIX: Error message when you run a query against a table that does not have a clustered index in SQL Server 2005: "A severe error occurred on the current command"

SYMPTOMS
Consider the following scenario. In Microsoft SQL Server 2005, you create a table that has one nonclustered index or more than one nonclustered index. The table does not have a clustered index. In this scenario, you may receive the following error message when you run a query against the table:

Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.

Additionally, you cannot display the estimated execution plan for the query, and a minidump file is generated.

RESOLUTION
The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

946608 (http://support.microsoft.com/kb/946608/LN/ ) Cumulative update package 6 for SQL Server 2005 Service Pack 2
Note 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 2005 fix release. Microsoft recommends 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:

937137 (http://support.microsoft.com/kb/937137/LN/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

WORKAROUND
To work around this issue, create a clustered index for the table. Note In some cases, this method may not work around this issue. In these cases, you must apply the cumulative update package that is described in this article.

read more here: http://support.microsoft.com/kb/948525/en-us

Necessary updates for Windows Vista

Are you running Windows Vista? Then you're going to want these two updates,which are not Windows Update at the moment:

An update that improves the performance, responsiveness, and reliability of Windows Vista is available
This update improves performance, responsiveness, and reliability of Windows Vista in various scenarios. This update resolves the following issues on a Windows Vista-based computer:
•
You receive a "Stop 0x000000A0" error when you try to switch the computer to the hibernate state.
•
You receive a "Stop 0x0000009f" error when you switch the computer to the hibernate state or to the standby state. Or, you receive this Stop error when you resume the computer from the hibernate state or from the standby state. This problem occurs on a computer that has a wireless network connection.
•
The disk does not spin down after a specified time of inactivity.Additionally, this update can help improve performance when you perform operations that are related to large disk I/O. After you apply this update, you may notice up to a 15 percent performance improvement in some copying operations and when moving some large files.



December 2007 Windows Vista Application Compatibility Update
The December 2007 Windows Vista Application Compatibility Update is a package of software updates that address common application compatibility issues in Windows Vista. When you try to install and run certain legacy games or applications in Windows Vista, you may experience one or more of the following symptoms:
•
The game, the application, or the firmware may not be installed correctly.
•
The game, the application, or the firmware may cause system instability.
•
The primary functions of the game, the application, or the firmware may not work correctly. This update is cumulative, and it supersedes update 935280. In addition to the fixes that are contained in update 935280, this update improves support in Windows Vista for the following games, applications, and firmware:
•
Adobe Acrobat Reader 7.0 - 7.07
•
WinAntivirus Pro 2007 v5.0.356
•
Webroot Software Spy Sweeper 5.0
•
Omniquad Total Security 2.0.3.0
•
Windows Internet Explorer 7 This update also includes fixes that are contained in update 932246. These fixes improve support in Windows Vista for the following applications:
•
Absolute Poker Version 5.7
•
ACDSee 8
•
Adobe Creative Suite CS2
•
Adobe Photoshop 7.0.1
•
Adobe Photoshop CS 8.0
•
Adobe Photoshop Elements Version 4.0
•
Adobe Premiere Elements 3
•
AOL 9.0 - x64
•
AOL Safety and Security Center 2.5.4.1
•
ArcSoft PhotoImpression 5
•
Auslogics Disk Defrag 1.0.3
•
AVG Anti-Spyware 7.5.0.47
•
Azureus 1.0
•
Battlefield 2 Deluxe
•
BeatJam 2006 SE
•
BitLord 1.1.5.6
•
Bitvise Tunnelier 4.20
•
Calyx Point 5.3
•
Crystal Player Professional 1.97
•
CyberLink PowerCinema 4.0
•
Delphi 7 Professional
•
Deterministic Network Extender (DNE) Driver - 3.12.2
•
Digital Zenkoku Map Townpage Database 7
•
Doranet Kids Nyugaku Jyunbi Taikenban
•
Doranet Shogaku Ichinensei Taikenban
•
EasyRecovery Professional Version 6.04
•
Family Feud Online Party
•
Google Desktop 4.2006.1008
•
HD Tach 3
•
HD Tune 2.5.1
•
IBM Rescue and Recovery with Rapid Restore 3.00
•
IBM SmartSuite Millennium Edition - Freelance Graphics 9.8
•
Justsystems Ichitaro 2006
•
Jv16 Power Tools
•
Label Mighty 6
•
LEGO Star Wars
•
Lenovo Presentation Director 1.0.0.1
•
LimeWire 4.12
•
Macromedia ColdFusion MX 7 Enterprise Edition
•
Macromedia Fireworks MX2004 7.0.2.295
•
Microsoft Age of Empires III : The Asian Dynasties Expansion Pack
•
Microsoft Age of Empires III : The WarChiefs Expansion Pack
•
Microsoft Age of Empires III
•
Microsoft DevStudio 9.0
•
Microsoft Digital Image Suite 2006
•
Microsoft Dungeon Siege II
•
Microsoft Dungeon Siege: Legends of Aranna
•
Microsoft Encarta Standard 2007
•
Microsoft Fable: The Lost Chapters
•
Microsoft Flight Simulator X
•
Microsoft Money 2005
•
Microsoft Money 2006
•
Microsoft Office 2003 Web Folders
•
Microsoft Office Outlook 2003
•
Microsoft Rise of Nations: Rise of Legends
•
Windows Small Business Server 2003 R2
•
Windows Small Business Server 2003 Service Pack 1 (SP1)
•
Windows Server 2003 Service Pack 1 (SP1) Administration Tools Pack
•
Microsoft Zoo Tycoon 2: African Adventure Expansion Pack
•
Microsoft Zoo Tycoon 2: Endangered Species Expansion Pack
•
Microsoft Zoo Tycoon 2: Marine Mania Expansion Pack
•
Microsoft Zoo Tycoon 2: Zookeeper Collection Expansion Pack
•
Microsoft Zoo Tycoon 2
•
Minna de TV Denwa Starter
•
Minna de TV Phone Starter 2.1.0.1
•
MotionDV STUDIO 5.8J for FUJITSU
•
Opera 9.02
•
Palm Desktop 6.0
•
Power Utility - Remote administration 3.1.0.0
•
RealNetworks RealPlayer 6.0.12
•
Rosetta Stone 2.1.3
•
Roxio Easy Media Creator 7.5
•
SG TCP Optimizer 2.0.3
•
SmartInstall 2.16
•
Softex OmniPass 1.0.0.1
•
Sony FeliCa Port (PaSoRi) 3.0.0.0
•
Speedbit Download Accelerator Plus (DAP) 8.1.5.6
•
SpeedFan 4.31
•
Sun Microsystems J2SE Runtime Environment 5.0 Update 9
•
Sun Microsystems Java Control Panel
•
The Weather Channel Desktop 5.0.1
•
Toshiba Tecra M7 1.70
•
Total Commander 6.55
•
Trend Micro Internet Security 2006 (PC-cillin) 14.0 – 14.59
•
Trend Micro Internet Security 2007 (PC-cillin) 15.0 – 15.19
•
TweakNow PowerPack 2006
•
Ulead DVD MovieFactory 5 Plus
•
Virtual CD 8
•
WinRaR 3.5-3.7
•
Yahoo AutoUpdater 8.1.0.249

Hotfix: FIX: A Service Broker endpoint stops passing messages in a database mirroring session of SQL Server 2005

SYMPTOMS
In a database mirroring session of Microsoft SQL Server 2005, a Service Broker endpoint stops passing messages from the initiating service to the target service. This problem occurs periodically and with increasing frequency.

When this problem occurs, a minidump file is generated. Additionally, the following error messages are repeatedly logged in the SQL Server 2005 error log:
Date Time SPID The mirror route is not operational. 'TCP://plpossrv135:4027' is acting as 'Unknown' []. 'tcp://slpossrv135:4027' is acting as 'Unknown' [].
Date Time SPID The mirror route is operational, but only connected to principal. 'TCP://plpossrv048:4027' is acting as 'Principal' []. 'tcp://slpossrv048:4027' is acting as 'Unknown' [].
Date Time Backup Log was backed up. Database: ShvaWebHO, creation date(time): 2006/07/17(23:01:56), first LSN: 50098:8649:37, last LSN: 50136:18614:1, number of dump devices: 2, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'VDI_0F67AA24-5C91-47D6-B048-7662275C1E35_0', 'VDI_0F67AA24-5C91-47D6-B048-7662275C1E35_1'}). This is an informational message only. No user action is required.
Date Time SPID Timeout occurred while waiting for latch: class 'SERVICE_BROKER_TRANSMISSION_WORK', id 0000000082EA40E0, type 4, Task 0x0000000004ACC718 : 0, waittime 300, flags 0xa, owning task 0x00000000052F9978. Continuing to wait.
Date Time SPID Using 'dbghelp.dll' version '4.0.5'
Date Time SPID **Dump thread - spid = 104, PSS = 0x0000000089DCEB40, EC = 0x0000000089DCEB50
Date Time SPID ***Stack Dump being sent to R:\Microsoft SQL Server\MSSQL.6\MSSQL\LOG\SQLDump0011.txt
Date Time SPID * *******************************************************************************
Date Time SPID *
Date Time SPID * BEGIN STACK DUMP:
Date Time SPID * 06/26/07 13:16:51 spid 104
Date Time SPID *
Date Time SPID * Latch timeout
Date Time SPID *
Date Time SPID *
Date Time SPID * *******************************************************************************
Date Time SPID * -------------------------------------------------------------------------------
Date Time SPID * Short Stack Dump
Date Time SPID Stack Signature for the dump is 0x0000000156139452
Date Time SPID Timeout occurred while waiting for latch: class 'SERVICE_BROKER_TRANSMITTER', id 0000000080283900, type 4, Task 0x0000000003C74EF8 : 0, waittime 300, flags 0x1008, owning task 0x0000000000000000. Continuing to wait.
Date Time SPID External dump process return code 0x20000001.Date

RESOLUTION
Cumulative update information
The fix for this issue was first released as a hotfix and is also available in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
941450 (http://support.microsoft.com/kb/941450/ ) Cumulative update package 4 for SQL Server 2005 Service Pack 2
Note 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 2005 fix release. We recommends 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: 937137 (http://support.microsoft.com/kb/937137/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Cumulative update package 3 for SQL Server 2005 Service Pack 2 Available

Cumulative update package 3 for SQL Server 2005 Service Pack 2 is available.

How to obtain Cumulative Update 3 for SQL Server 2005 Service Pack 2
A supported cumulative update package is now available from Microsoft. However, it is intended to correct only the problems that are described in this article. Apply it only to systems that are experiencing these specific problems. This cumulative update package may receive additional testing. Therefore, if you are not severely affected by any of these problems, we recommend that you wait for the next SQL Server 2005 service pack that contains the hotfixes in this cumulative update package.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the cumulative update package. To submit an online request to obtain the cumulative update package, visit the following Microsoft Web site:
http://go.microsoft.com/?linkid=6294451

Here is what is fixed:
50001581
938243 (http://support.microsoft.com/kb/938243/)
FIX: Error message when you run a full-text query against a catalog in SQL Server 2005: “The execution of a full-text query failed. The content index is corrupt."

50001585
938712 (http://support.microsoft.com/kb/938712/)
FIX: Some records in the fact table may not be processed when you process a dimension that contains many attributes or many members in SQL Server 2005

50001499
938962 (http://support.microsoft.com/kb/938962/)
FIX: You may receive an access violation or error 942 when you drop a database in SQL Server 2005

50001524
939563 (http://support.microsoft.com/kb/939563/)
FIX: Error message when you synchronize a merge replication in Microsoft SQL Server 2005: "MSmerge_del_, Line 42 String or binary data would be truncated"

50001582
939942 (http://support.microsoft.com/kb/939942/)
FIX: You receive an error message when you try to access a report after you configure SQL Server 2005 Reporting Services to run under the SharePoint integrated mode

50001583
940128 (http://support.microsoft.com/kb/940128/)
FIX: You receive error 8623 when you run a complex query in SQL Server 2005

50001586
940129 (http://support.microsoft.com/kb/940129/)
FIX: An MDX query does not return results when you execute the query against a cube that contains an unnatural hierarchy in a dimension in SQL Server 2005 Analysis Services

50001517
940160 (http://support.microsoft.com/kb/940160/)
FIX: Error message when you deploy a SQL Server 2005 Analysis Service project that contains many cubes, and the cubes contain linked measure groups: "Unexpected internal error"

50001449
940210 (http://support.microsoft.com/kb/940210/)
FIX: Error message when you try to insert more than 3 megabytes of data into a distributed partitioned view in SQL Server 2005: "A system assertion check has failed"

50001447
940220 (http://support.microsoft.com/kb/940220/)
FIX: Error message when you run a SQL Server 2005 Integration Services package that contains an FTP task: “An error occurred in the requested FTP operation"

50001448
940221 (http://support.microsoft.com/kb/940221/)
FIX: Error message when you try to create an Oracle publication by using the New Publication Wizard in Microsoft SQL Server 2005 Service Pack 2: “OLE DB Provider "OraOLEDB.ORACLE" for Linked server returned message "ORA-02074: Cannot RO

50001451
940223 (http://support.microsoft.com/kb/940223/)
FIX: Error message when you synchronize a subscription by using Windows Synchronization Manager in SQL Server 2005: “The merge process failed to get correct information about the Interactive Resolver component from the Registry"

50001416
940260 (http://support.microsoft.com/kb/940260/)
FIX: Error message when you use Service Broker in SQL Server 2005: "An error occurred while receiving data: '64(The specified network name is no longer available.)'"

50001435
940269 (http://support.microsoft.com/kb/940269/)
FIX: Error message when you try to edit a SQL Server Agent job or a maintenance plan by using SQL Server Management Studio in SQL Server 2005: "String or binary data would be truncated"

50001567
940281 (http://support.microsoft.com/kb/940281/)
FIX: An access violation may occur, and you may receive an error message, when you query the sys.dm_exe_sessions dynamic management view in SQL Server 2005

50001351
940370 (http://support.microsoft.com/kb/940370/)
FIX: The "User:" prefix is lost for the event information that is generated by a child package in SQL Server 2005 Integration Services after you install SQL Server 2005 Service Pack 2

50001382
940373 (http://support.microsoft.com/kb/940373/)
FIX: The performance of a Multidimensional Expressions query in SQL Server 2005 Analysis Services Service Pack 2 is much slower than the performance in earlier builds of SQL Server 2005 Analysis Services

50001433
940378 (http://support.microsoft.com/kb/940378/)
Fix: Unable to Change Transaction Isolation Level After Cursor Declaration

50001479
940384 (http://support.microsoft.com/kb/940384/)
FIX: You receive a System.InvalidCastException exception when you run an application that calls the Server.JobServer.Jobs.Contains method on a computer that has SQL Server 2005 Service Pack 2 installed

50001494
940386 (http://support.microsoft.com/kb/940386/)
FIX: You cannot install SQL Server 2005 Reporting Services Add-in for Microsoft SharePoint Technologies on a beta version of Windows Server 2008-based computer

50001602
940545 (http://support.microsoft.com/kb/940545/)
FIX: The performance of insert operations against a table that contains an identity column may be slow in SQL Server 2005

50001589
940935 (http://support.microsoft.com/kb/940935/)
FIX: Error message when you run a parallel query in SQL Server 2005 on a computer that has multiple processors: “SQL Server Assertion: File: , line=10850 Failed Assertion = 'GetLocalLockPartition () == xactLockInfo->GetLocalLockPartition ()'"

50001599
940937 (http://support.microsoft.com/kb/940937/)
FIX: Error message when you try to update the index key columns of a non-unique clustered index in SQL Server 2005: " Cannot insert duplicate key row in object 'ObjectName' with unique index 'IndexName'"

50001609
940939 (http://support.microsoft.com/kb/940939/)
FIX: Data is not rolled back after you roll back a transaction that contains a writeback operation in SQL Server 2005 Analysis Services

50001629
940942 (http://support.microsoft.com/kb/940942/)
FIX: Error message when you run a stored procedure that references a table that is upgraded from SQL Server 2000 to SQL Server 2005: “A time-out occurred while waiting for buffer latch"

50001573
940949 (http://support.microsoft.com/kb/940949/)
FIX: You receive an error message when you run an UPDATE CUBE statement to update a cube in SQL Server 2005 Analysis Services

50001576
940962 (http://support.microsoft.com/kb/940962/)
FIX: When processing a dimension on SQL Server 2005 Analysis Services an error is raised with the following format: "The following file is corrupted: Physical file: \\?\\MSMDBuildLevelStores_avl_672_29775_njzs2.tmp. Logical file ."

50001511
940126 (http://support.microsoft.com/kb/940126/)
FIX: Error 9003 is logged in the SQL Server error log file when you use log shipping in SQL Server 2005

50001436
940379 (http://support.microsoft.com/kb/940379/)
FIX: Error message when you use the UNLOAD and REWIND options to back up a database to a tape device in SQL Server 2005: "Operation on device '' exceeded retry count"

50001412
940375 (http://support.microsoft.com/kb/940375/)
FIX: Error message when you use the Copy Database Wizard to move a database from SQL Server 2000 to SQL Server 2005

50001522
939562 (http://support.microsoft.com/kb/939562/)
FIX: Error message when you run a query that fires an INSTEAD OF trigger in SQL Server 2005 Service Pack 2: "Internal Query Processor Error The query processor could not produce a query plan"

50001224
937100 (http://support.microsoft.com/kb/937100/)
FIX: Error message when you run a SQL Server 2005 Integration Services package that contains a Script Component transformation: "Insufficient memory to continue the execution of the program"

50001415
940377 (http://support.microsoft.com/kb/940377/)
FIX: Error message when you process cubes for one of the named instances of SQL Server 2005 Analysis Services: "Error opening file"

50001523
938363 (http://support.microsoft.com/kb/938363/)
FIX: Data is not replicated to a subscriber in a different partition by using parameterized row filters in SQL Server 2005

50001529
940945 (http://support.microsoft.com/kb/940945/)
FIX: Performance is very slow when the same stored procedure is executed at the same time in many connections on a multiple-processor computer that is running SQL Server 2005

50001578
939285 (http://support.microsoft.com/kb/939285/)
FIX: Error message when you run a stored procedure that starts a transaction that contains a Transact-SQL statement in SQL Server 2005: "New request is not allowed to start because it should come with valid transaction descriptor"

50001525
938086 (http://support.microsoft.com/kb/938086/)
FIX: A SQL Server Agent job fails when you run the SQL Server Agent job in the context of a proxy account in SQL Server 2005

50000872
936252 (http://support.microsoft.com/kb/936252/)
The file name of Cumulative Update 3 for SQL Server 2005 Service Pack 2 is incorrectly associated with Microsoft Knowledge Base article 936252

50000872
The MDX query performance is slow in SQL Server 2005 Analysis Services because SQL Server 2005 Analysis Services does not reuse the data cache
50001109
The dta utility stops unexpectedly and an exception occurs in SQL Server 2005
50001224
When you run a SQL Server 2005 Integration Services package that uses the VariableDispenser class, the package fails and you receive an error message
50001365
After you install SQL Server 2005 Service Pack 2, you receive error 8624 if the result set of a fast forward cursor contains a certain number of columns
50001368
After you install SQL Server 2005 Service Pack 2, the performance of a MDX query is 10 times slower than the performance on SQL Server 2005 Analysis Services build 1555
50001396
When you open a SQL Server 2005 Reporting Services report after you install SQL Server 2005 Service pack 2, the parameter toolbar and the report toolbar does not appear correctly if you specify the SP_Full value for the rc:StyleSheet URL access parameter on a report URL
50001412
Error message when you use the Copy Database Wizard to move a database from SQL Server 2000 to SQL Server 2005: "Cannot drop database "Database_Name" because it is currently in use.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly"
50001414
Error message when you use the bcp utility together with the queryout option to bulk copy data from SQL Server 2005 to a file: "SQLState = HY000, NativeError = 0 Error = [Microsoft][SQL Native Client]BCP host-files must contain at least onecolumn"
50001415
After you install SQL Server 2005 Service Pack 2, the Msmdredir.ini file is frequently updated by each instance of SQL Server 2005
50001436
Error message when you use the BACKUP DATABASE statement together with the UNLOAD option and with the REWIND option to back up a tape device in SQL Server 2005: "Operation on device 'TAPE0(<\\.\Tape0>)' exceeded retry count"
50001461
When some MDX queries are executed at the same for the same role or for the same user in SQL Server 2005 Analysis Services, the CPU usage is very high
50001475
When you open a report that contains a date and time picker (DTP) control in SQL Server 2005 Reporting Services, the format of the DTP control appears incorrectly
50001511
Error 9003 occurs when you restore a transaction log backup in SQL Server 2005
50001520
The query syntax of a report is changed when you run the report in SQL Server 2005 Reporting Services Service Pack 2 on SAP BW 3.5
50001522
Error 8624 occurs when you run a query in SQL Server 2005 Service Pack 2 (SP2) or later versions. However, you can successfully run the query in pre-SP2 version of SQL Server 2005
50001523
After you install SQL Server 2005 Service Pack 2, publications that use precomputed partitions can cause the non-convergence of data
50001525
Error message when you use SQL Server Agent to run jobs by using a proxy account: " SQLServer Error: 22046, Encryption error using CryptProtectData, CryptUnprotectData failed (1723)"
50001526
Using SQL Server Agent to run jobs in the context of a proxy account may fail with error "SQLServer Error: 22046, Encryption error using CryptProtectData, CryptUnprotectData failed (1723)"
50001529
The performance of SQL Server 2005 decreases because SQL Server 2005 is waiting for access to memory objects which is indicated by the CMEMTHREAD waittype
50001578
An exception occurs in SQL Native Client: "New request is not allowed to start because it should come with valid transaction descriptor"
50001579
When you use SQL Native Client to retrieve a value in a column of the TEXT data type, you obtain incorrect result if the value contains more than 1024 characters
50001580
Memory leak of the TokenAndPermAccessCheckResult entries occurs in SQL Server 2005
50001595
When you use SQL Native Client for a connection, the connection switches to use the auto-commit mode from the manually-commit mode
50001598
SQL Native Client overwrite error codes which causes that you do not receive informative error messages when some operations fails
50001639
The performance of an INSERT statement or an UPDATE statement that uses the result from a query is much slower in SQL Server 2005 Service Pack 2 than in SQL Server 2005 Service Pack 1 or earlier versions if the query uses the nodes method
50001164
FIX: Error message when you connect to an instance of SQL Server 2008 Analysis Services by using the AMO library that is included with SQL Server 2005 Service Pack 2 Analysis Services: "Cannot connect to Analysis Services version '10.0.1019.17'"

Hotfix: Operation on device '' exceeded retry count

FIX: Error message when you use the UNLOAD and REWIND options to back up a database to a tape device in SQL Server 2005: "Operation on device '' exceeded retry count"

SYMPTOMS
In Microsoft SQL Server 2005 Service Pack 2 (SP2), you use the UNLOAD and REWIND options to back up a database to a tape device. However, you receive an error message that resembles the following:
Operation on device 'TAPE0(<\\.\Tape0>)' exceeded retry count.

RESOLUTION
The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
939537 (http://support.microsoft.com/kb/939537/LN/ ) Cumulative update package 3 for SQL Server 2005 Service Pack 2

Get more details here: http://support.microsoft.com/kb/940379/en-US

Internal Query Processor Error The query processor could not produce a query plan

FIX: Error message when you run a query that fires an INSTEAD OF trigger in SQL Server 2005 Service Pack 2: "Internal Query Processor Error The query processor could not produce a query plan"

SYMPTOMS
Consider the following scenario. In Microsoft SQL Server 2005 Service Pack 2, you run a query that fires an INSTEAD OF trigger. The INSTEAD OF trigger references both the inserted table and the deleted table. The INSTEAD OF trigger updates the base table by using a cursor. In this scenario, you receive the following error message when you run the query:
Msg 8624, Level 16, State 1, Procedure TriggerName, Line LineNumber
Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.

RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 service pack that contains this hotfix.

Get the hotfix here: http://support.microsoft.com/kb/939562/en-US

Fix: Unable to start debugging on the web server. Debugging failed because integrated Windows authentication is not enabled

FIX: Error message when you try to debug an ASP.NET 2.0 application in Visual Studio 2005 on a Windows Vista-based computer: "Unable to start debugging on the web server. Debugging failed because integrated Windows authentication is not enabled"

SYMPTOMS
In Windows Vista Home Basic or in Windows Vista Home Premium, you create a Microsoft ASP.NET 2.0 application by using Internet Information Services (IIS) 7.0. When you try to debug the application in Microsoft Visual Studio 2005, you receive the following error message:
Unable to start debugging on the web server. Debugging failed because integrated Windows authentication is not enabled. Please see Help for assistance.

CAUSE
This problem occurs because Windows Vista Home Basic and Windows Vista Home Premium do not contain the Windows Authentication module for IIS. When the client tries to automatically attach the debugger in an ASP.NET 2.0 application, the client sends a HTTP request that contains the DEBUG verb. This HTTP request is used to verify that the process of the application is running and to select the correct process to attach. This HTTP request must be authenticated by using Windows Authentication. However, Windows Vista Home Basic and Windows Vista Home Premium do not contain the Windows Authentication module for IIS. Therefore, the problem that is described in the 'Symptoms" section occurs.


RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio 2005 service pack that contains this hotfix.

Download the Hotfix here: http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=7250

FIX: "HttpException (0x80004005): '/HandlerTest/WebForm1.aspx/a:b' is not a valid virtual path"

FIX: Error message when you try to visit an ASP.NET 2.0-based Web page: "HttpException (0x80004005): '/HandlerTest/WebForm1.aspx/a:b' is not a valid virtual path"

When you try to visit a Microsoft ASP.NET 2.0-based Web page, you may receive an error message that resembles the following:
HttpException (0x80004005): '/HandlerTest/WebForm1.aspx/a:b' is not a valid virtual path.
This problem occurs if the virtual path in the URL contains one of the following symbols:
• Colon (:)
• Asterisk (*)

For example, this problem occurs when you try to visit one of the following URLs:
• http://www.adventure:works.com/test.aspx
• http://www.adventure*works.com/test.aspx

Note This problem occurs even if you use the method that is described in Microsoft Knowledge Base article 826437 to set the value of the following registry subkey to 1:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET VerificationCompatibility


Get the HotFix here: http://support.microsoft.com/kb/932552/en-us?spid=8940&sid=global

Cumulative update package (build 3161) for SQL Server 2005 Service Pack 2 is available

How to obtain the cumulative update package (build 3161) for SQL Server 2005 SP2
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
http://go.microsoft.com/?linkid=6294451

SQL Hotfix bug number Knowledge Base article number Description
50000939 933508 Microsoft SQL Server 2005 Service Pack 2 issue: Cleanup tasks run at different intervals than intended

50000787 929240 FIX: I/O requests that are generated by the checkpoint process may cause I/O bottlenecks if the I/O subsystem is not fast enough to sustain the IO requests in SQL Server 2005

50000784 930505 FIX: Error message when you run DML statements against a table that is published for merge replication in SQL Server 2005: "Could not find stored procedure"

50000783 930691 FIX: SQL Server Profiler stops monitoring the instance after a time when you use SQL Server Profiler to monitor an instance of SQL Server 2005 Analysis Services

50000785 930775 FIX: Error message when you try to retrieve rows from a cursor that uses the OPTION (RECOMPILE) query hint in SQL Server 2005: "Could not complete cursor operation because the table schema changed after the cursor was declared"

50000873 931329 FIX: Error message when you run a query in Microsoft SQL Server 2005: "Msg 8624, Level 16, State 116 Internal Query Processor Error: The query processor could not produce a query plan"

50000875 932115 FIX: The ghost row clean-up thread does not remove ghost rows on some data files of a database in SQL Server 2005

50000900 933549 FIX: You may receive an access violation when you perform a bulk copy operation in SQL Server 2005

50000949 934109 FIX: The Distribution Agent generates an access violation when you configure a transactional replication publication to run an additional script after the snapshot is applied at the subscriber in SQL Server 2005

50000952 934188 FIX: The Distribution Agent does not deliver commands to the Subscriber even if the Distribution Agent is running in SQL Server 2005

50000958 934226 FIX: Error message when you try to use Database Mail to send an e-mail message in SQL Server 2005: "profile name is not valid (Microsoft SQL Server, Error 14607)"

50001012 934459 FIX: The Check Database Integrity task and the Execute T-SQL Statement task in a maintenance plan may lose database context in certain circumstances in SQL Server 2005 builds 3150 through 3158

50000948 934106 FIX: SQL Server 2005 database engine generates failed assertion errors when you use the Replication Monitor to monitor the distribution database

50000786 An application that uses Analysis Services 9.0 OLE DB Provider (Msolap90.dll) to connect to SQL Server 2005 Analysis Services may experience a memory leak.

50000810 When you update a view by using a cursor, error 16934 occurs. The error message for error 16934 is as follows: "Optimistic concurrency check failed. The row was modified outside of this cursor."

50000809 The lazywriter process may cause high CPU usage in SQL Server 2005 on a computer that has "non-uniform memory access" (NUMA) architecture.

50000874 The disk space that is allocated for temporary tables may not be released. This problem occurs when a temporary table is created on a connection that has the SET XACT_ABORT option set to ON.

50000889 In the Data Mining Client for Excel add-in, you perform the Analyze Key Influencers action against a SQL Server 2005 Analysis Services Standard Edition server. When you do this, you receive the following error message: "The 'MINIMUM_DEPENDENCY_PROBABILITY' data mining parameter is not valid for the 'ATableName' model."

50000921 A transactional replication publication that involves replicated procedure executions may cause error 701. The error message for error 701 is as follows: "There is insufficient system memory to run this query."

50000945 The USERSTORE_TOKENPERM SQL Server 2005 memory cache may grow too large. Therefore, high CPU utilization occurs, or "out of memory" errors occur.

50000964 SQL Server 2005 may select a poorly performing query plan for a query that references a scalar user-defined function that performs data access.

50000969 In SQL Server 2005, assertion error 3624 may occur. The error message for assertion error 3624 is as follows: "Attempt to access expired blob handle (3)."

50000918 When you run a query that uses the FOR XML clause together with the TYPE directive, the query may fail. Additionally, error 6611 may occur. The error message for error 6611 is as follows: "The XML data type is damaged."

50000960 A content query from the Data Mining Client for Excel add-in may take a long time to display the result set. This problem occurs especially when the result set is large. Microsoft Office Excel may appear to stop responding (hang) when the query is running.

50000919 When you run an encrypted stored procedure, error 565 may occur. The error message for error 565 is as follows: "A stack overflow occurred in the server while compiling the query. Please simplify the query."

50001026 After you perform a piecemeal restoration of a database that uses the vardecimal storage format, filegroups may be marked as defunct.

50001083 When you join an int data type column together with a bigint data type column, you may obtain incorrect results. This problem occurs if the join uses bitmap filtering.

50001076 Tables in SQL Server 2005 Reporting Services reports may not be displayed correctly when you view the reports in Microsoft Office Outlook 2007.

50001105 After you apply SQL Server 2005 SP2, the Print Preview feature in Reporting Services may show a solid black page.



Read more here: http://support.microsoft.com/kb/935356

You may receive an exception when you browse a .NET Framework 2.0 ASP.NET Web application Hotfix

SYMPTOMS
When you browse a Microsoft .NET Framework 2.0 ASP.NET Web application, you may receive one of the following exceptions:

Exception 1
Exception type: FileNotFoundException Exception message: Could not load file or assembly 'App_Web_-e9dbmaj, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

Exception 2
Compiler Error Message: CS0006: Metadata file 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\cms.web\44e73607\b028acb3\App_global.asax.fakktchx.dll' could not be found


Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft .NET Framework 2.0 service pack that contains this hotfix.

Download the hotfix here: http://support.microsoft.com/default.aspx/kb/934839