Forums  Register  Login  My Profile  Inbox  Address Book  My Subscription  My Forums 

Member List  Search  FAQ  Ticket List  Log Out

 

RE: Application Event log: Event ID: 6206

 
Logged in as: Guest
Users viewing this topic: none
  Printable Version
All Forums >> [Archiving & Fax] >> GFI MailArchiver >> RE: Application Event log: Event ID: 6206 Page: <<   < prev  1 [2] 3   next >   >>
Login
Message << Older Topic   Newer Topic >>
RE: Application Event log: Event ID: 6206 - 11.May2006 2:50:11 AM   
golovast

 

Posts: 7
Joined: 10.May2006
Status: offline
Its two messages happening at the same time. First message is as following:

Source: IMAP4SVC
Category: Content Engine
Event ID: 1023
Type: Error

Description:

Error 0x80040c05 occurred while rendering message 003e-000000b1a084 for download for user xxxx@xxxx.com.

The e-mail address in the above message is the account designated for GFI archiving.

Second event is:

Souce: Marc3Host
Category: None
Event ID: 6206
Type: Warning

Description:

Plugin DSScheduler reports exception.

Data Sources: Cannot open message.
      
Additional info: IMAP protocol error. 3 NO Invalid message format..



This happens repeatedly over a course of a few days. The message ID is always the same, although I don't know how to find that message in Exchange via that message ID. Message Tracking tool or searching the logs doesn't give me anything. I managed to resolve this today by using an IMAP client to login into the archiving mailbox and deleting a few hundred of the oldest messages. After that I've deleted dlearccache1.chc and dlearccache2.chc from the Mailarchiver\Cache folder and restarted the service. It picked up after that point and started archiving the messages.

However, this is the second or third time that this happened and I would like to be able to prevent this in the future. Exchange version is 2003 sp2. MailArchiver version is the latest build.

Thanks,
Arthur




(in reply to BenN)
Post #: 16
RE: Application Event log: Event ID: 6206 - 11.May2006 4:21:47 AM   
Rodion

 

Posts: 834
Joined: 15.Nov.2004
Status: offline
There is KB article from MS that relates to this problem
http://support.microsoft.com/?id=892397

Are you sure you have Ex2003 SP2 installed?



P.S. That was not a really good idea to delete dlecache files...

< Message edited by Rodion -- 11.May2006 4:23:21 AM >


_____________________________

Best regards

Rodion Denisyuk
GFI Software Ltd

(in reply to golovast)
Post #: 17
RE: Application Event log: Event ID: 6206 - 11.May2006 4:54:48 AM   
golovast

 

Posts: 7
Joined: 10.May2006
Status: offline
I saw the article.  I also saw some other ones dealing with a similar error as well as discussions in some forums.
None of them seemed to quite fit my problem.

I don't know how I can be more or less sure that I have the service pack
installed... I mean its either installed or it isn't, right?...:)

Also, as far as these files go, I didn't delete them outright. Stopped the service and moved them to another dir just in case.
I figured they are for write cache for GFI and perhaps something got corrupted in there.




if(typeof(dstb)!= "undefined"){ dstb();}

(in reply to golovast)
Post #: 18
RE: Application Event log: Event ID: 6206 - 11.May2006 5:17:27 AM   
Rodion

 

Posts: 834
Joined: 15.Nov.2004
Status: offline
I suggest next time you experience that error to stop polling, have a look at the messages in the archiving mailbox and try to locate the culprit.

The actual error occurs at the polling stage - before emails get to the dlecache.
There could be some files stuck in the cache you moved so I may suggest the following procedure to recover them:

1) stop polling
2) wait for approx 10 minutes
3) stop mailarchiver service
4) restore dlecache files
5) start mailarchiver service
6) start polling

_____________________________

Best regards

Rodion Denisyuk
GFI Software Ltd

(in reply to golovast)
Post #: 19
RE: Application Event log: Event ID: 6206 - 11.May2006 2:27:34 PM   
golovast

 

Posts: 7
Joined: 10.May2006
Status: offline
I was trying to find the message, but I don't know how to correlate the number in the event log (003e-000000b1a084) to the actual message. I assumed it was a message ID, but searches for that number or parts of it came out blank.

(in reply to golovast)
Post #: 20
RE: Application Event log: Event ID: 6206 - 11.May2006 3:32:13 PM   
golovast

 

Posts: 7
Joined: 10.May2006
Status: offline
There is goes again. Same exact situation less then a day later. Message ID is different though. Any advice on how to find this message?

Thanks,
Arthur

(in reply to golovast)
Post #: 21
RE: Application Event log: Event ID: 6206 - 12.May2006 5:37:13 AM   
Rodion

 

