Log Name: Security

Source: Microsoft-Windows-Security-Auditing

Date: 2/10/2011 4:28:02 PM

Event ID: 5061

Task Category: System Integrity

Level: Information

Keywords: Audit Success

User: N/A

Computer: AbdulRehman

Description:

Cryptographic operation.

Subject:

Security ID:LOCAL SERVICE

Account Name:LOCAL SERVICE

Account Domain:NT AUTHORITY

Logon ID:0x3e5

Cryptographic Parameters:

Provider Name:Microsoft Software Key Storage Provider

Algorithm Name:RSA

Key Name:Microsoft SQL Server$MSSQLSERVER$FallBackCert

Key Type:User key.

Cryptographic Operation:

Operation:Open Key.

Return Code:0x0

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />

<EventID>5061</EventID>

<Version>0</Version>

<Level>0</Level>

<Task>12290</Task>

<Opcode>0</Opcode>

<Keywords>0x8020000000000000</Keywords>

<TimeCreated SystemTime="2011-02-10T13:28:02.021710900Z" />

<EventRecordID>5127</EventRecordID>

<Correlation />

<Execution ProcessID="720" ThreadID="756" />

<Channel>Security</Channel>

<Computer>AbdulRehman</Computer>

<Security />

</System>

<EventData>

<Data Name="SubjectUserSid">S-1-5-19</Data>

<Data Name="SubjectUserName">LOCAL SERVICE</Data>

<Data Name="SubjectDomainName">NT AUTHORITY</Data>

<Data Name="SubjectLogonId">0x3e5</Data>

<Data Name="ProviderName">Microsoft Software Key Storage Provider</Data>

<Data Name="AlgorithmName">RSA</Data>

<Data Name="KeyName">Microsoft SQL Server$MSSQLSERVER$FallBackCert</Data>

<Data Name="KeyType">%%2500</Data>

<Data Name="Operation">%%2480</Data>

<Data Name="ReturnCode">0x0</Data>

</EventData>

</Event>

quote]Shawn Melton (2/10/2011)

---

Well you may not actually see any error in the SQL ERRORLOG file but default location is:

C:\Program Files\Microsoft SQL Server\MSSQ.1\MSSQL\LOG.

I would actually first look in your Windows Event Log (Start > Run > eventvwr). The Application and/or System Log should also tell you why it did not start, or what issue it is caught on.

Is the service set to run as a system account (Local System, or system account like NT AUTHORITY\SYSTEM) or a local/domain account? This can effect permissions if it is running as a customized account, depending on how it was setup.

If it is a local account within the properties of the service (using SQL Server Service Manager) re-enter the usrename and password. This will attempt to give it the correct permissions it requires.[/quote]