Network Management
Reports are not present on the shared drive even if running the scheduled report is successful.
This article provide steps on how to troubleshoot why reports are not present on the shared drive on a scheduled report event if the report schedule execution result is successful.
First published date
Last published date
Overview
2020-02-19 13:45:19,451 [51] ERROR ReportingLogger - (null) Error during fetching url: http://x-xxxxxx-xxxxxx:8787/Orion/Report.aspx?ReportID=4 using CSV type System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it xxx.xxx.xxx.xxx:8787 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
Product section
Cause
Resolution
2. Open the database manager and locate the website table.
3. The port used on the IIS bindings should be the same as the port use on the website table.
( On my case the port that is used on the website table is 8787 and IIS is using 80)
4. Stop the NetPerfMon service on the Orion Service Manager.
5. Edit the website table and change the port number to 80.
6. Start the NetPerfMon service.
7. Run the scheduled report and the report/s should be present on the network drive.
Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.