Serious crashes after upgrading to 2006

167>

If I read that right, it says the crash occured with QB 2002 and upgrading to QB 2006 didn't fix the file (after it was already corrupted by 2002).

-Greg

167>>

I read it the same way. Kind of makes you wonder why the OP titled the post in such a misleading manner.

167>>>

FUD ?

-Elw00de

If you look more closely at qbsrox' contribution to the thread I referred to and also at the other threads I have added you will, I hope, have second thoughts about impugning my motives for bringing some rather serious information to the attention of members of this group. You may know that qbsrox is a particularly knowledgeable contributor to the users group concerned.

Ken

Most problems seem to stem from users not knowing how to set up program for multi-user.

"I have been on remotes with clients the last few days and seen all kinds of bizarre things, and have a ton of screen shots with error messages. Back-ups that crash, verifies that crash, importing causing crashes, can't get to the qbwinlog on the ones we can open....most of these are in multi-user/networked environments; however some have been on stand-alone set-ups."

"I have a few clients calling and getting refunds, I can't repeat even half of what they are saying at this point. The amount of time and money lost in the upgrade for them has been horrible, and some of these clients are not the typical end-user, meaning, then know what they are doing in terms of computers and networks."

"Everyone needs to be SURE they have good back-ups before they upgrade, and it's best to have them on another computer; as some people are having severe computer crashes. Multi-user/networked environments are the worst."

"I wish I had better news, but at this time I don't....I was able to restore a few files using my Beta version, which again, is strange. I'm sure they will fix this soon, but I know the frustration in the meantime."

Sounds very fair to me and like sound advice.

Some other quotes from the threads I referred to my be of interest to other participants:

"We have a software business and have used QB for quite some time (for

2 different companies). I have to say I was very disappointed to find how they have architected their network (multi-user) install. I can only imagine that they've done this to help control / enforce licenses, but what a poor way to do it! We now have to leave two computers on, where one acts has a host, and our data files are stored on the file server where they're backed up.

"I'm not sure that we'll revert back to the previous 2004 version we had (given that we'd have to re-enter everything done since the upgrade), but I sure wouldn't have bothered purchasing the upgrade if I knew this ahead of time. Too bad that something like this overshadows the improvements they did make within the product." (fharrington)

"Us accountants that are working in a network environment with multiple client directories, were surprised when we installed QB 2006 and learned that Intuit had changed the network architecture of the 2006 product. Probably a good long-term enhancement, but a painful short-term pain to deal with. There is a patch available - but buyer beware. I would not install on a network environment until they get it sorted out" (gvacpa)

"I had 2004 and wanted to update to 2006 to try to keep up with the latest in taxes and other things. I put in the disc, went through the installation process and now cant find any of my previous info. nothing!!! I have no employees, no customers, no bank accounts." (puterilliterate)

Tim Teichman of Intuit has become involved in one of the threads and Lisa Peterson, another very knowledgeable QB Pro Advisor and participant in that user group, has posed the question to him:

"can you elaborate for us non-techies what EXACTLY we need to do to make 2006 work properly in a network environment?"

It will be very interesting to see what he replies.

Other participants in this users group may be interested in the very knowledgeable and useful attempts by several experts on those user groups to help others through these problems. (Please don't misunderstand me: I'm not punting for those user groups; I think different user groups with differing styles are a good thing.)

I have to join issue with you that these problems sound like "typical problems users experience when they upgrade ANYTHING".

I note that you say:

"The way your original message read, it sounded like you discovered some pervasive problem with 2006, but that doesn't appear to be the case at all, at least not from anything described in any of the posts you've referenced so far."

If I have given an over-stated impression I apologise, but I do think that my the extracts I have quoted from the messages posted on the other user groups indicate that there may indeed be a problem. It will be interesting to see whether you, Alan and others have similar or different experiences when you personally try installing 2006, which I gather from your messages you have not done yet. But if I am right in inferring that you have no personal experience yet, is it wise to pooh pooh the warnings of others, whose credentials seem - to me at least - to call for due weight to be attached to their warnings? May I ask: Are you personally going to ignore the warnings and take no extra care when you come to instal 2006?

My purpose in posting the message was to bring to the attention of participants in this users group some worrying things being said on other user groups. These user groups are are invaluable resource for participants, and advance warning of possible problems seems a useful function that could be of benefit to participants, eg those about to instal 2006 in a network/multi-user environment, even if only so that they take extra care to have a sound backup and perhaps to do a trial run on another computer.

Incidentally, I have no personal experience of 2006 as it is, as far as I know, not even available in this country - South Africa - yet.

Ken

Alan

I know that you are very knowledgeable about QB - not to mention, I notice, MS SBA - and I respect your knowledge, but I've noticed too that if it is a toss-up between sharing your expertise and having a good dig at other participants, the latter triumphs two times out of three. Come on, man! To some of us, these user groups are our lifeblood in the absence of adequate technical support from Intuit. Tennis needed John McEnroe and we need you but give us more of your expertise.

Ken

Distilled down to the pieces I've got time to respond to...

I backed up my original file, installed 2006, upgraded the original file using the upgrade tools and have not had a problem at, with 5 computers in my network AND terminal services set up.

I'm not sure what the issue is with the architecture of the network multiuser install. It's a non-issue. You simply install it. It asks if you want to host the file. If you say yes it does, if you say no, it doesn't. You can change that later. No installation architectural issue there.

With any give upgrade, there will be some pain on the part of (hopefully) a minority of users. That's expected. Seems like that's what is going on here. I see a few people complaining of real problems (loss of data) that can potentially be solved by restoring from backup. I see a larger number of people griping about user interface issues, but that's expected too.

So overall, I guess I don't see the problem. Back your files up, and install. If it fails, try it again. If there' a serious problem, revert to the original version with your backed up file. Not a big deal at all.

Rox has a few clients calling for refunds. So? Still doesn't sound lke a huge issue to me.

-Greg

The one out of three ratio was taught to me while watching old Charlie Chaplin movies. First you jump in the water and save a drowning puppy, then you kick two fat ladies in the ass.

We write accounting software and we've been in the business for over 13 years. We ALWAYS recommend backing up the data file whether you're upgrading, updating or just going home for the day. You can't back up too much or too often. Our software is extremely reliable but database corruption can happen no matter how careful you are. A lot of our customers are people who have outgrown Quickbooks, so I'll be curious to see how many converts we get due to their 2006 problems.

Rebecca

Greg,

You mentioned that you installed QB 2006 with Terminal Services.

Any issues there ?

We are looking at upgrading ro QB 2006 Pro *if* we can access it with Terminal Services.

Anything special about installing it on the Terminal Server itself?

Thanks,

*Watt