Skip to main content
Nintex Community Menu Bar

Same error message on different sites

  • August 25, 2015
  • 10 replies
  • 19 views

Forum|alt.badge.img+2

Hello Community,

I have a weird problem with my workflows.

Sometimes if I want to restart a workflow for a file or a list field I get an error message like this.

112167_pastedImage_0.png

If I try it a couple hours later it maybe works even if I didn`t change anything.

Has anybody an idea what`s the reason for this issue?

Thanks for helping me out.

Mark

10 replies

Forum|alt.badge.img+9
  • August 25, 2015

If error occured you have to analyze ULS-logs on sharepoint servers.

Open actual logfile with an ULS-Viewer, e.g. Download ULS Viewer from Official Microsoft Download Center , and filter logfile by Correlation-ID.


Forum|alt.badge.img+17
  • Nintex Partner
  • August 26, 2015

How is your farm configured by server role? Are there multiple servers?


Forum|alt.badge.img+2
  • Author
  • August 26, 2015

We have 2 WFE, 2 Applicaton and a WAC Server.


Forum|alt.badge.img+2
  • Author
  • August 26, 2015

I did that already. But there was no message which helped with the issues.


Forum|alt.badge.img+11
  • August 27, 2015

I would add log history actions to see how far you get in the workflows.


Forum|alt.badge.img+17
  • Nintex Partner
  • August 27, 2015

Is the Web Front End service and workflow timer service running on the Application servers?


Forum|alt.badge.img+2
  • Author
  • August 28, 2015

Yes, they are running both.


Forum|alt.badge.img+2
  • Author
  • August 28, 2015

The issue is not with the Workflows iteself. They are running.

But if I want to restart them, the error message returns.

So I think a log history action won`t help much. Or am I wrong?


Forum|alt.badge.img+11
  • August 28, 2015

I was thinking maybe if you hit the action causing the problem it may help with troubleshooting the issue. It may even give an error where the logs aren't.


Forum|alt.badge.img+2
  • Author
  • August 31, 2015

Good point. You`re right. I`ll try it as soon as possible.

I tried it last week on our test system. There was no issue. Everything is the same. But the error message returns only on our live system.