Headquarters Server Crashing

We recently have been experiencing a problem with Headquarters Server where it constantly crashes. The error received is "Run-time error: 3002. File could not be opened". If we restart the service, it'll run for a little while and then crash again. There's no commonality as to when it happens. Any help would be appreciated.

Ok, I did the check and reindex. I won't know if it worked until the stores open and start polling. I'll keep you posted.

Is this something that happens every now and then? This is the first time I've seen it.

"Jeff" wrote:

Database | Check | Database | Re-index

I had a similar problem last year when we were between VARs. I could not find a solution and ended up reinstalling the OS, SQL Server and RMS. It was drastic, but it was my last option after being handed the RMS responsibilities with no support I could contact. I know that is not what you wanted to hear, and I am not recommending it.

I hope you get a solution and post it here as it was a painful experience that I would not want to relive. It left such an impression, that I now have a server dedicated to just HQ Server communications. The SQL Server and HQ Databases live on another server entirely. This way, if I have the problem again, I can temporarily run HQ server on the SQL Server and keep connectivity going while I fix the HQ Communications server.

Ok, its still happening. It's not happening as often, but it still does. Is there something that I can check on each store's end to see I can resolve this issue?

"J Wray" wrote:

Database | Check | Database | Re-index

Thanks Butch. Yeah, I don't want to have to reinstall everything either. I'm in the same boat as you as I have no support or documentation.

Luckily, I'm pr> I had a similar problem last year when we were between VARs. I could not

use SO Admin instead.

I think we're getting closer. One of the stores lost Internet connection for about 4 days. During those 4 days, all the stores polled with no problem. The store came back online yesterday afternoon and the Run-time error: 3002 came back. Is there anyway to troubleshoot just one store?

I also found out that the previous consultant didn't create a new store. He took an existing store and copied it over somehow and I guess changed the store ID. Personally, it sounds like there's a conflict somewhere. Where can I check to make sure everything is unique?

What's the proper way to fix this?

"Jeff" wrote:

you use SO Admin instead

Andrew,

You might want to turn the debug log in the bad store's HQ client. That may tell us where to look.

I've never done it that way and as you've found is not the proper way of doing it. You want to delete and re-create the store. That's an extreme fix, but that might be the only way to fix the problem.

But try the debug log first and maybe you'll be lucky! ;-)