How to troubleshoot common errors that occur when you run the SharePoint Products and Technologies Configuration Wizard on a computer that is running Windows SharePoint

http://support.microsoft.com/kb/944267

To resolve this issue, clear the file system cache on all servers in the server farm on which the Windows SharePoint Services Timer service is running. To do this, follow these steps:

1. Stop the Timer service. To do this, follow these steps:
   1. Click Start, point to Administrative Tools, and then click Services.
   2. Right-click Windows SharePoint Services Timer, and then click Stop.
   3. Close the Services console.
2. On the computer that is running Microsoft Office SharePoint Server 2007 and on which the Central Administration site is hosted, click Start, click Run, type explorer, and then press ENTER.
3. In Windows Explorer, locate and then double-click the following folder:
   Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\GUID
   Notes
   • The Drive placeholder specifies the letter of the drive on which Windows is installed. By default, Windows is installed on drive C.
   • The GUID placeholder specifies the GUID folder.
   • The Application Data folder may be hidden. To view the hidden folder, follow these steps:
     1. On the Tools menu, click Folder Options.
     2. Click the View tab.
     3. In the Advanced settings list, click Show hidden files and folders under Hidden files and folders, and then click OK.
   • In Windows Server 2008, the configuration cache is in the following location:
     Drive:\ProgramData\Microsoft\SharePoint\Config\GUID
4. Back up the Cache.ini file.
5. Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
   
   Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
6. Double-click the Cache.ini file.
7. On the Edit menu, click Select All.
8. On the Edit menu, click Delete.
9. Type 1, and then click Save on the File menu.
10. On the File menu, click Exit.
11. Start the Timer service. To do this, follow these steps:
    1. Click Start, point to Administrative Tools, and then click Services.
    2. Right-click Windows SharePoint Services Timer, and then click Start.
    3. Close the Services console.
    Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
12.  Make sure that the Cache.ini file has been updated. For example it should no longer be 1 if the cache has been updated.
13. Click Start, point to Programs, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.
14. Click the Operations tab, and then click Timer job status under Global Configuration.
15. In the list of timer jobs, verify that the status of the Config Refresh entry is Succeeded.
16. On the File menu, click Close.

SPUpdatedConcurrencyException While Installing SharePoint 2010 Service Pack 1

http://sajiviswam.wordpress.com/2012/03/01/spupdatedconcurrencyexception-while-installing-sharepoint-2010-service-pack-1-2/

After installing SharePoint 2010 Service Pack 1 for SharePoint Server, the SharePoint Products and Technologies Configuration Wizard (either from GUI or using PowerShell) may fail throwing the following exception.

An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown. Additional exception information: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade -20110924-194525-15 was updated by DOMAIN\ACCOUNT, in the PSCONFIG (7240) process, on machine SERVER. View the tracing log for more information about the conflict.
Total number of configuration settings run: 3
Total number of successful configuration settings: 2
Total number of unsuccessful configuration settings: 1
Successfully stopped the configuration of SharePoint Products.
Configuration of SharePoint Products failed. Configuration must be performed before you use SharePoint Products. For further details, see the diagnostic log located at [LOCATION OF LOG] and the application event log.

This KB article describes the cause and and solution for this issue. The suggested solution is to clear Windows SharePoint Services configuration cache. Unfortunately, this may not work in most of the cases. If it doesn’t work, there is another workaround. This is by setting the ‘command-line-upgrade-running’ configuration property to ‘No’ and running Configuration Wizard again. Entire steps are given below.

1. Open command prompt as administrator.
2. Type in the command: stsadm -o setproperty -pn command-line-upgrade-running -pv No
3. Restart IIS and SP Timer
4. Run configuration wizard: psconfig -cmd upgrade -inplace b2b -wait –force

Sharepoint diagnostic studio (SPDIAG) performance counters have not been provisioned

