Today I try to migrate a BizTalk Server 2009 dev platform to a BizTalk Server 2010.
My platform was design with :
- Visual Studio 2008
- SQL Server 2008
- BizTalk Server 2009
And I want to migrate to
- Visual Studio 2010
- SQL Server 2008 R2
- BizTalk Server 2010
So first of all, I need to install Visual Studio 2010 and .Net Framework 4.0 which are prerequesites to install BizTalk Server 2010. Then I have the choice to upgrade (yes, I try to upgrade and not really just install new version by uninstall/desinstall :p) SQL Server 2008 R2 or BizTalk 2010.
Due to the fact that BizTalk 2009 not support SQL Server 2008 R2, the choice is simple, I have to upgrade BizTalk 2010 first.
before do anything, please keep this in mind :
Setup will upgrade BizTalk Server 2009 to BizTalk Server 2010 when you click Upgrade. Please make sure you have backed up all BizTalk databases before you continue with the upgrade.
During the installation, the setup detect the previous installation of BizTalk 2009 and purpose a upgrade keeping the configuration.
You have to stop W3SVC and Rule Engine Update Services to launch the setup (if it’s not, a message will appear to ask you some start/stop services)
Ok, it seems to be good :
Let’s get started the BizTalk Administration Console. Ok, I can see my BizTalk 2009 Application. Now I have to test this one to verify that my upgrade is good, then I will try to upgrade SQL Server 2008 to R2.
My host instance started correctly. Good thing to know, the BTSNTSvc(64).exe.config have kept the configuration.
Arg, finally I discover that my 64 bits refuse to start…
After trying a lot of thing, I don’t understand why only my 32 bits Instance succeed to work. So because of that, I decided to unconfigure BizTalk (keeping SSO configuration) and I deleted the database.
I reapply configuration manually (not with the export). And Voila!!! It worked!
Now I’m reading the Setup log of the upgrade to understand what change could be responsible of this problem…
I think I’m on the right track supposing that something happened in the ManagementDb…
So Stay tuned !!!