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 126.96.36.199 is not supported for upgraded Microsoft.Crm.CrmException: Database having version 188.8.131.52 is not supported for upgraded.
When upgrading from CRM 2013 to CRM 2015 you get an error: Microsoft.Crm.CrmException: Database having version 184.108.40.206 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.
CRM 2016 Import Upgrade from CRM 2015 Failure: Timeout expired On attempting to upgrade a Microsoft CRM Dynamics 2015 Database to CRM 2016 (without service pack) you receive a Failure: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.. This happens at the System Check stage. There are a bunch of suggestions online from earlier releases of CRM like 4.0 etc suggesting that you may need to change the timeout settings on the settings with some DWord changes in the registry. In this case it is not the cause. Cause Microsoft has again released an initial version of their software with some significant bugs. The biggest of these being that you cannot import your CRM 2015 database to upgrade to CRM 2016 if it has a Full Text Catalogue. Something that is likely if you have been using the improved searching functions of… Read More »CRM 2016 Import Upgrade from CRM 2015 Failure: Timeout expired
How to Set Up Microsoft CRM 2016 IFD on Windows 2012 R2 Server We already have a popular post for the configuration of IFD setup with CRM 2015, CRM 2013, CRM 2011. Now we are updating this post to support CRM 2016. Microsoft have a compatibility listing for CRM 2016 here: https://support.microsoft.com/en-us/kb/3124955 The Development Setup Once again we are running this configuration as a test environment for development. As such we will be running, we are running the server on a Hyper V server. A single VM machine, that is running a fully patched version of: Windows 2012 R2 SP2 64 Bit – (MSDN File: en_windows_server_2012_r2_x64_dvd_2707946) SQL 2014 R2 64 Bit – SQL Server 2014 Standard Edition x64 – (MSDN File: en_sql_server_2014_standard_edition_x64_dvd_3932034) – Patched to SP2 Microsoft Dynamics CRM Server 2016 – en_microsoft_dynamics_crm_server_2016_x86_x64_dvd_7171743 NOTE: The Domain we have used for setup with this dev server is: iwebscrm16.com You can substitute your domain in place throughout… Read More »How to Set Up Microsoft CRM 2016 IFD on Windows 2012 R2 Server
We already have a popular post for the configuration of IFD setup with CRM 2011, and recently we updated this blog to support CRM 2015 here: http://www.interactivewebs.com/blog/index.php/crm/how-to-set-up-crm-2015-ifd-on-windows-2012-and-adfs-3-0/ Many of you may find that better for setting up CRM 2013 than this blog, as the data is mostly exactly the same as this blog, but some of the order of things is better described. Upgrading from CRM 2011 to CRM 2013 and need help? InteractiveWebs offer professional Microsoft CRM Upgrade Services and Support. The Existing Setup Because this is a test environment, we are running the server on a Hyper V server. A single VM machine, that is running a fully patched version of: Windows 2012 R2 SP2 64 Bit – (MSDN File: en_windows_server_2012_r2_x64_dvd_2707946) SQL 2012 R2 64 Bit – (MSDN File: en_sql_server_2012_standard_edition_with_service_pack_2_x64_dvd_4351706) Microsoft CRM 2013 64 Bit – (MSDN File: en_microsoft_dynamics_crm_server_2013_sp1_x86_and_x64_4330464) How to Install CRM 2013 We pretty much followed a combination of these… Read More »CRM 2013 IFD Setup with ADFS 3.0 on Windows 2012 R2 Hosted Setup
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
Upgrading from CRM 2011 to CRM 2013 you cannot restore SQL on a Non Enterprise Server An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)Database ‘Org_MSCRM’ cannot be started in this edition of SQL Server because it contains a partition function ‘AuditPFN’. Only Enterprise edition of SQL Server supports partitioning. Database ‘Org_MSCRM’ cannot be started because some of the database functionality is not available in the current edition of SQL Server. (Microsoft SQL Server, Error: 905) CAUSE When Microsoft Dynamics CRM 2011 is installed using a Microsoft SQL Server Enterprise edition, a partition is created for the auditing functionality of Dynamics CRM 2011. The AuditBase table uses partitioning which is only available for Microsoft SQL Server Enterprise.RESOLUTIONUse the following Steps and Script to remove the partitioning. The following script recreates all the indexes on the Primary partition and then drops the partition.Be sure to have a database backup… Read More »Microsoft CRM Restore Database Failed Only Enterprise edition of SQL Server supports partitioning
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
The message cannot be sent to all selected recipients. When running a workflow / process in Microsoft CRM, you receive a message that looks like this: The e-mail address for one or more recipients is either blank or not a valid e-mail address The Cause This error message is a little misleading as it points to an email address problem. As the title of the error suggests, the problem could be from: 1. A blank email address. 2. An email address with an error, such as a “.” at the end of it: firstname.lastname@example.org. 3. The more likely one is that the contact or account record associated with the flow has a setting to E-mail Do Not Allow. This setting will prevent any workflows in CRM from running and sending email messages. The Solution The fix is easy… just change the setting back to allow. Then save the associated record.… Read More »The e-mail address for one or more recipients is either blank or not a valid e-mail address