Client has Exch2000 (ExchInfo version 1.5.3.2 SERVER (FULL)) on SBS2003 SP2 and they are saying that the Mail Server stops responsding at least once a day and has to be rebooted. I see errors in the Application log about the Message Store bing too large and the service terminating. I see the following error events in the log: Event Type: Error Event Source: POP3 Connector Event Category: Download Event ID: 1019 Description: The message download process finished with one or more errors. Event Type: Error Event Source: POP3 Connector Event Category: Download Event ID: 1036 Description: An error occurred during a POP3 transaction to server ... The error is 58 (The specified server cannot perform the requested operation). Event Type: Error Event Source: LicenseService Event Category: None Event ID: 202 Description: The product Windows Server is out of licenses. Use Licensing from the Administrative Tools folder for more information on which users are out of compliance and how many licenses should be purchased. Event Type: Error Event Source: POP3 Connector Event Category: Download Event ID: 1023 Description: The downloading process for mailbox <joes@elementscompanies.com [mail.elementscompanies.com]> was ended with one or more errors. Event Type: Warning Event Source: MSExchangeIS Mailbox Store Event Category: General Event ID: 9685 Description: Exchange store 'First Storage Group\Mailbox Store (XXX)': The current physical size of this database (the .edb file and the .stm file) is 24 GB. This database has exceeded the size limit of 18 GB. However, the logical free space in this database has not yet been evaluated. Therefore, it is possible that this database contains enough free space to bring its logical size below the maximum size limit. If the logical database size exceeds the maximum size limit, it will be dismounted on a regular basis. Event Type: Warning Event Source: MSExchangeMTA Event Category: Field Engineering Event ID: 2207 Computer: XXX Description: The MTA database recovery operation has completed successfully. Recovery details can be found in the file: C:\Program Files\Exchsrvr\mtadata\.\MTACHECK.OUT\MTACHECK.LOG. [DB Server MAIN BASE 1 67] (14) Event Type: Warning Event Source: MSExchangeMTA Event Category: Field Engineering Event ID: 2206 Description: The MTA database recovery operation is now checking queue: /O=ELEMENTSGROUP/OU=FIRST ADMINISTRATIVE GROUP/CN=CONFIGURATION/CN=CONNECTIONS/CN=SMTP (SERVER)/CN={228996E8-1C88-4305-8F92-E328A8DA3B82}, the filename of this queue is: 0100002C. [DB Server MAIN BASE 1 29] (14) Event Type: Warning Event Source: MSExchangeMTA Event Category: Field Engineering Event ID: 2219 Description: The MTA is running recovery on the internal message database because the MTA was not shut down cleanly. This operation may take some time. Status updates will be written to the Windows 2000 Event Log. [DB Server MAIN BASE 1 0] (14) Event Type: Error Event Source: MSExchangeSA Event Category: Monitoring Event ID: 1005 Date: 7/30/2010 Unexpected error <<0xc1050000 - Unknown Error. The logon to the Microsoft Exchange Server computer failed. Microsoft Exchange Server Information Store ID no: 80040111-03ee-80040111>> occurred. Event Type: Error Event Source: MSExchangeIS Mailbox Store Event Category: General Event ID: 9690 Description: Exchange store 'First Storage Group\Mailbox Store (SERVER)': The logical size of this database (the logical size equals the physical size of the .edb file and the .stm file minus the logical free space in each) is 22 GB. This database size has exceeded the size limit of 18 GB. This database will be dismounted immediately. Event Type: Error Event Source: MSExchangeSA Event Category: MAPI Session Event ID: 9175 Description: The MAPI call 'OpenMsgStore' failed with the following error: The attempt to log on to the Microsoft Exchange Server computer has failed. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0512-00000000 multiple logon errors bobby Event Type: Error Event Source: MSExchangeIS Mailbox Store Event Category: Logons Event ID: 1022 Description: Logon Failure on database "First Storage Group\Mailbox Store (XXX)" - Windows 2000 account XXX/X Error: -2147221231 Event Type: Error Event Source: MSExchangeIS Mailbox Store Event Category: General Event ID: 9689 Description: Exchange store 'First Storage Group\Mailbox Store (SERVER)': The logical size of this database (the logical size equals the physical size of the .edb file and the .stm file minus the logical free space in each) is 20 GB. This database size has exceeded the size limit of 18 GB. If the logical size of this database is not reduced to less than the maximum size limit, this database will be dismounted the next time a database size check is performed. Event Type: Error Event Source: MSExchangeSA Event Category: MAPI Session Event ID: 9175 Description: The MAPI call 'OpenMsgStore' failed with the following error: The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0526-00000000 Event Type: Error Event Source: MSExchangeFBPublish Event Category: General Event ID: 8206 Description: Unable to prepare message table for polling thread processing on virtual machine XXX. The error number is 0x80040115. Make sure Microsoft Exchange Store is running. Event Type: Error Event Source: MSExchangeSA Event Category: Monitoring Event ID: 1005 Description: Unexpected error <<0xc1050000 - Network problems are preventing connection to the Microsoft Exchange Server computer. An unexpected, unknown error has occurred. Microsoft Exchange Server Information Store ID no: 80040115-0514-000006b5>> occurred. Event Type: Error Event Source: MSExchangeFBPublish Event Category: General Event ID: 8206 Description: Unable to prepare message table for polling thread processing on virtual machine XXX. The error number is 0x80040115. Make sure Microsoft Exchange Store is running. Event Type: Warning Event Source: ESE Event Category: Performance Event ID: 508 Description: Information Store (3112) First Storage Group: A request to write to the file "D:\ExchangeData\priv1.stm" at offset 0 (0x0000000000000000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (86 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem. Is this a mailstore issue and what is the recommended method for properly remove the email account with message issues? Thanks TH

Hi, Check default POP3 virtual server server properties, POP3 connector manager properties. Try to mannually reterive mail from the mailserve Try to mannually reterive mail from the mailserver using telnet. Check the username and the password. The ISP was able to flush mail from the mailserver to the information store. Run the Configure E-mail and Internet Connection Wizard on the server to remove the accounts and then follow the wizard again to add the accounts back to POP3 connector. I hope this will help you. Regards. Shafaquat Ali.M.C.I.T.P Exchange 2007/2010, M.C.I.T.P Windows Server 2008, M.C.T.S OCS Server 2007 R2, Phone: +923008210320

This is the source of your problem: Event Type: Warning Event Source: MSExchangeIS Mailbox Store Event Category: General Event ID: 9685 Description: Exchange store 'First Storage Group\Mailbox Store (XXX)': The current physical size of this database (the .edb file and the .stm file) is 24 GB. This database has exceeded the size limit of 18 GB. However, the logical free space in this database has not yet been evaluated. Therefore, it is possible that this database contains enough free space to bring its logical size below the maximum size limit. If the logical database size exceeds the maximum size limit, it will be dismounted on a regular basis. You need to increase the maximum size of the database. http://technet.microsoft.com/en-us/library/aa998066(EXCHG.65).aspx That will be the cause of the database being made unavailable each day. The other errors are general POP3 connector errors, normally means a corrupt message. Your best option would be to switch to SMTP delivery. There would also appear to be a hardware problem with the storage. That could just mean the server is being taxed too hard, which is not uncommon with low end SBS servers, but could also be a sign of a pending hard disk failure. Simon.Simon Butler, Exchange MVP. http://blog.sembee.co.uk , http://exbpa.com/