Darktide00
asked on
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?
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?
ASKER
Hey, Glad to see you are here... I need your help bad!
ASKER
I am making a backup of the MDB file so I don't lose what I have so far
ASKER
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_PROBLE M
When I ran it I got the private store could not be updated reason: DS_E_COMMUNICATIONS_PROBLE
ASKER
I got the ISINTEG to go...
It completed successfully....
Same 429 error wwhen I attempt to start the store
It completed successfully....
Same 429 error wwhen I attempt to start the store
ASKER
I just tried to restart the server....
I got event id 1005
Unable to start the Microsoft Exchange Information Store. Error 0xfffffc05.
I got event id 1005
Unable to start the Microsoft Exchange Information Store. Error 0xfffffc05.
DS_E_COMMUNICATIONS_PROBLE M 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?
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?
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.
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.
ASKER
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
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
ASKER
Do I need to run the eseutil /p again?
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.
ASKER
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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
Hope this helps...
Dale Drew
ASKER
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
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
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.