VMware Cloud Community
Fwa
Enthusiast
Enthusiast
Jump to solution

Installation regarding MSSQL fails

During installing IaaS server automatically, I had error related to MSSQL as follows:

pastedImage_19.png

And therefore, I confirmed C:\Program Files (x86)\VMware\vCAC\InstallLogs\Server-Setup.log.

MSI (s) (84:FC) [20:02:17:040]: Note: 1: 2203 2: C:\Windows\system32\config\systemprofile\AppData\Local\Downloaded Installations\{XXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}\VMware vCloud Automation Center Server.msi 3: -2147287037

MSI (s) (84:FC) [20:02:17:072]: MainEngineThread is returning 3

MSI (s) (84:DC) [20:02:17:118]: User policy value 'DisableRollback' is 0

MSI (s) (84:DC) [20:02:17:149]: Machine policy value 'DisableRollback' is 0

MSI (s) (84:DC) [20:02:17:165]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (84:DC) [20:02:17:181]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

MSI (s) (84:DC) [20:02:17:196]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

MSI (s) (84:DC) [20:02:17:227]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

MSI (c) (20:BC) [20:02:17:290]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

MSI (c) (20:BC) [20:02:17:321]: MainEngineThread is returning 3 

What is the cause of this problem?

Tags (1)
1 Solution

Accepted Solutions
Fwa
Enthusiast
Enthusiast
Jump to solution

Hi scoch,

The MSDTC was properly configured on MSSQL. The right to create MSSQL seemed to be cause and this was solved. Thank you.

Regards

View solution in original post

2 Replies
skoch
Enthusiast
Enthusiast
Jump to solution

Do you have MSDTC configured properly on the MSSQL server? I believe this error can occur if that isn't configured properly.

Fwa
Enthusiast
Enthusiast
Jump to solution

Hi scoch,

The MSDTC was properly configured on MSSQL. The right to create MSSQL seemed to be cause and this was solved. Thank you.

Regards