InfoPath Forms Services，管理表单模板错误文件未找到
我正在使用 Sharepoint 2010，当我尝试访问中央管理时 ->常规应用程序设置 ->管理表单模板 (InfoPath Forms Services)，页面显示错误、未找到文件、解决 Microsoft Sharepoint Foundation 问题。相关 ID：xxxxxxxx。
我应该怎么做才能解决这个问题？
Im using Sharepoint 2010 and when i tried to go to Central Administration -> General Application Settings -> Manage form templates (InfoPath Forms Services), the page shows error , file not found, Troubleshoot issue with Microsoft Sharepoint Foundation. Correlation ID:xxxxxxxx.
i use this instructions for the services activation
What should i do to fix this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我解决了这个问题，Infopath表单服务是一项企业功能......甚至sharepoint也可以让您“激活”该功能。如果您没有 sharepoint 企业版，您将面临这个问题...
如果您有 sharepoint 企业 CAL 密钥，您可以升级您的安装，然后一切都会正常。 查看此链接，确保计时器没有任何问题当您执行此操作时的服务。
这是SP的一些企业服务的列表：
卓越服务
无障碍服务
InfoPath 表单服务
Visio 服务和更多...
我希望这对您有帮助...
我必须承认尝试在标准安装中激活和使用企业功能是我的错误，但 sharepoint 应该给出更有意义的消息...当尝试激活或单击链接时。
让我知道这是否适合您。
PS：对不起我的英语
i solved the problem, Infopath form services is an enterprise feature....even sharepoint let you "activate" the feature. if you dont have a the enterprise version of sharepoint you will face this problem....
If you have a sharepoint enterprise CAL key you can upgrade your installation and then everything will work. see this link , make sure you dont have any problem with the timer service when you do this.
This is the list of some of the Enterprise services of SP:
Excel Services
Access Services
InfoPath Form Services
Visio Services and more...
I Hope this help you....
I have to admit that was my mistake to try to activate and use a enterprise feature in a standard installation, but sharepoint should have given a more meaningful message ... when trying to activate or when i click in the links.
let me know if this work for you.
ps: sorry for my english
我也遇到同样的问题并且已经有一段时间了。我花了很多时间寻找解决方案。我最好的猜测是，引用的文件或文件中的命名空间之一无效，因为引用的文件似乎确实存在。也许可以使用 VS 调试文件并识别丢失的文件？
I am having this same issue and have had it for a while. I have spent a lot of time seeking a solution. My best guess is that one of the referenced files or namespaces in the files are invalid since it appears the referenced file does exist. Maybe it is possible to debug the file using VS and ID the missing file?