The runtime closes unexpectedly when a file cannot be deleted during file synchronization between server and standby server

• Related Articles

• FAQ: From a certain amount of connected Smart Clients the Smart Server closes unexpectedly, what can I do?

  It is possible that the Smart Server closes as it runs out of possible memory address space for a 32-bit application. In this case use the Smart Server 64-bit version.

• File synchronization between server and standby server takes a long time to complete with many files even if all files are already present

  Summary Under specific circumstances in a project with many files for historical archives, the reload of the runtime and file sychronization between server and standby server takes a long time to complete, even if all files are present and identical ...

• On closing the runtime on the server, the runtime on the standby server closes unexpectedly with an unhandled exception under specific circumstances

  Summary Under specific circumstances and timing conditions closing the runtime on the server may result in an unhandled exception on the standby server and unexpected closing of the runtime on the standby server. Description Under specific ...

• After reloading a sub project under specific circumstances the runtime on the standby server may close unexpectedly

  Summary With an integration project and a sub project as redundant network projects with same server / standby server, the runtime on the standby server may close unexpectedly after transferring the runtime files to the primary server and reloading ...

• Runtime on the server closes unexpectedly after a 7.50 client opens a batch control screen or command sequencer screen

  Summary Under specific circumstances with a 7.11 runtime server / standby server or a 7.20 runtime server / standby server and a 7.50 runtime client, the runtime on the server may close unexpectedly after the client opens a batch control screen or a ...