erauser598 0 Posted June 23, 2020 Share Posted June 23, 2020 We are trying to upgrade our Management Center to the latest version. We have ESMC installed on a Windows Server 2019 VM with MS SQL Server 2019 Express. After the Security Management Center Components Upgrade task failed I attempted to upgrade manually with the All-in-One installer. In the logs it mentions not being able to connect to the database without mentioning which account it is using. Specifically: Its new value: 'ERROR: Database server does not support windows authentication'. Its current value is 'ERROR: Database server does not support windows authentication'. Its new value: 'INFO: (SetProperty) Successful SET property 'P_DB_CONNECTION_STATUS' with value - 77704'. MSI (s) (44:8C) [10:25:48:797]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIEFFC.tmp, Entrypoint: StopSetup MSI (s) (44!A4) [10:25:49:109]: PROPERTY CHANGE: Modifying P_LAST_LOG_MESSAGE property. Its current value is 'INFO: Custom action 'DbCheckConnection' ended.'. Its new value: 'INFO: Custom action 'StopSetup' successfully initialized.'. MSI (s) (44!A4) [10:25:49:109]: PROPERTY CHANGE: Modifying P_LAST_LOG_MESSAGE property. Its current value is 'INFO: Custom action 'StopSetup' successfully initialized.'. Its new value: 'INFO: Successful GET property 'P_FORCE_STOP_MSG' with value - Cannot login as DB admin. Error status: 77704'. MSI (s) (44!A4) [10:25:49:109]: PROPERTY CHANGE: Modifying P_LAST_LOG_MESSAGE property. Its current value is 'INFO: Successful GET property 'P_FORCE_STOP_MSG' with value - Cannot login as DB admin. Error status: 77704'. Its new value: 'ERROR: Cannot login as DB admin. Error status: 77704'. MSI (s) (44!A4) [10:25:49:109]: PROPERTY CHANGE: Modifying P_LAST_LOG_MESSAGE property. Its current value is 'ERROR: Cannot login as DB admin. Error status: 77704'. Its new value: 'INFO: Successful GET property 'P_FORCE_STOP_RETCODE' with value - '. MSI (s) (44!A4) [10:25:49:109]: PROPERTY CHANGE: Modifying P_LAST_LOG_MESSAGE property. Its current value is 'INFO: Successful GET property 'P_FORCE_STOP_RETCODE' with value - '. Its new value: 'INFO: Custom action 'StopSetup' ended.'. Action start 10:25:48: CA_StopSetup.CA_DbCheckConnection. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 384 Posted June 23, 2020 ESET Staff Share Posted June 23, 2020 Depending on upgrade method (not sure of upgrade via all-in-one installer), either standard DB credentials as used by ESMC Server will be used, or credentials provided to installer during upgrade - in case upgrade is performed silently, I would expect first variant, but in case upgrade is partially interactive and database parameters were requested, those parameters will be used. Is it possible that DB user normally used by ESMC service was created manually or modified after ESMC was deployed? It might mean that it is missing specific permissions required for upgrade. Link to comment Share on other sites More sharing options...
erauser598 0 Posted June 23, 2020 Author Share Posted June 23, 2020 I am currently using the All-in-One installer to attempt the upgrade. Where would I find or configure what account ESMC is using to communicate with the Database? I am the one who installed ESMC initially on this server and have not changed any settings of the installation. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 384 Posted June 23, 2020 ESET Staff Share Posted June 23, 2020 1 minute ago, erauser598 said: I am currently using the All-in-One installer to attempt the upgrade. Where would I find or configure what account ESMC is using to communicate with the Database? I am the one who installed ESMC initially on this server and have not changed any settings of the installation. Please check configuration file StartupConfiguration.ini which contains DB connection string (documentation with full paths) Link to comment Share on other sites More sharing options...
erauser598 0 Posted June 23, 2020 Author Share Posted June 23, 2020 In that file I found this (name replaced): DatabaseType=MSSQLOdbc DatabaseConnectionString=Driver={SQL Server Native Client 11.0};Server=$servername\$instancename;Database=era_db;Trusted_Connection=yes I do remember referencing this article, https://support.eset.com/en/kb6913-use-windows-authentication-for-connection-to-sql-server-database-in-eset-security-management-center, just after the installation was complete. There is no mention of the account. However the service account running the ESMC server does have read, write, and owner permission on the database. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 384 Posted June 24, 2020 ESET Staff Share Posted June 24, 2020 (edited) 8 hours ago, erauser598 said: In that file I found this (name replaced): DatabaseType=MSSQLOdbc DatabaseConnectionString=Driver={SQL Server Native Client 11.0};Server=$servername\$instancename;Database=era_db;Trusted_Connection=yes I do remember referencing this article, https://support.eset.com/en/kb6913-use-windows-authentication-for-connection-to-sql-server-database-in-eset-security-management-center, just after the installation was complete. There is no mention of the account. However the service account running the ESMC server does have read, write, and owner permission on the database. Actually Trusted_Connection=yes means that ESMC Service is using it's domain credentials. So I would recommend to check under which credentials is ESMC service running and that user should be used also for upgrade - I guess it is different one as ESMC should be using some kind of service account. Edited June 24, 2020 by MartinK Link to comment Share on other sites More sharing options...
erauser598 0 Posted June 24, 2020 Author Share Posted June 24, 2020 I have found the main issue. In the same article I reference in my previous post, it mentions that the ESMC installer must be run while MS SQL is in Mixed authentication mode. After I changed to Mixed auth mode from only Windows auth the installer moved forward. After dealing with some unique service issues, I was able to successfully upgrade the server to v7.2.1266.0. I will need to add changing the authentication mode to the upgrade process for the future. Thank you for your assistance. Link to comment Share on other sites More sharing options...
Recommended Posts