SLD s/w version incorrect after patch rollback, how to resynchronise?

[alison_holden]

After encountering a problem applying SP25 to our XI 3.0 java stack the patches were removed. In the meanwhile the SLD auto update occured and now the SLD technical system shows the wrong version and is causing issues. Triggering an update via visual administrator SLD data supplier service does not fix the issue

Does anyone know how to force an update with the s/w version and patch stack details for the J2EE core components (SAP-JEECOR, SAP-JTECH, SAP-JEE)

thanks

Alison

[stuart_campbell]

Hi Alison

You may also be able to re-import a back-up of the SLD contents taken before the SP25 update (if you have one) - however bear in mind you may lose all changes between now and when the back-up was taken

Best wishes

Stuart

[stuart_campbell]

Hi Alison

Assuming you have rolled back - the next update from (manually or automatic) from the SLD Data Supplier service should update

the latest data supplier information to the SLD - even if this is a previous SP version

If this is not happening then perhaps there is a problem with the SLD Data Supplier service - check user defined is not locked and is in validity date similiarly check the password is correct and not recently changed and check the user rights are correct for Data Supplier user

At the same time one other possibility is that the original update of SP25 information or the creation of the system itself was done by another data source - i.e via SLD sync (from another SLD) or manually added in which case no manual or automatic update may work - in these cases customers need to continue the same import line - i.e if data supplier information was added by a sync only a subsequent sync can update, if manually added then the system must be manually updated in future

Best wishes

Stuart