Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

An error has been reported by ConfigureMsgService

Created: 29 Jun 2010 • Updated: 31 Jul 2013 | 22 comments
This issue has been solved. See solution.

Enterprise Vault v8 SP4
I am getting the followind error every 15 minutes.
I suspect that it mab be related to the Global Catalogue Server. The MAPI error suggests this.
However I can not find a 3411 error anywhere in the EV forums or Knowledgebase.

Anybody any ideas?

Event Type: Error
Event Source: Enterprise Vault
Event Category: None
Event ID: 3411
Date: 10/06/2010
Time: 17:54:46
User: N/A
Computer: xxxxx01
Description:
An error has been reported by ConfigureMsgService. It may be due to a problem contacting a Global Catalogue Server.

Exchange Server: xxxxxxxxx1A
Mailbox: SMTP:xxxxxxx@xxxxx.com
Error: MAPI_E_NETWORK_ERROR 0x80040115

Discussion Filed Under:

Comments 22 CommentsJump to latest comment

GertjanA's picture

Hi Abhee,

The error indicates communication error with GC. There are registry keys to set this. Look for Closest GC and another one.
Additionally, if your DC's are Windows2008, search for NSPI.

Check http://support.microsoft.com/?scid=kb%3Ben-us%3B319206&x=14&y=13
and http://seer.entsupport.symantec.com/docs/293154.htm

Thank you, Gertjan, MCSE, MCITP,MCTS, SCS, STS
Company: www.t2.nl

www.quadrotech-it.com

www.symantec.com/vision

Thiyagu's picture

Hi,

We tried that, but it goes back to the same error again now.
Is there any thing else we can do about this?

thanks
Thiyagu

Rob.Wilcox's picture

Okay, so first of all, can you give us some environmental details - like number of Exchange servers, number of archiving tasks, number of threads per task.  Is this occuring throughout the day?  What is your archiving schedule?

Next up .. check the system mailboxes for each of the tasks.  Can you open them with Outlook?  Are they hidden?

JesusWept3's picture

Try DS Server instead, I had this issue where closest GC didn't fix it but DS Server did

HonkyTonkHero's picture

I have tried the Closest GC as well and not had any success. I will now take "JesusWept2" advice and trice the DS Server. I have also heard from support that Outlook 2003 on the EV server performs better than Outlook 2007. It handles more MAPI threads oo something like that. Outlook 2007 is more stingy and processes slower. At this point I am not going to remove 2007 and put 2003 on the EV server. Moving backwards just doesnt feel right.

I will update in a few days as to whether the DS Server reg entry helped. So far (its been 30 min since the change) no more errors.

GertjanA's picture

In my previous job, we tried 2007 outlook (on ev8sp2), which was painfully slow, especially with journal-archiving. we've re-installed 2003, worked like a charm again.

Thank you, Gertjan, MCSE, MCITP,MCTS, SCS, STS
Company: www.t2.nl

www.quadrotech-it.com

www.symantec.com/vision

JesusWept3's picture

well the issue isn't with EV on this one, its with Microsoft Outlook and how much they've changed the MAPI interface, I know its being actively worked on with a lot of priority especially since Outlook 2007 is requred for Exchange 2010

AndrewNolan's picture

I've recently upgraded to EV 9.0.1 and Outlook 2007 as we are in the process of testing exchange 2010 and I'm seeing these errors all day long since the upgrade.  I've tried to set both the GC and the DS in the registry, but neither stopped the errors.  Rolling back to Outlook 2003 is not an option since we already have an archive task setup for the 2010 exchanges boxes.  I have noticed that the errors only occur on the exchange 2003 archiving task and not the 2010 archiving tasks.  Is there anything i can do to stop these or will I just have to wait until we're completely migrated to 2010?

Rob.Wilcox's picture

You should uninstall the hotfix mentioned in this post :

https://www-secure.symantec.com/connect/blogs/outlook-2007-update-resolve-issues-ev-server

There is a 9.0.1 Journal Task hotfix that might be what you're after too.

JesusWept3's picture

Try the Outlook 2007 performance hotfix, it resolved issues for us when we ran in to the same thing, but expect other issues to follow.....microsoft will be releasing another hotfix around stability and performance come the end of february

AndrewNolan's picture

Rob-  That hotfix had not been installed.  I read in an article from the link you sent that the following registry key should be changed to a lower number on busy EV servers: HKLM\Software\KVS\Enterprise Vault\Agents\ProfileExpire.  Could that help my situation?

Jesus-  What's the KB number to that hotfix?  Tried searching for it, but many came up.

Thanks

JesusWept3's picture

This is the Performance hotfix
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2458611

We found that we had every task failed, on 9 sp1 + Outlook 2007, very much the same as you had, Closest GC didn't fix anything, DS Server only resolved some of the tasks, but other tasks were failed due to being in another domain

However when you install the hotfix, you may see some Application 1000 errors in the event log showing that the ArchiveTask ahs crashed against EMSMDB32.DLL, microsoft are aware of this and have already resolved it internally and will be released as a cumulative hotfix at the end of february

It is this that Symantec are asking people not to install the hotfix, however in our position we were the same as you, rolling back to 2003 was not an option, so installing the hotfix and at least get the archive tasks running and people archiving was the only thing we could do

SOLUTION
Michael Bilsborough's picture

Hi,

If it was the Outlook 2007 connections limit issue then don't you normally get the Out of memory rather than network error that's mentioned here?

Mike

JesusWept3's picture

all i can say is it fixed our issues that we'd had before but were forced to go back to Outlook 2003, but then we had to install 2007 due to exchange 2010 deployment...we then got the same errors and our tasks would not run at all.

The performance hotfix resolved it

AndrewNolan's picture

I think I'm experiencing just the opposite effects from this hotfix that you are.  Even while I was seeing the GC errors(before installing this hotfix) all of my tasks were running just fine and everything seemed to be working normally.  I installed that hotfix last week and it fixed the GC errors, then I saw the 1000 errors against the archivetask.exe process, but it was then when my tasks started failing.  I was having to restart each task multiple times per day, which was a bigger problem than those GC errors.  I've rolled back that hot fix for now, so I'll just wait til the patch in Feb fixes all of this(hopefully!).

JesusWept3's picture

Where as we were experiencing the app 1000 crashes, archiving was running and archiving items, it just died when it was attempting to close the mapi profiles and then archive task started right back up (thanks to the EV Task Guardian), where as without the hotfix the tasks would stay running but process nothing  due to the fact it could never connect to the exchange servers.

That being said i can guarantee you that the next version of the MS hotfix will resolve the App 1000 crashes based on our testing with the dev hotfix that MS have provided, however end of february is still some time off so it could change before then theoretically

AndrewNolan's picture

Just curious.... Is the task guardian service supposed to start any failed task by default or is there some additional configuration that must be done?  I ask because it was not starting my archive task after it failed.  I had to do that manually after time.

JesusWept3's picture

The task guardian is there to start the task if it physically crashes, it will start it backup, however when its failed thats usually due to a number of retries where the task fails to connect to the exchange server etc, but it could be that it determines the task has crashed too many times thus fails the task so it wont start again until there is manual intervention from the users

RayVault's picture

We are experiencing the same problems.  We needed to stay on Outlook 2007 for our Exchange 2010 migration, however we are having to roll back to Outlook 2003 and postpone our migrations because the tasks are failing.

Any word on a fix?

JesusWept3's picture

Try the outlook 2007 performance hot fix released a couple of days ago