30 Mar’17

D365 SalesInvalid Namespace Error

Introduction:

We have an integration of CRM with 3 party system which sends sales data. We used Azure service bus to send data from CRM to 3 party system in real time. It was working fine until CRM 2016 But after upgradation of dynamics CRM to Dynamics 365 our integration stopped.

Description:

We decided to check why our integration has stopped so, we checked the system log and we found there is some issue with service connection.

After diagnosis of error we try to update the Azure service bus but we were not able to update the service end point. We continuously receiving the same error “Invalid Namespace” So we tried another approach and decided to create new service end point.

I have followed the below steps for registration.

  • Register a new Service Endpoint
  • Add the connection string from Service Bus portal.
  • Select the Designation Type as “Two way”
  • Error occurs “Provide a valid Namespace Address” while saving it.

Solution:

We connected with Microsoft and they suggested that there is slight modification in the Namespace Address. To resolve this issue you need to change Namespace Address from sb:// to https://

Example:
sb://xxx.servicebus.windows.net/abc/xyz -> https://xxx.servicebus.windows.net/abc/xyz

Conclusion:

Sometime unknown minor issues will stop your whole integration process and it will be not known to you.

Hope this blog help you resolve your service bus integration issue.

 

Written by

Subhash Mahato

Technical Consultant

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.

Want to streamline your business processes?

  • This field is for validation purposes and should be left unchanged.

Recent Articles

  • Reading more then 10K records in D3FOE OData API

    11 July’ 2018

    Introduction: We all know Dynamics 365 Finance and Operations has limitation of 10K records to be fetched at a time usi...

    Read more
  • Paging in D365 Customer Engagement v9.0

    10 July’ 2018

    Introduction: The Xrm.retrieveMultipleRecords method is used to retrieve a collection of records in Dynamics 365 Custom...

    Read more
  • Set up Dynamics 365 connection in Microsoft Social Engagement

    10 July’ 2018

    Introduction: This blog explains how to Set up Dynamics 365 connection in Microsoft Social Engagement. Steps to be follo...

    Read more
  • Voice of the Customer failed to install

    10 July’ 2018

    Introduction: Many people face issues in installing Voice of Customer solution on v9 environment and trying repeatedly ...

    Read more
  • Scribe Insight AX as a Web Service Find Block issue

    10 July’ 2018

    Introduction: If we need to look up for any value from AX then we do it by using a Find Block in Scribe Insight Eg: Basi...

    Read more