Unsolved
This post is more than 5 years old
2 Intern
•
138 Posts
0
893
December 22nd, 2009 11:00
Policy Engine failed to Initialize due to LDAP rules: esg106075
Hello.
Exchange 2003
EmailXtender 4.81.1459
I'm having trouble with Rules (or LDAP quieries?) on my new EmailXtender Server. The EX server is a member of the forest root domain where we have some Exchange Servers. We also have 6 child domains with Exchange Servers and Users. The goal is for all Servers to Journal to a Dedicated Journaling Server in the forest root and have the EX server pull the mail from the dedicated Journaling Exch Server.
We created a Cabinet for each of the 6 child domains and put a collection rule on each cabinet. We want to store each domain's mail separately. Each of these domains is used in one country and each country has their own email domain address, so the collection rules state to collect FROM/TO "domain-country.com".
The problem is that the rules are being ignored. During testing all journaled mail is ending up in an "unmatched" cabinet even though it matches one of the collection rules on another cabinet.
I did not see many error messages in the OTG log UNTIL I added a specific email address collection rule for a cabinet. I then got the exact error messages as show in esg 106075:
Source: Emailxtender
Category: AddrRule
Description: Creation of the distribution list cache or rules failed.
Source: Emailxtender
Category: AddrRule
Description: Policy engine failed to initialize
Source: Emailxtender
Category: AddrRule
CPolicy::CPolicy unable to use-access profile ''. Error: 0x80070006. Trying profile 'exMail4278'
Source : CProcessMailbox
Routine : Init
Description: m_ExAddrRule.CreateInstance
HR : E_FAIL - Unspecified error
Source: EmailXtender
Category: Smtp
Description: [Failed to Initialize ExAddrRule.exe] repeated 3 times.
Source: EmailXtender
Category: Smtp
Failed to Connect to Exchange Server: ExchangeServerName MailBox EXJournalMailboxName Reason: Failed to Invoke CoExMailBox 80004005
Source: EmailXtender
Category: Smtp
Description: [Failed to Initialize ExAddrRule.exe]
The ESG states the cause as:
There is one or more LDAP collection rules (Address-specific) that are unable to resolve through querying Active Directory. This is due to invalid query filters or resource names within the EXLDAP:// query
and the resolution is to try to identify the offending rule. I know which one is the offending rule, it's the email collection rule I created as a test. When i remove this the error messages in OTG go away but the remaining email domain collection rules do not work.
I created that email address collection rule by picking the user from the GAL. I don't understand how to continue because the Resolution in this ESG just states to remove them, however there is something else the matter.
I also reviewed esg100854 and verified that our MaxPageSize value is set to 2000, 1000 above default, not sure if that is relevant.
There is obviously something wrong here but I am not sure how to continue.
Any help is appreciated!
Wisers
2 Intern
•
138 Posts
0
December 23rd, 2009 07:00
A case opened with EMC revealed that If I have more than one collection rule that overlaps on the same item, this will cause problems.
For example, A Domain collection rule and a specific email address collection rule that both try to collect the same domain suffix will cause the Address Rule service to die in a horrible crash. EX stops pulling in mail from the connection mailboxes when this crash happens.
The case is still open, because they are investigating it still.
In my opinion, I do not think that this situation should crash EmailXtender. Rather, there should be one of two things that would happen:
1. The email message would flow through Email Xtender Vaults and cabinets and on every rule that it matches it would be processed with no errors. This would be more acceptable and in line with the idea that messages are duplicated when there are two cabinets or folders, with no rules. It is easiest to remember and understand.
OR
2. The email message would flow through Email Xtender Vaults and cabinets and when the FIRST rule that matches the message is found, the email is processed and it does not continue to other Rules.