Error when qualifying Lead into Opportunity | D365 Sales

There could be many reasons and most of it could be found when you perform an online search, but none of those suggestions fixed my issue. When I was qualifying the Lead into an Opportunity, it is showing the following error:

OrganizationServiceFault

And that is it. No other details about the error. No error log, not description of the error, no error code. Nothing!

Resolution

My user didn't have system administrator, but a custom role was assigned to the user. I took some help from my technical team who did a little bit of digging and came across this below message.

Entered Microsoft.Dynamics.SCMExtended.Plugins.Plugins.LeadPrimaryContactPostCreate.Execute(), Correlation Id: 021c0dc2-3e1e-46e5-81c0-b1524ae09ed2, Initiating User: e7925424-1da4-ed11-aad1-002248a13b63

Exception: System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Principal user (Id=xxxx5424-xxxx-ed11-xxxx-002248a1xxxx, type=8, roleCount=4, privilegeCount=1064, accessMode=0, MetadataCachePrivilegesCount=9751, businessUnitId=0b2c4b59-0e31-ee11-bdf4-000d3aba3d29), is missing prvReadSolution privilege (Id=b64e92c8-5d2a-4052-a026-1b73eff9cebf) on OTC=7100 for entity 'solution' (LocalizedName='Solution').

I provided a Read privilege to Solution table under; relevant Security Role > Customization > Solution, and it worked.

Hope it helps!

D365 CE: Unable to load plugin assembly when saving a record

Issue Statement

After setting up a new on-premise D365 CE v9.0 environment, when I tried creating the first record (Contact record), I received the below error message. I wasn't able to save the Contact record. 

Resolution 1

On the app server the C:\Program Files\Dynamics 365\Server\bin\assembly folder is not inheriting security permissions from C:\Program Files\Dynamics 365\Server\bin.  Enable inheritance and you'll be able to save the record successfully.  Inheritance added the following users to ntfs security: all application packages, all restricted application packages, creator owner, system, trusted installer.  Those were not there when inheritance was disabled.

Also ensure that the deployment administrator has full permissions on the bin folder C:\Program Files\Dynamics 365\Server\bin.

Resolution 2

Ensure the deployment administrator has full permissions on the bin folder C:\Program Files\Dynamics 365\Server\bin.

Resolution 3

Ensure CRMAppPool account has full access on bin folder C:\Program Files\Dynamics 365\Server\bin. Reset IIS.

How to fix: Insufficient Permissions issue in CRM 2013

Insufficient Permissions

You do not have permission to access this record. Contact your Microsoft Dynamics CRM Administrator.

Fortunately, you are reading a blog and you do have permissions to read on :)

Turn on CRM tracing and you will be able to point out the specific error.

Well in my scenario, we had upgraded from CRM 2011 to Dynamics CRM 2013 and when my users tried to access Account or Contact records, they received this error. Even when they had read permissions on them.

I initially thought may be it is something to do with the Append and Append To privileges. So I pumped them up but to no gain.

Resolution
You need to provide the following permission to Opportunity Relationship as show in the image below:

Organization level access rights on

• Read
• Append and
• Append To

User level access rights on

• Create
• Write and
• Delete

Provide Organization level Read access to Process Configuration which you can find on the Customization Tab of Security Role.

Turns out CRM 2013 requires this setting explicity which was available in CRM 2011 previously. For more information read Security Role UI Mapping

Insufficient Permission error for a User with System Administrator role

A very strange issue indeed. We are using CRM 2013 On-Prem and I was trying to assign an Account record to another user. The user I am logged in as is the CRM admin (with system administrator privileges). The same user who installed CRM 2013.

However, I am receiving Insufficient Permissions error when trying to assign an Account record to another user. Here is the error log:

Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: System.Web.HttpUnhandledException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #56C416D8Detail:
  -2147220970
  System.Web.HttpUnhandledException: Microsoft Dynamics CRM has experienced an error. Reference number for administrators or support: #56C416D8
  2014-11-13T07:29:15.5961334Z
    -2147220960
    Principal user (Id=3d3d03f5-f73e-e311-b67b-002219609c15, type=8) is missing prvReadContract privilege (Id=8022a167-ea97-4c91-a41c-b77c083f7113)
    2014-11-13T07:29:15.5961334Z

