在ACM 5.5.6762.1798中保存问题数据时的persistence_flushsqlerror [英] persistence_flushsqlerror when saving issue data in ACM 5.5.6762.1798
问题描述
我们在发明近60台机器后开始出现此错误。发送/接收数据的所有其他任务都在运行。它只是"保存问题数据"。错误的任务。 Windows应用程序日志中不存在相应的条目。 5个任务完成并且"保存问题数据"在"上传应用程序信息"时会出错并继续对数据进行后处理以成功完成。一旦完成，将出现错误对话框：
___________
执行synchonizaton时ACM遇到以下错误：
Persistence_FlushSqlError违反PRIMARY KEY约束'IssueSolution_PrimaryKey'。 Cannont在对象'dbo.IssueSolution'中插入重复键。
陈旧DAta
该声明已被终止。
你想重试吗？
__________________
另请注意，所有ACM日志文件都在处理中，没有一个落后。我们希望在进一步部署ACM msi之前解决此错误。
感谢您的帮助。
Greg
嗨GregDa，
似乎我找到了解决问题的方法。
您可以通过删除约束来修复它：
ALTER TABLE [dbo]。[IssueSolution] DROP CONSTRAINT [IssueSolution_Pri maryKey]
上述解决方案摘自以下博客： -
我希望以上信息有帮助！
谢谢，
Shruti
注意 - 免责声明
使用以下材料或示例代码，您同意受以下许可条款和Microsoft合作伙伴计划协议的约束，其条款通过此引用并入本文。这些许可条款是Microsoft Corporation（或者，如果适用，基于您所在地，其关联公司）与您之间的协议。我们提供给您的任何材料（示例代码除外）仅供您内部使用。提供任何示例代码仅用于说明目的，并非旨在用于生产环境。我们授予您非独家，免版税的使用和修改示例代码的权利，并复制和分发示例代码的目标代码形式，前提是您同意：（i）不使用Microsoft的名称，徽标或商标销售您的软件，其中嵌入了示例代码; （ii）在您的软件产品中包含有效的版权声明，其中嵌入了示例代码; （iii）代表分包商并为分包商的利益提供免责声明，免除间接和后果性损害的责任以及责任的责任限制; （iv）对使用或分发样本代码而产生或导致的任何第三方索赔或诉讼（包括律师费）的Microsoft，其附属公司和供应商进行赔偿，保护无害和保护。
We started getting this error after inventoring nearly 60 machines. All other tasks of the send/receive data are functioning. It is only the "Saving the Issue Data" task that errors out. No corresponding entry exists in the Windows Application Log. 5 of the tasks complete and the "Saving the Issue Data" will error out while the "Uploading Application Information" and Post-processing the data continue on to complete successfully. Once those have completed an Error dialog appears:
___________
ACM encountered the following error while performing synchonizaton:
Persistence_FlushSqlError
Violation of PRIMARY KEY constraint 'IssueSolution_PrimaryKey'. Cannont insert duplicate key in object 'dbo.IssueSolution'.
Stale DAta
The statement has been terminated.
Would you like to retry?
__________________
Also note that all ACM log files are being processed and none are lagging behind. We would like to solve this error before further deploying the ACM msi.
Thanks or your help.
Greg
Hi GregDa,
It seems that I have found a resolution for the issue.
You can fix it by removing the constraint:
ALTER TABLE [dbo].[IssueSolution] DROP CONSTRAINT [IssueSolution_PrimaryKey]
The above mentioned resolution is extracted from following blog:-
I hope above information helps!
Thanks,
Shruti
NOTE - Disclaimer
By using the following materials or sample code you agree to be bound by the license terms below and the Microsoft Partner Program Agreement the terms of which are incorporated herein by this reference. These license terms are an agreement between Microsoft Corporation (or, if applicable based on where you are located, on of its affiliates) and you. Any materials (other than sample code) we provide to you are for your internal use only. Any sample code is provided for the purpose of illustration only and is not intended to be used in a production environment. We grant you a nonexclusive, royalty-free right to use and modify the sample code and to reproduce and distribute the object code form of the sample code, provided that you agree: (i) to not use Microsoft's name, logo, or trademarks to market your software produced in which the sample code is embedded; (ii) to include a valid copyright notice on your software product in which the sample code is embedded; (iii) to provide on behalf of and for the benefit of your subcontractors a disclaimer of warranties, exclusion of liability for indirect and consequential damages and a responsible limitation of liability; and (iv) to indemnify, hold harmless, and defend Microsoft, its affiliates and suppliers from and against any third party claims or lawsuits, including attorney's fees, that arise or result from the use or distribution of the sample code.
这篇关于在ACM 5.5.6762.1798中保存问题数据时的persistence_flushsqlerror的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
