|
Home > Archive > BizTalk Server Orchestration > May 2004 > Biztalk 2004 Error
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Biztalk 2004 Error
|
|
| Amitesh Mishra 2004-05-19, 2:40 am |
| Hi Everyone,
I have configured a Receive Location in Biztalk server which is referring to an SQL Server database for obtaining the events to be passed to a Workflow. This SQL Receive location checks the event table with the help of a stored procedure.
Now when I have bound the ports and started the orchestration, I am getting the following error as shown in the Health & Activity Monitor.
"This service instance exists to help debug routing failures.
The context of the message associated with this instance contains all the
promoted properties at the time of the routing failure."
Can Anyone suggest as to when such an error is encountered and what is the solution.
| |
| Matt Milner 2004-05-19, 8:40 pm |
| most likely scenario is that the xml coming from SQL server does not map
correctly to a published schema.
make sure you have published the schema to biztalk that you setup for your
receive, and make sure that the xml coming back from sql has a proper root
node and namespace declaration.
matt
"Amitesh Mishra" <amitesh_m@hotmail.com> wrote in message
news:9AAA62F5-1E48-41C2-92D7-531BB1278DBB@microsoft.com...
> Hi Everyone,
>
> I have configured a Receive Location in Biztalk server which is
referring to an SQL Server database for obtaining the events to be passed to
a Workflow. This SQL Receive location checks the event table with the help
of a stored procedure.
>
> Now when I have bound the ports and started the orchestration, I am
getting the following error as shown in the Health & Activity Monitor.
>
> "This service instance exists to help debug routing failures.
> The context of the message associated with this instance contains all the
> promoted properties at the time of the routing failure."
>
> Can Anyone suggest as to when such an error is encountered and what is the
solution.
>
|
|
|
|
|