Did you try selecting the Client in the Clients tab of the Server admin panel and disconnecting that one client from there?
Once the disconnect issue is resolved, check your script for server compatibility of all script steps, and be sure that the FM Server where the import source is located has read permissions by the FM Server.
FM Server is very tight about which directories it can see when running Server-side scripts,
Yep, I tried disconnecting from the client panel as well, and had the same result (no disconnection).
As far as server side script step compatibility, I know the script is good, as it's run multiple times before without having any issues. I've also double and triple checked the script in ScriptEditor making sure that I have no incompatible steps. The script in question is used *only* by the server-side schedule.
For permissions, the directory is in the FileMaker Documents directory on the server, which I understand is one fo the few places that FMS can read from.
Are the permission in the Documents directory explicitly set for FM Server to read/write?
They are. Like I said, the script ran successfully for a few days before having the issue Sunday morning.
I ended up having to reboot the entire server to resolve things. I first tried simply stopping the FileMaker Server via the admin tool. The service seemed to stop, but I was unable to restart it via the admin tool. After restarting the admin tool, it looked as if the service did *not* stop, and nothing I did would kill off the hung script. Once I rebooted the entire server, however, everything was back to normal. I'll be doing some more testing over the rest of this week to see if I can pin down a cause.
To provide more information, I discovered yesterday that the issue was related to a change in data that was being provided to the database. One of the files that was being imported was improperly formatted, and some required data was missing from some records. An error code was captured and logged, but apparently the script was not able to abort the processing and simply hung.
At this point, I'm not sure how to fix the underlaying problem of the server-side script hanging, since it was not a matter of an infinite loop or anything. There was one field that required data, and no data was provided to it. AFter hitting that point, the script just froze, and only a reboot of the entire server would kill it. I've since made that particular field not mandatory and put some other checks in place as a bandaid, but I still think that there's an issue when a server side script hangs and requires a server reboot to resolve.