crash while archive is being done

[tlac]

Hey hey,

I have a crash of a2goengine.exe while doing the archive process.

Im using GW 2012 SP2 (12.0.2).

Tried with both 2.0.0.3 and 3.0.0.1 versions, it always crash. It’s a Windows error crash “Archive 2 Go stopped working blahb lah blah”

A DLL is displayed on Windows eventlog, msvcr110.dll. I’ve tried on another desktop, it still crashes, but with msvcr90.dll

The first desktop used is an XP SP3 computer, the second one is a W7 SP1. Both 32 bits, both with A2GO requirements ( http://www.advansyscorp.com/pr…-to-go/#requirements )

The crash occurs on only 2 accounts (for now) and for both of them, while archiving the user’s own archive.

Can you please help me to fix this error ?

Thanks.

Topic

[Support 3]

Thanks for your message.

Sorry to hear about the issue, most likely this behaviour is data related.

Is there any archive log file (*.log) available? You can find the archive log file by looking at the archive folder, for example: C:Temptest Archivetest.log. The archive log file may not show the specific message causing the issue, however it may show the folder it processing. Please send the archive log and some screen shots of the error to support AT advansyscorp.com.

We also recommend you to perform full health check of the mailbox, primarily by running GWCheck with the appropriate options. Please see the following feature topic for troubleshooting export problems:
http://www.advansyscorp.com/forums/topic/2021043902/

Best Regards,

Advansys Support

[tlac]

Thank you for your answer.

I’m currently running a new Archive To Go in order to get the logs you need (removed it yesterday because of lack of free space on hard drive)

After the first crash, i’ve ran a gwcheck on the archive before running the A2GO process, so it does not fix the problem.

[Support 2]

Thanks for the update about the GWCheck and sorry to hear that it did not resolve the problem. Experience over the years indicates that when data related problems occur, they are often within GroupWise personal archives. This may be simply the process of archiving over a long period of time, and perhaps different client revisions, which may increase risk of database corruption.

One approach we’ve found to be relatively successful is to identify the personal archive folder which is causing the problem from the error log. Then access the personal archive and move some messages from the problematic folder into onto another folder. This is also mentioned in our hints and tips. This approach is not an exact science but we believe the movement of messages causes a rewrite of some underlying database tables, which can resolve these type of export issues. Of course it could also come down to a specific corrupt message. The only way to help identify the general problem is by analyzing the log files and perhaps keeping note if A2Go seems to crash at exactly the same point in the export process.

Kind Regards,

Advansys Support

[Author]

Replies