4294966277 error when starting information store

Hi,
I have run the eseutil /p on both my priv and pub files... They are both consistent now.... the dir.edb file is also consistent...
However I am still receiving the above 4294966277 error when starting up the information store...
Any ideas?
Darktide00Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

munichpostmanCommented:
ISINTEG - Patch

give it a go. I am sure it will work. Be patient, let it run. When it is finish you will be able to start the store again.
0
Darktide00Author Commented:
Hey, Glad to see you are here... I need your help bad!
0
Darktide00Author Commented:
I am making a backup of the MDB file so I don't lose what I have so far
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Darktide00Author Commented:
Do I have to have any services on to do this?
When I ran it I got the private store could not be updated reason: DS_E_COMMUNICATIONS_PROBLEM
0
Darktide00Author Commented:
I got the ISINTEG to go...
It completed successfully....
Same 429 error wwhen I attempt to start the store
0
Darktide00Author Commented:
I just tried to restart the server....
I got event id 1005
Unable to start the Microsoft Exchange Information Store. Error 0xfffffc05.
0
munichpostmanCommented:
DS_E_COMMUNICATIONS_PROBLEM errors are usually related to permissions.

Are you logged on the Exchange Server using the Exchange 5.5 service account?
Had the password or account changed in the last few days?
0
marc_nivensCommented:
That error is Jet_errPageNotInitialized (also known as a -1019).  These are usually caused by hardware failures.  If you have repaired the databases, make sure you have removed all log files and the chk file.  If it still fails to start, with only the edb files present, then I'm sad to say they are unrecoverable.  At that point you will need to go to a previous backup.  However, please try removing the log/chk files first.

Oh, and the only error isinteg -patch will fix is a 1011 error.  It occurs when another store has been brought up with the present dir.edb.  The reason I tell people to only run isinteg -patch in the case of a 1011 error is that running after an online restore will corrupt the database.  So its better to only run it when you get the 1011 error.  
0
Darktide00Author Commented:
Hi,
I have already run the patch....
When I run the eseutil /g on priv file it errors out with a jet_err 1206 non-db file or db corrupted
0
Darktide00Author Commented:
Do I need to run the eseutil /p again?
0
marc_nivensCommented:
Assuming you moved the logs/chk files out and you still cannot start the IS, your database file is corrupt beyond repair.  You will need to either restore from backup or start with a blank database.
0
Darktide00Author Commented:
The last full backup was quite a while ago.....
There is over 18gigs of info in the priv.edb file and it is showing consistent...
Is there any other way to recover it? or move the info to a new server?
0
marc_nivensCommented:
The only other option at this point is 3rd party tools.  Ontrack has one that can extract data from a dead store (at least as much as possible).  Check this out:

http://www.ontrack.com/powercontrols/
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ddrewtxCommented:
Take a look at http://support.microsoft.com/default.aspx?kbid=242364, which talks about the error 4294966277 that you are getting.  I agree with Marc Nivens on his assessment, because the 0xfffffc05 error translates to a -1019 error (typically a hardware problem - search on that in Google or MSKB, and you should find the correlation).  We can keep chasing this, but your fastest way to get this back up and running with your data is using a utility to extract the data out of the store, and then create the new mailboxes on the new server, and import it back in. I've been down this road before, but it's your (and your bosses) decision...

Hope this helps...

Dale Drew
0
Darktide00Author Commented:
Hi,
Thank you so much for all your help on this one... It seems like a loss from here. However I turned it into a golden opportunity to finally upgrade out of 5.5 to 2003 all the way...
Using the powertools I was able to get all the mailboxes and create pst files. I then stopped the ADC and the site replicator for now. Created new mailboxes in 2003 then imported their pst's into their new mailboxes... Whew what a ride man!!! That powercontrol tool is way worth the 1500 bucks!!!!
Thanks again!
Bill
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.