Issue adding new Exchange server

[ashks2014]

We've added 2 new Exchange servers as targets. One is fine but the archiving task for the other keeps failing. Setup process for both mailboxes were the same

1.Created EV system mailbox on the exchange server

2.Make sure VSA has full access permissions on the system mailbox

3.Add the server as a target and create the archiving task.

The failed task has 2256 and 3305 errors but the permissions for both servers and system mailboxes are the same. Tried opening the system mailbox for the failed server in EV and it won't connect.

Should we re-run the set-evpermissions script? Can't see why 1 server is fine and the other is having issues when the same things were done on both?

[AmolB]

Do you see any error or warning related to the problem Exchange server in the deployment scanner?

[AndrewB]

if you cant open the system mailbox using outlook on the EV server logged in as the vault service account then you have an issue somewhere but it's not EV itself. you can start eliminating possibilities like can you open the same mailbox using the VSA on a different computer? can you open the same mailbox using a different account on the EV server? open the system mailbox in owa, etc.

[VargheseR]

What is the version of Exchange. if it is Exch 2013, can you check the porfile and see if it is connected using RPC over HTTP with NTLM authentication. Also make sure that the VSA is part of only Domain Users group and nothing else.

[ashks2014]

You can't open the system mailbox on the EV Server with the VSA. You can open it if you log into another computer.

You can open the other system mailboxes for all other Exchange servers on the EV server without issues.

Exchange version is 2007 SP3 and EV version is 10.0.4

Tried deleting the task, deleting the system mailbox and recreating and still the same issue. Permissions for the VSA on the system mailbox and the problem Exchange server are identical to the working servers.

Still we get 2256 and 3305 errors and the task fails straight away. Symantec support can't yet find a cause either!!

Any suggestions gratefully appreciated!!

[AndrewB]

I wouldnt expect it to work until you can open the system mailbox on the EV Server as the VSA.

[ashks2014]

It can't open the system mailbox (or other mailboxes on the Exchange server) on the EV server as the VSA.

We've done nearly all the EV troubleshooting we can with Symantec and they now think it should be referred to Microsoft!!

Has anyone seen anything like this before?

[AndrewB]

maybe try something like mfcmapi or outlookspy which will give you more debugging info as to what the issue could be? so far, i dont see anything EV-related. who knows, could even be a network or firewall issue but no indicators of something EV/Symantec so you have to troubleshoot at the root.

found a couple technotes:

https://support.microsoft.com/en-us/kb/325930

How to enable MS Outlook log file generation

• MS Outlook 2007 and older

1. 1. Expand Tools > click Options.
   2. Open the Other tab.
   3. Click Advanced Options.
   4. Activate the Enable logging (troubleshooting) option.
   5. Click OK twice.
   6. Restart MS Outlook.

Important notice: once you are over with troubleshooting, disable the logging. Otherwise the log file will keep growing, and that can potentially lead to a lack of empty hard disk space. 


Log file location

• For POP3, SMTP, MAPI protocols

%temp%\Outlook Logging\Opmlog.log

[Daniel_R_]

It sounds exchange permissions (http://www.symantec.com/docs/HOWTO108664 ) or some properties not inherited in the AD account for VSA.

Best Regards

[AndrewB]

it's been quite some time. were you able to get this worked out based on the info from my posts back in July?