Wrox Programmer Forums
Go Back   Wrox Programmer Forums > .NET > Other .NET > Biztalk
|
Biztalk General discussion about Biztalk server.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Biztalk section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old August 12th, 2004, 04:21 AM
Registered User
 
Join Date: Aug 2004
Posts: 8
Thanks: 0
Thanked 0 Times in 0 Posts
Default Error in BizTalk - SDK 2004 module 2 solution

Hi,

I am a newbie in biztalk, i have completed the first module of the 2004 update SDK. I have developed and deployed the second module as per the document.

although the Map had some errors while testing it with the "PoInstance.xml" (Even the built solution given in SDK had the same errors in the map !!) , the build had no errors and warnings.
I have deployed the project with no errors and warnings. All the ports, Orchestrations are ready and started.

When i paste the "POInstance.xml" to the FileDrop it is taken by Biztalk but does not come either to filedrop "Archive\ConfirmedPo" or "Archive\CommonPo".

I checked HAT using Search messages, with the "PoExample" schema
and the specific receive port which i use in the orchestration for the query.

The error says that the message could not be processed by the Messaging Engine because no proper subscriptions were found for it or that the schema input did not have paticular properties that were required to validate the subscription or that the send/receive ports were not started (Which actually was !)

The Message has status "Complete" for the DefaultReceiveXMLPipeline and has not gone further than this.

Please help.
If you need the actual working of the solution and the schemas i will provide it. i will also provide the the actual snapshot of the map errors and the HAT snapshots.

Thanks in advance
Regards



Vijay R
 
Old August 12th, 2004, 05:11 AM
Registered User
 
Join Date: Aug 2004
Posts: 8
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi,

Here is the actual error message from HAT:
----------------------------------------------------------------------
  Service Name: Microsoft.BizTalk.DefaultPipelines.XMLReceive

Activity ID: {28f86ee8-dc72-4baa-8a34-ab9ae3a29115}
Instance ID: {d12b612a-783c-4fc4-8184-bd9dc88283ac}
Host: BizTalkServerApplication
Type: Pipeline
Version ID: {f21605fc-288e-4e27-bae1-04f15907d1a2}
Deployment Time: 3/9/2004 4:36:30 PM
State: Terminated
Start Time: 8/12/2004 3:25:55 PM
End Time: 8/12/2004 3:25:56 PM
Duration: 00:00:00.9660000
Exit Code: 0xC0C01680

Error Info: Could not find a matching subscription for the message. The Messaging engine failed to process a message submitted by adapter:FILE Source URL:D:\VijayR\BizTalk Visual Studio Projects\VB2BSolution1\VB2BFILEDROP\ReceivePO\*.xm l. Details:Could not find a matching subscription for the message. . This error occurs if the subscribed orchestration schedule or send port has not been started, or if some of the message properties necessary for subscription evaluation have not been promoted. Please refer to Health and Activity Tracking tool for more detailed information on this failure

(PS : Can we attach files with message posts in this forum ? )

Thanks in advance







Regards
Vijay R





Similar Threads
Thread Thread Starter Forum Replies Last Post
Biztalk server 2004 schanda Biztalk 1 March 3rd, 2006 11:23 AM
question:biztalk 2004 subscription/orchestration pratdevil Biztalk 1 February 21st, 2006 05:11 AM
Query regarding BizTalk 2004 debsoft Biztalk 0 August 2nd, 2005 12:53 AM
Pipelines and ports for Biztalk 2004 PeterMathro Biztalk 0 May 14th, 2005 05:06 PM
BizTalk 2004 Business Rule Engine omshaath Biztalk 1 October 21st, 2004 08:24 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.