Major problems with restoring Exchange 2007 server
Hi,
I am currently testing out a backup strategy for our Exchange 2007 mail server. I have a test lab set up with 3 Windows 2003 (Standard Edition) servers. One is a domain controller/DNS server, one is a Mailbox/Hub Transport/Clien Access Server, and one server is an Edge Transport Server.
I am currently trying to simulate a server meltdown.
I made a backup of the mailbox databases on the Mailbox server, and then pulled the power cord.
I then follow the steps in this tutorial to a tee.
(Please scroll down to the heading: Recovering an Exchange 2007 Server Using the RecoverServer Switch)
http://www.msexchange.org/tutorials/Configuring-Exchange-Server-2007-Preview-Chapter9-Disaster-Recovery-Exchange-Server-2007.html
Anyway, I run the command: setup.com /M:RecoverServer / DoNotStartTransport
After everything is done, I get an error message from the command prompt:
"The default certificate for the local server was corrupted or missing the Active Directory. The problem has been fixed. If you have existing subscriptions, you must subscribe all the Edge Transport servers again by using New-EdgeSubscription.
The Exchange Server setup operation did not complete. Visit http://support.microsoft.com and enter the Error ID to find out more information.
Exchange Server setup encountered an error.
Checking the Event Viewer, there is an error under Application.
Source: MSExchangeSetup
Category: Microsoft Exchange Setup
Type: Error
Event ID: 1002
Exchange Server component Hub Transport Role failed.
Error: Error:
The default certificate for the local server was corrupted or missing the Active Directory. The problem has been fixed. If you have existing subscriptions, you must subscribe all the Edge Transport servers again by using New-EdgeSubscription.
Is this because I currently have the Edge Transport server running and there was a subscription to the Edge Transport from the mail server which I powered off?
Continuing on...
I run NTBackup.exe, click on the Restore And Manage Media tab, go to the tools menu and click "Catalog A Backup File". I navigate to the shared folder on the server where I store my backups. I notice the subfolders on my .bkf file show question marks (is this a problem?)
I check the box that says "Mailbox Databases" and click the "Start Restore" button.
In the restore to: box, I keep the default, I create a folder for logs and patch files called C:\Exchange Logs and hit OK.
Then I get the error message that is really troublesome:
"The specified computer is not a Microsoft Exchange server or its Microsoft Exchange services are not started."
Then I open up the Exchange Management Console.
When I click on Server Configuration->Mailbox, I get a whole slew of errors.
--------------------------
Microsoft Exchange Warning
--------------------------
The following warning(s) were reported while loading topology information:
Get-OWAVirtualDirectory
Completed
Warning:
Outlook Web Access has detected an inconsistency in the Active Directory configuration for the following virtual directory(ies). This can happen if OWA virtual directories were deleted in Internet Services Manager. Please verify that you have access to the metabase on the servers listed below. In order to fix this inconsistency, run the following command, which will remove references to these virtual directories from the Active Directory:
Remove-OwaVirtualDirectory
Warning:
Outlook Web Access has detected an inconsistency in the Active Directory configuration for the following virtual directory(ies). This can happen if OWA virtual directories were deleted in Internet Services Manager. Please verify that you have access to the metabase on the servers listed below. In order to fix this inconsistency, run the following command, which will remove references to these virtual directories from the Active Directory:
Remove-OwaVirtualDirectory
Warning:
Outlook Web Access has detected an inconsistency in the Active Directory configuration for the following virtual directory(ies). This can happen if OWA virtual directories were deleted in Internet Services Manager. Please verify that you have access to the metabase on the servers listed below. In order to fix this inconsistency, run the following command, which will remove references to these virtual directories from the Active Directory:
Remove-OwaVirtualDirectory
Warning:
Outlook Web Access has detected an inconsistency in the Active Directory configuration for the following virtual directory(ies). This can happen if OWA virtual directories were deleted in Internet Services Manager. Please verify that you have access to the metabase on the servers listed below. In order to fix this inconsistency, run the following command, which will remove references to these virtual directories from the Active Directory:
Remove-OwaVirtualDirectory
Warning:
Outlook Web Access has detected an inconsistency in the Active Directory configuration for the following virtual directory(ies). This can happen if OWA virtual directories were deleted in Internet Services Manager. Please verify that you have access to the metabase on the servers listed below. In order to fix this inconsistency, run the following command, which will remove references to these virtual directories from the Active Directory:
Remove-OwaVirtualDirectory
Get-ActiveSyncVirtualDirec
Completed
Warning:
IIS://TESTMAIL8.ikstest8.c
Warning:
Object TESTMAIL8\Microsoft-Server
Warning:
Exchange has detected an inconsistency in the Active Directory configuration for the following virtual directory(ies). This can happen if Mobile Sync virtual directories were deleted in Internet Services Manager. Please verify that you have access to the metabase on the servers listed below. In order to fix this inconsistency, run the following command, which will remove references to these virtual directories from the Active Directory:
Remove-ActiveSyncVirtualDi
Get-OabVirtualDirectory
Completed
Warning:
OAB Virtual Directory "OAB (Default Web Site)" exists in active directory, but not the IIS metabase. Please recreate the OAB Virtual Directory.
get-MailboxDatabase
Completed
Warning:
Failed to connect to information store service on the server "TESTMAIL8.ikstest8.com". The exception message is "MapiExceptionNetworkError
Diagnostic context:
......
Lid: 10648 dwParam: 0x6D9 Msg: EEInfo: Generating component: 2
Lid: 14744 dwParam: 0x6D9 Msg: EEInfo: Status: 1753
Lid: 9624 dwParam: 0x6D9 Msg: EEInfo: Detection location: 501
Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters: 4
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string: TESTMAIL8.ikstest8.com
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -1988875570
Lid: 15000 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Pointer val: 0x0x317755a0 (UnknownPtag)
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115".
--------------------------
OK
--------------------------
I'm assuming that somehow this new server with the same name didn't link back up the Active Directory server properly. Maybe the /DoNotStartTransport flag screwed something up? By the way, how do I START the transport again? Not that it really makes a difference, because when I right click on Hub Transport and do properties, I get that string of incoherent error message again. Ugh.
Can anyone help me with this?
What started as a simple project that should be relatively straightfoward to complete, has really turned into a nightmare for me.
Thanks,
Jamie
I am currently testing out a backup strategy for our Exchange 2007 mail server. I have a test lab set up with 3 Windows 2003 (Standard Edition) servers. One is a domain controller/DNS server, one is a Mailbox/Hub Transport/Clien Access Server, and one server is an Edge Transport Server.
I am currently trying to simulate a server meltdown.
I made a backup of the mailbox databases on the Mailbox server, and then pulled the power cord.
I then follow the steps in this tutorial to a tee.
(Please scroll down to the heading: Recovering an Exchange 2007 Server Using the RecoverServer Switch)
http://www.msexchange.org/tutorials/Configuring-Exchange-Server-2007-Preview-Chapter9-Disaster-Recovery-Exchange-Server-2007.html
Anyway, I run the command: setup.com /M:RecoverServer / DoNotStartTransport
After everything is done, I get an error message from the command prompt:
"The default certificate for the local server was corrupted or missing the Active Directory. The problem has been fixed. If you have existing subscriptions, you must subscribe all the Edge Transport servers again by using New-EdgeSubscription.
The Exchange Server setup operation did not complete. Visit http://support.microsoft.com and enter the Error ID to find out more information.
Exchange Server setup encountered an error.
Checking the Event Viewer, there is an error under Application.
Source: MSExchangeSetup
Category: Microsoft Exchange Setup
Type: Error
Event ID: 1002
Exchange Server component Hub Transport Role failed.
Error: Error:
The default certificate for the local server was corrupted or missing the Active Directory. The problem has been fixed. If you have existing subscriptions, you must subscribe all the Edge Transport servers again by using New-EdgeSubscription.
Is this because I currently have the Edge Transport server running and there was a subscription to the Edge Transport from the mail server which I powered off?
Continuing on...
I run NTBackup.exe, click on the Restore And Manage Media tab, go to the tools menu and click "Catalog A Backup File". I navigate to the shared folder on the server where I store my backups. I notice the subfolders on my .bkf file show question marks (is this a problem?)
I check the box that says "Mailbox Databases" and click the "Start Restore" button.
In the restore to: box, I keep the default, I create a folder for logs and patch files called C:\Exchange Logs and hit OK.
Then I get the error message that is really troublesome:
"The specified computer is not a Microsoft Exchange server or its Microsoft Exchange services are not started."
Then I open up the Exchange Management Console.
When I click on Server Configuration->Mailbox, I get a whole slew of errors.
--------------------------
Microsoft Exchange Warning
--------------------------
The following warning(s) were reported while loading topology information:
Get-OWAVirtualDirectory
Completed
Warning:
Outlook Web Access has detected an inconsistency in the Active Directory configuration for the following virtual directory(ies). This can happen if OWA virtual directories were deleted in Internet Services Manager. Please verify that you have access to the metabase on the servers listed below. In order to fix this inconsistency, run the following command, which will remove references to these virtual directories from the Active Directory:
Remove-OwaVirtualDirectory
Warning:
Outlook Web Access has detected an inconsistency in the Active Directory configuration for the following virtual directory(ies). This can happen if OWA virtual directories were deleted in Internet Services Manager. Please verify that you have access to the metabase on the servers listed below. In order to fix this inconsistency, run the following command, which will remove references to these virtual directories from the Active Directory:
Remove-OwaVirtualDirectory
Warning:
Outlook Web Access has detected an inconsistency in the Active Directory configuration for the following virtual directory(ies). This can happen if OWA virtual directories were deleted in Internet Services Manager. Please verify that you have access to the metabase on the servers listed below. In order to fix this inconsistency, run the following command, which will remove references to these virtual directories from the Active Directory:
Remove-OwaVirtualDirectory
Warning:
Outlook Web Access has detected an inconsistency in the Active Directory configuration for the following virtual directory(ies). This can happen if OWA virtual directories were deleted in Internet Services Manager. Please verify that you have access to the metabase on the servers listed below. In order to fix this inconsistency, run the following command, which will remove references to these virtual directories from the Active Directory:
Remove-OwaVirtualDirectory
Warning:
Outlook Web Access has detected an inconsistency in the Active Directory configuration for the following virtual directory(ies). This can happen if OWA virtual directories were deleted in Internet Services Manager. Please verify that you have access to the metabase on the servers listed below. In order to fix this inconsistency, run the following command, which will remove references to these virtual directories from the Active Directory:
Remove-OwaVirtualDirectory
Get-ActiveSyncVirtualDirec
Completed
Warning:
IIS://TESTMAIL8.ikstest8.c
Warning:
Object TESTMAIL8\Microsoft-Server
Warning:
Exchange has detected an inconsistency in the Active Directory configuration for the following virtual directory(ies). This can happen if Mobile Sync virtual directories were deleted in Internet Services Manager. Please verify that you have access to the metabase on the servers listed below. In order to fix this inconsistency, run the following command, which will remove references to these virtual directories from the Active Directory:
Remove-ActiveSyncVirtualDi
Get-OabVirtualDirectory
Completed
Warning:
OAB Virtual Directory "OAB (Default Web Site)" exists in active directory, but not the IIS metabase. Please recreate the OAB Virtual Directory.
get-MailboxDatabase
Completed
Warning:
Failed to connect to information store service on the server "TESTMAIL8.ikstest8.com". The exception message is "MapiExceptionNetworkError
Diagnostic context:
......
Lid: 10648 dwParam: 0x6D9 Msg: EEInfo: Generating component: 2
Lid: 14744 dwParam: 0x6D9 Msg: EEInfo: Status: 1753
Lid: 9624 dwParam: 0x6D9 Msg: EEInfo: Detection location: 501
Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters: 4
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string: TESTMAIL8.ikstest8.com
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -1988875570
Lid: 15000 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Pointer val: 0x0x317755a0 (UnknownPtag)
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115".
--------------------------
OK
--------------------------
I'm assuming that somehow this new server with the same name didn't link back up the Active Directory server properly. Maybe the /DoNotStartTransport flag screwed something up? By the way, how do I START the transport again? Not that it really makes a difference, because when I right click on Hub Transport and do properties, I get that string of incoherent error message again. Ugh.
Can anyone help me with this?
What started as a simple project that should be relatively straightfoward to complete, has really turned into a nightmare for me.
Thanks,
Jamie
ASKER
Yes before I installed it, I installed IIS and joined it to the active directory domain. It definitely has the same name.
--Install windows support tool
--open the Adsiedit.msc
--Expand the configuration
--Expand Services
--Expand Microsoft Exchange
--Expand the organization name
--Expand Administrative group
--Make sure are you able to First Administrative Group"?
--If so try to expand it and then expand servers and see whether it is listing the problematic server name.
--If so take the system state backup and delete that server name.
--Then re-run the exchange setup
Reff:
http://forums.msexchange.org/m_1800487387/printable.htm
--open the Adsiedit.msc
--Expand the configuration
--Expand Services
--Expand Microsoft Exchange
--Expand the organization name
--Expand Administrative group
--Make sure are you able to First Administrative Group"?
--If so try to expand it and then expand servers and see whether it is listing the problematic server name.
--If so take the system state backup and delete that server name.
--Then re-run the exchange setup
Reff:
http://forums.msexchange.org/m_1800487387/printable.htm
ASKER
SatyaPathak:
Thank you for responding. I actually did some more poking around today.
Simplified my setup. Just have 1 DC and 1 Exchange 2007 (installed with "typical setup")
Tested it out ... mail flowed.
Took a backup of the mailbox database with NTBackup.exe .... I then tested restoring the mailbox onto the same server.
When I try to mount the database I get this error:
FAILED TO MOUNT DATABASE 'MAILBOX DATABASE'
Error:
Exchange is unable to mount the database that you specified. Specified database fea0011c-25b0-47df-88b1-15
I installed the ADSIEDIT.MSC utility, but I am just way too new to Active Directory to understand what anything means. Is there something set up wrong in Active Directory that is causing these 2 problems?
Thank you for responding. I actually did some more poking around today.
Simplified my setup. Just have 1 DC and 1 Exchange 2007 (installed with "typical setup")
Tested it out ... mail flowed.
Took a backup of the mailbox database with NTBackup.exe .... I then tested restoring the mailbox onto the same server.
When I try to mount the database I get this error:
FAILED TO MOUNT DATABASE 'MAILBOX DATABASE'
Error:
Exchange is unable to mount the database that you specified. Specified database fea0011c-25b0-47df-88b1-15
I installed the ADSIEDIT.MSC utility, but I am just way too new to Active Directory to understand what anything means. Is there something set up wrong in Active Directory that is causing these 2 problems?
ASKER
Ok, ignore that last comment.
The database was corrupted somehow. I used the Database Recovery Toolkit and it fixed the problem and it restored.
Now back to the real issue of getting setup.com /M:RecoverServer working properly.
I have a server set up and running right now, I'll let you know if I get similar results, and I'll also run the adsiedit utility and see if I can come up with anything.
Thanks,
Jamie
The database was corrupted somehow. I used the Database Recovery Toolkit and it fixed the problem and it restored.
Now back to the real issue of getting setup.com /M:RecoverServer working properly.
I have a server set up and running right now, I'll let you know if I get similar results, and I'll also run the adsiedit utility and see if I can come up with anything.
Thanks,
Jamie
ASKER
I just set up a new environment without an Edge Transport server.
Used the setup.com /M:RecoverServer and it worked just fine.
Also restoring the mailbox databases worked.
So I don't know what to say. I guess having the Edge Transport server running during this process screwed it up? Would that make sense?
Used the setup.com /M:RecoverServer and it worked just fine.
Also restoring the mailbox databases worked.
So I don't know what to say. I guess having the Edge Transport server running during this process screwed it up? Would that make sense?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Did you ensure the servername was the same name as the one that "failed"?