Last post Sep 11, 2012 09:46 AM by Veritek
Jul 13, 2012 12:05 AM|Veritek|LINK
I have a project where the base web page is an basic HTML file calling an ASMX file. Everything works until there is a certain lenght of inactivity of the web site. Once this happens, IIS doesn't see anything .net related until I etheir edit and save a file
in the /app_code or I recompile a DLL in the /bin. Once that's done, everything works again like a charm. Note that there are no modification done to any file for the service to work again and that there was no changes on the site itself as well.
I have had this problem for a few months now, I was blaming the dev environement, but now that I am in production environement and I am still having the problem, I am faced with no other options that something is going on.
I have other web application using the same set up that re not having this problem.
Jul 13, 2012 02:35 AM|ignatandrei|LINK
IIS doesn't see anything .net related
what do you mean by this? What's the specific error?
Jul 13, 2012 07:11 AM|Veritek|LINK
I have the following related error, on any file with code that needs to be executed. The error, as I said gets corrected if I save any file in the app_code or recompile any dll in the bin folders.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Requested URL: /Services.asmx/Asynchrone
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272
Jul 17, 2012 08:11 PM|Veritek|LINK
Jul 17, 2012 11:45 PM|ignatandrei|LINK
deploy the application using
Jul 21, 2012 04:23 AM|Veritek|LINK
Not working, after a few minutes of inactivity it stop seeing the files that needs to be compiled.
Jul 21, 2012 07:32 AM|HostingASPNet|LINK
How did you deploy your site and have you use the GAC? Also, you can try to increase the application pool timeout to see if this will correct temporary the problem.
Sep 11, 2012 09:46 AM|Veritek|LINK
Same problem, new error message: