Share via

BizTalk Error: If the BizTalk Server Computer Is Renamed After BizTalk Server Configuration, the Configuration Wizard Will Fail

  • Article

This problem may manifest itself in several ways:

  • The configuration manager will load the Overview page correctly, but when attempting to configure a feature the feature options do not display on the screen.
  • The configuration wizard cannot connect to the SQL Server.
  • Attempting to Unconfigure All unconfigures some features, but not all.
Cause

The BizTalk Server configuration stores the computer network name. When the computer is renamed the configuration manager and configuration wizard cannot locate the BizTalk Server. A similar problem will occur if the SQL Server computer is renamed after BizTalk Server is configured.

Resolution

Do not rename the BizTalk Server computer or the SQL Server computer. If a server must be renamed, unconfigure all BizTalk Features before renaming the computer. After renaming the computer, reconfigure BizTalk Server features.

If you rename a SQL server you have to do this as well:

select @@servername

go

--If name is not correct to what you connect to, change it:

sp_dropserver OLDServerName

go

sp_addserver NewServerName, local

go

-- Restart SQL Service and verify with select @@servername again

Comments

  • Anonymous
    July 18, 2008
    This was causing an error: Server has already joined a group.