[BUG] Unable to add new Connections.

[mlnc21]

Describe the bug
Unable to add new Connections.

To Reproduce
Connection Manager

• select a Connection File
• New connection
• Microsoft Login Control
• (use default configuration)
• Open Microsoft Login Control
• Deployment Type: Office 365
• Login
• Enter Email and Password
• Accept OAuth
• Error -> Cant connect to Microsoft Dataverse -O365.

Log:

Source : Not Provided
Method : Not Provided
Date : 06.06.2024
Time : 14:33:04
Error : A Dataverse server name is required.
Parametername: CrmServerName
Stack Trace : Not Provided

Source : Microsoft.Xrm.Tooling.Connector
Method : MoveNext
Date : 06.06.2024
Time : 14:34:34
Error : Methode nicht gefunden: "Void Microsoft.Xrm.Sdk.Discovery.OrganizationDetail.set_SchemaType(System.String)".
Stack Trace : bei Microsoft.Xrm.Tooling.Connector.CrmWebSvc.d__204.MoveNext()
bei System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.Start[TStateMachine](TStateMachine& stateMachine) bei Microsoft.Xrm.Tooling.Connector.CrmWebSvc.QueryGlobalDiscovery(String authToken, Uri discoveryServiceUri, CrmLogEntry logSink) bei Microsoft.Xrm.Tooling.Connector.CrmWebSvc.DiscoverGlobalOrganizations(Uri discoveryServiceUri, ClientCredentials clientCredentials, X509Certificate2 loginCertificate, UserIdentifier user, String clientId, Uri redirectUri, PromptBehavior promptBehavior, String tokenCachePath, Boolean isOnPrem, String authority, CrmLogEntry logSink, Boolean useGlobalDisco, Boolean useDefaultCreds) bei Microsoft.Xrm.Tooling.Connector.CrmWebSvc.DiscoverOrganizations(Uri discoveryServiceUri, ClientCredentials clientCredentials, UserIdentifier user, String clientId, Uri redirectUri, PromptBehavior promptBehavior, String tokenCachePath, Boolean isOnPrem, String authority, CrmLogEntry logSink, Boolean useGlobalDisco, Boolean useDefaultCreds) bei Microsoft.Xrm.Tooling.CrmConnectControl.CrmConnectionManager.QueryOAuthDiscoveryServer(Uri discoServer, ClientCredentials liveCreds, UserIdentifier user, String clientId, Uri redirectUri, PromptBehavior promptBehavior, String tokenCachePath, Boolean useGlobalDisco) bei Microsoft.Xrm.Tooling.CrmConnectControl.CrmConnectionManager.QueryOnlineServerList(ObservableCollection1 svrs, OrganizationDetailCollection col, ClientCredentials liveCreds, Uri trimToDiscoveryUri, Uri globalDiscoUriToUse)
bei Microsoft.Xrm.Tooling.CrmConnectControl.CrmConnectionManager.FindCrmOnlineDiscoveryServer(ClientCredentials liveCreds)
bei Microsoft.Xrm.Tooling.CrmConnectControl.CrmConnectionManager.ValidateServerConnection(CrmOrgByServer selectedOrg)

Screenshots

Desktop (please complete the following information):

[MscrmTools]

It seems you are using beta version of connection controls.
Please revert to stable ones, it should work

[mlnc21]

i changed back, but same Issue.

/////Log
Source : Microsoft.Xrm.Tooling.Connector
Method : MoveNext
Date : 28.06.2024
Time : 15:10:45
Error : Methode nicht gefunden: "Void Microsoft.Xrm.Sdk.Discovery.OrganizationDetail.set_SchemaType(System.String)".
Stack Trace : bei Microsoft.Xrm.Tooling.Connector.CrmWebSvc.d__204.MoveNext()
bei System.Runtime.CompilerServices.AsyncTaskMethodBuilder1.Start[TStateMachine](TStateMachine& stateMachine) bei Microsoft.Xrm.Tooling.Connector.CrmWebSvc.QueryGlobalDiscovery(String authToken, Uri discoveryServiceUri, CrmLogEntry logSink) bei Microsoft.Xrm.Tooling.Connector.CrmWebSvc.DiscoverGlobalOrganizations(Uri discoveryServiceUri, ClientCredentials clientCredentials, X509Certificate2 loginCertificate, UserIdentifier user, String clientId, Uri redirectUri, PromptBehavior promptBehavior, String tokenCachePath, Boolean isOnPrem, String authority, CrmLogEntry logSink, Boolean useGlobalDisco, Boolean useDefaultCreds) bei Microsoft.Xrm.Tooling.Connector.CrmWebSvc.DiscoverOrganizations(Uri discoveryServiceUri, ClientCredentials clientCredentials, UserIdentifier user, String clientId, Uri redirectUri, PromptBehavior promptBehavior, String tokenCachePath, Boolean isOnPrem, String authority, CrmLogEntry logSink, Boolean useGlobalDisco, Boolean useDefaultCreds) bei Microsoft.Xrm.Tooling.CrmConnectControl.CrmConnectionManager.QueryOAuthDiscoveryServer(Uri discoServer, ClientCredentials liveCreds, UserIdentifier user, String clientId, Uri redirectUri, PromptBehavior promptBehavior, String tokenCachePath, Boolean useGlobalDisco) bei Microsoft.Xrm.Tooling.CrmConnectControl.CrmConnectionManager.QueryOnlineServerList(ObservableCollection1 svrs, OrganizationDetailCollection col, ClientCredentials liveCreds, Uri trimToDiscoveryUri, Uri globalDiscoUriToUse)
bei Microsoft.Xrm.Tooling.CrmConnectControl.CrmConnectionManager.FindCrmOnlineDiscoveryServer(ClientCredentials liveCreds)
bei Microsoft.Xrm.Tooling.CrmConnectControl.CrmConnectionManager.ValidateServerConnection(CrmOrgByServer selectedOrg)

[MscrmTools]

There must be some remaining beta dll somewhere... You shouldn't have this message anymore

[aprilkae]

I am also getting this error message. @mlnc21 were you able to get around this? This was a fresh install for me, so there should not be any beta dll's anywhere.

[MscrmTools]

Even with a fresh install, if your computer already had XrmToolBox installed and you did not change the storage path, it will reuse lot of files from previous installation

[Romaric-Nguena]

@aprilkae @mlnc21 I had the same problem and to solve it I had to download a new version of XrmToolBox which I deployed in a different directory to the old version which was already on my PC.
I didn't lose my connections and installed tools.
I hope this solution helps.

[spearruleina]

@aprilkae @mlnc21 I had the same problem and to solve it I had to download a new version of XrmToolBox which I deployed in a different directory to the old version which was already on my PC. I didn't lose my connections and installed tools. I hope this solution helps.

Thank you so much, this exactly solved my problem. And thanks to OP @mlnc21 for creating the issue so i could discover it (and feel less alone). I much more quickly got back up on my feet thanks to your helps. : )

[mlnc21]

@aprilkae and @Romaric-Nguena and @spearruleina
Thank you for your Inputs :-).
sometimes it works and sometimes it doesn't. the connection UI + functions should be revised.
I get a login error so often. also that when I select M365 login it requires a password in the UI, which I can only enter when the MS dialog appears.
also you should check that you can use the DisplayName default value of the selected Dynamics environment as the display name.

[MscrmTools]

When using Microsoft Login Control, I have no control at all on how it behaves...