HQ Server HQ Client

In my experience, setting up HQ Client to run as a service results in the service not communicating when the computer reboots. The service is running, but no communication happens with the server. There's no log info anywhere that points to a problem. Restarting the service in the Services tab gets things working again.

Our vendor has seen it working at other locations, so it's possibly our environment. Rather than fight with it, I just wrote two simple scheduled tasks. One to stop the HQClient service and another to start it (I probably could have written one to restart, but oh well). They run early in the morning before any store opens and well after any update-mandated or scheduled reboot.

With that in place, I haven't had a problem with HQClient not communicating in months.

Dann

"Sammy" wrote:

Did you write a batch file for the scheduled task?

Microsoft recommended I copy and paste the HQ Client in the startup folder. I have tested and they do start up, however I'm still not communicating. The only way to communicate seems to be to click on HQ Client and manually open the program.

Thanks !

"Jeff @ Check Po> Sammy,

Startup" with XP or "At Startup" with Vista