Article ID: 902150 - Last Review: June 19, 2007 - Revision: 5.4 FIX: Some 32-bit applications that use SQL-DMO and SQL-VDI APIs may stop working after you install SQL Server 2000 Service Pack 4 on an Itanium-based computer
Bug #: 20000151 (SQL Server 8.0) Microsoft distributes Microsoft SQL Server 2000 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 2000 fix release. On This PageSUMMARYThis article describes the following about this hotfix release:
SYMPTOMSYou install Microsoft SQL Server 2000 Service Pack 4 (SP4) on an Itanium-based computer that is running a 64-bit version of Microsoft SQL Server 2000. When you do this, some 32-bit applications that are running on the local computer may stop working. The applications that stop working use SQL Distributed Management Objects (SQL-DMO) or SQL Virtual Device Interface (SQL-VDI) APIs. Additionally, you may receive the following error messages: The application has failed to start because MSVCR71.dll was not found. Reinstalling this application may fix this problem. CoCreateInstance (CLSID, IID) produced COM error 0x8007007E with Windows error 1814 "The specified module could not be found."
CAUSEThis problem occurs because the 32-bit SQL-DMO and SQL-VDI APIs have a dependency on the Msvcr71.dll file. However, the Msvcr71.dll file was not included with the 64-bit SQL Server 2000 SP4 package for Itanium-based operating systems. Therefore, after you apply SQL Server 2000 SP4, any 32-bit applications that use SQL-DMO or SQL-VDI APIs that run on the Itanium-based computer may experience this problem. RESOLUTIONThe installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:
Hotfix informationA supported hotfix is 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.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesMicrosoft SQL Server 2000 Service Pack 4 (SP4)For more information about how to obtain SQL Server 2000 Service Pack 4, 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
Restart informationYou do not have to restart the computer after you apply this hotfix. However, the SQL services are automatically restarted when you apply the hotfix.Registry informationYou do not have to modify the registry.Hotfix file informationThis hotfix contains only those files that are required to correct the issues 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 tool in Control Panel. SQL Server 2000 Itanium-based versionDate Time Version Size File name Platform --------------------------------------------------------------------- 06-Jun-2005 22:46 8.11.50523.0 758,784 Mssdi98.dll IA64 08-Jul-2005 16:22 2000.80.2148.0 1,187,840 Pfclnt80.dll IA64 16-Jun-2005 21:15 552,068 Procsyst.sql 16-Jun-2005 21:15 18,810 Sp4_serv_qfe.sql 08-Jul-2005 17:10 2000.80.2148.0 1,061,376 Sqlagent.exe IA64 08-Jul-2005 16:33 2000.80.2148.0 334,336 Sqldiag.exe IA64 08-Jul-2005 16:24 2000.80.2148.0 246,784 Sqlfth75.dll IA64 08-Jul-2005 22:14 2000.80.2148.0 24,935,424 Sqlservr.exe IA64 STATUSMicrosoft 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 Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages
For more information about the terminology that Microsoft uses when it corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
| Article Translations
|
Back to the top
