BizTalk 2016 -BizTalk Server TMS无法启动
关于BizTalk 2016，这似乎应该很简单，但由于安全错误而失败。
文档基本上说：“输入SSO管理员组成员的用户的用户名和密码”。 https：https：https：// learch。 microsoft.com/en-us/biztalk/core/install-and-configure-biztalk-tms-for-for-fpor-fp
我在我的用户ID下运行了biztalktms.msi（安装令牌管理器服务）（这也是一个也是一个biztalk configureation.exe程序中定义的SSO admin组成员。正确的密码
返回错误：“ Biztalk Server TMS无法启动。
如果我使用的是运行企业SSO的相同的帐户， 您有足够的特权。 VE尝试了其他3个ID，它们都会出现相同的错误
。 =“ https://stackoverflow.com/questions/51209788/nothing-happens-when-i-press-sign-in-bress-in-button-in-button-in-infice365-outlook-email-apapter-c”>在这里）
< a href =“ https://i.sstatic.net/u5yye.png” rel =“ nofollow noreferrer”>
Regarding BizTalk 2016, this seems like it should be dead simple, but failing with a security error.
Documentation basically says "Enter the username and password of a user that's a member of the SSO Administrators group."
https://learn.microsoft.com/en-us/biztalk/core/install-and-configure-biztalk-tms-for-fp
I ran BizTalkTMS.msi (to install the Token Manager Service) under my userid (which is also a member of the SSO Admin group as defined in the BizTalk configureation.exe program. It prompts for user/pass to under which the service should run. I put the exact same account "domain\user" that is running the Enterprise SSO and supposedly the correct password.
It returns the error: "BizTalk Server TMS failed to start. Verify that you have sufficient privileges to start system services."
If I'm using the exact same account that is running Enterprise SSO, how could this happen? We've tried about 3 other IDS, and they all give the same error. What could be missing?
Trying to set this up to resolve issue: "Office365 Outlook Email - Sign-In button on Receive Location does nothing" (similar to here)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您必须同时使用SSO组中的用户，并以管理员的身份运行Biztalktms.msi。在其上执行“作为管理员”，或打开命令提示符作为admin，然后从那里运行。
You have to use both the user that is in the SSO group, and run BizTalkTMS.msi as an administrator. Either do "run as admin" on it, or open a command prompt as admin, then run it from there.