Solutions

At first I was baffled as I am logged in as System Administrator and how can I not have the privileges however, this is how I resolved it.

Focus on the tag in the error log above. The Principal User ID is '3d3d03f5-f73e-e311-b67b-002219609c15'

I searched for this ID in SystemUserBase table in SQL Server.

SELECT * FROM SystemUserBase WHERE SystemUserId LIKE '3d3d03f5-f73e-e311-b67b-002219609c15'

When I reviewed the details of this record, it wasn't the System Admin but the Target User to which I was assigning this record to.

I checked his Role in CRM (Setting / Administration / Security Roles) and provided him read privileges for Contracts entity (prvReadContract privilege as mentioned in the error above).

The error was resolved and the Account record now had a new Owner.

That's why they say, read between the lines

We had a CRM organization up and running for days (we are on Dynamics CRM 2013) and of course it went down. The error was pretty generic:

An error has occurred. Please try again and if it does not work, contact your system administrator.

I clicked on the Try Again button and here is the error detail.

http://CRM_SERVER:5555/_common/error/errorhandler.aspx?B ackUri=&ErrorCode=0x80040216&Parm0=%0d%0a%0d%0aE rror%20Details%3a%20Failed%20to%20get%20priv%20user%20 group%20information.%20k%20%3d%2021a6dcf2-a2d8-4642-9a76-90fce5f1f92a%20privUserGroupId%3a%20d955e0ef-453c-4c63-9cae-a8ac9a28c82f%2c%20localSystemAdGuid%3a%2071ced336-9ba0-49be-9ad7-f6ddb010b085%2c%20Exception%3a%20System.DirectoryS ervices.DirectoryServicesCOMException%20%280x80072030%29% 3a%20There%20is%20no%20such%20object%20on%20the%20 server.%0d%0a%0d%0a%20%20%20at%20System.DirectoryService s.DirectoryEntry.Bind%28Boolean%20throwIfFail%29%0d %0a%20%20%20at%20System.DirectoryServices.Director yEntry.Bind%28%29%0d%0a%20%20%20at%20System.DirectorySer vices.Director yEntry.get_NativeObject%28%29%0d%0a%20%20%20at%20System.DirectoryServices.Director yEntry.Invoke%28String%20methodNae zme%2c%20Object%5b%5d%20args%29%0d%0a%20%20%20at%2 0Microsoft.Crm.SecurityUtils.CheckMembership%28Guid%20princi palId%2c%20Guid%20groupId%29%0d%0a 
%20%20%20at%20Microsoft.Crm.Caching.OrganizationSet tingsCacheLoader.LoadCacheData%28Guidz%20key%2c%20ExecutionContext %20context%29.&RequestUri=%2fdefault.aspx& user_lcid=1033

If you read between the lines, it says : Failed to get priv user group information.......

This is almost always because the CRM Async service is not running. If it is running, then may be due to a restart that the CRM server was up before the AD server.

Solution
Restart all the CRM services and also restart the CRM website on the IIS (for your own satisfaction)

Result
Shoot an email to your management. Cuppa coffee! :)

How to fix: "Error while fetching data extension" reporting error in CRM 2011

As a consultant you might have come across this error while accessing reports on CRM 2011.

"Error occurred while fetching the data extension."

Below I show you the screenshot so you can have a familiar look at the error.

Resolution
You might use either of the below two solutions ....... or both:

SQL Server Reporting Service is not running
Check SQL Server Reporting Service for its status. Start the service if its already not running. Follow these steps:

1. Start > Administrative Tools > Services
2. Right click SQL Server Reporting Service > Properties > Start

Check SQL Reporting Services URL for the Organization
The SQL Report Server URL must have been configured incorrectly. Follow below steps to resolve:

