cancel
Showing results for 
Search instead for 
Did you mean: 

Solution manager Trusted RFC error code 1

Former Member
0 Kudos

Hello All,

We have setup the RFC connections from solution manager to the DEV system successfully.

However when we set up the RFC connections to the QAS system the RFC trusted connection from QAS to SM failed the authorisation test (SM59 ->test-> authoirsation) with the error message "You are not authorized to logon the target system (error code 1). The connection test passes.

The RFC connections from SM to QAS work fine (READ AND TRUSTED). The BACK connection from QAS to SM also works.

I have been given SAP_ALL, SAP_NEW and S_RFCACL and the connection is still not being created properly. We have tried deleting and recreating all the RFC connetions and just the Trusted connections. I log in as the same user to both systems when the connection are being created.

Any help would be appreciated

Thank you

Susan

Accepted Solutions (1)

Accepted Solutions (1)

Former Member

hi Susan

the solution for your p[roblem is create a new role which contain Authorization Objects like S_RFC & S_RFCACL. fill in the details and assign this role to the user id.

regards

Janak Mehta

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Susan:

The solution for your problem is in the following OSS Note #637429:

https://websmp101.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012006153200000582052003

Hope this helps!

Regards,

Federico

kevshill
Participant
0 Kudos

Hi Susan,

when you get the message

You are not authorized to logon the target system (error code 1)

Keep the cursor on the message and click on the documentation icon or CTRL+F1

Here you will get some documentation which will help you to find out the exact cause of the error.

An extract from the documentation is as follows.

**************

The error codes have the following meanings:

0,,Invalid logon data (user and client) for the trusting system

,,Solution: Create the user in the correct client in the target system.

1,,The calling system is not a trusted system, or its security key is invalid.

,,Solution: Create a trusted system

2,,The user has no authorization in the trusted system (object S_RFCACL), or logged on as one ,,of the protected users 'DDIC' or 'SAP*'.

,,Solution: Assign the user the correct authorizations, or use a user other than the protected ,,users 'DDIC' or 'SAP*'.

3,,The timestamp on the logon data is invalid

,,Solution: Check the system time on the client and server hosts and the validity period of the ,,logon data. (Note: the default date 00:00:00 means that the validity is unrestricted.

********************************

Also if you check transaction SMT2 in the 'trusted system' you will see the destination which is used to connect to the trusting system. Here you will have to check if the client and user setings are correct.

Hope this helps you.

regards,

Kevin Hill