Microsoft Exchange 5.5 Offline Restore Problems...
Ok, here goes my trials, tribulations and questions....
Yesterday we had a catastrophic disk failure on our Exchange 5.5 / Win2k server. The server was running Win2k with latest service pack and Exchange 5.5 Enterprise/SP4. The main drive failed AND the mirrored drive failed as well. What are the odds? We didn't have a backup of the database, so I spent most the day trying to retrieve data from the drive and I was able to successfully get the data off the drive with Winternals ERD. I have been planning to migrate this to a new server anyways, just not under these conditions. I had unwittingly deleted the logical server from the Site/Organization at the other Exchange server, so I know that screwed me on this whole offline restore procedure. Here's what I did:
I installed Exchange 5.5 and SP4 to a new server which was offline and named the same as the previous server.
Copied the priv.edb, pub.edb and dir.edb to the server in the appropriate places
ran eseutil /r on each of them
ran isinteg -patch on the database
brought the server up and it was running fine, so I connected it back to the network
Email was up an running at around midnight my time, so I called it a night at around 1am when I figured it was stable. When I woke up this morning and called in to see if all was well, I found that email was up and running but there were no names in the directory anymore. I am assuming because I deleted the logical server that it replicated with the existing server and wiped those names. I restored the databases again and repeated the procedure and haven't brought up the other server yet, which is only for OWA anyways. Now It is running again but I get a message that:
"Could not start the Microsoft Exchange Event Service on Local Computer.
The service did not return an error. This could be an internal Windows error or an internal service error.
If the problem persists, contact your system administrator."
In the event log I see:
Source: MSExchangeES
Event ID: 5
An unexpected MAPI error occurred. Error returned was (0x80004005).
I have tried several of the solutions I have found for this type of error, but I have not had any luck. The event service was fine after the initial restore, I am assuming that there was a problem with the replication between the servers last night that caused this.
1) I need help with settings to get this ES working again
2) I need help configuring the other server to properly communicate and replicate with this new server so as not to lose the complete directory again.
Thanks.....
Yesterday we had a catastrophic disk failure on our Exchange 5.5 / Win2k server. The server was running Win2k with latest service pack and Exchange 5.5 Enterprise/SP4. The main drive failed AND the mirrored drive failed as well. What are the odds? We didn't have a backup of the database, so I spent most the day trying to retrieve data from the drive and I was able to successfully get the data off the drive with Winternals ERD. I have been planning to migrate this to a new server anyways, just not under these conditions. I had unwittingly deleted the logical server from the Site/Organization at the other Exchange server, so I know that screwed me on this whole offline restore procedure. Here's what I did:
I installed Exchange 5.5 and SP4 to a new server which was offline and named the same as the previous server.
Copied the priv.edb, pub.edb and dir.edb to the server in the appropriate places
ran eseutil /r on each of them
ran isinteg -patch on the database
brought the server up and it was running fine, so I connected it back to the network
Email was up an running at around midnight my time, so I called it a night at around 1am when I figured it was stable. When I woke up this morning and called in to see if all was well, I found that email was up and running but there were no names in the directory anymore. I am assuming because I deleted the logical server that it replicated with the existing server and wiped those names. I restored the databases again and repeated the procedure and haven't brought up the other server yet, which is only for OWA anyways. Now It is running again but I get a message that:
"Could not start the Microsoft Exchange Event Service on Local Computer.
The service did not return an error. This could be an internal Windows error or an internal service error.
If the problem persists, contact your system administrator."
In the event log I see:
Source: MSExchangeES
Event ID: 5
An unexpected MAPI error occurred. Error returned was (0x80004005).
I have tried several of the solutions I have found for this type of error, but I have not had any luck. The event service was fine after the initial restore, I am assuming that there was a problem with the replication between the servers last night that caused this.
1) I need help with settings to get this ES working again
2) I need help configuring the other server to properly communicate and replicate with this new server so as not to lose the complete directory again.
Thanks.....
amaheshwari
You mean that you are not having any name in directory is your old server has those name.If so then what you can do is go to tools in Exchange administrator of old server and then do directory export to csv file and then import directory in exchnage 5.5 new server .
ASKER
The problem is in the new server resides all the names which is where they were, but in the old server they do not exist. When the directory replication takes place, the names disappear from the new server. Will this method work the other way around as well? Export from the new server and import to the old server?
or
To resolve this issue, use a different service account to start the Event Service, or modify the permissions on the current service account.
To resolve this issue, use a different service account to start the Event Service, or modify the permissions on the current service account.
yes but you said that now there is no name in new as well as old server.
You may try this :
To resolve this issue if you know the correct organization, server or site name, modify the appropriate registry value: 1. Start Registry Editor (Regedt32.exe).
2. Locate the appropriate value (Enterprise, Server or Site) under the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\
3. On the Edit menu, click String, modify the value to match the correct organization (enterprise), server or site name, and then click OK.
4. Quit Registry Editor.
NOTE: The Exchange Server organization, server and site names are case sensitive. Make sure that you type the correct name and case for each value.
To resolve this issue if you know the correct organization, server or site name, modify the appropriate registry value: 1. Start Registry Editor (Regedt32.exe).
2. Locate the appropriate value (Enterprise, Server or Site) under the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\
3. On the Edit menu, click String, modify the value to match the correct organization (enterprise), server or site name, and then click OK.
4. Quit Registry Editor.
NOTE: The Exchange Server organization, server and site names are case sensitive. Make sure that you type the correct name and case for each value.
ASKER
I have tried changing the service account and permissions - Didn't work
I have looked at those registry entries and they are correct
THanks
I have looked at those registry entries and they are correct
THanks
yes but you said that now there is no name in new as well as old server.Is this correct ?
ASKER
Correct, the only mailbox that stayed in the new server after the night was administrator. I have exported all from the new server and then imported to the old server. That should resolve that issue, correct?
So do you have all the entries in new server or it is blank.
ASKER
All the entries were in the new server and not the old. Now I have exported from the new, merged with the old then exported from the old after the merge and merged with the new so now both have identical directories.
ok so you got your directory entries back .
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That's exactly how I did it Exchange Admin....
Are you still facing same problem ?
Are you still getting same error of Exchange Event Service?
Are you still getting same error of Exchange Event Service?
ASKER
Yes, I am still getting the event service error, same one.
"That's exactly how I did it Exchange Admin...."
No I don't think you did.
Notice that I did not say to bring back the original DIR.EDB.
You said in your original post that you restored the DIR.EDB.
No I don't think you did.
Notice that I did not say to bring back the original DIR.EDB.
You said in your original post that you restored the DIR.EDB.
ASKER
I did it that way initially and I didn't hae any users in the recipients container and when I ran the DS/IS, there were recipients. The problem occurred overnight when the servers replicated. I suppose you are suggesting that I just delete it all and start again?
ASKER
Ok, I have noticed now that since it's been awhile and replication has taken place, all the email aliases have disappeard. Some people had somebody@blah.com as well as SBody@blah.com and now those are gone except for the original domain addresses.
ASKER
I'm still having the Event Service issues, any help out there?
ASKER
Anyone? Any help here at all?
Have you tried removing the Event service.
Run the Exchange setup program, uncheck ONLY the event service.
Then after it is removed, reboot the server.
Run setup again to install the event service.
Run the Exchange setup program, uncheck ONLY the event service.
Then after it is removed, reboot the server.
Run setup again to install the event service.
ASKER
I have tried that process, during the process it said that a file could not be removed so I ignored it. The process then finished and I restarted the server. The Event Service shows up in the services but doesn't start, when I try to add it in from Exchange installation, it will not install saying that the event service did not start in a timely manner. According to the installer, it is not installed.