Known Issues with Party Migration Tool
The following are the known issues with Party Migration Tool.
Party Migration tool will not be able to load ‘app.exe.config’ file on Windows Server 2003
Symptom
On startup, Party Migration tool crashes and throws an exception FileNotFoundException, this exception can be seen by attaching a debugger to the tool.
Cause
Microsoft .NET framework expects to read the file <app>.config instead of <app>.exe.config.
Resolution
Rename PartyMigrationTool.exe.config to PartyMigrationTool.config, and then run the Party Migration tool.
Note |
|---|
| If the above resolution does not fix the issue, make sure you rename PartyMigrationTool.config back to PartyMigrationTool.exe.config. |
Import of older binding files with EDI Party Migration
Importing older binding files for BizTalk Server applications that include EDI party data is not blocked. We recommend that you do not import bindings to migrate EDI party data from BizTalk Server 2006 R2 or BizTalk Server 2009 to BizTalk Server 2010.
Tip |
|---|
| Use the party migration tool for all EDI party migrations. |
Microsoft Windows Server 2000 does not support Party Migration Tool
Workaround: You need to install Microsoft Windows Vista, and then install BizTalk Server Administration console to run the Party Migration Tool.
Note