Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
I received an e-mail today from Spencer Harbar with a link to a post he wrote about his experience installing Team Foundation Server Beta 3.
So, I started off with my base W2K3 disk and fired up a differencing disk and - yes - I read the install guide - this is very well put together - YOU MUST READ this document! You know the score, multiple pre-release versions of .NET, VS.NET and SQL - you know it makes sense!
This part makes me think he was using SQL Server 2005 Developer Edition, which disallows remote TCP connections by default:
The only install blocks I had were the requirement to set SQL to accept remote TCP connections and to start the SQL Agent Service using the SQL Surface Area Config Tool, neither of which were in the doc but need doing following the SQL install.
Grace Francisco sent me mail yesterday about this issue, which I've since fixed in the Installation Guide. I'm just awaiting a new doc build so I can post it:
The doc also misses out the TFS Reporting account dialog in the single server deployment section, however this is pretty obvious, and is included in the dual server section.
Dave McKinstry met with success, too. See Jeff Beehler's blog for some other examples.
Comments
- Anonymous
September 24, 2005
Very good, very good, now... where's the VPC? - Anonymous
September 24, 2005
Yup, was using the developer edition of SQL... - Anonymous
September 26, 2005
It look like the link to TFSInstall-v50920.chm has stoped working for some reason. - Anonymous
March 06, 2014
Thanks a lot bro www.xphonereview.blogspot.com