1. Open Deployment Manager
2. Disable the Organization for which Reports are not running
3. Click Edit Organization
4. Check validity* of the Report Server URL. If it is not correct, update the Report Server URL. It might be of the kind http://crmsrv:5555/ReportServer_CRM2011
5. Follow the wizard further and click Finish
6. Enable the CRM Organization

*To know the correct URL for Report Server, open Reporting Services Configuration Manager and click on Web Service URL and check the URL towards the below of dialog window.

Produce reports and keep your management happy :)

Unable to load client print control

When you search the post title on your preferred search engine (mostly Google or Bing) there are scores of blogs, websites and talks about resolving this issue.

"client print control" What is this anyway?

Well, when you open a report, you have a little control for printing the report. When you (from a client machine) click this for the first time, the report server installs an ActiveX component which is called the Client Print Control. This control helps the client machine send a print command which will then print you the page.

This might fail to load for a lot of reasons:

• The ActiveX Print control is of an older version.
• Is not installed on the client machine (Due to not enough security permissions)
• Is installed but couldn't load (Due to not enough security permissions)

Now, you will find a lot of resources talking about how to resolve this issue. Could be to manually install the print control, push install the control on all clients, create exceptions, edit registry and more.

If you are still reading this, it clearly means none of the above mentioned solutions worked for you. It din't for me either.

My client is using Microsoft Dynamics CRM 4.0. To cater his database needs, he's on SQL Server 2005 SP4 (Build version - 9.00.5057) sitting on one box. The Reporting Services, since you know is a separate component was SQL Server Reporting Services SP2 (Build version - 9.0.3042) sitting on another box.

While it doesn't matter if they sit on the same box or different, I'm only mentioning the environment. (Can be ignored)

My persistency in pursuing the solution lead me to few websites.

SQL Server requirements and recommendations for Microsoft Dynamics CRM
How to determine the version and edition of SQL Server and its components
Microsoft Dynamics CRM Compatibility List

And hence a decision to upgrade SQL Server report server to a similar build as of SQL Server. So we went for a Report Server upgrade from SP2 to SP3 (at first).

The issue was resolved, even though the build versions are still not same (Report Server build was 9.0.4035). I'm hoping that other things should be fine as well. If not, we will consider upgrading Reporting Services to SP4 then.

As of now, I'm sipping coffee :)

The length of the 'messageid' attribute of the 'email' entity exceeded the maximum allowed length of '100'

I was receiving this error often at the Event Viewer > Application Log of the CRM Server.

#9628 – An error occurred while delivering the e-mail message with subject "This is a second demo" in mailbox crmdemo@gmail.com for delivery to http://192.168.1.205:5555/crmdemo.System.Web.Services.Protocols.SoapException: Server was unable to process request.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.Crm.Sdk.Proxy.CrmService.Execute(Request Request)
at Microsoft.Crm.Tools.Email.Providers.CrmPollingMailboxProvider.DeliverMessageInternal(EmailMessage emailMessage)
at Microsoft.Crm.Tools.Email.Providers.Pop3PollingMailboxProvider.DeliverMessageInternal(EmailMessage emailMessage)
at Microsoft.Crm.Tools.Email.Providers.CrmPollingMailboxProvider.DeliverMessage(EmailMessage emailMessage)
at Microsoft.Crm.Tools.Email.Providers.CrmPollingMailboxProvider.Run()\r\n
0x80044331
A validation error occurred. The length of the 'messageid' attribute of the 'email' entity exceeded the maximum allowed length of '100'.
Resolution:
Tweak the Message ID attributes Maximum Length from 100 - 200 or 250 and you are good to go.
Procedure:

1. Settings > Customizations > Customize Entities > Email > Attributes
2. Double click Message ID and change the Maximum Length
3. Save and Close
4. Publish

E-mail Sending Failed - Dynamics CRM 4.0 E-mail Router

Recently I had a chance to date with the E-mail Router for Microsoft Dynamics CRM 4.0. I did not have an Exchange Server setup so I tried with the POP3 e-mail settings. Though it was straight forward and easy to configure the E-mail Router, I had some trouble sending an e-mail from CRM.

