Setting up a new server

I’m currently on vacation and one of the fun things I have entertained myself with is to build a new server. It’s not used for much, it holds a few precious family media files, it gives me remote access to my things when I’m not home and of course it’s hosting my Team Foundation Server that holds my Windows Phone projects.

The old server had passed it’s due date, not only was it slow to the point of me falling asleep during checkouts, but mostly it was producing so much heat that the office became inhabitable now during the summer months. So I built a machine around an i5 2400s, and so far it’s working great. It’s faster by multitudes and it’s not raising the office temperature by any noticeable amount. (It’s also less noisy than the old one was :))

When I was in the process of checking in my NuGet packet structure into my TFS for one of the Windows Phone projects, I ran in to a small snag.

TF30063: You are not authorized to access Microsoft-IIS/7.5

I got this problem repeatedly when trying to check in a very small file structure, containing 40 or so items. And the most annoying thing was that after this happened I lost contact with the TFS. Choosing the Connect to Team Foundation Server… option in Visual Studio wasn’t helping either, I just could not log back on with my credentials. The solution to getting back on the TFS was to restart Visual Studio and connect again, then it worked.

The TF30063 error was not really solvable it seemed after reading some articles and messing about with various users and settings on the server. What seemed to be a workaround was checking in the files in smaller change sets. I started with the folder structure, then added the configs and xml files. Last I checked in the dll’s, and that seemed to do the trick.

Adventures in TFS
Tagged on:     

One thought on “Adventures in TFS

  • May 9, 2012 at 15:12
    Permalink

    I had this problem using VS11 Beta and TFS11. It turned out that the TFS server was running out of disk space. Once I added more space to the virtual server, the problem went away.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.