Board index » Web Programming » Execute Permissions being reset to "none".

Execute Permissions being reset to "none".

Web Programming350
I am running a website in IIS5.0. The site has some ASP content for database

lookup and such. On a random basis, sometimes in 30 minutes, sometimes every

48 hours, the execute permissions get reset to "none" from "scripts and

executables". I reset it to "scripts and execs" and eventually, it gets

changes back to "none". We've tried to isolate what activities are taking

place when this occurs, but it happens so randomly, it's hard to get a fix on

it. Once it get's reset to "none", the ASP scripts stop working, of course.



Does anyone have any ideas on what can be causing this? Can an ASP script

change this property of a web inadvertently? Or is the Management Console

Directory Tab the only way to change this attribute? Any ideas are

appreciated. I have read other threads on this type of issue and have

stopped/restarted IIS after setting the permissions, so they persist. Thx.



Curt


-
 

Re:Execute Permissions being reset to "none".

Is this on the entire website? Or just a particular folder (eg the /bin

folder)?



These settings are stored in the IIS metabase, so anything that can edit the

metabase (including the management console) can change those settings

(assuming it has sufficient privileges on the server).



Cheers

Ken



"Curt Anderson" <CurtAnderson@discussions.microsoft.com>wrote in message

Quote
I am running a website in IIS5.0. The site has some ASP content for

database

lookup and such. On a random basis, sometimes in 30 minutes, sometimes

every

48 hours, the execute permissions get reset to "none" from "scripts and

executables". I reset it to "scripts and execs" and eventually, it gets

changes back to "none". We've tried to isolate what activities are taking

place when this occurs, but it happens so randomly, it's hard to get a fix

on

it. Once it get's reset to "none", the ASP scripts stop working, of

course.



Does anyone have any ideas on what can be causing this? Can an ASP script

change this property of a web inadvertently? Or is the Management Console

Directory Tab the only way to change this attribute? Any ideas are

appreciated. I have read other threads on this type of issue and have

stopped/restarted IIS after setting the permissions, so they persist.

Thx.



Curt





-

Re:Execute Permissions being reset to "none".

Yes, I set it at the website level (right click on the web, select

properties, select directory tab, set execute permissions, apply to all

directories).



Is there a way that I can determine what/who is changing it? Is something

logged in the system or application log?



Thanks.



cja



"Ken Schaefer" wrote:



Quote
Is this on the entire website? Or just a particular folder (eg the /bin

folder)?



These settings are stored in the IIS metabase, so anything that can edit the

metabase (including the management console) can change those settings

(assuming it has sufficient privileges on the server).



Cheers

Ken



"Curt Anderson" <CurtAnderson@discussions.microsoft.com>wrote in message

news:4EFB4614-8140-4843-BFE9-B09238E90ACC@microsoft.com...

>I am running a website in IIS5.0. The site has some ASP content for

>database

>lookup and such. On a random basis, sometimes in 30 minutes, sometimes

>every

>48 hours, the execute permissions get reset to "none" from "scripts and

>executables". I reset it to "scripts and execs" and eventually, it gets

>changes back to "none". We've tried to isolate what activities are taking

>place when this occurs, but it happens so randomly, it's hard to get a fix

>on

>it. Once it get's reset to "none", the ASP scripts stop working, of

>course.

>

>Does anyone have any ideas on what can be causing this? Can an ASP script

>change this property of a web inadvertently? Or is the Management Console

>Directory Tab the only way to change this attribute? Any ideas are

>appreciated. I have read other threads on this type of issue and have

>stopped/restarted IIS after setting the permissions, so they persist.

>Thx.

>

>Curt







-