Archive | Errors RSS for this section

Enable Users to create sub-keys in the registry

Enable users to create sub-keys in the registry

Users are unable to create new registry keys if they are not local administrators. This is a problem incase you have feautres which need to create their own application log categories or similar. This leads to an error being thrown and the feature is not activated.

This problem was fixed by editing the registry.

  1. Log on to the computer as an administrator.
  2. Click Start, click Run, type regedit in the Open box, and then click OK. The Registry Editor window appears.
  3. Locate the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog

  1. Right-click Eventlog, and then click Permissions. The Permissions for Eventlog dialog box appears.
  2. Click Advanced. The Advanced Security Settings for Eventlog dialog box appears.
  3. In the Name column, double-click the Users group. The Permission Entry for Eventlog dialog box appears.
  4. Select the Set Value check box, select the Create Subkey check box, and then click OK.
  5. Quit Registry Editor
Advertisements

Load Control Template file (TaxonomyPicker.ascx failed) – ERROR

If you get the following 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’.

You need to check that the TaxonomoyPicker.ascx file has not been modified

  1. Open your 14-hive folder (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14)
  2. Open the TEMPLATE folder
  3. Open the CONTROLTEMPLATES folder
  4.  Find the TaxonomyPicker.ascx file and open it in notepad
  5. On the first line check if you have &#44 instead of ,

<%@ Control className=”TaxonomyPickerControl” Language=”C#” Inherits=”Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker,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” %>

Save the file, the error should be gone now.

PRC Server Unavailable Error

If your event log shows errors relating to the RPC Server being unavailable (COM Exception 0x800706BA, Event ID 3), like the one below.

 

Then you most likely need to start the remote procedure call service. Start the services.msc from the Start -> Run menu

Locate the Remote Procedure Call (RPC) services and

1. Make sure that they can both start automatic and

2.Make sure that they are running. (You could also try to restart the services if they are running and you still get the same error).

Starting/restarting these should solve the problem.

Could not find stored procedure ‘dbo.Search_GetRecentStats’

This error is generally due to the fact that the Search service application cannot write to the usage and health database.

Event ID: 6398

The Execute method of job definition Microsoft.Office.Server.Search.Monitoring.HealthStatUpdateJobDefinition (ID 9cb6be54-0384-4c6e-abfc-c2f25621a3ed) threw an exception. More information is included below.

Could not find stored procedure ‘dbo.Search_GetRecentStats’.

Event ID: 5586

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

Could not find stored procedure ‘dbo.Search_GetRecentStats’.

This is most likely either because the usage and health service does not have Health Data collection enabled. Go to central admin and under monitoring select Configure usage and health data collection. Select both the Enable usage data collection and the Enable health data collection.

Then perform an IISReset and restart the SPTimerV4 service.

(If these are already on, you need to disable them first then enable them again. Make sure to perform an IISReset and restart the SPTimerV4 service in between.)

If you have problem to disable the “Enable health data collection” you will have to stop some timer jobs:

Go to “monitoring” and to “Configure usage and health data collection”. Go to the “enable health data collection” and click on “health logging schedule”

Disable the following timer jobs (Diagnostics Data Provider: Performance Counters – Database Servers and UserProfileServices- User Profile to SharePoint Quick Syncronization):

Go to “monitoring” and  “Review job definitions”

Disable this timer job (Health Staticsics Updaing):

Now you should be able to disable the  “Enable health data collection”

The EXECUTE permission was denied on the object ‘proc_GetProductVersions’, database ‘SharePoint_Config’, schema ‘dbo’.

This error appears because the stored procedure for Proc_GetProductVersions does not have the correct permissions.

  1. Navigate to the SQL server
  2. Expand the Database tree
  3. Expand the SharePoint Config database
  4. Select Programmability
  5. Select Stored Procedures
  6. Find dbo.proc_GetProductVersions
  7. Right click the stored procedure and select properties
  8. Select permissions
  9. Add [WSS_Content_Application_Pools] and give the account execute permissions.
  10. No restart of any services needed.