URL for Central Adapter Engine

Question

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,
Manish

Answer 1

I 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