Microsoft Knowledge Base Email Alertz

(883548) - Explains how to resolve an issue that 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.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 883548 - Last Review: August 11, 2006 - Revision: 1.2

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

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

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
Keywords: 
kbbiztalk2004-2006swept kbtshoot kbprb KB883548
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate