Unsolved
This post is more than 5 years old
54 Posts
0
620
August 31st, 2007 06:00
EmailXtract archive task with Lotus Domino hangs
hello,
does anybody have experiences with EmailXtender in Domino environment. i have very confusing situation with EmailXtract archive task. btw, EX version is EX 4.81 and Domino/Notes is 7.0.2.
when i run archive task from console manually it works fine. but when i run it as service it hangs. usually it runs about 10-20 minutes and after that there is error message in task log:
*** NOTES Error in mailbox xxxx: The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists.
this xxx mailbox is different every time. so it is not dependent on particular mailbox.
after that error nothing works anymore. even journaling stops receiving new e-mails. there is no error messages in OTG event log. EX hangs so hard that i have to kill EX services (from Task Manager) or sometimes even restart server to get it working again.
and this happens every time when scheduled task is running. it does not matter whether this task runs on busy hours or not. sometimes it scans through 20 mailboxes, sometimes couple of hundred, but eventually it hangs... but once again, when starting task from console (clearing "run as service" checkbox) it works without any problem.
i have set up lots of EX environments for our customers but mostly with Exchange. this is first production Domino for me...
does anybody have a clue where to dig?
regards,
kipz
does anybody have experiences with EmailXtender in Domino environment. i have very confusing situation with EmailXtract archive task. btw, EX version is EX 4.81 and Domino/Notes is 7.0.2.
when i run archive task from console manually it works fine. but when i run it as service it hangs. usually it runs about 10-20 minutes and after that there is error message in task log:
*** NOTES Error in mailbox xxxx: The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists.
this xxx mailbox is different every time. so it is not dependent on particular mailbox.
after that error nothing works anymore. even journaling stops receiving new e-mails. there is no error messages in OTG event log. EX hangs so hard that i have to kill EX services (from Task Manager) or sometimes even restart server to get it working again.
and this happens every time when scheduled task is running. it does not matter whether this task runs on busy hours or not. sometimes it scans through 20 mailboxes, sometimes couple of hundred, but eventually it hangs... but once again, when starting task from console (clearing "run as service" checkbox) it works without any problem.
i have set up lots of EX environments for our customers but mostly with Exchange. this is first production Domino for me...
does anybody have a clue where to dig?
regards,
kipz
No Events found!
fschlupp
397 Posts
0
September 5th, 2007 12:00
¿ Verify that the ¿EmailXtender shortcut¿ user exists in the NAB and the comments field contains the correct EmailXtender Server name.
¿ Check if there is any errors in the log.nsf
¿ Verify the Domino console reports that the Shortcut extension manager is loaded
¿ Ensure the following entries exist in the Notes.ini file:
EmailXtenderShortcutDB = EXSHORTCUT.NSF
EXTMGR_ADDINS=EXNOTESSHORTCUTEXT
Hope this helps
kipz1
54 Posts
0
September 13th, 2007 06:00
actually, this list did not help. i still have that problem. i have opened case is support and currently they are investigating this issue...
kipz
szekelyk
129 Posts
0
September 13th, 2007 06:00
do you have such kind of list for Exchhange enviroment too?
Because I have the exactly same experinece with EX (various versions) and Exchange.
If I try to run a task as a service (what is a very good idea) it will hung without any error message. I have and older EX 4.7 connected to Exchange2003 and EX 4.81connected to Exchange2000 at two different customer.
Krisztian
fschlupp
397 Posts
0
September 13th, 2007 06:00
EmailXtract tasks are held in the registry. If you create a task and the system crashes when you launch it, it¿s possible that a previous task did not complete and it is caught in a loop. You can look in the registry, delete the task, and start another one to see if that is what is crashing the system.
If you create a new keyword called DebugEnabled in the registry, set it to 1, and stop and restart EmailXtract, you can skip the ¿already archived¿ check on the hidden settings tab. This improves performance because the mail application filters some of the messages before EmailXtract attempts to act upon them. It allows EmailXtender to make the decision as to whether or not to archive the messages. This setting is there only if you have already run EmailXtract. If this setting is enabled, it calls the SQL
database for every single message. If EmailXtract sets the flag on
the message, it doesn¿t check to see if it is archived.
EmailXtender 4.5 / 4.6:
¿ Are the forms on the client?
¿ The first time you attempt to open a shortcut, Outlook will recognize the message class of the mail item to be
IPM.Note.EXShortcut.
¿ When a user first resolves a shortcut in Outlook, the files (exscfs.exe and XtenderMsgRetriever.dll) are downloaded to the client. The files can be located at:
\Documents and Settings\ \Local Settings\Application Data\Microsoft\FORMS\IPM.Note.ExShortcut
¿ Many times, an Antivirus application will block the transmission of .exe and .dll files. To ensure these files get to the clients, you will need to:
¿ Setup an exclusion rule on the Antivirus server to allow the transmission of the files
¿ Manually copy these files to the clients
These files are located on the EmailXtender Server at the following location (if using the default installation
path):
\Program Files\OTG\EmailXtender\Exchange Forms
EmailXtender 4.7 (Outlook Shortcuts):
¿ If Shortcuts do not resolve through Outlook and you would like to enable the COM component in debug mode:
1. Create registry key HKEY_LOCAL_MACHINE\SOFTWARE\EMC\EXShortcutAddin
2. Add two registry values
LogFilePath String c:\
LogMode DWORD 3
3. Restart Outlook.
¿ This will write debug info to EXShortcutAddin.log file in the C:\ directory