Home Page link  

Q2006: Aborts On Startup

  
Groups | Search | About
User Password
Register Now! Lost Password?

Quicken Personal Finance Discussions - Quicken - personal finance software discussions

 Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Q2006: Aborts On Startup John 08-28-2006
Posted by John on October 2, 2006, 4:18 pm
Please log in for more thread options
 I had the program working on yet another computer. Everything was
working fine until I tried to do a Web Connect download from Charter
One Bank. After this download aborted I was not able to get my data
file to load in Quicken. I called technical support and he had me
reinstall Quicken. After reinstalling Quicken I was able to load my
data file. We ran a Validate and a Super Validate and there was no
data corruption. I was able to use Quicken again. I tried to do a
backup which ended with an error (#7097), which I sent to Intuit.. I
kept trying to load the file by doulble clicking on the data file and
by opening it after getting into Quicken. I got additional error
messages (#7157 & 7085). When I tried to send these error reports they
would not go and I had to abort the sending in Task Manager.

How can I be using the program with no problem and then get 1 error and
the program will not load my data file again? By the way I also tried
using the files I had backed up previouslly (prior to the first
problem) that worked fine and had no data corruption and they would not
load either. Now every time I try to use Quicken with my data file, it
says that it is load the data but then stops and I am back at my
desktop.

HELP!!!!
John Novak


Posted by dllapides on October 2, 2006, 10:25 pm
Please log in for more thread options
 John--

This sounds suspiciously like a problem I have encountered with Q2004
Premier, versions R3-R5. I've been following this string as I suspect
I will finally have to upgrade to Q2007 this year.

One solution that works for me (before the error re-appears) is to copy
the data file (I usually will do a 1-1-1965 through 1-1-2010 copy) and
then use the copy. (More precisely, have Q rename my datafile,
validate, super validate and copy back into my standard file name which
I continue to use until the problem re-appears.)

I'm running XP Pro with 1 Gig of RAM and ooodles of harddisk space.
The only recent software updates are Window's monthly fixes and
McAfee's episodic updates. No recent hardware updates (or except as
noted driver updates).

My file QDF file is 47.7 megabytes. Though the problem started around
the low 30's.

Below is one of my old emails, annotated to update it


Date: Tues, Dec 6 2005 12:00 am
Groups: alt.comp.software.financial.quicken


"Arnie Goetchius:

I've reported this error several times over the years since I upgraded
to Q2004. It started for me with R3 and has continued to the present
with Q2004 R5.


If you search this Usergroup, you will find similar errors back to at
least Q2002. (I jumped from Q2001 to Q2004, so I cannot speak from
experience). But interestingly, I cannot recall anyone complaining
about memory read errors in Q2005 or Q2006. I have seen messages in
this Usergroup stating that the newer versions just stopped. Maybe
Intuit eliminated the error message? THAT SEEMS TO BE CONSISTENT WITH
YOUR 2007 EXPERIENCE.

I would doubt that it is a physical memory issue. Do you have this
problem with other software? I don't, and I may have a dozen
applications open at any one time. FOR THE RECORD, THE PROBLEM OCCURS
WHEN QUICKEN IS THE ONLY PROGRAM RUNNING OR WHEN SEVERAL PROGRAMS ARE
OPEN.


I think it is a software bug that is harmless until you have either
lots of data (I started using one of the early DOS versions, my
transaction history goes back to 1990, and my investment history goes
back to 1967 (a gift of stock which I still own), lots of accounts
(some 100+, though most are closed), lots of investments over the years
(but I usually stop keeping current price history on stuff I've
dumped), or something similar which causes an internal table to expand
to a size greater than the software engineer thought was necessary.

I WOULD GUESS THAT THE REASON YOU GET A DATAFILE TO WORK ON SOME
COMPUTERS BUT NOT OTHERS IS PROBABLY RELATED TO MY EXPERIENCE WITH
HAVING QUICKEN COPY MY DATAFILE AND THEN USE THE COPY -- THE COPY
ROUTINE RE-SETS SOME VALUE WHICH CHANGES EVERYTIME WE OPEN THE
DATAFILE. THE ONLY WAY TO VERIFY THIS WOULD PROBABLY BE TO CLOSE A
DATAFILE SET, MAKE A COPY USING WINDOWS. RE-OPEN THE OLD DATAFILES IN
QUICKEN. CHANGE 1 CHARACTER IN SOME RECORD. THEN CHANGE THE CHARACTER
BACK. CLOSE QUICKEN, AND THEN DO A BYTE LEVEL COMPARE. I HAVE A HUNCH
THERE WILL BE DIFFERENCES.

That's all I'm saying. ...... BUT IF YOU DO FIND A CURE, PLEASE POST
IT.

-dll

John wrote:

> HELP!!!!
> John Novak


Posted by John on October 3, 2006, 6:00 pm
Please log in for more thread options
I am using WIndows XP Professional and also have lots of hard drive
space. If it is in fact a software bug why won't Intuit acknowledge
it. If you call them with a large data file, they immediately tell you
reduce the size considerably.

I am confused by the fact that it was working fine until I ded a web
connect download, then the problems started. The file would not open.
Why did reinstalling the software fix the problem temporarily? There
must be something written to the registry or to some hidden file that
prohibits the large file from loading while allowing smaller files to
load even though the larger file is not corrupted. Someone must know
what is causing this problem!!!

If the problem is an internal data file that is too small, why doesn't
Intuit fix it? I can't believe that it is in their best interest to
have unhappy customers and a product that is buggy!!

Thanks,
John Novak


dllapides wrote:
> John--
>
> This sounds suspiciously like a problem I have encountered with Q2004
> Premier, versions R3-R5. I've been following this string as I suspect
> I will finally have to upgrade to Q2007 this year.
>
> One solution that works for me (before the error re-appears) is to copy
> the data file (I usually will do a 1-1-1965 through 1-1-2010 copy) and
> then use the copy. (More precisely, have Q rename my datafile,
> validate, super validate and copy back into my standard file name which
> I continue to use until the problem re-appears.)
>
> I'm running XP Pro with 1 Gig of RAM and ooodles of harddisk space.
> The only recent software updates are Window's monthly fixes and
> McAfee's episodic updates. No recent hardware updates (or except as
> noted driver updates).
>
> My file QDF file is 47.7 megabytes. Though the problem started around
> the low 30's.
>
> Below is one of my old emails, annotated to update it
>
>
> Date: Tues, Dec 6 2005 12:00 am
> Groups: alt.comp.software.financial.quicken
>
>
> "Arnie Goetchius:
>
> I've reported this error several times over the years since I upgraded
> to Q2004. It started for me with R3 and has continued to the present
> with Q2004 R5.
>
>
> If you search this Usergroup, you will find similar errors back to at
> least Q2002. (I jumped from Q2001 to Q2004, so I cannot speak from
> experience). But interestingly, I cannot recall anyone complaining
> about memory read errors in Q2005 or Q2006. I have seen messages in
> this Usergroup stating that the newer versions just stopped. Maybe
> Intuit eliminated the error message? THAT SEEMS TO BE CONSISTENT WITH
> YOUR 2007 EXPERIENCE.
>
> I would doubt that it is a physical memory issue. Do you have this
> problem with other software? I don't, and I may have a dozen
> applications open at any one time. FOR THE RECORD, THE PROBLEM OCCURS
> WHEN QUICKEN IS THE ONLY PROGRAM RUNNING OR WHEN SEVERAL PROGRAMS ARE
> OPEN.
>
>
> I think it is a software bug that is harmless until you have either
> lots of data (I started using one of the early DOS versions, my
> transaction history goes back to 1990, and my investment history goes
> back to 1967 (a gift of stock which I still own), lots of accounts
> (some 100+, though most are closed), lots of investments over the years
> (but I usually stop keeping current price history on stuff I've
> dumped), or something similar which causes an internal table to expand
> to a size greater than the software engineer thought was necessary.
>
> I WOULD GUESS THAT THE REASON YOU GET A DATAFILE TO WORK ON SOME
> COMPUTERS BUT NOT OTHERS IS PROBABLY RELATED TO MY EXPERIENCE WITH
> HAVING QUICKEN COPY MY DATAFILE AND THEN USE THE COPY -- THE COPY
> ROUTINE RE-SETS SOME VALUE WHICH CHANGES EVERYTIME WE OPEN THE
> DATAFILE. THE ONLY WAY TO VERIFY THIS WOULD PROBABLY BE TO CLOSE A
> DATAFILE SET, MAKE A COPY USING WINDOWS. RE-OPEN THE OLD DATAFILES IN
> QUICKEN. CHANGE 1 CHARACTER IN SOME RECORD. THEN CHANGE THE CHARACTER
> BACK. CLOSE QUICKEN, AND THEN DO A BYTE LEVEL COMPARE. I HAVE A HUNCH
> THERE WILL BE DIFFERENCES.
>
> That's all I'm saying. ...... BUT IF YOU DO FIND A CURE, PLEASE POST
> IT.
>
> -dll
>
> John wrote:
>
> > HELP!!!!
> > John Novak


Posted by dllapides on October 3, 2006, 11:28 pm
Please log in for more thread options
John--

I got out of the software industry in 1975, so I am obsolete. But one
of my projects back then was to figure out why a print routine in a
statistical package "bombed" whenever the number of pages exceeded
something like 850 pages (that big 132 column paper). The software
module was probably 2,000 punch cards long, in a mixture of COBOL and
assembly language. Needless to say, it was a very difficult bug to
track down, and you had to take over a mainframe to try fixes.

But in those days, we all could read and write assembly language and go
though it line by line until we found the error. Needless, to say a
routine that worked on 750 pages of printout but not 850 pages had a
very obscure bug.

My point is we had a fighting chance. We had a good idea where the
problem was and had tools that let us monitor the situation and dealt
with static, lock step code. We also had a management that wanted the
bug fixed because it affected a lot of important folks in the
organization.

The guys and gals at Intuit if they were to chime in would probably
tell us that Quicken is 1,000,000 lines long of some process driven
(i.e., mouse click activated) programming language and the problem
could literally be anywhere. And I'll hazard a guess that you are not
willing to share with them a live data file that they could use to
duplicate the problems. I know I would not.

But why do the help line folks give you mis-information? I suspect
most of them are reading from a script. The folks who wrote the script
are a committee of marketing folks who want customers to feel like
Intuit is being helpful. (The lawyers sure are not going to let them
say "We don't have a clue why it doesn't work.")

Is it fixable? Unless Intuit wants to incur the cost of re-writing
Quicken from scratch, I think it will pure happenstance that this gets
fixed.

PS-- I tried my 1 cent change, and then change back, found my ancient
PC Magazine COMPARE.COM DOS utility from 3 or 4 computers ago. Yep,
the QDF file and the almost duplicate QDF file show differences at the
byte level. This gives credence to my thought that the database itself
constantly changes whih results in the episodic nature of the problem.

Where do we go? Heck if I know. With my historical data, converting
to MS Money would not be much fun.

-dll


Posted by John on October 7, 2006, 12:09 am
Please log in for more thread options
So my only options are to stop using Quicken or to delete the majority
of my historical data, right? The most frustrating part is that
Intuit's technical support will not even entertain the fact that there
is a problem! If they did, maybe some of the users having this problem
would work with them during beta testing to fix the problem. But if
you won't even acknowledge that there is a problem it will never get
fixed. Their solution is always to get rid of all but a coule of years
of data. Not only do I not want to do this, I am sure that if I broke
down and did it they would solve the problem and my data would be gone.
What options do I have? Who can communicate with Intuit to start a
dialog to get the problem fixed?

Thanks,
John Novak

dllapides wrote:
> John--
>
> I got out of the software industry in 1975, so I am obsolete. But one
> of my projects back then was to figure out why a print routine in a
> statistical package "bombed" whenever the number of pages exceeded
> something like 850 pages (that big 132 column paper). The software
> module was probably 2,000 punch cards long, in a mixture of COBOL and
> assembly language. Needless to say, it was a very difficult bug to
> track down, and you had to take over a mainframe to try fixes.
>
> But in those days, we all could read and write assembly language and go
> though it line by line until we found the error. Needless, to say a
> routine that worked on 750 pages of printout but not 850 pages had a
> very obscure bug.
>
> My point is we had a fighting chance. We had a good idea where the
> problem was and had tools that let us monitor the situation and dealt
> with static, lock step code. We also had a management that wanted the
> bug fixed because it affected a lot of important folks in the
> organization.
>
> The guys and gals at Intuit if they were to chime in would probably
> tell us that Quicken is 1,000,000 lines long of some process driven
> (i.e., mouse click activated) programming language and the problem
> could literally be anywhere. And I'll hazard a guess that you are not
> willing to share with them a live data file that they could use to
> duplicate the problems. I know I would not.
>
> But why do the help line folks give you mis-information? I suspect
> most of them are reading from a script. The folks who wrote the script
> are a committee of marketing folks who want customers to feel like
> Intuit is being helpful. (The lawyers sure are not going to let them
> say "We don't have a clue why it doesn't work.")
>
> Is it fixable? Unless Intuit wants to incur the cost of re-writing
> Quicken from scratch, I think it will pure happenstance that this gets
> fixed.
>
> PS-- I tried my 1 cent change, and then change back, found my ancient
> PC Magazine COMPARE.COM DOS utility from 3 or 4 computers ago. Yep,
> the QDF file and the almost duplicate QDF file show differences at the
> byte level. This gives credence to my thought that the database itself
> constantly changes whih results in the episodic nature of the problem.
>
> Where do we go? Heck if I know. With my historical data, converting
> to MS Money would not be much fun.
>
> -dll


Similar ThreadsPosted
Q2005 freezes on startup October 31, 2006, 2:14 pm
Q2008P Startup Issue July 10, 2008, 12:02 pm
TurboTax 2007 - Startup Return? March 2, 2008, 6:54 pm
startup annoyances -- quicken 2008 home & business June 3, 2008, 10:03 pm
Q2006 Mac registration nag July 3, 2006, 6:57 pm
Q2006 and 401k August 22, 2006, 6:32 pm
Q2006 H&B question October 16, 2006, 9:19 am
Q2006 wants uninstall itself October 16, 2006, 4:32 pm
Help Unlocking Q2006 Deluxe July 14, 2006, 5:22 pm
Help - Payment question (Q2006) August 13, 2006, 2:15 am

Contact Us | Privacy Policy
This site is not affiliated with Intuit - makers of Quickbooks and Quicken software
This site is not affiliated with Sage Software - makers of Peachtree accounting software
XML SitemapXML Sitemap