Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
The issues listed in this article have been encountered while attempting to export PDFs from the Orion Web Console. When available, a resolution or workaround is provided. If the problem you are having is not addressed in this article, please submit a technical support ticket.
Issue: In environments using self-signed certificates, the following error has occurred when attempting to use the Export to PDF function in the Orion Web Console:
There was an error trying to export the page to PDF. Please try again later.
Export to PDF failed. Err: The underlying connections was closed; could not establish trust relationship for the SSL/TLS secure channel.
Resolution: To correct this issue:
Issue: In IIS6 environments using web gardens, attempts to list resources or export to PDF may fail.
Resolution: Using web gardens in IIS6 may result in failures to list resources or export to PDF from the web console.
For more information about web gardens, see the Microsoft TechNet article Configuring Web Gardens with IIS 6.0 (IIS 6.0).
Issue: Export to PDF is not available in an Orion NCM Integrated Web Console
Resolution: This is a known issue in Orion NCM 6.0. When viewing NCM reports from the Orion Web Console (Configs), though the report may contain data, clicking the Export PDF option often returns an error. The Export to PDF option was removed for NCM 6.1; the functionality will return in working order when Orion NCM releases again later in 2011.
The current workaround is to use a third party PDF creation tool (for example, Cute PDF).
Issue: Export to PDF Fails with a 400 Error
Resolution: There is a known bug that is slated to be fixed in a future release, but there is no specific time frame announced for this release. Potential workarounds include the following:
Issue: Export to PDF Fails with a 404 Error
Resolution: There is a documented bug that is fixed in NPM 10.1.2 SP1. Potential workarounds include the following:
Issue: Export to PDF shows "No data for Selected Time Period" or incorrect date
NTA sends the date format in US English format - mm/dd/yyyy. When using browsers set to languages other than US English, the date is read as dd/mm/yyyy. This causes an erroneous date or a "No data for Selected Time Period" error.
Resolution: This is a known issue. The workaround is to temporarily change the browser language setting to US English.
Issue: Export to PDF is not retaining filter information for event, alert, syslog, traps, or message center views.
In some versions of Orion NPM, the conditions applied in a filtered event, alert, syslog, traps, or message center view may not be retained when the filtered view is exported to PDF. This is a known issue that will be addressed in a future release of Orion NPM.
The following procedure serves as a workaround, allowing you to retain all filter settings passed in the URL of the view you are exporting to PDF.
Resolution: To retain filter settings when exporting an event, alert, syslog, traps, or message center view to PDF: