Hq Client crashing

Sep 21, 2010 4 Replies

We have RMS 2.0 installed at 21 stores, and our HQ server here at the office. On one of our stores, HQ client does not seem to want to start with windows. When you login to windows, HQ immediately crashes, with the windows error "HQ Client has encountered a problem and needs to close". The techincal details of this error are that HQclient.exe caused an IPF in Kernel.exe. If you reboot, it works fine. If you launch the program manually it works fine. And some days it works fine all on it's own.



I have checked security on the program locations, and recreated the darn shortcut in the startup folder about 23 times. I verified that nothing is loading with windows, except the HQ client. The store isn't scheduled to sync until a couple of hours after the store is open.



Any suggestions? We're almost to just replacing the computer.



Try uninstalling the program, reinstalling, then applying whatever current service pack you are already using.

Another suggestion may be to try running HQ Client as a service instead of how MS designed it. Then it is always running in the background.

Thank you,

Ryan Sakry Program Manager snipped-for-privacy@rite.us

formatting link

320-230-2282 ext. 4002 (Office) 320-230-1796 (Fax)

We have RMS 2.0 installed at 21 stores, and our HQ server here at the office. On one of our stores, HQ client does not seem to want to start with windows. When you login to windows, HQ immediately crashes, with the windows error "HQ Client has encountered a problem and needs to close". The techincal details of this error are that HQclient.exe caused an IPF in Kernel.exe. If you reboot, it works fine. If you launch the program manually it works fine. And some days it works fine all on it's own.

I have checked security on the program locations, and recreated the darn shortcut in the startup folder about 23 times. I verified that nothing is loading with windows, except the HQ client. The store isn't scheduled to sync until a couple of hours after the store is open.

Any suggestions? We're almost to just replacing the computer.

Uninstall and Reinstall seems to have fixed it for now. Jeff, the startup timer is a great idea, but these systems are clones. 21 of them currently run with no issues, just this one. Probably a software update installed in the wrong order or some other ridiculous thing. Thanks again for all the ideas

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required