Solving Test-CSEXStorageConnectivity cmdlet error 50043

Share this:

When integrating Exchange Server 2013 and Skype for Business Server you may encounter the error 50043, and the complete description of the error is: “ExCreateItem exchange operation failed, code=50043, reason=#CTX#{ctx:{TraceID:”. In this Tutorial we are going over a possible solution for this error.


First of all, we assume that you started the integration already and it is on the testing phase, and for that we will be using the Test-CSEXStorageConnectivity cmdlet as shown in the image below. We are assuming that you have the proper certificate installed on the environment (for Exchange the recommendation is to use a Public Certificate, more info here:


This issue may be caused (at least on the RTM version of Skype for Business) because you don’t have the autodiscover entry on your DNS, and if that is your case there is a simple way to configure S4B to use the right location.

First of all, logged on your Exchange Server, run the following cmdlet to retrieve the name being used by the SCP (internal Autodiscover based on Active Directory):

Get-ClientAccessServer | Select Name,*uri*


Using the hostname portion of the previous cmdlet, add /autodiscover/autodiscover.svc to it and configure it on S4B using Set-CSOAuthConfiguration cmdlet using –ExchangeAutoDiscoverURL. After configuring that attribute, the output of Get-CSOAuthConfiguration should be similar to the information being displayed in the picture below.


Now, you can re-run the cmdlet to test the integration and you should be good to go.

Let us know if you find another solution for the issue on the comments area of this Tutorial.

Written by Anderson Patricio

Anderson Patricio

Anderson Patricio is a Canadian MVP in Cloud and Datacenter Management, and Office Server and Services, besides the Microsoft Award he also holds a Solutions Master (MCSM) in Exchange and several other certifications. Anderson has been contributing to the Microsoft Community with articles, tutorials, blog posts, twitter, forums and book reviews. He is a regular contributor here at,, and Anderson (Portuguese).

Related Post

Installing Skype for Business – Part 4 Time to prepare the CMS (Central Management Store) and create and publish the Topology. Solution The CMS (Central Management Store) is respons...
Fixing the error “The network path was not found” ... In situations where a new server is built to be used as witness server the administrator can get the error “The network path was not found” during the...
Exchange Server 2013 CU3 Available for download Hello there! Microsoft Exchange Team has just released the Exchange Server 2013 CU3. Cumulative Update 3 for Exchange Server 2013 resolves issues th...
Managing DAG in Exchange Server 2013 – The Series... In this series we are going over the entire process to create a DAG environment in Exchange Server 2013. At the end of the series we will have built ...