I have been working on and testing an asp.net website on our local IIS server (Windows Server 2016). Today when I enter the URL in my browser nothing happens. It just spins a wheel on the browser tab but the site does not display. I looked at the Windows
Application log on the server and it shows nothing. How can I figure out and correct the reason for the website to "hang"?
I have been working on and testing an asp.net website on our local IIS server (Windows Server 2016). Today when I enter the URL in my browser nothing happens. It just spins a wheel on the browser tab but the site does not display. I looked at the Windows
Application log on the server and it shows nothing. How can I figure out and correct the reason for the website to "hang"?
Start troubleshooting... Stop and start the application pool. Verify DB connection. Login to the server and check resources using task manager. Restart the server. Try running the code from localhost. Revert to a code base you know works.
Restarted app pool, there is no db connection, don't know what to look for in task manager, restarted the server, tried form localhost (failed on server but worked on local pc), reverted back to old code and all failed the same. There are dozens of other
sites on this server that are working perfectly.
According to your description, I suggest you could try to enable the Failed Request Tracing to capture the hanging requests. You could use it to set rules that capture traces when requests to specific URLs exceed a time limit, or fail with specific errors,
etc.
To enable FRT rules, run:
This will tracing the request exceed the 30 seconds and generate the FRT XML. Then you could analysis the xml and find out the reason.
%windir%system32inetsrvappcmd configure trace "Default Web Site" /enable /path:test.aspx /timeTaken:00:00:30
Best Regards,
Brando
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue.
If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
Are you sure your command is correct? Are there missing slashes? Also, what should /path: contain? Is this the path under Default site for the web page to trace?
Are you sure your command is correct? Are there missing slashes? Also, what should /path: contain? Is this the path under Default site for the web page to trace?
If you couldn't modify the command line to match your requirement, I suggest you try to use management UI console.
More details, you could refer to below steps:
1.Open IIS management console and select fail request tracing.
2.Type in which aspx page you want to tracing or select all apsx page.
3.Set the time taken 30 seconds.
4.Click finish.
Best Regards,
Brando
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue.
If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
Member
324 Points
1455 Posts
Website won't come up
Jul 23, 2019 07:50 PM|dlchase|LINK
I have been working on and testing an asp.net website on our local IIS server (Windows Server 2016). Today when I enter the URL in my browser nothing happens. It just spins a wheel on the browser tab but the site does not display. I looked at the Windows Application log on the server and it shows nothing. How can I figure out and correct the reason for the website to "hang"?
All-Star
47391 Points
20777 Posts
Re: Website won't come up
Jul 23, 2019 08:13 PM|mgebhard|LINK
Start troubleshooting... Stop and start the application pool. Verify DB connection. Login to the server and check resources using task manager. Restart the server. Try running the code from localhost. Revert to a code base you know works.
Member
324 Points
1455 Posts
Re: Website won't come up
Jul 23, 2019 09:00 PM|dlchase|LINK
Restarted app pool, there is no db connection, don't know what to look for in task manager, restarted the server, tried form localhost (failed on server but worked on local pc), reverted back to old code and all failed the same. There are dozens of other sites on this server that are working perfectly.
Star
9771 Points
3115 Posts
Re: Website won't come up
Jul 24, 2019 02:20 AM|Brando ZWZ|LINK
Hi dlchase,
According to your description, I suggest you could try to enable the Failed Request Tracing to capture the hanging requests. You could use it to set rules that capture traces when requests to specific URLs exceed a time limit, or fail with specific errors, etc.
To enable FRT rules, run:
This will tracing the request exceed the 30 seconds and generate the FRT XML. Then you could analysis the xml and find out the reason.
Best Regards,
Brando
Please remember to click "Mark as Answer" the responses that resolved your issue.
If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
Member
324 Points
1455 Posts
Re: Website won't come up
Jul 25, 2019 09:06 PM|dlchase|LINK
Are you sure your command is correct? Are there missing slashes? Also, what should /path: contain? Is this the path under Default site for the web page to trace?
Star
9771 Points
3115 Posts
Re: Website won't come up
Jul 26, 2019 02:07 AM|Brando ZWZ|LINK
Hi dlchase,
If you couldn't modify the command line to match your requirement, I suggest you try to use management UI console.
More details, you could refer to below steps:
1.Open IIS management console and select fail request tracing.
2.Type in which aspx page you want to tracing or select all apsx page.
3.Set the time taken 30 seconds.
4.Click finish.
Best Regards,
Brando
Please remember to click "Mark as Answer" the responses that resolved your issue.
If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.