Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Sun, 28 Oct 2007 23:06:36 -0400,    group: microsoft.public.exchange2000.information.store        back       


Transaction Log Replay   
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
date: Sun, 28 Oct 2007 23:06:36 -0400   author:   Matt

Re: Transaction Log Replay   
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"  wrote in message 
news:07cVi.249$vI3.245@newsfe12.lga...
> 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
>
>
>
date: Fri, 2 Nov 2007 00:24:58 -0400   author:   seth

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us