A bit of a wierd one this.. We have two identical servers, both running Windows 2000 (SP4).
If I run a vbscript via Scheduled Tasks, on one server Wscript.exe in Task Manager closes as the vbscript has executed... on the other server (identical O/S, identical vbscript etc) the instance of Wscript.exe remains in Task Manager after the script has ended.. whats going on??
This happens for every vbscript that is executed on that server - Wscript.exe is left behind in Task Manager.
It causes a real problem with overnight scheduled tasks because if there are more than two instances of Wscript.exe in Task Manager, the next script that comes along won't execute.
Any one else experienced this problem? - or, any one know how to solve it?
If I run a vbscript via Scheduled Tasks, on one server Wscript.exe in Task Manager closes as the vbscript has executed... on the other server (identical O/S, identical vbscript etc) the instance of Wscript.exe remains in Task Manager after the script has ended.. whats going on??
This happens for every vbscript that is executed on that server - Wscript.exe is left behind in Task Manager.
It causes a real problem with overnight scheduled tasks because if there are more than two instances of Wscript.exe in Task Manager, the next script that comes along won't execute.
Any one else experienced this problem? - or, any one know how to solve it?