Exchange Hangs with errors
Every 2 wks are exchange 2003 server hangs. The logs are reporting:
1) Notificatons for the volume f:\ are not active, Context: Windows Application, Details: The device is not ready.
2) Information Store (4544) First Storage Group: An attempt to read from the file "F:\Program Files\Exchsrvr\mdbdata\priv1.edb" at offset 2058256384 (0x000000007aae8000) for 4096 (0x00001000) bytes failed after 0 seconds with system error 21 (0x00000015): "The device is not ready. ". The read operation will fail with error -1022 (0xfffffc02). If this error persists then the file may be damaged and may need to be restored from a previous backup.
3) Error Disk IO error occurred on message 1-1C0728A during a background cleanup on database "First Storage Group\Mailbox Store"4) Database error Disk IO error occurred in function JTAB_BASE::EcRetrieveColumnByPtagId while accessing the database "First Storage Group\Mailbox Store
ALSO, HOW DO I CHECK THE MAINTENANCE SCHEDULE FOR EXCHANGE?
May 14th, 2009 5:14pm
Hi,Please start with the following things:- update the drivers and firmware of your storage environment- run the Exbpa tool to check your system and apply the tips you will get from the tool- ensure that the correct directories are excluded for virusscanningTo change the maintenance schedule perform the following steps:- Open Exchange System Manager- Expand Servers, and then expand the server that you want to work with. - Expand the storage group that you want to work with.- Right-click the store that you want to work with, and then click Properties.-- On the Database tab, click Maintenance interval and click a new interval, or click Customize to create a custom schedule. Regards,Johanblog: www.johanveldhuis.nl
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2009 12:04am
Hello,Please update as suggested by Johan and addition to The failure was due to the issue that exchange was unable to read from the file. This was a result of the failure of communication with the disk, which can be either due to a hardware issue or a network issue. Hence it would be better to check with your hardware vendor if there are any logging on the hardware side to see what is happening. You have Symantec? If yes... get back to symantec for update :)Ref:Exchange Server 2003 and Exchange 2000 Server information store maintenance and online defragmentationhttp://support.microsoft.com/kb/324358JeremyK's [MSFT] WebLoghttp://blogs.msdn.com/jeremyk/archive/2004/06/12/154283.aspxArun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3
May 15th, 2009 1:42am