...
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.
...
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>
...
If the service not found or throwing error to start up, please refer this following article.
[Draft] Web Report - Report Scheduler service is not running or working
Service running but still connectivity test fails
...
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)
...
Reference: How To: Perform Telnet
RELATED ARTICLE
...
[Draft] Web Report - Report Scheduler service is not running or working