cancel
Showing results for 
Search instead for 
Did you mean: 

In XI no adapters are visible RWB and the error "AE_DETAILS_GET_ERROR"

former_member971233
Discoverer
0 Kudos

In XI no adapters are visible in the RWB and I get the error "AE_DETAILS_GET_ERROR"<BR>

It happens after a database copy from PRD to QAS.<BR>

I tried restarting the system, and checked the SLD content. Also the cash is refreshed.<BR>

The standard after care actions are carried out, like: SXMB_ADM, SMICM, SE06, STMS, Exchange Profile, SM59, RZ20 and RZ21, SLD content, SLDAPICUST and RZ70.

Thanks in advance

Accepted Solutions (1)

Accepted Solutions (1)

mstitsel
Active Participant
0 Kudos

When in XI no adapters are visible RWB or you get the error "AE_DETAILS_GET_ERROR" I have several steps for this:

<P>

Check that all adapters are running in the Visual Administrator (under services)

<P>

Make sure the RFC's to the SLD (SAPSLDAPI) and Exchange profile (LCRSAPRFC) are maintaint correct in SM59.<BR>

Check this also with transaction SLDcheck

<P>

Make sure the correct URL is maintaint in SXMB_ADM > Integration Engine configuration<BR>

This should be like : http://hostname:80nr/sap/xi/engine?type=entry

Check the settings with F7.

<P>

Check the users and passwords in the ExchangeProfile.<BR>

<P>

Check the users and passwords in SAP (check for locked users with RSUSR200).<BR>

<P>

Check the users and passwords in the SLD if this is a standalone (check for locked users).<BR>

Try logging on with all XI users in the useradmin of the SLD (http://hostname:5nr00/useradmin)<BR>

Sometimes a new password must be set. You can set it directly to the old password.<BR>

<P>

If there is a problem that not all XI components are shown in the SLD: see note 764176

<P>

If there is a problem between the function module SAI_AE_DETAILS_GET (line 241 adapaterType) and the SLD

<P>

(class browser > tab LD > XI Adapter Service : it shows AdapterType).<BR>

In this case create a repair in the function module by editting it and transport it to the other XI systems.

<P>

Restart XI

<P>

Perform a cache refresh:<BR>

http://hostname:5nr00/CPACache/refresh?mode=full<BR>;

use the XIDIRUSER user

<P>

http://hostname:5nr00/rwb/rtc?op=init<BR>;

use the XIRWBUSER user

<P>

SAP transaction SXI_CACHE > start complete cache refresh (shift F6)<BR>

<P>

Sometimes a restart of the service SAP XI AF messaging is nessesary.<BR>

You can perform this restart via the Visual Administrator<BR>

<P>

If all does not work: check if the content is up to date.<BR>

Sometimes after a patchlevel upgrade, the XI basis content is forgotten.<BR>

Importing the XI Content for Software Component Version SAP Basis 6.40 SR1:<BR>

Copy XI3_0_SAP_BASIS_6.40_<PATCHNR>_00.tpz to directory <BR>

<P>

/usr/sap/<SAPSID>/SYS/global/xi/repository_server/import/<BR>

Goto the the XI Repository (Design).<BR>

Choose ? Tools ? Import Design Objects<BR>

Choose the file XI3_0_SAP_BASIS_6.40_<PATCHNR>_00.tpz<BR>

Import the file

<P>

Check if the XI services in SICF are active.<BR>

Activate them with : SE38 > RSXMB_ACTIVATE_ICF_SERVICES<BR>

<P>

Transaction SUPC (mass generation of roles) for all SAP_XI* roles.<BR>

And perform a User comparison in transaction PFCG for all SAP_XI_* rolles<BR>

<P>

User comparision (via SU01 > PISUPER > dubbelclick on each roll)<BR>

<P>

Check the CIM content of the SLD.<BR>

This is very intensive work.<BR>

Check and compare with a correct running XI/PI system the content.<BR>

SLD > Administration > Content Management<BR>

Check and compare all components that have associasions!!!<BR>

<P>

Perform a complete cache refresh via URL:<BR>

http://hostname:5nr00/rep/start/index.jsp<BR>;

Administration > Repository > Cache overview<BR>

Administration > Directory > Cache overview<BR>

Administration > Runtime > Cache overview<BR>

<P>

Refer to Note 1031321 "Self-Registration of Adapter Engine and RWB fails"

Best regards,<BR>

Marco

<P>

Answers (1)

Answers (1)

Shabarish_Nair
Active Contributor
0 Kudos

Solutions can be;

1. Re-import SAP BASIS SWCV 7.0 into Integration repository

2. Apply SAP Note 764176.

Also ref:

/people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory