glenramsey
asked on
global.asa changes not taking effect
Using NT4 IIS.
Whenever we make changes to global.asa the changes do not show through the browser.
The only way to get changes to take effect is to reboot the server.
erk! has anyone ever had this under NT?
Whenever we make changes to global.asa the changes do not show through the browser.
The only way to get changes to take effect is to reboot the server.
erk! has anyone ever had this under NT?
Try to stop and start IIS.
ASKER
yep, tried that. tried restarting the server - still no joy.
we are now getting all files acting like this - if you make a change you do not see it through the browser
we are now getting all files acting like this - if you make a change you do not see it through the browser
What service pack are you on?
To use the Global.asa file after applying SP4, ensure that the file is in an application root folder. This is a change from the implementation in the Windows NT Option Pack, in which Global.asa was mistakenly processed from within a virtual directory.
The Global.asa file specifies event scripts and declares objects that have session or application scope. In the Windows NT Option Pack, the file Asp.dll processed Global.asa from the lowest defined virtual directory. This has been changed in SP4. After SP4 is installed, customers who are using Global.asa may need to make changes to IIS for the file to work properly. For more information, see the "Global.asa Reference" topic in the Windows NT Option Pack online documentation.
To ensure that Global.asa is available to Asp.dll after applying SP4, folders that contain Global.asa files should be marked as applications. For more information, see the "Creating Applications" topic in the Windows NT Option Pack online documentation.
To use the Global.asa file after applying SP4, ensure that the file is in an application root folder. This is a change from the implementation in the Windows NT Option Pack, in which Global.asa was mistakenly processed from within a virtual directory.
The Global.asa file specifies event scripts and declares objects that have session or application scope. In the Windows NT Option Pack, the file Asp.dll processed Global.asa from the lowest defined virtual directory. This has been changed in SP4. After SP4 is installed, customers who are using Global.asa may need to make changes to IIS for the file to work properly. For more information, see the "Global.asa Reference" topic in the Windows NT Option Pack online documentation.
To ensure that Global.asa is available to Asp.dll after applying SP4, folders that contain Global.asa files should be marked as applications. For more information, see the "Creating Applications" topic in the Windows NT Option Pack online documentation.
Does the browser on the IIS server itself show these changes (logged on as administrator) ?
did you allow caching of asp files? we removed that and specifically added the cachetime=0 to all asp files to keep it from happening.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.