We have identified and resolved the issue that is causing this problem.
If you have been affected and have lost files, please contact Intuit through the methods detailed in the Knowledge Base article here. You will be contacted by a specialist to evaluate your situation.
ALERT - QuickBooks Update Deletes Desktop - READ BEFORE RUNNING QUICKBOOKS Jan 08, 2008 11:30 pm
I have been having so strange problems with my quickbooks since this problem.
I am sending my hard drive to a hard drive recovery company. I lost 6 months of QB backup and figure it is worth one more try before I spend the months re-entering all my lost work.
First problem- Since 2 data recovery sessions did not recover my back up files (data rescue and file salvage) I figured it was time to just get to work. My QB is shutting down unexpectedly. I have stopped using it again.
Second problem- Deciding that my task of re-entry is far too great, and deciding to send of my hard drive. I wanted to perform a back up from my main computer QB and restore it to my laptop QB so I at least have my program access while it is gone- OK so my problem is I cannot get my backup to restore. I am wondering if this has something to do with the prior problems. I have tried to load QB pro 2006 & 2007 and neither will take the backup and restore. I am not sure what else to try.
Thank you! That was such an easy fix. I have certainly learned a lot more about not only quickbooks but my computer thanks to these many posts by all of you with a ton of QB & MAC knowledge.
ALERT - QuickBooks Update Deletes Desktop - READ BEFORE RUNNING QUICKBOOKS Feb 07, 2008 11:41 am
Is there a patch to prevent QuickBooks 2006 from trying to load an update every time I start up the program? I keep hitting CANCEL, but based on other posts, I'm afraid my desktop will be ruined.
Is there a patch to prevent QuickBooks 2006 from trying to load an update every time I start up the program? I keep hitting CANCEL, but based on other posts, I'm afraid my desktop will be ruined.
It won't... if it was going to, then it would have already.
Hitting cancel did not prevent the Desktop from getting deleted... that was unavoidable. Intuit has disabled the original server update and is now just trying to update your program to fix the original problem.
You can probably find the download link on this web site and update it yourself.
Please remember that this is a User-to-User community forum. If you come in to get an answer, see if there are any that you can provide. The more people who do that, the more likely you will get your answer.
ALERT - QuickBooks Update Deletes Desktop - READ BEFORE RUNNING QUICKBOOKS Feb 14, 2008 09:13 am
This post is about: Pro 2007 for Macintosh
I experienced difficulty after applying the R6 Update. I deleted the R6 file from my computer, deleted the preference file from the library files and re-installed the application, then ran the R5 Update and all seems to be working okay. Except for one thing, I have recently attempted to condense data for the 2006 accounting year and have received the following error message -
I experienced difficulty after applying the R6 Update. I deleted the R6 file from my computer, deleted the preference file from the library files and re-installed the application, then ran the R5 Update and all seems to be working okay. Except for one thing, I have recently attempted to condense data for the 2006 accounting year and have received the following error message - V9.0 R4 (M=/Volumes/QBB/07-Magma Build System/Stage/Projects/Magma/QuickBooks/Code/QuickBooks/transio.mm, L=2874, C= 225, V=3577 (DF9)) followed by an unexpected error message, essentially the transio.mm code again, followed by a fatal error causing the system to crash. Question: Is the inability to condense data associated with the fact that I do not have the R6 update applied to the program? Whatever help you can provide would be greatly appreciated. ~cws
Don't take this the wrong way because my comments are not directed specifically at you.
But if something like this had happened to me, the first thing I'd be doing is calling Intuit and demanding competent tech support. If they gave me any problems I'd be asking for a supervisor.
This discussion forum is great for little problems, annoyances, gripes, bugs, suggestions, etc. but I never understood this place as a first choice for a disaster that could threaten business operations.
If you'd rather not call Intuit, might I suggest a new thread where your problem would get more attention.
No offense taken. Just wanted to share what has worked for me regarding the R6 Update. That issue was directed to a support technician, but they were not able to assist me (the language barrier played a significant role in my dissatisfaction). The company accountant has been made aware of the current situation. Oddly, the program is still running, albeit slowly, without having condensed the data. I back up the program daily, once a week the files are taken off site. So for now, I feel as though I am covered. Please recognize that this forum was not my first attempt to correct what might one day be a problem, just thought that the two incidents might somehow be related and wondered if anyone else had experienced a similar situation pre- or post- the R6 Update. Thanks for taking the time to respond to my original post.
~cws
No offense taken. Just wanted to share what has worked for me regarding the R6 Update. That issue was directed to a support technician, but they were not able to assist me (the language barrier played a significant role in my dissatisfaction). The company accountant has been made aware of the current situation. Oddly, the program is still running, albeit slowly, without having condensed the data. I back up the program daily, once a week the files are taken off site. So for now, I feel as though I am covered. Please recognize that this forum was not my first attempt to correct what might one day be a problem, just thought that the two incidents might somehow be related and wondered if anyone else had experienced a similar situation pre- or post- the R6 Update. Thanks for taking the time to respond to my original post.
~cws
I understand.
Again, a new thread would get you a ton of attention for this problem where all the QB gurus would see it
My QB 2005 had a condense error like that for about a year; I usually condense every year or two. Tech support was not much help; aside from commenting that my data file was too big (right now it's around 45mb) they didn't have much to offer, aside from suggesting that I start over from scratch. I did start condensing a month at a time till I narrowed the "bad spot" down to a particular month in 2004 or something like that. I have not tried again since I upgraded from QB2005 to 2007 in November.
If anybody has anything to offer in regards to the file size, I'd be interested to hear it and would be happy to start a new thread to do so.
Hi Colleen - there's really no such thing as 'too big'. Tech Support has seen QB for Windows files as large as two gigs and those required 'help' because of an OS limitation, not QB.
There are limits to the number of items on lists but there are no limits to the number of transactions or the size of a datafile. The only thing you need to be concerned about is some kind of performance degradation on your system. If it starts taking AGES to run a report or you can brew a pot of coffee while launching QB, then you'd need to start looking at starting a new file.
If and when the time comes that you decide you want to start a new file, try to do it at year end. It isn't a 'terrible' process and that's a good time to do housekeeping too. You can import all your lists into a new file - you can delete ancient customers/vendors/accounts because there's no data attached to them. You pretty much manually enter balance forwards from a Balance Sheet but your outstanding A/R and A/P have to be rebuilt brick-by-brick so you've got accurate records for your customers and vendors.
So, until YOU can't stand it anymore there's no reason to start another company and I wouldn't even bother condensing because the reduction is minimal at best.
ALERT - QuickBooks Update Deletes Desktop - READ BEFORE RUNNING QUICKBOOKS Feb 20, 2008 09:08 am
This post is about: Pro 6.0 for Macintosh
I launched QuichBooks on December 17, 2007 and had my desktop erased. After reporting/registering the problem, I was instructed to purchase the Prosoft Data Rescue 2 software and a hard drive a bit larger that the drive affected and I would be reimbursed. The receipts were emailed on 1.2.08 to machelp@intuit. On 1.7.08 an Intuit employee emailed me and said "Processing usually takes 7 to 10 business days." The last reply email from machelp@intuit was received on 1.23.08 asking for my patience.
Does anyone know how long should I expect to wait for reimbursement?
ALERT - QuickBooks Update Deletes Desktop - READ BEFORE RUNNING QUICKBOOKS Feb 25, 2008 05:13 pm
MAC DEATH UPDATE for QB2006 V8.0.3 R5
There is a lot of data here. I installed the Update but haven't run QB. What do I do????
Delete and use last backup before backup.
Is it Version V8.0.3 R5????
I can't believe I was just recently advised to install it on this forum. Figures.
Fortunately I didn't open QB. So I just deleted the file and the update I downloaded.
Have been too busy to install on my desktop so I guess I lucked out.
How about fixing the other bugs in Pro 2005, Pro 2006 and Pro 2007 while you are at it.
Boy Intuit is on a roll. Standard front line procedure: Never accept responsibility for anything not good, Deny everything, Blame the Customer, but Backup procedure: play it down, don't damager sales, keeping issue out of sight and quiet and only resolve what won't go away.
What Next????
TheBear
Time is too valuable to waste editing moving targets in the fields. Fix the scrolling feature problems, live in the solution and give us all a break. Just fix the problems. Ya think?
"TheBear"
I can't make any sense out of your post. Did you lose data? Or just download an updater then not install it?
The QB 2006 bug was supposed to be just a one-time fluke in December. I had a client safely using QB 2006 in January, before their free 2007 upgrade arrived.
Switch to 2007 if 2006 makes you nervous. You might still be able to get a free one.
Hi Colleen - there's really no such thing as 'too big'. Tech Support has seen QB for Windows files as large as two gigs and those required 'help' because of an OS limitation, not QB. There are limits to the number of items on lists but there are no limits to the number of transactions or the size of a datafile. The only thing you need to be concerned about is some kind of performance degradation on your system. If it starts taking AGES to run a report or you can brew a pot of coffee while launching QB, then you'd need to start looking at starting a new file. If and when the time comes that you decide you want to start a new file, try to do it at year end. It isn't a 'terrible' process and that's a good time to do housekeeping too. You can import all your lists into a new file - you can delete ancient customers/vendors/accounts because there's no data attached to them. You pretty much manually enter balance forwards from a Balance Sheet but your outstanding A/R and A/P have to be rebuilt brick-by-brick so you've got accurate records for your customers and vendors. So, until YOU can't stand it anymore there's no reason to start another company and I wouldn't even bother condensing because the reduction is minimal at best. (p.s. good to see you back here)
Hi Jfisher
No, my QB runs fine, it's just annoying that there's one spot in 2004 or so that I can't condense past. But that's ok if the size is not an issue. I wonder why the tech misinformed me (maybe it matters in Windows?)
Anyway, especially since a lot of my sales are of inventory items, not much was getting condensed anyway, as you point out.
And starting over would be a big pain, as I order a lot of stuff for clients and use the Time/Costs link a lot. Please, please don't break the chain!
And thanks for the gift, it was an unexpected pleasure.
The entire incident revolved around a QB bug COMBINED with an Intuit server problem on three days in December. Server problem was immediately shut down to prevent file deletion issue.
Find rjkconst on the map!