SOLVED ERROR "There is a problem communicating with the Microsoft CRM Server" when configuring Microsoft Dynamics CRM for Outlook

In this article we describe Step by step How to solve the ERROR "There is a problem communicating with the Microsoft CRM Server"  when configuring Microsoft Dynamics CRM for Outlook.
This error can occur during/after the installation the Microsoft Dynamics CRM client addon for Microsoft Office Outlook.After getting this message, you might this other one, while clicking the OK button:
"An error occurred loading Microsoft CRM functionality. Try restarting Microsoft Outlook. Contact your system administrator if error persists."

 How to solve the ERROR "There is a problem communicating with the Microsoft CRM Server"  when configuring Microsoft Dynamics CRM for Outlook

To resolve this problem, follow this steps:

1) Open the IE Options,and click the Security tab. Click Local intranet >> Sites, and then Advanced.
Then type the IP of the Microsoft CRM server, and click OK three times. Restart Microsoft Outlook.

2) Open regedit, and locate the following subkey: HKEY_CURRENT_USER\ Software\Microsoft\MSCRMClient. There, check for the correct URL of your Microsoft CRM server.

If these steps were NOT enought , continue with the following:

3) Inside Dynamics CRM, open Settings >> Business Unit Settings >>  Users, and locate the user who is experiencing this error. Click the information side tab, and there clear the Restricted Access Mode check box.

4) Open CONTROL from the Start of your PC, and open User Accounts >>> Advanced tab.
Click Manage Passwords, and proceed to delete all CRM passwords and usernames there.

That's all...
In this article we've seen Step by step  How to solve the ERROR "There is a problem communicating with the Microsoft CRM Server"  when configuring Microsoft Dynamics CRM for Outlook.
Enjoy Microsoft Dynamics 365 CRM!

by Carmel Schvartzman

כתב: כרמל שוורצמן

SOLVED ERROR "File already exists" when configuring Microsoft Dynamics CRM for Outlook

In this article we describe Step by step How to solve the error "File already exists"  when configuring Microsoft Dynamics CRM for Outlook.


This error can appear as follows:
"There is a problem communicating with the Microsoft Dynamics CRM server. The server might be unavailable. Try again later. If the problem persists, contact your system administrator.
File already exists. Try using a different database name."

How to solve the error "File already exists"  when configuring Microsoft Dynamics CRM for Outlook

The cause of this error, is related to succesive installations of Microsoft Dynamics CRM for Outlook.
Having a previous installation of Dynamics CRM for Outlook, can result in an existing previous configuration of the database file for the current Dynamics instance.
In order to solve this problem, follow this steps:
1) Close Outlook
2) In Explorer, go to the folder  :\Users\<Your User>\AppData :








3) In Windows, this folder is hidden by default. If that's your case, open the "Folder and search options" :

4) In the window "Folder Options", check on "Show hidden files, folders and drives":

5) Now, you could see the \AppData directory. Open it and browse to \AppData\Local\Microsoft\MSCRM\Client :

6) Delete the file that is included in the error message.

7) Finally, rerun the Configuration Wizard  .

That's all...
In this article we've seen Step by step How to solve the error "File already exists"  when configuring Microsoft Dynamics CRM for Outlook.
Enjoy Microsoft Dynamics 365 CRM!

by Carmel Schvartzman

כתב: כרמל שוורצמן

Dynamics CRM Errors when importing unmanaged solution

In this article we see Step by step How to fix Dynamics CRM Errors when importing unmanaged solution , in both CRM 2011 and CRM 2013 .
Several errors can be thrown by Microsoft Dynamics CRM while importing an unmanaged solution from test to production environments, such as "This import has failed because a different entity with the identical name" , or "Field Is Not Unique"...
Usually the causes are differences of schema between fields or entities.

First of all, try to check this 2 things:

1) Schema name and name : have the fields/entities EXACTLY (letter capitalization) the same schema names? (  new_MyField < > new_myfield ) 

2) Schema data types: have the fields/entities EXACTLY the same type? (nvarchar = nvarchar, int = int)

We'll see here in only 10 minutes how to perform a search for the DYNAMICS CRM API web service error codes , such as "0x80044150" or "0x80041a06" , for example :

How to fix Dynamics CRM Errors when importing unmanaged solution

Usually, you will get this kind of error while importing a CRM solution:




The steps are usually as following:
0) open the importing error file and make a search for "0x" to get the error!!!
1) get the hexadecimal error code for the Entity and delete the hexadecimal prefix "0x"
2) search the web for the error without the "0x" prefix
3) re-build any custom Field which has an schema name ("new_myfield") difference
4) re-build any custom Field which has a type difference

1) Step #0: open the log file to find the error :

2) Step #1: get the hexadecimal Error Code & delete its "0x" prefix :

3) Step #2: search the Web for the code but without the prefix "0X":

Make a search for "DYNAMICS CRM API web service error codes" , and append the error code:

Remember: as long as Microsoft Dynamics CRM uses GUIDs , and they are different between a development environment to a production environment, the only way it has to identify an Entity is its schema name and its type !!!!!!

Happy CRM.....

      by Carmel Schvartzman

כתב: כרמל שוורצמן

How to Fix the Dynamics CRM ERROR Public assembly must have public key token

