Quick Books Shutdown Problems

Oct 20, 2006 9 Replies

I recently installed QB 2006 for a client on a Win 2K (SP4) Server machine. She advised me by phone that QB has spontaneously shut down several times. It happened when she was doing payroll entries and also seems to be prone to happen when doing splits in banking entries. Over the phone I had her run the Verify Data utility option which reports no problems. I also had her check the QBWIN.LOG file. It showed one error at a time corresponding to one shut down event. oaerror.c (109) : CHECKPOINT: Fri Feb 10 13:20:19 OAstdMethodRet (80040600)



I have found other reports of this error, but no one seems very sure what it really indicates or how to prevent it.



This computer is malware free and has no other problems. At this point, I have downloaded the R8 update pack to burn to CD and bring to the site to run (as they have no online access) on the chance that it may help. If anyone has any specific info re. this error message or other suggestions, I'd appreciate your advice. Would it be of any possible value to run Rebuilt Data even thought Verify Data reports no problem?


BTW - although this is installed on a W2K server, it is a single user copy used only on that computer. There is no network use involved.

Hi GTS!

As far as I know Checkpoint lines are not errors in the qbwin.log. It sounds a little like an antivirus or firewall conflict. When she installed the program, she needed to make sure to turn off all antivirus/firewall programs. You may want to walk her through configuring hers to allow QuickBooks to access the internet properly.

Click on the below link to see the port instructions:

formatting link
Good luck! Amy

formatting link

Thank you but as I said in my post 1. This error was in the QBWIN.LOG (as are all other reports of this error which I have researched) and 2. This office has no Internet access. Additionally there is no firewall or antivirus program involved.

If someone who actually read my post has another idea, I'd appreciate hearing from you.

To answer your question, it may be of some value to run the Rebuild regardless of that Verify Data returns. But I'm not sure the problem is with the data, but a portion of the application. I know you say it is malware free, but considering it is the server, you must be running some services on there. Possibly there is a conflict. Also, even though you have a single license, did you set the database up as shared? I'm just trying to get a clearer picture of the installation.

Gary

If QB is still at R1, then I would update it to R8 before spending much effort looking for other causes.

Only other suggestion I have is to make sure you have turned off Automatic Updates: Help | Update QuickBooks, Options tab page.

Per your reply, I will run the rebuild when I go back there next week as well as the QB update pack. I'll do an extra backup first, so it certainly couldn't hurt to try. I concur that the problem isn't necessarily in the data. I have a suspicion that it might be because there is another QB file that seems less problematic, although it's smaller and hasn't been used a lot, so it's not a sure indication one way or the other. The database is definitely not set up as shared.

I've also considered possible software conflicts. I plan to do some further testing on that possibility. There are a few other programs running on the server. I'm also considering running the Win 2K SP4 rollup update to bring Windows more up to date. (This office is very unusual, among my clients, in having no Internet access and very strictly controlled computer use, so I don't always keep it as up to date.)

I appreciate your thoughts. Any other ideas would be welcomed. Thanks!

Thanks. I definitely do plan to do the R8 update. Since there's no Internet access, turning off Auto Updates makes sense though it doesn't seem to likely it would be causing the problem.

GTS, I'm sorry you felt I didn't read your post.

The qbwin.log does list errors, if you have them, but a line that says "CHECKPOINT" in the qbwin.log is not an error. I apologize if I was confusing in my original post.

Amy

-- I see on rereading that my post, made in a aggravated moment, that it was a little touchy. Sorry about that. I appreciate that you took the time to reply.

Join the Discussion

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

Didn't find your answer?

Ask the community — no account required