Installing BizTalk ESB Toolkit 2.0

Microsoft BizTalk ESB Toolkit 2.0 (formerly known as ESB Guidance 2.0) is out. I installed it, together with the ESB Management Portal, today on a Windows Server 2008 32-bit virtual machine using the following procedure:

  1. Install BizTalk ESB Toolkit 2.0-<CPU>.msi.
  2. Import C:Program FilesMicrosoft BizTalk ESB Toolkit 2.0/Microsoft.Practices.ESB.CORE.msi into BizTalk Server using the BizTalk Server 2009 Administration Console and install the .msi file.
  3. Now, before you install the ESB Management Portal, you should follow the steps in Installing the BizTalk ESB Toolkit –> Configuring Services and Components in the help.
  4. Extract C:Program FilesMicrosoft BizTalk ESB Toolkit 2.0/ to C:ProjectsMicrosoft.Practices.ESB.
  5. Navigate to C:ProjectsMicrosoft.Practices.ESBSamplesManagement PortalInstallScripts, and then start ManagementInstall.cmd.

When browsing the portal (http://localhost/ESB.Portal/Home/HomePage.aspx), I first got an exception. From the event log:

Event Type:    Warning
Event Source:    ASP.NET 2.0.50727.0
Event Category:    (3)
Event ID:    1309
Date:        2009-06-22
Time:        09:04:23
User:        N/A
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 2009-06-22 09:04:23
Event time (UTC): 2009-06-22 07:04:23
Event ID: 6a2cd3b312364acf8bda81406418cb91
Event sequence: 211
Event occurrence: 8
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/1/ROOT/ESB.Portal-1-128901266654457632
    Trust level: Full
    Application Virtual Path: /ESB.Portal
    Application Path: C:ProjectsMicrosoft.Practices.ESBSourceSamplesManagement PortalESB.Portal
    Machine name: BTS2009
Process information:
    Process ID: 4816
    Process name: w3wp.exe
Exception information:
    Exception type: SqlException
    Exception message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 – No connection could be made because the target machine actively refused it.)
Request information:
    Request URL: http://localhost/ESB.Portal/Lists/RegistrySummaryContainer.aspx
    Request path: /ESB.Portal/Lists/RegistrySummaryContainer.aspx
    User host address: ::1
    User: BTS2009Administrator
    Is authenticated: True
    Authentication Type: Negotiate
    Thread account name: NT AUTHORITYNETWORK SERVICE
Thread information:
    Thread ID: 5
    Thread account name: NT AUTHORITYNETWORK SERVICE
    Is impersonating: False

I searched the web and found this blog post that provided the solution:

  1. Use SQL Server Configuration Manager to enable TCP/IP.
  2. Restart SQL Server.
  3. Restart IIS (by typing IISReset at a command prompt).

One thought on “Installing BizTalk ESB Toolkit 2.0”

  1. Henrik,I solved the problem the opposite way: I altered the connection string to remove "Network Library=dbmssocn", thus eliminating the requirement to use TCP/IP.Richard

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.