December 1, 2017 at 2:34 am
We have made various attempts to update two of our SQL Server 2014 instances, but the update errors on every attempt with the following message (even with full administrator privileges):
"Error installing SQL Server Common Files
This installation is forbidden by system policy. Contact your system administrator.
Error code: 1625"
We are trying to update the builds below to Service Pack 2 CU7 - build 12.0.5556.0 (KB 4037356). Previous attempts to update to SP1 a few months back resulted in the same error.
Current Builds
Microsoft SQL Server 2014 (SP1-GDR) (KB4019091) - 12.0.4237.0 (X64)
Jul 5 2017 22:03:42
Copyright (c) Microsoft Corporation
Web Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
Microsoft SQL Server 2014 - 12.0.4100.1 (X64)
Apr 20 2015 17:29:27
Copyright (c) Microsoft Corporation
Web Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
We have attempted installs with "DisableMSIpolicy" in the registry set to 0 (“Windows Installer is enabled for all applications. All install operations are allowed.”), full admin privileges, temporarily de-activated antivirus, checked the domain group policy settings, etc. but nothing seems to help.
Can anyone please advise how we can update these instances?
December 1, 2017 at 5:38 am
Hi,
did you start the exe updatefile with "run as administrator", or just with an account with administrator rights?
Kind regards,
Andreas
December 1, 2017 at 7:46 am
We've tried both.
Here are some more things we've tried:
- Modified local security policies
- Modified Domain GP for admin accounts
- Used a domain admin account
- Use the local administrator account
- Use RSOP to show whether the domain policy and the local policy is in effect for software installations (showed the domain policy was in precedence)
When the update failed – Windows thought it was installed and it appeared as an installed patch even though it wasn’t there and had rolled back anything it had done.
We always removed the “apparently” installed service pack from “programs and features” before re-trying.
We checked the domain policies against another domains policies (where the service pack did update) and they appear to be the same.
The only success we had was removing the server (a restored VM copy) from the domain.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply