#191 - AVEVA System Platform How to open a new Galaxy

 - How to open a new Galaxy: Copy and paste the .cab file into this folder:

 - Close and open AVEVA System Platform in order to update the templates catalogue:

- Name the Galaxy (without spaces) and login

- Note that it may be required to download SQL Server Management Studio and configure the login with the user and password. Enable SQL Server and Windows Authentication:

Enable user: sa, password: Password#1 Ensure role sysadmin is selected:

Ensure the user sa connects to the DB.

Restart the Service: SQL Server (MSSQLSERVER)

Login to the Galaxy with sa username and password.

------

Check groups and users levels:

Troubleshooting when (attention to windows updates): StartMSSQLServer::StartService() - Access is denied., ArchstraUser does not have required permissions Sql service could not be started

- In SQL Server Management Studio, in the Properties > Security, we changed Server authentication to be ‘SQL Server and Windows Authentication mode’ - In Local Security Policy, we added the ArchestrA Network account ‘user’ into ‘Act as part of the operating system’ and ‘Allow log on locally’ - We ran the Change Network Account utility under the username ‘user’ and restarted the machine - We went into SQL Server Management Studio, in Logins, enabled the ‘sa’ account and used the same password - We selected Logins > New Login and added ‘user’ into here, with sysadmin role. We then restarted SQLSERVER service. - We ran the SQL Access Configurator (aaConfig SQL) in Legacy Mode, using ‘user’ and restarted the machine The issue was not resolved still - We went into Computer Management, then in the local Administrators group, added ‘user’ into here. - We made the user ASBServices a member of the local Administrators group and the aaAdministrators group. - We signed out of the machine and signed back in - We created a new Galaxy and were able to connect to this and open this successfully. - We opened our original Galaxy and now this opened successfully.

- Try to Deploy the Galaxy. In case of some strange errors, such as "Object doesn't exist or is in bad state", or "WWPackageServer Error: Failed to deploy 0x80040154", try to repair the ASP installation by launching the installation file again.

- Check the login in the "SQL Access Configurator"

- When it Opens it may ask if we want to migrate to the current version. Note that a version migrated like this one below can take a couple of hours.