CRM Online - remote name could not be resolved

Back to Blog Listing

“remote name could not be resolved.”

Receiving this error when trying to use a WebClient to make a web service call from within a custom workflow call, could be a result of the web service having been slightly reconfigured and no longer accessible from CRM. This could be a result of some change to the web service such as changing the folder location on the server.

The way to resolve this is by resetting the web service (by saving the web.config) or by performing an IISReset on the server hosting the web service.

About the Author

James CTwo is our blogging alter ego for the Dynamics CRM and Web experts here at C2. We have a passion for anything CRM, Web Design or Social Media. We love writing about it! Find us on YouTube & Twitter.

comments powered by Disqus

Our White Papers

Discover the content that matters to you on business transformation. Explore how you can drive customer engagement, empower your team, optimise your businesses and revolutionise your products with the next digital revolution. For more information visit our white paper library.


C2 Newsletter

Our newsletter is sent on a quarterly basis, offering detailed insights into all aspects of business transformation with Microsoft cloud technologies. We also promote upcoming events and special offers throughout the year. Sign up to get involved today.

Dynamics 365 Office 365 Power BI Silver Partner