mO SharemO Share

"Unable to connect to the remote server" or "Tcp channel protocol violation: expecting preamble." - Error while testing Schedule Remoting host connection

Owned by Tech Contributor (Unlicensed)
Last updated: Jun 15, 2020 by Arindam Banerjee (Unlicensed)
3 min read

SYMPTOMS

In Ginesys Report module we can test report scheduler service connectivity under Scheduler Settings of Server tab. The value mentioned for Schedule Remoting Host can be tested there. The test may fail for different reasons. Following error messages may appear.

Menu to test connectivity:

Ginesys Web > Report > Server > Scheduler Settings > Schedule Remoting Host

Error Messages :

Connection to http://192.168.1.140:2001 fails: : Unable to connect to the remote server.

Connection to tcp://192.168.1.141:2001 fails: : Tcp channel protocol violation: expecting preamble.

CAUSES

During report installation, the report scheduler service is being manually installed. A windows service gets created once the installation completes successfully. Further, while configuring Report scheduler, the host URL need to specify under Scheduler Settings. Generally, the URL consists, the Channel Type, the Host name or IP and the Port. Following are the explanation of each part.

Complete URL: <channel type>://<host name or IP>:<port>
Example: http://192.168.1.140:2001

Channel Type
It is either HTTP or TCP. It should be same as mentioned in Report Scheduler configuration XML file.
Report scheduler configuration file i.e. eWebReportsScheduler.xml.
Config file location: /GinesysReport/ReportScheduler/.
Tag: <Channel_Type>

Host name or IP
The system name or IP where the service running. This is the same as Ginesys application server. If separate report server is configured then, it will be that report server details.

Port
The default port is 2001. It should be same as mentioned in Report Scheduler configuration XML file.
Report scheduler configuration XML file i.e. eWebReportsScheduler.xml.
Config file location: /GinesysReport/ReportScheduler/.
Tag: <Port>

Probable cause of connectivity check failure.

  • Report Scheduler service is either not installed or not running.

  • Improper value mentioned for Schedule Remoting host.

  • The connection blocked by Windows firewall or any third-party antivirus application

RESOLUTION

Check for Report Scheduler service

If report scheduler is configured properly, a service should exist in Windows Service manager (services.msc).

  • Open services.msc

  • Find the service GinesysReportScheluer in service list.

  • Start the service if found stopped or restart the service if it is found running.

If the service not found or throwing error to start up, please refer this following article.

https://ginesys.atlassian.net/wiki/spaces/PUB/pages/1927578067

 

Service running but still connectivity test fails

If the service is running but still unable to test the connection then you can verify the connection entry.

  • Channel type should be HTTP or TCP and as same as mentioned in Report scheduler configuration XML file i.e. eWebReportsScheduler.xml located in /GinesysReport/ReportScheduler/. (see CUASE section for explanation).

  • The protocol can be altered between TCP and HTTP if either protocol fails.

  • The URL for Schedule Remoting Host contains correct IP or Host name of the Ginesys application server or Report server (if report server is separate). Mention correct system name or IP address.

  • In general, port should be 2001. Same port should be mentioned in Report scheduler configuration XML file i.e. eWebReportsScheduler.xml located in /GinesysReport/ReportScheduler/. (see CUASE section for explanation)

 

Check firewall and antivirus

Even if carrying out above troubleshooting still the connectivity fails, please check in Windows firewall or third-party antivirus is blocking the connection. Need to check for necessary exceptions.
The connectivity can alternatively checked using TELNET command from application server. Telnet Client should be enabled and following command to execute. A blank screen denotes successful readability.

TELNET <host IP> <port>

Example:
TELNET 192.168.1.140 2001

Reference: How To: Perform Telnet

RELATED ARTICLE

https://ginesys.atlassian.net/wiki/spaces/PUB/pages/1927578067