This seemed like an appropriate forum as I strongly believe this is somehow a configuration-related issue. Please bear with me; I haven't worked on this app or ASP.Net period in years.
It's an intranet app which has been deployed and running smoothly for those years, on IIS 6 on SBS 2003. Recently the system drive became completely full and caused a raft of problems, most of which have been fixed at this point. (The problems with the app
started when the drive was full, before the other fixes were carried out.)
App connects to an MDB file using OleDb to populate some data-driven pages. Reports, basically. A couple of reports still work fine -- ones where the user clicks a link, and the page automatically loads the report data based on predetermined criteria. However,
a couple reports require the user to input some criteria into some WebForm controls first, then click a button to load the page with the actual report output. The problem is that the DropDownLists on these "enter criteria" Forms are no longer populating.
Again, this happened spontaneously, seemingly due somehow to the system/inetpub drive filling up. For now, I won't bother sharing
all my speculation, other than a hunch that something became "corrupt" due to the full drive preventing IIS/ASP.Net from properly writing to some file.
Anyone have any idea what the cause might be, or more importantly, how to recover? Force a complete recompile of the app, delete cached files, etc.? Looking for minimally-invasive techniques for now. The other issues caused by this overall incident were
relatively huge and I am highly reluctant to go really wrenching on things at this point.
Even the first clue as to how/why data access would be working in some cases but not others would lend insight. The MDB file is the same, the conn strings are the same; the database objects in the MDB file itself seem to have no problems.
I will be happy to provide any more information required. Thanks for reading.
Have you tried recycling the application pool? Restart IIS? Ran the app in debug mode and break where it populates to see if the data is being fetched correctly and that the data is as expected?
Recycle the application pool, no. But it sounds interesting. Are there any side effects I need to be concerned about? Potential to break or cause configuration issues with any other IIS apps such as companyweb/sharepoint, OWA, OMA, ActiveSync, etc.? I
am very afraid to touch things that might have ANY negative side-effects right now, because these surrounding issues with the full drive caused such major problems, that, to be blunt, the people who sign my checks would definitely NOT appreciate a repeat or
ANY similar scenario for a long time to come. Treading very lightly.
As for reverting to the debug level, that's another thing I'm trying to avoid. My dev environment isn't even tooled for ASP.Net right now. I can look at the data directly in the MDB, and there is really no reason it should be anything but fine. We're
literally talking about a table with literally 3 rows and two columns. Customer Name and Number, for 3 customers. And again, nothing was (voluntarily) changed with any of this. I have, however, run "compact and repair" on the MDB, to no effect.
zmBu
0 Points
3 Posts
Aspects of ASP.Net app broke when inetpub/system drive became full
Aug 07, 2012 10:11 PM|LINK
This seemed like an appropriate forum as I strongly believe this is somehow a configuration-related issue. Please bear with me; I haven't worked on this app or ASP.Net period in years.
It's an intranet app which has been deployed and running smoothly for those years, on IIS 6 on SBS 2003. Recently the system drive became completely full and caused a raft of problems, most of which have been fixed at this point. (The problems with the app started when the drive was full, before the other fixes were carried out.)
App connects to an MDB file using OleDb to populate some data-driven pages. Reports, basically. A couple of reports still work fine -- ones where the user clicks a link, and the page automatically loads the report data based on predetermined criteria. However, a couple reports require the user to input some criteria into some WebForm controls first, then click a button to load the page with the actual report output. The problem is that the DropDownLists on these "enter criteria" Forms are no longer populating.
Again, this happened spontaneously, seemingly due somehow to the system/inetpub drive filling up. For now, I won't bother sharing all my speculation, other than a hunch that something became "corrupt" due to the full drive preventing IIS/ASP.Net from properly writing to some file.
Anyone have any idea what the cause might be, or more importantly, how to recover? Force a complete recompile of the app, delete cached files, etc.? Looking for minimally-invasive techniques for now. The other issues caused by this overall incident were relatively huge and I am highly reluctant to go really wrenching on things at this point.
Even the first clue as to how/why data access would be working in some cases but not others would lend insight. The MDB file is the same, the conn strings are the same; the database objects in the MDB file itself seem to have no problems.
I will be happy to provide any more information required. Thanks for reading.
Mythran
Participant
924 Points
206 Posts
Re: Aspects of ASP.Net app broke when inetpub/system drive became full
Aug 07, 2012 11:30 PM|LINK
Have you tried recycling the application pool? Restart IIS? Ran the app in debug mode and break where it populates to see if the data is being fetched correctly and that the data is as expected?
zmBu
0 Points
3 Posts
Re: Aspects of ASP.Net app broke when inetpub/system drive became full
Aug 09, 2012 10:42 PM|LINK
Thanks for the response.
Restart IIS, yes; no effect.
Recycle the application pool, no. But it sounds interesting. Are there any side effects I need to be concerned about? Potential to break or cause configuration issues with any other IIS apps such as companyweb/sharepoint, OWA, OMA, ActiveSync, etc.? I am very afraid to touch things that might have ANY negative side-effects right now, because these surrounding issues with the full drive caused such major problems, that, to be blunt, the people who sign my checks would definitely NOT appreciate a repeat or ANY similar scenario for a long time to come. Treading very lightly.
As for reverting to the debug level, that's another thing I'm trying to avoid. My dev environment isn't even tooled for ASP.Net right now. I can look at the data directly in the MDB, and there is really no reason it should be anything but fine. We're literally talking about a table with literally 3 rows and two columns. Customer Name and Number, for 3 customers. And again, nothing was (voluntarily) changed with any of this. I have, however, run "compact and repair" on the MDB, to no effect.
Thanks for any info!
Mythran
Participant
924 Points
206 Posts
Re: Aspects of ASP.Net app broke when inetpub/system drive became full
Aug 14, 2012 03:50 PM|LINK
Have you fixed your problem? I've been out of the office for a few days and forgot to check my mail yesterday :P
Ruchira
All-Star
42888 Points
7020 Posts
MVP
Re: Aspects of ASP.Net app broke when inetpub/system drive became full
Aug 15, 2012 01:57 PM|LINK
Hello,
Since this is related to IIS, more appropriate forum would be IIS forums. Please post your question on there too so you can get help from IIS experts.
My Tech blog | My YouTube ChannelPlease 'Mark as Answer' if this post helps you.