The error seen as some of the counters  used to create these reports are not added to the  SP Diagnostic Performance  counters .  Below are the steps that fixed the issue in my environment .

1. From the SharePoint Manage shell  run the following commands to add missing SQL counters

Add-SPDiagnosticsPerformanceCounter –category SQLServer:Locks –counter "Average Wait Time (ms)" –allinstances -databaseserver

Add-SPDiagnosticsPerformanceCounter –category LogicalDisk –counter "Disk Reads/sec" –allinstance -databaseserver

Add-SPDiagnosticsPerformanceCounter –category LogicalDisk –counter "Disk Writes/sec" –allinstance –databaseserver

2.  Run the following command to ensure the new counters added are visible in the list , You should get response as below

Get-SPDiagnosticsPerformanceCounter | where  {$_.providername -eq "job-diagnostics-performance-counter-sql-provider"}| FL

InstanceNames               : {_Total}

MonitorAllInstances         : False

CategoryName                : Processor

CounterNames                : {% Processor Time}

LocalizedCategoryName       : Processor

ProviderName                : job-diagnostics-performance-counter-sql-provider

UpgradedPersistedProperties : {}

InstanceNames               :

MonitorAllInstances         : False

CategoryName                : Memory

CounterNames                : {Available Mbytes}

LocalizedCategoryName       : Memory

ProviderName                : job-diagnostics-performance-counter-sql-provider

UpgradedPersistedProperties : {}

InstanceNames               : {*}

MonitorAllInstances         : True

CategoryName                : LogicalDisk

CounterNames                : {Avg. Disk Queue Length, Avg. Disk sec/Transfer,

                              Disk Reads/sec, Disk Writes/sec}

LocalizedCategoryName       : LogicalDisk

ProviderName                : job-diagnostics-performance-counter-sql-provider

UpgradedPersistedProperties : {}

InstanceNames               : {*}

MonitorAllInstances         : True

CategoryName                : SQLServer:Locks

CounterNames                : {Average Wait Time (ms)}

LocalizedCategoryName       : SQLServer:Locks

ProviderName                : job-diagnostics-performance-counter-sql-provider

UpgradedPersistedProperties : {}

InstanceNames               : {}

MonitorAllInstances         : False

CategoryName                : SQLServer:Latches

CounterNames                : {Average Latch Wait Time (ms)}

LocalizedCategoryName       : SQLServer:Latches

ProviderName                : job-diagnostics-performance-counter-sql-provider

UpgradedPersistedProperties : {}

3. Restart the Timer service on  the WFE used to run SPDIAG .

4.  Launch the SQL Diagnostic Studio again , Click on New project & create the project with same name again .  This removes the old project & all the provider configurations are  re-initialized .

5.  The “SQL overview Report” should now work  without throwing any errors .

Thanks!!

---

Regards,
Manas Biswas
Microsoft Online Community Support


Please remember to click 'Mark as Answer' on the post that helps you or click 'Unmark as Answer' if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Troubleshooting SharePoint user profile service – Replicate Directory Changes

http://sriramkunapuli.com/2012/01/04/troubleshooting-sharepoint-user-profile-service-replicate-directory-changes/

I am actually trouble shooting one of the SharePoint 2010 newly setup Service Farm which is causing issues during Replicating the user profile from Active directory.
One simple step that the Administrator of the Farm who installed it forgot was, giving the “Replicate Directory Changes” permission to the user account which is configured as the administrative account for the User Profile Service Application. In order to make the Fore Front Identity Manager properly do it’s job of replicating the content this permission has to be given to the account which is the administrative account that does the replication BETWEEN the active directory and SharePoint.
Login to the Active Directory Server (i am assuming Windows 2008 R2) and perform the following steps to give the permissions.
1) Launch “Active Directory Users and Computers”
2) Right click on the domain which needs to be replicated and click on properties.
3) Click on “Delegate Control”, Add the User Profile administrative account user and click on next.
4) Make sure ”This folder, existing objects in the folder and Creation of new objects in the folder” radio button is selected and click on Next
5) “General” checkbox is checked by default, and from the list of permissions select “Replicating Directory Changes” checkbox and click on next and finish.
This will grant the administrative account to perform the replication of the objects between Active Directory and SharePoint.

