Autosys installation for 12.X is failing when installing against AWS SQL PAAS
Article ID: 392885
Updated On:
Products
Issue/Introduction
During the installation of Autosys Scheduler 12.x against AWS SQL PAAS, three different errors were seen:
Error 1:Database Validation-------------------Warning:[CAUAJM_W_114005] The following host(s) are unreachable:"<Hostname>-********************.<domain>.com"
Note: Connectivity to the database instance was validated from the new Autosys server.
Error 2:2025-04-01 13:54:45,587 [main] WARN com.ca.autosys.db.install.CreateMSSQLDatabaseService(129) - Autosys installation database not created correctly, kindly check logscom.microsoft.sqlserver.jdbc.SQLServerException: The server principal "<UserName>" is not able to access the database "master" under the current security context. ClientConnectionId:<ClientID>
Error 3:2025-04-02 12:00:22,736 [main] INFO com.ca.autosys.db.validation.MssqlDBValidator(311) - create login autosys with password='******' 2025-04-02 12:00:22,741 [main] ERROR com.ca.autosys.db.main.AutoSysDBConnection(499) - Error in query execution :com.microsoft.sqlserver.jdbc.SQLServerException: User does not have permission to perform this action. 2025-04-02 12:00:22,742 [main] ERROR com.ca.autosys.db.validation.MssqlDBValidator(321) - Error in creating login. com.microsoft.sqlserver.jdbc.SQLServerException: User does not have permission to perform this action.
Environment
Autosys 12.x
Linux RHEL 9
AWS SQL PAAS
Cause
User permissions on the SQL PAAS Instance
Resolution
Solution for Error 1:
The install tries to do a ping to the database. If this is blocked, this error will be seen.
Setting the variable below will allow this to be bypassed.
export IA_AE_SKIP_DB_CHECK=1
Solution for Error 2:
The user being used in the installation instead of SA must have FULL admin rights.
To resolve this error, read and write permissions were granted to the user for the master database.
Solution for Error 3:
The user being used in the installation instead of SA must have FULL admin rights.
add the "loginmanager ADD MEMBER" applied to db user.
Additional Information
The AutoSys installer connects to the master database to verify certain things like the Server Edition, Server Version, existence of the Database, existence of the user etc.
Even though the DBA has created the Database Application User ahead of AutoSys installation, the Database Admin user has to connect to the master database to perform the other checks.
When the Database Admin user is trying to check if the Database Application User exists, the query fails as the Admin user lacks permission to the master database.
As the query failed, the installer assumes the user does not exist and tries to create the Application User again. Which eventually fails with permission issues again.
The Database Admin user must have privileges to the master database.
This is needed only during the Installation/Upgrade.
In the installation process, it will create the Application user and add the necessary roles to it, so admin privileges are required to complete this must be present.
Once the installation is complete, the privileges of the Admin user can be revoked, but will be required for upgrades.
Feedback
