Unsolved

This post is more than 5 years old

5 Posts

3676

February 1st, 2007 06:00

EmailXtender 4.8

Hello...

have some problems when try to connect with EmailXtender 4.8 to Exchange 2003. In EventLog icon apear Error:

Creation of the distribution list cache failed.

Failed to establish a MAPI connection: Failed logging on to MAPI profile: exMail32692

Policy engine failed to initialize

Source : CProcessMailbox
Routine : Init
Description : HrOpenExchangePrivateStore
HR : Unable to resolve mailbox

If somebody can help ... are welcome !

2 Intern

 • 

305 Posts

February 1st, 2007 22:00

Hi Vladslav
I've moved your question into its correct forum.
julie Gibson
Forums Support

397 Posts

February 5th, 2007 16:00

Can you open the connection mailbox using Outlook? Is there a distribution list in Exchange?
Try this:
Delete the profile under control panel>mail
Make sure the connection mailbox appears in the EmailXtender administrator under Vault Properties.

Hope this helps.

10 Posts

February 7th, 2007 06:00

Hello Vladislav,

You could login to your EX server with a service account which you use to run EX and open Outlook from there (as well as configure default profile).

Thx, Serge.

64 Posts

February 7th, 2007 12:00

Source : CProcessMailbox
Routine : Init
Description : HrOpenExchangePrivateStore
HR : Unable to resolve mailbox

^^

This error message tends to be generated when we are unable to locate a hidden connection mailbox.

I would recommend ensuring that our jounaling mailbox is not hidden from exchange address lists.

Hope this helps...

Chris

February 20th, 2007 09:00

I found that the mailbox store that my account was located in had been dismounted. Once we remounted the store, the issue was resolved.

Hope this helps.

Empire Geoff

1 Message

February 27th, 2007 15:00

On EmailXtender 4.8 -

Anyone know what these warnings are that get logged every now and again during an archive task?

No recordset found when attempting to update owners for message 44FC6F07A94C652BADEE3B3A

Event ID 0 - in the OTG event log

65 Posts

June 30th, 2008 04:00

When I have this error "No volumes when attempting to update owners for message . Requeing item back to Index Queue" I do this:

* disable journal mailbox updates via the following registry key:
HKLM\Software\OTG\EmailXtender\EnableJournalMbxAsOwner

Set the value to '0'(zero)

* A restart of the LEGATO EmailXtender Data Source service is required for the change to take effect.

If I have many items in Index_queue:

* Set the registry value:
HKLM\Software\OTG\EmailXtender\MaxRetryPerUPD

Set the value to '0'(zero)

* To increase the index poll time frequency:

Open EmailXtender Administrator from the Program menu on EmailXtender server
Right-click on the EmailVault object
Set the Indexer Process Poll time on the General tab to 1 second
Activate changes when prompted

When you have Index_queue, you must restore these values.

2 Intern

 • 

138 Posts

April 13th, 2010 07:00

Pit wrote:

When I have this error "No volumes when attempting to update owners for message . Requeing item back to Index Queue" I do this:

* disable journal mailbox updates via the following registry key:
HKLM\Software\OTG\EmailXtender\EnableJournalMbxAsOwner

Set the value to '0'(zero)

* A restart of the LEGATO EmailXtender Data Source service is required for the change to take effect.

Pit or other,

Is the value simply left at 0 or changed back after some time?  what does this key do?  Can the event simply be ignored or is it important?

Thanks much,

12 Posts

April 15th, 2010 16:00

Hello,

    

     The EnableJournalMBXAsOwner registry key should remain enabled ("1") and the MaxRetryPerUPD registry key should remain at least at the default of "60".  Altering these keys from their default could result in unintended loss of owner updates.

     If you are recieving a large number of "No Volume Found" or "No RecordSet" warnings in the OTG log please open a Service Request so Support can determine the root cause of the errors to prevent them from happening.  In some cases these warnings can be ignored as they are expected and in others they should be looked into.  For example, when using rules that exclude messages from the archive these warnings can be expected but they should not flood the Event log.

Thanks!

No Events found!

Top