Re:Corrupt Company file repair please help

Posted by Charlie on October 11, 2007, 7:52 am

Please log in for more thread options

I am looking for the tools or knowledge to fix the file.

Posted by David Smith on October 11, 2007, 8:29 am

Please log in for more thread options

>I am looking for the tools or knowledge to fix the file.

How about some more information -error codes, messages, description of
attempt to open file?

Posted by Charlie on October 11, 2007, 8:23 pm

Please log in for more thread options

>>I am looking for the tools or knowledge to fix the file.

>How about some more information -error codes, messages, description of

>attempt to open file?

The QB error message was error code -6000,-301 which did not mean much.
I then went to the adptive server tools in which case it showed me the the data
file was shorter
than expected. Assertion failed 201129 file is shorter than expected--
transation rolled back

I tried to add data to the file to fill up the size. I grabed the last 16 lines
in the data file and
copied them repeatedly until I did not get the me shorter than expected message.
I used 16
because that was what I though I could see as the pattern.

I got behond that to get this set of errors.
Assertion failed 201417
Invalid count or free space offset on a table page.

Since I do not know the encryption code I can not read the data to see if I was
close.

The backup is way to old. I tried going up a release but that did not work
either. Since I can
not open the file to connect I can not run a dbvaildate.

Any thoughts?

Posted by Phil Nelson on October 12, 2007, 12:44 am

Please log in for more thread options

Charlie wrote:

>>> I am looking for the tools or knowledge to fix the file.

>>>

>> How about some more information -error codes, messages, description of

>> attempt to open file?

> The QB error message was error code -6000,-301 which did not mean much.

> I then went to the adptive server tools in which case it showed me the the

data file was shorter

> than expected. Assertion failed 201129 file is shorter than expected--

transation rolled back

> I tried to add data to the file to fill up the size. I grabed the last 16

lines in the data file and

> copied them repeatedly until I did not get the me shorter than expected

message. I used 16

> because that was what I though I could see as the pattern.

> I got behond that to get this set of errors.

> Assertion failed 201417

> Invalid count or free space offset on a table page.

> Since I do not know the encryption code I can not read the data to see if I

was close.

> The backup is way to old. I tried going up a release but that did not work

either. Since I can

> not open the file to connect I can not run a dbvaildate.

> Any thoughts?

I think you should not treat a database file that way unless
the accuracy of the information contained doesn't matter.

I also think when you have an important file that is inexplicably
corrupt and no backup, you should make a mirror image of the drive
that file was on before doing anything else.

Further I think if you didn't do the mirror first, it's probably too
late now, but you should do it anyway, because no matter how bad you
think things are now, they could be worse.

If you think things can't get any worse, seek assistance, because if
you touch complex equipment while believing that things can't get any
worse, you will probably make things worse.

The process of mirroring will give you useful information- If you get
a bunch of errors when mirroring the drive, then you know you need a
new drive, and probably what happened to your file. Also the mirror
program might be able to recover some or all of the lost sectors and,
if lost sectors were the cause of the file damage, some or all of the
file. If you edit the file first, recovery is much more difficult.

If you get a clean mirror, you have other problems, but at least you
have a way to recover if your repair efforts make things worse, which
they probably will if you have no backup.

One final thought- Do the backups.

--
Phil Nelson

Posted by allstreamit on October 13, 2007, 10:42 am

Please log in for more thread options

I recommend www.quickbooksfilerepair.com

On Oct 12, 12:44 am, Phil Nelson

> Charlie wrote:

> >>> I am looking for the tools or knowledge to fix the file.

> >> How about some more information -error codes, messages, description of

> >> attempt to open file?

> > The QB error message was error code -6000,-301 which did not mean much.

> > I then went to the adptive server tools in which case it showed me the the

data file was shorter

> > than expected. Assertion failed 201129 file is shorter than expected--

transation rolled back

> > I tried to add data to the file to fill up the size. I grabed the last 16

lines in the data file and

> > copied them repeatedly until I did not get the me shorter than expected

message. I used 16

> > because that was what I though I could see as the pattern.

> > I got behond that to get this set of errors.

> > Assertion failed 201417

> > Invalid count or free space offset on a table page.

> > Since I do not know the encryption code I can not read the data to see if I

was close.

> > The backup is way to old. I tried going up a release but that did not work

either. Since I can

> > not open the file to connect I can not run a dbvaildate.

> > Any thoughts?

> I think you should not treat a database file that way unless

> the accuracy of the information contained doesn't matter.

> I also think when you have an important file that is inexplicably

> corrupt and no backup, you should make a mirror image of the drive

> that file was on before doing anything else.

> Further I think if you didn't do the mirror first, it's probably too

> late now, but you should do it anyway, because no matter how bad you

> think things are now, they could be worse.

> If you think things can't get any worse, seek assistance, because if

> you touch complex equipment while believing that things can't get any

> worse, you will probably make things worse.

> The process of mirroring will give you useful information- If you get

> a bunch of errors when mirroring the drive, then you know you need a

> new drive, and probably what happened to your file. Also the mirror

> program might be able to recover some or all of the lost sectors and,

> if lost sectors were the cause of the file damage, some or all of the

> file. If you edit the file first, recovery is much more difficult.

> If you get a clean mirror, you have other problems, but at least you

> have a way to recover if your repair efforts make things worse, which

> they probably will if you have no backup.

> One final thought- Do the backups.

> --

> Phil Nelson- Hide quoted text -

> - Show quoted text -