We had a lot of problems with BizTalk and the development environment, and I
discovered laity that some of these problems were because of the fact that
the development environment is based on a cleaned Windows 2003 VPC image.
Here are some tips that may help you.
Never clone the same Windows 2003 Image, always install a new one for each
client or server !!!! This will fix you most of the problems, but if you don
't want to, here are some tips.
1- Make sure that each image has a unique SID, to change the SID search
google for the NewSID utility.
2- But even when you change the SID, there are some services that remember
the old SID, like the DTC service, if that service remembers the old SID,
you will not be able to deploy a BizTalk orchestration from the development
machine (from VS.NET), to the BizTalk server (if they originated from the
same image) even if you changed the SID.
To fix that, you need to stop the DTC service, to run the dtc -uninstall, to
delete the service from the registry, to delete the dtc files from the
machine, to reinstall the dtc again with the dtc -install command, and then
the deployment will work.
My advice is: Install Windows separately for each image and BizTalk will
work fine :-)
Here is what I did when I cloned an image:
- Install image with Windows 2003, VS.Net 2003 (c# at least), MSDN help
files, SQL Server 2000 + sp3a + Q831950, other utils you want to use and
then all WindowsUpdates.
- Clone the image (copy + paste)
- Start up the copy
- Get New SID
- Rename the computer, re-join to domain if running on a domain
- Run sp_deleteserver 'OldServerName'
- Run sp_addserver 'NewServerName'
"G. Tarazi" <Tar...@LiveTechnologies.ca> wrote in message