EMC SourceOne – Exchange 2016 “system call failed”

“System call failed.  Unknown error”

“CoExExchProvider::LogonDS: Cannot log into mailbox”

If after you migrated the SourceOne service account and journal mailbox to Exchange 2016, and your jobs keep failing you may have a similar issue to me.

During the process of migrating the last two mailboxes (Both SourceOne) to the new environment I was getting permission errors throw in the logs while attempting to run the journaling jobs. This was because SourceOne DOES NOT SUPPORT HTTPS. 

In order to get SourceOne working properly on exchange 2016 if you are forcing HTTPS you need to enable RPC over http using the KB articles below.


Each step must be done on each worker node after migration has completed:

  1. Log into worker node using SourceOne Service account
  2. Control Panel > Mail (32-Bit) > Delete old mail profile > Create new profile (Make sure to uncheck Cached exchange mode)
  3. Regedit.exe navigate to “HKEY_CURRENT_USER\Software\Microsoft\Exchange”
  4. Create new DWORD “MapiHttpDisabled”
  5. Set value to “1”
  6. Restart Outlook client

There is an KB from Microsoft that shows you how to remove this setting, so i did not add it because it may have been confusing. But the KB is 2937684.

 

EMC SourceOne 7.2 SP6- Cannot connect to journal mailbox in a mixed Microsoft Exchange scenario (2010 and 2016)

So this has bitten me for the past couple of weeks we would try to fail over our last two mailboxes from exchange 2010 to exchange 2016. One Journal and One Service account. Come to find out (No thanks to EMC SourceOne install documentation) That the service account needs to be the last mailbox to move.

Take a look at this bug report: https://community.emc.com/docs/DOC-60862

If you are going to run in a mixed environment for a long time follow the steps below in the article and always make sure you migrate your SourceOne Service account last!

With 2010/2016 co-existence, there are certain requirements for it to work.    
    
    These requirements are:-    
    
    1) Service Account mailbox needs to be always on the lower exchange version.It should be the last mailbox to move to 2016. Exchange 2010 should be configured with RPC over https.    
    2) Exchange 2016 should have RPC over https enabled. By default Exchange 2016 has MAPI over https which is not supported by SourceOne. Customer will have to enable RPC over https and configure it correctly    
    3) All ES1 servers should have only Outlook 2010 SP2 + KB2878254. No other HF or update. Updates for Outlook should be disabled.    
    4) Profile needs to be configured on Outlook to have Outlook using RPC over https with the proxy server pointing to the 2016 server. For these changes you will need to configure AutoDiscovery.    
    5) Set the correct permissions mailbox on 2016    
    
    Without these 5 criteria, they will not be able to communicate between 2 versions of exchange.       

EMC ESRSve admin password reset (VXRail Edition)

Resetting a password on a ESRS appliance is pretty straight forward. But there is a pesky error that can pop up from time to time with ESRS appliances that get deployed via the VXRail deployment.

The normal esrs admin password reset goes something like this:


ESRSapplicance:~ # cd /opt/esrs/webuimgmt-util/
ESRSapplicance:~ # ./passwordAdmin.sh

Normally this would then ask you for a new password for the admin account associated with your ESRS appliance.

But what is the error you might ask? Well it happens in lieu of asking for a new password.

“User Configuration File Missing. Please contact ESRS Support”

In order to get around this error it is a simple command you must run before starting the ./passwordadmin.sh script:


ESRSapplicance:~ # echo admin > /etc/esrsadmin.conf
ESRSapplicance:~ # cd /opt/esrs/webuimgmt-util/
ESRSapplicance:~ # ./passwordAdmin.sh

And thats it! Have fun with ESRS and let me know it this article helped you!