BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
alexal
SAS Employee

@nhvdwalt,

 

That's a problem. When has this file been modified? Do you have any backup copies of this file?

alexal
SAS Employee

@nhvdwalt,

 

The COMMON key in registry.xml must have the following value:

 

<Value data="<USER_NAME>" name="install_user"/>
nhvdwalt
Barite | Level 11

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.

nhvdwalt
Barite | Level 11

Thank you @alexal @Kurt_Bremser @Anand_V @JuanS_OCS

 

Awesome to be part of this community.... 🙂

Kurt_Bremser
Super User

@nhvdwalt wrote:

Thanks @alexal, no need. Below is the entire file.....

 

 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<Registry version="3"/>

 

 


Ouch. That file is > 200K on my server.

alexal
SAS Employee

Yeah, you have to restore registry.xml from a backup.

nhvdwalt
Barite | Level 11

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.

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

CLI in SAS Viya

Learn how to install the SAS Viya CLI and a few commands you may find useful in this video by SAS’ Darrell Barton.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 22 replies
  • 2159 views
  • 12 likes
  • 5 in conversation