Posts

Showing posts from January, 2018

Updating CRM 2016 TO Dynamics 365 Fails with 'DUPLICATE KEY' Error

This week I tried to apply the Dynamics 365 update to a couple of CRM organisations that were running on v8.0.1.79. This failed and in the log file I found the following error: dbo.SolutionBase' with unique index 'ndx_UniqueName'. The duplicate key value is (SnapshotSolution80) Just to explain what I believe has happened here, I think that someone at Microsoft created a solution snapshot in V8.0.1.79 with the unique name SnapshotSolution80. This Snapshot Solution is removed from the DB when you apply update V8.1.0.359. Later, in V8.2.0.749 the same unique name is used on a different solution snapshot and when the CRM tries to insert this record into SQL it throws the error mentioned above because you never applied update V8.0.1.359 to remove the duplicate key. How to fix it 1 Restore DB to a CRM server running CRM V8.1.0.359 2 Attempt to apply Update 8.1.0.359 to CRM DB. If it fails with the error: Cannot insert duplicate key row in object 'dbo.SolutionBas

Unable to Install profiler through Plugin Registration Tool Dynamics365

I was having an issue trying to install profiler through Plugin Registration Tool. I was able do all actions on plugins from registration to disabling them.  I was using Microsoft Dynamics® CRM 2016/D365 (8.2.2.112) (DB 8.2.2.112) On-premises, and Registration tool version is 8.2.1.8676 64bit. What I have tried: I tried tp install profiler in a Dev environment, and a sandbox environment this did not work. I tried to install it on the DEV instance running plugins and still  the same issue. NOTE: This issue was happening evening though l was a system administrator and deployment admin. Error Log: Unhandled Exception: System.Exception: Solution Import Failed: 31 Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: Access is denied.Detail: <OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="ht

WorkFlows Failing After Upgrading CRM to Dynamics365 (On-Premise)

Issue After Upgrading Dynamics CRM 2016 on prem to Dynamics365 on Prem you may notice workflows may suddenly stop completing with an error: Error Attenetion Needed if you look in details on the workflow/Backend server event viewer you will see the below error message. Out of memory issues After Upgrade Unhandled Exception: System.TypeInitializationException: The type initializer for 'Microsoft.Crm.ErrorCodes' threw an exception.    at Microsoft.Crm.ErrorCodes.Out of memory issue in Dynamics365GetErrorType(Int32 errorCode)    at Microsoft.Crm.Admin.AdminService.CrmDatacenterService.ClassifyErrorCode(Int32 errorCode)    at Microsoft.Crm.Asynchronous.JobResultCodeServiceLevelAgreementResultStrategy.MarkFailedResult(IGenericHandlerResult asyncResult, ITelemetryOperation operation)    at Microsoft.Crm.Asynchronous.AsyncEventExecutionManager`2.ExecuteHandler(IAsyncEventHandlerFactory handlerFactory)    at Microsoft.Crm.Asynchronous.PoolHandler.ProcessAsyncEvent(IAsyncEventExec

So Why Microsoft Dynamics 365?

Microsoft Dynamics 365 is an easy to use, web-based, complete suite of business applications software. Microsoft Dynamics 365 offers many advantages to an organisation looking to improve their results, especially in the areas of sales and business intelligence. Using Microsoft Dynamics 365, you can put your customers first All your teams and departments can use the same information - wherever they are based Every team member gets and easy to use set of tools to access all the data Microsoft Dynamics 365 is more than just a simple sales tool.  As well as providing functionality to increase sales while maintaining (or lowering) cost of sales, Microsoft Dynamics 365 helps you with customer service and helps manage field service people (who look after clients and equipment at their premises and elsewhere), and provides project service automation for organisations who help people by providing services via projects.    The Question Now is Cloud or on Premise? Cloud? It works ev

Dynamics 365 - Dashboards – You do not have enough privileges to access the Microsoft Dynamics CRM object or perform the requested operation.

I have of recent noticed this error when users trying to access dashboard data that has been shared with them. Error: “You do not have enough privileges to access the Microsoft Dynamics CRM object or perform the requested operation” Solution : Make sure all personal views are shared Make sure all teams/users have the correct access to entities and/or data Make sure all teams/users have been given access to the dashboards (…) Make sure all the individual charts in the dashboards are shared. (Advanced find, entity, charts section, share. Change chart, share..)

CRM 2016 integration with SharePoint 2016 On Premise (401) Unauthorized Error

We spent a lot of time while we encountered  the below exception when we were integrating CRM with SharePoint. Exception: System.Net.WebException: The remote server returned an error: (401) Unauthorized. Environment details: CRM 2016 on-premise with Claims authentication enabled. SharePoint Server On-premise with Claims authentication enabled. User Account using to set up is Admin on both the CRM and Sharepoint servers. Reason & Fix: Fix suggested in the following MSDN Forum worked for us. ( https://social.microsoft.com/Forums/en-US/9d3ebcf2-daf4-4564-a992-67a038aef9c5/crm-and-sharepoint-integration-401-unauthorized-when-setting-trusted-security-token-issuer?forum=crm) It seems there is a known issue/bug with CRM 2016 that doesn’t allow this to work if you try using https in the MetadataEndPoint. To get this working, you will have to temporarily do the following items before running the SharePoint Power Shell command. Note : Make sure you note all the existing se