Today I decided that I was going to attempt an install of the Team Foundation server beta 3 refresh. I decided, as always. to start with a fresh VPC image running Windows 2003 server.
I followed the instal guide for a single server deployment. The guide really was good for me and I followed it word for word hoping that if I did so all would go well. I also decided that I was going to install the RTM of SQL Developer Edition instead of the Enterprise or Standard. All went well until I ran the Team Foundation install. It blocked the instal because SQL Server was not listening on TCP/IP. Apparently from what I was able to gather is that the Dev edition does not set that during installation like Standard or Enterprise do. The details provided me with a resolution which was to run the SQL Surface Configuration tool and set the correct setting. I did that and reran the install. All seemed to be humming along nicely until I got the 28905 error message “Error 28905. WiDbLoc: Could not list of fields to localize from the database”. I clicked retry and it continued to fail. At this point I decided to google the error to see what I could find, and what do you know, many folks have had this issue, but there were no real answers until I stumbled on to this post at MS http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=104101 . Well I found the answer. I had not restarted the SQL Service and for some reason it was choking. The issue had nothing to do with localization as I installed with Engllish(US), but had everything to do with the TCP/IP setting not taking effect. I restated the service and I also decided to follow the post and kept the VPC in the foreground and about 5 minutes later the install was complete. I must say that for a first stab install of a completely new product, I am impressed. I really thought from posts that I had read prior to the attempt that this was going to be a frustrating process. Glad to see that MS had this one right. Hope this helps anyone looking to solve that same issue.