Y release - scheduled /on-demand PDF report - issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Hello ,
We are in Y release.
Scheduled/On-Demand PDF reports open with Error: Export failed using PARExport server.
This was working before Y upgrade.
Thank you and appreciae support with this request.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Have you checked if all plugins are updated to the most recent version?
I assume you saw this one already, since it's the first result when you ask google: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2139716
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
We faced similar issue in our environment and it was resolved by updating Platform Analytics, UI Builder and Data Visualization plugins to latest version.
Go to System Definition -> Plugins and look for Platform Analytics 'sn_app_analytics_w', Data Visualizations 'sn_par_vis_base' and 'sn_ui_builder' plugin and update to latest version. Clear browser cache, logout and login again and try it.
If it does not work, refer below knowledge article and check for system property glide.par.export.host configuration
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2139716
As per community guidelines, you can accept more than one answer as accepted solution. If my response helped to answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Thank you both for your input.
we verified all properties/plugins etc mentioned , but still issue existed, and contacted SN support.
They responded that the issue was on their "parexport" servers and restarting servers fixed the issue.
Thank you and appreciate the support from SN community.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Glad to know it is working fine now and thanks for explaining the resolution steps. This could help someone else in future.
Thanks,
Bhuvan
