Gig Posted May 26, 2007 Share Posted May 26, 2007 (edited) Hello everybody.I have a big, big trouble.Old NT4 Server with Exchange Server 5.5 - Near to dismission, but we need it for a couple of months...Yesterday it decided to do not download email anymore (it download email from a pop3 "catchall" address and then deilvers it to the right recipient).No error in error log.Looking to the services, I find "Microsoft Exchange Connector for POP3 Mailboxes" not active. I try to enable it. Doesn't run. Try again. Nothing to do. Error window:Could not start the Microsoft Exchange Connector for POP3 Mailboxes on\\servernameError 1067: The process terminated unexpectedlyIn the log there is absolutely anithing strange! I went to Exchange Administrator and set logging POP3 Connector to maximum...But everything that appears in my application log when I try to start the service is:* ID 1000- Pop3 ConnectorThe service is starting Microsoft Exchange Connector for POP3 Mailboxes 4.50.2113-----------* ID 1001- Pop3 ConnectorThe service started successfully-----------* ID 4008- Pop3 ConnectorThe delivery service is flushing its outgoing and incoming queues------------* ID 4009- Pop3 ConnectorFlushing Transaction Complete.--------------Adsolutely no indication of any error.I can't understand... it worked perfectly until yesterday!I tryed di clean a not o messages on the server and reboot, but nothing.I can't find anything about it on internet, I suppose that 1067 is a generic error.Today I applyed the SP4 patch, but it did not revolved the problem.Please help me, I am a dead man!!! Edited May 26, 2007 by Gig Link to comment Share on other sites More sharing options...
andrewpayne Posted May 26, 2007 Share Posted May 26, 2007 POP3 connector was only released for Small Business Server 4.5. Which OS are you using? Also why did you not reboot the server (as most admins do in a emergency) Link to comment Share on other sites More sharing options...
Gig Posted May 26, 2007 Author Share Posted May 26, 2007 (edited) I tried di clean a lot of messages on the server and reboot, but nothing.Yes, it is SBS 4.5System Properties reportMicrosoft Windows NT 4.00.1381 Edited May 26, 2007 by Gig Link to comment Share on other sites More sharing options...
The Glimmerman Posted May 26, 2007 Share Posted May 26, 2007 How many space available on HD?I found this on the net?Maybe it will help.SYMPTOMSWhen you attempt to start the directory service in Microsoft ExchangeServer 5.5 after restoring it from backup, the directory may not start andyou may receive the following error message:Error 1067. The process terminated unexpectedly.The following events may appear in the Event Viewer:Event ID: 124Source: ESE97Description: MSExchangeDS ((1432 ) ) Unable to read the log header.Error -530.Event ID: 1196Source: MSExchangeDSDescription: Couldn't recover the restored Microsoft Exchange Serverdatabase (EDB). Cannot continue. Error c8000212.CAUSEThis behavior can occur on a recovery server or on a server you use fortesting purposes because the Edb.log file that is created during a restoreoperation from backup interferes with the recovery process when therestore operation is finished.RESOLUTIONTo resolve this behavior, manually remove the existing data in the Dsadatafolder before starting the restore operation from backup.NOTE: If you delete the Edb.log file to restart the directory service, runeseutil with the /g /v /x /ds options to ensure that this deletion doesnot introduce errors into the directory Link to comment Share on other sites More sharing options...
The Glimmerman Posted May 26, 2007 Share Posted May 26, 2007 or thisIf NT4/SP6a server running Exchange 5.5/SP4 developed an illness during the night - and now cannot start the Internet Mail Services service, resulting in the following Dr Watson application error: "MSEXCIMC.exe Exception: access violation (0xc0000005), Address: 0x00417531" Soon after, you get a services error with a "Error 1067: The process terminated unexpectedly." Event Viewer provides the following further information: "Event ID: 4037" "An exception has occurred which was handled internally by the Internet Mail Service. This may have resulted in a message not being delivered. Code: 0xc0000005 Flags: 0x00000000 Address: 0x00417531" The fix Just go to c:\exchsrvr\imcdata\out (This is the default path), and see if u have any messages there, then try to cut and paste somewhere. Then try starting the IMC Service. If u had splited the folders of exchange server thru Exchange Optimizer, then see at the same path but on different drive i.e. d:\exchsrvr\imcdata\out and a side note To avoid future incidence bring your file version to Msexcimc.exe 5.5.2655.15 Imcmsg.dll 5.5.2655.15 This is service pack 5 for Exchange 5.5, to fix a few problems with IMC. Smooth sailing.. Link to comment Share on other sites More sharing options...
Gig Posted May 26, 2007 Author Share Posted May 26, 2007 (edited) There were about 2GB of space (so I tried to clean up some emails).During my attempts to repair this situation, i Ghosted the disk to another, bigger one. But nothing to do.I can't understand the fact that no error event is logged...Well, let's see the article you found.. but it seems strange to me... it was not a test server ad it is not the IMS service, but the POP3 Service that does not work... What?Exchange 5.5 Service pack 5? Does it Exist? It is named in your post, But I can't find it on microsoft.com! Strange... Edited May 26, 2007 by Gig Link to comment Share on other sites More sharing options...
Gig Posted May 26, 2007 Author Share Posted May 26, 2007 Do you think I could restore a backup disk (entire ghost) and then overvrite the email container file with the latest one?How? Link to comment Share on other sites More sharing options...
Gig Posted May 26, 2007 Author Share Posted May 26, 2007 Maybe here we are..After attempting anything, I went to c:\program files\pop3 connector\incomingand there I found about 10 .mmd files, that seemed email downloaded but not delivered.I moved them out there, and the I successfully started the service!It downloaded ad delivered the emails of the last two days. But now there is a strange problem: usually when someone send an email to an @mydomain address that does not exist, it arrives to me as an "Notification Inbound email failure". But it does not do it anymore. What may it depend from? Does it depend from Service Pack 4? Does it depend from some "hidden" option? Link to comment Share on other sites More sharing options...
cluberti Posted May 26, 2007 Share Posted May 26, 2007 Moving to more appropriate forum. Link to comment Share on other sites More sharing options...
Gig Posted June 4, 2007 Author Share Posted June 4, 2007 Hi guys.Exchange works now... but sorry, do you know how to re-enable the "Notification: inbound email failure" emails to be delivered to the administrator's mailbox? Link to comment Share on other sites More sharing options...
Gig Posted July 6, 2007 Author Share Posted July 6, 2007 Hi guys.Exchange works now... but sorry, do you know how to re-enable the "Notification: inbound email failure" emails to be delivered to the administrator's mailbox?Does someone have any idea? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now