Windows SharePoint Services Search – Required on Farm, not running

We had this problem using MOSS 2007 SP2 when we first installed SharePoint. We tried starting it with an administrators account as well as changing the Indexing schedule with no luck. What we ended up doing was detaching the WSS_Search_<your server name> database and taking it offline in SQL, then when we went back in to Central Administration – Operations – Services on Server and selected Start next to that service, we put in a new database since it will give you an Unknown Error if you try to use the same name, and it started fine.

Leave a comment

Posted by on July 26, 2010 in SharePoint Installation


Configuration Failed on MOSS 2007 SP2

We were trying to apply Service Pack 2 to our MOSS 2007 installation. Once we installed the service pack we tried to run the config wizard and it would get to task 5 and the configuration would fail. Then we would get the following events in the Event Viewer:

Event ID: 100

Source: SharePoint Products and Technologies Configuration Wizard


Configuration of SharePoint Products and Technologies failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_7_20_2010_8_9_2_615_239088506.log, fix the problem, and run this configuration wizard again.

Event ID: 104

Source: SharePoint Products and Technologies Configuration Wizard


Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServiceInstanceInConfigDB(Boolean provisionTheServiceInstanceToo, String serviceInstanceRegistryKeyName, Object sharepointServiceObject)

at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServiceInstances(Boolean provisionTheServiceInstancesToo, String serviceRegistryKeyName, Object sharepointServiceObject)

at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServices(Boolean provisionTheServicesToo)

at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.Run()

at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Event ID: 2426

Source: Windows SharePoint Services 3 Search


Advise Status Change failed. The system is probably low on resources. Free up resources and restart the service.

Context: Application ‘Search’, Catalog ‘index file on the search server Search’



Event ID: 10029

Source: Windows SharePoint Services 3 Search


Error backing up registry hive to the configuration database.

Context: Application ‘Search index file on the search server’


Access is denied. (0x80070005)

Event ID: 10030

Source: Windows SharePoint Services 3 Search


Error importing registry hive from the configuration database and into the registry.

Context: Application ‘e1daee80-85f6-4538-9358-59e286d2c897’


Access is denied. (0x80070005)

Event ID: 6066

Source: Office SharePoint Server


Couldn’t Register with Load Balancer: Unable to connect to the remote server

Event ID: 6102

Source: Office SharePoint Server


LoadBalancer.RegisterLauncher failed: Unable to connect to the remote server

All of these were caused by one registry key:

HK_local_machine\software\microsoft\shared tools\web server extensions\12.0\wss\services\

 Under that key, find the service that it was failing on and delete that key. In our case it was Windows SharePoint Services Search. We backed up that registry key and then deleted it. We reran the configuration wizard and it worked.

I hope this helps!!

Leave a comment

Posted by on July 22, 2010 in SharePoint Installation


Event ID: 6482 Source: Office SharePoint Server

We were getting this error every minute on our MOSS 2007 server:

Here are the error details:

Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (6e8fd438-2b7f-4672-a1fc-f206f342dc4a).

Reason: Object c46d04b6-690e-4ced-a1fd-18bbf492e421 not found.

Techinal Support Details:

System.Collections.Generic.KeyNotFoundException: Object c46d04b6-690e-4ced-a1fd-18bbf492e421 not found.

at Microsoft.Office.Server.Search.Administration.SearchApi.get_App()

at Microsoft.Office.Server.Search.Administration.SearchApi.SetUsersPermittedToQuery(String[] userNames, Boolean force)

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

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

Here’s how I fixed this on our server:

I went to the Services on Server page from Central Administration and clicked on the Office SharePoint Server Search link that opened the Configure Office SharePoint Server Search Service Settings on server <my server> page.

I entered the password for my search service and clicked OK.  Then I stopped and started the Search service in the Services mmc.

That ended up giving me an Application Log entry that said Successfully imported the application configuration snapshot into the registry.

Now, I search the registry and I find the application under HKLM\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\<My Search App GUID>

I restart IIS and now, I’m getting search results.

1 Comment

Posted by on July 22, 2010 in SharePoint Common Issues


Explorer View requires Internet Explorer 5.0 or greater and Web Folders or Your client does not support opening this list with Windows Explorer.

If you receive this message in SharePoint when attempting to use the Explorer View option you should try enabling the WebClient service (see below image):

