I have an asp page that displays the results in Excel in the browser.
It has about 40 columns and sometimes records can grow upto 1100.
For small number of records I do not get any error messages or displays
the result in Excel format properly. But for the higher number of
records even if the program runs for all day it hangs up and shows
nothing.
In the asp program I have many if and then statement as well as big
loop.
My question is how can I solve this problem? Do I have to look into the
web server memory and other configuration settings? Or is there a
maximum size limit in Excel.
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?
what I should be looking at when looking for a memory leak.. Using Process Explorer by SysInternals, and they have a Working Set and a Virtual Size memory column. Which one should I be looking at?
I'm using Windows 2000 server n IIS I'm Using FileSystemObject of ASP in Server Every File and Folder has 2 Size when we get properties of any 1 actual size and Size on Disk.now my problem is when i get the file size from ASP object it give Size value but when i try to get folder size it gives size on disk and both values are different.
I'm creating a size to access limited size to upload files so i just check the folder size and then get size for those which are going to update by user then i will less those size to actual folder size to get remaining size.
We are receiving an error in our ASP website that used to run fine on our old servers but seems to be struggling on our new ones, I'm wondering if you've seen this error before?
Microsoft Cursor Engine error '8007000e'
Out of memory.
/oob/activities/default.asp, line 470
The last line that shows where the error happening is different on every page but it appears at the first database connection on each page.
The only way to get rid of the error and get the site working again is to recycle the application pool for the site (or restart IIS).
We have two servers, one running IIS and the other running MSSQL 2005. Both are the following specs: Code:
I think I already know the answer ("NO"), but I figured I'd ask anyway:
Is there a way to populate a SQL-like object entirely in memory, without having to save it in a SQL-like environment like MySQL, MS-SQL, or Access?
I'd like to take the contents of some CSV's and dump them into a virtual SQL table, and then call from that table using a SQL statement ("SELECT * FROM VirtualTable WHERE Foo='Bar'"). I know that in .NET I could use a data-grid to do basically that, but I was wondering if there was a classic ASP solution.
I am getting an ASP error.. that tells the server it is OUT OF MEMORY.then the server displays a message about the DLLHOST.exe and it waits for an "OK" from me.after hitting OK... it goes back to working fine.BUT, while the notification is up on the screen.the website is NOT AVAILABLE.that is the message that visitors get when they try to get to the website.so, is there a way I can tell the system to SKIP the notification .andmjust restart the service.
What memory is the issue here.I am assuming this memory error is coming from an INFINITE LOOP or something.from one of my ASP pages. so, I would imagine the best move would be to get RID of the "On Error Resume Next" code at the top of my pages.. to try and isolate the problem?
I'm having a problem that I can only attribute to something that I don't know about ADO. I am using an ADODB.Connection with .CursorLocation = 3 since I am using MSSQL with text fields.
I am running a large set of 4 LEFT JOINS (5 tables in all). Currently my recordset is returning 168 rows and 23 colums. After looping through the ADO connection 27 times (creating a pdf report for users to print) the data goes nutz. I have tried using different inputs and no matter what on the 27th time is stops.
I am trying to write a search script in my spare time at work. We have a knowledge base consisting of 200+ .mht files. My script was working ok when I was testing it on just a few files but I am getting out of memory errors trying to search through the whole KB. Here is the search code:
am just wondering is there a easier way to release all the memory after the program is done?or do I need to set all my variable = nothing one by one at the end of my code?
We've got this problem on our site where slowly eats virtual memory until IIS stops serving pages...
Restarting the IIS process fixes the problem, until the next time it reaches that point. I've made sure all our ADO objects are being closed and set = Nothing. I don't know what else could eat up all that memory...
Had developed a webpage to refresh automatically from one ASP page to another, with the feature of displaying local data that is actively poll & inserted from other remote database servers. The local server is using IIS & Microsoft SQL 2000. I have the problem of "Out of Memory at line 30" after the ASP page has ran for 13 hours, at client machines that is connecting to the server hosting the ASP. However by closing the Internet Explorer and re-open the ASP page, the problem is temporary resolved until another 13 hours later. I think i've had the server objects set to nothing, and had put all queries into sub. I couldn't think of other solution for the problem...
Is duplication of sub affecting the performance? Any setting to be done on server, e.g. IIS / SQL? I've attached the ASP file.
Are there any tools to test asp code on memory leaks. Or the took that will monitor IIS server against specific asp-page in order to find mem leaks on in.
I am trying to beef-up the security when passing data between pages. I am currently using the following code to navigate between some of my pages.
<a href="javascript: GetFormValue(FRMTRANSFERS.TXTHOSPITALID,'ADDPATIEN T');"> <SCRIPT LANGUAGE="JavaScript"> function GetFormValue(FField,StrPage) { var myField = FField var myNumber = myField.value self.location = StrPage + ".asp?ID=" + myNumber; } </SCRIPT>
I would rather use cookies to do this but i need to know if you can create a cookie that doesn't get written to the harddrive. I can't use session variables as i can't write then in Javascript - at least i think not -
I have a page which sends a query to an DB2 using an ODBC. The results are then written to a text file. I am unable to write directly to the users drive because of permissions.
The problem I have is that when the query set becomes too big, I get error '8007000e' Not enough storage is available to complete this operation. The query is returning 100, 000 records or more. So my question is how do I handle this? Somebody had suggested to me to chunk the data. Code:
I get the following error message from an ASP page that we have:
METHOD: POST ERROR DESCRIPTION: 007~ASP 0100~Out of memory~Unable to allocate required memory. ERROR NUMBER: -2147024882 ERROR SOURCE: Response object
Does anyone out there have any ideas? Please let me know if you need any more information ... I am not sure why this message has suddenly started to pop up.
I checked the system logs and cannot see any particular memory loss related message so I don't know.
I have found this message in Event Viewer on my Windows 2000 server.
Error: File/Test/upload/upload.asp Line 85 Out of memory. Unable to allocate required memory..
It seems to be the cause of a problem I have had uploading and downloading files through an ASP page using Binary Stream Objects. Anyone got any ideas about how to solve this?
I have a problem with a bit of asp used in a date selection box. It is supposed to get the right days and dates and then list them in the select box for up to a week ahead. The error i get is Out Of Memory specifically the line reading:
I'm creating some menus based on a recursive menu script I got from here
I have modified it to use a SQL database as well as a jquery nested menu which works similarly to suckerfish dropdowns.
What I want the script to do is to recursively go through the list and when there is a child display it. My version works just fine the first go around but then fails once it's called a second time.
I can't show you the link because it's on our internal server, but here is my code:
I am getting the following error from my ASP application: Microsoft VBScript runtime error '800a0007'
Out of memory: 'Server.CreateObject'
It always (as far as i have observed) occurs when i try to create a new ADODB.connection object in my cCon helper function (opening a connection and returning it):
Function cCon() Dim cnRet set cnRet = server.createobject("ADODB.Connection") 'This is where the error is thrown cnRet.connectionstring = GLB_CONSTR_DB cnRet.open Set cCon = cnRet End Function
The page that errors will typically call this function 6- 10times from different functions which handle their connections in this way: Code:
I have a huge web site mixed ASP and ASP.NET and MSSQL. I am using hosting provider who set my site to use no more than certain amount of memory. Some times the site gives error server down because the server starts to freee up the memory when it reaches the maximum. Please give me some advices how to track the leeking memory. I suppose it's because of some unclosed db connections.
We are doing a stability test on our application to prepare for Microsoft SQL Server 2000 certification, and we found a memory leak, but we cannot find its source and fix it.
We use an ASP page written in JScript that connects to Analysis Services 2000 using ADOMD and retrieves data from it (this is a very simplified version of our real application that we created just to test the memory leak), see the code below.
We are using Microsoft Application Center Test to run this page, and Performance Monitor to monitor the Memory/Committed Bytes and Processor usage of our web server. The Memory/Committed counter slowly increases over time, which indicates a memory leak, right? The Private Bytes for the InetInfo process remain stable.
Our setup is a web server running Windows 2000 and Analysis Services on a different server running Windows 2000. The application Center Test is running from another computer. We also tried using a web server running Windows XP Pro instead of Win2000, with similar results.
Using PerfMon, we monitor the number of Analysis Services connections, and this number remains stable, so the memory leak doesn't seem to be due to an ever increasing number of AS open connections.....
Is there a way of performing an sql query and then call it again from memory rather than having to execute the query again?
As We have a few pages which gets data from a long query but then depending on user interaction could get recalled several times but with the data still the same.
Can this be the reason for huge memory expansion ? Doesn't this script free memory of the object it had created?
sub createCOMobject() set obj1 = createObject("object1") dim flag = 1 useObject flag,obj1 end sub ---------------------------------- sub useObject (flag, byRef obj1) .... set obj1 = Nothing end sub ....
We are running asp (not asp.net) and vb com dll web sites on a machine which also has sql server 2000 sp3a running and uses Windows Server 2003. We recently migrated from Windows 2000 (same database) where we had no problems. However on the new machine, despite much being much more powerful and having the same usage, the box is periodically grinding to a halt. The cause seems to be sql server using excessive amounts of memory, it steadily builds up to after a reboot to a high level. This seems to point in the direction of a memory leak, is anyone aware of any such problems with asp/sql server on windows 2003 and how to diagnose/fix them. I am aware of some unclosed connections in the asp code and objects that have not be set to nothing but this did not seem to cause a problem in the old machine and it is not practical to fix them all in the short term. I thought it might be unclosed connections although when I looked at SQL Server:General Statistics and User Connections I did not seem to see a large or increasing number of connections.
I am using ASP code to auto-generate a gallery based on files within a directory structure and I got it to work a while back. Lately I've been consistently receiving "Out of Memory" errors when I access that module. I haven't made any drastic changes to my system so I can't exactly figure out what subtle changes if not inherent in the code flaw is causing this ...
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.)
I am using traditinal asp in IIS6 and seem to be experiencing memory leaks problems that I did not have or at least did not seem to notice as much when I was running the same code under IIS5.
There may beunclosed connections/recordsets and/or connections/recrodsets that have not be set = nothing in the code. Two questions
1. Is IIS6 less forgiving of this?
2. If you do not close recordset or connection objects or set them equal to nothing is there some sort of garbage collection going on in asp that will release the memory anyway.
