Search results matching tag 'Classic ASP Error Messages IIS 6 Windows Server 2003'

Script Time Out with no source

kmwise — Mon, 16 Mar 2009 14:37:35 GMT

I get the following error in my application log but can't figure out the source?

Event Type: Warning
Event Source: Active Server Pages
Event Category: None
Event ID: 9
Date:  3/16/2009
Time:  1:22:38 AM
User:  N/A
Computer: My Web Server

Description:
Warning: IIS log failed to write entry, Script timed out. The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeout or by changing the value in the IIS administration tools..

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Is there a maximum number of variables that can be used in a VBScript / ASP page?

Hobbes23 — Sun, 11 Jan 2009 08:52:14 GMT

I have an error that recently came up as I was adding more code to a large application written in VBScript in the classic asp.
After some testing it seems to me that it has an issue with the number of variables used in my script. Since all pages are linked by using includes, and all processing and displaying is done through the same root asp page, it is thousands of lines long and could have this many variables I guess.
Here is the error message I get:
Microsoft VBScript runtime error '800a0006'

Overflow: '[number: 32771]'

/default.asp, line 519

the line 519 is actually after the server has processed thousands of lines in other files. Line 519 is actually blank, and I'm not sure why it even says that line. Made it really difficult to narrow down the actual issue's source.

but when I remove a small displaying of a variable, even that triggers the error. And removing a variable from my code seems to decrement the number displayed in the error after number.

Any ideas? Is there somewhere or somehow for this max limit to be increased?
-Peter

Active Server Pages, ASP 0129 (0x80004005)

Kapil007 — Fri, 19 Dec 2008 08:08:39 GMT

Hi,

I am facing this problem 2nd time the first time i faced this problem and i had formatted my system to solve this problem can some body help me. the below error facing when i am trying to view preview the .asp page from dreamweaver.

HTTP 500.100 - Internal Server Error - ASP error
Internet Information Services

Technical Information (for support personnel)

Error Type:
Active Server Pages, ASP 0129 (0x80004005)
The scripting language 'JAVASCRIPT' is not found on the server.
/unistone/index.asp, line 1
Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; InfoPath.2)
Page:
GET /unistone/index.asp

Thanks
Regards

Kapil

Error calling a ATL function from ASP page

maxblog — Fri, 17 Oct 2008 06:18:20 GMT

Hi All

I made an MFC app and then added an atl object to it and expose an interface. I then register the tlb file and call its functions from an ASP page.

I use Server,CreateObject to create the my C++ object which is fine and it gets created.

But when I call one of its function I get this error messagbox :

The instruction at "0x--------" referenced memory at "0x0------", the memory could ... 'Memory Cannot be read'

Could you please help me and tell me what is wrong?????

Thanks in advance

No ASP Error Messages from IIS 6.0 on Windows Server 2003

billappledorf — Mon, 29 Sep 2008 18:44:01 GMT

The shop I am working in uses Classic ASP on IIS 6 and Windows Server 2003.

About a week ago the familiar “VBScript Error . . . [filename] [line number]” error messages disappeared, and now page processing halts on errors with nary a whimper. Our network administrator says that “nothing has changed”, so I am thinking maybe a behind-your-back Windows Update installed some code on our server that is causing this.

A co-worker has admitted to having installed Visual Web Developer 2005 Express Edition on the server in question. Express Edition was subsequently uninstalled, but we are still not seeing any ASP error messages.

We are clueless as to how to diagnose this problem and have a mountain of ASP code to maintain.

Do you have any more insight into this problem than has been offered in the few posts out there (most of which reference IIS 7, which we do not use) regarding this?

Thanks.