Team System 2008 Virtual Machine Naming Issue
I haven't seen anyone else post on this so maybe it's a very strange anomaly only to me. I have been meaning to blog this a while. If you download Team System 2008 Beta 2 and decide to download the Visual Studio Team System 2008 Beta 2 Team Suite & Team Foundation Server VPC don't be alarmed if you start your machine up and get an error about a service not starting. This happened to me and I dutifully ignored it. It wasn't until I open up Visual Studio and wanted to connect to the TFS that something seemed wrong. It had a TFS server instance listed that it could not connect to. The TFS instance in the "Connect to Team Foundation..." dialog box was Orcasbeta2_tfsv. It wouldn't connect. I checked the machine name. The machine name was orcasbeta2_tfsvsts. A mismatch. That is odd.
I, of course, ignored it. Went back entered my server name into the connections to TFS instances and voila it connected and I had a perfectly empty team Explorer.
Now to create a Team Project. It failed.
I don't recall what exactly the message was but it said something about check that reporting services service and reporting web site was running. The log had said it timed out.
Odd. The whole point of the VPC is to avoid this type of stuff. I looked. Everything was running.
Let's reboot.
Some pesky event notice that a service failed to start came up again. Let's ignore that. Try again on a Team project with the same results.
Finally I decided let's look at that message in the event log that was coming up on boot up. Hmm... SharePoint services couldn't start because it couldn't find the database orcasbeta2_tfsvs. WAIT A MINUTE! The entire server is installed and setup to be name orcasbeta2_tfsv and that it not it's name. Craziness.
I renamed the machine to the one apparently being expected, orcasbeta2_tfsv, instead of the name it came with orcasbeta2_tfsvsts. The obligatory reboot.
No message about a service not starting.
Start up the IDE and connect to the server name originally listed and the now current server name. Success.
Create a Team Project. Success.
So... if you get an issue on your Beta 2 VPC take a close look at the server name and the name that the server is expected to be by all the software. That may be your issue.