Re: Problem in recovering mailbox

  • From: "Anthony Paillard" <anthony.paillard@xxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Sat, 7 Jan 2006 20:16:05 +0100

Hi,

How are doing your restore operation.
When do you had this error ?
During ntbackup restore or when you're extract mailbox from recovery storage ?


Anthony Paillard



----- Original Message ----- From: "Balkar Singh Kang" <netsmartz_balkars@xxxxxxxxxxx>
To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
Sent: Saturday, January 07, 2006 2:34 PM
Subject: [exchangelist] Problem in recovering mailbox



http://www.MSExchange.org/

Dear Sir,

I need your kind help to recover mailbox from backup. After restore(ntbackup), When I recover mailbox from Recovery Storage Group then I got following error message.

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

I tryed to find solution on microsoft site but still it is not working. I visited the following link for the solution.

http://support.microsoft.com/kb/264413/en-us


What else I can do to recover mailboxes of users.

I am using Exchange 2003+SP1

I need your kind co-operation.

Waiting for your reply

Balkar Singh

_________________________________________________________________
How good are you in a Formula One car? Play now http://server1.msn.co.in/sp05/tataracing/onlinegame.asp



------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp ------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as: anthony.paillard@xxxxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to info@xxxxxxxxxxxxxx








Other related posts: