Unable to save workflow configuration

(0) Share

Report

Posted on by Trung Nguyen

1,245

Hi all,

I'm facing a problem with workflow in AX 2012 R2. After I create workflow, I click on button "Save and close" in order to save workflow. Unfortunately, the workflow is not saved.

I looked into Event Viewer --> Applications and Services log --> Microsoft AX workflow and I saw these errors:

Error 1:

Workflow threw an exception for the following reason: The server has rejected the client credentials.

Error 2:

Workflow threw an exception for the following reason: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.

Error 3:

Exception thrown in : Workflow configuration The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state

Error 4:

Workflow threw an exception for the following reason: Exception has been thrown by the target of an invocation.

Does anyone face this problem? Please help me to fix it

Thanks in advance

Trung

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (0)

Tommy Skaue Moderator on at

Like (0)

Report

Hi

Please make sure the entire AOT compile without errors (just errors). Make sure CIL compiles. Restart the AOS.

Make sure the client configuration has refreshed WCF bindings with proper endpoint principals.

Was this reply helpful? Yes No
Trung Nguyen 1,245 on at

Like (0)

Report

Hi,

I compiled AOT without error, have full CIL generation and restart AOS but nothing changed. Do you have any ideas?

BR,

Trung

Was this reply helpful? Yes No
Trung Nguyen 1,245 on at

Like (0)

Report

Hi,

No one face this error?

Please help me.

Was this reply helpful? Yes No
Martin Dráb 237,970 Most Valuable Professional on at

Like (0)

Report

"The server has rejected the client credentials" sounds like a clear indication of what's wrong. Please verify that workflow execution account is configured correctly.

See more about workflow setup in Configure the workflow system [AX 2012].

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hello Trung,

I had this problem before and here is the fix for it:

wizardofax.wordpress.com/.../unable-to-save-workflow-configuration-in-dynamics-ax2012

Unable to save an existing workflow to which you are making small changes, is a known issue at Microsoft the good thing is that it can be fixed via a simple code change on the “canclose” method of the workflowEditorHost form.

If you go to the AOT > Forms > WorkflowEditorHost. Find the CanClose() method and change the code:

==============

From this:

==============

public boolean canClose()

{

boolean ret;

ret = super();

if (saveOnClose)

{

ret = modelEditorControl.SaveAndClose();

}

return ret;

}

===========================

To This

===========================

public boolean canClose()

{

boolean ret;

ret = super();

if (saveOnClose)

{

try

{

ret = modelEditorControl.SaveAndClose();

}

catch (Exception::Error)

{

info(“Caught ‘Exception::Error’.”);

}

catch (Exception::CLRError)

{

info(“Caught ‘Exception::CLRError’.”);

netExcepn = CLRInterop::getLastException();

info(netExcepn.ToString());

}

}

return ret;

}

=======================================

After making this change then do the following:

1. Run an Incremental CIL.

2. Compile Forward on the NumberSeq class (Right-click > Add-in > Compile Forward).

3. Generate an incremental CIL.

I hope this helps!

Was this reply helpful? Yes No
Jose Nedumpuram 10 on at

Like (0)

Report

Hi,

I am facing the same issue in AX2012 R3, what was the solution which you had applied to solve the issue.

Was this reply helpful? Yes No
Jose Nedumpuram 10 on at

Like (0)

Report

I have tried all the methods mentioned above, but no success...

Was this reply helpful? Yes No
Kevin Roos 265 on at

Like (0)

Report

Any updates on this issue?

I seem to be having the same problem om 2012R3CU8

Was this reply helpful? Yes No
Suggested answer

Jose Nedumpuram 10 on at

Like (0)

Report

Hi Kevin,

I hope you have resolved the issue, if not pls try the following which solved my issue:

made change in registrty :-

social.technet.microsoft.com/.../event-6037-lsasrv

This settings should fix it:

HKLM\system\CurrentControlSet\Services\Lanmanserver\parameters

DisableStrictNameChecking:DWORD=1

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

DisableLoopbackCheck:DWORD=1

interesting...

just googled around these values.

after you set DisableStrictNameChecking=1 and reboot computer, you will have two options.

more secure... Update BackConnectionHostNames=.

or less secure... set DisableLoopbackCheck=1

both ways described in kb support.microsoft.com/.../896861

Was this reply helpful? Yes No
Kevin Roos 265 on at

Like (0)

Report

Hi Jose,

Thank you for the feedback!

I'm not sure if the environment is still existing because it was for pre sales purposes but if I encounter the issue I'll check it ;-)

Kind regards,

Kevin

Was this reply helpful? Yes No