Production Terminal shows signs of instability, lockups, unable to log in, stuck on loading screen, etc.

There are several potential causes to the problem above, below is a list of a few items that could ultimately lead to issues with Production Terminal.

1. Incorrect version of Production Terminal files installed that are not compatible with the installed version of Control or the Cyrious SSLIP.
2. Improper IIS configuration for the Production Terminal Website.
3. Incorrect configuration of Production Terminal within Control.
4. Random network drops, instability which lead to interrupted network traffic causing the SSLIP to become unstable.
5. Errors within Control which lead to a stability issue with the SSLIP, such as a improperly configured scheduled Macro or recurring activity.

It is recommended you conduct a full review of all components pertaining to Production Terminal. Below are some ideas of information to check, please review the other Troubleshooting links. While reviewing the items below you may find an error that has already been documented and the steps to resolve have been noted.

1. Ensure you have the proper Production Terminal files and program executable.
2. Check network stability utilizing the Pinger.exe application to check for intermittent drops. Please keep in mind that you may not experience any issues when utilizing Pinger.exe if you're encountering a hibernation problem with the network cards as the Pinger.exe utility will likely keep the network cards active.
3. Review Event Viewer logs within Windows for recurring errors.
4. Check the Control and SSLIP Error Logs for recurring errors that may be leading to your problem.