Hi,

I've seen a thread on this issue, but it was old and didn't apply to my problem, so I decided to post a new thread.

So I installed TFS in a single-server configuration (following the installation documentation to the letter), put it behind an ISA 2004 firewall and created some publishing rules so it could be accessed from outside clients. I can successfully connect to it, but when I try to create a new project, it fails when trying to contact SharePoint services on the same machine. I'll paste the exception message from the log:

(I will mention that the computer name is not the same as the external DNS name)

---begin Exception entry---
Time: 2006-10-10 20:07:44Z
Module: Engine
Event Description: TF30162: Task "SharePointPortal" from Group "Portal" failed
Exception Type: Microsoft.TeamFoundation.Client.PcwException
Exception Message: Unable to connect to the Windows SharePoint Services at <hostname>:8080 Exception Details: The Project Creation Wizard was not able to connect to the Windows SharePoint Services
at <hostname>:8080 The reason for the failed connection cannot be determined at this time.
Because the connection failed, the wizard was not able to complete creating
the Windows SharePoint Services site.
Stack Trace:
   at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.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   --

Any ideas?

Thanks

Can you use PCW fine if you're connecting from an internal (not going through the ISA proxy) client? Can internal clients use the external hostname?

If the answers are both "Yes", you can change the registration so that the Sharepoint server is registered at its external name rather than just the hostname.

An example of doing so (also using ISA): http://www.vergentsoftware.com/blogs/ckinsman/CommentView.aspx?guid=4f5f8046-c0a6-4fd4-844f-128b03fba264

Great! Glad to hear it worked.

I agree with you about the tfsreg msdn article - I'll ping our docs lead to get that fixed up.