Has anyone encountered this error? I've just installed TFS and when I try and create a project from Team Explorer, I'm presented with this error after a few seconds processing. It's complaining about a file in the user's local temp directory.

I'm using Visual Studio 2005 SP1 Beta.

Can you include the project creation log (via email (james.manning@) is fine and/or post the relevant exception chunk here). TF30170 just means one of the steps failed, but doesn't give us any more information.

Potentially related threads that also had that error:

• http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=199258&SiteID=1
• http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=205675&SiteID=1
• http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=353685&SiteID=1

Exception Details:

Event Description: TF30162: Task "Queries" from Group "WorkItemTracking" failed
Exception Type: Microsoft.TeamFoundation.Client.PcwException
Exception Message: Error Creating Query My Work Items from C:\Documents and Settings\Peter Ritchie\Local Settings\Temp\TPW_tmpE67.tmp\WorkItem Tracking\Queries\MyWorkItems.wiq
Stack Trace:
at Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.WitPcwPlugin.PcwPluginComponentCreator.Execute(ProjectCreationContext ctxt, 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.VisualStudio.TeamFoundation.WorkItemTracking.WitPcwFatalException
Exception Message: Error Creating Query My Work Items from C:\Documents and Settings\Peter Ritchie\Local Settings\Temp\TPW_tmpE67.tmp\WorkItem Tracking\Queries\MyWorkItems.wiq
Stack Trace:
at Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.WitPcwPlugin.PcwPluginComponentCreator.WitPcwTask.StoredQueryTask.AddQuery(String name, String file)
at Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.WitPcwPlugin.PcwPluginComponentCreator.WitPcwTask.StoredQueryTask.Execute()
at Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.WitPcwPlugin.PcwPluginComponentCreator.Parse(ContextWrapper wrapper, XmlNode taskXml, Boolean fExecute)
at Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.WitPcwPlugin.PcwPluginComponentCreator.Execute(ProjectCreationContext ctxt, XmlNode taskXml)
-- end Inner Exception --
-- Inner Exception --
Exception Type: Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.WrongServerContextException
Exception Message: The server context cannot be changed through a call to the DocumentService. Force a server context switch and then call the method.
Stack Trace:
at Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.DocumentService.CreateQuery(TeamFoundationServer tfsServer, String teamProjectName, Boolean publicQuery, String queryText, Object lockToken)
at Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.QueryDocument.UploadQuery(String tfsServer, String projectName, String wiqFilePath, String queryName, QueryScope scope)
at Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.WitPcwPlugin.PcwPluginComponentCreator.WitPcwTask.StoredQueryTask.AddQuery(String name, String file)
-- end Inner Exception --
--- end Exception entry ---

Update:

My scenario: The problem occurs on a computer running VS Team Suite that was upgraded from VS Pro. While running VS Pro, Team Explorer was installed and connected to Codeplex. The recent VS SP1 Beta was installed. TFS was installed on a new computer without SP1 Beta (production-capable computer).

As it turns out, I had no problem creating the first project from another computer. The other computer (which happens to be the TFS Server) had Team Explorer installed. This installation of Team Explorer had no problem creating the first project.

Now that there is at least one project created, the first computer (that could not create the first project) is now having no problem creating projects.

Very odd indeed - we've got a bug logged on this and we're trying to track it down now. Thanks for reporting it! Hopefully we can figure it out soon and we'll try to update this thread once we know what's going on.

Thanks, Peter!