TF31002, VS2008 and TFS2010

It’s funny (but not at the time) how easily you can find the answer to a question once you’ve already answered the question.

Last Friday I spent way too much time trying to figure out why I was getting the error TF31002 when trying to connect my Visual Studio 2008 instance to Team Foundation Server 2010. I knew you could do it. I have the configuration running at home. I have multiple co-workers with successful configurations. Yet, on these two machine, nothing but TF31002.

Today I can search and find all kind of solutions as long as I don’t include TF31002 in my search. Searching with the terms ‘VS2008 TFS2010’, returns the solution as the first hit. Search on TF31002 gets nothing useful. That’s why I put TF31002 in the title of this post.

The setup:

VS2008 with SP1 already installed.

We installed TFS2010.

We then installed Team Explorer for VS2008 and the Visual Studio Team System 2008 Service Pack 1 Forward Compatibility Update for Team Foundation Server 2010 (Installer). I tried to get to the TFS2010 box and received the error TF31002. Oh. I was told that you’re supposed to include the url to the team project :

http://server:8080/tfs/collection

That got me an nice message about not allowing ‘http:’, ‘https:’ nor ‘/’ in the server name.

Sound familiar?

Sadly, the answer is in the sequence of the installs. Since I installed Team Explorer after installing VS2008 SP1, I had to reinstall SP1 and then the Forward Compatibility Update.

Creating a NetBIOS alias for the local machine

My current assignment is with a client that has a system consisting of multiple components where each component is a separate .EXE. This wouldn’t be so bad except for the configuration problem that is created. Each component has its own config file and there is a requirement for some consistency between the config files for some values. In addition, the system is deployed to multiple environments and clients.

Configuration is a nightmare and we’re still doing it manually.

This past week, one of the team members thought of the idea of using aliases instead of referring to actual machine names (for file and application location). The thought was that we could define the aliases in the Hosts file and reference the loopback address (127.0.0.1).

Eh, no.

Using the Hosts file works well for HTTP but has no affect on UNC paths.

Luckily this client has an infrastructure group and they were able to help us out. They identified four registry entries that have to be changes in order to create aliases for the local machine.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters Add a new Multi-String value called OptionalNames. Enter one or more aliases, one per line.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters Add a new DWORD value called DisableStrictNameChecking and set to 1.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters Add a new DWORD value called DisableLoopBackCheck and set to 1.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
Add a new Multi-String Value BackConnectionHostNames. Enter one or more aliases, one per line.

You’ll have to cycle the machine for the configuration to take affect.

Hyper-V: “No virtual machines were found on this server” and “Access Denied”

It seems that my adventures with Hyper-V will never end. Today I was finishing up the rebuild of my laptop, which included installing the Hyper-V manager. Luckily I had previously taken good notes, I just wish I had followed them. I remembered that I had to get the Remote Server Administration Toolkit for Windows 7. After installing it, I enabled it, tried to connect to my host server, and was rewarded with the Access Denied message. After a few minutes, the Access Denied changed to the No virtual machines… message.

Sadly I spent more time on this than I should have. After review my notes, I realized that I didn’t make the COM security changes using the DCOMCNFG tool. 30 seconds to make the change and no more error messages.

Laptop Rebuild

I decided to join the cool kids and purchase an SSD. An opportunity appears and I decided to take advantage of it. I did a little bit of research and decided to get the Intel X25-M. There are an assortment of 128GB drives available but the little extra to get the 160GB seemed to be worth it.

I must say that I’m really impressed with the speed of the drive but my favorite “feature” is the sound level. There is no noise and I really like that.

Now, the downside to a new driver is installing all the software that you accumulate over the years. It’s amazing. Here’s the list of everything that I just installed:

• AVG
• Ascendo DataVault
• Foxit
• Office 2010
• Outlook Connector
• Office Communicator
• SharedView
• Silverlight 4
• PersonalBrain
• Quicken
• Blackberry Desktop Manager
• blu
• VMWare Workstation
• Windows Home Server Connector
• Windows IM
• Windows Live Writer
• Zune
• Live Meeting
• Hyper-V Manager
• Adobe Digital Edition
• ImgBurn
• Intel SSD Tools
• All the necessary drivers

Yes, there are no development tools in the list. I do all of my development in VMs. It really simplifies things.