The Exclaimer Community

Exclaimer Forums
Welcome to The Exclaimer Community Sign in | Join | Help
in Search

Error "Writing mail to database"

Last post 04-03-2008, 2:45 AM by mickhardy. 8 replies.
Sort Posts: Previous Next
  •  09-24-2007, 12:52 PM 1946

    Error "Writing mail to database"

    Server is running Windows 2003 Server Standard SP2, Exchange 2003 SP2, SQL Server Express Edition SP2. (german localized versions)

     

    The Exclaimer Email Archiver Service has issued the following error: Mailbox: Exclaimer Email Archiver Service

    Current Operation: Writing mail to database

    Status: Error

    Further Information:

    The Exclaimer Archiver Service has experienced a serious problem or a number of problems whilst processing mail and has now stopped processing. It will attempt to resume in 600 seconds. If you experience continued problems please use the system documentation and the Event Log to check the root cause of the problems and restart the Exclaimer Email Archiver Service.

    Last reported information:

    There was an error (0x80040e14) writing the mail 'Easy download' to the database. Exclaimer Email Archiver will attempt to re-process this mail at a future time.

    The Exclaimer Archiver Service will continue to process mails unless it encounters repeated problems.

    --

    The Exclaimer Email Archiver Service has issued the following error: There was a problem sending a notification message (0x80070005). Please check your configuration options.

    --

    The Exclaimer Email Archiver Service has issued the following warning: Mailbox: Exclaimer Email Archiver Service

    Current Operation: Writing mail to database

    Status: Warning

    Further Information:

    There was a problem (0x80040e14) writing the mail 'Easy download' to the database. Exclaimer Archiver will attempt to process the message another 1 times before failing.



     

  •  10-04-2007, 9:43 AM 1975 in reply to 1946

    Re: Error "Writing mail to database"

    Hello,

    Please click on the options button of the Archiver to see if the SMTP server options are correct. Please then click on edit and check the account selected for error notifications exists.

    I would advise granting yourself rights to the Exclaimer Email Archive Mailbox, opening in Outlook, locate the message "Easy download" and delete as the Archiver is having problems processing this message.

    Best Regards

    Joshua Clarke

    Exclaimer Support


    Joshua Clarke
    Exclaimer Support
  •  10-18-2007, 12:25 PM 2019 in reply to 1975

    Re: Error "Writing mail to database"

    Hello,

    I have the same problem. I removed the complete Archiver an reinstalled it. No solution, deleted the mailbox and created a new one, no solution. Granted my-self full controll over all the mailboxes, no solutions. I checked all the settings, everything looks good inside the Archiver tool.

     I am using an Windows 2003 SBS Premium Server with SP2. SQL 2005 is installed.

     Are there more things I can check??

     

    Greetings,

    Marco Pol.

    Consultant.

    Beerepoot Computers, Exclaimer Reseller The Netherlands.

  •  10-23-2007, 12:39 PM 2034 in reply to 2019

    Re: Error "Writing mail to database"

    Hi Marco,

    What is the error you are receiving in the Status window of the Archiver?

    Many Thanks

    Joshua Clarke

    Exclaimer Support


    Joshua Clarke
    Exclaimer Support
  •  10-23-2007, 7:51 PM 2040 in reply to 2034

    Re: Error "Writing mail to database"

    Hello Joshua,

    There was an error (0x80040e14) writing the mail 'FW:Gevoel op je werk' to the database. Exclaimer Email Archiver will attempt to re-process this mail at a future time.

    Thanks,

     

    Marco Pol

  •  12-17-2007, 8:36 AM 2167 in reply to 2040

    Re: Error "Writing mail to database"

    Good luck on getting this to work,  I have the same environment and issue and they were unable to fix it
  •  12-17-2007, 8:03 PM 2170 in reply to 2167

    Re: Error "Writing mail to database"

    Hi Guys

     Well I have had this issue and as you have been searching. I did manage to get it working on SBS 2k3 with SQL 2005, after several failures and re-builds (test systems are great)

    It appears to be linked with the install of SQL,  if you accept all the defaults whilst installing SQL Server you will experience this error and nothing will ever get from the journal account to the SQL DB.

    Whilst installing SQL ensure Full text Search is installed and all client components, this then worked OK for me.

    This was on a fresh install - i am just trying to see if a 'broken' install can be fixed by changing components in the SQL install.

    Hope this helps for now will post findings when i get them.

    Bluemarlin

  •  04-02-2008, 4:23 PM 2440 in reply to 2170

    Re: Error "Writing mail to database"

    Luckily I had this error during testing and have decided not to go ahead with a purchase... Lack of support does not go down well with prospective customers...
  •  04-03-2008, 2:45 AM 2441 in reply to 2440

    Re: Error "Writing mail to database"

    I've had loads of issues importing old PST files and our mail store on an SBS2003 box including the error in this thread. I've been importing by year in reverse order so older emails are in the older archives. I think this should be automated but that's a feature request. Importing emails by year into appropriately named databases would be nice but it's only available as a rollover option for new emails not importing old emails.

    All my problems were due to the AutoGrow setting in SQL Server. I had this set too high at 1GB with 10GB rollovers and always around about the time of rollover, OMI would crash, this error would be logged and the SQL Server Event ID 17055 AutoGrow time out or cancel event would be logged.

    Changing AutoGrow to 10MB caused further problems as the database would automagically change itself back to grow by 10% which would cause all the errors and OMI to hang and the server to become quite unresponsive. Auto grow by huge amounts like 1GB or 10% of 10GB causes numerous archiving failures, 17055 time out errors and OMI crashes.

    I have this set to 100MB and everything seems to be happy. The installation manual recommends 20MB.

    Edited to correct installation manual auto grow recommended value.

View as RSS news feed in XML
Powered by Community Server, by Telligent Systems