cpgreen
asked on
SMTP Local Delivery Queue - Mail never delivered
Helllo,
We have a MS Exchange 2000 SP2 Server and some mail sits in the SMTP Local Queue and never actually gets sent.
I enabled Maximum Logging and started receiving Event ID 327 reports which gives the following Error:-
The following call : EcLocallyDeliverMsg to the store failed. Error code : -1017. MDB : 8f3bc704-4f7a-4751-a059-d4 fe1e05b10b . FID : 1-33. MID : 1-4185CA. File : .
For more information, click http://www.microsoft.com/contentredirect.asp.
MS KB Article 328671 (Error Code -1017) is the closest match I have found so far and refers to possible Information Store corruption.
The MS KB Article suggestes running eseutil /d to defrag the database and then isinteg.exe to fix and repair the IS. I am a bit reluntant to run a repair as I have heard stories about the repair procedure causing more problems.
Has anyone had any experience of the error above and / or eseutil.exe and isinteg.exe
Thank you
Carl
We have a MS Exchange 2000 SP2 Server and some mail sits in the SMTP Local Queue and never actually gets sent.
I enabled Maximum Logging and started receiving Event ID 327 reports which gives the following Error:-
The following call : EcLocallyDeliverMsg to the store failed. Error code : -1017. MDB : 8f3bc704-4f7a-4751-a059-d4
For more information, click http://www.microsoft.com/contentredirect.asp.
MS KB Article 328671 (Error Code -1017) is the closest match I have found so far and refers to possible Information Store corruption.
The MS KB Article suggestes running eseutil /d to defrag the database and then isinteg.exe to fix and repair the IS. I am a bit reluntant to run a repair as I have heard stories about the repair procedure causing more problems.
Has anyone had any experience of the error above and / or eseutil.exe and isinteg.exe
Thank you
Carl
Yep, you have a corrupt database. You will need to follow the instructions to try to repair the database. Do you have AV software installed on this server?
ASKER
We have AV software installed on the Exchange Server and have read articles from the MS Website saying that you should not scan the
\ExchSrvr directory and subdirectories + the M:\ Drive. The AV software had previously been scanning the directories but has since been turned off. However its possible the corruption occurred before then.
\ExchSrvr directory and subdirectories + the M:\ Drive. The AV software had previously been scanning the directories but has since been turned off. However its possible the corruption occurred before then.
Yes, if you have ever scanned the M drive, I would say it is the source of the corruption.
ASKER
To repair the database should I just follow MS KB Article 328671 ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.