URL Xi Adapter
Hi,
just a short question . What is the url of the XI-Adapter. I know it's in the abap stack and has the port 80XX. So it must be soemthing like http://[server]:[ABAP-Port]/?????? but I am not sure of the rest of the URL. Is it the same like the ABAP-Proxy on an XI
kind regards Bernd
The URL is
http://server:ABAP-port/sap/xi/engine?type=entry
Also refer to Note 791379 - XI Adapter service properties documentation
Regards
Bipin
Similar Messages
-
Reg Unable to find URL for Adapter Engine Error
Hello,
During execution of a scenario, i am getting these errors in sxmb_moni:
AE_DETAILS_GET_ERROR
3: Unable to find URL for Adapter Engine af.xip.poecspxioo4
Error when reading the access data (URL, user, password) for the Adapter Engine.
Seems like it is a problem of XI Server unable to locate the Central adapter engine due to some parameter not set properly.
So, what are the points we can check while installation of XI so as to rectify this problem.Hi all,
I got the similar error in my scenario and i solved the same.Actually i ma not pretty surte this will solve your problem.
In my case proxy generation settings was mis configured in the sender system. so its caused the reason.
I made an entry in the SPROXSET table and i did other activities like RFC and application system also.
Then its worked for me. Its not matching with your case please do ignore this one
Regards
Vijay -
Basic URLs of adapter engine associations properties are missing
Dear all
We are running on the nw 7.11 pi version.
And we recently enabled the ssl on the system.. we have HA in place with web dispatcher.
We updated the exchane profile parameter with all ssl n required parameters.
CPA cache refresh is working fine.. but. While doing the Intergration server ABAP cache its failing.
And we checked the sap note 1678104 under the XRIA assoctiation and as well as under the Basic urls of adapter engine "Secure URL" properties are missing . Since we r not able to update this property.. the adapter engine is still ponting to http url instead https.
Please see the screen shot.
Regards
Manoj KHi Agasthuri,
yes, maybe something gone wrong in the post install, I will ask the guy which did the installation of the PI. Therefore I didn't have the logon data for performing a cache refresh, but in the log entries it seems that this is working properly.
Hi Praveen,
in Communication Channel Monitoring (In PI this is no longer found under Adapter Monitoring), I can see that the messages are delivered, but I can't see the Audit Log entries there.
I checked the MDT, but there are also no messages displayed.
End-to-End-Monitoring seems to be a good solution, but it seems that it is something configured wrong in this installation I will try to get the guy which cares for Basis to look after it.
Best regards,
Daniel -
No_messaging_url_found: Unable to find URL for Adapter Engine
Hi,
I am facing the same problem. I have configured a RFC-File scenario.
I get the error"no_messaging_url_found: Unable to find URL for Adapter Engine af.<SID>.<server>"
and <INTERNAL.AE_DETAILS_GET_ERROR>
I get the error "no_messaging_url_found: Unable to find URL for Adapter Engine" when I execute the Function Module SAI_AE_DETAILS_GET.
This error occured in the line 235( sap_xi_adapter_services = sld_accessor->associators( iref = sap_xi_adapter_framework assocclass = 'SAP_HostedXIAdapterServi) of the FM.
The value is not filled and i get the error mentioned.
I have gone through thread and verified all the points mentioned.
I have checked SXI_CAHCE,there are no locked users in RSUSR200,
SXI_CACHE, Goto->AdapterEngine Cache, I have an entry af.<sid>.<server>
In SLD,Technical Landscape,Exchange Infrastructure I have the entry <SID>.<Server> against the Adapter Engine
But as was mentioned in the thread the line 241 of the Fucntion Module has 'adapterType' and not 'Adaptertype' as in the exchange profile.I did not try changing 'a' to 'A'.
Could you please let me know how to solve the problem.
Thanks in advance.Hi Vani,
Check the pipeline URL in the SLD
Business System->URL
It should be
http://host:HTTPport/sap/xi/engine?type=entry
Just check this thread- may be useful-
File Adapter - Sender Problem
RFC adapter - AE_DETAILS_GET_ERROR - no adapter engine
https://websmp103.sap-ag.de/~sapdownload/011000358700002757652005E/HowtoMintorAF.pdf
Hope this helps,
Regards,
Moorthy -
Unable to find URL for Adapter Engine af.xid.xidev ?
Hi,
I have scenario.
Abap proxy -
> ccBPM -
> RFC (synchronous).
The error happen for ccBPM -
> RFC
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>2: Unable to find URL for Adapter Engine af.xid.xidev</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Any idea for what happening ?
Cheers
FernandHi.
Have you tried with this
Re: Wrong Adapter Engine on RWB?
Regards
Seshagiri -
Unable to find URL for Adapter Engine
Hi,
We have installed the XI 7.0 and I have realized a simple scenario "File > XI > File" in order to validate the installation... and on has a dump around Adapter Framework.
Inside SXMB_MONI, on has the following error:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.xid.bcnssap006</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>no_messaging_url_found: Unable to find URL for Adapter Engine af.xid.bcnssap006</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.xid.bcnssap006</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
It's probably a problem with aii but which one ?Hi Mickael,
The problem that you are facing looks like it is unable to connect to the adapter engine itself, please check the following:-
The userid being used must have the authorizations of group SAP_XI_APPL_SERV_USER on the Integration Server.
*During the configuration of the adapter (From Help documentation):-
<i>Specifications for the Integration Engine
Enter the complete address (URL) of the Integration Engine that you want to send the message to:
XI.TargetURL=http://IntegrationEngineHost:port/pipeline-arguments
This specification is mandatory.</i>
One suggestion:- Please try the following and see if you are still facing the problem, this might help you in decreasing the number of places to verifyconfigurations!
Again, from help:-
<i>The Integration Engine address can also be accessed dynamically from the SAP System Landscape Directory (SLD). The following entry is added to the configuration for this purpose:
XI.SLDConfiguration=SLDaccessor
In this case the URL of the corresponding Integration Server for the system specified with XI.SenderService is read from the SLD and used instead of the value specified under XI.TargetURL. Therefore, specify the following:
XI.TargetURL=<fromSLD>
To be able to access the SLD, the SLDaccessor service must be configured correspondingly and the respective entries must be maintained in the SLD.</i>
Hope this helps!
-Sushumna -
Error : Unable to find URL for Adapter Engine
Hi Experts,
I have searched several forums , but i am not clear on how to resolve this error.
I am using XI 3.0, my scenario is File->XI->File
I am getting this error in SXMB_MONI.
*Can any body suggest me a clear step-by-step procedure to solve it.*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Message canceled
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.xd2.host-dev</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>no_messaging_url_found: Unable to find URL for Adapter Engine af.xd2.host-dev</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.xd2.hydrus-dev</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
saiHi Debashish,
Thanks for ur reply,
I have executed
--->Execute SAI_AE_DETAILS_GET from se37
>Enter AE name:<host>.<systemid>
After executing, i got these param
Exception NO_ADAPTER_ENGINE_FOUND
Message ID: SAI_GLOBAL Message number: 016
Message:
no_adapter_engine_found: Unable to find Adapter Engine host-DEV.XD2
Exchange profile parameters are like this
Calling function EXCHANGE_PROFILE_GET_PARAMETER
Retrieving data from the XI Profile...
Function call terminated sucessfully
Retrieved value of
section = Connections
parameter = com.sap.aii.ib.server.connect.webas.r3.ashost
-> value =
and i dont have authorizations for SU01 fro lock/unlock.
Any suggestions how to proceed.
Thanks
Sai -
What is the URl for Adapter Monitoring?
My Xi system is not recognizing host name. It needs the IP to be specified.
I added it in the hosts file of my front end machine.
But it is still not helping.
So Can you pl let me know where else I can change to reflect IP instead of host name?
Also what is the URL to access Adapter Monitoring.
Thanks,
BhaskarHi,
then you made somethong wrong. At least the hosts file should help..
Adapter Monitor:
http://<xi_box_adress>:<port>/MessagingSystem
a, it is case sensitive
b, there are of course only java based adapters (no idoc)
ooops, now I see.. Yes, Adapters are of course in the Runtime Workbench.. Component Monitoring and then Adapter Monitoring and for some adapters Communication Channel Monitor
Peter
Message was edited by:
Peter Jarunek -
Error while reading access data (URL, user,password) for the Adapter Engine
Hi,
Any idea on below message? I am doing file to file scenario and got the below tarce from sxmb_moni.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.pi1.piserver1</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>no_messaging_url_found: Unable to find URL for Adapter Engine af.pi1.piserver1</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.pi1.piserver1</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
BalajiIt looks like the adapter engine is not able to register him self on SLD, you have to check in the SLD the "Exchange Infrastructure" domain, you have to verify restarting the J2EE the adapter engine update the entries in the SLD related to the specific XI Domain.
Launch Visual Administrator >> Server >> Services >> SAP AF CPA Cache
Enter the appropriate values for:
SLD.selfregistration.hostname (Use fully qualified hostname)
SLD.selfregistration.httpPort
SLD.selfregistration.httpsPort
Sandro -
URL for Central Adapter Engine
Hi,
It seems like our XI Server is unable to locate the Central adapter engine for doing an outbound RFC call. I am trying to call an RFC using the RFC adapter, and getting the following error:
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.nw4.netweaver</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>no_messaging_url_found: Unable to find URL for Adapter Engine af.nw4.netweaver</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.nw4.netweaver</SAP:Stack>
Where do we maintain the URL of the adapter engine ?
thanks,
ManishI have the same problem since we changed the name of the database server - the server name reported in the error is the old name. I've checked all the properties in this thread, plus follwed through OSS note 764176 with no luck. All the properties reflect the new name, but testing the proxy (SPROXY) still fails with the error:
<CODE>INTERNAL.AE_DETAILS_GET_ERROR</CODE>
<ERRORTEXT>Error when reading the access data (URL, user, password) for the Adapter Engine af.xix.sapsbxcrmdb2</ERRORTEXT>
sapsbxcrmdb2 is the old database server name.
I found one location where this is displayed - in transaction SXI_CACHE (in the client of th integration server), Menu option GOTO -> Adapter Engine Cache. The column 'Adapter Engine Name' reflects the incorrect name. Where is this property stored?
I cleared this entry manually by selecting the row and clicking on the trash can icon. Later it was refreshed properly.
-Mike
Update: I found that the SOAP Reciever channel in my Integration Scenario had a hard-coded entry pointing to the old integration server name in the property 'Adapter Engine'. I changed this by selecting the 'Integration Server' in the drop down. This changed the error behavior (still doesn't work, but the above errors went away).
-Mike
Message was edited by: Mike Hatch
Message was edited by: Mike Hatch
Message was edited by: Mike Hatch -
Error while calling RFC adapter(FILE-XI-RFC scenario)
Hi,
I am trying for FILE-XI-RFC scenario. I am getting the following error. I have checked in message monitoring. The error is coming while calling the RFC adapter. Can any body tell what problem is this?
Regards,
Dhana
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.f23.sofd00001530a</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>2: Unable to find URL for Adapter Engine af.u7a.us4296</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.f23.sofd00001530a</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>Hi,
I did SLD check.
The status says 'Summary: Connection to SLD works correctly'.
But it fails while checking the access to XI profile.
Here is the status
Summary: Connection to SLD works correctly
Now checking access to the XI Profile
Properties of RFC destination LCRSAPRFC
RFC host:
%%RFCSERVER%%
program id: LCRSAPRFC_DZ1
gateway host:
gateway service:
Testing the RFC connection to the SLD java client...
RFC ping returned exception with message:
/ CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679#Transaction program not registere -
Creating a File Adapter in XI 3.0
Hi
I want to use the File adapter in XI 3.0 to generate a file on my server. Is there any detailed!!! step by step guide where I can read about this?
I have created a business service, a communication channel, interface determination and a receiver determination. I have a R/3 system which sends an IDOC to XI where I want XI to use the File adapter to export a csv or text file. I get the following error(TR:SXMB_MONI) in my XI system:
no_messaging_url_found: Unable to find URL for Adapter Engine af.xid.nb13
Error when reading the access data (URL, user, password) for the Adapter Engine af.xid.nb13
Best regards
GöranHi Sai,
You will surely have that option in RWB just check this link below...
http://www.dataxstream.com/2010/11/configuring-availability-time-planning-in-sap-pi/
Regards,
Naveen -
We are getting the following error in XI that we have not received before, has anyone seen this error and can help us?
<b>3: Unable to find URL for Adapter Engine af.xip.rnosapxip1</b>
<b>Error when reading the access data (URL, user, password) for the Adapter Engine af.xip.rnosapxip1</b>
Thanks in advance
MikeI was finally able to get into the exchangeProfile and as soon as I logged in I got the following error:
?????????? (I/O error)
Stack Trace class com.sap.rprof.dbprofiles.DBException:
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:418)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1271)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3884)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3320)
at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:104)
at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1286)
at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:193)
at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfile(RemoteProfile.java:143)
at com.sap.rprof.dbprofiles.ExchangeProfile.getExchangeProfile(ExchangeProfile.java:45)
at com.sap.rprof.remoteProfile.webui.ProfileWebTree.(ProfileWebTree.java:24)
at com.sap.rprof.remoteProfile.webui.Edit.getWebTree(Edit.java:320)
at jsp_treeexprof1182552776717._jspService(jsp_treeexprof1182552776717.java:19)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:538)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
Any clue on what this means?
Thanks
Mike -
hello
running a sync service and recieve this error.
couldnt determine if this is XI problem or WS.
if it is XI, how can I debug it?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>3: Unable to find URL for Adapter Engine af.xip.mgnt154</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>Hi,
This merely problem with cache. It is saying XI engine is not able identify the adapter engine URL.
please do this.
You can view the cache data in
transaction SXI_CACHE. To do this,
select Go to �� Adapter Engine
Cache.
You can delete the cache data in
transaction SXI_CACHE. To do this,
select Go to �� Adapter Engine
Cache. Then choose the recycle bin
push button ( ).
Thanks,
Gujjeti -
Hi,
While implementing a file to file interface I am facing problem in Integration Engine. Data is not passing to Integration engine, so it is not able to reach receiver.
Receiver file adapter is working fine for other scenarion like IDoc to File.
File Adapter status is Green in RWB.
I am not able to see message in SXMB_MONI
The error details in Adapter Engine is bellow
Audit Log for Message: 410424a0-c496-11da-aa48-00111120e6db
Time Stamp Status Description
2006-04-05 16:51:37 Success Channel file2file_in_channel: Send binary file "D:\usr\sap\QN7\DVEBMGS00\work\XiPattern2\testfile2in.xml". Size 209 with QoS EO
2006-04-05 16:51:37 Success Application attempting to send an XI message asynchronously using connection AFW.
2006-04-05 16:51:37 Success Trying to put the message into the send queue.
2006-04-05 16:51:37 Success Message successfully put into the queue.
2006-04-05 16:51:37 Success The application sent the message asynchronously using connection AFW. Returning to application.
2006-04-05 16:51:37 Success The message was successfully retrieved from the send queue.
2006-04-05 16:51:37 Success File "D:\usr\sap\QN7\DVEBMGS00\work\XiPattern2\testfile2in.xml" deleted after processing
2006-04-05 16:51:37 Success The message status set to DLNG.
2006-04-05 16:51:37 Error Transmitting the message to endpoint http://sapep:50000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404 : Not Found.
2006-04-05 16:51:37 Success The asynchronous message was successfully scheduled to be delivered at Wed Apr 05 16:56:37 GMT+05:30 2006.
2006-04-05 17:01:37 Success The message status set to WAIT.
2006-04-05 17:06:37 Success Retrying to send message. Retry: 3
2006-04-05 17:06:37 Success The message was successfully retrieved from the send queue.
2006-04-05 17:06:37 Success The message status set to DLNG.
2006-04-05 17:06:37 Error Transmitting the message to endpoint http://sapep:50000/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 404 : Not Found.
2006-04-05 17:06:37 Error The message status set to NDLV.
Please suggest the solution.
Is there any place where I can find the exact error log?
Thanks,
Smita.Hi,
I found there was a problem with HTTP port in the URL. After fixing this, I am able to see the message in SXMB_MONI. But it is with an error. The error details is as bellow.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.qn7.sapep</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>no_messaging_url_found: Unable to find URL for Adapter Engine af.qn7.sapep</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.qn7.sapep</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In RWB->Adapter engine there is a success message, But in the RWB->Integration Engine there is an error with Error Code : AE_DETAILS_GET_ERROR.
Please suggest how to fix this. I am able to logon to XI system with user XIAFUSER.
Thanks,
Smita
Maybe you are looking for
-
Battery problem & Device heating
My device BB Curve 9360 one month old is having battery charge problem.I cant even use it for half a day.It will dry out within 5 hrs and also the mob is getting heated while using like...reading messages,while talking for some time.Some has asked me
-
Help! 27" iMac bought In 2009 has never gone a day without fighting spinning wheel of death
We bought this at the end of 2009, and ever since has had issues with getting the "beach ball" or spinning wheel of death anytime you click something new, try to open a file, or a program or any link, etc. It soins for about a minute then is good to
-
Final Cut Pro Unix Executable file??? what do i do?
Hey All, So I wanted to dig up an old movie i edited in 2003 so i took out the old IMac. I found the Final Cut Pro 2 sequence on there but because all the footage (capture scratch, etc.) is saved to an external hard drive i need to reconnect the mate
-
Underscores Found Under the .HHK's Hood
Hi RHelpers! Question for you. Here's a portion of my .hhk file... I have a question about some entries in our .hhk file. I *think* (but can't remember) that this index was generated using the SmartIndex wizard. Notice the items marked in orange: <li
-
Hi, What technology shoud we use to replace all the Java Applets in our MII applications ¡? . The reason is that java applets slows them down , sometimes the application screen ( GUI ) seems like not responding & when the end user is proactive