After pressing the button to generate an online report through our legacy reporter application part of reports and dashboards, the following error is presented:
When following the presented link to find out more on the error raised, we get the following microsoft page. The page is suggesting that classic ASP is not yet installed on the DMA used to generate the report but when checking this on the server in question, we see that these roles have been installed properly on there:
The DataMiner system where we encounter this issue on was recently installed and is running on Windows 2016 server edition.
Any idea what might be missing from the server configuration in order to have the legacy reporter functioning correctly?
Hi Jeroen, you should be able to get a more meaningful error message after enabling the "Send Errors To Browser" option for ASP in IIS Manager.
The error is presumably somewhere in the custom report code.
It sounds like the report code (or code triggered from there) is trying to add an entry into an AssocArray which is already in there (a duplicate key)
It might be helpful to add debug output lines (Response.Write(“xxx”)) in the custom report code to see where it crashes (maybe copy it to a new file first)
The custom report used here, is the standard SLDMS Daily Report. I’ll check if changes are required to be done into this report in order to resolve the generation error.
You can get this error when an unhandled exception occurred while running the report template asp file. This is a "friendly" error message which hides the technical details, as those can contain valuable information which could be misused by hackers. On production systems, this is the error message you will get by default. However, to debug, it can be interesting to know more details of where this unhandled exception occurred.
It's possible to disable the "friendly" error message in IIS Manager:
- Open IIS Manager
- Go to Default Web Site
- Open ASP
- Under Compilation -> Debugging Properties -> set Send Errors To Browser to True
- Click on Apply
Now you'll get to see more details of what went wrong. Don't forget to restore this setting again in case this is a production DMA.
Hi Wouter, thank you for helping out on this one. I enabled the errors to be forwarded to the browser and now get the following error presented:
Microsoft JScript runtime error ‘800a01c9’
Unknown runtime error
/Reports/Framework/Includes/AssocArray.inc.asp, line 36
Does this give you any further info towards the root cause of the issue?