Sep 072007
 

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:

originallyConfiguredPipeline

and changed it to

newlyConfiguredPipeline

You will get the following error (Value does fall within the expected range) in the event log when trying to process a file:

valuenotinrange

May 152007
 

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, cure make sure there is a send port that is filtered by the receive port.

image

May 102007
 

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).

image

4.  Look for errors in coding

May 072007
 

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.

image

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.

Apr 232007
 

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

image

2.  Open Visual Studio and ensure the correct schema is used in the pipeline

image

image

image

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.

Apr 192007
 

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

image

2.  Open Visual Studio and ensure the correct schema is used in the pipeline

image

image

image

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.