When you create your first project, you may get an error during the creation process. When you look at the log file and see a “proxy error” message detail it may be to do with the way that TFS installs.
I many large networks you can’t connect to the server in the browser if you use the server name. This is because the proxy server is checking DNS for the name and unless you get every server in your company added to the proxy PAC file, you will get an error. To see if this is the issue try putting the server name into the browser:
http://myServerName.
If you get the error then you should try the FQDN:
http://myServerName.myInternalDomain.com
If this work then you need to change the URL’s within TFS that it uses to define these calls. You can check what the current settings are by:
Save (or just view) the resultant XML so you can have a look at it. There are two section of importance here. One is the Reports section which will look like:
<RegistrationEntry> <Type>Reports</Type> <ServiceInterfaces> <ServiceInterface> <Name>BaseReportsUrl</Name> <Url>http://[serverName]/Reports</Url> </ServiceInterface> <ServiceInterface> <Name>DataSourceServer</Name> <Url>[serverName]</Url> </ServiceInterface> <ServiceInterface> <Name>ReportsService</Name> <Url>http://[serverName]/ReportServer/ReportService.asmx</Url> </ServiceInterface> </ServiceInterfaces> <Databases /> <EventTypes /> <ArtifactTypes /> <RegistrationExtendedAttributes /> </RegistrationEntry>
The second is the is the WSS section that is in the same format.
Now, we have established that [serverName] will not work so we will have to update TFS with the new details. To do this you need to:
iisreset /stop
cd "%programfiles% Microsoft Visual Studio 2005 Team Foundation ServerTools"
TFSReg.exe RSRegister.xml [yourDataTierServerName
]isreset /start
You can repeat this for the WSS (Windows Sharepoint Services) section.
All done and TFS should work. Although it is worth noting that in my company environment I could then no longer create projects from the TFS App server itself as [serverName] works but the FQDN did not. Typical…
If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.