Team Foundation Server 2010 Beta2 Experience
My experiences with Visual Studio Team System and Team Foundation Server 2010 Beta2 have been exellent for the most part, but I just spent the last few days trying to troubleshoot a client installation that just wasn’t working. Everything installed fine (as usual), but then something really bizarre happened … I couldn’t create team projects! The following error would occur (originally posted on MSDN – http://social.msdn.microsoft.com/Forums/en-US/tfsprerelease/thread/6fb067e5-f0cd-4bf2-a277-99958a445b12 by my team mate Ryan Jaeger):
2009-11-06T11:57:51 | Module: Rosetta | Thread: 14 | Creating report: Bug Status
2009-11-06T11:57:52 | Module: Rosetta | Thread: 14 | Setting data sources for report: /TfsReports/DefaultCollection/TestTFS19/Bugs/Bug Status
2009-11-06T11:57:52 | Module: Rosetta | Thread: 14 | Creating report: Bug Trends
2009-11-06T11:57:53 | Module: Rosetta | Thread: 14 | Setting data sources for report: /TfsReports/DefaultCollection/TestTFS19/Bugs/Bug Trends
2009-11-06T11:57:53 | Module: Rosetta | Thread: 14 | Creating report: Reactivations
2009-11-06T11:57:53 | Module: Rosetta | Thread: 14 | Setting data sources for report: /TfsReports/DefaultCollection/TestTFS19/Bugs/Reactivations
2009-11-06T11:57:53 | Module: Rosetta | Thread: 14 | Creating report: Build Quality Indicators
2009-11-06T11:57:54 | Module: Rosetta | Thread: 14 | Setting data sources for report: /TfsReports/DefaultCollection/TestTFS19/Builds/Build Quality Indicators
2009-11-06T11:57:54 | Module: Rosetta | Thread: 14 | Creating report: Build Success Over Time
—begin Exception entry—
Time: 2009-11-06T11:57:54
Module: Engine
Event Description: TF30162: Task “BuildTask” from Group “Build” failed
Exception Type: Microsoft.TeamFoundation.Client.PcwException
Exception Message: TF203013: The path C:\Users\CARMDS~2\AppData\Local\Temp\tmp8F32.tmp is in the DOS (8.3) short path format and is not supported. Enter a full path to the item and try again.
Exception Details:
Stack Trace:
at Microsoft.VisualStudio.TeamFoundation.Build.ProjectComponentCreator.ExecuteInternal(ProjectCreationContext context, XmlNode taskXml, Boolean validationOnly)
at Microsoft.VisualStudio.TeamFoundation.Build.ProjectComponentCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.TaskExecutor.PerformTask(IProjectComponentCreator componentCreator, ProjectCreationContext context, XmlNode taskXml)
at Microsoft.VisualStudio.TeamFoundation.ProjectCreationEngine.RunTask(Object taskObj)
– Inner Exception –
Exception Type: Microsoft.TeamFoundation.Build.Client.BuildServerException
Exception Message: TF203013: The path C:\Users\CARMDS~2\AppData\Local\Temp\tmp8F32.tmp is in the DOS (8.3) short path format and is not supported. Enter a full path to the item and try again.
Stack Trace:
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.Build.Client.BuildWebService.AddProcessTemplates(ProcessTemplate[] processTemplates)
at Microsoft.TeamFoundation.Build.Client.BuildServer.SaveProcessTemplates(IProcessTemplate[] processTemplates)
at Microsoft.VisualStudio.TeamFoundation.Build.ProjectComponentCreator.ExecuteInternal(ProjectCreationContext context, XmlNode taskXml, Boolean validationOnly)
– end Inner Exception –
– Inner Exception –
Exception Type: System.Web.Services.Protocols.SoapException
Exception Message: TF203013: The path C:\Users\CARMDS~2\AppData\Local\Temp\tmp8F32.tmp is in the DOS (8.3) short path format and is not supported. Enter a full path to the item and try again.
SoapException Details: <detail xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” ExceptionMessage=”TF203013: The path C:\Users\CARMDS~2\AppData\Local\Temp\tmp8F32.tmp is in the DOS (8.3) short path format and is not supported. Enter a full path to the item and try again.” BaseExceptionName=”Microsoft.TeamFoundation.InvalidPathException” />
Stack Trace:
– end Inner Exception –
— end Exception entry —
As you can see, it’s not a terribly useful error. We scoured the event logs, trace logs … everything, but we couldn’t find any more information. Time was ticking and we needed a solution fast, so … I decided to build up a new mock environment to see if we could replicate the issue. After hours of tedius installation and environment alignement, sure enough, we couldn’t replicate the issue! The team projects created perfectly in the mock environment.
After breaking the issue down further we realized that the only difference between the production environment and the mock environment was the user accounts we used for the services. This also happened to be cryptically referenced in the error line:
The path C:\Users\CARMDS~2\AppData\Local\Temp\tmp8F32.tmp is in the DOS (8.3) short path format and is not supported. Enter a full path to the item and try again.
The main difference between the account names in production and in the mock environment was that the production names were 13 characters long, and the mock environment names were only 6 characters long. AH HA! We decided to switch the TFS Service account to using a shortner name and guess what … everything worked! The team projects created properly and all was well.
The obvious lesson here is … beware of beta software, and plan time for finding and dealing with bugs. ; )
In: Development, Team Foundation Server, Team System · Tagged with: Beta, Microsoft, Team System, Visual Studio
