not surprised it took that long with that many logs
as far as that error goes, that is to be expected.
the IS and SA is running, but with the stores dismounted because of the
restore, the SA mailbox cannot be accessed thus generating that error
"Matt" <gawerbissu@[EMAIL PROTECTED]
> wrote in message
news:07cVi.249$vI3.245@[EMAIL PROTECTED]
> Hello,
>
> I am doing a test restore drill. After restoring my databases and
> transaction log files, I ran eseutil /cc to commit the log files. The
> process completed successfully, but it took 4.5 hours to complete! Is
this
> normal? I suppose the answer depends on the size of the database and the
> hardware of the server. The database is 15GB with 2GB of log files. The
> server is a 1.6ghz P4 with 1 GB of RAM. However, during the commit
> process,
> the cpu and memory were mostly idle. I did observe the cpu usage of
> store.exe fluctuate a bit, but not much.
>
> The only clue I found was an repeating error in the Application Log. The
> event ID is 9175 and the error is:
>
> The MAPI call 'OpenMsgStore' failed with the following error: The
attempt
> to
> log onto the Microsoft Exchange Server computer has failed. The MAPI
> provider failed. Microsoft Exchange Server Information Store ID no:
> 8004011d......
>
> Any ideas?
>
> Thanks,
> Matt
>
>
>
|
