If you’re a professional developer, you likely have an MSDN subscription and have been digging into Visual Studio 2010. I have regular MSDN, so that means I only have access to Professional, not Premium or Ultimate. However, I DO have access to Team Foundation Server. The idea was to install TFS on a dedicated server with all the bells-and-whistles, that is – SharePoint and SQL Reporting Services.
I have a Dell server that’s a quad-core with 8GB of RAM that has Hyper-V installed, and so yesterday I built a Windows 2008 R2 Enterprise server, installed SQL Server 2008, MOSS, then tried to install TFS. Well, that didn’t work… and for so many reasons. Least of which is that SQL nor SharePoint liked the idea of the server name being longer than 15 characters. When you rename a server, that messes up the SQL installation so….. blah, blah, blah… zoom ahead around 30 hours later, to tonight. I’ve installed and uninstalled SQL and SharePoint several times, and think I almost have it.
I’m to the point now where I am finally actually running the TFS Configuration and it seems like it’s working. That is with the exception of SQL Reporting Services. I found this blog post a few minutes ago which describes the exact problem on a new installation – and the solution:
So if you just take the obvious path with the installs, the link above describes the exact problem you will likely run into.
I am going to try this workaround after my install is done. If it works, I will likely crash everything down one more time – and do one, final install with everything correct. My intention for the "Part II" of this blog post – is: "I have a clean install of an OS, what do I need to install in what order to get TFS going with SharePoint and SQL Reporting Services". Well, that’s the goal at least.
More to come…