User profiles Sync DB doesn't have Tables or Stored Procedures

Issue:

While you are trying to import the user profiles in SharePoint 2010, you will get lots of errors. Particularly, we will face some of the issues like below:

1. Forefront Identity Manager Service may not be started.

2. Forefront Identity Manager Synchronization service may not be started.

3. If you see the "eventvwr", you will get some of the errors like below:

Error 1:

The Forefront Identity Manager Service cannot connect to the SQL Database Server.

The SQL Server could not be contacted. The connection failure may be due to a network failure, firewall configuration error, or other connection issue. Additionally, the SQL Server connection information could be configured incorrectly.

Verify that the SQL Server is reachable from the Forefront Identity Manager Service computer. Ensure that SQL Server is running, that the network connection is active, and that the firewall is configured properly. Last, verify the connection information has been configured properly. This configuration is stored in the Windows Registry.

Error 2:

.Net SqlClient Data Provider: System.Data.SqlClient.SqlException: Could not find stored procedure 'RegisterService'.

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)

at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)

at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)

at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

at Microsoft.ResourceManagement.Data.DataAccess.RegisterService(String hostName)

Error 3:

The Forefront Identity Manager Service was not able to initialize a timer necessary for supporting the execution of workflows.The Forefront Identity Manager Service could not bind to its endpoints. This failure prevents clients from communicating with the Web services.

Error 4:

A most likely cause for the failure is another service, possibly another instance of Forefront Identity Manager Service, has already bound to the endpoint. Another, less likely cause, is that the account under which the service runs does not have permission to bind to endpoints.

Ensure that no other processes have bound to that endpoint and that the service account has permission to bind endpoints. Further, check the application configuration file to ensure the Forefront Identity Manager Service is binding to the correct endpoints.

Solution:

I have spent lots of time to fix this issue. Hmmmm... The solution is in SQL server side. In SQL Server database, you cannot find any "tables" or "Stored Procedures" in "Sync DB"

I have given the solution in single screenshot. In the below screenshot, set the "db_owner" schema for "dbo".

If you set the "dbo" as "db_owner", you can able to start the "Forefront Identity Manager Service". so that you will be able to start the profile import process.

Thats it...

FIM – Forefront Identity Manager Failed to Connect to SQL Server

FIM – Forefront Identity Manager Failed to Connect to SQL Server


ISSUE
=====
SharePoint 2010 connects to a SQL Instance
In SharePoint 2010 FIM is used for importing and synchronising user profiles by the User Profile Service Application. Starting the User Profile Synchronising Service (from Central Admin – System Settings – Mange Service on Server) Fail’s. Reviewing the Event log you receive the following error message:

Log Name: Application
Source: FIMSynchronizationService
Date: 13/07/2010 15:19:37
Event ID: 6324
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: .
Description:
The server encountered an unexpected error and stopped.


Resolution
=========

Somehow the SQL Instance information for the FIM Synchronising Service is missing

To resolve the issue add the SQLInstance name to the following Reg key:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\FIMSynchronizationService\Parameters]
"SQLInstance"=""

The EXECUTE permission was denied on the object ‘proc_GetProductVersions’- Insufficient SQL database permissions for user

http://sajiviswam.wordpress.com/2011/05/24/the-execute-permission-was-denied-on-the-object-proc_getproductversions-insufficient-sql-database-permissions-for-user/

