Hi there,
So why am I getting this error please ?
How come there is more then one schema that matches the message type ?
Technology Tips and News
Hi there,
So why am I getting this error please ?
How come there is more then one schema that matches the message type ?
Hi,
This error is thrown because BizTalk doesn't know which XSD schema should match the incoming message.
Probably you have several schemas with the same root and namespace deployed.
You can manually specify the full qualified name of the schema you wany to use in the XML Receive pipeline DocumentSpecNames property:
R
If it is unintended that you have the same schema deployed multiple times, you could also remove the excess schemas.
Go to All Artifacts -> Schemas and locate where there are deployed.
Morten la Cour
Hi,
You get this error when you have deployed a particular schema more than once(intentionaly -under different applications or may be by mistake).
In either of the case, you will get error. In case you need schema to be used in more than one application, then I would recommend going for a Shared Application wherein all shared application can be deployed and can be referenced from the other application which need them.
You should refer following post for more insights:https://msdn.microsoft.com/en-us/library/aa577468(BTS.10).aspx
In case you don't need it in multiple application, then you can go ahead and delete the unwanted one. Go to All Artifacts in Biztalk Admin console and you would see multiple entries for that particular schema, delete which you are not going to use.
______________________
Maheshkumar S Tiwari|User Page|Blog|Primary location cannot be deleted
So there are three schemas generated.
I remember using the TypedPolling one in VS, why then all the others are still present and why is it that I cannot remove them ???
No. These are not three different schemas, these are three different type inside your schema.
In BizTalk all the messages are processed or identified on the unique combination of
TargetNamespace#RootName
So you have to make sure every schema which you are using or deploying has this combination unique.
Check this article The BizTalk Server Message for more details on this. Also you can use this blog post to verify your schema after deployment Verifying Schemas after deployment
Hi,
There may be duplicate schema deployed with your application with same message type. You can just query the Management Db to verify the same.
Select msgtype, assemblyid, clr_namespace, clr_assemblyname from bt_documentspec where msgtype like % http://schemas.microsoft.com/Sql/2008/05/TypedPolling/GetAssessments#TypedPolling%
Once you find schema's having same rootnode and namespace(same messagetype) then you need to update the those schemas so that message type does not remain same . when you will be done with above process of changing the messagetype then you need to delete the deployed Application and to have a fresh deployment before testing it again.
Thanks
Abhishek
Hi,
There may be duplicate schema deployed with your application with same message type. You can just query the Management Db to verify the same.
Select msgtype, assemblyid, clr_namespace, clr_assemblyname from bt_documentspec where msgtype like % http://schemas.microsoft.com/Sql/2008/05/TypedPolling/GetAssessments#TypedPolling%
Once you find schema's having same rootnode and namespace(same messagetype) then you need to update the those schemas so that message type does not remain same . when you will be done with above process of changing the messagetype then you need to delete the deployed Application and to have a fresh deployment before testing it again.
Thanks
Abhishek
Hi,
There may be duplicate schema deployed with your application with same message type. You can just query the Management Db to verify the same.
Select msgtype, assemblyid, clr_namespace, clr_assemblyname from bt_documentspec where msgtype like % http://schemas.microsoft.com/Sql/2008/05/TypedPolling/GetAssessments#TypedPolling%
Once you find schema's having same rootnode and namespace(same messagetype) then you need to update the those schemas so that message type does not remain same . when you will be done with above process of changing the messagetype then you need to delete the deployed Application and to have a fresh deployment before testing it again.
Thanks
Abhishek