An unexpected error has occurred

1. Restored the deleted workflow from the Recycle Bin, and then tested: still experienced error message.
2. Noted the correlation ID presented in the error message.
3. Launched ULSViewer, and then connected it to live feed.
4. Searched for the correlation ID and found this event:

   
   System.ArgumentException: Column '[SomeColumnName]' does not exist. It may 
     have been deleted by another user.  /Path/To/List   
    at Microsoft.SharePoint.SPFieldCollection.GetFieldByInternalName(String strName, Boolean bThrowException)    
    at Microsoft.SharePoint.Workflow.SPWorkflow.GetIStatusAsText(Int32 iStatus)    
    at Microsoft.SharePoint.Workflow.SPWorkflow.GetIStatusAsHtml(Int32 iStatus)    
    at Microsoft.SharePoint.Workflow.SPWorkflow.GetIStatusAsHtml()    
    at Microsoft.SharePoint.ApplicationPages.WorkflowPage.StrStatus(SPWorkflow wf)    
    at ASP._layouts_workflow_aspx.__Render__control11(HtmlTextWriter __w, Control parameterContainer)    
    at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)    
    at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)    
    at System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer)    
    at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)    
    at System.Web.UI.HtmlControls.HtmlForm.RenderChildren(HtmlTextWriter writer)    
    at System.Web.UI.HtmlControls.HtmlForm.Render(HtmlTextWriter output)    
    at System.Web.UI.HtmlControls.HtmlForm.RenderControl(HtmlTextWriter writer)    
    at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)    
    at System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer)    
    at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)    
    at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)    
    at Microsoft.SharePoint.WebControls.UnsecuredLayoutsPageBase.RenderChildren(HtmlTextWriter writer)    
    at System.Web.UI.Page.Render(HtmlTextWriter writer)    
    at Microsoft.SharePoint.WebControls.UnsecuredLayoutsPageBase.Render(HtmlTextWriter writer)    
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

5. Noted the SomeColumnName in the event.  This column was completely unfamiliar.  Noted that the column type was not indicated.
6. With ULSViewer up, tested the error for repeatability, by attempted several times to connect to a list item's workflow history page: error was reproducable and correlated with events appearing in the trace log, viewed in ULSViewer.
7. In SharePoint Designer, checked Association Columns, but did not find SomeColumnName.  Also checked Local Variables, but also not successful.
8. Attempted to view workflow information on an archived copy of the list co-located in the same site.  This was successful.
9. Then, using SharePoint Designer, alternatively compared list column listings between the two versions: discovered a column in the archived list missing from the current one.  However, the displayed column name bore no resemblance to that shown in the ULS event message.
10. Then, connected to the site as Administrator and added a new field, SomeColumnName, to the list, as single line string.  Tested again: unsuccessful.  However, the error message correlated with the error message changed:

    
    System.ArgumentException: Column '[SomeNewColumnName]' does not exist. It may have been deleted by another user.  /Path/To/List
     at Microsoft.SharePoint.SPFieldCollection.GetFieldByInternalName(String strName, Boolean bThrowException)    
     at Microsoft.SharePoint.Workflow.SPWorkflow.GetIStatusAsText(Int32 iStatus)    
     at Microsoft.SharePoint.Workflow.SPWorkflow.GetIStatusAsHtml(Int32 iStatus)    
     at Microsoft.SharePoint.Workflow.SPWorkflow.GetIStatusAsHtml()    
     at Microsoft.SharePoint.ApplicationPages.WorkflowPage.StrStatus(SPWorkflow wf)    
     at ASP._layouts_workflow_aspx.__Render__control11(HtmlTextWriter __w, Control parameterContainer)    
     at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)    
     at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)    
     at System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer)    
     at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)    
     at System.Web.UI.HtmlControls.HtmlForm.RenderChildren(HtmlTextWriter writer)    
     at System.Web.UI.HtmlControls.HtmlForm.Render(HtmlTextWriter output)    
     at System.Web.UI.HtmlControls.HtmlForm.RenderControl(HtmlTextWriter writer)    
     at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)    
     at System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer)    
     at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)    
     at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)    
     at Microsoft.SharePoint.WebControls.UnsecuredLayoutsPageBase.RenderChildren(HtmlTextWriter writer)    
     at System.Web.UI.Page.Render(HtmlTextWriter writer)    
     at Microsoft.SharePoint.WebControls.UnsecuredLayoutsPageBase.Render(HtmlTextWriter writer)    
     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

