Chewy Chong works in Southeast Asia and lives in Singapore. He does something technology related.
Renaming BizTalk Development Machine Causes Problems
As if we did not expect this to begin with. Anything that involve renaming a machine never goes well.
We use VPC images as our standard operating environment (SOE) for the development project I’m on. The majority of my work involves BizTalk. I created a SOE W2K machine with Visual Studio 2003 and BizTalk 2004. When a developer grabs the image, renames the machine and joins the domain… BizTalk breaks.
Why? BizTalk store configuration information in a series of databases. The database server which holds these configuration databases are stored in the registry. If you rename the machine, be sure to update the name of the server. The keys to look at is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\3.0\Administration (‘MgmtDBServer’ value)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BusinessRules\3.0 (‘Database Server’ value)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ENTSSO\SQL (‘Server’ value)
You should unconfigure and reconfigure the BizTalk framework.
Unconfigure = configframework /u
Configure = configframework
[NEW] Additional Items Affected
- BizTalk Security Groups Added to SQL reflect the old server’s name. Need to delete before reconfiguring the framework.
- Potential “Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server” error. To fix, run the following tsql command on the ‘msdb’ database:
DECLARE @srv sysname
SET @srv = CAST(SERVERPROPERTY(‘ServerName’) AS sysname)
UPDATE sysjobs SET originating_server = @srv
