Forum Discussion

-Maurice's avatar
-Maurice
Level 4
14 years ago
Solved

Error 0x8007000e (Outlook 2007 SP2 + HF2475891)

Hi all,

we have one customer which is getting Error Messages EventID 3411 (Not enough Storage available...) followed by EventID 2216 (Message dispenser will suspend processing...) , during the archiving window. This results in really poor archiving throuput/performance and thousends of messages stucking in MSMQ.

Environment:

  • 7x EV Servers running on 9.0.2
  • Outlook 2007 SP2 + HF2475891
  • EV Servers on Windows Server 2008 R2
  • Exchange 2003 latest SP2 & Exchange 2010 SP1 (2003 and 2010 SP1 Archiving Tasks are located on seperate EV Servers)
  • 6x Ex2010 Mailbox Archiving Tasks on EV003
  • 5x Ex2003 Mailbox Archiving Tasks on EV001

Exact Error Message:

An error has been reported by ConfigureMsgService.  It may be due to a problem contacting a Global Catalogue Server.

Exchange Server: XXXXXXXX011
Mailbox: SMTP:EnterpriseVault-XXXXXXXX011@customer.com
Error: 0x8007000e   
 

 

The Customer is in an on going exchange 2010 migration and centralization of ~16k mailboxes (2k mailboxes are already migrated). We are dealing more than 5 month with support to solve that issue with no solution. Hopefully someone has an Idea which helps to fix that issue.

 

We tried already the the following to solve the issue:

  • Set the "DS Server" key to CAS array and also to a specific CAS
  • Set the "DS Server" key to specific GC server
  • Re-Installed Outlook Hotfix 2475891 and also Re-Installed Outlook 2007 SP2
  • After advice from syma support we implemented NSPI regkey to 0xffffffff on every server in CAS array
  • Lowering the concurrent connections to 1 or 2 did "solved" the error message, but not the archiving performance, what is logical in result of the reduced connections
  • Set ProfileExpiry to 0 - after restart of task controller the servers are operating more or less well for 1 or 2 hours and then the error occurs again.

Thanks for reading

Best Regards, Maurice

  • Well regardless of a crash once it traps 0x8007000e it should still generate the debug logs

    But really your best bet is to continue to work with symantec, get them to work with microsoft to see if they can get this resolved for you