Export to PDF is not working on Dashboards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2017 11:52 PM
One user is not able to export to PDF on Dashboard. getting error :- "An unexpected error has occurred. Please contact your system administrator. " while i am able to do so as an Administrator. any idea why this is happening.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2017 02:59 AM
can you check in the sys_logs if you see any error occurred? if yes, please share details of the error here
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2017 03:00 AM
Also provide details on servicenow version.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2017 03:12 AM
Checked in sys_logs. couldn't find anything. current version is "
"glide-jakarta-05-03-2017__patch3-08-23-2017"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2017 04:37 AM
I would suggest to raise a Hi ticket in this case because I am getting a feeling this might be related to known problem PRB1073171, already logged.
In the meantime the workaround (given in problem ticket):
You can export your dashboard to PDF using the platform's "Printer friendly version" icon button which is available from the top most cog wheel button. Clicking that icon will display the dashboard in "printer friendly" mode. This view allows the user to select things like page size and orientation. Then using the browser's built-in "print to PDF" options a PDF file can be generated. The generated file will only show widgets, not the extra toolbar seen on the browser.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2017 02:02 AM
Got the below response from Hi-Support
The issue that is experienced is related to an known problem: PRB1041779 and it is fixed in Jakarta Patch 7
it is related to the system and the role: snc_internal this role should normally be allowed to connect to internal processors,
but in some versions that is failing.
The work arround for this issue is to disable this ACL:
HTTPAuthProcessor: