HYPERAXE

A few weeks ago, I came to realize that I’m still a jack of all trade even here in my new job. It’s not meant for bragging, but I really didn’t expect that I can still be of much use even in Windows based services, when I am more of a Linux/Unix guy.

There was this problem regarding our Team Foundation Proxy Server that even our Windows Administrator cannot figure out. The problem was that after starting the TFS Proxy service on our Windows 2003 server, the service just stops and throws out some errors that is not really useful at all. Well, what’s new with Windows errors, they always give out those weird characters not readable by ordinary men.

One of our managers decided to throw me into the problem, for the intention that I’ll learn things and be the one in charge of such things in the future. I guess what everyone didn’t expect was for me to solve the problem. It was really quite easy, the initial finding of our Windows admin is that the user account used to run the TFS Proxy server was corrupted, so he created a new one but still the TFS Proxy service stops after around 3 requests. That’s where he got stuck, and was simply at lost on how to resolve the issue at hand.

After creating the new user, the TFS Proxy still exhibited the shutting down problem. That’s where I came in and after a few tinkering of the IIS configuration, and analyzation of the logs, I found out that the problem was simply due to the fact that the new user was not included in the IIS group that’s allowed to run applications in its application pool. So I simply configured the new user to be a member of the said group and walah!, TFS Proxy Server was fixed.

I guess that most of the administrative stuffs either on Linux or Windows can easily be resolved if you understand how things work and how the components relate to each other.

[tags]Team Foundation Server,Team Foundation Server Proxy, Windows 2003, Internet Information Server, Microsoft Windows, Windows Administration,TFS[/tags]

Popularity: 3% [?]