The system displays the message "Error during call of SAP back end system (see long text)". The long text contains the following text as additional information: "Name or password is incorrect. Please re-enter" or the note "Error when you open an RFC connection" when you specify the destination, or the additional information "Destination blocked: too many failed connections due to wrong user/password".
The reason of the error may be, when generating the SAP-OSS, you accidentally entered an incorrect S-user ID or an incorrect password or you changed the password of the S-user defined in the SAP-OSS destination in the user administration of the SAP Support Portal under http://service.sap.com/user-admin. However, the destination still uses the old password.
Problems may occur when changing the password because changes to a user in the SAP Support Portal must be replicated to the other systems of the SAP support back end before they are active. This replication may take up to half and hour. Even if you simultaneously change the password of a user in the SAP Support Portal and in the SAP-OSS destination, the user may be locked after several failed logon attempts because the password change has not yet taken effect in the back-end system used by Solution Manager.
For the additional information "Destination blocked: too many failed connections due to wrong user/password", the same problem specified above is the cause. The Solution Manager recognized this and blocked the destination for i's applications. This is to prevent the relevant S-user being locked in the SAP back-end system, among other things. In transaction SOLUTION_MANAGER, choose "Goto -> RFC Connection Error" to obtain a list of the RFC destinations for which the above error occurs. The system then displays a message that provides information about the cause of the problem (reactivate the connection only after you have performed the steps described in this note to repair the destination).
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. The same applies if the user is locked (error code 2). As of Support Package 12 S users can no longer be locked from the system.
If the system issues message SOLMAN_SAP_BACKEND 015 with the additional information "Destination blocked: too many failed connections due to wrong user/password", refer to the long text of this message. After the repair, if the authorization test is successful, release the connection in transaction SOLUTION_MANAGER again for use in the Solution Manager by choosing "Goto -> RFC Connection Error".
If you must change the password of the S-user defined in SAP-OSS, remove the user ID from the destination before you make the change and reenter the user with the new password at least half an hour later. As a result, you can avoid locking the user if incorrect logon attempts are made in the meantime.
For the additional information "Error when opening an RFC connection", there is probably a technical network problem. To solve this, regenerate the SAP-OSS destination as follows:
1. The SAP-OSS destination is copied from the SAPOSS destination. To ensure that no incorrect settings are copied, test the connection for the SAPOSS destination in SM59. If this test does not return any error, proceed with step 4.
2. If this test returns errors, call transaction OSS1, choose the menu option "Parameter -> Technical settings", and maintain the settings as described in Note 33135.
3. When you save the entries, the system regenerates the SAPOSS destination . As a result, errors should no longer occur for this destination in the connection test in transaction SM59. If errors still occur, check the entries.
4. Regeneration of destination SAP-OSS
- Use transaction SM59 to delete destination SAP-OSS. If you cannot delete the destination, it is not completely regenerated based on SAPOSS; instead, only the user and the password are reset.
- Up to release 7.0 Support Package 11: Use transaction DSWP -> choose "Edit -> Global settings". Choose the tab "Connection to SAP".
- As of release 7.0 Support Package 12: Go to the solution overview of transaction DSWP. Choose the menu point "Settings -> Global settings". Choose the tab "Connection to SAP".
- As of release 7.1: In the work center SAP Solution Manager: Configuration -> Basis Configuration -> 2 Specify User & Connectivity Data-> Specify Connectivity Data-> Maintain Connections.
- Re-enter the user (S user for your customer number) and the password and save your entries. When you save, the destination SAP-OSS is regenerated if it was previously deleted. In this case, the technical settings are transferred from those in the destination SAPOSS. If SAP-OSS was not deleted, the technical settings remain unchanged.
5. Retest the connection for the SAP-OSS destination in transaction SM59.
6. If the connection test functions but the authorization test fails, you can solve this problem by proceeding as described for the additional information "You are not authorized to logon to the target system".