Can't Reset Super User Password

[MikeSI]

Hi All,

I have inherited a Hot-Standby redundant Geo SCADA server pair running version 2021 (August 2022 update).

Both servers supposedly have a super user account but the login doesn't work. The password can not be obtained.

I have tried following the procedure in: https://www.se.com/au/en/faqs/FAQ000244794/ 

to reset the SU password but it hasn't worked. I have tried it on each server separately, plus both servers together.

Normally I would say it's not an issue because an Admin account is available, but in this case the User  and User Group objects in the database are hidden from everyone except the SU. Don't ask me why - I can't see any reason to do this.

This means I can't add users to a group and I can't change passwords for existing users because even as Admin I can't see any of them in the DB tree.

Has anyone else had issues with resetting the SU password? Am I missing a step?

[tfranklin]

If you've stepped through the steps in the link, I'd expect it to work as well.  I've never personally had this issue.  Are you logging in locally to the local DB? Keep in mind SU only works when you're RDP'd in to the server in question.  Outside of that, I can't recall if changing SU requires a restart of the DB, but maybe that's the next thing to check. 

[geoffpatton]

On each server you can run the installer again, select Modify the installation, and select Change super user.

[geoffpatton]

LOL it would help if I looked at the link you shared first before posting.

You could try uninstalling and reinstalling I have had to do that for some license server service problems before.

Another alternative, if you know your system well enough and know that doing this will not affect any of your processes, you can install Geo SCADA on a computer and set a super user on it. Copy the folders and files from one of the servers' Database folder over to this computer and edit the database to give your admin users permissions on everything. then copy the config folder back. You don't want to copy the history folders or Event Journal folders. You would have to stop both servers while you copy the Config folder back to a server and start and if it is successful then start the other server. other wise stop the server and then start the one you did not update and then start the one you changed and it will retrieve to or files from the running server.

[sbeadle]

In answer to Trent's query, you do need to restart Geo SCADA after changing the SU password.

Don't forget to make a 'real' user the admin and then disable the SU password in the Server Config tool. (The Server Status tool has a warning to encourage you to do this).

Other notes - you can't transfer the SU user/password settings to another server by copying the registry.

[MikeSI]

Apologies everyone for such a late reply and thanks for all the responses, I'm away on annual leave and haven't tried to reset the SU again.

It does sound like I've been doing the right thing so a bit of a mystery.

I RDP to the server, shutdown GeoSCADA and run the installer, select modify, and tick 'reset SU' and follow the prompts. Everything appears to work except when I go to login and username/pwd is not recognised.

It will probably be atleast another week until I have a chance to try again.

[AdamWoodlandToo]

If it were me I would:

1. Shutdown the Geo SCADA service on the target server
2. Delete the Reg key at HKEY_LOCAL_MACHINE\SOFTWARE\Schneider Electric\ClearSCADA\DB\WebSSLHash (export the key first or copy the text as necessary)
3. Run the installer again as you did above and tick the Reset Super User box, enter the details and allow it to complete
4. Verify in Regedit that the WebSSLHash value is back and has a load of text in (if not then the installer didn't do its job, not aware of anything that would do this but let's double check the installer bit worked)
5. Create a new system in Configure Connections that only connects to 127.0.0.1
6. Start the Geo SCADA server on that server and run ViewX
7. Try to log into that newly created system only (no other system) as the superuser

That should hopefully let you in as it should mean you've verified that new superuser details have been written to the Registry and you're only connecting to the local server (as the superuser won't work over the network).