I recently updated my ASP.NET Core MVC web application from .NET 5 to .NET 8 and have since been having intermittent timeout issues with IIS while running larger queries against the database.
The application starts fine, lets me log in, and lets me view most pages, but any page with a table that is pulling a larger list of data back eventually times out. The rest of the application will continue to work, but it is much slower than it was before I updated everything.
I had to upgrade from Visual Studio Community 2019 to 2022 (v17.9.4) to use .NET 8. And I also updated SQL Server Management Studio to 2019 (v19.3). Microsoft SQL Server is still 2012 (v11.0.2100) though.
The only error occurring while running the web application is this IIS timeout error:
Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
I can run the queries that are triggering this timeout in SSMS, and they run pretty quickly (the largest query takes 8 seconds in SSMS). They were not giving timeout errors prior to updating to .NET 8 and Visual Studio 2022.
When I run my other ASP.NET Core console application that I also updated from .NET 5 to .NET 8, I get this TLS Security Warning:
Security Warning: The negotiated TLS 1.0 is an insecure protocol and is supported for backward compatibility only. The recommended protocol version is TLS 1.2 and later.
That security warning message pops up on the command prompt every time the database connection is being opened.
Would that TLS security warning be the reason I’m getting a timeout error? And if so, what solutions can I take to remove that warning? (For example, would upgrading Microsoft SQL Server to the latest version remove this warning and stop the timeout errors?) I tried updating SSMS to 2019, but that did not solve the TLS warning or the timeout problem.
I also only have 13 GB of storage free on the C: drive (and 32 GB free on the D: drive). Would the lower amount of space left on the C: drive have anything to do with the timeout error? The timeouts are happening both while debugging the application and when I run the program through the browser after publishing to another folder. When I restart the server, everything seems to work quickly like it used to, but after only 15 minutes or so, the application slows down and the timeouts start.
Any advice on what to try from here would be greatly appreciated. Thank you!
I tried clearing out space on the C: drive: I used the Disk Clean up, cleared the nuget cache, removed temp files. Then I restarted the server. I could only get 13 GB space free on the C: drive.
I updated SQL Server Management Studio to v19. This did not remove the TLS security warning.
I'm not sure if I'm having a server space issue or a Microsoft SQL Server issue.