Tuesday 7 December 2010

Query Server Not Responding

I Recently installed the "republished" October Cumulative Updates for SharePoint 2010. I then discovered that Search was not working. Crawl was going on forever and I was getting the message "Query Server not responding" therefore no propogation was happening . All my Search components were installed on a single server at this point. The Crawl component was also reporting a "Recovering" status. I added a new Query component and deleted the original one but this did not fix the problem.

I then remembered that I had seen something similar in SharePoint 2007 where updating the farm with a cumulative update would cause the Adobe PDF iFilter settings to be lost from the registry which in turn would break search. I have blogged this previously  http://mrvsharepoint.blogspot.com/2009/03/moss-february-2009-cumulative-updates.html

It seems that this is still the case with SharePoint 2010 and certain Cumulative updates. I went back and added the PDF iFilter  settings back into the registry (http://support.microsoft.com/kb/2293357), rebooted the server, did a full crawl and it all worked again.

Thursday 11 November 2010

FIM Service Stops after Import and User Profile Synch Connection Disappears

I opened a support call  with Microsoft recently where miiserver.exe would fault after an incremental import every night which would cause the FIM services to stop. This would result in the User Profile Synch connection disappearing. Restarting the FIM services would fix the problem but obviously this wasn't ideal.

A description of the issue is as follows:

At 1am every night the Incremental User Profile Import runs. Following this the FIM Service enters a "Stopped" state. Inspection of the System Log indicates:

EVENT ID: 1000

Faulting application name: miiserver.exe, version: 4.0.2450.11, time stamp: 0x4c3e8067 Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdfe0 Exception code: 0xe053534f Fault offset: 0x000000000000aa7d Faulting process id: 0x%9 Faulting application start time: 0x%10 Faulting application path: %11 Faulting module path: %12 Report Id: %13

The fix as suggested by Microsoft was as follows:
  
“Please add the following line (highlighted) to the miisserver.exe.config (C:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\Bin) and see if it helps….restart the FIM services (through services.msc) and re-run incremental sync." 

 <?xml version="1.0" encoding="UTF-16"?>
<configuration>
        <configSections>
                                <section name="resourceManagementClient"

type="Microsoft.ResourceManagement.WebServices.Client.ResourceManagementClientSection, Microsoft.ResourceManagement"/>
        </configSections>
                <startup>
                                <requiredRuntime version="v2.0.50727"></requiredRuntime>
                                <supportedRuntime version="v2.0.50727"></supportedRuntime>
                </startup>
  <runtime>
    <disableStackOverflowProbing enabled="true"/>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="3.3.0.0" newVersion="4.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

 An explanation for the line that resolves the problem can be found here at http://msdn.microsoft.com/en-us/library/ms149581.aspx and is due to the stack size.



Friday 1 October 2010

Event ID 3 ForeFront Identity Manager Error

After applying the August 2010 Cumulative Update for SharePoint 2010, I started to see the following error in Application Event Logs around every 30 seconds. They occurred on the server that was running the FIM Services:

EVENT ID 3

Provider: ForeFront Identity Manager

Microsoft.ResourceManagement.Service: Microsoft.ResourceManagement.Workflow.Hosting.WorkflowManagerException: Forefront Identity Management Service does not support workflows of type 'Microsoft.ResourceManagement.Workflow.Activities.SequentialWorkflow, Microsoft.ResourceManagement, Version=4.0.2450.9, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. at Microsoft.ResourceManagement.Workflow.Hosting.HostActivator.ActivateHost(ResourceManagementWorkflowDefinition workflowDefinition) at Microsoft.ResourceManagement.Workflow.Hosting.WorkflowManager.StartWorkflowInstance(Guid workflowInstanceIdentifier, KeyValuePair`2[] additionalParameters

After a call to Microsoft I was told that they are "aware of the issue" and a hotfix and associated KB article will be released very soon. The product group stated that these "errors are benign".


Verdict: Harmless but annoying