FileNet P8 4.5 中的工作流程错误
在 FileNet P8 4.5 中运行工作流程时，我间歇性地收到此错误。我收到此错误的步骤有两个 CE 操作 - “createFolder”和“applySecurityTemplate”。我无法追踪这个问题。任何帮助将不胜感激。
Work Performer Exception: <Server Name - name removed>com.filenet.api.exception.EngineRuntimeException;An error was returned from the server. A Web services request received a non-HTTP response. Response contents: maxRecursion="2">Id</IncludeProperties></PropertyFilter></ObjectRequest></GetObjectsRequest></e:Body></e:Envelope> 400 Bad Request<CRLF>Connection: close [Code=null] ... Object Reference [OBJECT_STORE:4] ID "{210A5F13-CA1A-44D6-808F-CA763C882BDA}" in ObjectStore "{210A5F13-CA1A-44D6-808F-CA763C882BDA}"; OMFC/Library/GetProperties//E_SERVER_ERROR
Root Cause:
An error was returned from the server. A Web services request received a non-HTTP response. Response contents: maxRecursion="2">Id</IncludeProperties></PropertyFilter></ObjectRequest></GetObjectsRequest></e:Body></e:Envelope> 400 Bad Request<CRLF>Connection: close
I am receiving this error intermittently when running a workflow in FileNet P8 4.5. The step where I get this error has two CE operations - "createFolder" and "applySecurityTemplate". I have not been able to trace the issue. Any help would be appreciated.
Work Performer Exception: <Server Name - name removed>com.filenet.api.exception.EngineRuntimeException;An error was returned from the server. A Web services request received a non-HTTP response. Response contents: maxRecursion="2">Id</IncludeProperties></PropertyFilter></ObjectRequest></GetObjectsRequest></e:Body></e:Envelope> 400 Bad Request<CRLF>Connection: close [Code=null] ... Object Reference [OBJECT_STORE:4] ID "{210A5F13-CA1A-44D6-808F-CA763C882BDA}" in ObjectStore "{210A5F13-CA1A-44D6-808F-CA763C882BDA}"; OMFC/Library/GetProperties//E_SERVER_ERROR
Root Cause:
An error was returned from the server. A Web services request received a non-HTTP response. Response contents: maxRecursion="2">Id</IncludeProperties></PropertyFilter></ObjectRequest></GetObjectsRequest></e:Body></e:Envelope> 400 Bad Request<CRLF>Connection: close
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我首先有几个问题：
解决 CA 问题可能很困难。基本上您可以执行以下操作：
另外，由于这些似乎是与 Web 服务相关的问题，您可能需要安装一个嗅探器（如 ethereal）来查看来回传递的内容。
哈！
汤姆普尔
I have a few questions first:
Troubleshooting CA issues can be tough. Here's basically what you can do:
Also, since these seems to be a web service-related issue, you may want to install a sniffer (like ethereal) to see what is being passed back and forth.
HTH!
Tom Purl
通过 PMR，IBM 要求我们从 /opt/FileNet/WebClient/Router/routercmd.sh 启动组件管理器，并将 CE URI 从现有的 FNCEWS40DIME 更改为 FNCEWS40MTOM，问题得到解决。
Through a PMR, IBM asked us to start component manager from /opt/FileNet/WebClient/Router/routercmd.sh and change the CE URI to FNCEWS40MTOM from the existing FNCEWS40DIME and the issue is resolved.