KWSN_Millennium2001Guy
02-27-2003, 09:44 AM
Howard, during this last changeover I discovered a new "bug" with the existing client. Here are the symptoms:
On Windows 2000 machines, client running as a service.
DF server not available.
Start the foldtrajlite.ex service.
service creates the foldtrajlite.lock file but never kicks in to production mode because it is unable to contact DF server.
Try to shut down the foldtrajlite service by either deleting the .lock file or using net \stop servicename.
service does NOT shut down and NT service manager shows the the service is "stopping", but even after 4 hours the service never completely clears.
Forced to reboot the machine to clear the service.
I am not able to test this on the beta client because it requires your server to not be available, which is something that I don't have control over (thank goodness).
I believe that the client should be able to clear itself from running regardless of whether the DF server is available or not.
Thanks for your support. :)
Ni! :crazy:
On Windows 2000 machines, client running as a service.
DF server not available.
Start the foldtrajlite.ex service.
service creates the foldtrajlite.lock file but never kicks in to production mode because it is unable to contact DF server.
Try to shut down the foldtrajlite service by either deleting the .lock file or using net \stop servicename.
service does NOT shut down and NT service manager shows the the service is "stopping", but even after 4 hours the service never completely clears.
Forced to reboot the machine to clear the service.
I am not able to test this on the beta client because it requires your server to not be available, which is something that I don't have control over (thank goodness).
I believe that the client should be able to clear itself from running regardless of whether the DF server is available or not.
Thanks for your support. :)
Ni! :crazy: