Out of Memory When using COM Objects

We have a few COM objects writen in VB6 that are used by our web sites
with ASP. Recently the DLLHOST (which I believe hosts the DLLs) often
cause the server to go out of memory.

I can view the DLLHOST process and the memory it's using by using
Process Explorer from sysinternals.com. Sometimes it occupies almost
2G of memory. At that time, no asp page will run because of not enough
memory. But our server has 1.5G RAM on it, and I think the DLLHOST is
taking more memory than it should.

Anyone knows what could be the reason?


Thanks,

James

If you are finding your IIS server crashing out of the blue and are
trying to figure out the problem(s) it won't hurt to try the following:

If you are running ASP/Access databases try compacting
your Access Databases if the sites that are going off line without notice.
If you use the databases very often that they tend to "Corrupt"
every once in a while. Be very sure that you Compact all of the Databases
that are on the server and for each one that you run the Compact tool on
that you then check the Rights on the file AFTER you run the Compact tool, I
have found that each time I run the tool it resets the IUSR account back to
Read only and if you are allowing some sort of Writing to the database you
need the Write permission. Be sure you get all of the Access databases
because just one bad database can take all the ASP/Access sites offline.

Before you use the Compact tool take note of the size of your database in
Kb's, and when you are done notice that most of your databases will be much
smaller in size, I've had some go from being 1.28 Mb's to 148 Kb's. You
will find the Compact and Repair tool by first having your Access database
open and on the "Tools", then "Database Utilities" tab on your Tool bar, and
then click on the "Compact and Repair Database" and it will run, there is
nothing else to do your done.

Again be sure you find and Compact ALL of the databases and check each one
for their permission after you Compact or you will be hearing from each of
your clients that they have a problem writing to the database.

Also I had a problem at one time with a UPS that was running way out of wack
too, and it was "banging away" at a COM port every second over and over, and
by unloading the software I quickly determined that Energizer UPS does not
work with a Windows 2000 Server, I did notify the Energizer company and they
did inform me that this particular model was not supported on a Windows 2000
IIS Server.

--


Regards,

Carroll


"James" <czhan.TakeThisOut@hotmail.com> wrote in message
news:c72bfd95.0404202130.1ff80ae9@posting.google.com...
 > We have a few COM objects writen in VB6 that are used by our web sites
 > with ASP. Recently the DLLHOST (which I believe hosts the DLLs) often
 > cause the server to go out of memory.
 >
 > I can view the DLLHOST process and the memory it's using by using
 > Process Explorer from sysinternals.com. Sometimes it occupies almost
 > 2G of memory. At that time, no asp page will run because of not enough
 > memory. But our server has 1.5G RAM on it, and I think the DLLHOST is
 > taking more memory than it should.
 >
 > Anyone knows what could be the reason?
 >
 >
 > Thanks,
 >
 > James<!-- ~MESSAGE_AFTER~ -->