Skip to content
LambogeniusDocs

BizTalk Orchestration Viewer

Troubleshooting

Common problems and how to fix them.

VS Code extensionlambogenius.biztalk-orchestration-viewerFree · MIT license

Common problems

An .odx file opens as text
Use Open With… and choose BizTalk Orchestration Viewer. Check workbench.editorAssociations for a "*.odx": "default" entry and remove it or set it to biztalkOrchestrationViewer.odxEditor.
The file could not be parsed as XML
The designer XML is not well-formed. Check that the .odx comes from source control, not a compiled artifact. The error appears in the sidebar; the diagram keeps showing what was loaded before (the sample, the first time).
No orchestration shapes were detected
The file has no elements the viewer recognises, for example a schema-only file. See Shape types and migration notes.
Large artifact detected
The file has more than 160 shapes. Everything is drawn; use the type filter or search to make the diagram easier to read.
A shape has the wrong type
Types come from keywords, so a shape's name can change its type. Check the source tag and attributes in the inspector.
Nothing happens when I drop a file
Hold Shift while you drop: without it VS Code opens the file itself instead of passing it to the viewer. Version 0.1.0 also ignored files dragged from the Explorer; update to 0.2.0, or use Open Artifact.
Export parsed model does nothing
Update to version 0.2.0, which saves the JSON through a Save dialog.
The extension does not install
It needs VS Code 1.85 or later. Check Help › About.

Found a bug? Open an issue on GitHub with a small file that shows it (no customer data).