Secure Store Application Error 8306

Dec 22, 2011 at 2:02 PM

After using the AutoSPInstaller to install SharePoint, I am getting the Error 8306 in the event viewer so many times, that a new error shows up 2159 stating another has been replicating too often.

When this occurs, Sharepoint will not start.  Trying to get to the CA, returns a 503 error in the browser.  When I do start the application pool in IIS, it will start, but as soon as open CA, it stops again.

Reading thru posts has not helped fix this problem.  In the installer, I have the windows token service set to true.

Ideas?

Dec 22, 2011 at 2:19 PM
Edited Dec 22, 2011 at 2:37 PM

I have experienced similar situation when I had a client that has a very strict  group policy. It turned out to be an IIS issue.

You may like to read this section "Windows user rights that are assigned by local security policy" in http://support.microsoft.com/kb/981949 and compare it to your policy. 

In your particular case make sure that the farm account (the identiy that is used for the Application Pool for Central Admin) has at least "Login as a service", "Login as a batch job", "Adjust memory quotas".

This also may disappear if you have the farm account as a "Local admin" on the server running CA. Though ideally not recommended by Microsoft and throws health analyzer warnings.

Dec 22, 2011 at 3:04 PM

I will give that a try.  I had the farm account set a log on locally and login as a service.  The Service account had the login as a batch job.

So now the farm account has the above rights that you suggest and will see.

Dec 22, 2011 at 3:32 PM

This should have been already granted by merit of installing SharePoint (AutoSPInstaller or not). if it isn't there, I'd Look at rsop.msc to check for group policy potentially overriding those, it could be that IIS was already installed or you have .Net 4 framework.

Dec 22, 2011 at 3:35 PM

The farm account must be the service account that is used for CA App pool. Are they different?

Dec 22, 2011 at 3:37 PM

No it is the account for CA.  Just finished the installation.  Looking at the event view, I have a warning: Object Cache: The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources.
 To configure the account use the following command 'stsadm -o setproperty -propertyname portalsuperuseraccount -propertyvalue account -url webappurl'. The account should be any account that has Full Control access to the SharePoint databases but is not an application pool account.
 Additional Data:
 Current default super user account: SHAREPOINT\system

In the installer, I did set a SuperUser and SuperReader account.  Not sure why this error is coming up.

Dec 22, 2011 at 11:16 PM

I have seen numerous posts on these event id's but none seem to fix my issues.  The environment is Windows 2008 R2 Server with SharePoint 2010 and a separate SQL Server running Windows 2008 R2 and SQL Server 2008 R2.

I have tried clearing the cache and restarting the timer service, checked the permissions of the DCOM OSearch.  So I am at a loss of what else to look for.  These errors are blowing up my event viewer every few minutes.

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Server Search
Date:          12/22/2011 3:22:30 PM
Event ID:      67
Task Category: Gatherer
Level:         Error
Keywords:     
User:          Domain\sps_search
Computer:      server.domain.com
Description:
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.

Context: Application '414b2ca5-9303-43f5-a912-65b8caf843a9-query-0'

Details:
    Class not registered
 (0x80040154)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-SharePoint Server Search" Guid="{C8263AFE-83A5-448C-878C-1E5F5D1C4252}" />
    <EventID>67</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>137</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2011-12-22T20:22:30.043241500Z" />
    <EventRecordID>2310</EventRecordID>
    <Correlation />
    <Execution ProcessID="788" ThreadID="3284" />
    <Channel>Application</Channel>
    <Computer>server.domain.com</Computer>
    <Security UserID="S-1-5-21-1757981266-1303643608-682003330-3808" />
  </System>
  <EventData>
    <Data Name="string0">

Context: Application '414b2ca5-9303-43f5-a912-65b8caf843a9-query-0'

Details:
    Class not registered
 (0x80040154)</Data>
  </EventData>
</Event>

 

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          12/22/2011 3:20:50 PM
Event ID:      6398
Task Category: Timer
Level:         Critical
Keywords:     
User:          domain\sps_farm
Computer:      server.domain.com
Description:
The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID 42633def-100b-4fff-af9e-f3a77cec8296) threw an exception. More information is included below.

The search application '414b2ca5-9303-43f5-a912-65b8caf843a9' on server CLINSP did not finish loading. View the event logs on the affected server for more information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6FB7E0CD-52E7-47DD-997A-241563931FC2}" />
    <EventID>6398</EventID>
    <Version>14</Version>
    <Level>1</Level>
    <Task>12</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2011-12-22T20:20:50.868955600Z" />
    <EventRecordID>2304</EventRecordID>
    <Correlation ActivityID="{2A1E3197-804A-4F20-9032-1240038BAC79}" />
    <Execution ProcessID="1916" ThreadID="3268" />
    <Channel>Application</Channel>
    <Computer>server.domain.com</Computer>
    <Security UserID="S-1-5-21-1757981266-1303643608-682003330-3804" />
  </System>
  <EventData>
    <Data Name="string0">Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition</Data>
    <Data Name="string1">42633def-100b-4fff-af9e-f3a77cec8296</Data>
    <Data Name="string2">The search application '414b2ca5-9303-43f5-a912-65b8caf843a9' on server XXXX did not finish loading. View the event logs on the affected server for more information.</Data>
  </EventData>
</Event>

 

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Server
Date:          12/22/2011 3:20:13 PM
Event ID:      6482
Task Category: Shared Services
Level:         Error
Keywords:     
User:          domain\sps_farm
Computer:      server.domain.com
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (50b9b192-b464-4864-bf05-15890dbaaca5).

Reason: The device is not ready. 

Technical Support Details:
System.IO.FileNotFoundException: The device is not ready. 
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-SharePoint Server" Guid="{C33B4F2A-64E9-4B39-BD72-F0C2F27A619A}" />
    <EventID>6482</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>3</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2011-12-22T20:20:13.911954700Z" />
    <EventRecordID>2301</EventRecordID>
    <Correlation ActivityID="{2BB8BBCA-060B-418D-A804-DFCC7FBD8CE6}" />
    <Execution ProcessID="1916" ThreadID="3952" />
    <Channel>Application</Channel>
    <Computer>server.domain.com</Computer>
    <Security UserID="S-1-5-21-1757981266-1303643608-682003330-3804" />
  </System>
  <EventData>
    <Data Name="string0">Microsoft.Office.Server.Search.Administration.SearchServiceInstance</Data>
    <Data Name="string1">50b9b192-b464-4864-bf05-15890dbaaca5</Data>
    <Data Name="string2">The device is not ready.  </Data>
    <Data Name="string3">System.IO.FileNotFoundException: The device is not ready. 
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)</Data>
  </EventData>
</Event>

Coordinator
Jan 25, 2012 at 2:46 AM

"Device not ready" seems to be a clue pointing to an invalid path somewhere in the Search Service app - for example, a data directory pointing to D:\Program Files\... but D: is actually a DVD drive perhaps, etc. Just a guess...

Brian