oRS.CursorType = 1
oRS.LockType = 3
sSQL = "select * from sat_lesson_drills where drill_id=" & drill_id
oRS.open sSQL, conn
For each Field in oRS.Fields
if instr(Field.Name,"MA") = 0 then
oRS.Update Field.Name, Request.Form(Field.Name)end if
next
oRS.Close
Im suddenly having a problem with the asp pages displaying on my website. Whenever I try to access an asp page, the processor usage of the task "dllhost.exe" shoots up to
100% and my asp script times out.
This asp code has been running on my site for over a year and nothing has changed about it. All the articles/advice that I have read relate to programming variables within
the asp script to prevent these type of problems. If the script has been running for this long, why would this type of problem manefest itself at this time?
I have intermittent problems with asp pages timing out. When this happens, my DLLHOST.exe runs away with all of my CPU for about 2-3 minutes. As I understand it, this component executes asp requests in a COM server on IIS.
I am not using any custom COM objects in my app, but lots of ADO. Could this be a memory leak with my use of ADO, or is this caused by something else? If it is a memory issue, I can start tracking it down. I just need to know what the possible issues/causes could be to get started troubleshooting.
The following is the error keep getting while running web application.
Tools used: HTML, ASP, DLL's(written in Delphi).
Application Error: dllhost.exe - Application Error
---------------------------
The instruction at "0x00000000" referenced memory at "0x00000000". The
memory could not be "read".
Click on OK to terminate the program
I've got a Windows 2000 server running with about 50 websites on it, all
running ASP scripts. I've noticed that the servers CPU usage gets up 100%
sometimes, caused by dllhost.exe, which I'm certain is a hanging ASP script
somewhere on the box. Probably an on error resume next line that doesn't go
anywhere when an error is an encountered. Anyways, I'm not sure if there's
a way to isolate the website where its originating, or even the page this
problem is originating from. Is there a way to do this?
I have an IIS app running in high isolation, although the dllhost.exe COM+
process isn't shutting down & accumulated memory released. I've tried to set
the 'Server Process Shutdown' on the server package in COM+ in an attempt to
shut-down the process when idle for more than 3 mins (the default), but this
ain't happening.
I've read that this may be because IIS is caching the TypeLibs so I tried
setting the AspEnabletypelibCache flag to try stop IIS doing this, if indeed
it was, but the process still doesn't shut down.
Is there another way to get the process to shutdown (I thinkin this must be
happening because references to various dll's aren't being released in the
code), I would hope there to be a way to tell IIS/COM+ to shut-down the
process anyway. I don't want to have to run a script to keep unloading the
process.
I am running a web application with application protection level set to high, so it runs in a separate dllhost.exe process, the process takes around 14,000 K of memory I wanna know if this is fine or I have a memory leak problem.
I set all record sets to nothing without closing them and also I close the database connection.
Are there any tools that can measure the ASP page performance and tell me where do I have performance bottlenecks?
I'm running IIS 5.0 under Windows 2000 Server. My ASP (VBscript) code
instantiates and uses some objects implemented in custom-written Visual Basic
6 DLLs. (Thanks to a previous thread, we no longer store those objects in
Session variables.) Application Protection for this site's Virtual Directory
is set to Medium (Pooled).
I'm using the Microsoft Web Application Stress Tool to monitor performance
and make sure database connections (opened within the VB6 DLLs) are being
closed and pooled properly. At the same time, I'm using the Windows Task
Manager to watch how much memory DLLHOST.EXE is using.
Windows Task Manager is showing me that DLLHOST is using more and more
memory over time. Memory usage goes up while a test is running, and then goes
down a bit when the dust settles after a test (e.g., once the closed
connections are removed from the pool and finally deleted), but it never goes
back down to what it was before the test ran--over time, memory usage keeps
creeping upward.
The VB6 DLLs used by my ASP pages open ADO database connections, but the
code is very careful about closing Recordsets and Connections and setting
them to Nothing.
A few questions:
1. Is this normal? Should I be concerned?
2. The ASP code instantiates these object with code like this:
set obj = Server.CreateObject("DLLname.ObjectName")
Is it important for the ASP code to do something like "set obj = Nothing"
before it exits? If the ASP code doesn't do that, will the memory used by the
object be freed when the ASP page terminates or when the user's Session ends?
3. Is there a better way I should be monitoring memory usage for this kind
of situation? (The Counters in the Perofrmance Monitor are kind of daunting.
If you can suggest an article that would help me understand memory usage,
that would be great.)
Today, an interesting thing happened to me. When I am doing the test of an
asp program, one of the pages(which I submitted several ten times before, no
problem at all) caused our server cpu rising to 100% and I reset IIS and
submit that page again and same thing happened again, and then reset IIS
again and it happened again, the process caused this is dllhost.exe.
Thinking about what's the difference this time from what I submitted before.
The only thing I can think of is I entered some name fields data with
apostrophe.
We have a web application in AS. It also uses COM+ and SQL Server as back-end. Sometimes the size of the dllhost.exe grows unexpectedly. It is such that we restart our IIS/ PWS. Also there is only one instance of dllhost running when we restart the webserver but later on we notice more than one instance sometimes.
View Replies View RelatedI have an ASP application that has been running for 5 years that I am now modifying. Since then, I have installed asp.net 1.1 and 2.0 on my xp pro box. Whenever I run the "login" code for the app, it crashes as my dllhost goes to 98% cpu. I have traced the code to this line:
Session("SCHUserID")=123
What is strange is if I set the value to 11 or lower, this does not fail. What is also strange is if I set Session("SCH1UserID")= 123 it works. I know this has to have something to do with running asp.net on this box as well. I have tried running the app in its own process (High) and creating it's own virtual directory with no luck.
I am having serveral web applications in ASP in my server ( windows 2000 advance server ), sometimes dllhost.exe taking more memory and causes the cpu usages to be 100% and makes the server hangup and causing error like "TNS : listener failed to start a dedicated server process", by the way if i end the process of dllhost.exe manually then the cpu usage will be very less and i wont get such error .
i have the following questions regarding that
1)what causes the dllhost.exe to takes more cpu usage,
2)is there any command from dos to kill such process so that i can create bat file to be run every one minute. i have searched i found only some third party tools and there is command taskkill but it is not for windows 2000 ( it is available only for win xp and windows 2003)