For most of these you will need to recycle the report service
Method not found
This will usually be error along these lines as soon as you try to run the report:
"An error occured generating the document. Method not found"
This can also sometimes show as different errors eg.
"FileNotFoundException: Could not load file or assembly"
Check that the report service AppPool is running with 32bit disabled
The File Exists
If after running the report you see an error along the lines of
"An error occured generating the document. The file exists"
Also in the report service logs you will see something along the lines of:
2019-10-10 05:00:25.0366 Error System.IO.IOException: The file exists.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Path.InternalGetTempFileName(Boolean checkHost)
at CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext)
at CrystalDecisions.CrystalReports.Engine.FormatEngine.ExportToStream(ExportRequestContext reqContext)
at CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToStream(ExportOptions options)
at CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToStream(ExportFormatType formatType)
at ReportWebServices.Domain.Services.ReportService.GetReport(Guid guid, String& fileName)
at ReportWebServices.Web.Api.ReportController.GetReport(Guid guid)
This is most likely due to C:\Windows\Temp exceeding 65,000 files, clearing the temp folder will resolve the issue
Failed to Open the Connection
After running the report you receive an error along these lines, also on some (but not all) reports won't load the prompts.
An error occured generating the document. Failed to open the connection. Details: [Database Vendor Code: 17 ] Failed to open the connection.
You may also see an error along these lines in backend jobs for user reports:
Message: Cannot create PDF from [....] for message System.Exception: Unable to retreive stream from guid:[.....]
System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
- Check the report validation entries are setup for the correct database
- Check the ClickHome.Reporting.RepServerURL setting
- If this is a large report you may have to increase the report service timeout window:
Something went wrong
When trying to load the report you get an error along these lines, the technical message will be as follows
This is a more generic error, there are a few known causes:
- The report itself is inaccessible, check that the report exists and is accessible by the reports service
- Can't connect to report service DB, check the connection string to the report service database is correct
- Upgrades may change report web services to "Integrated Security" in the ConnectionString file
- Check the setting ClickHome.Reporting.RepServerAPIKey exists and the key is correct
Unable to connect to the remote server
When trying to load the report you receive a technical message along these lines, also similar you may receive an error that complains about the certificate.
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
This error, and the error about SSL, is usually an issue with the app on the server trying to connect locally to the report service. Relating specifically to the ClickHome.Reporting.RepServerURL setting. Effectively the error is saying that the link in here isn't valid when run on the server. Changing this setting (not the display one) to localhost or the specific server name should resolve. In the same vein, the certificate error can come up you have https for localhost
Server Error in ReportWebServices Application
When attempting to load reports the initial error which shows is a Runtime error. When running reports internally another error is shown in the second screenshot.
When you see this check IIS and under Application Pools > CH3_ReportWebServices
Stop the application and start it again. This should fix the reports.