UNSOLVED

mbarnes5

updated

21 years ago

M

mbarnes5

2 Posts

0

844

December 15th, 2005 06:00

Faulting Application EmailXtract_Exchange.exe, version 4.70.337.0

all of a sudden EmailXtract will not initialize completely. GUI pops up for a couple of seconds and then disappears. The fault address is 0x0002767e. Nothing shows up in OTG logs. Only errors show in MS app event log. Any help is appreciated.
  • mbarnes5

    2 Posts

    260

    0

    Posted December 15th, 2005 08:00

    Do you know what causes the fault?
  • sdesrosi1

    70 Posts

    260

    0

    Posted January 4th, 2006 08:00

    EMC Support is still looking for the Root cause of this.
    What is going on is one of the task gets corrupt and it is preventing Xtract from loading.

    Not all the task are bad. if you don't want to recreate all the task you can start by removing them one by one until you find the one that is corupted. Then put the others back.

    To help you for the future (until this gets fixed) I would export all your tasks from the registry (when it's working) and keep them aside. If the problem surfaces, import the registry.

    In anycase, open a support incident and have them put you on the affected customer list of the "bug" that was opened for this.
  • ssakaria

    1 Message

    260

    0

    Posted January 9th, 2006 10:00

    Hi,

    I have a customer with excatly teh same problem running ob 4.70.434.

    The registry key that has been referred here does not appear to exist - please advice

    Sailesh Sakaria, MTI
  • mricketts

    11 Posts

    260

    0

    Posted January 23rd, 2006 10:00

    I experienced the same problem. The path was different in my case as well, but the end result was that it resolved my issue. Try this path:

    HKLM-SOFTWARE-OTG-EmailXtender-EmailXtract_Exchange-Tasks

    I would definitely export the key before deleting anything. Then delete any tasks that you have created until you remove the corruption and can open the application GUI. I would then create a .REG file so you can restore the key to a working state easily in the event it should corrupt again.
  • gparker2

    30 Posts

    260

    0

    Posted April 5th, 2006 16:00

    Hi,

    I experienced this same problem almost 12 months ago - and now I'm implementing EmailXtender v4.70.477 at another customer site and guss what - it's still happening!!!

    The issue has nothing whatsoever to do with so called "corrupted" tasks. The issue is this:-
    1) Create a recurring task in EmailXtract and configure it to "run as a service".
    2) You can exit out and relaunch EmailXtract without a problem as often as you like - UNTIL THE STROKE OF MIDNIGHT. Try launching the EmailXtract GUI at 12.05am the day after the task was created and the GUI will fail with the error message popping up in the Application Evant log!
    3) Edit the registry and delete the task. No need to bounce the EmailXtender services.
    4) Presto - the EmailXtract GUI works again!

    This is a very very serious issue/bug, as my customer needs to schedule recurring archive and shortcut tasks.
  • mricketts

    11 Posts

    260

    0

    Posted April 12th, 2006 11:00

    I have to agree with you. I still haven't found a resolution.
  • fschlupp

    2 Intern

    •

    397 Posts

    260

    0

    Posted April 14th, 2006 13:00

    What operating system are you using?

    Could Data Execution Protection be the culprit? We recently solved an issue with exQuery constantly blowing. We turned DEP off by changing the boot.ini entry '/noexecute={optin|optout}' to '/noexecute=AlwaysOff'
  • gparker2

    30 Posts

    260

    0

    Posted April 14th, 2006 23:00

    I think I might have solved it! If I create my EmailXtract tasks via the actual console of the EX server rather then via a remote desktop session, the EmailXtract GUI doesn't seem to crash anymore. For some reason, it doesn't like the recuurring tasks being configured via remote desktop.
  • ccharlto

    64 Posts

    31

    0

    Posted April 17th, 2006 12:00

    My understanding is that Extract is not a multi threaded application. Therefore you should always be on console 0 when administering the EX server.

    To do this correctly, enter the following steps:

    Start > Run > mstsc /v:machinename /console

    The above will force Console 0.

    Cheers,

    ccharlto