Aspimage.dll is a com component written by a company called serverobjects. As best I can tell they are selling a product but not offering any support for it whatsoever. As such their support email even bounces. It just so happens I have several sites under my responsibility that use this component. What is the issue you ask? Aspimage has a severe bug that causes it to randomly crash w3wp.exe in windows 2003 (not 2000). This does nice things like destroying session states and timing out pages among other things.
Currently I am writing a simple wrapper class in ASP classic that uses a much much better component called imageglue. The end result will be that anyone relying on ASPimage can change one line of code and instantly use imageglue instead. I have this working pretty well on a test site, but I want to clean it up a bit before I post the code. I would like to share it though seeing how my hate for aspimage runs deep. Look for the code in the next week or so hopefully.
Update: Wrapper class is posted here
I’m getting that error now too when moving my code from 2000 to 2008 web server.
Ouch. Imageglue is $299 for one license and I already own aspimage.
I hate to dish out that kind of money on an obsolete ASP classic component that I hope to do away with after rewrites to .net.
You can’t even buy it for that price for both .net and classic. you have to buy a whole new version for .net.
sigh.
If you’re running on a server with .NET 2.0 or greater installed, check out the ASPNetImage drop-in replacement for ASPImage. It’s not feature complete yet, but it works great so far and is free:
http://code.google.com/p/aspnetimage/