Cannot generate report in Web Viewer after upgrade to 5.22.1
Hello,
We recently updated Reporting, Workflow and Web Viewer to the latest versions. After upgrade I can no longer generate a report through the Web Viewer.
The report runs fine in the Report Designer. I also, have a workflow and uses that same report, and the report runs fine in the Workflow Sandbox. That same Workflow is consumed in the Web Viewer and that's where the issue happens. I am getting an error that says: "An unexpected error has occurred. More detailed diagnostic information may be available in the browser console. Please contact the site administrator if the problem persists."
There is not much information in the browser console, all is says that 'Job Failed'?
Any suggestions on what could be a problem?
Thank you,
Nataliya
-
Hey Nataliya Lys
I'd try swapping out that failing report with a basic one. If that fails too, we know it's at the reporting application level. If that succeeds, we know the issue is something related to the specific report content.
0 -
Hi Gareth,
I added a report directly to WebViewer and it ran just fine. But when I added a workflow, that included that same report (I use workflow with Display Form so user can enter parameters), that's where it fails.
Thanks
0 -
Hey Nataliya Lys, which version of Workflow are you using - 5.32.1?
0 -
Gareth Evans my workflow version is 5.28.1
0 -
I'd try simplifying the issue, and take out as many variables as possible. Try a super basic workflow that's just a run report with a basic report - does that work? If so, then throw in your custom report - see if that works. I suspect that'll fail somewhere along the lines.
It may also be worth submitting a support ticket to vertigisstudio-support@vertigis.com - they can lend hands-on help and have a great deal of experience and insight.
0 -
I ran a report from a Workflow in Web 5.22.1 on prem this am with no issues. We are using WF version 5.31.0 and Reporting version 5.19.0.
1 -
Thank you all for suggestions. I ended up rebuilding a workflow that I use to run the report, and everything is working now.
0
Comments
7 comments