I published a simple .NET 6.0 web app with user authentication on my IIS 10.0 web server hosted on Azure.
The application read and write data from a SQL Server 2017 database hosted on another machine on the same virtual network of the web server.
Everything works fine but after a while, even though nobody is using the app, it stop working and send Http Error 503 Service Unavailable and I have to restart it every time from the application pool.
I enabled tracing on the event log, but I don't receive any message explaining this.
These are the application settings:
IIS application settings
I tried to follow these advices but none of them worked:
IIS HTTP Error 503. The service is unavailable
503 “Service Unavailable” error for all apps after installing .NET Core 2.2 Runtime & Hosting Bundle for Windows
.Net core Service Unavailable after Publish to IIS
On the same web server I have other applications but this problem appears only on this one. None of the other apps is using .NET 6, most use .NET Framework 4.7/4.8 and another couple .NET Core 3.1.
I also tried to publish the application on Azure WebApp service and it has the same problem.
1. If you're deploying on IIS, we can install DebugDiag Tools and then use the DebugDiag collection to crawl the dump logs.
2. If you are using the azure app service, it is recommended to get dump in the azure portal.
My Suggestion
Enable Failed Request Tracing, and find which request will cause the Http 503.
Maybe this 503 is not a problem with the code, and it is possible to find some useful information in the log.
Check the EventViewer, try to find the useful info about the application.
Download the DebugDiag Tools, use debugdiag collection to collect the dump file when the issue occured, and use the debugdiag analysis to analyze the dump file and check the stacktrace.
My suggestion can't tell you the root cause directly, but it will help you to find it. You are also welcome to update the useful stacktrace information in the future, and there will be more people to help you.
I'm currently having the issue but using MySQL on a remote server.
Azure WebApp, Azure VM (IIS 10) and AWS EC2.
Http Error 503 Service Unavailable when the database connection timesout or fails to connect and the AppPool failed to restart.
No crashes when debugging in VS via console app.
I changed the hosting model to out-of-process and this solved the issue.
<aspNetCore processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" hostingModel="outofprocess">
I have IIS log files, I need to findout the errors generated by the asp.net web application which are hosted by IIS 7.
I used Log parser to paarse IIS log files, but I want to find errors such as timeout errors ,session errors and other 500x errors occured in the web application hosted in the server, only by analysing IIS logs.
I'm puzzled about which feild in IIS logs i need to look upon ? I have only IIS log files and no access to Event viewer.
What are the necessary feild i can parse in IIS logs to indicate that the application has undergone some error due to heavy load,or server is taking too long to respond?
How can i use 'timetaken' or any other feild in feild in IIS logs to say that the web application is lagging inperformance and prone to errors by analysing the previous IIS log files.
I'm a newbie to this.Pls help.
I am using webdeploy to deploy my web application to IIS. I followed Microsoft's 12 part tutorial for this. I successfully deployed it on my local IIS.
I have to now deploy this to production and I am following the same steps. I am connected to the remote machine via VP. Form VS2010 publish profile the connection to the server was successful. But when I enter the DB connection string as
"Data Source=xxxx\SQLExpress;Initial Catalog=SWSS;Integrated Security=True"
and try to preview the Database, I get the following error:
Web deployment task failed. ((4/1/2013 9:18:42 PM) An error occurred when the request was processed on the remote computer.)
(4/1/2013 9:18:42 PM) An error occurred when the request was processed on the remote computer.
Exception has been thrown by the target of an invocation.
Member 'ClassName' was not found.
The remote machine does not have TCP/IP enabled.
1. Is it safe to enable this in production machine?
2. If not, how to deploy DB, taking advantage of the dbdacfx?
Update 1:
Based on the comments below, I have changed my connection string as follows:
"Data Source=SWSS\SQLExpress;Initial Catalog=SWSS;User Id=xxxx;Password=xxxx;"
I created a sysadmin user in SQL server with SQL authentication rather than Windows authentication. Now the error is as follows:
Web deployment task failed. (Could not generate deployment script.
Unable to connect to target server.
Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXECUTING_METHOD.)
Update 2:
Using mixed mode authentication on SQL Server fixed my issue.
I can't seem to get a simple application to deploy to an IIS server that I am the administrator of. Here is the error message I get from VS2010 (domain name modified to protect the innocent):
------ Build started: Project: HelloWorldWeb, Configuration: Debug Any CPU ------
HelloWorldWeb -> D:\$Data\mhtest\HelloWorldWeb\bin\HelloWorldWeb.dll
------ Publish started: Project: HelloWorldWeb, Configuration: Debug Any CPU ------
Transformed Web.config using Web.Debug.config into obj\Debug\TransformWebConfig\transformed\Web.config.
Auto ConnectionString Transformed Account\Web.config into obj\Debug\CSAutoParameterize\transformed\Account\Web.config.
Auto ConnectionString Transformed obj\Debug\TransformWebConfig\transformed\Web.config into obj\Debug\CSAutoParameterize\transformed\Web.config.
Copying all files to temporary location below for package/publish:
obj\Debug\Package\PackageTmp.
Start Web Deploy Publish the Application/package to http://www.myserver.com/MSDEPLOYAGENTSERVICE ...
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets(3847,5): Error : Web deployment task failed.(Remote agent (URL http://www.myserver.com/MSDEPLOYAGENTSERVICE) could not be contacted. Make sure the remote agent service is installed and started on the target computer.)
Make sure the site name, user name, and password are correct. If the issue is not resolved, please contact your local or server administrator.
Error details:
Remote agent (URL http://www.myserver.com/MSDEPLOYAGENTSERVICE) could not be contacted. Make sure the remote agent service is installed and started on the target computer.
An unsupported response was received. The response header 'MSDeploy.Response' was 'V1' but 'v1' was expected.
The remote server returned an error: (401) Unauthorized.
Publish failed to deploy.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========
So far I have:
Installed Web Deploy 3.0 on the IIS server
Installed Web Management Service, although I don't think I'm attempting to use this yet, I want to do all this over port 80 for the time being (as opposed to 8172).
Ensured the service MsDepSvc is running as a user who is a member of Administrators
Ensured the credentials I use in VS2010 during deploy is a user who is a member of Administrators
Ensured the site and the application I've entered match what's already in existence on the IIS server
Other details:
The IIS server is remote, behind a firewall, not on my workstation's domain. I assume I should be doing this using Basic Auth, although I cann't find a way to specify this if it's not already the default.
If I open a browswer and navigate to http://www.myserver.com/MSDEPLOYAGENTSERVICE, sure enough I'm prompted for credentials. If I key in valid admin credentials, I get a blank screen - network tracing shows that the server responded with a 401.
I managed to get it working. I returned to a troubleshooting document:
http://www.iis.net/learn/publish/troubleshooting-web-deploy/troubleshooting-common-problems-with-web-deploy
About a third of the way down it references 401 errors, I read it more closely:
Trying to access Remote Agent Service as a non-administrator
SYMPTOMS
Microsoft.Web.Deployment.DeploymentException:
Could not complete the request to remote agent URL 'http://DestinationServer/msdeployAgentService'. ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized.
ROOT CAUSE
Remote Agent Service requires that the caller is a member of the Administrators group or from a domain account that has been added to the Administrators group. A local administrator which is not the built-in account will not work with the Remote Agent Service because of a bug in Web Deploy 2.0.
FIX/WORKAROUND
Provide administrative credentials
So, I didn't need to use "an" administrator account, I needed to use "the" Administrator account. I might have noticed this the first time if it didn't use a confusing double-negative and was clear about the bug also existing in the current version, i.e. 3.0 at the time of writing.
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 have uninstalled and reinstalled TFS many times
The application pool "Microsoft Team Foundation Server Application Pool" is running
The application pool "Microsoft Team Foundation Server Web Access Application Pool" is running
Other website in IIS that point to the "ASP.NET v4.0" app pool seem to run fine.
If I point my other sites to "Microsoft Team Foundation Server Application Pool" they
seems to run fine
The Windows user "TFS" is in the following rolls: Administrator, IIS_IUSRS, - TFS_APPTIER_SERVICE_WPG, Users
I'm able to run SQL Server Management Studio (SSMS) as the user "TFS" and access the databases "Tfs_Configuration" and "Tfs_DefaultCollection"
I have confirm the account for "TFS" is not disabled or expired
For IIS application "Team Foundation Server", I Configured "Failed Request Tracing Rules" to log status codes 401.3-999
After IIS Reset and browser refresh, no files in the "FailedReqLogFiles" directory
No log information in IIS Logs
In Team Foundation Server Administration Console, I can change account info(Update Password, Change Account, Reapply Account).
In Team Foundation Server Administration Console, when I try to changing Group Membership or Administer Security I get the error "Team Foundation services are not available from server http://localhost:8080/tfs. Technical information (for administrator): HTTP code 503: Service Unavailable"
In Event Viewer, I do not see anything that may be of value
In Sql Server Configuration Manager, confirmed "SQL Native Client 10.0 Configuration - (32bit)", "SQL Server Network Configuration", and "SQL Native Client 10 Configuration" all have the following protocols enabled (Shared Memory, TCP/IP, and Named Pipes"
In IE confirmed that that Proxy server is not enable.
I installed Team Foundation Server 2010 Power Tools. The following are the Critical Issues returned by the tool
Accessing "AuthorizationService" Web service at "/DefaultCollection/Services/v3.0/AuthorizationService3.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
Accessing "BuildService" Web service at "/DefaultCollection/Build/v3.0/BuildService.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The Web service call "CommonStructureService.ListAllProjects" at "/Services/v1.0/CommonStructureService.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable."
Accessing "GroupSecurityService" Web service at "/DefaultCollection/Services/v1.0/GroupSecurityService.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
Accessing "IdentityManagementService" Web service at "/DefaultCollection/Services/v3.0/IdentityManagementService.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The Web service call "Integration Services ProcessTemplate.GetTemplateName" at http://MyServer:8080/tfs/DefaultCollection/Services/v1.0/ProcessTemplate.asmx failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
Accessing "LabService" Web service at "/DefaultCollection/Lab/v3.0/LabService.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The Web service call "ProcessTemplate.TemplateHeaders" at "/Services/v1.0/ProcessTemplate.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable."
Accessing "Repository" Web service at "/DefaultCollection/VersionControl/v1.0/repository.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
Accessing "SecurityService" Web service at "/DefaultCollection/Services/v3.0/SecurityService.asmx" failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The Web service call "TeamProjectCollection.GetDefaultCollectionId" at http://MyServer:8080/tfs/TeamFoundation/Administration/v3.0/TeamProjectCollectionService.asmx failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The Web service call "VersionControl.Administration.QueryRepositoryInformation" at http://MyServer:8080/tfs/DefaultCollection/VersionControl/v1.0/administration.asmx failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The Web service call "VersionControl.Administration.QueryRepositoryInformation" at http://MyServer:8080/tfs/DefaultCollection/VersionControl/v1.0/administration.asmx failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The Web service call "ConfigurationSettings.ServiceGetWorkitemTrackingVersion" at http://MyServer:8080/tfs/DefaultCollection/WorkItemTracking/v1.0/ConfigurationSettingsService.asmx failed. Error message: "The remote server returned an error: (503) Server Unavailable.".
The follow are additional issues that were not critical:
SharePoint Products is not installed or integrated with Team Foundation Server.
Team Foundation Server is not configured to use the data warehouse.
Team Foundation Server is not configured to use Report Manager.
Results for rules that require access to Team Foundation Build cannot be included in the report.
Cannot validate the configuration of Visual Studio Lab Management. Results for rules that check the health of Visual Studio Lab Management will not be included in the report.
Paged pool memory on MyServer is over the warning threshold of 180 MB. This may not be a problem if a backup is currently in progress. Current value: 490 MB.
The follow are Information Items:
Computer: MyServer. Manufacturer: System manufacturer. Model: System Product Name.
The application tier connected to Team Foundation Server at 12/2/2010 9:09:49 PM.
The connection string in config file c:\Program Files\Microsoft Team Foundation Server 2010\Application Tier\Web ervices\Web.config on MyServer is: Data Source=MyServer;Initial Catalog=Tfs_Configuration;Integrated Security=True;.
The connection string stored in the Team Foundation Server registry is: Data Source=MyServer;Initial atalog=Tfs_Configuration;Integrated Security=True.
Logical disk C: on MyServer is 500 GB in size.
No Sharepoint Site is configured for this Team Project Collection "DefaultCollection".
No Sharepoint Site is configured for this Team Project Collection "DefaultCollection".
The MyServer is running the 64-bit version of Windows.
The SQL Server (MSSQLSERVER) service on MyServer is configured to run as user NT AUTHORITY\NETWORK SERVICE.
The account Identity for the Team Foundation Server application pool on MyServer is MyServer\TFS. This is the same as the Team Foundation Server service account.
The Team Foundation Server Product Version is 10.0.30319.317
The Team Foundation Server Service Level is Tfs2010.RTM.KB2135068.P#3.
The MyServer has 1 processor(s) installed.
The MyServer has 6134 MB of memory installed.
Volume C:\ on MyServer is a mount point.
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:
My primary computer is 64-bit and the Virtual Machine is 32-bit.
On my primary computer, IIS "Team Foundation Server Website" has a "aspnet_client" directory. On the virtual machine, this directory does not exist
On my primary computer, in IIS Manager for "Team Foundation Server" the section ASP.NET are the same on both my primary computer and virtual machine.
On my primary computer, IIS Manager IIS Section has these additional feature that the virtual machine does not include (ASP, Authorization Rules, CGI, IP Address and Domains, and WebDav Authorization)
On my primary computer, IIS Application Pool setting has a property call "Enabled 32-Bit Application". This was set to false and I changed it to true. Understandably this feature is not available on the virtual machine.
Thanks.
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).
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
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
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
The very first thing you must do is to ensure that the application pool is running.
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.
Uncheck Limit connection on IIS to solve this problem.
Limiting Connections (IIS 6.0)
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...
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!).
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.
After installing several times I got it working with installing SQL Server 2008 R2 (Developer) instead of using SQLExpress.
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).
Go to Application Tier in TFS Administration Console and change account; it may fix the problem
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...
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
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)
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.