By the way, I am using Google Mail (Gmail) POP3 service to configure my environment.

I received the below error

#61042 - An error occurred while processing the outgoing e-mail
message with subject "xyz" for SMTP: http://localhost:5555/organizationName for
delivery through smtp.gmail.com. System.Net.Mail.SmtpException: The operation
has timed out.
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at
Microsoft.Crm.Tools.Email.Providers.SmtpPollingSendEmailProvider.ProcessMessageInternal(email
emailMessage)
at
Microsoft.Crm.Tools.Email.Providers.CrmPollingSendEmailProvider.ProcessMessage(email
emailMessage)
at
Microsoft.Crm.Tools.Email.Providers.CrmPollingSendEmailProvider.Run()

After trying things like re-configure E-mail Router, Gmail POP3 settings, E-mail Router service restart etc. something dawn'd on me.

I noticed that Gmail had provided with 2 port numbers, SSL (Secure Sockets Layer) and it's successor TLS (Transport Layer Security). I replaced the SSL port number with the TLS (ie 465 with 587) in the E-mail Router Outgoing Configuration Settings under the Advanced tab.

Result: The E-mail moved on and so did I. Happy e-mailing!!

The SELECT permission was denied on the object 'Build Version', database ', schema 'dbo'.

• So you were trying to Restore CRM database on another machine?
• You used the Deployment Manager to Import Organization?
• You tried to load CRM using the browser but received something you didn't want to see

The SELECT permission was denied on the object 'Build Version', database ', schema 'dbo'.

No wonder you reached this blog post. Read on. This might help:

• Open SQL Server Management Studio
• Select the CRM Database you are working with
• Right-click the BuildVersion table from the CRM Database and click Properties
• Select Permissions tab on the left pane
• Click on View Schema Permission on the right pane
• Click on Add button
• Click Browse
• Select CRMReaderRole of type Database Role
• Click OK twice (Back to Table Properties Window)
• Check the intersection Select vs. Grant
• Click OK

You should be good to go.

DMM Import Error - Source data is not in the required format

While importing data recently, I recieved the above error message. With the application of my brains I understood that Dynamics CRM and Office Excel Date formatting did not match.

I changed the Date format to mm/dd/yyyy in Excel and CRM (Tools > Options > Format) to maintain consistency and I had a favorable outcome.

MSCRMAsync error in Event Viewer

Lately I encountered another interesting error during CRM implementaion. After installing Update Rollup 4, I noticed MSCRMAsync Service in the Event Viewer throwing an error at regular intervals.

Google looked around the world wide web and brought to me that .Net Framework 3.0 SP1 was missing. I downloaded and before it could finish installation, it threw another error and took everything down (including SQL Server 2005). I un-installed Update Rollup 4 for CRM, .Net Framework 3.0 and .Net Framework 2.0. Re-installed them again in this manner

• .Net Framework 2.0
• .Net Framework 2.0 SP1
• .Net Framework 3.0 &
• .Net Framework 3.0 SP1
• Update Rollup 4

after which everything seem'd to be perfect. Event viewer was error spotless.

If you've received a similar error but had a different solution, I'm sure you want to share it as a comment.

Microsoft Dynamics CRM Server Setup did not complete successfully

Microsoft Dynamics CRM Server install failed.

Action Microsoft.Crm.Setup.Server.MsiInstallServerAction failed. This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.

I was very close to completing the CRM v4.0 installation on the server during a client implementation when I received a dialog box just as one displayed below. I've done plenty of implementations before but never came across any such error during installation. It made me think for a while, what different did I do during this installation and I noticed it was the recommended update. (The first step during a CRM installation)


After a while of thought and reading the error over and over again, I thought let me try this.

I simply cleared the IE cache, increased the cache size to almost 2 GB and re-installed CRM from the beginning, including the recommended update during the installation steps. The CRM installation glided to finish.

A happy ending!

CRM for Outlook cannot be installed on a computer where Exchange Server prior to Exchange Server 2007 are installed

