I've just tried to generate an Report of a CPU Threshold in the Alert center. The following happend:
- Export to Excel: The size of the file seems to be ok. But when I try to open it, I get an error. Regarding Excel Report, why is it a xls and not xlsx?
- Export to pdf - Error Message: Failed while generating PDF! Could not render the url. Could not get image from url. The URL is not accessible......
regards,
Rainer
Comments
WhatsUp generates XLS format because it is compatible with older versions of Microsoft Excel. XLSX was introduced with Microsoft Excel 2007.
As for the export to PDF, are you trying to export the whole Aler Center workspace? Whats OS is your WUG installed on?
Reply to this Comment
Be the first to rate this
|
Sign in to rate this
Dear Ambar,
About the xls, I was just wondering as Excel 2007 is on the market for quite a while... but I'm fine with xls np.
Regarding my System, I'm running the TPP v14.2 on a W2K8 R2 server. About the export to PDF, I just tried to export a Report from the webgui, which shows me on two charts (Past and real time) cpu utilization of single machine.
Thanks,
Rainer
Reply to this Comment
Be the first to rate this
|
Sign in to rate this
Rainer,
I just confirmed that this indeed is a defect that has been fixed after WUG v14.2 TPP2 was released. It only affects Alert Center reports.
Did the report with charts get exported to PDF correctly?
-Ambar
Reply to this Comment
Be the first to rate this
|
Sign in to rate this
I just figured out, that when I'm working with the webgui over HTTP, then the pdf export works fine with all the graphs. So the above mentioned problem with the PDF-Export occurs only when I'm working over HTTPS. The complete error message is attached.
Reply to this Comment
Be the first to rate this
|
Sign in to rate this
Ah, ok. This occurs because we ship a "sample" (but invalid) SSL certificate with WhatsUp. anybody interested in using HTTPS feature of our Web server should obtain a true valid certificate from one of the root certification authorities such as VeriSign, Inc.
Reply to this Comment
Be the first to rate this
|
Sign in to rate this