none
Event ID 3 with Approval activity

    Question

  • Hi

    Has anyone had problem with Approval activity on FIM 2010R2 SP1 (running on SPS Foundation 2013 and Windows Server 2012 - just for information), where workflow which contains approval activity just fails to initialize and logs on Event with ID 3 (pretty generic):

    Error message from Event ID 3:

    Microsoft.ResourceManagement.Service: System.NullReferenceException: Object reference not set to an instance of an object.
       at Microsoft.ResourceManagement.Workflow.Hosting.HostActivator.ActivateHost(ResourceManagementWorkflowDefinition workflowDefinition, Boolean suspendWorkflowStartupAndTimerOperations)
       at Microsoft.ResourceManagement.Workflow.Hosting.WorkflowManager.StartWorkflowInstance(Guid workflowInstanceIdentifier, KeyValuePair`2[] additionalParameters)

    First I thought that it is some my activity, but it happens even if only activity on a workflow is Approval activity. Once approval activity is removed from the workflow this problem is also gone.


    Tomek Onyszko, memberOf Predica FIM Team (http://www.predica.pl), IdAM knowledge provider @ http://blog.predica.pl

    Monday, May 20, 2013 9:12 PM

Answers

  • OK - it looks like a bug when FIM is running on SPS Foundation 2013 or under some other condition in our setup. If anyone could confirm that probably would be helpful. 

    Reason for a problem:

    When new approval workflow is created and approval activity is placed in this workflow it contains following element in a XOML definition:

    (...)

    xmlns:ns1="clr-namespace:System.Workflow.Activities;Assembly=System.WorkflowServices, Version=3.5.0.0 (...)

    Above is from standard approval workflow delivered with FIM. But in custom authorization workflow it is as follows:

    (...) xmlns:ns1="clr-namespace:System.Workflow.Activities;Assembly=System.WorkflowServices, Version=4.0.0.0, (...)

    Now the challenge is - spot the difference :).

    If one will edit standard approval workflow and change something and save it, XOML will get "upgraded" as well and this will start to fail. 

    Now where I can re-claim 2 lost days on this :)? 


    Tomek Onyszko, memberOf Predica FIM Team (http://www.predica.pl), IdAM knowledge provider @ http://blog.predica.pl

    Tuesday, May 21, 2013 12:23 PM

All replies

  • OK - it looks like a bug when FIM is running on SPS Foundation 2013 or under some other condition in our setup. If anyone could confirm that probably would be helpful. 

    Reason for a problem:

    When new approval workflow is created and approval activity is placed in this workflow it contains following element in a XOML definition:

    (...)

    xmlns:ns1="clr-namespace:System.Workflow.Activities;Assembly=System.WorkflowServices, Version=3.5.0.0 (...)

    Above is from standard approval workflow delivered with FIM. But in custom authorization workflow it is as follows:

    (...) xmlns:ns1="clr-namespace:System.Workflow.Activities;Assembly=System.WorkflowServices, Version=4.0.0.0, (...)

    Now the challenge is - spot the difference :).

    If one will edit standard approval workflow and change something and save it, XOML will get "upgraded" as well and this will start to fail. 

    Now where I can re-claim 2 lost days on this :)? 


    Tomek Onyszko, memberOf Predica FIM Team (http://www.predica.pl), IdAM knowledge provider @ http://blog.predica.pl

    Tuesday, May 21, 2013 12:23 PM
  • hi,

    have you ever found a solution for this Problem?

    BR,

    juvi

    Wednesday, July 24, 2013 11:05 AM
  • Juvi

    At this point the only work around is to update the XOML, If you can open a ticket so we can get the issue logged

    David

    Saturday, October 05, 2013 5:17 PM
    Moderator
  • Juvi

    At this point the only work around is to update the XOML, If you can open a ticket so we can get the issue logged

    David

    David;

    I'm getting this issue also.

    I have the FIM Sync Service and FIM Service on Server A (Windows 2008 R2)

    I have the FIM Portal on Server B (Windows Server 2012 w/ SharePoint 2013) 

    What is the resolution for this or troubleshooting steps?

    Thanks;

    Jonathan

    Thursday, November 21, 2013 3:37 PM
  • Juvi

    At this point the only work around is to update the XOML, If you can open a ticket so we can get the issue logged

    David

    David;

    I'm getting this issue also.

    I have the FIM Sync Service and FIM Service on Server A (Windows 2008 R2)

    I have the FIM Portal on Server B (Windows Server 2012 w/ SharePoint 2013) 

    What is the resolution for this or troubleshooting steps?

    Thanks;

    Jonathan

    After Changing the XOML to 3.5 Framework for System.WorkflowServices in the XOML I get Event ID 32 in the logs:


    There is no specific exception reported by the mail server, that is where the text ends.

    FIM is sending notification emails, so I doubt it is an issue with Exchange Connectivity.

    Any ideas?

    I've opened a ticket with PSS.

    Thanks!

    -Jon

     
    Friday, November 22, 2013 1:32 PM
  • Have you tried to send e-mail as account of FIM Service as per your configuration (SMTP or Exchange)? I mean start process as this account and then try send e-mail as usual (remember that if Exchange is used it uses Exchange Web Service and not client like Outlook etc.). There might be something with your configuration or permissions which causes it to fail. At one of my customers it was Exchange certificate which becomes not-trusted. 

    Anyway - that would be my first troubleshooting step.


    Tomek Onyszko, memberOf Predica FIM Team (http://www.predica.pl), IdAM knowledge provider @ http://blog.predica.pl

    Saturday, November 23, 2013 11:02 PM
  • Have you tried to send e-mail as account of FIM Service as per your configuration (SMTP or Exchange)? I mean start process as this account and then try send e-mail as usual (remember that if Exchange is used it uses Exchange Web Service and not client like Outlook etc.). There might be something with your configuration or permissions which causes it to fail. At one of my customers it was Exchange certificate which becomes not-trusted. 

    Anyway - that would be my first troubleshooting step.


    Tomek Onyszko, memberOf Predica FIM Team (http://www.predica.pl), IdAM knowledge provider @ http://blog.predica.pl

    Tomasz;

    Thank you for your reply. I've logged in to OWA as the FIMService account and it is sending notification emails fine via the webservice. The issue I'm having appears related to Approval emails only.

    Thanks Again;

    Jon

    Monday, November 25, 2013 8:57 PM
  • Thanks i had the same problem using FIM R2 and Sharepoint 2013 and changing from 4.0.0.0 to 3.5.0.0 helped for me!

    Ulf Lindström

    Friday, March 07, 2014 2:44 PM
  • That helped me aswell , thanks!

    Tuesday, July 01, 2014 1:31 PM