none
Could not load file or assembly 'System.WorkflowServices RRS feed

  • Question

  • Hi All,

     I am currently running 4.0.3606.2 and I am getting the error below on object exports on the FIM MA.  It seems that I am somehow missing a file although I don't know which one.  The main question at this point: Is there a reliable way to tell whether this is a Sync server issue or a Portal server issue?

    Following that,  I was thinking of trying to re-install the last patch to get the missing file, but I'm not sure if that is a good idea or not.  Any thoughts would be appreciated! 

    Thanks!

    Bryan

    There is an error executing a web service object creation request. 
    Type: System.IO.FileNotFoundException 

    Message: Could not load file or assembly 'System.WorkflowServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

    Stack Trace:    at Microsoft.ResourceManagement.WebServices.DurableServiceClient`1.InitializeContextManagement()
       at Microsoft.ResourceManagement.WebServices.ResourceFactoryClient.Open()
       at Microsoft.ResourceManagement.WebServices.Client.ResourceManagementClient.CreateResourceFactoryClient(ContextualSecurityToken securityToken, EndpointAddress resourceFactoryAddress)
       at Microsoft.ResourceManagement.WebServices.Client.ResourceTemplate.CreateResource(Guid identifier, String synchronizationSequenceIdentifier)
       at MIIS.ManagementAgent.RavenMA.ExportObjectCreation(DataSourceObject dsObject, SchemaManager schemaManager, Boolean specifyObjectId)
       at MIIS.ManagementAgent.RavenMA.Export(DataSourceObject dsObject)

    Inner Exception: Could not load file or assembly 'System.WorkflowServices, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

    Tuesday, September 11, 2012 4:35 PM

Answers

  • RavenMA appears to be an internal name for the FIM Service MA -- it is found in the FIM Synchronization Service's mmsmafim.dll.

    Are you sure your FIM Synchronization Service is running under the .NET 4 Framework (and not 2.0 / 3.5)?  The requested version of System.WorkflowServices lives in the NET 4 GAC only.

    • Marked as answer by B_Easton Thursday, September 13, 2012 2:21 PM
    Wednesday, September 12, 2012 3:19 PM

All replies

  • From the namespace 'Microsoft.ResourceManagement.WebServices' it's a good guess that this is a FIM Service issue (the portal runs on top of the FIM service).

    You may have a problem with a workflow that is suppose to run on based on what you're trying to export.

    What is this RavenMA doing?


    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt

    Tuesday, September 11, 2012 5:58 PM
  • As to what RavenMA is, I have no idea.  I have no MA's named anything even close to that and it doesn't fit our naming convention for MA's anyway.  I will take a look at the workflows though to see if I can identify anything that might be the culprit but we don't have a lot of workflow happening, mostly things like populating a few groups, etc.  Also, this is a QA environment, so there haven't been many changes recently as far as FIM is concerned.  The last major thing that was changed was the version upgrade to 4.0.3606.2 and it was tested and running fine after that upgrade.

    Thanks,
    Bryan

    Tuesday, September 11, 2012 7:14 PM
  • I belive this is referring to the FIM MA. You stated you were running version 4.0.3606.2, check your service config file and verify if the binding redirect statements are present at bottom of file. These should be there after patch has been applied. I have seen these get wiped out when service tracing is enabled due to statements being overwritten.

    This is what the end of my file looks like

    <

    runtime>

    <

    assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

    <

    dependentAssembly>

    <

    assemblyIdentity name="FunctionLibrary" publicKeyToken="31bf3856ad364e35" culture="neutral" />

    <

    bindingRedirect oldVersion="4.0.0.0-4.65535.65535.65535" newVersion="4.0.3617.2" />

    </

    dependentAssembly>

    <

    dependentAssembly>

    <

    assemblyIdentity name="Microsoft.IdentityManagement.Activities" publicKeyToken="31bf3856ad364e35" culture="neutral" />

    <

    bindingRedirect oldVersion="4.0.0.0-4.65535.65535.65535" newVersion="4.0.3617.2" />

    </

    dependentAssembly>

    <

    dependentAssembly>

    <

    assemblyIdentity name="Microsoft.ResourceManagement.Automation" publicKeyToken="31bf3856ad364e35" culture="neutral" />

    <

    bindingRedirect oldVersion="4.0.0.0-4.65535.65535.65535" newVersion="4.0.3617.2" />

    </

    dependentAssembly>

    <

    dependentAssembly>

    <

    assemblyIdentity name="Microsoft.ResourceManagement" publicKeyToken="31bf3856ad364e35" culture="neutral" />

    <

    bindingRedirect oldVersion="4.0.0.0-4.65535.65535.65535" newVersion="4.0.3617.2" />

    </

    dependentAssembly>

    <

    dependentAssembly>

    <

    assemblyIdentity name="Microsoft.IdentityManagement.WFExtensionInterfaces" publicKeyToken="31bf3856ad364e35" culture="neutral" />

    <

    bindingRedirect oldVersion="4.0.0.0-4.65535.65535.65535" newVersion="4.0.3617.2" />

    </

    dependentAssembly>

    </

    assemblyBinding>

    </

    runtime>This definitely looks like issue when exporting to FIM MA. Do you get errors in the sync manager console?
    Wednesday, September 12, 2012 3:52 AM
  • Thanks for the suggestion.  Here is what mine looks like, I think it looks fine.  Yes, I get the errors in the sync console on export to FIM MA. 

    <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
        <dependentAssembly>
          <assemblyIdentity name="FunctionLibrary" publicKeyToken="31bf3856ad364e35" culture="neutral" />
          <bindingRedirect oldVersion="4.0.0.0-4.65535.65535.65535" newVersion="4.0.3606.2" />
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.IdentityManagement.Activities" publicKeyToken="31bf3856ad364e35" culture="neutral" />
          <bindingRedirect oldVersion="4.0.0.0-4.65535.65535.65535" newVersion="4.0.3606.2" />
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.ResourceManagement.Automation" publicKeyToken="31bf3856ad364e35" culture="neutral" />
          <bindingRedirect oldVersion="4.0.0.0-4.65535.65535.65535" newVersion="4.0.3606.2" />
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.ResourceManagement" publicKeyToken="31bf3856ad364e35" culture="neutral" />
          <bindingRedirect oldVersion="4.0.0.0-4.65535.65535.65535" newVersion="4.0.3606.2" />
        </dependentAssembly>
        <dependentAssembly>
          <assemblyIdentity name="Microsoft.IdentityManagement.WFExtensionInterfaces" publicKeyToken="31bf3856ad364e35" culture="neutral" />
          <bindingRedirect oldVersion="4.0.0.0-4.65535.65535.65535" newVersion="4.0.3606.2" />
        </dependentAssembly>
      </assemblyBinding>
    </runtime>

    Wednesday, September 12, 2012 2:13 PM
  • RavenMA appears to be an internal name for the FIM Service MA -- it is found in the FIM Synchronization Service's mmsmafim.dll.

    Are you sure your FIM Synchronization Service is running under the .NET 4 Framework (and not 2.0 / 3.5)?  The requested version of System.WorkflowServices lives in the NET 4 GAC only.

    • Marked as answer by B_Easton Thursday, September 13, 2012 2:21 PM
    Wednesday, September 12, 2012 3:19 PM
  • .NET 4 was installed and seemed to be in order.  I figured maybe re-installing might work.  I re-installed the .NET 4 Framework and that did the trick.  Not sure how I initially lost a file or something but it is working fine now.  Thanks for the suggestion Steve!
    Thursday, September 13, 2012 2:21 PM