Hi,
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 !!!
Jérémie - an other BizTalker 
Thanks Jeremie – I am trying to find out if it is possible to build a new 2010 environment and then simply redeploy my old 2009 apps onto it? Can you let me know if this is possible in your experience?
Many thanks
Yes, ,it is possible, you could create your package from your old 2009 Platform by export msi (without bindings) and Import on the new Platform. This works well when you don’t have any particular features in your application. I succeed theses manipulations with one of my client
Carefull, if you use EDI because the Platform has evolved on this point between 2009 and 2010.
If needed more help, don’t hesitate. we could talk on private message
Hey thanks for your response Jeremie! This is exactly the information I wanted. We are not using EDI at all, mainly WCF adapter so hopefully will not experience many problems.
I hope you don’t mind I linked to this blog from my stackoverflow question: http://stackoverflow.com/questions/13914882/biztalk-2009-to-2010-upgrade-path
thanks 😉
Jeremie,
I am migrating an application from BizTalk 2009 / .NET 3.5 to BizTalk 2010 / .NET 4.0
Once the BizTalk 2010 upgrade has complete, do I need to import my orchestrations rebuilt in .NET 40 into the admin console? Or do I simply need to run the orchestration installer?
Assumption: there is no need to import the .NET 40 orchestration MSI. All that is needed is to run the orchestration installer which will take care of installing them in the .NET 40 GAC.
Could you please confirm?
Thanks
Xavier Chorin
Hi Xavier,
I suggest you to create a backup of all your applications and your BizTalk DataBase before starting any update.
Don’t create a unique msi that export all your platform, at least, create an msi for each your BizTalk Application.
After the upgrae has complete, you should retrieve all your application, but you have to check before that your orchestration or component doesn’t use any obsolete piece of code that is not any longuer supported in BTS 2010.
If you use .Net 3.5 orchestration, your dll will be installed in the .Net 2 GAC Folder.
Maybe you must use these lines of code in your config file :
to support v3.5 orchestrations
You can check this word document for more informations : http://download.microsoft.com/download/0/F/F/0FFEF5D0-BE04-4D03-9125-75B8AD243E57/Upgrading%20to%20BizTalk%20Server%202010%20from%20BizTalk%20Server%202009%20or%202006%20R2.docx
Thanks!