We have applied SPS10 to our SOLMAN 7.1, and now we have problems when we try to set up a new managed system. In step 3 of Managed System Configuration, when we try to create the RFCs if, for any reason (for example, a wrong password), the creation fails, then we cannot fix the issue, whatever changes we make in the configuration parameters. From this point on, we get the following sequence of error messages:
- Name or password are wrong
- Establish connection to system <connection string>
- READ RFC not created in system <SID> client <client>
We have deleted the technical system, the users and the RFC that had been created (if any), and tried to configure it again, but when we go to this step again, it shows some of the parameters that we had previously entered (administrator users and saprouter strings) and, when we run the assistant, we get the same error. We have even tried using a 'fake' user for the managed system configuration user, and the assistant seems to keep using the previous one (in fact, after several attempts, it was locked in the managed system, due to wrong password). It does not matter what other options we choose (create or not the RFCs, generate the users and passwords or not, ...) we always get the same errors. It seems as if, after the first failed attempt, the system kept the old values somewhere.
If we create the users and RFCs manually, it works, but then we cannot assign them to the managed system. If we go to the Destinations section in the LMDB Technical System maintenance screen, and select the option RFC Maintenance, it goes to the same assistant that the managed system comfiguration uses.
Has anybody had the same problem? Or do you know if there is a way to assign the manually created RFCs to the managed system, without going through the assistant?.
Thank you,
José Carbonell
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.