Thursday, July 26, 2007 4:15 PM
Thsi problem has plagued me repeatedly over the past year. Twice I have had to reinstall VS.Net 2005 and BizTalk 2006 on my dev machine to solve the problem. When I attempt to open an orchestration in an existing project or add a new orchestration to a newly created project, the Orchestration Designer crashes VS.Net.
I have come across very few posts related to this issue. It would appear to be a VS.Net issue as opposed to a corrupted .odx file since even a brand new empty .odx file causes the same problem.
Can anyone help? Thanks.
Thursday, July 26, 2007 9:49 PM
Have you uninstalled any BizTalk prerequisties??? Have you uninstalled MSXML 4??? Please make sure that all the prerequisties are present...
Friday, July 27, 2007 6:16 AM
I'd agree with Kumar.
I've seen this in BT2004 when you create a MSI using the BTSInstaller package, and not remove the BTS core libraries before compiling the package and distributing the MSI. If you do this and then do an uninstall... say ERRRRR.... Kaboom!!!
I haven't seen this on 2k6 except if you're using an old 2k4 msi built unsing the old 2k4 btsinstaller packages on 2k6 that is not created correctly, and then do an uninstall, and it removes the core BizTalk libraries.