When I try to create a project through Team Explorer, the wizard fails when it is trying to upload the documents to the site. When I view the error log, I see the following exception (tfs.example.com is a placeholder):

2006-08-11 16:00:58Z | Module: WssSiteCreator | Thread: 11 | TF30267: Exception: System.Web.Services.Protocols.SoapException: Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.TeamFoundation.Proxy.Portal.Admin.CreateSite(String Url, String Title, String Description, Int32 Lcid, String WebTemplate, String OwnerLogin, String OwnerName, String OwnerEmail, String PortalUrl, String PortalName)
at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.CreateSite(WssSiteData siteCreationData, ProjectCreationContext context)
at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
---begin Exception entry---
Time: 2006-08-11 16:00:58Z
Module: Engine
Event Description: TF30162: Task "SharePointPortal" from Group "Portal" failed
Exception Type: Microsoft.TeamFoundation.Client.PcwException
Exception Message: The Project Creation Wizard encountered an error while uploading documents to the Windows SharePoint Services server on https://tfs.example.com/.
Exception Details: The Project Creation Wizard encountered a problem while uploading
documents to the Windows SharePoint Services server on https://tfs.example.com/.
The reason for the failure cannot be determined at this time.
Because the operation failed, the wizard was not able to finish
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 --
Exception Type: System.Web.Services.Protocols.SoapException
Exception Message: Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
SoapException Details: <detail><errorstring xmlns="http://schemas.microsoft.com/sharepoint/soap/">The server instance specified was not found. Please specify the server's address and port.</errorstring><errorcode xmlns="http://schemas.microsoft.com/sharepoint/soap/">0x81070366</errorcode></detail>
Stack Trace:
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.TeamFoundation.Proxy.Portal.Admin.CreateSite(String Url, String Title, String Description, Int32 Lcid, String WebTemplate, String OwnerLogin, String OwnerName, String OwnerEmail, String PortalUrl, String PortalName)
at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.CreateSite(WssSiteData siteCreationData, ProjectCreationContext context)
at Microsoft.VisualStudio.TeamFoundation.WssSiteCreator.Execute(ProjectCreationContext context, XmlNode taskXml)
-- end Inner Exception --
--- end Exception entry ---

When I try to sniff HTTP, the Request:

(Request-Line): POST /_vti_adm/admin.asmx HTTP/1.1
User-Agent: Team Foundation (devenv.exe, 8.0.50727.147)
X-TFS-Version: 1.0.0.0
accept-language: en-US
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://schemas.microsoft.com/sharepoint/soap/CreateSite"
Accept-Encoding: gzip,gzip,gzip
Authorization: NTLM <COOL STRING OF TEXT HERE>
Host:tfs.example.com
Content-Length:711
Expect:100-continue

The Response:

(Status-Line): HTTP/1.1 500 Internal Server Error
Date: Mon, 11 Sep 2006 21:51:26 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Content-Length: 691
Connection: close
X-Pad: avoid browser bug

The Body:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.</faultstring>
<detail>
<errorstring xmlns="http://schemas.microsoft.com/sharepoint/soap/">The server instance specified was not found. Please specify the server's address and port.</errorstring>
<errorcode xmlns="http://schemas.microsoft.com/sharepoint/soap/">0x81070366</errorcode>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>

I am trying to find the configuration in TFS that builds the URI for this SOAP call so I can know what URI it is trying to use. Our environment doesn't allow the TFS machine to make requests to the internet so if I was logged in locally to that machine, I could not resovle https://tfs.example.com. I figure that admin.asmx is trying to make a web service request and is building the URI and failing. I want to be able to modify the configuration for TFS so that it will then build the URI for the request and point to http://tfsmachinename:17012 so that it will work locally.

The only problem I see with this is if the configuration is used to build the URI's for both internal and external requests.

I tried to use reflector to look into the DLL's but I couldn't find the WssSiteCreator type so I'm just looking for pointers now. We've done so much to get it working to this point and we're very close to having this setup.

Thanks in advance.

The interfaces are found in the TFSIntegration database, in the tbl_service_interface table. You can find the particular entry and modify it to use the fully qualified name.

Also, clients need to be able to hit the server as well, so any IE configuration needed to hit the sharepoint server from the client is also needed.