|
Home > Archive > FrontPage Server Extensions for Windows > June 2006 > User management crashing server extensions?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
User management crashing server extensions?
|
|
| Benefits Anorak 2006-06-06, 1:20 pm |
| We are trying to establish what it is we keep doing that crashes the FP
server extensions on our server. We think perhaps the problem arises when we
delete a user from a password-protected subweb. We do this by opening the
remote site in FrontPage and managing users by going through tools/server.
Is there a known reason why deleting users can corrupt the server extensions,
or does this sound more like a unique problem with our server? Thanks for
any suggestions.
| |
| Mark Fitzpatrick 2006-06-06, 1:20 pm |
| Something I've found over the years is errors can creap into NTFS
permissions. Sometimes it happens when a service pack is applied as that
seems to have the server tweak permissions (or cause a new inheritance
check). What I've seen is that sometimes an odd permission is placed in the
root of the web, or in a directory that the subweb inherits from. The
extensions get stuck trying to work around this as it's an inherited item.
The permissions for FP can be very touchy at times, and someome can
inadvertantly lock down one of the accounts FP needs, or tweak a policy
somewhere. Although the circumstances that will make this happen will be
unique to your servers (ie: the user policies and permissions) the general
problem is not uncommon. Sometimes I've had to go as far as wiping out the
permissions on the web by resetting them to Everyone Full Control, adding my
admin account, setting everyone back down to browse, then tweaking things
from there. Sometimes I've gone as far as to adjust these within Windows
Explorer to ensure that whatever errant permission was there is definitely
removed. (don't forget to always make a copy of the web and place it
somewhere else on the server to make sure that the NTFS ACL security
descriptors you originally had are intact on a backup.
I appoligize if I'm not doing this description justice since it's been a
while since I've toyed with some of these permissions problems.
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage
"Benefits Anorak" <Benefits Anorak@discussions.microsoft.com> wrote in
message news:54B920E5-6DE8-461E-A094-F7444C57A1AC@microsoft.com...
> We are trying to establish what it is we keep doing that crashes the FP
> server extensions on our server. We think perhaps the problem arises when
> we
> delete a user from a password-protected subweb. We do this by opening the
> remote site in FrontPage and managing users by going through tools/server.
> Is there a known reason why deleting users can corrupt the server
> extensions,
> or does this sound more like a unique problem with our server? Thanks for
> any suggestions.
| |
| Benefits Anorak 2006-06-06, 1:20 pm |
| Thank you Mark - reassuring to know that we are not committing some dreadful
beginner's error!
"Mark Fitzpatrick" wrote:
> Something I've found over the years is errors can creap into NTFS
> permissions. Sometimes it happens when a service pack is applied as that
> seems to have the server tweak permissions (or cause a new inheritance
> check). What I've seen is that sometimes an odd permission is placed in the
> root of the web, or in a directory that the subweb inherits from. The
> extensions get stuck trying to work around this as it's an inherited item.
> The permissions for FP can be very touchy at times, and someome can
> inadvertantly lock down one of the accounts FP needs, or tweak a policy
> somewhere. Although the circumstances that will make this happen will be
> unique to your servers (ie: the user policies and permissions) the general
> problem is not uncommon. Sometimes I've had to go as far as wiping out the
> permissions on the web by resetting them to Everyone Full Control, adding my
> admin account, setting everyone back down to browse, then tweaking things
> from there. Sometimes I've gone as far as to adjust these within Windows
> Explorer to ensure that whatever errant permission was there is definitely
> removed. (don't forget to always make a copy of the web and place it
> somewhere else on the server to make sure that the NTFS ACL security
> descriptors you originally had are intact on a backup.
>
> I appoligize if I'm not doing this description justice since it's been a
> while since I've toyed with some of these permissions problems.
>
> Hope this helps,
> Mark Fitzpatrick
> Microsoft MVP - FrontPage
>
> "Benefits Anorak" <Benefits Anorak@discussions.microsoft.com> wrote in
> message news:54B920E5-6DE8-461E-A094-F7444C57A1AC@microsoft.com...
>
>
>
|
|
|
|
|