You are viewing limited content. For full access, please sign in.

Question

Question

Root Element Missing when publishing wokflows

asked on May 15, 2018

Since upgrading Laserfiche from 10.2 to 10.3 we have been having uncharacteristic issues with workflow.
We have also upgraded workflow to the latest issue.
We are unable to publish any new workflows or even republish existing workflows.
I have also tried publishing empty workflows but still the same.
The errors we are getting are either "Object reference not set to an instance of an object." or "Root element is missing."

I have come across this issue before but none of my previous solutions are working.
The only thing that works is restarting the server.
But after a few minutes it just comes back again.
Since this is a production server restarting the server is not an option.

0 0

Replies

replied on May 15, 2018

It sounds like a potential rights issue that's best investigated through Tech Support. Please attach the full error message from the Errors pane of the Designer.

0 0
replied on May 16, 2018

Hi Miruna.


Should I log this as a support call?

0 1
replied on May 16, 2018

Hi Miruna.

We are now getting the same issue within an IFrame to web access from Forms.
"Object reference not set to an instance of an object."

I have attached the requested error.

0 0
replied on December 10, 2019 Show version history

Ran into this the other day. Publishing a workflow that was already published, even with no changes made to the workflow, returned "Object reference not set to an instance of an object." Creating a new workflow and trying to publish it returned, "Root element is missing." This happened across all workflows directly from the workflow server (didn't get a chance to test on client machines).

The fix was to uninstall workflow, delete the workflow folder from the program files folder, reboot the server, and re-install/ reconfigure workflow. I noticed while going through installation again that one of the prerequisites was not on the machine, one of the C++ runtimes. I think that is the real root of the issue.

This post has a screenshot of which C++ runtimes are required: https://answers.laserfiche.com/questions/146452/Windows-Client-and-Prerequisites-with-C-or-C-Plus-Plus

You can see which versions of the runtimes are installed through the Add or Remove Programs console.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.