Check out the latest features available in Dynamics 365 for Customer Engagement, including LinkedIn Connect, Voice of the Customer and Universal Resource Scheduling.
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
I am working in a 2015 environment, and every time I add a field in the account and opportunity entity, I keep getting a generic SQL error.
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=126.96.36.199, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: System.Data.SqlClient.SqlException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #4A5E7AC2Detail: <OrganizationServiceFault xmlns:i="www.w3.org/.../XMLSchema-instance" xmlns="schemas.microsoft.com/.../Contracts"> <ErrorCode>-2147220970</ErrorCode> <ErrorDetails xmlns:d2p1="schemas.datacontract.org/.../System.Collections.Generic" /> <Message>System.Data.SqlClient.SqlException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #4A5E7AC2</Message> <Timestamp>2019-05-10T16:54:03.7864101Z</Timestamp> <InnerFault i:nil="true" /> <TraceText i:nil="true" /></OrganizationServiceFault>
Has anyone experienced this before?
Try to restart DB server , restart IIS and CRM services .
If the solution suggested by Goutam does not fix your issue, please enable trace and get to the actual error message as the error message you shared above does not have the actual error detail. The one you shared above is a generic one. But CRM trace or Windows Server event viewer will most likely have the actual error logged. If you have a separate SQL server, if the CRM trace or CRM Server event viewer does not have any useful error messages logged, better to check logs on SQL Server as well
If you are not familiar with enabling trace and reading CRM trace logs, please see below
You can enable tracing using the following tool
Download the archive, unzip, under the releases folder, rename the file inside the folder 5 to .zip and unzip this to get the actual exe. Copy this across to crm server an run and enable trace
And you can use the traced reader to identify the error easily
Download the archive, unzip the file, under the releases folder, rename the file in folder 3 to .exe and this is the reader application. Copy this across to CRM server to read the trace file
Make sure you disable the tracing once you have done the debugging as it will be logging a lot of data and might quickly fill up the server hard disk
As per the previous posts, tracing will give you more information. There are 2 likely causes:
Business Applications communities