These problems can occur when you start Backburner Manager or Backburner Server on Linux or Windows systems.
Problem | Common Cause |
---|---|
An Application Terminated error appears in the Backburner Monitor or the Backburner Web Monitor. | An incorrect IP address for the Backburner Manager, incorrect port numbers for the Manager and/or Server, incorrectly configured TCP/IP information. |
A Host Not Found error appears when starting Backburner Server on a Windows system. | An incorrect IP address for the Backburner Manager, incorrect port numbers for the Manager and/or Server, incorrectly configured TCP/IP information. |
An Overlapped I/O Operation is in Progress error appears when starting Backburner Server as a Windows service. | The Backburner Server service is already running. This is not a problem. You can continue with network rendering. |
A Service is Installed. Cannot run Server Application. error appears when starting Backburner Server on a Windows system. | The Backburner Server service is installed and running. You can continue with network rendering without launching the Backburner Server application. |
An Error registering to <server_name> error appears when starting Backburner Manager or Server on a Windows system. | Invalid IP addresses in the DNS Search Order, or the Primary or Secondary WINS Server in the Microsoft TCP/IP dialog. See Resolving Network Card Priority. |
A Cannot handle registration from <server_name>. Will try later. error appears when starting Backburner Manager or Server on a Windows system. | The number of concurrent TCP sessions currently exceeds the limit the Manager can handle. Servers automatically retry, usually within a minute, so the problem should resolve itself. |
A Cannot access job share <server_name>. Requesting archive directly. error appears when starting Backburner Server on a Windows system. | This warning may appear only on Backburner networks and can be disregarded. The warning appears when a required folder and/or drive is not shared using Windows file sharing. If this occurs, Backburner switches to TCP/IP to access the required folder and/or drive across the network. You can prevent this warning from appearing by ensuring all network components share the same folders and drives. |
An Invalid name or TCP/IP subsystem not installed error appears when starting Backburner Manager or Backburner Server on a Windows system. | The TCP/IP protocol is not running or not working properly. This error may occur on workstations where a pre-installed version of Windows includes a misconfigured TCP/IP protocol. Remove and then reinstall the TCP/IP protocol and reboot the workstation. Once the workstation has rebooted, see Verifying Communication Between Two Hosts to ensure that it can communicate with other network components. |