Hot To Enable TLS 1.2 in Windows Server 2008 or 2016 We previously had a post that handled this solutions called: How to Enable TLS 1.2 on Windows 2008 R2 This post is an update to how the enable and Mange TLS 1.2 on Windows Servers. The reason for the update is because we now use a free tool when we are managing our servers. But first some background. What you need to know about TLS 1.2 According to…https://docs.microsoft.com/en-us/windows/desktop/SecAuthN/protocols-in-tls-ssl–schannel-ssp- TLS 1.2 client and server are enabled by default. But… https://social.technet.microsoft.com/Forums/en-US/cb1a695b-a15c-4fa7-94f0-1aaa20c1279d/enabling-tls-12-on-windows-server-2012-amp-2016?forum=winserversecurity …says Turns out it is, but not enabled for SCHANNEL service Hence you MUST follow… https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/operations/manage-ssl-protocols-in-ad-fs#enable-and-disable-tls-12 Please articulate this! Say… You can enable and disable SSL 2.0 and 3.0 and TLS versions 1.0, 1.1, and 1.2 using Manage SSL Protocols in AD FS. On Windows Server 2016, to use TLS 1.2, you must explicity enable it by following instructions at… Read More »Hot To Enable TLS 1.2 in Windows Server 2008 or 2016
Problem While trying to run the OAuth provider setup in Microsoft Dynamics CRM, to configure among other things the Post-instillation setup to allow connectivity by devices and applications. I was banging my head on a problem following the instructions: Configure the OAuth provider Follow these steps to configure the OAuth provider in Microsoft Dynamics 365. Log on to the Microsoft Dynamics 365 server as an administrator. In a Windows PowerShell console window, run the following script. Windows PowerShell $ClaimsSettings = Get-CrmSetting -SettingType OAuthClaimsSettings $ClaimsSettings.Enabled = $true Set-CrmSetting -Setting $ClaimsSettings Found on this page: https://msdn.microsoft.com/en-us/library/hh699726.aspx#BKMK_WS2012R2 I was getting in the Power Shell: PS C:\Users\administrator.FSERVER4> $ClaimsSettings = Get-CrmSetting -SettingType OAuthClaimsSettings Get-CrmSetting : The term ‘Get-CrmSetting’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and… Read More »Get-CrmSetting : The term 'Get-CrmSetting' is not recognized as the name of a cmdlet
Microsoft CRM IFD The SSL certificate does not contain all UPN suffix values that exist in the enterprise – Cannot Login
Cannot Login to a Previously working Microsoft CRM IFD A previously working IFD deployment of CRM 2016 (but could be CRM 2015 or CRM 2013). About 1 year after you set the system up, you start receiving: An error has occurred. Try this action again. If the problem continues, check the Microsoft Dynamics CRM Community for solutions or contact your organization’s Microsoft Dynamics CRM Administrator. Finally, you can contact Microsoft Support. When researching this error, we suspected what it was, and related to an article we covered here: http://www.interactivewebs.com/blog/index.php/crm-2013/microsoft-crm-2013-or-2015-event-id-1309-adfs-ifd-resolution/ However we never found and EVENT ID 1309 or anything close to that in our logs. The closest error we found (and we are not even certain that it was pointing as a result fo this problem) was the error: EVENT ID 415 The SSL certificate does not contain all UPN suffix values that exist in the enterprise. Users with UPN suffix values not… Read More »Microsoft CRM IFD The SSL certificate does not contain all UPN suffix values that exist in the enterprise – Cannot Login
CRM in-line search fails with SQL error After upgrading Microsoft CRM from earlier versions we found that the global search function when enabled failed to return any results, and once the index for the global search had run over a 24-hour period, the in-line search function for any entity would cause a crash and SQL error message to be displayed on page. The problem In our particular instance this CRM environment had been upgraded from much earlier versions of CRM and included an attempt to solve some upgrade issues by dropping indexes. Initially our thoughts were that the dropping of the indexes were responsible for the problems. However it appears retrospectively that was a fragmentation of indexes that cause the issue. I cannot be exactly sure why the maintenance procedure that is run on the SQL Server did not rebuild and reorganise the indexes sufficiently that the global social function.… Read More »Microsoft CRM global search fails causing in-line search SQL error
Changing your password in ZenDesk may affect your Microsoft CRM integration if you are to upgrade or change the password that you utilise in your ZenDesk system for the account that has been set to synchronise data with the Microsoft CRM platform, you will notice that the synchronisation may not function correctly or may only perform a one-way synchronisation. You will remember from the instructions that you likely followed in your initial configuration: http://www.interactivewebs.com/blog/index.php/zendesk/zendesk-to-crm-2015-integration/ that part of these configuration settings is to set up your password and username in the SETTINGS / ZD Personal Settings – area of your Microsoft CRM system. Below is an extract from the vendor’s configuration portal found here Step 2: Setting up new security roles The Zendesk integration introduces two new security roles to Microsoft Dynamics CRM that must be assigned before you can proceed to the next step: Zendesk – Read configuration settings – grants… Read More »ZenDesk to Microsoft CRM integration password change
Microsoft.Crm.CrmException: Database having version 184.108.40.206 is not supported for upgraded Microsoft.Crm.CrmException: Database having version 220.127.116.11 is not supported for upgraded.
When upgrading from CRM 2013 to CRM 2015 you get an error: Microsoft.Crm.CrmException: Database having version 18.104.22.168 is not supported for upgraded. Cause: This is usually because there is already a database that exists with the same ID. You will need to delete that Organisation in CRM deployment manager before upgrading the new organisation from the same name.
Microsoft CRM IFD Event ID 364 and 111 We got the ADFS login screen as expected, but on trying to login we received an error: Activity ID: 00000000-0000-0000-0400-0080020000f4 Relying party: CRM IFD Relying Party Associate with two errors in the ADFS Event Log. Event ID: 111 Additional Data Exception details: System.ArgumentException: ID4216: The ClaimType ‘* Name’ must be of format ‘namespace’/’name’.Parameter name: claimTypeat Microsoft.IdentityModel.Threading.AsyncResult.End(IAsyncResult result)at Microsoft.IdentityModel.Threading.TypedAsyncResult`1.End(IAsyncResult result)at Microsoft.IdentityModel.SecurityTokenService.SecurityTokenService.EndIssue(IAsyncResult result)at Microsoft.IdentityServer.Web.WSTrust.SecurityTokenServiceManager.Issue(RequestSecurityToken request, IList`1& identityClaimSet) Event ID: 364 Encountered error during federation passive request. Additional Data Protocol Name: wsfed Relying Party: https://crm2016.iwebscrm16.com:444/ Exception details: Microsoft.IdentityServer.RequestFailedException: MSIS7012: An error occurred while processing the request. Contact your administrator for details. —> System.ArgumentException: ID4216: The ClaimType ‘* Name’ must be of format ‘namespace’/’name’.Parameter name: claimTypeat Microsoft.IdentityModel.Threading.AsyncResult.End(IAsyncResult result)at Microsoft.IdentityModel.Threading.TypedAsyncResult`1.End(IAsyncResult result)at Microsoft.IdentityModel.SecurityTokenService.SecurityTokenService.EndIssue(IAsyncResult result)at Microsoft.IdentityServer.Web.WSTrust.SecurityTokenServiceManager.Issue(RequestSecurityToken request, IList`1& identityClaimSet)at Microsoft.IdentityServer.Web.Protocols.PassiveProtocolHandler.SubmitRequest(MSISRequestSecurityToken request, IList`1& identityClaimCollection)at Microsoft.IdentityServer.Web.Protocols.PassiveProtocolHandler.RequestBearerToken(MSISRequestSecurityToken signInRequest, Uri& replyTo, IList`1& identityClaimCollection)at Microsoft.IdentityServer.Web.Protocols.WSFederation.WSFederationProtocolHandler.RequestBearerToken(MSISSignInRequestMessage signInRequest, SecurityTokenElement onBehalfOf, SecurityToken primaryAuthToken, SecurityToken deviceSecurityToken, String desiredTokenType, WrappedHttpListenerContext httpContext, Boolean isKmsiRequested, Boolean… Read More »Microsoft CRM IFD Event 364 and 111 in ADFS
How to Update SSL Certificates for AD FS 3.0 in CRM IFD Introduction Microsoft Dynamics CRM can be configured to use SSL (Secure Sockets Layer). For this to work, an SSL certificate is required. Certificates can be purchased from certificate providers and will expire after a certain period of time. Once this time has elapsed, Microsoft Dynamics CRM will no longer work until the certificate is updated. This article describes the process to update the certificate for Microsoft Dynamics CRM Installing the new certificate You will need to import your certificate into the local certificate store on each CRM server that uses web services, and the AD FS server if claims-based authentication is enabled. Instructions on how to import a certificate can be obtained from your certificate provider. Symantec (Verisign, Thawte, GeoTrust) Comodo SSL GlobalSign Go Daddy DigiCert Note: Problems may occur if you do not remove the old certificate.… Read More »Update ADFS SSL Certificates Microsoft CRM 2013 2015 and 2016 IFD
When attempting to login to an IFD deployment of CRM 2013 or 2015 you receive an event Error: 1309 looking like this: Event code: 3005 Event message: An unhandled exception has occurred. Event time: 7/01/2016 12:08:14 AM Event time (UTC): 6/01/2016 1:08:14 PM Event ID: 0daeff15a8f24e939623db80c40522d5 Event sequence: 3 Event occurrence: 2 Event detail code: 0 Application information: Application domain: /LM/W3SVC/2/ROOT-1-130965592186041416 Trust level: Full Application Virtual Path: / Application Path: C:\Program Files\Microsoft Dynamics CRM\CRMWeb\ Machine name: VSERVER07 Process information: Process ID: 2300 Process name: w3wp.exe Account name: NT AUTHORITY\NETWORK SERVICE Exception information: Exception type: SecurityTokenException Exception message: ID4175: The issuer of the security token was not recognized by the IssuerNameRegistry. To accept security tokens from this issuer, configure the IssuerNameRegistry to return a valid name for this issuer. at Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.CreateClaims(SamlSecurityToken samlSecurityToken) at Microsoft.IdentityModel.Tokens.Saml11.Saml11SecurityTokenHandler.ValidateToken(SecurityToken token) at Microsoft.IdentityModel.Tokens.SecurityTokenHandlerCollection.ValidateToken(SecurityToken token) at Microsoft.IdentityModel.Web.TokenReceiver.AuthenticateToken(SecurityToken token, Boolean ensureBearerToken, String endpointUri) at Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.SignInWithResponseMessage(HttpRequest request) at Microsoft.IdentityModel.Web.WSFederationAuthenticationModule.OnAuthenticateRequest(Object sender,… Read More »Microsoft CRM 2013 or 2015 Event ID 1309 ADFS IFD Resolution
Installing the Zendesk to CRM 2015 or Dynamics 365 integration These instruction have been updated from the Zendesk instructions provided here: https://support.zendesk.com/hc/en-us/articles/203660156-Zendesk-for-Microsoft-Dynamics-CRM-Part-1-Installing-the-Zendesk-for-Microsoft-Dynamics-CRM-as-a-module-in-Microsoft-Dynamics-CRM They use a combination of the original processes that Zendesk have created originally for CRM 2011 and that worked on Pre SP1 versions of CRM 2013. The packages referenced have been update by InteractiveWebs to work with CRM 2013 Post SP1 and CRM 2015 (technically all versions but we recommend post SP 0.1) Instillation of the CRM Solution Install the CRM Managed Solution as you would any other CRM solution. Download the managed solution for CRM 2015 https://www.dropbox.com/s/0rhlgnxcwz9s4yh/ZendeskDynamicsCRMConnector_2_0_0_2_managed.zip?dl=0 In CRM Navigate to SETTINGS / SOLUTIONS Click on Import Chose File Select the Managed CRM package – Click Next Click Next Leave the Enable any SDK ticked, and click on Import Allow the Import to take place Click on Close On Completion, Click “Publish… Read More »Zendesk to CRM 2015 and Microsoft Dynamics 365 Integration
While importing a solution to CRM 2011, CRM 2013, or CRM 2015 you receive an error Fields that are not valid were specified for the entity The Cause The cause of this is likely that one of the attributes that you are importing (from a dev environment) already exists in the CRM instance, but with a different attribute. For Example: In your Live Environment Within Accounts, you create a new attribute called “Friendly Cusomter” and mark it TEXT Publish and all is well and good. In you Dev Environment Within Accounts, you create a new attribute called “Friendly Customer” and make it a PICK LIST in other words, the same name for the attribute, but a different kind of field. Then try to export from DEV and import to LIVE. You get the error. The solution You have to remove the conflicting fields from the destination (live… Read More »Microsoft CRM Solution Import Fields that are not valid were specified for the entity
How to Delete a Managed Solution in CRM 2013 or CRM 2015 Sometimes when you try to delete a managed Solution, there is an error message about the dependancies of the solution being in use. When you download the log file, you see some typical Microsoft Crap that really does nothing to help you. The only thing it does is to tell you that you can’t delete the component because it is being used in this case by two other components. Now the hard part is finding the components that are using it. Finding the Referenced Dependencies CRM 2015 Components 1. Work out the Solution Name. Navigate to CRM / Settings / Solutions – and read the exact Name of the Solution to be deleted. In this case it was “ZendeskCRM2011Connector“ 2. Login to your CRM Server and open the SQL database that matches the Organisation name being… Read More »CRM 2015 2013 find Dependencies for Managed Solution
CRM 2015 and CRM 2016 IFD will Automatically Logout the user with a Message: Your session in Microsoft Dynamics CRM is about to expire. To continue working, you must sin in again. By Default this setting is 60 minutes, and the message will pop up around 20 minutes before logout. Any unsaved changes will be lost as your session ends. The Fix To extend the automatic logout time in CRM 2015, we must extend the time set in ADFS 3.0 using the PowerShell command. First we need to know the name that was used to set up the Relying Party Trust in ADFS. 1. Open Server Manager and from the Tools menu select ADFS Management 2. in AD FS management, open Relying Party Trusts and find the Display name for the CRM IFD Relying Party Trust In this case, we have called the Relying Party Trust – “CRM IFD… Read More »CRM 2015 Extend Auto Logout Time in IFD