Home Page › Forums › BizTalk 2004 – BizTalk 2010 › request response webservice using Wizard
- This topic has 1 reply, 1 voice, and was last updated 9 years, 10 months ago by
community-content.
-
AuthorPosts
-
-
August 15, 2008 at 7:37 AM #20417
Hi Gurus,
I am trying to access a BAPI from SAP and for that I published one webservice using the schema.I had used the schema for the request response and I setup the receive location using the wizard itself and I created a Static Solicit response send port as I am expecting a response in the same port from SAP.But When I am calling the webservice using .NET program I getting the following error.In the steps mentioned above I even created a filter at the send port based on the receive port used.did I miss out anything?I am not using any orchestration as the process is pretty straight forward.Please let me know if I missed out anything or if I have to add anything.Its very urgent.
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5753
Date: 8/15/2008
Time: 10:18:26 PM
User: N/A
Computer: SCCUTL02-SDC
Description:
A message received by adapter “SOAP” on receive location “WebService_BizTalkTestRFC/TestRFC_WS” with URI “/BizTalkTestRFC/TestRFC_WS.asmx” is suspended.
Error details: There was a failure executing the receive pipeline: “Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35” Source: “XML disassembler” Receive Port: “WebPort_BizTalkTestRFC/TestRFC_WS” URI: “/BizTalkTestRFC/TestRFC_WS.asmx” Reason: The type BiztalkTest_RFC.ZTESTRFC__x32003 is not a valid part type for a message. This invalid type may be from a property schema.
MessageId: {08E75808-85C3-4D4F-AB1F-6C694FA66217}
InstanceID: {E655E377-4925-4CC8-8642-DD585EDBD37A}Cheers
Sri,Singapore
-
August 17, 2008 at 6:20 AM #20426
Haven’t seen that error before… You’re using the SOAP adapter for this? If you are on R2, there’s not much reason to use the SOAP adapter now that you have the WCF-BasicHttp adapter. This issue will probably go away just by using the WCF adapter, and even if it doesn’t, you will have MUCH better troubleshooting capabilities and flexibility to fix the problem. Here is more info: http://msdn.microsoft.com/en-us/library/bb246098.aspx.
Hope this helps!
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.