Problems Restoring Exchange Database to a Recovery Server

[Tony Dennis]

I have been trying to recover a mailbox from a backup tape
for the last few days using KB Article 813337 and the
associated white pager, e2kbrecovery.doc. Have followed
the instructions and get the following error form Backup
when I try to restore:

"Unable to create log path. Check to make sure that it is
a valid path."

Clicking OK brings on the next dialog box:

"The specified computer is not a Microsoft Exchange server
or its Microsoft Exchange Services are not started.

Both the original machine and the recovery server are
patched to Win2K SP3 plus all security patches. Both
versions of Exhange are patched to SP3. I have gone
through the drill of making sure that trust is established
between the two forests and have given the Administrator
in the domain that the tape is being restored from full
permission on the target Exchange Server inside the target
Exchange Server Administrator. I have tried multiple
paths in to temporarily store the log file including hard
paths, relative paths, and UNC's. I have verified that
the user running the restore (Administrator) has Full
permissions on the paths that I've attempted.

I have pulled down the restore forest (twice) to make sure
there wasn't an error there. I have de-installed and re-
installed Exchange server a number of time. I have
searched for an update to the backup provided with Win2K
without success (I would assume this is covered in the
SP's).

Am hoping this is something stupid-simple that I have
overlooked. Any help appreciated.

Tony

[S.R.]

make sure that LegacyExchangeDN attribute on recovery server is identical to
production server,
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B273863

also remeber to have identical store names on both production and recovery
servers

"Tony Dennis" <to...@energytrust.org> wrote in message
news:00b201c2e4da$c3aa5a40$a401...@phx.gbl...

[Tony Dennis]

Yes, I'd thought of that. Here are the lines from
respective servers.

dn: CN=SMTP (HAGRID-{72C969E9-F66B-4BF7-A8F8-
3A79E1F41DB3}),CN=Connections,CN=Energy Trust of
Oregon,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=etoo,DC=org
changetype: add
legacyExchangeDN:
/o=Energy Trust of Oregon/ou=First Administrative
Group/cn=Configuration/cn=Co
nnections/cn=SMTP (HAGRID)/cn={72C969E9-F66B-4BF7-A8F8-
3A79E1F41DB3}

dn: CN=SMTP (ETO-GOLD-DATA-D-{D82896C3-2A14-448A-84EC-
29090E44417C}),CN=Connections,CN=The Energy Trust of
Oregon,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=forest,DC=org
changetype: add
legacyExchangeDN:
/o=The Energy Trust of Oregon/ou=First Administrative
Group/cn=Configuration/c
n=Connections/cn=SMTP (ETO-GOLD-DATA-D)/cn={D82896C3-2A14-
448A-84EC-29090E4441
7C}

As I understand it from the white paper, the /o and /ou
pieces have to match. They do. The database names match
as well. The databases are offline, as per the
instructions and have the "Allow overwrites" checkbox
checked under the Databases tab.

Tony

>.
>

[S.R.]

drop the "The" from /o= or add it if it is recovery server which is missing
it.

"Tony Dennis" <to...@energytrust.org> wrote in message

news:01ab01c2e760$83740290$a601...@phx.gbl...

[Tony Dennis]

Ok, did that, admitadly that was a stupid mistake on my
part. Am now getting the following errors in the
Application Log on the target machine when I try to
restore:

The MAPI call 'OpenMsgStore' failed with the following
error:
The attempt to log on to the Microsoft Exchange Server
computer has failed.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0512-00000000

For more information, click
http://www.microsoft.com/contentredirect.asp.

(The EventID is 9075, which the asp above can't place.)

And...

Unexpected error <<0xc1050000 - The attempt to log on to
the Microsoft Exchange Server computer has failed. The
MAPI provider failed. Microsoft Exchange Server
Information Store ID no: 8004011d-0512-00000000>>
occurred.

For more information, click
http://www.microsoft.com/contentredirect.asp.

(The EventID is 1005, which also can't be placed.)

Tried deleting the databases out of the MDBDATA directory
and having the server create new ones. Also tried to
restore with both the stores mounted and dismouted. I am
able to access shares from machine to machine, so I don't
believe it's a trust issue.

Thanks for the last. Any additional help appreciated.

Tony

>.
>

[S.R.]

Try the following link suggestion, do not get distracted by the title of the
article
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B274534

"Tony Dennis" <to...@energytrust.org> wrote in message

news:029001c2e82b$d768c2c0$a401...@phx.gbl...

[bonma...@gmail.com]

A centralized Exchange access and management facility is provided by the Lepide Exchange Manager that helps in repairing corrupted, damaged, inaccessible Exchange database and also helps in restoring Mailbox using available backup. The utility performs various operations such as effective Exchange recovery, restoration using available backup and easy eDiscovery.
For more information - http://www.exchangedatabaserecovery.co.uk