Error message when you try to install a SQL Server 2008/2008 R2 SP3: “The NT service 'MSSQLSERVER' could not be started

Issue - We encountered an issue while working on a SQL 2008 R2 SP3 Installation. While running SP43 setup files suddenly a window populated with message.

Error Message – “SQL Server has encountered the following error: The NT Service: MSSQLSERVER could not be started, error code 0x884B20001”




Troubleshooting done –
1.     Some blogs were suggesting, it’s a permission issue, immediately we logged in to the server with different admin account and tried to install SP3 but it threw the same error.
2.     When we checked the “installed updates” under “programs and features”, we found that SP3 got installed. We tried to remove installed components of service pack 3 but again it was giving “Access Denied” error.
3.     We tried to repair SQL instance but again we came across “Access Denied” error.
4.     We checked the summary.txt (C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log) and observed following logs:

Final result:  The patch installer has failed to update the following instance:. To determine the reason for failure, review the log files.
Exit code (Decimal):   -2068709375
Exit facility code:        1202
Exit error code:          1
Exit message:            The NT service 'MSSQL' could not be started.
Requested action:       Patch

Additionally, observed below error message in the Details log placed at (C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\Instancenamefolder\Details.txt

Slp: The following NT service was in a stopped state prior to patch action: SQLServer
Slp: Sco: Attempting to open SC Manager
Slp: Attempting to run patch request for instance: Instancename
Slp: Error: Failed to run patch request for instance: SQLinstance (exit code: -2068709375)

Above logs clearly says while patching installer not able to start and stop the NT services, which seems to be issue with the permissions of the account running the upgrade. While checking the permissions and goggling we found that account used for patching should have administrative rights on SQL and Windows server including below permissions in local policies listed below.

Backup files and directories (SeBackupPrivilege)
Debug Programs (SeDebugPrivilege)
Manage auditing and security log (SeSecurityPrivilege)
Local policies can be accessed from below path
Control Panel--> Administrative Tools --> Local Security -->Settings --> Local Policies --> User Rights Assignment

Resolution - Immediately, we checked Group policies being applied on this server and found that our patching account does not have rights on these above polices i.e. causing issues while for NT services start/stop.

To resolve this we moved this affected server in proper OU where administrators are being added to these above group policies, we rebooted the server and re-initiate the installation and it completed successfully this time. 

Comments

Post a Comment

Popular posts from this blog

Enterprise CA option is greyed out / unavailable

Many times, when installing Active Directory Certificate Services they cannot choose to install Enterprise Certification Authority, because it’s unavailable as in following picture: Well, you need to fulfill basic requirements: Server machine has to be a member server (domain joined). You can run an Enterprise CA on the Standard, Enterprise, or Data Center Windows Edition. The difference is the number of ADCS features and components that can be enabled. To get full functionality, you need to run on Enterprise or Data Center Windows Server 2008 /12/R2/ Editions.  In order to install an Enterprise CA, you must be a member of either Enterprise Admins or Domain Admins in the forest root domain (either directly or through a group nesting). If issue still persists, there is probably a problem with getting correct credentials of your account. There are many thing that can cause it (network blockage, domain settings, server configuration, and other issues). In al...
Read more

Rearm the Office 2013 installation

Image
There is a 25-day grace period from the time of installation of Key Management Service (KMS) clients before notifications to activate are displayed to the user. If you want to deploy an image, you must rearm your Office 2013 installation before you capture the image. If you do not rearm, users see notification dialog boxes at the time that the image is deployed, instead of 25 days after deployment. The 25-day grace period gives ample time for a KMS host to be found and activation to succeed. If activation is successful, users do not see notifications to activate. Rearm the Office installation Rearming does the following important tasks: Resets the grace timer to 30 days. Freezes the grace timer until either an Office application is run, or the ospp.vbs script is run. Resets the client computer ID (CMID). This is important because the KMS host uses the CMID to determine the num...
Read more

MP has rejected registration request due to failure in client certificate

Image
Issue:- We have System Center Configuration Manager 2012 R2 deployed on Windows Server 2008R2 host. Recently we have moved our Certification Authority to Windows Server 2012 , renewed Root CA Certificate and intermediate Certificates also migrated Hashing algorithm from 'sha1' to 'sha2'  . New Root CA and intermediate CA also present on client machines and on SCCM. However, i have discovered these errors on MP: MP has rejected registration request due to failure in client certificate (Subject Name: ) chain validation. If this is a valid client ,  Even though Newly imaged machines are getting SCCM client installed but won't see all the client cycle under 'Actions tab' and also  'client certificate shows "None".  The operating system reported error 2148204809: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.  Solution:- Register  new Certificate of Root CA    under SCCM20...
Read more