Article ID: 939285
Article Last Modified on 11/20/2007
APPLIES TO
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Workgroup Edition
Bug: #50001379 (SQL Hotfix)
Notice
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.
SUMMARY
This article describes the following about this hotfix release:
- The problems that are fixed by the hotfix package
- The prerequisites for installing the hotfix package
- Whether you must restart the computer after you install the hotfix package
- Whether the hotfix package is replaced by any other hotfix package
- Whether you must make any registry changes
- The files that are contained in the hotfix package
SYMPTOMS
Consider the following scenario. You develop a Microsoft SQL Server 2005-based application that uses the SQL Native Client ODBC provider. In the application, you run a stored procedure by calling an ODBC function in synchronous mode. The stored procedure starts a transaction that contains a Transact-SQL statement. In this scenario, if the Transact-SQL statement times out, the successive statements contain the following error message:
RESOLUTION
Hotfix information
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 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:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
- SQL Server 2005 Service Pack 2
For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:913089 How to obtain the latest service pack for SQL Server 2005
Restart information
You do not have to restart the computer after you apply this hotfix.
Registry information
You do not have to change the registry.
Hotfix file information
This hotfix contains only the files that are required to correct the problems that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build. The 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.
SQL Server 2005 32-bit version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Microsoft.analysisservices.dll | 9.0.3177.0 | 1,217,904 | 25- | 19:28 | x86 |
| Microsoft.sqlserver.maintenanceplantasks.dll | 9.0.3177.0 | 296,304 | 25- | 19:28 | x86 |
| Msmdlocal.dll | 9.0.3177.0 | 15,948,144 | 25- | 19:28 | x86 |
| Mssqlsystemresource.ldf | Not Applicable | 524,288 | 25- | 13:30 | Not Applicable |
| Mssqlsystemresource.mdf | Not Applicable | 40,108,032 | 25- | 13:30 | Not Applicable |
| Odsole70.dll | 2005.90.3177.0 | 59,248 | 25- | 19:28 | x86 |
| Rdistcom.dll | 2005.90.3177.0 | 644,976 | 25- | 19:28 | x86 |
| Replmerg.exe | 2005.90.3177.0 | 320,880 | 25- | 19:28 | x86 |
| Replrec.dll | 2005.90.3177.0 | 784,752 | 25- | 19:28 | x86 |
| Sqlaccess.dll | 2005.90.3177.0 | 350,576 | 25- | 19:28 | x86 |
| Sqlservr.exe | 2005.90.3177.0 | 29,193,072 | 25- | 19:28 | x86 |
| Sqlwep.dll | 2005.90.3177.0 | 90,992 | 25- | 19:28 | x86 |
| Sqsrvres.dll | 2005.90.3177.0 | 70,512 | 25- | 19:28 | x86 |
| Sysdbupg.sql | Not Applicable | 510,622 | 10- | 16:40 | Not Applicable |
| Xpstar90.dll | 2005.90.3177.0 | 295,792 | 25- | 19:28 | x86 |
SQL Server 2005 x64-based version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Microsoft.analysisservices.dll | 9.0.3177.0 | 1,217,904 | 25- | 19:28 | x86 |
| Microsoft.sqlserver.maintenanceplantasks.dll | 9.0.3177.0 | 296,304 | 25- | 19:28 | x86 |
| Msmdlocal.dll | 9.0.3177.0 | 15,948,144 | 25- | 19:28 | x86 |
| Mssqlsystemresource.ldf | Not Applicable | 524,288 | 25- | 13:30 | Not Applicable |
| Mssqlsystemresource.mdf | Not Applicable | 40,108,032 | 25- | 13:30 | Not Applicable |
| Odsole70.dll | 2005.90.3177.0 | 90,480 | 25- | 19:38 | x64 |
| Rdistcom.dll | 2005.90.3177.0 | 828,784 | 25- | 19:38 | x64 |
| Replmerg.exe | 2005.90.3177.0 | 417,648 | 25- | 19:38 | x64 |
| Replrec.dll | 2005.90.3177.0 | 1,011,568 | 25- | 19:38 | x64 |
| Sqlaccess.dll | 2005.90.3177.0 | 357,744 | 25- | 19:38 | x86 |
| Sqlservr.exe | 2005.90.3177.0 | 39,697,264 | 25- | 19:38 | x64 |
| Sqlwep.dll | 2005.90.3177.0 | 90,992 | 25- | 19:28 | x86 |
| Sqlwep.dll | 2005.90.3177.0 | 123,760 | 25- | 19:38 | x64 |
| Sqsrvres.dll | 2005.90.3177.0 | 83,312 | 25- | 19:38 | x64 |
| Sysdbupg.sql | Not Applicable | 510,622 | 10- | 16:40 | Not Applicable |
| Xpstar90.dll | 2005.90.3177.0 | 546,672 | 25- | 19:38 | x64 |
WORKAROUND
To work around this problem, run the stored procedure in asynchronous mode.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kbfix kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver kbsql2005engine KB939285
