FIX: You receive error 1456 when you try to add a witness to a DBM session in SQL Server 2005

Article translations Article translations
Article ID: 930284 - View products that this article applies to.
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.
Expand all | Collapse all

On This Page

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by this 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 the hotfix package contains

SYMPTOMS

When you add a witness to a database mirroring (DBM) session in Microsoft SQL Server 2005, you receive error 1456. Additionally, the witness is not added to the DBM session.

This problem occurs if the following conditions are true:
  • All endpoints in the DBM session are configured to only listen on a private network.
  • The private network does not have a DNS server.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2005. For more information, 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

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 SQL Server 2005 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Microsoft SQL Server 2005 Service Pack 1 (SP1) installed to install this hotfix.

For more information about how to obtain SQL Server 2005 Service Pack 1, 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. However, you must restart the SQL Server service after you apply this hotfix. To do this, follow these steps:
  1. Click Start, click All Programs, click Microsoft SQL Server 2005, click Configuration Tools, and then click SQL Server Configuration Manager.
  2. Click SQL Server 2005 Services, right-click SQL Server (<ServerName>), and then click Restart.

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 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 item in Control Panel.
SQL Server 20005 32-bit versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Databasemailengine.dll9.0.2211.072,48005-Jan-200705:15x86
Gac.as.adomdclient.dll9.0.2211.0543,52005-Jan-200705:16x86
Hauresourcedb.ldfNot Applicable524,28805-Jan-200702:13Not Applicable
Hauresourcedb.mdfNot Applicable40,108,03205-Jan-200702:13Not Applicable
Logread.exe2005.90.2211.0398,11205-Jan-200705:16x86
Microsoft.analysisservices9.0.2211.01,215,26405-Jan-200705:16Not Applicable
Microsoft.sqlserver.sqlenum9.0.2211.0908,06405-Jan-200705:16Not Applicable
Ms.as.adomdclient.dll9.0.2211.0543,52005-Jan-200705:16x86
Ms.as.deployengine.dll9.0.2211.0138,01605-Jan-200705:16x86
Ms.ss.mgdsqldumper.dll2005.90.2211.075,55205-Jan-200705:16x86
Msasxpress.dll9.0.2211.022,30405-Jan-200705:16x86
Msgprox.dll2005.90.2211.0197,92005-Jan-200705:16x86
Qrdrsvc.exe2005.90.2211.0366,88005-Jan-200705:16x86
Rdistcom.dll2005.90.2211.0640,80005-Jan-200705:16x86
Repldp.dll2005.90.2211.0184,60805-Jan-200705:16x86
Replmerg.exe2005.90.2211.0318,24005-Jan-200705:16x86
Replprov.dll2005.90.2211.0547,61605-Jan-200705:16x86
Replrec.dll2005.90.2211.0782,11205-Jan-200705:16x86
Replsub.dll2005.90.2211.0404,76805-Jan-200705:16x86
Sbmsmdlocal.dll9.0.2211.015,642,91205-Jan-200705:16x86
Sbmsmdredir.dll9.0.2211.03,991,32805-Jan-200705:16x86
Spresolv.dll2005.90.2211.0174,36805-Jan-200705:16x86
Sqlaccess.dll2005.90.2211.0347,93605-Jan-200705:16x86
Sqlagent90.exe2005.90.2211.0318,75205-Jan-200705:16x86
Sqlservr.exe2005.90.2211.028,970,84005-Jan-200705:16x86
Sysdbupg.sqlNot Applicable218,48629-Dec-200620:53Not Applicable
Template_hauresourcedb.ldfNot Applicable524,28805-Jan-200702:13Not Applicable
Template_hauresourcedb.mdfNot Applicable40,108,03205-Jan-200702:13Not Applicable
Xmlsub.dll2005.90.2211.0192,80005-Jan-200705:17x86
Xpstar90.dll2005.90.2211.0292,64005-Jan-200705:17x86
Xpstar90.rl2005.90.2211.0152,86405-Jan-200705:16Not Applicable
SQL Server 2005 64-bit version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Databasemailengine.dll9.0.2211.072,48006-Jan-200703:14x86
Gac.as.adomdclient.dll9.0.2211.0543,52006-Jan-200703:14x86
Hauresourcedb.ldfNot Applicable524,28805-Jan-200702:13Not Applicable
Hauresourcedb.mdfNot Applicable40,108,03205-Jan-200702:13Not Applicable
Logread.exe2005.90.2211.0522,52806-Jan-200703:14x64
Microsoft.analysisservices9.0.2211.01,215,26405-Jan-200705:16Not Applicable
Microsoft.sqlserver.sqlenum9.0.2211.0875,29606-Jan-200703:14Not Applicable
Ms.as.adomdclient.dll9.0.2211.0543,52006-Jan-200703:14x86
Ms.as.deployengine.dll9.0.2211.0138,01605-Jan-200705:16x86
Ms.ss.mgdsqldumper.dll2005.90.2211.091,42406-Jan-200703:14x64
Msasxpress.dll9.0.2211.027,42406-Jan-200703:14x64
Msgprox.dll2005.90.2211.0259,36006-Jan-200703:14x64
Qrdrsvc.exe2005.90.2211.0431,39206-Jan-200703:14x64
Rdistcom.dll2005.90.2211.0833,82406-Jan-200703:14x64
Repldp.dll2005.90.2211.0235,29606-Jan-200703:14x64
Replmerg.exe2005.90.2211.0415,00806-Jan-200703:14x64
Replprov.dll2005.90.2211.0745,24806-Jan-200703:14x64
Replrec.dll2005.90.2211.01,008,41606-Jan-200703:14x64
Replsub.dll2005.90.2211.0525,60006-Jan-200703:14x64
Sbmsmdlocal.dll9.0.2211.015,642,91205-Jan-200705:16x86
Sbmsmdredir.dll9.0.2211.03,991,32805-Jan-200705:16x86
Spresolv.dll2005.90.2211.0223,00806-Jan-200703:14x64
Sqlaccess.dll2005.90.2211.0355,10406-Jan-200703:14x86
Sqlagent90.exe2005.90.2211.0389,92006-Jan-200703:14x64
Sqlservr.exe2005.90.2211.039,353,12006-Jan-200703:14x64
Sysdbupg.sqlNot Applicable218,48629-Dec-200620:53Not Applicable
Template_hauresourcedb.ldfNot Applicable524,28805-Jan-200702:13Not Applicable
Template_hauresourcedb.mdfNot Applicable40,108,03205-Jan-200702:13Not Applicable
Xmlsub.dll2005.90.2211.0317,21606-Jan-200703:14x64
Xpstar90.dll2005.90.2211.0540,96006-Jan-200703:14x64
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

WORKAROUND

To work around this problem, make sure that you have a DNS server listening when you use a private network.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 2005 Service Pack 2.

MORE INFORMATION

In this situation, all server names that are referenced in the ALTER DATABASE commands must use IP addresses instead of the server name.

Changing the hosts file on the servers that are part of the DBM session does not resolve this problem.

This problem does not occur when you originally create the DBM session between the partners as the two ALTER DATABASE commands. One command exists on each partner server to notify the partner server of the other partner.

For more information about the terminology that Microsoft uses when correcting software after it is released, 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
For more information about database mirroring in SQL Server 2005, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/cc917680.aspx

Properties

Article ID: 930284 - Last Review: September 17, 2011 - Revision: 2.0
APPLIES TO
  • 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 Developer Edition
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
Keywords: 
kbsql2005sp2fix atdownload kbqfe kbfix kbbug KB930284

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com