Skip to end of metadata
Go to start of metadata

Purpose

The purpose of this wiki is to provide details on why the SAPOSS RFC destination may fail with a username/password error.

Overview

It is possible to logon directly to the Marketplace with the username and new password however the authorisation test in SM59 for destination SAPOSS fails.This wiki looks at 2 different possibilities why this problem would occur. There is either a problem with the logon details in the SM59 RFC destination OR there is a replication issue on the SAP side. 

 

Troubleshooting

Problems have occurred with  SAPOSS RFC destinations in SM59. This happens after changing the password for the SAP Service Marketplace to investigate the issue check the authorisations for the relevant destination in SM59:

 


You will see something like the following:

 

The SAPOSS destination still fails even though the password is correct.

To resolve the issue see KBA 1636864   RFC connection error  - name or password is incorrect.

If it is possible to logon directly to the Marketplace with the username and new password however the authorisation test in SM59 for destination SAPOSS fails (even though the correct username and password are used), see note  982045 :

Check to see if you can log on directly to the SAP Support Portal with the user and password defined in the destination SAP-OSS. If you can log on in this way, but the authorization test for the "SAP-OSS" destination fails, enter the correct logon data for the destination directly (SM59, tab "Logon & security") and repeat the test. If this does not solve the problem, there is probably a replication problem within the systems of the SAP support backbone. Only SAP can solve this problem. Create a message under component XX-SER-SAPSMP-USR.

 

Related Content

Related Documents

Related SAP Notes/KBAs

Note 182308  Incorrect logon data in R/3 destination SAPOSS

  • No labels