SQL Server 2016 Install - VS Shell Installation Failure

Question

SQL Server 2016 Install - VS Shell Installation Failure

hawg

SSCertifiable

Points: 6039
More actions
June 2, 2016 at 10:14 am

#310921

I was running through the install with the final release of SQL Server 2016 and during the "Installation Progress" portion, I get an error message that pops up stating:
"VS Shell installation has failed with exit code 5"
Can anyone tell me what is happening here? I can find this error with other exit codes but I can't seem to find anything with this exit code so I'm not even sure where to go next.
----------------------------------------------------------
01010011010100010100110000100000010100110110010101110010011101100110010101110010
001000000101001001101111011000110110101101110011

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

hawg SSCertifiable Points: 6039 More actions · Answer 1

Here is an update on what the issue was for me. Exit code 5 is an "access denied" code. The problem had to do with UAC settings on my server.

For installation, and configuration purposes, the account I was using to install SQL Server was part of the Local Administrator group on the server. Even with that, I had to go into Local Group Policy Editor -> Windows Settings -> Security Settings -> Security Options and ENABLE the option called User Account Control: Admin Approval Mode for the Built-in Administrator Account.

I didn't have to restart the server. I just made the change then re-ran the install and it worked.

Hope this helps.

----------------------------------------------------------

01010011010100010100110000100000010100110110010101110010011101100110010101110010
001000000101001001101111011000110110101101110011

paultormey Mr or Mrs. 500 Points: 569 More actions · Answer 2

You did mean:

Local Group Policy Editor -> Windows Settings -> Security Settings -> Local Policies -> Security Options...

Cheers

Br. Kenneth Igiri SSCarpal Tunnel Points: 4759 More actions · Answer 3

hawg (6/2/2016)
Here is an update on what the issue was for me. Exit code 5 is an "access denied" code. The problem had to do with UAC settings on my server.
For installation, and configuration purposes, the account I was using to install SQL Server was part of the Local Administrator group on the server. Even with that, I had to go into Local Group Policy Editor -> Windows Settings -> Security Settings -> Security Options and ENABLE the option called User Account Control: Admin Approval Mode for the Built-in Administrator Account.
I didn't have to restart the server. I just made the change then re-ran the install and it worked.
Hope this helps.

This solution seems not to have worked for me. Do you mind sharing additional details? Did you perform your installation with the inbuilt administrator?

Br. Kenneth Igiri
https://kennethigiri.com
All nations come to my light, all kings to the brightness of my rising

Br. Kenneth Igiri SSCarpal Tunnel Points: 4759 More actions · Answer 4

Br. Kenneth Igiri (7/19/2016)
hawg (6/2/2016)
Here is an update on what the issue was for me. Exit code 5 is an "access denied" code. The problem had to do with UAC settings on my server.
For installation, and configuration purposes, the account I was using to install SQL Server was part of the Local Administrator group on the server. Even with that, I had to go into Local Group Policy Editor -> Windows Settings -> Security Settings -> Security Options and ENABLE the option called User Account Control: Admin Approval Mode for the Built-in Administrator Account.
I didn't have to restart the server. I just made the change then re-ran the install and it worked.
Hope this helps.
This solution seems not to have worked for me. Do you mind sharing additional details? Did you perform your installation with the inbuilt administrator?

In my case it was the antivirus blocking the operation. Did not realise earlier that we had it configured on this server

Br. Kenneth Igiri
https://kennethigiri.com
All nations come to my light, all kings to the brightness of my rising

Jamie-2229 SSCrazy Eights Points: 8156 More actions · Answer 5

Is it possible that this error occurs when SSMS 2016 is installed before SQL 2016? I only had trouble with this error when the SSMS 2016 was installed, but not if I installed SQL 2016 first and then installed SSMS 2016
Also of note, the log on as service must be configured for the NT SERVICE\SSISTELEMETRY130 account

Jamie