In this article we see Step by step How to Fix the Dynamics CRM ERROR Public assembly must have public key token , in both CRM 2011 and CRM 2013 and CRM 2015 .
Several errors can be thrown by Microsoft Dynamics CRM while registering a custom plugin at the CRM server.
Usually the error message will express "Public assembly must have public key token".

We'll see here in only 10 minutes how to fix this error , which is shown this way , for example :

How to Fix the Dynamics CRM ERROR Public assembly must have public key token

Usually, you will get this kind of error while registering a new custom plugin using the Plugin Registration Tool of the Microsoft Dynamics CRM SDK:

TO FIX THIS ERROR, reopen your Visual Studio project , and open the Properties window at the "Signing" tab , as follows :

There, check the "Sign the assembly" option.

Optionally, you can sign the assembly using a password.

Then, REBUILD your project, and go to the BIN folder to get the assembly.

Open the Plugin Registration Tool, and specify the location of the assembly:

Then, set the isolation to "None", sot that there will be no limitations to the plugin functionality.

Also , select the database option as the place to store the assembly:

And click on the "Register Selected Plugins" button:

This time, because the plugin includes a signature, CRM will accept the registration:

The steps are usually as following:
0) reopen your Visual Studio project
1) open the Properties window at the "Signing" tab
2) check the "Sign the assembly" option
3) sign the assembly using a password (optional)
4) REBUILD your project
5) go to the BIN folder to get the assembly

6) Open the Plugin Registration Tool

7) specify the location of the assembly

8) click on the "Register Selected Plugins" button

Happy CRM.....

      by Carmel Schvartzman

כתב: כרמל שוורצמן

How to Check Error Codes in Dynamics CRM API Web Service

In this article we see Step by step How to Check Error Codes in Dynamics CRM API Web Service  .
We'll review here in only 5 minutes how to search for the DYNAMICS CRM API web service error codes , such as "0x80041a06" , for example :

How to Check Error Codes in Dynamics CRM API Web Service

The steps are as following:
1) open the error file and find the corresponding XML element for the Entity
2) get the hexadecimal error code for the Entity and get rid of the hexadecimal prefix "0x"
3) search the web for the error without the "0x" prefix

1) Step #1: open the error file and find the XML element for the Entity :

2) Step #2: get the hexadecimal Error Code without its "0x" prefix :

3) Step #3: search the Web for the Error code without the prefix "0X":

That's all.

Happy programming.....

      by Carmel Schvartzman

כתב: כרמל שוורצמן

How to use Tracing in CRM 2011-2013 Plugins and Workflows

In this article we describe Step by step How to use Tracing in CRM 2011-2013 Plugins and Workflows in C# in 5 minutes.
Since CRM Plugins and Workflows are deployed on web servers after the development reaches the release stage , it is usually very helpful to include tracing in your code in profusion, not only in error cases, at least when you are putting to the test new developments .
CRM 2011-2013 allows you to include tracing galore:

How to use Tracing in CRM 2011-2013 Plugins and Workflows

Phase 1: use the GetExtension() method from the "context" at your plugin-workflow:

Since this is a generic C# Dot.Net method, use the ITracingService interface to get the tracing service from the context.

Phase 2: Send the ITracingService to any method where you intend to log information using tracing:

For example:

Phase 3: inside the plugin's methods, call the ITracingService's Trace() method to send messages to the tracing:

In case of error, CRM will display an alert showing the tracing:

That's all...Enjoy Dynamics CRM

by Carmel Schvartzman

כתב: כרמל שוורצמן

How to fix the "Attribute: parentid cannot be set to NULL" exception in Dynamics CRM 2013 (2011)

1. In this article we see how to fix the "Attribute: parentid cannot be set to NULL" exception in Dynamics CRM 2013 (2011) .
   
   

How to fix the "Attribute: parentid cannot be set to NULL" exception in Dynamics CRM 2013 (2011)

1. This error appears in Dynamics CRM 2011 - 2013 custom Plugins or custom Workflows, or any C# code calling the Organization Web Service WCF endpoint using late binding. Specifically we're creating a new address for an Account or a Contact entity. The CustomerAddress CRM entity has a reference field which points to the "ParentId" , the Account or Contact to which belongs this new address :
   
   
2. The C# code above instantiates the "ParentId" field with the actual Account ID (guid) . The guid is guaranteed to contain a Value, elsewhere the code inside the brackets wouldn't be executed :
   
   
3. However, there is an exception raised , expressing that the value is null : the error message is misleading, since the data type of the CRM SQL column is indeed "uniqueidentifier" , therefore a Guid, which we tried to insert in the attribute:
4. 
   
   
   
5. You wouldn't imagine that that is not enough for CRM, and that it is expecting to get another Type at all: an "EntityReference" CRM type, and not just a Guid:
   
    

     /*  CREATE PARENT REFERENCE FOR CUSTOMER ADDRESS  */
                    EntityReference parentID = new EntityReference();                    parentID.Id = guidParentAccount.Value;                    parentID.LogicalName = "account";
                    oAccountAddress.Attributes["parentid"] = parentID;
                        /***************************************************/

This way you get rid of the error, giving to the CRM Organization Service exactly what it needed.
There is another way to write the code above, shorter, as follows:

      /*  CREATE PARENT REFERENCE FOR CUSTOMER ADDRESS  */
          oAccountAddress["parentid"] = new EntityReference("account", guidParentAccount.Value );                                            /***************************************************/

That's all...Enjoy Dynamics CRM

by Carmel Schvartzman

כתב: כרמל שוורצמן