Friday, 23 October 2009
Failed to create feature receiver object from assembly
Remember that the class that inherits from SPFeatureReceiver need to be "Public"
Thursday, 8 October 2009
User Profile Import stuck on "Enumerating"
I keep an eye on some of our clients SharePoint farms and today I came across an error in the profile import for one of the SSPs. “The user profile database connection cannot be made, because of error 0x80004005” is displayed on the “User Profiles and Properties” page and the “Profile import status” was only displaying “Enumerating”.
The import cannot be stopped, if the server is restarted then the error doesn´t disappear according to several posts in newsgroups.
So what to do? I checked and double-checked the SSP database and the values in the Profile_Stats, MIPObjects and MIPScheduleJob tables which all had values related to the Profile Import. But nothing that I did could solve the problem.
But then I remembered that the crawler application is based on the good old Indexing Service which means that the registry is also used to store settings. So after some digging I found the solution by changing a value in the registry for the crawler.
Open the registry editor. Browse to “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications”. Here you will find a key for each SSP in the farm. Drill down to "\Gather\ProfileImport\ContentSources\0" (which is the Full Import) and check the key “CrawlNumberInProgress”. If it´s not “0xffffffff” then the number displayed corresponds to a key under the branch “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\\Gather\ProfileImport\Crawls”.
I changed the number in the key “CrawlNumberInProgress” to “0xffffffff” and then restarted the “Office SharePoint Server Search” service for the settings to be applied.
The error message disappeared from “User Profiles and Properties” and I could start a new full import to the “User Profile Import”
Disclaimer: remember to backup your registry before making any changes. I am not responsible for your system damages because of any registry errors
The import cannot be stopped, if the server is restarted then the error doesn´t disappear according to several posts in newsgroups.
So what to do? I checked and double-checked the SSP database and the values in the Profile_Stats, MIPObjects and MIPScheduleJob tables which all had values related to the Profile Import. But nothing that I did could solve the problem.
But then I remembered that the crawler application is based on the good old Indexing Service which means that the registry is also used to store settings. So after some digging I found the solution by changing a value in the registry for the crawler.
Open the registry editor. Browse to “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications”. Here you will find a key for each SSP in the farm. Drill down to "
I changed the number in the key “CrawlNumberInProgress” to “0xffffffff” and then restarted the “Office SharePoint Server Search” service for the settings to be applied.
The error message disappeared from “User Profiles and Properties” and I could start a new full import to the “User Profile Import”
Disclaimer: remember to backup your registry before making any changes. I am not responsible for your system damages because of any registry errors
Monday, 5 October 2009
Subscribe to:
Posts (Atom)