|
Home > Archive > BizTalk Server General > June 2004 > Schema deployed & assembly implements the correct document spec er
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 |
Schema deployed & assembly implements the correct document spec er
|
|
|
| I am trying to get a simple Flat File Disassembler to work and them output the content as XML messages. I believe this should be simple.
When deployed on my local workstation I get a message in the event log: "There was a failure executing the receive pipeline...Reason Loading the document specification from the assembly failed. Verify that the schema is deployed properly and the assembly
implements the correct document spec".
To attempt to diagnose the problem I have used Validate Instance by setting the appropriate properties for the schema (right click ones). This does produce one single XML document that contains the data of the first row of the CSV file. It looks as thou
gh the diassembler is working from this perspective. I also have used FFDASM from the Utilities and this does in fact generate 6 XML messages one for each row in the CSV.
I use the deploy method from VS and it places the built assembly in the GAC. When I look at the assembly it references my built file andon inspecting this with ILDASM it shows a class with the name of the schema that is used to disassemble the file. Som
eone suggested it was better to place schema in a sperate assembly and register this. However this route was explored and there does not seem to be same options avaiable in the properties for specifying the type name and namespace.
When I undeploy I see the assembly being removed from the GAC and when I deploy I see it being inserted and referecing the file I have just compiled. What else could be wrong and how can I correct it?
| |
|
| A solution to the problem has been found. However I would suspect there si a problem here with BizTalk not removing the bindings port binding correctly, when they are deleted. This does not appear to be a memory problem as the problem persists between r
eboots.
Although the BizTalk assembly was uninstalled correctly and the Receive & Send ports deleted through BizTalk Explorer when the project was deplolyed again on the workstation an added schema was not being recognised. The problem was solved by undeplyoying
& deleteing the ports as before however the version number of the assembly was incremented. This suggests there is something in the registry that is remaining after undeploying and deleting.
Microsoft perhaps there should be a closer look at what is incorrectly going on here.
For everyone else don't assume everything has been removed when undelopying and deleting ports.
BenW
"BenW" wrote:
> I am trying to get a simple Flat File Disassembler to work and them output the content as XML messages. I believe this should be simple.
>
> When deployed on my local workstation I get a message in the event log: "There was a failure executing the receive pipeline...Reason Loading the document specification from the assembly failed. Verify that the schema is deployed properly and the assemb
ly implements the correct document spec".
>
> To attempt to diagnose the problem I have used Validate Instance by setting the appropriate properties for the schema (right click ones). This does produce one single XML document that contains the data of the first row of the CSV file. It looks as th
ough the diassembler is working from this perspective. I also have used FFDASM from the Utilities and this does in fact generate 6 XML messages one for each row in the CSV.
>
> I use the deploy method from VS and it places the built assembly in the GAC. When I look at the assembly it references my built file andon inspecting this with ILDASM it shows a class with the name of the schema that is used to disassemble the file. S
omeone suggested it was better to place schema in a sperate assembly and register this. However this route was explored and there does not seem to be same options avaiable in the properties for specifying the type name and namespace.
>
> When I undeploy I see the assembly being removed from the GAC and when I deploy I see it being inserted and referecing the file I have just compiled. What else could be wrong and how can I correct it?
>
>
|
|
|
|
|