收到错误2011年CRM插件:"无效的URI:主机名无法解析"。 [英] Getting error on CRM 2011 Plugin: "Invalid URI: The hostname could not be parsed."

查看:395
本文介绍了收到错误2011年CRM插件:"无效的URI:主机名无法解析"。的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有上不同领域的不同的盒子工作的插件。不过,我有它的注册上继续每次触发相应的实体事件时抛出此错误一个特别的盒子。需要说明的?甚至没有被执行的代码。即:IPlugin.Execute()接口实现的从不到达。我刚刚得到的CRM对话框,指示无效的URI:主机名无法解析。每次

I have a plugin that works on different boxes on different domains. However, I have it registered on one particular box that continues to throw this error every time the applicable entity event is triggered. The caveat? The code isn't even being executed. IE: The IPlugin.Execute() interface implementation is never reached. I just get the CRM dialog indicating "Invalid URI: The hostname could not be parsed." every time.

我已经确认代码因为我已经把它贴Visual Studio中适用的CRM流程没有被输入。在其他框,我可以,没有问题,通过步骤。这是我的决定没有被达到的代码。

I've confirmed the code isn't being entered as I've attached Visual Studio to the applicable CRM processes. On the other boxes I can step in and through with no issues. This is how I determined the code isn't being reached.

该插件已经注册在CRM一样,因为它是由其他机器。我把它放在一个特定的解决方案文件的下面,并公布(尽管这一步是没有必要的)。

The plugin has been registered in the CRM the same as it is on the other machines. I've placed it underneath a particular Solution file and published (even though that step isn't necessary).

思考?

推荐答案

我想通了。我也想通这将是在自然界愚蠢一旦我想通了。

I figured it out. I also figured it would be idiotic in nature once I figured it out.

摘要:注销旧的,过时插件

详细内容:

这是一个以前开发的插件(单独的代码库),两者的重写这是围绕一个第三方Web调用封装。第三方问题的重构营造怀旧SOAP端点到一个REST / JSON调用。该SOAP调用正式在13年1月15日下线。 AND ...等待它... 旧插件仍然注册

This was a rewrite of a previously developed plugin (separate codebase), both of which are wrappers around a third-party web call. The third-party in question refactored their old-timey SOAP endpoint to a REST/JSON call. The SOAP call was officially taken offline on 1/15/13. AND...wait for it...the old plugins were still registered.

所以,你在上面看到的错误正在被抛出SOAP端点后,旧的插件被正式弃用。

So, the error you see above was being thrown by the old plugins after the SOAP endpoint was officially deprecated.

的复合问题?因为有连接到同一个Entity.Event组合的两个IPlugin.Execute()接口,我不能踏入我的代码调试。现在,旧的插件被注销,它如预期立即中的步骤

The compounded problem? Since there were two IPlugin.Execute() interfaces wired to the same Entity.Event combination, I couldn't step into my code to debug. Now that the old plugins have been unregistered, it steps in immediately as expected.

蛋糕上的结霜?这两个执行执行()方法似乎是完全非确定性。 IE:有时我的新代码将运行(一个点),有时不会。因此,无论双方执行()方法正在同时运行,或人会先于另一个有时,反之亦然被调用。

The frosting on the cake? The execution of those two Execute() methods appeared to be completely nondeterministic. IE: Sometimes my new code would run (to a point), and sometimes it wouldn't. So either both Execute() methods were being run at the same time or one would be called before the other sometimes and vice-versa.

我不会很快忘记这一。感谢所有你们谁评论以上。其实,我尝试新鲜的创建一个空的插件,但它显然呈现相同的结果。希望这会帮助别人一天。

I won't soon forget this one. Thanks to all you guys who commented above. I actually attempted the fresh creation of an empty plugin, but it obviously rendered the same results. Hopefully this'll help someone someday.

这篇关于收到错误2011年CRM插件:"无效的URI:主机名无法解析"。的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