技术文章 - CS350718
“无法处理参与者 xxxx,因为相关的断开连接的参与者 wt.org.WTGroup:<number>在 Windchill 中添加用户到组时出现“数据库中已存在”错误
已修改: 26-Nov-2025
适用于
- Windchill PDMLink 10.2 to 13.0
说明
- 在 Windchill UI 中,无法将用户添加到任何组。
- 尝试将用户分配到组时收到错误消息
- 将用户添加到参与者管理表时收到错误消息
- 升级后,企业 LDAP 群组断开连接。
- 如果注册是由当前已断开连接的用户创建的,则成熟度历史记录会显示以下错误:
Cannot process participant XXXX because a related disconnected participant wt.org.WTUser:<number> exists in the database - 将用户添加到组时,用户界面上出现以下错误消息
Cannot process participant XXXX because a related disconnected participant wt.org.WTGroup:<number> exists in the database
Cannot process participant XXXX because a related disconnected participant wt.org.WTUser:<number> exists in the database
- 打开“成熟度历史记录”表时,日志中出现以下错误:
RROR [DataSource Task Executor-29407] com.ptc.mvc.components.ds.AbstractDataSourceComponentDataBuilder wcadmin - Unable to process component data (async) for component: maturity.history[57] wt.org.PrincipalRepairFailedException: (wt.org.orgResource/54) wt.org.OrganizationServicesException: Cannot process participant xxxxx because a related disconnected participant wt.org.WTUser:xxxxx exists in the database Nested exception is: (wt.org.orgResource/54) wt.org.OrganizationServicesException: Cannot process participant xxxxx because a related disconnected participant wt.org.WTUser:xxxx exists in the database at wt.org.StandardOrganizationServicesManager._getPersistablesValidateNewPrincipals(StandardOrganizationServicesManager.java:17613) at wt.org.StandardOrganizationServicesManager._getPersistables(StandardOrganizationServicesManager.java:17223) at wt.org.StandardOrganizationServicesManager._getPersistable(StandardOrganizationServicesManager.java:17189) at wt.org.StandardOrganizationServicesManager._getPersistable(StandardOrganizationServicesManager.java:17171) at wt.org.StandardOrganizationServicesManager._queryPrincipal(StandardOrganizationServicesManager.java:11644) at wt.org.StandardOrganizationServicesManager.getUser(StandardOrganizationServicesManager.java:3376) at jdk.internal.reflect.GeneratedMethodAccessor1110.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at wt.services.ServiceFactory$ServerInvocationHandler.invoke(ServiceFactory.java:399) at com.sun.proxy.$Proxy73.getUser(Unknown Source) at com.ptc.windchill.enterprise.history.HistoryTablesCommands.getActorName(HistoryTablesCommands.java:1288) at com.ptc.windchill.enterprise.history.HistoryTablesCommands.getMaturityData(HistoryTablesCommands.java:1131) at com.ptc.windchill.enterprise.history.HistoryTablesCommands.maturityHistory(HistoryTablesCommands.java:1015) at com.ptc.windchill.enterprise.history.mvc.builders.MaturityHistoryTableBuilder.buildComponentData(MaturityHistoryTableBuilder.java:92) at com.ptc.jca.mvc.components.DefaultJcaComponentDataBuilder.buildRawData(DefaultJcaComponentDataBuilder.java:71) at com.ptc.jca.mvc.components.DefaultJcaComponentDataBuilder.buildRawDataAsync(DefaultJcaComponentDataBuilder.java:99) at com.ptc.mvc.components.ds.AbstractDataSourceComponentDataBuilder$ComponentDataSourceTask.run(AbstractDataSourceComponentDataBuilder.java:455) at com.ptc.mvc.ds.server.DefaultDataSourceManager$DataSourceTaskCallable.callInContext(DefaultDataSourceManager.java:224) at com.ptc.mvc.ds.server.DefaultDataSourceManager$DataSourceTaskCallable.callInContext(DefaultDataSourceManager.java:193) at com.ptc.mvc.ds.server.MethodContextCallable.call(MethodContextCallable.java:47) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829)
这是文章 350718 的 PDF 版本,可能已过期。最新版本 CS350718