\n
![\"sma_installation_failed\"](\"https:\/\/p0wershell.com\/wp-content\/uploads\/2014\/12\/sma_installation_failed.png\")
<\/a><\/p>\nNot sure if this matters, but in my case, the database is hosted in a SQL AlwaysOn Availability Group on a non-default port (not 1433), and we are using “Windows Authentication”, or a “trusted” connection to log into the database.<\/p>\n
After investigating this issue and looking at the network communication I realized that the installation actually tries to validate the connection on the database-settings page, but when it’s finally time to start the installation, it just fails right away. Also, I found that the connection at the “verify sql settings”-step is established via a service (svchost.exe or CcmExec.exe), which could explain why this workaround actually works (it’s probably using the same component in the OS).<\/p>\n
I finally found a workaround for this issue though, which is pretty weird, but it got me through the installations of all my runbook workers and web services so I thought I’d share it if anyone else is experiencing this issue.<\/p>\n
Workaround using temporary ODBC-connection<\/strong> Fill in all the settings in the SMA Runbook Worker-wizard but do not<\/em> click “Install” at the last page.<\/p>\n Instead, start the “ODBC Data Sources (64-bit)” (%windir%\\system32\\odbcad32.exe) using the same account as your installation wizard is running with and click “Add…”, see below: Then click “Finish”: Fill in the details of your database for SMA (the first two fields can be anything): Fill in the name of your sql server, click next, and choose “Client Configuration” if you are using a non-default port and fill in the one you are using: Click next, and choose to change default database to master (not 100% sure this is needed, but a thread @technet suggested this), like this:
\nWe will not actually create the connection, just fill in enough information to be able to do a test.<\/p>\n
\n<\/a><\/p>\n
\n<\/a><\/p>\n
\n<\/a><\/p>\n
\n<\/a><\/p>\n
\n<\/a><\/p>\n