SharePoint Troubleshooting: Server Site Dependencies Common Issue After Upgrade

  • Article

After recent upgrade SharePoint 2007 to SharePoint 2010 SP1 + CU, you might see these issues when upgrading:

  • Event ID 6398,
  • Event ID 7043,
  • Event ID 2137, Event ID 7362,
  • Event ID 57,
  • Event ID 5586,
  • Server site dependencies

Event ID 6398

Message

The Execute method of job definition Microsoft.SharePoint.Administration.SPSqmTimerJobDefinition (ID e3dec18a-5376-4312-b18f-2183eb6f2405) threw an exception. More information is included below.

Data is Null. This method or property cannot be called on Null values.

Resolution

Go to Central Admin - monitoring - review job definitions - job history (left) and change the view (right) to Failed jobs. Click the Failed link and you should get similar error messages logged. Review the job (check configuration) to fix and if not needed disable it.

Event ID 7043 - TaxonomyPicker

Error

Load control template file /_controltemplates/TaxonomyPicker.ascx failed: Could not load type 'Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker' from assembly 'Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'.

Task category

Web Controls

Resolution

This is not causing any issues except for a wrong ULS log message a single time in a web application process life time, the exception is caught and that template file is skipped. This message should be treated as log noise and can be ignored.

To change this behavior:

  1. Navigate to /14/TEMPLATE/ControlTemplates/TaxonomyPicker.ascx user control
  2. Open the user control in a text editor and locate the first line
  3. Find the character string , and replace with a comma ‘,’ (without quotes).
  4. Save the user control

Go to <drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES,

Open TaxonomyPicker.ascx in any text editor,

Locate the following line :

<%@ Control className="TaxonomyPickerControl" Language="C#" Inherits="Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker**&#44**;Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

Replace '&#44' with ',' , the correct line should look like

<%@ Control className="TaxonomyPickerControl" Language="C#" Inherits="Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker, Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

Event ID 7043 - NWLOnlineComponents

Error Message

Load control template file /_controltemplates/NWLOnlineComponents.ascx failed: The expression prefix 'NWLResources' was not recognized. Please correct the prefix or register the prefix in the <expressionBuilders> section of configuration.

Task category

Web Controls

Resolution

http://connect.nintex.com/forums/thread/22630.aspx

Go to Central Admin > Nintex Workflow Management > Live Settings and activate Nintex Live.

This solved my problem and no 7043 events will be reported anymore.

Nintex Support had provided me the below to remove the feature from our site collections to prevent anyone from enabling the feature at the Site Collection level. Apparently, even if it isn't installed it is still available to be turned on since it's included in the Nintex Workflow solution.

The "Nintex Workflow - Nintex Live Catalog" feature belongs to the Nintex Workflow solution and is not part of the Nintex Live solution. That is why the feature is in the list even though Nintex Live isn't installed. You can remove the feature manually using PowerShell however.

Firstly, make sure the feature is deactivated on all Site Collections. Then open PowerShell and run the following command:

 Uninstall-SPFeature NintexWorkflowLiveSite -force

Event ID 2137

Error Message

The SharePoint Health Analyzer detected an error. The KnowledgeLake Infrastructure Manager job is invalid in the farm.

The KnowledgeLake Imaging solution cannot be validated for the farm. Ensure the KnowledgeLake Infrastructure job has ran within the last 24 hours on each web application on each server.

Run the KnowledgeLake Infrastructure Manager job to ensure proper farm configuration for the KnowledgeLake Imaging solution. You may automatically run this job by performing a repair action on this health rule. Please review the KnowledgeLake Imaging Server installation guide for more information on installation and configuration.

Task category

Health

RESOLUTION

Please run the Knowledgelake Infrastructure Manager job in the Central Administration job definitions. Then check the job history to ensure that it was successfully run. If this job fails please be sure that the farm account is a local admin on all servers in the farm. Please keep me updated on your results.

Event ID 7362 Web Content Management

Error

http://www.sharepointnutsandbolts.com/2010/09/set-object-caching-user-accounts-with.html

http://technet.microsoft.com/en-us/library/ff758656.aspx

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 unnecessary 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

Task category

Publishing Cache

Event ID 57

Error message

A database error occurred. Source: Microsoft SQL Server Native Client 10.0 Code: 1205 occurred 1 time(s) Description: Transaction (Process ID 128) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Task category

RESOLUTION

http://social.technet.microsoft.com/Forums/en-SG/sharepointadminlegacy/thread/e71861ee-7692-44d6-b8df-6a4137937dca

The deadlock is a job in SQL Server, can you access SQL and review the jobs, filter the logs to find the keyword deadlock and then look for the PID. That's the process that's help and locked. Kill that process and try to do your work again.

Just wondering, how many items are in that calendar list? 20,000 is the norm for deadlocks.

Event ID 5586

Error

Unknown SQL Exception 2812 occurred. Additional error information from SQL Server is included below.

Could not find stored procedure 'proc_UpdateStatisticsNVP'.

2013-01-09T00:00:10.110: Starting

2013-01-09T00:00:10.110: Dropping automatically created stats on user tables

2013-01-09T00:00:10.110: Updating statistics on user indices

2013-01-09T00:00:10.113: Statistics for dbo.IX_Dependencies_ObjectId are now being updated with default sampling.

2013-01-09T00:00:10.113: Rebuilding

2013-01-09T00:00:10.120: Done

2013-01-09T00:00:10.120: Statistics for dbo.IX_Objects_Version are now being updated with default sampling.

2013-01-09T00:00:10.120: Rebuilding

2013-01-09T00:00:10.123: Done

2013-01-09T00:00:10.123: Statistics for dbo.PK_Objects are now being updated with default sampling.

2013-01-09T00:00:10.123: Rebuilding

2013-01-09T00:00:10.130: Done

2013-01-09T00:00:10.130: Statistics for dbo.IX_Objects_ClassId_ParentId_Name are now being updated with default sampling.

2013-01-09T00:00:10.130: Rebuilding

2013-01-09T00:00:10.147: Done

2013-01-09T00:00:10.147: Statistics for dbo.IX_Tombstones_Version are now being updated with default sampling.

2013-01-09T00:00:10.147: Rebuilding

Task category

Database

RESOLUTION

For the first error message: Could not find stored procedure 'proc_UpdateStatisticsNVP'.

The SharePoint 2010 Health Analyzer consists of a rule with the Title "Databases used by SharePoint have outdated index statistics". This health rule runs on a daily schedule and checks the SharePoint databases for outdated index statistics. If databases index statistics are found to be outdated, the rule automatically attempts to update the statistics on the databases. The error is generated because the health rule attempts to run 'proc_UpdateStatisticsNVP' stored procedure against the configuration database, however, this stored procedure does not exist in the configuration database.

This is a known issue that will be fixed in a future release of the product. The error does not affect the functionality of the product in any way and can be safely ignored.

From your second error message, the cause could be DCOM permissions were not set.

  • Go to Start | Programs | Administrative Tools | Component Services
  • Expand Component Services | Computers | My Computer | DCOM Config.
  • Right-Click on IIS WAMREG Admin service and go to Properties | Security.
  • Click the edit button under Launch and Activation Permissions.
  • Add the accounts that the errors are complaining about here with Local Launch and Local Activation permissions.