Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 230169 - Last Review: February 22, 2007 - Revision: 1.2
Users are unable to open or create Web folder for restricted FrontPage Web
This article was previously published under Q230169
After you create a FrontPage Web that is set to
Only registered users have browse and you add an account with Author or Administer permission,
users cannot create a Web Folder for this Web or open the Web in FrontPage 2000
or any other Microsoft Office 2000 application. This problem occurs for IIS Web
servers running version 4.0.2.2717 of the FrontPage 2000 Server Extensions. The
user receives multiple authentication dialogs that never authenticate, and
eventually, one of the following error messages occurs:
You do not have permission to access this Web Folder location.
You are not authorized to perform the current
operation.
The problem occurs because when the Web is set to
Only registered users have browse, the Everyone group is removed from the access control lists on
the Web, and access to _vti_pvt is restricted. In this case, FrontPage fails to
write the Network and Interactive groups to the _vti_pvt folder. This
restriction prevents the valid user from opening the Web or creating a Web
Folder because access to the configuration files in _vti_pvt are required in
order to perform the operation.
To work around this problem, add the Network and
Interactive groups to the _vti_pvt folder. This is achieved by performing a
Check Server Extensions. On the IIS 4.0 Web server where the Web was created,
do the following:
- On the IIS 4.0 Web server, click Start, point to Programs, point to Windows NT 4.0 Option Pack, point to Microsoft Internet Information Server, and then click Internet Service Manager.
- Under Internet Information Server, select the computer
name, and click the Virtual Server where the restricted subweb
resides.
- Right-click the Virtual Server, point to Task, and click Check Server Extensions. When asked to tighten security as much as possible for all
FrontPage Webs, click Yes.
- After you complete the Check Server Extensions, the Web
will be accessible by the user. Also, if the permissions for the _vti_pvt
folder for the Web are viewed in Windows Explorer, the Network and Interactive
groups are listed.
To avoid fixing this problem for other new subwebs, use
the following steps:
- Open the root Web for the Virtual Server in
FrontPage.
- On the Tools menu, point to Security, and click Permissions.
- On the Groups tab, click Everyone, click Remove, and then click OK.
- Click Tools, click Security, and then click Permissions. On the Users tab, select Everyone has browse access and click OK.
- When permissions are propagated to new subewbs, the new
permissions on the root Web are initially inherited. This step helps to ensure
the correct permissions are inherited when creating a new subweb.
Microsoft has confirmed
that this is a problem in the FrontPage 2000 Server Extensions.
APPLIES TO
- Microsoft FrontPage 2000 Server Extensions
| kbpermissions kberrmsg kbweb kbopenfile kbbug kbpending KB230169 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate