If you compile a flat file disassemble pipeline with a schema as is required in the note and then remove the schema in the management console as shown here:
and changed it to
You will get the following error (Value does fall within the expected range) in the event log when trying to process a file:
Information: The receiving server is not responding.
Troubleshooting:
1. Check the details of the error and ensure the receiving server is available. Example: Send Port destination path to a server that is down.
Information: There are no subscribing orchestration or send ports to the message being dropped off to the message box.
Troubleshooting:
1. Ensure there is a started orchestration that is watching for the message being dropped off.
2. If you are not using an orchestration, make sure there is a send port that is filtered by the receive port.
Information: Biztalk Orchestration language XLANG threw an exception. There is most likely a coding error in your orchestration.
Troubleshooting:
1. Look for the Shape name specified in the error.
2. Look for the Error thrown by that shape.
3. Run the Orchestration debugger and put a break point before that shape (F9). Run a new message through the same orchestration and interrogate the values being passed into the shape (Debug -> Attach).
4. Look for errors in coding
Information: If the EDI Subsystem receives a message that is not loaded in the BiztalkEDIDb/dom1 table.
Troubleshooting:
1. Check the Send Port Properties to ensure a map is in place translating Your Source Document Schema to an EDI X12 Schema is in place.
2. You can check which X12 EDI Schemas are loaded into the BiztalkEDIDb by running the following SQL Query.
SELECT block
FROM dom1
WHERE mcvr LIKE ‘X12EDISchema%’ AND block LIKE ‘%targetnamespace%
X12EDISchema Examples – 850, 812, 867, etc.
Information: When you restart the Biztalk Host the EDI Subsystem which is controlled by the Biztalk Host also restarts. All new EDI receive location properties are loaded into the Biztalk Host instance. These Event Logs are showing the restart status of the EDI Subsystem.
Information: Event Log entry showing the status of the Biztalk Host. The Biztalk Host status can be found in the Biztalk Admininstration Console.
Information: This error occurs when a document is picked up by a receive location and the pipeline specified in that receive location does not recognize the data.
Troubleshooting:
1. Check that the correct pipeline is selected in your Receive Location Properties
2. Open Visual Studio and ensure the correct schema is used in the pipeline
3. Right click on your schema and manually validate the file that threw the error by selecting properties -> Input Instance Filename – > Select Original File. Then right click again on schema and select Validate Instance. You will be manually doing what the pipeline did to throw the original error. You should see detailed error information in the Visual Studio Output Window.
Information: This error occurs when a document is picked up by a receive location and the pipeline specified in that receive location does not recognize the data.
Troubleshooting:
1. Check that the correct pipeline is selected in your Receive Location Properties
2. Open Visual Studio and ensure the correct schema is used in the pipeline
3. Right click on your schema and manually validate the file that threw the error by selecting properties -> Input Instance Filename – > Select Original File. Then right click again on schema and select Validate Instance. You will be manually doing what the pipeline did to throw the original error. You should see detailed error information in the Visual Studio Output Window.
