I just installed a fresh copy of FMS 13 (updated to 13.0.5) on a new server running Windows Server 2012 R2 Standard. Everything is working fine except for the "Perform Script on Server" function.

 

When it is called for the first time from the client, the script engine on the server hangs and then times out with the log entry:

Client "[script name] (Filemaker Script)" no longer responding; connection closed. (51)

 

After that, any attempt to call "Perform Script on Server" receives the error message popup "Host's capacity was exceeded, try again later."

 

The script being called to run on the server is 2 simple steps 1) Set Variable and then 2) Exit Script. No Plugins are being touched. Windows Firewall is completely turned off. There is only a single client connected to the database.

Does your file have an OnOpen script?  PSoS will run that too and if it contains unsupported script steps it may produce unexpected results.

 

What are the specs on that server?

You mention that you did a reinstall.  Did you completely uninstall / reboot / manually remove remaining folders in Program FilesFileMaker ?

To paint a clearer picture, this is a brand new server machine. Fresh install of FMS. The database does have OnOpen scripts, however the scripts ran without problems on the old server (also running FMS13).

 

I have a suspicion that there is an external file reference that is failing to reconcile being that the file is now at a new location on the network (new LAN ip). I haven't found it yet, going to keep looking.

 

The specs of the new server are Intel Xeon E5-2440 1.9Ghz (8 cores), 16GB ram, Windows Server 2012 R2 standard

FIXED: Turns out it was a bad installation of Java causing plugins to crash the script engine.