Event ID - 7000

Event Id	7000
Source	Service Control Manager
Description	Description 1: The service failed to start due to the following error: Description 2. The Protected Storage service failed to start due to the following error:The system cannot find the path specified. Description 3. The Certificate Authority service depends on the Protected Storage service which failed to start because of the following error:The system cannot find the path specified. Description 4. The IIS Admin Service depends on the Protected Storage service which failed to start because of the following error: The system cannot find the path specified.
Event Information	According to Microsoft : Cause : Service Control Manager (SCM) could not start the specified service, probably because the service is not configured correctly. Resolution : Do one or all of the following: Review the error information displayed in the message. Verify that the service password has not expired. Verify that the service is in the correct location. Verify that the service is not infected with a virus. To display the WIN32_EXIT_CODE error that SCM encountered when trying to start the program, at the command prompt, type sc query service name The information displayed can help you troubleshoot possible causes for the error. If the WIN32_EXIT_CODE is zero, then SCM did not attempt to start the service because the error was detected first. Cause 1: This behavior can occur if you configure the service to log on to a user account, and any of the following conditions are true: The right to log on as a service is revoked for the specified user account. The password is changed on the user account that the service uses to log on. The password data in the registry is damaged. Resolution : Method 1: Configure User Rights If the right to log on as a service is revoked for the specified user account, restore the right by using either of the following methods, as appropriate to your situation. On a Domain Controller If the user is in an Active Directory domain, follow these steps: Log on to the domain controller as administrator. Start the Active Directory Users and Computers snap-in. Right-click the organizational unit (OU) in which the user right to log on as a service is granted, and then click Properties . By default, this is in the Domain Controllers OU. Click the Group Policy tab. Click Default Domain Controllers Policy , and then click Edit . Expand Computer Configuration , expand Windows Settings , and then expand Security Settings . Expand Local Policies , and then click User Rights Assignment . In the right pane, right-click Log on as a service , and then click Security . Add the user that you want to the policy, and then click OK . Quit the Group Policy Editor, click OK, and then close the Active Directory Users and Computers snap-in. On a Local Computer If the user is on a stand-alone Windows XP-based computer, follow these steps: Log on to the computer as administrator or as a member of the Administrators group. Start the Local Computer Policy snap-in. Expand Local Computer Policy , expand Computer Configuration , expand Windows Settings , and then expand Security Settings . Expand Local Policies , and then click User Rights Assignment. In the right pane, right-click Log on as a service , and then click Properties. Click Add User or Group, add the user that you want to the policy, and then click OK twice. Close the Local Computer Policy snap-in. Method 2: Configure Logon Information for the Service If the password is changed on the user account that the service uses to log on, configure the password to match the current password for that user. To do this, follow these steps: Click Start , click Control Panel , click Performance and Maintenance , and then click Administrative Tools . Double-click Services . In the right pane, right-click the appropriate service, and then click Properties . Click the Log On tab, type the correct password in the Password and Confirm Password boxes, and then click OK. Right-click the service, and then click Restart . Quit the Services tool. ------------------------------------------------------------------------------------------------------------------ According to Microsoft: CAUSE 1: The Protected Storage service registry key is missing from the registry. Before proceeding with the workaround, verify that the Protected Storage service registry key is missing. The ProtectedStorage service registry key is located at the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services RESOLUTION: To resolve this issue, register the Protected Storage service to the Windows NT Registry by performing the following steps: 1.Type the following command at a command prompt: %SystemRoot%\System32\Pstores.exe -install 2. Close all programs and restart the computer. This same command can be used to remove the Protected Storage keys. If you run this command and the registry key is there, it may remove it along with all of the other Protected Storage keys. Cause 2: This error event will be logged for every failed service startup. The causes for the services failure to startup could be numerous and can be identified from other related events that have occurred. "Event message: mrtrate service failed to start due to the following error: Suggested Solutions: 1. I may have isolated the problem, by seeing the message that a service called mrtrate service failed to start due to the following error: The system cannot find the file specified. Then, I went out and did a search for this condition; it was apparently related to Quicken 2004 Deluxe which Ive been running for some time. There was a fix to change a value in the registry for it after backing it up which I did. Then, I rebooted and the error did not reoccur." 2." Error: "The system cannot find the file specified." - Windows is trying to start the "mrtRate" service at boottime. I got this error after installing Quicken XG (Canadian Version of Quicken 2003). Get rid of the error by disabling Quickens Background Downloading Driver (you can always do manual. Cause 2: Service Control Manager (SCM) could not start the specified service, probably because the service is not configured correctly. Resolution: Do one or all of the following: 1.Review the error information displayed in the message. 2.Verify that the service password has not expired. 3.Verify that the service is in the correct location. 4.Verify that the service is not infected with a virus. 5.To display the WIN32_EXIT_CODE error that SCM encountered when trying to start the program, at the command prompt, typesc query service name The information displayed can help you troubleshoot possible causes for the error. If the WIN32_EXIT_CODE is zero, then SCM did not attempt to start the service because the error was detected first.
Reference Links	Protected Storage Failed to Start Event ID 7000: %1 Not A Valid Windows NT Application Event ID 7000 - file is corrupt or missing or LFN is not quoted System event log has ID 7009 and ID 7000 After you redirect the Documents and Settings folder, you receive System event 7000 and 7009 Added SMTP Service Fails after IIS 4.0 Is Installed on Non-Default Path Err Msg: Event ID 7000: Spooler Service Failed to Start... IBM 16/4 Auto Token Ring Adapter Driver Causes Event ID 7000 Event ID 7000: RDR Service Failed to Start Compex PNP NE2000 Compitable NIC May Cause Event ID 7000 Cluster Service Does Not Start with Event ID 7000: Not Responding to Control Function "Event ID: 7000" Error Mess Event Id:7000 Source Id:Service Control Manager

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught