SolMan 7.1 SP10: Managed Systems Configuration: client 000 OK, client 100 error

[rdiger_hckel]

Hello,

after installing SolMan 7.1 SP10 successfully I also completed the steps "System Preparation" and "Basic Configuration".

Now I'm connecting the managed ABAP systems to the Solution Manager by performing step "Managed Systems Configuration".

After several other ABAP systems I'm now connecting our productive CRM 7.0 EHP1 system "CM3" (SAP_BASIS 702).

I also connected the CRM development and CRM quality assurance system without a problem.

For client 000 everything worked fine, the RFC destinations were created and a green light is shown.

Now the problem is to connect the productive client 100:

The log for Activity RFC Connection says:

The corresponding dev_rfc tracefile says:

**** Trace file opened at 20140326 164911 W. Europe Standard Time, by disp+work

**** Versions SAP-REL 720,0,523 RFC-VER U 3 1468763 MT-SL

======> Name oder Kennwort ist nicht korrekt (Wiederholen Sie die Anmeldung)

ABAP Programm: SAPLSM_SETUP_API (Transaction: )

Called function module: FUNCTION_EXISTS

User: SOLMAN_ADMIN (Client: 001)

Destination: 0050568713C71ED3AD9FC4F78AC9D9EB (Handle: 16, DtConId: 27FEB4E356BCF14F99EB0050568713C7, DtConCnt: 1, ConvId: 64734943,{27FEB4E3-56BC-F14F-99EB-0050568713C7})

EPP RootContextId: 0050568713C71ED3AD9FB7AD4C4859EB, ConnectionId: 0050568713C71ED3AD9FB784232C59EB, ConnectionCnt: 1

EPP TransactionId: BDFDB4E3626AF14899EB0050568713C7

But both users taken to execute this step (SAP Solution Manager Administrator "SOLMAN_ADMIN" and Managed System Configuration User "SM_ADMIN_SM3") exist and have the correct provided password.

Does anyone have a clue?

Kind regards

Rüdiger Höckel

[Former Member · Accepted solution]

Hi Rudiger,

I am not sure if you are following the right process.

You have to first go to the systems ensure that ST-APIs are updated there, and go to rz70 and push the data into the SLD of Solman or to whichever is your Central SLD.

There after you need to go into Managed System Configuration -> Select the ABAP component showing up and then click on Configure.

This will help you to use a Wizard to establish RFC connections automatically.

Typically there will be no errors if you are following this step.

Are you following the Configuration guide available in the SMP?

Regards,

Ranjith

[rdiger_hckel · Accepted solution]

Hello Ranjith,

thanks for your quick response.

The ST-A/PI software component is the same on all systems: 01Q_700 #2.

SolMan system: SM3

CRM systems: CM0 (ok), CM1 (ok), CM3 (problem with client 100, client 000 OK).

I also tried the recommendation found in the SAP Community Network

(http://scn.sap.com/thread/3483642) but this didn't help either:

1.Delete system from LMDB.

2.Delete system from SLD of solman.

3.Re- register the system to SLD of solman(rz70 for AS ABAP)

[the LMDB synchronizes with the SLD every 10 minutes, system CM3 is visible again in the LMDB]

4.Now follow the steps in managed system configuration.

The wizard worked fine for client 000 but throws this error for client 100.

I use all the latest installation and configuration guides.

For this step I'm using the guide "Managed System Configuration" that is available in the SOLMAN_SETUP wiki.

https://websmp206.sap-ag.de/~sapidb/011000358700001120342013E.pdf

Kind regards

Rüdiger

P.S. In total I have already connected eight systems (SAP_BASIS 700 to 731) but this is the first system that gives an error.

[rdiger_hckel · Accepted solution]

As the managed system is on SAP_BASIS 702 I also followed SAP note

1734607 - SM: Authorization object S_RFC_TT 7.02 and higher

but this didn't help as well.

[Former Member · Accepted solution]

Hi Rudiger,

Could you assign the IP for the Managed System Host Name and check if it makes any difference?

this is in managed system configuration at configure system - 3rd step.....instead of the application server name which is what it says is not correct due to some reason.....enter the IP address. Get it from LMDB and retry establishing the rfc. This will work.

Regards,

Ranjith

[Reagan · Accepted solution]

If you were able to configure for client 000 and it fails for client 100 then it is not an issue with the IP address or connectivity. The error message is "Username or Password is incorrect". As this is a production system and the user is present in the CRM system then the issue could be with the password set for this user. Check whether there is some password restriction enabled on the server.

Try to login to the CRM system with the user and if the login is successful or assign a complex password for the user.

Regards

RB

[rdiger_hckel · Accepted solution]

Hi Ranjith,

instead of "ap400h.apetito.de" I tried both the IP address and just the single hostname

but the error still occurs.

Kind regards

Rüdiger

[rdiger_hckel · Accepted solution]

Hello Reagan,

the user SM_ADMIN_SM3 exists in the productive client 100 of system CM3 and is a "System" user so you can't log on with SAPGUI.

I changed the user type to "Dialog" and the password is correct.

Update:

I changed the password in SU01 and took this new password to the wizard.

Now it works better (the question "Do you want to upload roles" now finally appears again which is a good sign)...

I'll keep you updated.

Kind regards

Rüdiger

[rdiger_hckel · Accepted solution]

OK, after I changed the password for user SM_ADMIN_SM3 on the managed CRM system the RFC destinations were created successfully.

I just had to change the users SM_SM3 and SMTMSM3 who had no roles attached:

ZSAP_SOLMAN_READ_702 and ZSAP_SOLMAN_TMW_702

The only error message I still get is this one:

but when I use the "Test RFC" button I get a green light.

Kind regards

Rüdiger

[Reagan · Accepted solution]

Provide S_A.SYSTEM profile to the user and see if that helps.

Regards

RB

[rdiger_hckel · Accepted solution]

Thanks for the hint.

I added the profile to users SM_SM3 and SM_ADMIN_SM3 on the managed system.

But as it is working right now I don't want to delete and re-create the RFC destinations again - I hope you understand.

Kind regards

Rüdiger

[Reagan · Accepted solution]

You can do an authorisation check for the RFC's from SM59 and see if they throw the error.

Good to know the issue has been fixed.

Regards

RB