Troubleshooting
The following sections provides details on how to diagnose common problems that you may have with StreamLink.NET.
Caplin Support
If you cannot resolve a problem with StreamLink .NET by following the troubleshooting tips given here, contact Caplin Support providing us with as much detail about the problem as possible. If StreamLink.NET is actually running then please provide the StreamLink.NET log (see Activating the StreamLink.NET FileLogger).
Also provide the Liberator Logs for the period during which the problem occurred. These logs are located in the directory liberator/var on the server on which Liberator runs. (For further information on enabling Liberator logs, and the log formats, see the Liberator Administrator Guide).
Once you have obtained all the logs that will help Caplin Support diagnose your problem, send an e-mail, with the logs attached, to
Note: If the total size of the log file is more than 10 Mbytes, don’t send them with the email; instead let us know and we will give you FTP details so that you can upload the files directly to Caplin Support.
Connection Problems
The most common causes of connection problems are configuration or general network errors
- Ensure that the Liberator addresses and ports listed in the StreamLink.NET configuration are correct.
- Ensure that your machine has a live network connection and that there are no network problems between your machine and the Liberator host. You can check this by pinging the Liberator.
- Ensure that third party software or hardware is not interfering with your connection by checking settings for things such as proxies and/or firewalls which may be on the client machine and also running on the network. You may need to contact your system administrator to check the latter.
If your problem cannot be diagnosed by checking all the above points then contact Caplin Systems Support. See the Caplin Support section.
Data Problems
To help us diagnose data problems as quickly as possible please provide as much information as you can about the problem:
- The StreamLink.NET logs (See StreamLink.NET FileLogger below).
- The Liberator logs (See Liberator Logs below).
Activating the StreamLink.NET FileLogger
To activate the Caplin StreamLink.NET FileLogger modify the <FileLoggerConfiguration> section of the StreamLink.NET XML configuration file. within the >RttpConfiguration< element. For more information on logging see the StreamLink Configuration XML Reference documentation. The example below shows a configuration file with the <FileLoggerConfiguration> specified so that the FileLogger is activated at run time.. set.
CopyXML<?xml version="1.0" encoding="utf-8"?> <RttpConfiguration> <RttpService Name="Example RTTP Service" NoopInterval="2" NoopTimeout="7" ReconnectInterval="3" ReconnectAttempts="9"> <Connections> <Type2Connection Protocol="Http" Port="8080"/> <Type3Connection Protocol="Https" Port="8080"/> </Connections> <ServerGroup Type="order"> <Server Name="My Development Server" Address="localhost:8080"/> </ServerGroup> </RttpService> <FileLoggerConfiguration> <LogFileName>C:\sl4net.log</LogFileName> <!-- Optional --> <MaxLogFileSize>10000000</MaxLogFileSize> <!-- Optional --> <LogFileNameSuffix>yyyyMMddhhmmss</LogFileNameSuffix> </FileLoggerConfiguration> </RttpConfiguration>
Liberator Logs
- Liberator logs are located in the directory liberator/var on the machine on which the Liberator runs. Please only provide logs for the period during which the problem was experienced.
- For further information on enabling Liberator logs and the log formats see Liberator Administrator Guide