Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Opening Biztalk Orchestration files (.odx) on VS 2005 IDE closes the IDE
- This topic has 4 replies, 1 voice, and was last updated 9 years, 3 months ago by
community-content.
-
AuthorPosts
-
-
August 20, 2008 at 10:27 AM #20453
Hello ALL,
I am experiencing a strange issue with Biztalk orchestration files. I’m a new bee and I was trying to create a sample orchestartion. After creating the orchestration I was able to see the result. But recently I have issues in opening any .ODX file on my machine. When ever I tried to open the Biztalk orchestration files the Visual Studio IDE closes. This has been the scenario for all the sample applications and the one I have created. Even i tried opening the orchestration file independent of the application still the same issue… the Visual Studio IDE closes as soon as I tried to open the ODX files. One more strange issue is adding a new orchestration also causes the same problem. My current configuration is – VS 2005 IDE, Biztalk 2006 R2 & SQL Expresss edition. I am using Windows XP. I tried reinstalling both Biztalk and VS 2005 but still the issue persists.
Has anyone experienced the similar issue.?
I appreciate your help.
-Krish
-
August 21, 2008 at 4:21 PM #20470
Did you check the event viewer for any error messages before it crashes.
Does the editor open a dialog (error encountered) before this happens?
-
August 22, 2008 at 2:52 AM #20473
A repair of the BizTalk installation and/or Visual Studio may be necessary.
Nick.
-
August 22, 2008 at 12:29 PM #20481
There are no error/log messages in event viewer. Everything looks perfect. Even I tried reinstalling both biztalk and VS 2005 still i am encountering the problem.
The only change I did was installing ILOG rules engine after creating my first biztalk orchestration project. But after removing ILOG, still not able to open the .ODX files.
Thanks,
Krish
-
August 23, 2008 at 6:42 AM #20485
I know this is probably not what you want to hear, but this is about the time I would look at re-imaging the machine. Better yet: set up a virtual machine for development and enable differencing disks. That way, when this kind of thing happens, you can spin up a new differencing disk and have everything back to normal in minutes. Here is an excellent post on using Virtual PC and differencing disks: http://www.andrewconnell.com/blog/articles/UseVirtualPCsDifferencingDisksToYourAdvantage.aspx.
-
-
-
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.