SharePoint 2010 SP1 issues   

Tags: SharePoint 2010
Technorati Tags:

SharePoint SP1 has been released a couple of weeks ago. So I went experimenting with the SP1.

 

I followed this little guide for installing SP1 on my SharePoint environment.

http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=984

 

 

First Issue Sandboxed solutions

 

When the installation was finished I deployed a sandbox solution that I created before the sp1 update.

 

I don’t have the exact error but it was something about the event receiver class.

 

The Fix:

Install the hotfix for SharePoint 2010 SP1 (released a few days after SP1 update) => CU June

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

 

 

Second  Issue search service

 

I went to the event viewer and saw some errors showing up. One of the errors are search service related

 

Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (66681a95-f624-47d9-b422-ad17ea8d453f).

Reason: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by ONPRVP\srv_sp2010_dev_farm, in the OWSTIMER (1980) process, on machine PDV-MOSS06.  View the tracing log for more information about the conflict.

Technical Support Details:

Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by ONPRVP\srv_sp2010_dev_farm, in the OWSTIMER (1980) process, on machine PDV-MOSS06.  View the tracing log for more information about the conflict.

   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()

   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

 

The fix:

 

  1. Stop the Windows SharePoint Services Timer service (Found in Windows Services)

 

  1. Navigate to the cache folder
    In Windows Server 2008, the configuration cache is in the following location:
    Drive:\ProgramData\Microsoft\SharePoint\Config
    In Windows Server 2003, the configuration cache is in the following location:
    Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
    Locate the folder that has the file "Cache.ini"
    (Note: The Application Data folder may be hidden. To view the hidden folder, change the folder options as required)

 

  1. Back up the Cache.ini file.

 

  1. 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.

  1. 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.

  1. Double-click the Cache.ini file.

 

  1. On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu. On the File menu, click Exit.

  1. Start the Windows SharePoint Services Timer service

 

  1. 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.

  1. Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.

Source:

http://www.social-point.com/sharepoint-2010-event-id-6482-application-server-administration-job-failed-for-service-instance-microsoft-office-server-search-administration-searchserviceinstance

 

 

Third Issue Database version

 

The other error was database related. The event viewer showed this error

 

The mount operation for the gatherer application 71250ce4-00b6-447b-bda5-c42efd93ecdd-crawl-0 has failed because the schema version of the search gatherer database is less than the minimum backwards compatibility schema version supported for this gatherer application. The database might not have been upgraded.

 

The Fix:

 

  • Launch an elevated (Run as Administrator) SharePoint 2010 Management shell from start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Management Shell.
  • Once the shell opens, type the following command followed by enter:
    (get-spserver $env:computername).NeedsUpgrade

image

  • If the result of the command is true.
  • Open an Administrative command prompt
  • Change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
  • Run PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

 

Source:

http://blogs.technet.com/b/sbs/archive/2011/07/06/potential-issues-after-installing-sharepoint-foundation-2010-sp1.aspx

 

 

Fourth Issue User Profile Application Service

 

After installing CU June the Forefront Identity Manager Synchronization Service stops running. When you try to start the service again it will give the following error.

 

The server encountered an unexpected error and stopped.
 
