EmailXtender policy engine failed

Hi,

It is safe to assume that this one is a bug of sorts, there is no reason why EX Installer wouldn't at least create an empty Emailxtender.dlc automatically, when there are any problems with names-gathering from mailsystem. I have rarely seen any problems with EX after creating this file manually (empty file), and when they appeared they were mostly connected with users' permissions on mailsystem.

As you probably know, dlc file contains all the names that were gathered, that might be receiving emails for archiving. I don't know the exact procedure for this, but somehow distribution lists in mailsystem are entrance for "name harvesting", so if you are fed up with creating empty dlc file you might want to try setting up 2 or 3 distribution lists, each with 5 - 10 users - this should set up environment where policy engine might not fail.
Still, creating empty file seems easier, doesn't it ?

Well yes, it is easier to create an empty dlc file but if it is a bug, why can't the support solve this? I had opened a case long time ago and it was not taken as a bug. As a workaround, I will create an empty dlc file or even copy it off my machine onto the server (however creating an empty file seems logical).

Thanks. Let's see what others can come up with.

Voting won't help here - you need to open this as official case at support.

I come across the same problems!
I also vote that this bug be fixed!!

As I mentioned earlier, I had opened an official case with Legato support at the time I first installed this. It was not taken as a bug and this surpised me. Anyways, the problem never got solved.

Besides, no matter what OS, no matter the version of Exchange, no matter the version of EX that I have used, I have always got the same problem. It is still annoying to have to create an empty dlc file or copy it off some place. Also, it is annoying that this was not taken as a bug.

If they won't recognize it as bug you should open this as RFE to fix it. Then each of us could assign our companies or ourselves as interested parties to the RFE. More of us gets attached to the same RFE more the chance is that it is changed (or fixed if you like it more that way).

This is something from a case I had with similar symptons issues, try at your own risk or preferably in a lab environment!

NOTE: Backup entire registry before performing the actions below.

In the registry we need you to change the following:
[HKEY_LOCAL_MACHINE\SOFTWARE\OTG\EmailXtender\] "MaxNumIndexProcesses"=dword:00000004 Change this value from 'a' to '4'

[HKEY_LOCAL_MACHINE\SOFTWARE\OTG\EmailXtender\Accounts] Delete these 2 values under
"InstallDate"
"PolicyEmail"

[HKEY_LOCAL_MACHINE\SOFTWARE\OTG\EmailXtender\OnChange] Change this value from '1e' to '5' as shown below:
"ServicesReload"=dword:00000005

Please post results to this forum.

I encountered the same policy engine failed message in my test environment. The problem for me was caused by the lack of distribution lists containing actual mailboxes. The test Exchange server contained only a restore of some mailboxes and was not a complete DR.

This thread has helped me. I had the same problems in the test lab with this.
I mail-enabled Domain Users group and updated ExAddrRule.exe to version 4.70.570 and the problem went away.

Hello, Can you explain clearly about your solution? How can I update the EXAddrRule.exe file? and what is "mail-enabled Domain Users Group" ?

There is a 570 patch just for this file.
An mail enabled group means taht you have to have at least one group of users in your active directory which is mail enabled, ie: super_duper_users@mydomain.com (mail sent to this mail would go to all users belonging to this group).