Posts: 834
Joined: 15.Nov.2004
Status: offline
Open the archiving mailbox using Outlook Express via IMAP and try to access and download each email

_____________________________

Best regards

Rodion Denisyuk
GFI Software Ltd

(in reply to golovast)
Post #: 22
RE: Application Event log: Event ID: 6206 - 12.May2006 4:47:25 PM   
golovast

 

Posts: 7
Joined: 10.May2006
Status: offline
I can open the mailbox via IMAP and access and download the email in question. Basically it comes down to this. There is an occasionall e-mail that the Archiver can't get. At that point it keeps retrying until the e-mail is deleted. I can go into the mailbox and delele the "bad" email, but this is not a really good option. If I have to do this once a day, then this is not really an automated solution. So far, these email have been SPAM, but that does change the fact that the Archiver stops working. Since has been happening at a fairly high frequency since I've upgraded to the latest release. Considering the amount of emails that my company receives, I am sure that similar e-mails have come through before and I haven't had this problem. Below is information on the type of e-mail that it can't handle:

This is a multi-part message in MIME format.
--------------002_Dragon452823382426
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


This is from the header:

Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="------------002_Dragon951164367413"

(in reply to BenN)
Post #: 23
RE: Application Event log: Event ID: 6206 - 30.May2006 9:37:40 AM   
michaelw

 

Posts: 1
Joined: 30.May2006
Status: offline
This is happening to us, too.

I've noticed this has been happening for quite some time to a lot of folks.  Are we getting anywhere in solving it?

(in reply to golovast)
Post #: 24
RE: Application Event log: Event ID: 6206 - 30.May2006 10:47:35 AM   
Rodion

 

Posts: 834
Joined: 15.Nov.2004
Status: offline
Hi

Make sure that you have envelope journaling enabled. It solves the problem (except that you will still need to manually delete existing stuck emails from journaling mailbox)

_____________________________

Best regards

Rodion Denisyuk
GFI Software Ltd

(in reply to michaelw)
Post #: 25
RE: Application Event log: Event ID: 6206 - 7.Jun.2006 12:21:22 AM   
srakkhit

 

Posts: 77
Joined: 7.Feb.2006
Status: offline
Hi

I have uploaded my debaug files in a folder called BUPA-Australia

Thanks

(in reply to Rodion)
Post #: 26
RE: Application Event log: Event ID: 6206 - 6.Sep.2006 1:25:35 PM   
wazinga

 

Posts: 1
Joined: 22.Aug.2006
Status: offline
Hi Rodion
I have exh 2003 with SP2 but this happens to me as well and i have to log onto the journal mailbox and look for the mail.
I think GFI should look try and get a solution un the next build.
Because of this, i have to keep a constant eye on mail archiver since poll.

(in reply to Rodion)
Post #: 27
RE: Application Event log: Event ID: 6206 - 7.Sep.2006 3:06:46 AM   
Rodion

 

Posts: 834
Joined: 15.Nov.2004
Status: offline
Hi wazinga

Do you have envelope journaling enabled? (refer to the MailArchiver manual for the details)

_____________________________

Best regards

Rodion Denisyuk
GFI Software Ltd

(in reply to wazinga)
Post #: 28
RE: Application Event log: Event ID: 6206 - 25.Oct.2006 8:29:08 PM   
adenhaan

 

Posts: 7
Joined: 25.Oct.2006
Status: offline
Rodion,

quote:

(except that you will still need to manually delete existing stuck emails from journaling mailbox)


With all due respect, this means that this is NOT a solution... it is merely a workaround.

Having to check status of service multiple times a day, and then having to manually delete a message from the journaling mailbox to get archiving going again is not something any admin will look forward to.

The perticular situation is caused by using IMAP protocol to retrieve messages. I'd like to suggest that you consider adding support for MAPI to the product to really "solve" the issue. Especially since this impacts many if not all of your customers.

Andre.

(in reply to srakkhit)
Post #: 29
RE: Application Event log: Event ID: 6206 - 27.Oct.2006 4:22:17 AM   
Rodion

 

Posts: 834
Joined: 15.Nov.2004
Status: offline
Hello adenhaan

Are you affected by the above problem? There were only a few customers reporting this issue and enabling envelope journaling (highly recommended to be used with MailArchiver) solves the problem.

MAPI has its own problems - mostly related to the client configuration

_____________________________

Best regards

Rodion Denisyuk
GFI Software Ltd

(in reply to adenhaan)
Post #: 30
Page:   <<   < prev  1 [2] 3   next >   >>
All Forums >> [Archiving & Fax] >> GFI MailArchiver >> RE: Application Event log: Event ID: 6206 Page: <<   < prev  1 [2] 3   next >   >>
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts