CRM/NAV Connector – Object reference not set to an instance of an object

Another day working with the CRM/NAV connector and another error.

One of the frustrating aspects of the CRM/NAV connector is transferring the maps from one server to another (e.g. test to live).

Almost every time I have tried to do this it hasn’t worked and I have had to copy all the maps by hand.

Today I was trying it and then when I tried to open the CRM/NAV connector I was getting the error

“Object reference not set to an instance of an object”

The problem with the error above is it doesn’t really give you an indication what exactly is wrong.

If you search for the problem you will find a microsoft page – Trouble: integrating the connector

Resolving issues when reinstalling Microsoft Dynamics NAV and starting the Connector for Microsoft Dynamics

When you reinstall Microsoft Dynamics NAV and then try to start the Connector for Microsoft Dynamics, you may see the following message:

Object reference not set to an instance of an object.

To resolve this error, enable the Connector in Microsoft Dynamics NAV, verify that Microsoft Dynamics NAV web services are turned on, and then start the Connector for Microsoft Dynamics again.

This didn’t solve the problem because the web service was running.

The solution to the problem this time I found on this page

Basically the problem was caused when I created a map from file, it had created rows on the MSDI database (the database the connector uses) with nulls in.

Thank fully the blog page above supplies the solution

  1. Open SQL Management Studio for server where NAV Connector database was installed
  2. Find Maps table in MSDI database
  3. Open Maps table in Edit mode
  4. Delete all records where ReaderBinder and WriterBinder is NULL

Another problem I had after this was one CRM/NAV connector integration could import maps from file and another one couldn’t.

so I had to import them into one and then copy them to the other but this didn’t actually work because it was creating nulls in the MSDI database, which means I have to type them out manually again.

I have to say I have spent days trying to configure the connector and searching for solutions to mysterious problems.

The connector might be free to download but it costs you a lot in time trying to work out how to configure it and why it’s not working.

5 thoughts on “CRM/NAV Connector – Object reference not set to an instance of an object

  1. Chris Hetzler January 25, 2012 / 3:03 pm

    Normally this situation occurs when you are trying to import a map into an integration and the map contains a reference or references to object providers that do not exist in that integration.

    For example, let’s say in a test environment you are integrating a custom entity in CRM, let’s say Vendor to another non-standard page in NAV, let’s say Vandor again. You have generated the ObjectProvider.config files using the CRM and NAV configuration utilities and have created you map in the test environment. You then save this map to a file so you can import it to a new environment. When you try to import, you get the Object Reference error you mentioned before and the database gets invalid entries written to it, preventing launch of the Connector client until you hand-edit the MSDI database using the process you point out. This scenario is something that the Connector team is aware of and will be addressing in a future release.

    However, this can also be avioded by following the user guide step by step when creating the new integration and ensuriong that the Configuration utliity has been run for each system. Which will inturn ensure that each integrated system has had its configuraiton metadata generated for it, before importing maps.

    Thanks again for using Connector for MIcrosoft Dynamics and for helpiung to make the product better.


    • Hosk January 25, 2012 / 3:16 pm

      Thanks for the detailed response, all information about the CRM/NAV connector is welcome.

      I have had this error a few times and the solution has been to do something different each time.

      What I would really like from the CRM/NAV connector team is more examples with the connector and I would like more people to blog about using the connector so there is more information about it.

      A definitive name would also be useful because that would help searching for it.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s