CODEWITHSUNDEEP
visual-studio-2010tfs
Mike Barlow - BarDev
Mike Barlow - BarDev

Reputation: 11267

TFS 2010: Service Unavailable 503

I've been trying to solve this problem for about a week now. I posted this question on Microsoft website and only received one reply, which did not solve my issue. The following is a combination of my posts on Microsoft website.

I installed and configured TFS 2010 on Window 7 PC 64-bit. When I navigate to http://localhost:8080/tfs in my browser, I get

Service Unavailable – HTTP Error 503. The service is unavailable.

Any help to solve this problem would be greatly appreciated.

Based on previous reading, I have done much work to figure this out. Following are the steps I have gone through to solve this issues. The list is fairly long, but I want to make sure all the information that may be pertinent to solving this problem is available.

I installed Team Foundation Server 2010 Power Tools. The following are the Critical Issues returned by the tool

The follow are additional issues that were not critical:

The follow are Information Items:

I started up a Virtual Machine with Windows 7. Installed and configured TFS. Everything seems to work fine on the Virtual Machine. With an environment working, I started to compare differences between the two.

Here are some of the differences I found between the two environments:

Thanks.

Upvotes: 19

Views: 33331

Answers (17)

Niklas Peter
Niklas Peter

Reputation: 1856

Another, pretty special reason could be, that you set "Logon as a batch job" in AD explicitly. If you do not specify this setting it defaults to "Administrators;Backup Operators". If you overwrite it e. g. to allow a custom account to schedule a task you must make to not forget adding the default values. Else exactly this problem 503 Service unavailable and a stopped app pool appears.

Upvotes: 0

Alaa Alweish
Alaa Alweish

Reputation: 9084

  • Start -> Administrative Tools -> IIS
  • {Server name} -> Application Pools
  • Right Click on Microsoft Team Foundation Server Application Pool -> Advanced Settings
  • Identity -> Choose Custom Account -> Click Set -> Enter the username and password of the system admin
  • Stop then Start Microsoft Team Foundation Server Message Queue Application Pool
  • Stop then Start Microsoft Team Foundation Server Application Pool enter image description here

Upvotes: 7

Santosh
Santosh

Reputation: 1

I have TFS installed on my local machine and TFS is running under custom account.

I solved 503 error by setting the App Pool credentials again (Microsoft Team Foundation Server Application Pool and Microsoft Team Foundation Server Message Queue Application Pool)

Upvotes: 0

Greg Bray
Greg Bray

Reputation: 15707

If the TFS server name is longer than 15 characters it could be an issue with the netbios name being different than the servername. In our case the AppFabric Service was crashing, and we had to use the following to fix the Cache Host name:

http://www.andrewjbillings.com/long-server-name-causing-app-fabric-service-to-crash/

This resolved the TF24668: The following team project collection is stopped errors that we were getting, along with some TF400732: The request has been canceled. and TF246066: Team Foundation Server is offline. error messages

Upvotes: 0

CodingBushman
CodingBushman

Reputation: 53

I very recently ran into a similar issue. One of our tools sporadically failed when attempting to contact our TFS resource. Comparing the machines in our TFS VIP, only one machine had IIS errors, namely (truncated): 503 8080 QueueFull Microsoft+Team+Foundation+Server+Application+Pool. A quick comparison of app pool settings showed that the good machine had a queue length of 1000, the bad had only 10. 1000 might be excessive, but 10 was apparently too small. I am yet to verify that changing queue length from 10 to 1000 fixed my issue. Hopefully I remember to complete my post! Hope this helps someone...

Upvotes: 0

angle
angle

Reputation: 1

Go to Application Tier in TFS Administration Console and change account; it may fix the problem

Upvotes: 0

Todrich
Todrich

Reputation: 21

I just ran into this problem. Our TFS server is not part of a domain. I noticed that the HTTP log file seemed to list IPv6 addresses at times and at other times IPv4.

I turned off IPv6 and we were able to once again connect to TFS.

Upvotes: 2

TonyBromo
TonyBromo

Reputation: 13

In my case... (my problems aren't related to how TFS is setup but accessed from a workstation)

I work for a large bank and have a sophisticated firewall/proxy - suffice it to say I have had to play with clicking various options to properly connect to our TFS AND connect to the Internet (to download Visual Studio extensions). I fix my error under the proxy settings in IE under OPTIONS | Connections | LAN Settings...

Upvotes: 1

gdbdable
gdbdable

Reputation: 4501

I encountered the same problem today. Resolution is start installation distrib of TFS and repair product (in my way i re-install only tfs 2010 service pack 1).

Upvotes: 0

Dan Weaver
Dan Weaver

Reputation: 101

I got this error as well. In the application pool there is a TFS App Pool that was stopped. Once this was started again the 503 error stopped occuring

Upvotes: 5

riezebosch
riezebosch

Reputation: 2028

After installing several times I got it working with installing SQL Server 2008 R2 (Developer) instead of using SQLExpress.

Upvotes: 0

Steeve
Steeve

Reputation: 11

Uncheck Limit connection on IIS to solve this problem.

Limiting Connections (IIS 6.0)

Upvotes: 1

user1102142
user1102142

Reputation: 206

My application pool had been stopped as well and when I looked into why or how, I discovered that it was running under a domain account of one of our admins who initially installed TFS (months ago).

B/C of a corporate domain policy, he was forced to recently enter a new password for his account. Then after business hours last night, an update was applied to the IIS server on which TFS runs, and the update required a reboot. B/C the password of the identity under which the app pool runs had changed, IIS could not restart the pool, as the identity was still set to the original domain account and password.

Once I had the admin enter his new password with the app pool's identity, the pool would restart. However, b/c corporate enforces password expiration like every 90 days, I ultimately changed the identity to local system account in order to avoid this problem in the future (choosing local system may not be the best choice).

Upvotes: 19

pankaj
pankaj

Reputation: 11

I just checked my team foundation services from application pool through inetmgr and found my services was not running.i started it and now i am able to connect to the server.

Upvotes: 0

pocjoc
pocjoc

Reputation: 510

The very first thing you must do is to ensure that the application pool is running.

Upvotes: 2

Mike Barlow - BarDev
Mike Barlow - BarDev

Reputation: 11267

I never got it to work. I created a VM and installed Team Foundation Server (TFS) 2010 and everything seem to work good. To conclude, I'm not sure what was wrong, but if I install it on a fresh server everything works fine

Upvotes: 2

Daniel Morritt
Daniel Morritt

Reputation: 1817

I've had some 503 errors from TFS myself, if my memory serves correctly (I can't test much as my test server is currently down) I had some issues with the versions of ASP.NET the TFS website was configured to use.

Check that ASP.NET is configured to use version 4.0 in IIS (right click the site > Properties > ASP.NET). Also make sure that no other non TFS sites are in the same application pool as your TFS site (actually a virtual directory in your TFS site) and configured separately (they don't seem to play well together!).

Upvotes: 0

Related Questions