|
|
re:Last update 5/10/200...
Last update 5/10/2005): <br>
Check to see if E00.log is missing or is no longer in the Exchsrvr\Mdbdata folder or in the log file folder. According to Microsoft’s Q895856 article: "This condition may occur if a file-based virus scanner moves the E00.log file to the Quarantine folder. File-level antivirus scanners sometimes locate data that matches a known virus signature in an Exchange log file. Therefore, the virus scanner may determine that the log file contains a virus and then move the log file to the Quarantine folder". KB article Q313184 offers detailed steps to test and repair this situation.<br>
<br>
Ionut Marin (Last update 1/30/2005): <br>
As per Microsoft: "This issue may occur if the System Attendant and the Information Store services are not using the local system account". See Q327352, Q274534, Q288700, Q290215, Q296933, Q313184, Q315250, Q321102, Q329685, Q823022, and Q888179 to fix this problem.<br>
<br>
See the link to "Microsoft event 9175 from source MSExchangeSA" for more details.<br>
<br>
Fred Orcutt (Last update 7/19/2004): <br>
Error received along with EventID 9518 from source MSExchangeIS. Attempting to mount mail stores may terminate with message, that store cannot be mounted due to corruption. Before attempting any repair/restoration, I checked the store properties/permissions. Everyone account was granted no permissions. Granting the Everyone account standard user permissions and applying, then attempting to remount the stores, resulted in a successful mount without any further action required. I am not personally sure at this time whether changing Everyone account permissions for the stores is strictly by-the-book, but it did the trick in this case.<br>
<br>
Christian Jones (Last update 7/12/2004): <br>
I got this error when the information store service went to a stopped state. I could simply reboot the server or start the service and it would run for a couple of hours. The error was due to me running a beta version of Exchange 2003 that expired.<br>
<br>
Tim Long (Last update 4/15/2004): <br>
I saw this event when I removed “Everyone” from the permissions on the root of my hard drive. The Exchange Store was located on the drive and apparently the installation did not set explicit permissions on the exchange folders. Reinstating “Everyone: Full control” on the root of the drive cured the problem, though obviously this is a security vulnerability.<br>
<br>
Adrian Florin Moisei (Last update 5/9/2003): <br>
The error can occur if you try to mount the Mailbox Store or the Public Folder Store. This issue may occur if the Microsoft Windows 2000 Group Policy Object has been deleted or modified. See Q316709 link below.<br>
<br>
Aaron Guilmette <br>
This event can also happen if you use the "Reinstall" option for Exchange 2000 Server on a server that's running a service pack (any service pack). Since the mail stores are updated with service packs, previous versions of Exchange don't understand and can't mount them. If you have reinstalled Exchange on top of itself, don't forget to apply the same SP level that the server had before you reinstalled it.<br>
<br>
Roland Hausin <br>
This event also may occur if the disk holding the log files runs out of disk space.<br>
<br>
Adrian Grigorof <br>
As per Microsoft: "This issue can occur if the information store is not running. When the information store is stopped and the System Attendant is still running, the System Attendant keeps the MAPI session active. This issue can also occur if a mailbox store failed to mount. ". See Q262456 link below for more details.<br>
<br>
Art Sennholtz <br>
I was getting this on a Cluster Server. Make sure the name of the virtual server is NOT in AD's Users And computers. See Q288598. |
|
狗仔卡
发表于 2005-5-19 09:32:25
收藏
分享
淘帖
支持
反对
提升卡
置顶卡
沉默卡
喧嚣卡
变色卡
显身卡
楼主