As mentioned in an earlier post by a colleague, we're having problems where HQ server constantly craps out with a Run-time Error: 3002. We reindexed the main DB and the remote store DBs as well to no avail.
Is there a way to restart the app everytime it fails? Like it checks every minute to see if it's up and running or not? Is there a downside to making the app run as a service?
1) The HQ Server program no longer checks the Dongle to renew the license activation - that is done by HQ Manager. If manager is not opened on the system with the dongle (probably a workstation rather than the server now)for more than 48 hours, HQ Server will stop accepting connections and the only indication will be "Socket rejected connection" messages in HQ Client.
2) MS has posted instructions to set up as a service (I think that is a Partner Only article). but I don't think they *officially* suppor tthe configuration.
3) HQ Server was not really designed to run as a service, although it seems to perform just fine that way with the above caveats.
There are probably other issues, those are the ones that leap to mind for me...
The upside is that you don't have to leave a user logged in and locked at all times - and that is a really big upside!
I suspect that running as a service would actually make your issue worse, as the service is not going to alert you to the failure - it will just die silently I think...
Glenn Adams Tiber Creek C> As mentioned in an earlier post by a colleague, we're having problems where
What's the exact message that displays? Is there any commonality to the occurances? Similar worksheets running at the time, x minutes past the hour, time of day, day of week, particular store connecting, anything at all? Have you checked the system event logs for anything that might coincide with the errors?
Glenn Adams Tiber Creek C> Glenn, thanks for the info. Perhaps you can lend some guidence on how to
As mentioned in an earlier post by a colleague, we're having problems where HQ server constantly craps out with a Run-time Error: 3002. We reindexed the main DB and the remote store DBs as well to no avail.
Is there a way to restart the app everytime it fails? Like it checks every minute to see if it's up and running or not? Is there a downside to making the app run as a service?
Yes, J and I are are working on the problem. I figured that I would start a new post because the old one was getting buried deep and I didn't think I'd get the right exposure since this is a critical problem.
Yes, we're getting the red X's for every store under Store Status. What does that mean, and would that help resolve the issue?
It's full blown SQL.
Thanks
"Jeff" wrote:
about a Store Status with red Xs.
turn on Auto_Close.
make a new task for the HQ Server program and select When my computer starts. It checks the dongle when doing it this way.
HQ server writes some local/temp files during connections. Sometimes those files are not closed or deleted correctly - for example if HQ Server were interrupted by a power failure. It sounds like it is having problems with those files, but I haven't seen that specific message before. I'd suggest opening a support incident with MS on this one...
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.