本文介绍了工作流已暂停:SPSecurityContext:安全令牌请求因事件8306而失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们的生产服务器工作流停止工作并保持暂停状态

on our production server workflow ceased to work and stay in Suspended state with

RequestorId:24c6fe30-eb6a- 123F-0000-000000000000。详细信息:在执行工作流实例期间发生未处理的异常。异常详细信息:System.ApplicationException:HTTP 401 {" error_description":"由于内部错误,服务器无法
处理请求[...]

RequestorId: 24c6fe30-eb6a-123f-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 401 {"error_description":"The server was unable to process the request due to an internal error [...]

启动用户配置文件服务应用程序,并将Worflow Manager后端服务帐户作为用户配置文件服务应用程序的完全控制。

The user profile service application is started and Worflow Manager Backend service account as Full Control on User Profile Service Application.

启动用户配置文件同步服务(一旦我重新创建UPS)。

User Profile Synchronization Service is started (once I did recreate UPS).

请帮助所有工作流程关闭。

Please help all workflows are down.

谢谢

/ Patrice

/Patrice

推荐答案

您是否能够找到解决方案?我们有类似的问题。当工作流引擎在我们的应用服务器上运行时,EventID 8306,ae0sr,af3zp和fo1t都在WFE上快速连续发生。我已经尝试了几个建议,我在网上找到了
,但没有任何帮助。

Were you ever able to find a solution to this? We have a similar problem. EventID 8306, ae0sr, af3zp, and fo1t are all coming in rapid succession on the WFE while the workflow engine is running on our app server. I have tried several suggestions that I found online but nothing is helping.

有没有人知道你是否在工作流程(app)服务器之间使用声明身份验证(Kerberos)在Web前端,我们是否需要任何特殊的SPN或AD配置来满足Kerberos?

Does anyone know if you use Claims Authentication (Kerberos for us) between the workflow (app) server and the web front end, do we need any special SPN or AD configuration to satisfy Kerberos?

谢谢。


这篇关于工作流已暂停:SPSecurityContext:安全令牌请求因事件8306而失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

11-03 02:23