With SharePoint 2010 RTM production farm, the following error was being logged in application event logs with severity level Critical when users try to open some of the site administration pages। An example is Site Actions > More Options page।
Insufficient SQL database permissions for user ‘Name: SID: ImpersonationLevel: Impersonation’ in database ‘SharePoint_Config’ on SQL Server instance ‘’. Additional error information from SQL Server is included below.
The EXECUTE permission was denied on the object ‘proc_GetProductVersions’, database ‘SharePoint_Config’, schema ‘dbo’.
In order to resolve the issue, I provided Execute permission to the database role “WSS_Content_Application_Pools” into the stored procedure “proc_GetProductVersions”. I performed the following steps to do this.
1.In the database server, expand SharePoint Config database and naviage to Programmability/Stored Procedures/dbo.proc_GetProductVersions using SQL Server Management Studio.
2.Right click on the above stored procedure and select Properties.
3.On the popup screen, select Permissions on the left and click Search button.
4.On the new popup screen, click Search, select [WSS_Content_Application_Pools] database role and click OK.
5.Click OK again.
6.On the first popup screen, select the role, check Execute permission and click OK.
There is no need to restart any services for this change to take effect.

Error 7043 "Load control template file /_controltemplates/TaxonomyPicker.ascx failed"

Error 7043 "Load control template file /_controltemplates/TaxonomyPicker.ascx failed"

http://support.microsoft.com/kb/2481844
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
The above solution from Microsoft doesn't work for me.
The solution is to rename the file "TaxonomyPicker.ascx" to "TaxonomyPicker.ascx_bug"

SandBox Service Error

http://social.technet.microsoft.com/Forums/en-US/sharepoint2010programming/thread/ff3a5e65-dc5b-4b80-b8c9-752adcc3a903/

Hi Rick, Everybody,

I'm the customer that you referred in your post. For sake of information of the group, here are the specs of the systems that we are using:

- Three separated SharePoint Server 2010 farms (Integration, Q&A, Production), two FE + two Application each, individual instance of SQL 2010 R2 each in the SQL Cluster
- Eight different SharePoint 2010 farms (development), each one in one separated box (Win, SP, SQL, VS)
- Everything running inside the same Domain Controller
- No one has Internet access
- Everything using http (not https)

When we try to install a SandBox solution (very simple solution, just a WebPart with one button and one label: if you push the button, you get "Hello world" in the label), we get in all the twelve environments the message "The sandboxed code execution request was refused because the Sandboxed Code Host Service was too busy to handle the request"

- It is possible to install the solution in the "Solutions" gallery
- This message appears at installation of the WebPart in a page (using IE or Firefox)
- The Sandbox Service is running
- The Sandbox processes run using the super-administrator account (the account used to install the farms)
- If we install the solution in a farm outside the DC, everything works perfectly

After hours making traces we found that the Sandbox solution was trying to find certificate revocations using the Microsoft certificate server (crl.microsoft.com). The solution doesn't use any certificate, and all the other functionality in the farms is running as expected.
Based in our conclusions and as Rick mentioned, we were able to make it working using two different approaches:

1 Modifying the Registry Key that controls the check "Check for publisher's certificate revocation" in Internet Explorer (HKEY_USERS\[SID OF THE SERVICE ACCOUNT]\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing. The value of "State" need to be set to "0×00023e00".)
2 Using a host name in the servers: "127.0.0.1 crl.microsoft.com" (I used this solution and worked fine)

The first approaches is not desirable to be implemented in a production environment and, if the account where is applied is changed anyhow, the workaround will stop working. We are implementing right now the second approach as a temporary workarond, being not happy with it, but it works at least.

Very curious if the modification in the host name works also for the other cases described here.

Gr., Gustavo

---

Gustavo - http://www.gavd.net/ - http://geeks.ms/blogs/gvelez/

Fab 40 Templates for SharePoint 2010

SharePoint 2010: Fab 40 Templates for SharePoint 2010: "Now you can download Fab 40 templates for sharepoint 2010 which were not available before. The 'Fantastic 40' templates were created for Wss..."