Did you ever happen to see this especially when you are installing CRM client for Outlook?

Microsoft Dynamics CRM for Outlook cannot be installed on a computer where Microsoft Exchange Server versions prior to Exchange Server 2007 are installed.

It showed up today while I was installing Microsoft Dynamics CRM 4.0 Client for Office Outlook on one of the client machine's and this is how I went about solving it.

• Click Start > Run and type regedit.exe (Registry editing has been disabled by your administrator)
• Navigate to HKEY_Local_Machine\Software\Microsoft\Exchange
• Right click Exchange and export it as .reg file
• Now delete the Exchange folder from the registry
• Go ahead and install Microsoft Dynamics CRM 4.0 client for Office Outlook and also configure the CRM client.
• Once through with installation and configuration of CRM client for Office Outlook, restore the Exchange .reg file back into the registry. (Just double click it to add it back into the registry)

Your client user should be happy now!

Error while Creating a New Entity in CRM v4.0

Suppose you are creating a new Entity Projects. You enter the relevant details on the General tab while creating new entity.


On the Primary Attribute tab you mention the following details.


Now you click Save or Save and Close but you don't expect this.


Since the error is very generic, it might put you in a fix.
Fiddler clarifies with this message

Column names in each table must be unique. Column name 'new_projectid' in table 'new_projectExtensionBase' is specified more than once.

What it means is, you cannot have the Primary Attribute's Schema Name field as new_ProjectID as this name would be given to the Primary Key that CRM creates in the background which is used as the GUID. You must either change the schema name of the primary attribute or the schema name of the entity in the Entity Definition section on the General tab.

If above is not the case, it might be related to System Customizer Security Role

CRM Client for Outlook Error - The path is not of a leagal form

While installing CRM v4.0 client for Office Outlook you might encounter an error

THE PATH IS NOT OF A LEGAL FORM.

It may also appear while installing the Data Migration Manager for CRM v4.0. Here is the solution.

License Error

One of the errors that I din't have trouble solving. The error message is quite clear.

Assign a security role to the user.

Did you login now?

Event Journaling Error on Dynamics CRM 4

In Microsoft Dynamics CRM 4, when you try to open a calendar view from the Workplace, you receive this error:

Event Journaling

Invalid Recipient Type

There is a KB article I found in this regard on Microsoft site. Below is a snapshot of the article. You could get more details from http://support.microsoft.com/kb/952673

CRM Outlook Client Fails

You may seem all set after installing CRM client for Outlook and configuring it, but all attempts to run Outlook with CRM client fails with :

MS CRM webservice hoster has encountered a problem and needs to close. We are sorry for the inconvenience.

Application Event log entry :

MSCRMAddin event 5911 (info), .NET Runtime 2.0 error reporting event1000, MSCRMAddin event 5909, MSCRMAddin event 16940, MSCRMAddin event 16930, MSCRMAddin event5903.

This is because CRM client for Outlook is not comfortable when you're an Admin User. So let it have it's way and change the users Account Access mode to Full User.

"The path is not of a legal form" Error - While installing Data Migration Manager

While installing Data Migration Manager for Microsoft Dynamics CRM 4.0 on the Server, I received the error message "The path is not of a legal form"


Here is how you make the path legal to install Data Migration Manager.

• Start > Run
• Type "regedit.exe" (without quotes)
• Navigate to key - [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\59DD8CB00184F24E99A62CF4D6109FA\InstallProperties]
• Right-click InstallLocation and select Modify
• In the Value Data text field type "C:\Program Files\Microsoft Dynamics CRM"

The Value Data field had no value, until I did the above needful. Now your installation must be smooth. You can also follow this thread on Microsoft Forums for further information.

Happy Installing..

Please Note: The value 59DD8C...... after the \Products\ folder in regedit.exe might differ in some cases. I have learnt this as it has come up on forums. You might have values like:

• 43689CC1EAEE14C458FDAD0580BC0C97
• 059DD8CB00184F24E99A62CF4D6109FA

Go ahead with them. After all you want a successful installation, don't you?