Global ASA Not Firing When Visual InterDev Made IIS 4.0 Application

This article was previously published under Q188715
This article has been archived. It is offered "as is" and will no longer be updated.
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 7.0 running on Microsoft Windows Server 2008. IIS 7.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:For more information about IIS 7.0, visit the following Microsoft Web site:
SYMPTOMS
After creating a new application with Visual InterDev on InternetInformation Server 4.0 (IIS), the code in the Global.asa for thisapplication does not execute. A common symptom is while an administratoris logged into the IIS 4.0 computer, applications are created successfully,and when an administrator is not logged into the IIS computer, projectsare not created as applications.
CAUSE
If the virtual directory that contains the Global.asa is not set as anApplication Root, the code in the Global.asa will not be executed. VisualInterDev will be unable to create an application root if the MicrosoftTransaction Server (MTS) system package logon identity is set to"Interactive user - the current logged on user" and no one is currentlylogged on or the current logged on does not have the proper permissions tocreate an MTS package.
RESOLUTION
During the installation of Internet Information Server 4.0, a user canspecify the account for MTS sessions to run under. By default, theInteractive User is specified. What this means is that when there is noInteractive User (for example, an administrator is not logged onto the Webserver), administrative operations that require authentication, such ascreating an Application Root, fail.

Use the following steps to resolve existing problems:
  1. Bring up the Microsoft Management Console (MMC).
  2. Right-click the directory that contains the Global.asa that is not firing and select "properties."
  3. Select the Directory or Virtual Directory tab.
  4. Click the Create button to establish this directory as anapplication root.
While the above steps will resolve existing problems, you can use thefollowing steps to prevent future problems:
  1. Bring up the MMC for the server.
  2. Expand "Microsoft Transaction Server."
  3. Expand "Computers."
  4. Expand "My Computer."
  5. Expand "Packages Installed."
  6. Right-click "System" and bring up the Property page.
  7. On the Identity tab, change from the interactive user to a user thatis an administrator* on the machine.
  8. Close the Property page.
  9. Reboot.
*Following are steps to create an account to use for the MTS SystemPackage:

Follow these steps to use the user manager:
  1. Create a new local group and name it MTSAdministrators.
  2. Create a new user and name it MTS Administrator.
  3. Make the new user a member of the both the Administrators group andthe MTS Administrators group,
  4. Give the new user the advanced user right to log on as a service.
For more information on how to configure the system package account, seethe Internet Information Server 4.0 product documentation under GettingStarted Release Notes for Microsoft Transaction Server
REFERENCES
For more information about application settings, see the "ConfiguringApplications" topic in the Windows NT 4.0 Option Pack onlinedocumentation.

For the latest Knowledge Base articles and other support information onVisual InterDev and Active Server Pages, see the following page on theMicrosoft Technical Support site:

Properties

Article ID: 188715 - Last Review: 02/23/2014 01:09:49 - Revision: 8.1

  • Microsoft Internet Information Server 4.0
  • Microsoft Visual InterDev 1.0 Standard Edition
  • Microsoft Visual InterDev 6.0 Standard Edition
  • kbnosurvey kbarchive kbprb KB188715
Feedback