ASP – What IS GLOBAL.asa File

The Global.asa file is an optional file that can contain declarations of objects, variables, and methods that can be accessed by every page in an ASP application. All valid browser scripts (JavaScript, VBScript, JScript, PerlScript, etc.) can be used within Global.asa.

The Global.asa file can contain only the following:

  • Application events
  • Session events
  • <object> declarations
  • TypeLibrary declarations

Note: The Global.asa file must be stored in the root directory of the ASP application, and each application can only have one Global.asa file.

Events in Global.asa

In Global.asa you can tell the application and session objects what to do when the application/session starts and what to do when the application/session ends. The code for this is placed in event handlers. The Global.asa file can contain four types of events:

Application_OnStart – This event occurs when the FIRST user calls the first page from an ASP application. This event occurs after the Web server is restarted or after the Global.asa file is edited. The “Session_OnStart” event occurs immediately after this event.

Session_OnStart – This event occurs EVERY time a NEW user requests his or hers first page in the ASP application.

Session_OnEnd – This event occurs EVERY time a user ends a session. A user ends a session after a page has not been requested by the user for a specified time (by default this is 20 minutes).

Application_OnEnd – This event occurs after the LAST user has ended the session. Typically, this event occurs when a Web server stops. This procedure is used to clean up settings after the Application stops, like delete records or write information to text files.

A Global.asa file could look something like this:

<script language=”vbscript” runat=”server”>


sub Application_OnStart

””some code

end sub

sub Application_OnEnd

””some code

end sub

sub Session_OnStart

””some code

end sub

sub Session_OnEnd

””some code

end sub


Note: We cannot use the ASP script delimiters (<% and %>) to insert scripts in the Global.asa file, we will have to put the subroutines inside the HTML <script> tag.

<object> Declarations

It is possible to create objects with session or application scope in Global.asa by using the <object> tag.

Note: The <object> tag should be outside the <script> tag!



Parameter Description
scope Sets the scope of the object (either Session or Application)
id Specifies a unique id for the object
ProgID An id associated with a class id. The format for ProgID is [Vendor.]Component[.Version]


Either ProgID or ClassID must be specified.

ClassID Specifies a unique id for a COM class object.


Either ProgID or ClassID must be specified.


The first example creates an object of session scope named “MyAd” by using the ProgID parameter:

The second example creates an object of application scope named “MyConnection” by using the ClassID parameter:

The objects declared in the Global.asa file can be used by any script in the application:



You could reference the object “MyAd” from any page in the ASP application:



TypeLibrary Declarations

A TypeLibrary is a container for the contents of a DLL file corresponding to a COM object. By including a call to the TypeLibrary in the Global.asa file, the constants of the COM object can be accessed, and errors can be better reported by the ASP code. If your Web application relies on COM objects that have declared data types in type libraries, you can declare the type libraries in Global.asa.









Parameter Description
file Specifies an absolute path to a type library.


Either the file parameter or the uuid parameter is required

uuid Specifies a unique identifier for the type library.


Either the file parameter or the uuid parameter is required

version Optional. Used for selecting version. If the requested version is not found, then the most recent version is used
localeid Optional. The locale identifier to be used for the type library

Error Values

The server can return one of the following error messages:

Error Code Description
ASP 0222 Invalid type library specification
ASP 0223 Type library not found
ASP 0224 Type library cannot be loaded
ASP 0225 Type library cannot be wrapped

Note: METADATA tags can appear anywhere in the Global.asa file (both inside and outside <script> tags). However, it is recommended that METADATA tags appear near the top of the Global.asa file.


Restrictions on what you can include in the Global.asa file:

  • You can not display text that is written in the Global.asa file. This file can’t display information
  • You can not use the #include directive in Global.asa
  • You can only use Server and Application objects in the Application_OnStart and Application_OnEnd subroutines. In the Session_OnEnd subroutine, you can use Server, Application, and Session objects. In the Session_OnStart subroutine you can use any built-in object

How to use the Subroutines

Global.asa is often used to initialize variables.

The example below shows how to detect the exact time a visitor first arrives on a Web site. The time is stored in a Session variable named “started”, and the value of the “start” variable can be accessed from any ASP page in the application:

<script language=”vbscript” runat=”server”>


sub Session_OnStart


end sub


Global.asa can also be used to control page access.

The example below shows how to redirect every new visitor to another page, in this case to a page called “newpage.asp”:

<script language=”vbscript” runat=”server”>


sub Session_OnStart


end sub


And you can include functions in the Global.asa file.

In the example below the Application_OnStart subroutine occurs when the Web server starts. Then the Application_OnStart subroutine calls another subroutine named “getcustomers”. The “getcustomers” subroutine opens a database and retrieves a record set from the “customers” table. The record set is assigned to an array, where it can be accessed from any ASP page without querying the database:

<script language=”vbscript” runat=”server”>


sub Application_OnStart


end sub

sub getcustomers

set conn=Server.CreateObject(“ADODB.Connection”)


conn.Open “c:/webdata/northwind.mdb”

set rs=conn.execute(“select name from customers”)




end sub


Global.asa Example

In this example we will create a Global.asa file that counts the number of current visitors.

  • The Application_OnStart sets the Application variable “visitors” to 0 when the server starts
  • The Session_OnStart subroutine adds one to the variable “visitors” every time a new visitor arrives
  • The Session_OnEnd subroutine subtracts one from “visitors” each time this subroutine is triggered

The Global.asa file:

<script language=”vbscript” runat=”server”>


Sub Application_OnStart


End Sub

Sub Session_OnStart




End Sub

Sub Session_OnEnd




End Sub


To display the number of current visitors in an ASP file:







There are <%response.write(Application(“visitors”))%>

online now!




The ASP Response object is used to send output to the user from the server.

Reference : Dilip Kumar Jena ( )


3 thoughts on “ASP – What IS GLOBAL.asa File

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s