Enterprise Vault Archive Task Fails To Start MS Exchange 2013

[Ravi_Bhandari]

Hi, I'm attempting to migrate mailboxes to a new exchange server which happens to be version Exchange 2013.

However all my attempts to get the archive task to work with this new server end in "Could not be started due to Startup errors", Event 2256.

My question is "What can I do to diagnose the problem?"

I had to manually create a mail profile for the system mailbox as the Exchange 2013 autodiscovery thingy didn't work for me.

I had to manually configure the mail account to connect using Outlook Anywhere and had to provide the proxy server name.

And I can connect to the Exchange server using this same profile and the MS Outlook 2007 SP3 with Hot fix installed on the server.

I can send mail successfully using this system mailbox account in outlook.

I have run the EVThrottling and EV Permission powershell scripts and given the send as permissions.

I'm not sure what else it is I need to do and would be extremely grateful for any insight or advice as to what my next step should be.

[GabeV]

Hi Ravi,

You can restart the archiving task while collecting a dtrace for the ArchiveTask. Follow this technote (Command Line section):

http://www.symantec.com/docs/TECH38122

In addition, take a look at this technote:

Enterprise Vault Event 2256 Errors - Troubleshooting Digest
http://www.symantec.com/docs/HOWTO95555

I hope this helps.

[Ravi_Bhandari]

Thanks for that, there were a couple of issues in the dtrace log,

one involves the global catalog

DirectoryHelper::GetDcName() - Unable to contact GC; trying nearest DC

Hopefully this will resolve it.

http://www.symantec.com/business/support/index?page=content&id=TECH73314

The other was to do with autodiscover

{EVExchangeWebServicesProxy.UpdateConnectionPointDetails} exception occurred: The remote server returned an error: (400) Bad Request.

I'm not sure what to do about that, apart from the url it's attempting has one too many dots "." after the mailbox name.

{ExchangeAutodiscover.GetAutodiscoverResponseForUrl} Attempting to autodiscover [EVSYSMBX-EXCHSVR2@NPL.CO.UK] with redirect url [https://autodiscover.<domain>:443/Autodiscover/<mailbox>..<domain>/Autodiscover.xml]

[AndrewB]

are you using the FQDN of your exchange 2013 server when setting up the task?

[Ravi_Bhandari]

How do you mean? I've tried using the long random proxy server name in the domain properties.

[AndrewB]

when you add the new exchange 2013 server as a target in the EV admin console

[Ravi_Bhandari]

Yes the FQDN is what I used and I can select the system mailbox on the new exchange server.

[Ravi_Bhandari]

I can see this in the dtrace

{ExchangeConnectionPointInformation::IsValid:#65} Invalid Exchange connection point information, proxy server name [], certificate principal name [] and authentication [0x1]