I have a set of Active-X Components working inside an ASP application. Many of them function by directly writing text to the Response object. Once in a while, we have run into problems where, for no apparent reason, the objects stop being able to access the Response object. We get a "0x8000ffff - catestrophic failure" error message and cannot do anything. Once the object is in this state, it has been our experience that nothing short of creating a NEW project and "cut-and-paste"ing the code from one to the other will solve it.
Also, once in this state, we have boiled it down to any access to the "Response" object. Simply asking for "Response.GetState()" will generate the error. Meanwhile, there are other objects on the same server, built in the same manner, using the Response object just fine.
Here's the scenario...we need to make a simple mod to the object. We check it out from VSS and open up Delphi 5. Make the change, and <poof>...catestrophic failure. I undo the change that I made...still get the error. I do a diff via VSS on all files...no differences from the last time the project was checked in (working). Rebuild the entire project...same error. Delete all compiled files (dcu, dll, etc) and rebuild...same error. Undo checkout from VSS...same error! Unregister and re-register the library...same error!
So then, I get really frustrated, and I create a NEW active-X library, a new component, add all my methods and cut-and-paste the code from the old non-working project to the new one, without changing a thing...unregister the old one, reregister the new one and VOILA! It works fine now...at least for now!
Can anyone give me some help on how to handle this?