Why Is My Global.asa Not Being Fired?

I am having trouble getting my global.asa file to be read. Essentially, I work in an environment where I can set up my own web pages/applications on an IIS server, even though I don't have System Administrator access to the web server. That means I can save data to the web server through a Windows network drive, but I don't have access to IIS Manager (inetmgr) on the server--or anything like that. I have been talking to the System Admin people who do have this access to try to get them to set up the server to read my global.asa file. So far, I have checked my global.asa carefully for errors--there are no errors. I have told the System Admin people to create a Virtual Directory for my application--they have done this. My global.asa and the rest of my .asp files are in the this "virtual directory." This virtual directory exists well below the root directory of the server (I'm using made up directories names to illustrate my point):

http://www.mywebserver.com/directory 1/directory 2/directory 3/directory 4/MyApp

So my web application, its global.asa, and all the ASP files are in the directory "MyApp." There are multiple global.asa files on the web server. I know my global.asa is not being read because I am defining application/session values that are returning null values when printed in the browser using response.write. There is a global.asa file in the root directory of the server
http://www.mywebserver.com/global.asa). This is the global.asa file that is being read by my application! I have verified this through retrieving an application variable that is defined in that global.asa file. There is obviously a problem with the way my application is defined in IIS. The server is a Windows 2000 Server running IIS 5.0. What should I tell the System admin people to do to fix this problem? The "virtual directory" does point to the right path, but the web server refuses to read my global.asa when I execute my web app.