问题已经解决并关闭！ [英] The issue has been resolved and closed !

问题描述

此问题已解决并关闭！

谢谢！

解决方案

< span style ="color：＃1f497d; font-family：'Segoe UI'，'sans-serif'; font-size：10pt">感谢收集Asker2012问题的详细信息。 
LookupTableSortOrderIndexDuplicate错误似乎确实是重要的日志条目，并且往往表明某些数据在幕后不好。 
最好的方法是打开支持事件，因为我们很可能需要在数据库级别进行更深入的调查，以查找发生的情况并纠正错误。 
这不是我在现有案例中可以找到的错误 - 并且唯一提到此错误的错误是由特定数据库编辑复制排序顺序索引引起的。

如果您或您所在的公司不知道如何开启事件，那么请 http://support.microsoft.com 有各种选项的详细信息。

执行你想做的事情应该没有任何问题，并且很可能尝试以编程方式执行此操作会产生同样的错误。

This issue has been resolved and closed !

Thanks !

解决方案

Thanks for gathering such good details of the issue Asker2012.  The LookupTableSortOrderIndexDuplicate error does appear to be the important log entry and does tend to indicate that some data is bad behind the scenes.  The best approach would be to open a support incident, as very likely we will need to do some deeper investigation at the database level to find what has happened and to correct things.  This isn’t an error that I can find in existing cases – and the only bug that mentions this error was caused by a specific database edit to duplicate the sort order index.

If you or the company you are working for do not know how to open an incident then http://support.microsoft.com has details of the various options.

There shouldn’t be any issue doing what you are trying to do, and very likely trying to do this programmatically would give the same error.

这篇关于问题已经解决并关闭！的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！