2 Intern

 • 

204 Posts

July 22nd, 2008 13:00

Cool stuff and excellent news. - I am glad you fixed it. I will keep the info in mind and thanks for sharing it in the forum.

Keep well, Jochen.

2 Intern

 • 

600 Posts

July 28th, 2008 23:00

Greetings,

One piece of advice, "DebugEnabled" is not meant to be used unless your environment has been accessed by EMC support. Even a support engineer will go to his upper peers to get the approval.

Reason is quite simple that "DebugEnabled" is not a documented procedure to be followed unless EMC support is engaged.

I have seen this registry key haunting people in future.

Usually when you miss email always check "EmailVault\Baddir" that is the first directory that gets the mails in case EX cannot processes that which include loosing connection to SQL or many other things. If you find messages there you could engage support to help you to process these.

In any case if in doubt its never wrong to engage EMC support.

Hope this helps.

Thanks,
Raj

80 Posts

September 4th, 2008 14:00

OK...so after exhausted tried with EMC tech support, I was instructed to begin with a clean install of EX and SQL databases. So, I verified that all containers were closed (after removing the journaling mailbox), uninstalled EX from the server, then removed the SQL databases. Reinstalled from scratch, then ingested all container files. I am now running an Archive Task, and it is picking up messages that were being skipped before...a very long process. Just thought that I would update everyone.
No Events found!

Top