Hi,

I created a schema by using the "Create Schema" option on an instance of my
XML purchase order.

I use this schema for the Message Type defined in my ports and messages.

I'm able to build and deploy my solution without problem. I'm even able to
enlist the orchestration in Biztalk.

I created a receive location for an xml file using the File transport type.
When I drop a file in the folder specified in the receive location, Biztalk
picks up the file (it disappears from the folder). So far, no problem.

Then, nothing happens. When I look in the event log, I find the following
message:

There was a failure executing the receive pipeline:
"Microsoft.BizTalk.DefaultPipelines.XMLReceive" Source: "XML disassembler"
Receive Location: "e:\ReceivePO\*.xml" Reason: The disassembler cannot
retrieve the document specification by using this type: "PO". Either the
schema is not deployed correctly, or more than one schema is deployed for th
e
same message type.

Followed by:

The Messaging Engine encountered an error publishing a batch of "1" messages
to the Message Box database for the transport adapter "FILE". Please refer t
o
Health and Activity Tracking tool for more detailed information on this
failure and check the endpoint bindings are correctly configured.

The "FILE" adapter is suspending a message coming from Source
URL:"e:\ReceivePO\*.xml". Details:"Error in accessing the part data or one o
f
its fragments. The part or fragment may not exist in the database




Where do I look to see if my schema was deployed properly?

My development PC runs on Windows XP Professional. The Biztalk Server 2004
and SQL Server share the same machine running on Windows 2003.

If anybody has an idea, let me know.

Thanks for your help.


--
Marc-Andre Laurin, MCSD
20-20 Technologies

[ Post a follow-up to this message ]

The type "PO" suggests that you are not using target namespace for your
schema?
Verify that you have not deployed the same schema under a different
assembly.
If this doesn't work then create a custom pipeline, Put an XML Disassembler
and point the disassembler to your schema, so that BizTalk knows which
schema the message is talking about when its message type is "PO".
HTH
Regards
Dev
"Laurinma" <Laurinma@discussions.microsoft.com> wrote in message
news:D4A3CCFE-3465-42F4-AB56-64822B151401@microsoft.com...
> Hi,
>
> I created a schema by using the "Create Schema" option on an instance of
my
> XML purchase order.
>
> I use this schema for the Message Type defined in my ports and messages.
>
> I'm able to build and deploy my solution without problem. I'm even able to
> enlist the orchestration in Biztalk.
>
> I created a receive location for an xml file using the File transport
type.
> When I drop a file in the folder specified in the receive location,
Biztalk
> picks up the file (it disappears from the folder). So far, no problem.
>
> Then, nothing happens. When I look in the event log, I find the following
> message:
>
> There was a failure executing the receive pipeline:
> "Microsoft.BizTalk.DefaultPipelines.XMLReceive" Source: "XML disassembler"
> Receive Location: "e:\ReceivePO\*.xml" Reason: The disassembler cannot
> retrieve the document specification by using this type: "PO". Either the
> schema is not deployed correctly, or more than one schema is deployed for
the
> same message type.
>
> Followed by:
>
> The Messaging Engine encountered an error publishing a batch of "1"
messages
> to the Message Box database for the transport adapter "FILE". Please refer
to
> Health and Activity Tracking tool for more detailed information on this
> failure and check the endpoint bindings are correctly configured.
>
> The "FILE" adapter is suspending a message coming from Source
> URL:"e:\ReceivePO\*.xml". Details:"Error in accessing the part data or one
of
> its fragments. The part or fragment may not exist in the database
>
>
>
>
> Where do I look to see if my schema was deployed properly?
>
> My development PC runs on Windows XP Professional. The Biztalk Server 2004
> and SQL Server share the same machine running on Windows 2003.
>
> If anybody has an idea, let me know.
>
> Thanks for your help.
>
>
> --
> Marc-Andre Laurin, MCSD
> 20-20 Technologies

[ Post a follow-up to this message ]

Also try validating your XML against the schema (right-click on the schema, 
go to "Properties", set Input instance filename and click Ok. Then right-cli
ck on the schema and
select "Validate Instance").

Thanks
Tatyana
--------------------
>From: "Devdutt Patnaik" <aquarius@taurus.com>
>References: <D4A3CCFE-3465-42F4-AB56-64822B151401@microsoft.com>
>Subject: Re: Biztalk 2004: Error in schema deployement
>Date: Wed, 15 Sep 2004 16:11:38 -0400
>Lines: 72
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
>Message-ID: <#p2m2A2mEHA.1248@TK2MSFTNGP09.phx.gbl>
>Newsgroups: microsoft.public.biztalk.orchestration
>NNTP-Posting-Host: host-65-124-127-205.amicore.com 65.124.127.205
>Path: cpmsftngxa06.phx.gbl!cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!TK2MS
FTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.orchestration:8180
>X-Tomcat-NG: microsoft.public.biztalk.orchestration
>
>The type "PO" suggests that you are not using target namespace for your
>schema?
>Verify that you have not deployed the same schema under a different
>assembly.
>If this doesn't work then create a custom pipeline, Put an XML Disassembler
>and point the disassembler to your schema, so that BizTalk knows which
>schema the message is talking about when its message type is "PO".
>HTH
>Regards
>Dev
>"Laurinma" <Laurinma@discussions.microsoft.com> wrote in message
>news:D4A3CCFE-3465-42F4-AB56-64822B151401@microsoft.com... 
>my 
>type. 
>Biztalk 
>the 
>messages 
>to 
>of 
>
>
>


--

This posting is provided "AS IS" with no warranties, and confers no rights. 
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note:  For the benefit of the community-at-large, all responses to this mess
age are best directed to the newsgroup/thread from which they originated.

[ Post a follow-up to this message ]