Where's Mama?
I had been experiencing massive delays after connecting to a TFS server in Team Explorer 2008. These usually ended up with a COM exception – Creating an instance of the COM component with CLSID {B69003B3-C55E-4B48-836C-BC5946FC3B28} from the IClassFactory failed due to the following error:80004005.
This turned out to be a problem with the October release of the TFS PowerTools. I found the solution here which was based on disabling the new ‘Collaboration’ feature that was added to Team Explorer.
We recently had a problem on a couple of Vista machines where the TFS client would not cache the credentials used to connect. Typically you would get a challenge the first time you attempt to connect, and the credentials would then go into the standard windows credential store.
I’m not certain why the bevahiour changed, but the resolution was fairly simple. Go to Control Panel > User Accounts > Manage Your Network Passwords, then manually add in an entry for the remote machine, specifying the user account to use when authenticating. Any future TFS commands issued will pick up this entry and won’t challenge you to authenticate.
Our devbuild script issues a tf get command via an msbuild task, and this was failing as it was attempting to prompt the user to authenticate. After manually adding the entry as described, the devbuild runs as it should.
No public Twitter messages.
Please feel free to get in touch, I'd love to hear from you.
