I just went through this issue. Microsoft believes it was the virus scanning software (CA) and the non-aware backups attempting to backup the database, even though the backups were not running at the time the services stopped. We configured the virus software (non-exchange aware) not to scan the exchsrvr directories. After resolving the issue, Microsoft recommended rebuilding the server due to this issue and other issues in the past. I'm not telling you to rebuild it but prevent your non-exchange aware virus software from scanning your exchange directories. Once we did that the services didn't fail, but we did rebuild it anyway due to other issues.
todd >>> [EMAIL PROTECTED] 12/27/01 09:45AM >>> OK, so you verified you had plenty of space on each partition/drive letter? I would keep a gig or more free, just in case. What are you using for AV? -----Original Message----- From: Cris Vitsorek [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 27, 2001 9:43 AM To: MS-Exchange Admin Issues Subject: RE: Event ID 125 and Event ID 193 the problem was the store stopped and I don't know why. There are no other errors. It restarted but I can't resolve the issue as to why it stopped - it seems like a phantom error. One q article related it to the virus checking software api going into a "null state" because it was trying to do an update when an on access scan was occuring. but that wasn't happening. Basically, I'm wondering if anyone else has had this happen and some possible causes. Cris -----Original Message----- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 26, 2001 8:34 PM To: MS-Exchange Admin Issues Subject: RE: Event ID 125 and Event ID 193 So what was the problem. You ask for help, you have to tell us what the solution was. -----Original Message----- From: Cris Vitsorek [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 26, 2001 2:06 PM To: MS-Exchange Admin Issues Subject: Event ID 125 and Event ID 193 I received an Event ID 125 source ESE97. The error was MsExchange(188) unable to create the log. The drive maybe readonly, out of disk space, misconfigured, or corrupt Error -1032 This was concurrent with Event ID 193 - Database failed with error -510 hwile trying to log the commit of a transaction. The IMC failed next and then the Sa reported unexpected network problems. There is no way that the drive was read only or out of disk space. Started and stopped the informaiton store and it logged a recovery and played back logs. Any insight on where to go next with this? THank for any help Exchange 5.5, sp4, List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
