Export PDF fails with "An unexpected error has occurred. Please see the instance logs for more details"Issue When a PDF is exported from a list view or a form view from ServiceNow, the export fails with an error below: An unexpected error has occurred. Please see the instance logs for more detailsCauseThe PDF export uses WHTP or PAREXPORT (PDF rendering server), the system property 'glide.servlet.uri' is the value used by default to connect back to the instance for communication between the PDF rendered and the instance. If the value is not pointing to the correct instance URL, the connection fails with the export failure. This can be observed in the case of clones from prod to sub prod instances with sys_properties table not excluded. So possible related to a cloning issue: where glide.servlet.uri is set to the incorrect instance. Another property that needs to be reviewed is com.snc.whtp.host: it will contain the type of PDF renderer that is used (Either http://whtp or http://parexport).ResolutionVerify if the property: com.snc.whtp.host contains the value: pre-Rome: "http://whtp"post-Rome upgrade: "http://parexport" If this property is set correctly: If the value: com.snc.whtp.host is empty: The Export Will seemingly succeed but result in a "Requested attachment does not exist". If this value is set correctly but you are still seeing the error: "An unexpected error has occurred. Please see the instance logs for more details" Then: Verify the value for glide.servlet.uri using a background script: var Property = gs.getProperty('glide.servlet.uri'); gs.print(Property); This should return the correct instance URL for this particular instance. If this returns a different URL then a default instance URL: Verify if the URL that is used for accessing the instance is using a vanity Proxy URL or a default instance URL (https://<instance-name>.service-now.com) Please note that if non-standard (vanity URLs) are used, the requests from the parexport server back to the instance are perhaps not accepted. "Vanity URL and Proxy URL related issues are out of scope for Support". However in this case it is possible that the connection from the PDF renderer coming back to the Proxy URL is blocked off. (IP Access controls or other). Supported for PDF export are the default "Instance URL", or instances using the "Custom URL Plugin".Related LinksAssociating custom URLs to your instance