COVAST BBOT – Using BizTalk and SQL

COVAST BBOT – Using BizTalk and SQL

by | Aug 2, 2007 | BizTalk Community Blogs via Syndication

Got this from Katya at COVAST.

 

Chris Vidotto
As a professional in the Integration space, you know that many large organizations have already invested in a great B2B gateway!

HOWEVER, many small and medium sized Suppliers or Customers do not have the IT skills to connect to these large organizations.

BBot is THE solution:

BBotProductPhoto small

Built on Microsoft technology:

Microsoft Windows Server 2003
Microsoft SQL Server 2005
Microsoft BizTalk Server 2006 R2
Microsoft SharePoint Services V3

WE MAKE IT SIMPLE!

1)   Covast publish a profile containing information about the supply chain processes and the types of documents  exchanged by trading partners like EDI, XML or any other
2)   The smaller trading partner installs a plug-and-play BBot that will automatically download the profile at first startup and instantly configure itself to exchange the published   documents
A fully supported BBot is leased for a low monthly fee.

Do you want to know more about how BBot works and what it can do for you? 
CLICK HERE

Covast looks forward to helping you in your projects to streamline the supply chain processes!

Event 5778 – The Messaging engine failed to process a message submitted by adapter:EDI Source. Details:The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not bee

by | Aug 2, 2007 | BizTalk Community Blogs via Syndication

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.

Event 10034 – Uncaught exception (see the ‘inner exception’ below) has suspended an instance of service.

by | Aug 2, 2007 | BizTalk Community Blogs via Syndication

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 thesame orchestration andinterrogate the values being passed into the shape (Debug -> Attach).

4. Look for errors in coding

Event 24 – Error encountered: ERROR (39) : The document type is not recognized. Contact the sender.

by | Aug 2, 2007 | BizTalk Community Blogs via Syndication

Information: If the EDI Subsystem receives a message thatis not loaded in the BiztalkEDIDb/dom1 table.

Troubleshooting:

1. Check the Send Port Properties to ensurea map is in place translatingYour Source Document Schema to an EDI X12Schema 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.

Event 5753 – A message received by adapter is suspended. Reason: No Disassemble stage components can recognize the data.

by | Aug 2, 2007 | BizTalk Community Blogs via Syndication

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.