Microsoft KB Archive/895955

From BetaArchive Wiki

Article ID: 895955

Article Last Modified on 11/15/2007



APPLIES TO

  • Microsoft BizTalk Server 2004 Service Pack 1




SYMPTOMS

When you run the sp_GetRemoteServerName stored procedure in Microsoft BizTalk Server 2004 Service Pack 1 (SP1), you may receive an error message that is similar to the following:

Msg 7403, Level 16, State 1, Server servername, Line 2 Could not locate registry entry for OLE DB provider 'MSDASQL'. OLE DB error trace [Non-interface error: Provider not registered.].

Note In this error message, servername is a placeholder for the name of the instance of Microsoft SQL Server.

For example, you may receive this error message when you run the sp_BackupAllFullSchedule stored procedure. The sp_BackupAllFullSchedule stored procedure calls the sp_GetRemoteServerName stored procedure.

This problem occurs when SQL Server is installed on a 64-bit version of Microsoft Windows Server 2003.

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:


Warning You cannot roll back this hotfix from the BizTalk Server environment. Therefore, make sure that you fully test this hotfix in a test environment before you apply this hotfix to a production environment. Do not try to use Add or Remove Programs to remove this hotfix because this does not roll back the database changes, and leaves the BizTalk Server environment in an inconsistent state.

Prerequisites

You must have BizTalk Server 2004 SP1 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

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.

File name File size Date Time
Backup_setup_all_procs.sql 14,756 30-Mar-2005 21:07
Bts_administration_logic.sql 511,694 30-Mar-2005 21:07

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

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, 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: kbbiztalk2004-2006swept kbbug kbfix kbpubtypekc kbhotfixserver kbqfe KB895955