Workflow execution account failed to log on

(0) Share

Report

Posted on by Community Member

Hello everyone,

We configured a timesheet approval workflow, very simple. The problem is when we submit it for approval it gets stuck in the "stopped" status.

I then checked the event viewer, and I saw that everytime I launch the review of the timesheet, this error appears in the event viewer log :

Object Server 04: An error has occurred in the services framework. Method: AifMessageInspector::AfterReceiveRequest. Error: System.ServiceModel.FaultException: Failed to logon to Microsoft Dynamics AX.
à Microsoft.Dynamics.Ax.Services.AxServiceOperationContext.InitializeSession()
à Microsoft.Dynamics.Ax.Services.AxServiceOperationContext.InitializeContext()
à Microsoft.Dynamics.Ax.Services.AxServiceOperationContext.Attach(OperationContext owner)
à System.ServiceModel.ExtensionCollection`1.InsertItem(Int32 index, IExtension`1 item)
à System.Collections.Generic.SynchronizedCollection`1.Add(T item)
à Microsoft.Dynamics.Ax.Services.AifMessageInspector.AfterReceiveRequest(Message& request, IClientChannel channel, InstanceContext instanceContext)

So I guessed it was the workflow execution account, I tried changing it several times with no luck.

Please if you have crossed this type of error I'd be greatfull if you could help!!

Thank you.

Slim Rouissi

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Vilmos Kintera 46,149 on at

Like (0)

Report

Do you have any other workflows which are work fine? Is this the only workflow, so you did not have it working before?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

No we don't have any other workflow running. This is the first one we created.

Was this reply helpful? Yes No
Vilmos Kintera 46,149 on at

Like (0)

Report

Did you specify a workflow execution account?

technet.microsoft.com/.../gg732189.aspx

Have you added it and enabled it as an AX user with System User, System Administrator (required!) and Business Connector security roles?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes of course, I even followed this fix, and put the AOS service account as workflow exectuion, added it as a user and gave it administrator rigths.

[View:https://axmartina.wordpress.com/2013/10/30/error-failed-to-logon-to-microsoft-dynamics-ax/:750:50]

I just added the Business Connector security role and tried resuming the workflow, but it still goes "Stopped"

and I get the same error in the event viewer :

An error has occurred in the services framework. Method: AifMessageInspector::AfterReceiveRequest. Error: System.ServiceModel.FaultException: Failed to logon to Microsoft Dynamics AX.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

Okay guys, solved it. Apparently someone specified an Active Directory group as workflow execution account and runned the Workflow infrastructure configuration wizard using that account which caused that "Failed to log on" error.

The solution is to remove the batch jobs from the queue, choose an AX user ( Active Directory User ) as workflow execution account, and finally run the Workflow infrastructure configuration wizard again.

Was this reply helpful? Yes No
Vilmos Kintera 46,149 on at

Like (0)

Report

It is good to see you have been able to resolve the issue.

Please mark my response an answer for your questions, I have stated after the link that you need the workflow execution account to be an actual AX user (and obviously not a user group).

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

Hi Vilmos,

Thank you for your response, but this wasn't the right answer, because the account had already been changed to an AX user before my intervention. I just tried the fix of adding the AOS service account as user, with admin privilege and used it as workflow execution account, and it didn't work. I still got the same error.

The real link that helped is this thread :

community.dynamics.com/.../129265

Because the wrong account was selected when running Workflow infrastructure configuration, and it kept using the user group, instead of the actual specified Workflow Execution account ( which was already an AX user ).

So i just had to delete the workflow batch jobs and run the Workflow infrastructure configuration again!

Was this reply helpful? Yes No