Comments
Sort by recent activity
Not the answer(s) I was hoping for, but they are the answers I was expecting. Just one more thing I'll need to keep in mind in our slow migration to PaaS Thank you both! / comments
Not the answer(s) I was hoping for, but they are the answers I was expecting.Just one more thing I'll need to keep in mind in our slow migration to PaaSThank you both!
We did update to the most current version that was available for download (14.0.68) as of my last post here. I did again try to email a test report to myself, which still never came through, however, I now believe I have more information on WHY the reports may not be getting emailed. I attempted to save the same report as a PDF, which caused Monitor to throw an error, “Error generating PDF file.” Which leads me to suspect either:
On the server with the base monitor and web server, permissions aren't correct to a folder somewhere
The server with the base monitor / web server needs additional software, such as Acrobat (which in our environment will be a hard “no”)
Looking in the website.{date}.log file for today, the error reported there is “Error while rendering pdf from url for job group 0: ‘Aborted job 0 for browser 1: Error ’ERR_NAME_NOT_RESOLVED' while loading browser 1'” This occurred in MS Edge and Google Chrome / comments
We did update to the most current version that was available for download (14.0.68) as of my last post here.I did again try to email a test report to myself, which still never came through, however...
Apologies for the delay in responding. We are currently on V14.0.47.8355, which I know puts us a bit behind the version curve, I'm in the process of scheduling our next update to the application. I did set up a scheduled report as a test, and found that the report didn't go out (or at least, was never received on my end,) despite the test email from the reports page going through. So that's another issue, it seems. Once we update to the current version, I'll try again, and report back here. / comments
Apologies for the delay in responding.We are currently on V14.0.47.8355, which I know puts us a bit behind the version curve, I'm in the process of scheduling our next update to the application.I d...