11. Changed column type to Choice, populated some choices, and repeated test: still unsuccessful.  Same event message appearing in ULS.
12. Removed all workflows from the site and then again tested:  still experienced error message.
1. Conclusion: issue remains tied to list.
13. Exported list from production farm, using CA, and then imported to development farm site using PowerShell.  Connected to site through SharePoint Designer: the workflows were not exported.  Testing unnecessary.
1. Conclusion: workflows are not stored at the list level.
14. Exported site (not site collection) from production farm, using PowerShell, and then restored site to dev farm using PowerShell. Opened browser, navigated to list, checked workflow history: this time able to view without error, but no history was listed. Navigated to list workflows and found none.
1. Conclusion: workflows are not stored at the site level.
15. Stopped IIS on both WFEs. In CA,"detached" content databases from web application (this is a SharePoint detach). Restored backup copies of DBs (in SQL Svr); and then mapped appropriate accounts to restored DBs (in SQL Svr). In CA, "attached" content databases to web application. Started IIS on both WFEs.  Navigated to list and checked workflows: no error, workflow history existed, workflows worked.
1. Conclusion: workflows are stored at the site collection level.

1. SharePoint 2010 List workflow status – unexpected error
2. SharePoint 2010: Manager
3. Troubleshoot workflow errors (SharePoint Foundation 2010)
4. How to migrate SharePoint 2010 List based workflows
5. SharePoint Designer Workflow Overview
6. How to Delete/Remove a Workflow from SharePoint Designer
7. HOWTO: Remove a Workflow from a List or Library

• Open the Windows Media Player Library troubleshooter
• media player rip tab greyed out
• Windows Media Player
• Rip music from a CD

• Windows 7
• Windows Media Player 12

1. Login to Central Administration under a farm administrator account.
2. Go: CA > Application Management > Site Collections > Configure quotas and locks.
3. From the Site Collection dropdown, select the appropriate site collection.
4. In the Site Lock Information section, set the Lock status for this site to: Not locked.
5. Click OK.

• Lock or unlock site collections (SharePoint Foundation 2010)
• Lock or Unlock site collections in SharePoint 2010

1. Checked farm servers:

• all up and running.

• connecting to this site resulted in same error.

• SQL Server service running.

• Group of 8306 errors occuring at 2:10 AM: An exception occurred when trying to issue security token: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms..
• A large volume of 5586, 6398, 8088, 5240, 6772 and other errors began appearing at approximately 11:20 PM.

• same error appearing on connection; same errors appearing in Application logs.

1. Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > System cryptography: Use FIPS compliant algorithms for encryption... this was set to Enabled.

1. The setting change was pushed out at the corporate NOC level (above us), thus, we could not change it directly.
2. Instead, department sysadmin added a new instance of the FIPS policy setting to the AD container but configured it at a higher priority.  Thus, after the corporate policy set the FIPS setting to Enabled, the department policy set the FIPS setting back to DISABLED.
3. Forced the update to the servers in this container.
4. Reset IIS on farm servers.
5. Check security settings: security setting now DISABLED.

• System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing
• "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" security setting effects in Windows XP and in later versions of Windows
• Disabling the FIPS Algorithm Check
• FIPS and SharePoint
• DISABLE FIPS ALGORITHMS BEFORE INSTALLING SHAREPOINT 2010
• Open the Local Group Policy Editor

