Hello,
In one of our applications we're using the Navision application server in combination with Windows Task Scheduler and some batch-files to read and process some files every 2 hours. At the end of our codeunit a batchfile is called that will stop the NAS, the way it always worked:
NET STOP %NASNAME%
since a few weeks, the service starts stopping, but remains in the state "stopping". So, the next scheduled start can 't be processed.
We have figured out a simple solution (kill nas.exe) , but I prefer a proper way to stop it, and most of all, I would like to know why it's doing this. No extra software was installed on this server since a month or so
A guess anyone ??
thx,
scOOb
0
Comments