2. ASPRunnerPro General questions
  3. Microsoft VBScript compilation error '800a03e9'
This topic is locked

Microsoft VBScript compilation error '800a03e9'

 		8/5/2010 11:43:01 AM
ASPRunnerPro General questions
M
 mfred author

Starting about 2 months ago, we get the following error in a couple of applications that I created in ASPRunner 6.2. It occurs on 2-3 week intervals. People can log into the applications but the error occurs when I click on a menu link to a list page. The error persists until I reboot the server. We are analyzing the server but http://support.microsoft.com/kb/174634 indicates that it is a scripting issue. I ran a search in this forum and the issue does not appear to have been reported. But I am reporting the issue so that I can cover all the possible bases.
Microsoft VBScript compilation error '800a03e9'
Out of memory
..._list.asp line 0
A
 		ann 8/6/2010

Hi,
check this article:

http://dev.mysql.com/doc/refman/5.0/en/out-of-memory.html
M
 		mfred author 8/6/2010

I'm not using MySQL. The ASPRunenr applications with the issue connect to Access databases.
J
 		Jane 8/9/2010

Hi,
this error usually means that server does not have enough memory to store the query result (too many fields in the resulted query) or number of queries on the page is too large (there are some lookup fields in each record).

Try to turn on debug mode in the generated include/appsettings.asp file and reproduce this error.
W
 		webwork 8/10/2010



I'm not using MySQL. The ASPRunenr applications with the issue connect to Access databases.


see: http://databases.aspfaq.com/database/what-are-the-limitations-of-ms-access.html
W
 		webwork 8/10/2010



I'm not using MySQL. The ASPRunenr applications with the issue connect to Access databases.


another person had similar symptoms and..\

http://www.ozzu.com/programming-forum/urgent-help-needed-out-memory-error-t34016.html
Turns out it was disk fragmentation. I thought a "managed hosting" solution would take care of little things like that... heh.
The hard drive where the site files were located was at around 68% fragmentation. This was causing serious page file read/write problems that resulted in the ASP processor not being able to allocate enough internal resources to complete what would otherwise have been very basic ASP processing.
Defragmenting hard drives is something I always forget about... I don't know about other operating systems, but on Windows, massive fragmentation can eventually result in a serious system crash... Glad I was able to catch this when I did...