简体   繁体   English

CRM 2013升级到CRM 2015后导入现有托管解决方案时出错

[英]Error in importing existing managed solution after Upgrading CRM 2013 to CRM 2015

We are facing an issue in CRM 2015 online which was recently upgraded from CRM 2013 online version., since Earlier back with CRM 2013, it was a smooth process. 我们面临着CRM 2015 Online的一个问题,该问题最近是从CRM 2013 Online版本升级的。自CRM 2013早期以来,这是一个平稳的过程。

Issue is occurring while importing same managed solution (from dev) over same managed solution (in Test environment). 在同一托管解决方案(在测试环境中)上导入同一托管解决方案(从开发者)时发生问题。 The exception is getting raised: 异常正在引发:

"Violation of UNIQUE KEY constraint 'UQ_LocalizedLabelCheck'. Cannot insert duplicate key in object 'MetadataSchema.LocalizedLabel'. The duplicate key value is (4badb078-13be-e311-b2b9-080027842291, name, 1033, Jun 19 2015  8:13AM, 0). The statement has been terminated."

We tracked down the flawed component through GUID (ie 4badb078-13be-e311-b2b9-080027842291 in this case). 我们通过GUID(即4badb078-13be-e311-b2b9-080027842291)跟踪了有缺陷的组件。 We managed to detect and remove certain charts but after doing this repetitive action, it took us to the Chart which was dependent on Account and a custom Entity, Describing-In short, that this may lead to problem sometime later (ie after we try to removing dependency). 我们设法检测并删除了某些图表,但是在执行了此重复操作后,我们进入了依赖于帐户和自定义实体Desc Charting-In的图表,这可能会在以后的某个时间导致问题(例如,删除依赖项)。

Please let us know if anyone has seen this issue before. 请让我们知道是否有人以前见过此问题。 Any pointers will be helpful. 任何指针都会有所帮助。

Thanks! 谢谢!

try removing the entity that causes the problem from the solution. 尝试从解决方案中删除导致问题的实体。 import the solution and afterwards import the original solution. 导入解决方案,然后再导入原始解决方案。 sometimes CRM has problems with dependencies. 有时,CRM在依赖方面存在问题。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM