Microsoft KB Archive/883548

= You may receive a &quot;Could not connect to database&quot; error message when you start the BizTalk Server Base EDI service =

Article ID: 883548

Article Last Modified on 8/11/2006

-

APPLIES TO


 * Microsoft BizTalk Server 2004 Enterprise Edition
 * Microsoft BizTalk Server 2004 Developer Edition
 * Microsoft BizTalk Server 2004 Standard Edition
 * Microsoft BizTalk Server 2004 Partner Edition

-





SYMPTOMS
When you start the BizTalk Server Base EDI service in Microsoft BizTalk Server 2004, you may receive an error message that is similar to the following:

  Application Event Error: “Could not connect to database” The DB server name instance did not match the real SQL instance name



CAUSE
This issue may occur if the database instance name is not specified during installation or if the database instance name has been modified or changed manually after installation. To determine whether you are experiencing this problem, start SQL Server Enterprise Manager, and then verify the database instance name.



RESOLUTION
If the database instance name is set to local, you either can register the instance of Microsoft SQL Server again, or you can manually change the value of the ServerName entry to localhost in the Esp.ini file. By default, the Esp.ini file is located in the following folder:

C:\Program Files\Microsoft BizTalk Server 2004\EDI\Subsystem

The following sample shows the ServerName entry set to SERVER_01\RAN in the Database section of the Esp.ini file. [Database] DBMS=MSS (Msoft) SQL Server 2000 Database=BizTalkEDIDb AutoCommit=FALSE ServerName=MYSERVER_01\RAN

Keywords: kbbiztalk2004-2006swept kbtshoot kbprb KB883548

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.