So, just to conclude this one....   Turns out, there are no backups available for this server. Using proc product_status I then found a server with the same software installed, then just used the *.xml files from that server. SDM then came up no problem.   Thanks again for the help. ... View more

Thank you @alexal @Kurt_Bremser @AnandVyas @JuanS_OCS   Awesome to be part of this community.... 🙂 ... View more

Bingo !!   Extract from a working server...   <Value data="9.4" name="major_releases"/> <Value data="user123" name="install_user"/> <Value data="en_ZA" name="sashome.locale.name"/>   ...actual admin user replaced with user123.   Thanks @alexal, will look for a backup. ... View more

Thanks @alexal, no need. Below is the entire file.....     <?xml version="1.0" encoding="UTF-8" standalone="no"?> <Registry version="3"/>     ... View more

@Kurt_Bremser....No way, that's a cool trick 🙂   It returned those files....elssrv, sasauth and sasperm as you mentioned. So confirmed, all files belong to the admin user as expected. ... View more

Thanks @Kurt_Bremser, belongs to the user I'm running with. ... View more

Thanks @AnandVyas, id command yields the same UID across all 6 hosts. ... View more

Hi team,   Thanks for the replies.   @JuanS_OCS, thanks for the tip on loglevel 2. Unfortuantely it didn't give any more useful info.   I agree it might be a user id mismatch, but I need to prove the theory. There are only three possible userids and I've tried them all, no difference.   Now, I not saying it is, but......   We have six servers. On 4 out of the 6, the hotfix was ok, on the 2 others, $SASHOME/deploymntreg/registry.xml is practically empty whereas on the other 4 servers there is plenty of info in the file. There are also a couple of registry.* files on the working servers that are missing on the faulty ones.   Unfortunatly the system is up at the moment, else I would have copied the files across to at least test the theory....   Throughts ? ... View more