"BAIL: MMS(7368): storeimp.cpp(308): 0x80230443 (Service start up has failed.  Cannot open the FIM Synchronization Service database because the database schema version in existing database does not match the required version.)
ERR: MMS(7368): server.cpp(373): Failed to connect to the database Sync DB on PDV-MOSS06
BAIL: MMS(7368): server.cpp(374): 0x80230443 (Service start up has failed.  Cannot open the FIM Synchronization Service database because the database schema version in existing database does not match the required version.)
BAIL: MMS(7368): server.cpp(3860): 0x80230443 (Service start up has failed.  Cannot open the FIM Synchronization Service database because the database schema version in existing database does not match the required version.)
BAIL: MMS(7368): service.cpp(1531): 0x80230443 (Service start up has failed.  Cannot open the FIM Synchronization Service database because the database schema version in existing database does not match the required version.)
ERR: MMS(7368): service.cpp(980): Error creating com objects. Error code: -2145188797. This is retry number 0.
BAIL: MMS(7368): clrhost.cpp(224): 0x80131022
BAIL: MMS(7368): scriptmanagerimpl.cpp(7670): 0x80131022
BAIL: MMS(7368): server.cpp(251): 0x80131022
BAIL: MMS(7368): server.cpp(3860): 0x80131022
BAIL: MMS(7368): service.cpp(1531): 0x80131022
ERR: MMS(7368): service.cpp(980): Error creating com objects. Error code: -2146234334. This is retry number 1.
BAIL: MMS(7368): clrhost.cpp(224): 0x80131022
BAIL: MMS(7368): scriptmanagerimpl.cpp(7670): 0x80131022
BAIL: MMS(7368): server.cpp(251): 0x80131022
BAIL: MMS(7368): server.cpp(3860): 0x80131022
BAIL: MMS(7368): service.cpp(1531): 0x80131022
ERR: MMS(7368): service.cpp(980): Error creating com objects. Error code: -2146234334. This is retry number 2.
BAIL: MMS(7368): clrhost.cpp(224): 0x80131022
BAIL: MMS(7368): scriptmanagerimpl.cpp(7670): 0x80131022
BAIL: MMS(7368): server.cpp(251): 0x80131022
BAIL: MMS(7368): server.cpp(3860): 0x80131022
BAIL: MMS(7368): service.cpp(1531): 0x80131022
ERR: MMS(7368): service.cpp(980): Error creating com objects. Error code: -2146234334. This is retry number 3.
BAIL: MMS(7368): service.cpp(994): 0x80131022
Forefront Identity Manager 4.0.2450.34"

 

Other issue it creates that I found:

 

Secure store service application will lose his master key and you can’t create a new master key until you resolve the user profile service application issue. 

 

For more information about the Secure Store Service Application:

http://msdn.microsoft.com/en-us/library/ee557754.aspx

 

The NON Recommended fix:

 

The only fix I found was thanks to my colleague Steven. By recreating the service application the error is resolved BUT you will lose all data bind to the service application.

 

Source:

Steven

 
Posted by  Gilissen Timmy  on  7/15/2011
6  Comments  |  Trackback Url  | 0  Links to this post | Bookmark this post with:        
 

Links to this post

Comments


Antonio  commented on  Monday, July 18, 2011  4:59 PM 
How di you resolve the User Profile Application Service issue?


Timmy  commented on  Thursday, July 28, 2011  2:16 PM 
Hi Antonio

I resolved it by recreating the user profile application service.

This fix is not recommended because you will lose date.


Dan Peters  commented on  Friday, September 16, 2011  5:00 PM 
Is there any update on the UPS fix?
Recreating the Service Application is definitely not an option!


Timmy  commented on  Thursday, September 22, 2011  12:22 PM 
Hi Dan,

For the moment i'm on an other project so i haven't had the time to check it out.

If I find a solution i will certainly keep you updated.


Asela  commented on  Friday, October 14, 2011  4:39 AM 
I just installed the SP1 and now i cannot access the Libraries?

Error
An unexpected error has occurred.

Troubleshoot issues with Microsoft SharePoint Foundation.

Correlation ID: c3bbe10f-7e6b-4b57-bbba-108f3539db00



Rune Mariboe  commented on  Thursday, December 8, 2011  1:58 PM 
Just install the second June 2011 CU, the August 2011 CU or the October 2011 CU, run the SharePoint Products Configuration Wizard, restart the User Profile Sync. server service and IISreset, and everything (regarding UPS) will be in order.
If not, reboot and repeat (or try restarting the SharePoint 2010 Timer service first - in case of deadlock) :)

Name *:
URL:
Email:
Comments:


CAPTCHA Image Validation