Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Getting data from SAP via RFC
- This topic has 4 replies, 1 voice, and was last updated 9 years, 1 month ago by
community-content.
-
AuthorPosts
-
-
March 20, 2010 at 5:58 AM #24421
hi,
i want to get some data using a rfc in sap.
i have created some schema-files by adding a generated item (Add Adapter Metadata -> WCF-SAP), an orchestration, shapes and physical and logical ports.
when i test my solution, i get following error:
(I know, this is german, but possibly you can help me yet)
Event Type: Error
Event Source: BizTalk Server 2009
Event Category: BizTalk Server 2009
Event ID: 5753
Date: 19.03.2010
Time: 20:39:52
User: N/A
Computer: DEGAB-BIZ-01
Description:
Eine vom Adapter “FILE” am Empfangsspeicherort “Receive Location1” mit dem URI “C:\Projects\SAP_GAB\BT_RFC_AFIHSYNC\receiveExchange\*.xml” empfangene Nachricht wurde angehalten.
Fehlerdetails: Die veröffentlichte Nachricht konnte nicht weitergeleitet werden, da keine Abonnenten gefunden wurden. Dieser Fehler tritt auf, wenn die abonnierte Orchestrierung oder der abonnierte Sendeport nicht eingetragen wurden oder einige der zur Prüfung des Abonnements erforderlichen Nachrichteneigenschaften nicht höher gestuft wurden. Verwenden Sie die BizTalk-Verwaltungskonsole, um diesen Fehler zu beheben.
MessageID: {8852475A-8D1B-4043-8F47-6AFC9C679A27}
InstanceID: {553F87AB-2661-403D-A93B-7EAB97A66BB1}Can anyone help me with this error?
Thanks!
mster
-
March 20, 2010 at 6:46 AM #24422
this translates to –
“FILE” to receive location “Receive Location1” with the URI “C:\Projects\SAP_GAB\BT_RFC_AFIHSYNC\receiveExchange\*.xml” received message has been suspended.
Error details: The published message could be not forwarded because no subscribers were found. This error occurs when the subscribed orchestration or subscribed Sendeport were not registered or some necessary to check the subscription message properties were not promoted. To resolve this error, use the BizTalk Administration console.
MessageID: {8852475A-8D1B-4043-8F47-6AFC9C679A27}
InstanceID: {553F87AB-2661-403D-A93B-7EAB97A66BB1}
[Automatically translated by Microsoft® Translator-
March 20, 2010 at 6:53 AM #24423
so basically you published some message to biztlak for which no-body is subscribing .. hance the routung failure.
You can quickly check thae following –
1. you have used XMl receive pileline(not- pasthrouch pileline) for the receive location.
2. You have correctly added the wcf-action mapping for the WCF-SAP send port.
3. If you are mapping multiple logical send ports to one physial send port, the action names match the actual logical send port names in the orchestarion.-
March 22, 2010 at 1:57 AM #24429
i have tried the XML and the passthrough pipeline an i haven`t multiple logical send ports to one ohysical send port in my aplication. i don`t know whether i have corrctly added the wcf-action mapping for the wcf-sap-send port – i hope so …
unfortunately i can´t find a tutorial / “how to” with wich i can check this …
-
March 22, 2010 at 4:19 AM #24430
i have found now an error in my receive location!
but now i have a new problem:
Error 3 Unable to deploy early bindings.
Failed to update binding information.
Could not validate configuration of Primary Transport of Send Port ‘BT_RFC_AFIHSYNC_1.0.0.0_Module_1.ocGetOrdersFromSAP_connectToSAP_d6ae850a56280cbf’ with SSO server.
Dies ist ein ungültiger Wert für die Eigenschaft ‘URI’.
Dies ist ein ungültiger Wert für die Eigenschaft ‘URI’. 0 0That means, my URI is incorrect … anybody an idea? i have tried a lot of different URIs … no success … 🙁
-
-
-
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.