SM:RCD_CHECK_UPDATES_TEST Completed with error log Maintain S-User logon information

[Former Member]

Dear All,

While Configuring RCD for solution Manager 7.2, Job SM:RCD_CHECK_UPDATES completes with below error log.

• Job started Step 001 started (program RCSU_AUTO_NOTIFY_AND_DWLD, variant , user ID SOLMAN_BTC) Job SM:RCD_CHECK_UPDATES started Maintain S-User logon information in Solution Manager Configuration Error while downloading delivery 6: Error Text - Maintain S-User logon information in Solution Manager Configuration Maintain S-User logon information in Solution Manager Configuration Error while downloading delivery 7: Error Text - Maintain S-User logon information in Solution Manager Configuration Maintain S-User logon information in Solution Manager Configuration Error while downloading delivery 12: Error Text - Maintain S-User logon information in Solution Manager Configuration Maintain S-User logon information in Solution Manager Configuration Error while downloading delivery 5: Error Text - Maintain S-User logon information in Solution Manager Configuration Job finished

We already maintained S-user on System Preparation step, and also followed RCD configuration step with respect to Solution manager 7.2.

Is some one facing same issue, please do let me know if i am missing something.

Thank you

Regards,
Veekshith Shetty

[RiccardoEscher]

Hi, I have the same problem and trying to solve it I experience a typical SAP documentation chain 😞

You have to go to Basic Configuration, step 3 "Configure manually", here you find the step Configuration for Rapid Content Delivery, here you find in the documentation the configuration of the Netweaver Download Services, her you find a mention of note 2433483, which is rather empty, it contains only a link to a document "Overview of Rapid Content Delivery in SAP Solution Manager 7.2 SP05" which cannot be downloaded but only printed (I will use a pdf creator). I hope that this document will tell me which sapservice user has to be added to the zoo of already existing users managed by setup step "System Preparation" 3 Setup connection to SAP

[RiccardoEscher]

Oh, yes! And in this document there is a reference on help.sap.com, and after 10 Minutes you finally may have reached the needed infos:
https://help.sap.com/viewer/9d6aa238582042678952ab3b4aa5cc71/7.4.18/en-US/7cd5bc1666824b3eba96e8a79d...

[RiccardoEscher]

After half an hour of configuration (transaction SDS_CONFIGURATION & STRUST) I have now a new error message for which I found note 2548049 - "Job SM:RCD_CHECK_UPDATES cancels with error ....does not match the supported patterns" which tells to apply the correction of note 2456654 and also that many steps I did before were useless, that I have import the root certificate of GeoTrust Global CA 😞

Ok, I implemented the correction. The error message is gone away.

Ha ha ha HA!

Now the import job terminates with a new error message! I find note 2579229 - "Background job SM:RCD_CHECK_UPDATES/xxxxxxxx is currently running" which points to note 2577104. OK, let us repeat the change process (it would have been too easy to implement all error corrections in one step!)

This time the download starts, but the job ends with a short dump UNCAUGHT_EXCEPTION CX_SDS_FILE_ERROR. Reason seems that I didn't notice that we have a special file directory setup, and the funny download report does not notice this until it tries to open the file.

I have edited with FILE the right path and finally, after 2 hours of Mario jump&run the download succeeded!

[darrylmg]

For anyone hitting this same issue as described by Riccardo above, his solution (and mine), was to ensure that both logical paths match the same location: DOWNLOAD_SERVICE_PATH and CSU_DOWNLOAD_SERVICE

as defined in transaction FILE.

Good luck and I hope it saves you hours!

[jan_j_novak]

Hi,

not sure if someone here still has the same issue, but here is my solution for this error on Solman 7.2 SP08:

In SDS_CONFIGURATION switch your S-User with Technical Communication User.

After I have done that, RCD works again.

Jan

[Frank_KLR]

Hi,

Thank you Jan.

What you need to do is just to update the password of the technical communication users filled in the transaction SDS_CONFIGURATION.

Frank

[Diggeshhjoshi]

I have the same issue. Did you find any solution?