| Author |
Message |
Will
Guest
|
Posted:
Thu Dec 08, 2005 1:43 am Post subject:
Exchange 5.5 & ISINTEG |
|
|
Hi,
I have a client with an Exchange 5.5 server. The db went down and they had
to do some repairing on it. Now, isinteg is reporting 119 errors and 70
fixes all in folders everytime they run it. The number of errors, warnings &
fixes never improves.
When the DB is mounted, most of the users can get to their data, but there
are about 20 or so who have lost everything and cannot connect.
Any suggestions?
--
--Will
Take the dontspam out of the email to email me. (every even letter until
spc.net)
|
|
| Back to top |
|
 |
Paul Ford
Guest
|
Posted:
Thu Dec 08, 2005 1:59 am Post subject:
Re: Exchange 5.5 & ISINTEG |
|
|
The best option will be to restore from backup however as you have run
repairs on the database I presume a backup was not available. Do any of the
users have ost files ? If so, do not try and sync these to the mailbox
server as it will fail and then users wil be unable to access their OSTs.
When you say that the users cannot connect, what errors do they get ?
Did the customer run eseutil prior to isinteg ?
Regards
Paul Ford
Edge IT Ltd
"Will" <wdiolnlt@wsiplalmspc.net> wrote in message
news:B5275A85-5D7D-4B08-A563-EEE8E758428B@microsoft.com...
| Quote: | Hi,
I have a client with an Exchange 5.5 server. The db went down and they
had
to do some repairing on it. Now, isinteg is reporting 119 errors and 70
fixes all in folders everytime they run it. The number of errors,
warnings &
fixes never improves.
When the DB is mounted, most of the users can get to their data, but there
are about 20 or so who have lost everything and cannot connect.
Any suggestions?
--
--Will
Take the dontspam out of the email to email me. (every even letter until
spc.net)
|
|
|
| Back to top |
|
 |
Will
Guest
|
Posted:
Thu Dec 08, 2005 1:59 am Post subject:
Re: Exchange 5.5 & ISINTEG |
|
|
Paul,
Sadly, it appears that they did not have backups... there are a myriad of
issues with this client and that is one of them.
Yes, we tried eseutil /p prior to the isinteg.
The users are having a few different errors - some users (those that appear
to have 0 size folders) simply get unable to connect or unable to open folder
when they try opening their mailbox in Outlook. Others apparently can open
their email but don't see all their email and/or are receiving email directed
to others.
Right now we found a copy of their priv.edb file from 11/22/05 and have
replaced it in the directory and are doing another eseutil /p. (I've left
the site at this point) - it found some inconsistencies in the scan and was
repairing the database tables when we left.
I know that the short/best solution would likely be to accelerate their
upgrade to Win2003 Server & Exchange 2003... (and that the upgrade should
have been done a few months ago).
I have copies of the EDB as it was this evening prior to my replacement with
the older file as well.
--
--Will
Take the dontspam out of the email to email me. (every even letter until
spc.net)
"Paul Ford" wrote:
| Quote: |
The best option will be to restore from backup however as you have run
repairs on the database I presume a backup was not available. Do any of the
users have ost files ? If so, do not try and sync these to the mailbox
server as it will fail and then users wil be unable to access their OSTs.
When you say that the users cannot connect, what errors do they get ?
Did the customer run eseutil prior to isinteg ?
Regards
Paul Ford
Edge IT Ltd
"Will" <wdiolnlt@wsiplalmspc.net> wrote in message
news:B5275A85-5D7D-4B08-A563-EEE8E758428B@microsoft.com...
Hi,
I have a client with an Exchange 5.5 server. The db went down and they
had
to do some repairing on it. Now, isinteg is reporting 119 errors and 70
fixes all in folders everytime they run it. The number of errors,
warnings &
fixes never improves.
When the DB is mounted, most of the users can get to their data, but there
are about 20 or so who have lost everything and cannot connect.
Any suggestions?
--
--Will
Take the dontspam out of the email to email me. (every even letter until
spc.net)
|
|
|
| Back to top |
|
 |
|
|
|
|