1. Launch SharePoint Designer 2010.
2. Connect to the target site.
3. On the Navigation pane, at left, click Lists and Libraries.
4. On the Results pane, click on the target list or library.  The Results pane will change to show the properties and objects associated with the list or library you clicked.
5. Look for the Forms group.  It will list all of the New, Edit and View forms created for this list or library.  If this is for a library, you will also see an Upload form item listed there too.
6. Click the New... button for this group.
7. Enter a name for this new default edit form, and the select the Edit item form option.
8. Click OK.
9. This dialog will close and a new edit form will appear listed in the Forms group.
10. Click this item to open it in edit mode.  What you will see is all of the fields layed out nicely.  This is the DataForm Web Part.  You don't want this.
11. Click anywhere in this form.  You'll see the DataFormWebPart title appear just above this form.
12. Select this title.  This then selects the entire web part.
13. Click the Delete key.
14. Click anywhere inside the now empty web part zone.
15. Up above, select the Insert ribbon.
16. In the Controls group, click the SharePoint item.  A dropdown will open.
17. Click List Form..., down at the bottom.  The List or Document Library Form dialog appears.
18. Select the target list or document library, and then select the Edit item form option.  Leave the Show standard toolbar option checked.
19. Click OK.  This inserts the LFWP onto the page.
20. Save the page.
21. On the Forms group, select the new edit form listed there (don't click on the filename itself).  This updates the ribbon.
22. On the ribbon, select the Forms tab.
23. Click the Set as Default button.
24. Test.

• Web Parts for views and forms in SharePoint Designer 2010
• SharePoint 2010: The HTML Web Part
• Restore list form web part for EditForm

1. Increase the MaxTemplateDocumentSize property using either PowerShell or stsadm.  Default is 50 MB.  Maximum is 500 MB.
2. Using PowerShell:
1. Execute the following commands in a PowerShell command window to increase the maximum to 500 MB:

   [void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
   [void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Administration")
   $docSize = 500000000
   $webservice = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
   $webservice.MaxTemplateDocumentSize = $docSize
   $webservice.Update()
   

3. Using stsadm:
1. Run the following command at the command prompt:

   stsadm -o setproperty -propertyname max-template-document-size -propertyvalue 500000000

• The PowerShell commands can be executed on any server in the SharePoint farm.  Note that if you use
• stsadm can be executed in the command window on any SharePoint server in the SharePoint farm.  If you experience an error trying to execute stsadm, check the DOS Path environment variable to be sure that it includes the path to the stsadm binary, which, by default for 2010, is located here:

  C:\Program Files\Common Files\Microsoft Shared\web server extensions\14\BIN 

• System.Reflection Namespace
• Assembly Class
• Assembly.LoadWithPartialName Method
• Microsoft.SharePoint namespace
• Microsoft.SharePoint.Administration namespace
• SPWebService class
• SPWebService.ContentService property
• SPWebService.MaxTemplateDocumentSize property
• Increase maximum size of List Template
• How to use Powershell to set Max template document size
• Tip: Quickly Import List and Library Templates into SharePoint

Read error on file "_catalogs/.../MyListTemplate.stp"

Throttled:Query exceeds lookup column threshold...

1. Open the SharePoint 2010 Management Shell
2. Execute the following:

   $Web = Get-SPWeb "http://PathToTargetSite"
   $List = $Web.Lists["YourListName"]
   $List.EnableThrottling = $false
   $List.Update()
   

3. Re-attempt the save list as template with data process.
4. Once completed, re-execute the above script, this time setting EnableThrottling to $True.

• Query Throttling and Indexing
• Understand and Configure Resource Throttling on SharePoint Server 2010
• infopath - cannot create list item error: Throttled:Query exceeds lookup column threshold
• The SharePoint 2010 “List View Lookup Threshold” and Why We Don’t Change It

Log Name:      Application
Source:        MSSQLSERVER
Date:          [date/time]
Event ID:      28005
Task Category: Server
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      [databasename]
Description:
An exception occurred while enqueueing a message in the target queue. 
Error: 15404, State: 19. Could not obtain information about Windows NT 
group/user '[domain\accountname]', error code 0x5.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSSQLSERVER" />
    <EventID Qualifiers="49152">28005</EventID>
    <Level>2</Level>
    <Task>2</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="[date/time]" />
    <EventRecordID>1127225</EventRecordID>
    <Channel>Application</Channel>
    <Computer>[databasename]</Computer>
    <Security />
  </System>
  <EventData>
    <Data>15404</Data>
    <Data>19</Data>
    <Data>Could not obtain information about 
Windows NT group/user '[domain\accountname]', error code 0x5.</Data>
    <Binary>656D000010000000100000004F00430053002D00
560053002D004E0041005600530051004C00440031000000070000006D00610073007400650072
000000</Binary>
  </EventData>
</Event>

1. Reviewed server Application log to find start of issue:

• Results: 33,000 repetitions of event completely flooded log through beginning - log was overwriting itself.  Estimated duration of event thus far: (33K total occurrences in log) / (77 occurrences per cycle) / (~ 63 seconds per cycle) > = 7 hours.

• Result: no issues; users able to access content

• Result: no related issues.

• Result: no resolution.

• Result: no resolution.

• Result: no resolution.

• Result: did not find any NULL values as discusses in the reference, thus not helpful

• Result: not locked, thus not helpful

EXECUTE AS LOGIN = ‘[yourdomain]\me’
Go

• Results: failed. Tried again on problematic account: succeeded.  Tried on other service accounts: failed.

• Results: found three databases created under (and thus owned by) the farm account, which was unusual, as these are usually created by the admin account. Databases involved the securestore and web analytics services. Neither the admin nor the farm account were mapped to these databases (this accounted for an unrelated error involving failed database upgrade - psconfig).

• Results: servers had been patched with latest Windows server CUs the previous day.  Found some older discussion associating eventID 28005 with patching.

• Result: again noted that the account identified in the error, the farm service account, was identified as the DBO for three particular databases; and that these databases were all created recently.  Also noted the owner for a new content database, created recently, also used the farm account.

• Result: no resolution, but improved my understanding of issue.  28005 error now presented my administrator account in its error message, rather than the farm service account.  This help bound the scope of the issue by demonstrating that I could affect the error outcome, even in a minor way.

• Result: no resolution.

• Result: success.  EventID 28005 stopped appearing in the server Application log.

1. Changed the DBO for the three particular databases to the SA (using the same TSQL statement shown above).

• Result: success. 24 hours later, the error message still has not appeared.

• SQLServer Error: 15404 with Active Directory
• Could not obtain information about Windows NT group/user .......error code 0x534
• ALTER AUTHORIZATION (Transact-SQL)
• Event ID 28005
• An Exception occured while enqueueing a message in the target queue. Error 15404....
• David Klein's Corner blog entry for Wednesday, 13 July 2011
• SUSER_SNAME (Transact-SQL)

• Farm topology: Windows Server 2008 R2, SQL Server 2008 R2 Standard, SharePoint 2010 Server Enterprise.
• Methodology: the troubleshooting steps were wide ranging in order to more definitively bound the scope of the issue and improve understanding of it.

1. Reviewed job history for SharePointServer1.

• Result: no job currently scheduled, nor any job completed since midnight.

• Result: service is set to Auto and is stopped.

• Result: service remained started.

• Result: new jobs began appearing in history.  All jobs completed successfully except for two, which were repeatedly aborted: Service Application Instance Provisioning Job, Application Server Administration Service Timer Job.

• Result: message: "The administration service job definition 'SecurityTokenServiceApplication' (id 5e0bad8b-948b-460a-8bb2-19da7e10fd9c) was not executed because the administration service on this server is not started. This job definition can be run manually using 'stsadm -o execadmsvcjobs'. "

• Result: message: The administration service job definition 'job-application-server-admin-service' (id 43b74f53-53ba-4eb2-981d-28c13bf012e2) was not executed because the administration service on this server is not started. This job definition can be run manually using 'stsadm -o execadmsvcjobs'.

• Result: service is set to Auto and is stopped.  Also noted that its logon is set to Local System.

• Result: service is set to Auto and is started.  Also noted that its logon is set to Local System.

• Result: service remained started.

• Result: job repeatedly being completed successfully.

• Result: this job did not reappear.

• Result: Severity changed to "4 - Success"

• Application Server Administration Service Timer Job status - failed .....
• SharePoint Administration service is disabled (SharePoint 2010 Products)

• Starting the SharePoint 2010 Administration will generate an error event in the server Application log: EventID 2137: The SharePoint Health Analyzer detected an error.  One or more services have started or stopped unexpectedly.

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          [date/time]
Event ID:      8306
Task Category: Claims Authentication
Level:         Error
Keywords:     
User:          [domain\FarmServiceAccount]
Computer:      [NameOfFailingServer]
Description:
An exception occurred when trying to issue security token: Could not 
connect to 
http://localhost:[port]/SecurityTokenServiceApplication/securitytoken.svc/actas. 
TCP error code 10061: No connection could be made because the target 
machine actively refused it 127.0.0.1:[port]. .
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>8306</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>47</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="[date/time]" />
    <EventRecordID>29898</EventRecordID>
    <Correlation ActivityID="{4F0A4944-93C2-44D8-9C81-68162604774B}" />
    <Execution ProcessID="7128" ThreadID="3156" />
    <Channel>Application</Channel>
    <Computer>[NameOfFailingServer]</Computer>
    <Security UserID="S-1-5-21-3026233045-20759957-1393672501-82644" />
  </System>
  <EventData>
    <Data Name="string0">Could not connect to 
http://localhost:[port]/SecurityTokenServiceApplication/securitytoken.svc/actas. 
TCP error code 10061: No connection could be made because the target machine 
actively refused it 127.0.0.1:[port]. </Data>
  </EventData>
</Event>

1. Solution A: Restart the Security Token Service application pool:
1. As Administrator, launch IIS Manager.
2. In the Connections pane (at left), expand the tree to view Application Pools.
3. Select Application Pools.  This updates the results pane (center pane).
4. Right-click on SecurityTokenServiceApplicationPool, and then click Stop.
5. Right-click on SecurityTokenServiceApplicationPool, and then click Start.
6. Go back to Central Administration, Review problems and solutions :All Reports view.
7. Click on the issue, The Security Token Service is not available.
8. Click Re-analyze Now.
9. Click Close.
10. Refresh after several minutes.
2. Solution B: Re-provision the service
1. Launch the SharePoint Management Shell as Administrator.
2. Run the following script:

   $sts = Get-SPServiceApplication | ?{$_ -match "Security"}
   $sts.Status
   $sts.Provision()​
   

3. Go back to Central Administration, Review problems and solutions :All Reports view.
4. Click on the issue, The Security Token Service is not available.
5. Click Re-analyze Now.
6. Click Close.
7. Refresh after several minutes.

• SharePoint 2010: Receiving error: “Security token service is not available”
• Configure the security token service (SharePoint Server 2010)
• The Security Token Service is not available (SharePoint Foundation 2010)
• SharePoint 2010: Nailing the error "The Security Token Service is unavailable"

The search application for [SearchAppName] on server [ServerName] is not provisioned.  Confirm that the Windows SharePoint Services Timer service and Windows SharePoint Services Administration service are running on the server.

1. Check Windows SharePoint Services Timer Service

• Result: started; logon: admin account.

• Result: started (obviously); logon: local system

• Result: started; logon: admin account

• Result: success

1. Result: Index Server not configured.
2. Action: set Index Server; re-entered SSP Service Credentials password; clicked OK.

1. Result: experienced small delay in loading page (good sign); on load, crawl status indicating crawling.  Successful resolution of issue. 

• Spsearch: Stsadm operation (Windows SharePoint Services)
• SSP Search error (Search application for SSP… is not provisioned)

1. Copy the content database backups to a local folder on the database server.
2. Perform a SharePoint detach of the content databases from web application:
1. Go: CA > Application Management > Manage Content Databases.
2. Remove each database.
3. Detach old/corrupted content database(s) (SQL Server Management Studio)
4. Restore backup content database(s) (SQL Server Management Studio)
5. Add farm service and farm administration accounts to database logins and map appropriately (SQL Server Management Studio)
6. Perform a SharePoint attach of the content database(s) (through SharePoint Central Administration or via PowerShell script)
7. Refresh browser.

• Restore a content database (SharePoint Foundation 2010)
• Databases running in compatibility range, upgrade recommended (SharePoint Server 2010)
• Attach or detach content databases (SharePoint Foundation 2010)
• Mount-SPContentDatabase
• Upgrade-SPContentDatabase

• There really is nothing more to do, when restoring multiple content databases associated with a web application - no special procedure, script to run, special order, etc. You don't even need to perform an IISReset. Just attach them and go.  SharePoint will detect that multiple databases are associated with the web application and relink everything appropriately.
• You may find, after attaching the content databases (either via CA or via PowerShell script), that the site collection(s) in one of the content databases are not visible, and navigating to the URL for one of these site collections returns the "404" error.  The basis for this experience is unclear but can be resolved by performing a SharePoint detach/attach of these databases in CA.  You may need to repeat this several times.
• TIP: the following procedure has worked for me when I encountered this problem: first perform the SharePoint attach of the content database containing the main site collection - the one hosting the default site collection.  Next, before performing SharePoint attachments of the other content databases, open a browser and navigate to the default site collection.  Then, perform a SharePoint attach of the next content database, open a browser and navigate to a site collection in this next content database; and so on.
• Performing SharePoint attachments of content databases by using Central Administration may require a database upgrade afterwards.  On the other hand, using the Mount-SPContentDatabase PowerShell script automatically performs the database upgrade as a part of the attach process.
• I have performed a restore in this fashion, for a farm hosting three site collections and about 150 sites, in about 1 hour, and that's with lots of double-checking.
• I've bolded SharePoint when referring to performing an attachment through SharePoint Central Administration or via PowerShell script, as opposed to performing such operations directly with SQL Server.  The terminology here is a bit ambiguous, as these words are also used when performing attach/detach operations when working with SQL Server.  However, the two are effectively different operations.

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          [date/time]
Event ID:      6398
Task Category: Timer
Level:         Critical
Keywords:     
User:          [farmServiceAccount]
Computer:      [machineName]
Description:
The Execute method of job definition 
Microsoft.SharePoint.Administration.SPSqmTimerJobDefinition 
(ID 2912d44e-0ada-4536-8e05-d79fbeae9fcc) threw an exception. 
More information is included below.
Data is Null. This method or property cannot be called on Null values.
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="[date/time]" />
    <EventRecordID>33386</EventRecordID>
    <Correlation ActivityID="{2217063A-9355-4C01-83AA-7C121F704FC9}" />
    <Execution ProcessID="2296" ThreadID="5900" />
    <Channel>Application</Channel>
    <Computer>[machineName]</Computer>
    <Security UserID="[SID]" />
  </System>
  <EventData>
    <Data Name="string0">Microsoft.SharePoint.Administration.
            SPSqmTimerJobDefinition</Data>
    <Data Name="string1">2912d44e-0ada-4536-8e05-d79fbeae9fcc</Data>
    <Data Name="string2">Data is Null. This method or property cannot 
be called on Null values.</Data>
  </EventData>
</Event>

1. Perused Application log for other instances of the 6398 event associated with a timer definition execution failure

• Result: several other instances of the same timer failure were found.

• Result: Verified failed status of jobs; also verified time of failed job status matched with event time in Application log.

1. Result: three of four web applications had the Enable Customer Experience ImprovementProgram set to No.  One web application (of all things, CA itself), had this set to Yes.

1. Result: the Sign up for the Customer Experience Improvement Program option was set to No.

1. Launch Central Administration
2. Navigate to: Application Management > Web Applications > Manage Web Applications
3. Select the target web application.
4. Select General Settings from the General Settings dropdown on the Web ribbon.
5. Scroll down to the bottom.
6. Set Enable Customer Experience Improvement Program to No.

• Wictor Wilen: About the Customer Experience Improvement Program in SharePoint 2010
• Event ID 6398 due to CEIP Data Collection for SharePoint Foundation

• Use the document library's Manage files which have no checked in version option:

1. Navigate to the document library using at least a Site Collection Administrator account.
2. On the Library ribbon, click Library Settings button.
3. In the Permissions and Management group, click Manage files which have no checked in version.

• Designing large lists and maximizing list performance (SharePoint Server 2010)
• Managing Checked-Out Documents in SharePoint
• Configure a site library to require check-out of files
• SharePoint 2010: PowerShell Script to List the documents checked out with version details in a Site Collection
• “Manage files which have no checked in version” list larger than list view threshold

• If you click this link, and then experience the error, "The query cannot be completed because the number of lookup columns...", you will need to increase the threshold value for the list.  You can do this in Central Administration by:

1. Navigating: Central Administration > Application Management > Web Applications > Manage Web Applications
2. Select the target web application
3. Click the General Settings button on the Web Applications ribbon.
4. Select Resource Throttling from the dropdown.
5. Set the List View Threshold for Auditors and Administrators to a larger number.

1. Use the SQL Server Installation Center:
1. Go: Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools > SQL Server Installation Center.  The familiar installation dialog appears.
2. Click Installed SQL Server features discovery report.  The report is generated and presented as a web page.
2. Use saved setup reports:
1. Go to: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log.  Each running of setup or the discovery report generates data that is saved here.
   
2. Open the file, Summary.txt.  This file contains the configuration details from the most recent setup or discovery operation.

• Validate a SQL Server Installation
• View and Read SQL Server Setup Log Files
• How to identify SQL Server 2008 setup issues in the setup log files
• Query to see what components or features are installed
• SQL Server Powershell is here!
• SQL Server Perceptions

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          [date/time]
Event ID:      8305
Task Category: Claims Authentication
Level:         Error
Keywords:      
User:          [domain\your account]
Computer:      [machinename]
Description:
An exception occurred when trying to establish endpoint for context: 
Could not load file or assembly 'Microsoft.IdentityModel.Extensions, 
Version=2.0.0.0, Culture=neutral, PublicKeyToken=69c3241e6f0468ca' or 
one of its dependencies. Either a required impersonation level was 
not provided, or the provided impersonation level is invalid. 
(Exception from HRESULT: 0x80070542).
Event Xml:
.
.
.

1.  Check Services for SharePoint 2013 services

• Results: SharePoint Administration service running; Claims to Windows Token Service (C2WTS) disabled; other SP services appropriately configured and running.

• Result: still experience 503 error.

• Results: these application pools stopped: search, main site, SharePoint Central Administration V4, SecurityTokenServiceApplicationPool, and some other app services; other SharePoint app pools are started.

• Results: still experienced 503 error; additionally, SecurityTokenServiceApplicationPool stopped again.  Re-attempts also failed.

• Result: connecting to main site now gets HTTP Error 500.  Central administration backup.

• Results:  Main site now up, but CA now down and returns "Unexpected error" message in browser.

• Results: Main site still up and CA still down with same error message.

• Results: both main and CA now up.

1. Have the application pool identities for all farm web applications configured with Logon as batch and Impersonate a client at authentication local rights.
2. After granting the identities these rights, restart the application pools.

• SharePoint 2013 – ‘HTTP 500 Internal Server Error’ while trying to browse to a SharePoint site
• An exception occurred when trying to issue security token: The HTTP service located at
• SharePoint 2013 - Application Server Job Failed (Event ID 6481)
• Sharepoint Central Administration - Site comes up with "Unexpected Error

• Could not have resolved this without the assistance of sysadmins.
• Application pool identities must have Logon as Batch and Impersonate a client afterauthentication local rights.
• The above troubleshooting steps are not complete but are to the best of memory and may be missing some quick steps.

Word Web App cannot open this document for viewing because of an unexpected error.  To view this document, open it in Microsoft Word.

To open this document, your computer must be running a version of Microsoft Word and a browser that supports opening files directly from the Office Web Apps.  Learn more about the requirements.

1. Two separate issues:
1. Office Web App configuration
2. Accessing 32-bit object (Word) from 64-bit application (IE9-64)
2. Ignore the first issue.
3. Have user access document using 32-bit IE.

• The Office Web App cannot open an Office document in Office if the action is triggered from a 64-bit web browser
• Version of IE 32 bit or 64 bit? - How can I tell which version I am using?

• Neither Chrome nor FF get around this issue.

This view cannot be displayed because it exceeds the list view threshold (5000 items) enforced by the administrator.
To view items, try selecting another view or creating a new view. If you do not have sufficient permissions to create views for this list, ask your administrator to modify the view so that it conforms to the list view threshold.
Learn about creating views for large lists.

1. Logon as site collection administrator
2. For each List View web part that exhibits the above error, identify the fields on which it is filtering the list.
3. Navigate to the list's Site Settings.
4. Scroll down below the Columns section until you find the Column options below it.
5. Click Index Columns
6. Click Create a new index.
7. Select a Primary Column from the dropdown and do not select a Secondary Column.  The column that you select should be one of those columns that you found in
8. Click Create.  A new index will be shown.
9. Open a command prompt as Administrator, and then perform an IISRESET.
10. Refresh the dashboard page (use CTRL+F5).
11. If the web part continues to present the same error, configure another column as index - taking the column from the list of such columns you found in step 3.  It may take just one, it may take several together.  You'll just need to test to determine the right combination.
12. Once you have successfully resolved this for one List View web part, repeat for the next one, and so on.  For additonal information on the relationship between resource throttling and indexing, see the MSDN article Query Throttling and Indexing.

• Microsoft Office SharePoint 2010: Manage lists and libraries with many items
• Microsoft Technet Magazine: Understand and Configure Resource Throttling on SharePoint Server
• Microsoft TechNet SharePoint 2010: Performance and capacity test results and recommendations (SharePoint Server 2010)
• MSDN Dina Ayoub's Technical Blog: SharePoint 2010: How to Change the List View Threshold and Other Resource Throttling Settings
• SharePoint 2010 Indexing Best Practices
• MSDN Data Models in SharePoint 2010: Query Throttling and Indexing

• To configure the List View Threshold, go: Central Administration > Application Management > Manage web applications > [select the target web application] > General Settings > Resource Throttling.

1. Launch Central Administration.
2. Navigate to: General Application Settings > Search > Farm Search Administration.
3. Click Settings> Edit page.
4. Make any change to a web part (e.g., change the title of a web part), and then undo (don't worry: this won't break anything).
5. Save the web part, and then exit edit mode.
6. Navigate to: General Application Settings > Farm Search Administration > Search Administration.
7. Click Settings> Edit page.
8. Make any change to a web part (e.g., change the title of a web part), and then undo.
9. Save the web part, and then exit edit mode.
10. Navigate to: Monitoring > Health Analyzer > Review problems and solutions.
11. Click on the error, Missing server side dependencies.
12. Click the Re-analyze Now button.
13. Click Close.
14. Wait a minute or two.
15. Click the error link again.

• SharePoint 2010 Health Analyzer: Missing server side dependencies
• Sterling: SharePoint 2013 Missing Server Side Dependencies

• Unlike in 2010, navigating to the page and refreshing it was insufficient for resolving this issue in 2013.

Unhandled exception has occurred in your application.  if you click Continue, the application will ignore this error and attempt to continue.  If you click Quit, the application will close immediately.

An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings:Could not load file or assembly 'System, Version 4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies.  The system cannot find the file specified. (C:\Users\[username]\AppData\local\Microsoft_Corporation\Landingpage.exe_StrongName_ryspccglaxmt4nhllj5z3thycltsvyyx\11.0.0.0\use
.
.
.

1. Remove the folder %localappdata%\Microsoft_Corporation.

• LandingPage error: An error occurred creating the configuration section handler
• An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or assembly 'System, Version=4.0.0.