Open topic with navigation
Error connecting to the Report Server. No connection could be made because the target machine actively refused it
Last Updated: 2016-08-08
- Guard1 Plus versions: 5.x
- Guard1 Plus SE versions: 5.x
During the Reports phase of the Data Maintenance Application you receive the following error:
- Error connecting to the Report Server. No connection could be made because the target machine actively refused it <IPAddress>:<PortNo> Unable to connect to the remote server There was no endpoint listening at http://PCNAME/ReportServer_InstanceName/ReportService2010.asmx that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
NOTE: the highlighted item may be http or https.
- The ReportServer service is not running.
- Firewall or other security software is blocking the default Reporting Services port (HTTP port 80).
- The Report Server is offline.
- The Report Server name cannot be resolved due to a DNS issue.
- The connection parameters provided for the Report Server are incorrect.
- Reporting Services is not configured.
- The Report Server SSL settings do not match the SSL setting chosen on the Reporting Services Configuration page of the Data Maintenance Application.
- Verify the ReportServer service is running on the Services tab in Windows Task Manager. If not, start it and try again.
- Reporting Services uses HTTP port 80 by default. Ensure that your firewall and antimalware application is not blocking communication on the Reporting Services port.
Guard1 Plus SE only
- Verify that the Report Server (typically the PC where SQL Server resides) is running and on the network.
- Verify that you can ping the Report Server by name and by IP address. If name resolution fails, there is a problem with your network DNS. Specify the IP address on the RS Connection Parameters page of the Data Maintenance Application.
- Ensure that you've provided the correct connection parameters for the Report Server. Refer to SQL Reporting Services Configuration Manager on the Report Server.
- Report Server Name or IP address
- Report Server Virtual Directory. If using a SQL Named Instance, specify it after the Virtual Directory name, separated by an underscore (e.g. VirtualDirectoryName_InstanceName)
- Report Folder name. This folder will be created on the Report Server.
- Use SSL (HTTPS). Check this box only if your Report Server is configured to use SSL endpoints.
- Verify that Reporting Services is properly configured and that you can reach the Report Manager Home Page (e.g. http://ReportServerName/Reports) successfully.
- Verify your Report Server SSL settings and configure Guard1 Plus SE appropriately.
After making necessary changes to the items above, reset the Report Server Connection Parameters:
- Exit the Data Maintenance Application.
- Delete the file Tks.G1Plus.Dc.G1pRsConfig from the folder C:\ProgramData\TimeKeeping Systems\Guard1 Plus\TKS Guard1Plus Service. This will allow you to re-enter your Report Server connection parameters by re-running the Data Maintenance Application.
- Launch the Data Maintenance Application from the All Programs menu by right-clicking its shortcut and selecting Run as administrator.
- Log in with your Guard1 Plus SE Supervisor credentials.
- Enter your Report Server Name or IP, Report Server Virtual Directory (with appended Instance Name if applicable) and desired Report Folder name.
- Select the appropriate SSL option:
- If the highlighted item in Symptoms is http: Your Report Server is configured to use HTTPS only. Select Use SSL (HTTPS).
- If the highlighted item in Symptoms is https: Your Report Server is configured to use HTTP only. Do not select Use SSL (HTTPS).
- Click Next. The Reports configuration should complete successfully.
Copyright © 2013-2016 TimeKeeping Systems, Inc.
Open topic with navigation