If you’re unsure of how to get to your Services list simply go to Start, Settings, Control Panel and open your Administrative Tools then click on Services. This may vary depending on whether you’re using XP, Vista or Windows 7 but it should be enough to get you going in the right direction.

If you’re using MOSS 2007 you may receive this message:

“Your client does not support opening this list with Windows Explorer”

If enabling the WebClient service alone doesn’t fix the issue check the following registry key:


Double click the AuthForwardServerList value and type in your servers URL and click OK, If you do not have that value then right-click and go to New – Multi-String Value and type in AuthForwardServerList. Then you can add your URL.

Then restart the WebClient service and retry the Explorer View

See also:

Hope this helps!

Leave a comment

Posted by on February 8, 2010 in SharePoint Common Issues


Unable to Load Workbook – MOSS 2007

We had a user upload an Excel document and when I opened it, it worked fine but when other users opened it they received the following:


The workbook that you selected cannot be loaded because it contains the following features that are not supported by Excel Services:

Comments, ActiveX controls, Shapes, Text Boxes, Pictures, WordArt, Clip Art, Embedded OLE objects, Ink Annotations, Forms Toolbar controls, Control Toolbox controls, Charts that are part of a group, Signature Lines, or Camera objects

Contact the workbook author.

This really threw me off but ultimately what I found was that the Excel spreadsheet was created in Office 2007 with the .xlsx extension and the users having issues were trying to open it in Office 2003. It’s a very simple solution to a weird SharePoint issue. Another solution if this is not your issue is that IE is opening the document via the Web Browser instead of directly through Excel. If so, check your Internet Options and Programs list to see what the default program those file types are opening in.

I did find that there are certain things that aren’t compatible with SharePoint using Excel such as external data tables but the only good info I could find on this was to convert them to pivot tables and they should work although I have not tested this. Here is a link for the following error:

The workbook that you selected cannot be loaded because it contains the following features that are not supported by Excel Services:

External data ranges (also called data ranges)

Contact the workbook author.

Leave a comment

Posted by on October 29, 2009 in SharePoint Common Issues


Event ID: 6482 Office SharePoint Server & Event ID: 7034 Windows SharePoint Services 3

When firing up the Excel Calculation Services  on a new farm, if you get the following “Handle is Invalid” error:
System.Security.Cryptography.CryptographicException: The handle is invalid.

   at System.Security.Cryptography.Utils.CreateProvHandle(CspParameters parameters, Boolean randomKeyContainer)
   at System.Security.Cryptography.Utils.GetKeyPairHelper(CspAlgorithmType keyType, CspParameters parameters, Boolean randomKeyContainer, Int32 dwKeySize, SafeProvHandle& safeProvHandle, SafeKeyHandle& safeKeyHandle)
… and so on …

You need to set permissions as follows:
“C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys”
Add Local Administrators – Full

In the Security tab of the folder’s Properties:

Click Advanced

Click the Owner tab

Ensure the current owner says Administrators, if not, click it in the “Change owner to” box

Check the checkbox that says “Replace owner on subcontainers and objects”

Hit Apply & Ok

On the Permissions Tab

Add the Everyone group (if you haven’t already) by using the Add button, type Everyone, and click OK

Highlight the Everyone group and click Edit

Ensure “Allow” is checked for all the boxes and click OK

Check the box that says “Replace permission entries on all child objects with entries shown here that apply to child objects”

Click Apply, then Yes on the warning to continue

Click OK

Then click Apply & OK on the MachineKeys Properties window.

This should allow the Excel Calculation Service to start in Central Admin.

Leave a comment

Posted by on August 13, 2009 in SharePoint Common Issues


Event ID: 6641 Office SharePoint Server



I have run into this problem even when I have not changed the password.  I tried the fix to add the service account to the backup operators group and that did not completely fix the problem.  Additionally, I have notice that I have had a lot of other mysterious SharePoint Server Errors  What you need to do to correct this problem is:

1.     Go to Central Administration > Operations > Service Accounts

2.     Click on the Web Application Pool

3.     Under Web Service choose Windows SharePoint Service Web Application.

4.     Under Application Pool choose your Shared Services Provider application pool account. This should populate your application pool account under configurable.

5.    Re-enter your password and click OK. You need to perform an IIS reset for this to take effect.


Posted by on July 28, 2009 in SharePoint Common Issues