|
Home > Archive > BizTalk Server General > April 2005 > schema not dployed properly??
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 not dployed properly??
|
|
| nalaka 2005-04-26, 8:47 pm |
| Hi......
I have a test project (all components are in this project)....
After the project was working... I added a new schema to it... and then a
"send" shape. (uses default xml.assembler)...
I can build and then deploy properly....
but the following error pops up saying that the schema, I added last cannot
be found.
Are the any special steps that, I should take, if I added a schema to a
project later??
Error
------------------------------------
There was a failure executing the send pipeline:
"Microsoft.BizTalk.DefaultPipelines.XMLTransmit" Source: "XML assembler"
Send Port:
" C:\BizTalkSolutions\Invoice\PetroCanada\
InvoiceFromPetroCanada\out\yy%Messa
geID%.xml" Reason: This Assembler cannot retrieve document specification by
using this type: "InvoiceLine".
C0C01300: Finding document specification by message type "InvoiceLine"
failed. Verify that the schema is deployed properly.
Thanks
Nalaka
| |
| nalaka 2005-04-26, 8:47 pm |
| Hi...
I also had "expressions" (and loop etc.) that I deployed.
but the runTime engine did not run them...
I could see the shape in the "HAT Orchestration debugger"... but the events
showed that it diod not run.
any idas, on how I can, get the latest deployment to work?
Thanks
Nalaka
"nalaka" <nalaka@nospam.nospam> wrote in message
news:uVt2ForSFHA.3184@TK2MSFTNGP15.phx.gbl...
> Hi......
> I have a test project (all components are in this project)....
> After the project was working... I added a new schema to it... and then a
> "send" shape. (uses default xml.assembler)...
> I can build and then deploy properly....
> but the following error pops up saying that the schema, I added last
cannot
> be found.
> Are the any special steps that, I should take, if I added a schema to a
> project later??
>
> Error
> ------------------------------------
> There was a failure executing the send pipeline:
> "Microsoft.BizTalk.DefaultPipelines.XMLTransmit" Source: "XML assembler"
> Send Port:
>
" C:\BizTalkSolutions\Invoice\PetroCanada\
InvoiceFromPetroCanada\out\yy%Messa[vbco
l=seagreen]
> geID%.xml" Reason: This Assembler cannot retrieve document specification[/vbcol]
by
> using this type: "InvoiceLine".
> C0C01300: Finding document specification by message type "InvoiceLine"
> failed. Verify that the schema is deployed properly.
>
>
> Thanks
> Nalaka
>
>
>
>
| |
|
|
Make sure you are not auto versioning your projects, that has gotten me
before with the same error.
(look in the gac and see if more than one DLL exists for your schemas)
"nalaka" <nalaka@nospam.nospam> wrote in message
news:uVt2ForSFHA.3184@TK2MSFTNGP15.phx.gbl...
> Hi......
> I have a test project (all components are in this project)....
> After the project was working... I added a new schema to it... and then a
> "send" shape. (uses default xml.assembler)...
> I can build and then deploy properly....
> but the following error pops up saying that the schema, I added last
cannot
> be found.
> Are the any special steps that, I should take, if I added a schema to a
> project later??
>
> Error
> ------------------------------------
> There was a failure executing the send pipeline:
> "Microsoft.BizTalk.DefaultPipelines.XMLTransmit" Source: "XML assembler"
> Send Port:
>
" C:\BizTalkSolutions\Invoice\PetroCanada\
InvoiceFromPetroCanada\out\yy%Messa[vbco
l=seagreen]
> geID%.xml" Reason: This Assembler cannot retrieve document specification[/vbcol]
by
> using this type: "InvoiceLine".
> C0C01300: Finding document specification by message type "InvoiceLine"
> failed. Verify that the schema is deployed properly.
>
>
> Thanks
> Nalaka
>
>
>
>
| |
| WenJun Zhang[msft] 2005-04-27, 7:55 am |
| Hi Nalaka,
Schemas are identified by name spaces. Please check if the schema's
target namespace is specified properly and not duplicate. From the
error info, looks like it's not set: "InvoiceLine". Generally to make
namespace be unique, we can use something like:
http://projectname.schemaname .
Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
| |
| nalaka 2005-04-27, 8:50 pm |
| ok.... here is the problem.. error says.....
Reason: This Assembler cannot retrieve document specification by using this
type: "myRootName".
This is because I constructed a message using xPath....
This message does not have a nameSpace... and the biztalk cannot send
this....
after looking around in the messageboards... came across following 3
solutions.
1. in the send port .. for pipe line option.... use "passthrough" insted of
the default "xml something".
2. actually use a pipe line and, set the document to the correct schema...
so biztalk does not have to search.
3. Map the message using a map to another... so that the resulying one will
have the namespace.
Following link kinda explains.....
(search for....... biztalk Reason: This Assembler cannot retrieve)
http://dallas.sark.com/SarkBlog/mho...2005/04/08.aspx
""WenJun Zhang[msft]"" <v-wzhang@online.microsoft.com> wrote in message
news:9YXBGAxSFHA.3864@TK2MSFTNGXA02.phx.gbl...
> Hi Nalaka,
>
> Schemas are identified by name spaces. Please check if the schema's
> target namespace is specified properly and not duplicate. From the
> error info, looks like it's not set: "InvoiceLine". Generally to make
> namespace be unique, we can use something like:
> http://projectname.schemaname .
>
> Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
| |
| WenJun Zhang[msft] 2005-04-28, 7:54 am |
| Glad to hear you've figured out the root cause. :-)
Best regards,
WenJun Zhang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
|
|
|