TFS 2011构建代理问题 [英] TFS 2011 Build Agent Problem
问题描述
我在安装了构建服务的Server 2008 R2 x64服务器上安装了TFS 2011预览版。 我在TFS服务器上运行了构建控制器，并在Windows 7 x64客户端上安装/配置了构建代理。 我有一个简单的构建定义
定义为运行* manual * build。
I have TFS 2011 preview installed on a Server 2008 R2 x64 server with build service installed. I have a build controller running on the TFS server and a build agent installed/configured on a Windows 7 x64 client. I have a simple build definition defined to run a *manual* build.
每个系统上的TFS构建服务配置相同...在"服务标识"选项卡我指定域帐户domain \tfsBuild和"项目集合标识"我也指定了domain \tfsBuild帐户。 domain \tfsBuild帐户
属于项目集合安全组"Project Collection Build Services"。分组。
The TFS Build Service on each system is configured the same ... On the "Service Identity" tab I specify the domain account domain\tfsBuild and on the "Project Collection Identity" I too specify the domain\tfsBuild account. The domain\tfsBuild account belongs to the project collection security group "Project Collection Build Services" group.
问题...
每次构建都会失败并出现以下错误。 我已尝试使用相同的结果指定其他域帐户等。 给出了什么？ 以下错误中引用的帐户（CM TFSBUILD，POR）是帐户域的显示名称\ tfsBuild
...我在服务帐户和项目收藏帐户标签中指定的帐户构建服务安全性。
The build fails every time with the error below. I've tried specifying a different domain account, etc. with the same result. What gives? The account referenced in the error below (CM TFSBUILD, POR) is the display name for the account domain\tfsBuild ...the one I'm specifying in the Service Account and Project Collection Account tabs in the build services security.
错误：
Microsoft.TeamFoundation.VersionControl.Client.IllegalIdentityException：TF10158 ：用户名或组名CM TFSBUILD，POR包含不受支持的字符，为空或太长。 ---> System.Web.Services.Protocols.SoapException：TF10158：用户或组
名称CM TFSBUILD，POR包含不受支持的字符，为空或太长。
Microsoft.TeamFoundation.VersionControl.Client.IllegalIdentityException: TF10158: The user or group name CM TFSBUILD, POR contains unsupported characters, is empty, or too long. ---> System.Web.Services.Protocols.SoapException: TF10158: The user or group name CM TFSBUILD, POR contains unsupported characters, is empty, or too long.
---内部异常堆栈跟踪结束---
--- End of inner exception stack trace ---
服务器堆栈跟踪：
Server stack trace:
at Microsoft.TeamFoundation.Client.TeamFoundationClientProxyBase.ProcessHttpResponse（HttpWebResponse response，Stream responseStream，WebException webException，XmlReader& xmlResponseReader）
at Microsoft.TeamFoundation.Client.TeamFoundationClientProxyBase.ProcessHttpResponse(HttpWebResponse response, Stream responseStream, WebException webException, XmlReader& xmlResponseReader)
at Microsoft.TeamFoundation.Client.TeamFoundationClientProxyBase.ExecWebServiceRequest（HttpWebRequest request，XmlWriter requestXml，String methodName，HttpWebResponse& response）
at Microsoft.TeamFoundation.Client.TeamFoundationClientProxyBase.ExecWebServiceRequest(HttpWebRequest request, XmlWriter requestXml, String methodName, HttpWebResponse& response)
at Microsoft.TeamFoundation.Client.TeamFoundationClientProxy.ExecWebServiceRequest（HttpWebRequest request，XmlWriter requestXml，String methodName，HttpWebResponse& response）
at Microsoft.TeamFoundation.Client.TeamFoundationClientProxy.ExecWebServiceRequest(HttpWebRequest request, XmlWriter requestXml, String methodName, HttpWebResponse& response)
at Microsoft.TeamFoundation.VersionControl.Client.Repository.LabelItem（String workspaceName，String workspaceOwner，VersionControlLabel label，LabelItemSpec [] labelSpecs，LabelChildOption children，Failure []& failures）
at Microsoft.TeamFoundation.VersionControl.Client.Repository.LabelItem(String workspaceName, String workspaceOwner, VersionControlLabel label, LabelItemSpec[] labelSpecs, LabelChildOption children, Failure[]& failures)
  at Microsoft.TeamFoundation.VersionControl.Client.VersionControlServer.CreateLabel（VersionControlLabel label，LabelItemSpec [] itemSpecs，LabelChildOption options）
at Microsoft.TeamFoundation.VersionControl.Client.VersionControlServer.CreateLabel(VersionControlLabel label, LabelItemSpec[] itemSpecs, LabelChildOption options)
at Microsoft.TeamFoundation.Build.Workflow.Activities.TfLabel.TfLabelInternal.RunCommand（VersionControlScope versionControlScope，String nonFatalError，VersionControlLabel label，IEnumerable`1 items，LabelChildOption childOption）
at Microsoft.TeamFoundation.Build.Workflow.Activities.TfLabel.TfLabelInternal.RunCommand(VersionControlScope versionControlScope, String nonFatalError, VersionControlLabel label, IEnumerable`1 items, LabelChildOption childOption)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage（IntPtr md，Object [] args，Object server，Object []& outArgs）
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
在System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage（RuntimeMethodHandle md，Object [] args，Object server，Object []& outArgs）
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage（IMessage msg，IMessageSink replySink）
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
异常重新抛出[0 ]：
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper（Message reqMsg，Boolean bProxyCase）
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke（Object NotUsed，MessageData& msgData）
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
at System.Func`6.EndInvoke（IAsyncResult result）
at System.Func`6.EndInvoke(IAsyncResult result)
at Microsoft.TeamFoundation.Build.Workflow.Activities.TfLabel.TfLabelInternal.EndExecute（AsyncCodeActivityContext context，IAsyncResult results）
at Microsoft.TeamFoundation.Build.Workflow.Activities.TfLabel.TfLabelInternal.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity`1.System.Activities.IAsyncCodeActivity.FinishExecution（AsyncCodeActivityContext context，IAsyncResult result）
at System.Activities.AsyncCodeActivity`1.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext context, IAsyncResult result)
at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute（ActivityExecutor executor，BookmarkManager bookmarkManager）
at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)
推荐答案
因此，在进一步的故障排除之后，如果我在构建期间将构建定义配置为不标记源，则构建成功完成。
So after further troubleshooting it appears if I configure the build definition not to label source during the build the build completes successfully.
一旦我更改构建定义"Label Sources =真QUOT;然后我收到错误。
As soon as I change the build definition "Label Sources = True" then I get the error.
我是否需要手动将构建服务帐户添加到另一个TFS组？ 出于好奇，我确实把它添加到了"贡献者"中。然而，那组没有效果。 如果我有构建定义设置来应用标签，构建仍然会失败。
Do I need to manually add the build service account to another TFS group? Out of curiosity I did add it to the "Contributors" group however that had no effect. The build still fails if I have the build definition setup to apply a label.
这让我开始坚持。
这篇关于TFS 2011构建代理问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
