我正在尝试使用内部团队基础(2015 Update 3)中的Web访问来安装扩展,但它总是给我一个访问被拒绝错误(使用自定义扩展或从市场下载的一个)。
Image error from web interface
当我尝试使用tfx-cli安装它时也是如此:
C:\>tfx extension install --auth-type basic --service-url http://servername:8080/tfs/collection1--extension-id "extension1" --publisher pubb
2016-09-14T20:50:35.411Z : loader.load
TFS Cross Platform Command Line Interface v0.3.30
Copyright Microsoft Corporation
2016-09-14T20:50:35.882Z : cache.getItem
> Username: domainame\asdffasdsa
> Password:
2016-09-14T20:50:43.054Z : extensioninfo.getExtInfo
2016-09-14T20:50:48.712Z : Error: Failed Request: Internal Server Error(500) - Access denied.
2016-09-14T20:50:48.712Z :
2016-09-14T20:50:48.712Z : at processResponse (C:\Users\asdffasdsa.domainame\AppData\Roaming\npm\node_modules\tfx-cli\node_modules\vso-node-api\RestClient.js:59:18)
2016-09-14T20:50:48.712Z : at C:\Users\asdffasdsa.domainame\AppData\Roaming\npm\node_modules\tfx-cli\node_modules\vso-node-api\RestClient.js:162:13
2016-09-14T20:50:48.712Z : at callback (C:\Users\asdffasdsa.domainame\AppData\Roaming\npm\node_modules\tfx-cli\node_modules\vso-node-api\HttpClient.js:141:17)
2016-09-14T20:50:48.712Z : at handleResult (C:\Users\asdffasdsa.domainame\AppData\Roaming\npm\node_modules\tfx-cli\node_modules\vso-node-api\HttpClient.js:157:17)
2016-09-14T20:50:48.712Z : at IncomingMessage.<anonymous> (C:\Users\asdffasdsa.domainame\AppData\Roaming\npm\node_modules\tfx-cli\node_modules\vso-node-api\HttpClient.js:168:17)
2016-09-14T20:50:48.712Z : at emitNone (events.js:72:20)
2016-09-14T20:50:48.712Z : at IncomingMessage.emit (events.js:166:7)
2016-09-14T20:50:48.712Z : at endReadableNT (_stream_readable.js:921:12)
2016-09-14T20:50:48.712Z : at nextTickCallbackWith2Args (node.js:442:9)
2016-09-14T20:50:48.712Z : at process._tickCallback (node.js:356:17)
Error: Failed Request: Internal Server Error(500) - Access denied.
任何可能是问题或如何诊断它的想法?
谢谢!
答案 0 :(得分:0)
通常您缺少权限。请尝试将您的用户帐户添加到 Build Administrator Group ,然后再次尝试安装。
您还可以使用tfssecurity command为您的帐户授予相关权限。
请在GitHub https://github.com/Microsoft/tfs-cli/issues/141中查看此问题。请注意它与nodejs版本有关。