Error occurred while registering the connector

Brass Contributor



We're trying to setup UP, 


Server meets all the requirements listed on the MS Docs (Win 2016+, .NET 4.7.2 etc) 


Upon logging in and creating a new name to register the Connector we get: 


2021-01-19 15_16_48-Window.png


In the event viewer we are shown: 


2021-01-19 15_24_51-Window.png


Searched and searched, no real success.  


The full error in event viewer reads: 

Exception occurred while initializing the Proxy Service: System.TypeInitializationException: The type initializer for 'ProxyLibrary.Constants' threw an exception. ---> System.DirectoryServices.ActiveDirectory.ActiveDirectoryOperationException: A local error has occurred. ---> System.DirectoryServices.DirectoryServicesCOMException: A local error has occurred. at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_AdsObject() at System.DirectoryServices.PropertyValueCollection.PopulateList() at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName) at System.DirectoryServices.PropertyCollection.get_Item(String propertyName) at System.DirectoryServices.ActiveDirectory.PropertyManager.GetPropertyValue(DirectoryContext context, DirectoryEntry directoryEntry, String propertyName) --- End of inner exception stack trace --- at System.DirectoryServices.ActiveDirectory.PropertyManager.GetPropertyValue(DirectoryContext context, DirectoryEntry directoryEntry, String propertyName) at System.DirectoryServices.ActiveDirectory.Domain.GetDomain(DirectoryContext context) at ProxyLibrary.Constants.IsAdJoined() at ProxyLibrary.Constants.CheckForImpersonation(JObject jsonConfig) at ProxyLibrary.Constants..cctor() --- End of inner exception stack trace --- at ProxyService.PrintProxyService..ctor()
Any help greatly appreciated.  

9 Replies
Which version of the connector are you trying to register?


Installed version: 1.34.7683.23618  

@Adam Weldon-Ming 

Looking into it.


  1. Is your connector joined to an AD domain or not?
  2. Are you planning to enable the hybrid AD/AAD config mentioned here?


No worries - thanks for your input. 


  1. The UP connecter is being installed onto a Local DC, 
    1. The Local DC is where the printers are also installed 
  2. Local site has a Express Route to Azure 
    1. Azure also has a DC with AD Connect On - Azure DC and Local on-prem local DC replicate
  3. Environment is in Hybrid AD/AAD 

The article you've posted throws some suspicion around Step 2 - Curious if I should follow instruction in Step 2

@Adam Weldon-Ming 


Thank you for the info! You've actually helped us uncover a bug. We are fixing it and will release a new connector version ASAP. 


Regarding your question, if I understand correctly, you're asking about "Step 2 - Install Application Proxy". I'll verify and get back to you.

Thanks @Rani_Abdellatif 


Look forward to the new release. Once released I will mark solved. 



@Adam Weldon-Ming 


Thanks. We're working on releasing the new connector version ASAP.


Regarding your about "Step 2 - Install Application Proxy":

Please use the dsregcmd to check whether the PC is Hybrid AD Joined. If it is, you can skip step 2.

Also, installing App Proxy when it's not needed doesn't negatively affect the setup.

best response confirmed by Adam Weldon-Ming (Brass Contributor)

@Adam Weldon-Ming we have a canary/pre-release version of Connector with a few fixes, including this crash. Can you try upgrading to it via and trying to run the Connector again? Please let us know if you see any issues or if it ends up resolving the issue you were seeing earlier.



@keeron @Rani_Abdellatif 


Hi guys,


This has worked, new version did not crash with the error form before - we will continue our setup this side - Many thanks for your input and prompt resolution.