|
 |
 |
 |
|
Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms
of Use |
Trademarks
Article ID: 260159 - Last Review: February 19, 2007 - Revision: 1.2 "An error occurred accessing your FrontPage web files" error message when you create a new subweb or view Permissions in FrontPage 2000This article was previously published under Q260159 In FrontPage, when you point to Security on the Tools menu and then click Permissions, or if you try to create a new subweb, you may receive the
following error message: An error occurred accessing
your FrontPage web files. Authors - if authoring against a web server, please
contact the webmaster for this server's site. WebMasters - please see the
server's system log for more details. In the Event Viewer on the
server, the following error messages appear: Microsoft
FrontPage Server Extensions:
(OS Error #-1073741795 Message: exception
occurred at 0x00c00982)
-and-
Microsoft FrontPage Server Extensions:
http://servername - Error #80002 Message: Unrecognized Windows exception
(0xc000001d)
-and-
Microsoft FrontPage Server Extensions:
Received empty response from Microsoft FrontPage Server Extensions
You may also receive the following error message when you try to create a new
project in Microsoft Visual InterDev: An unexpected
error occurs, accessing your web files. See the server's System
Event log for more information. These error messages appear because certain accounts in the
Access Control Lists (ACLs) are deleted, or the accounts' friendly names are
not resolvable from their security IDs (SIDs). This problem can occur if the
Web server is removed from a domain after domain accounts are added to the
permissions on the Web content. In this case, the Web server cannot contact the
domain controller to resolve the SID. To resolve this problem, you can rejoin the domain or
disable accounts rather than deleting them. If you cannot rejoin the domain, you must work around this
problem by removing the accounts from the permissions. This usually involves
resetting the permissions for the entire site. To do that, follow these steps.
NOTE: Because there are several versions of Microsoft Windows, the
following steps may be different on your computer. If they are, see your
product documentation to complete these steps. - Right-click Start and then click Explore.
- Locate the folder that contains your Web content, and then
right-click that folder.
- Click Properties.
- Click the Security tab.
- Look for accounts that do not display a friendly name but
instead display something like the following:
S-1-5-21-124525095-708259637-1543119021-15767
- Select the unresolved accounts or groups, and then click Remove.
Usually it is best to remove all accounts but leave
the SYSTEM account with Full Control and the local Administrators group with Full Control. - Select the Apply to all subfolders and
files check box, and then click OK.
- Open the Web in FrontPage and re-add the accounts that you
want to use. To do this, point to Security on the Tools menu, and then click Permissions.
- On the Users tab, set the browse access by selecting the appropriate button at
the bottom of the dialog box.
- Click OK.
NOTE: If the preceding workaround does not resolve this problem,
locate and delete unresolved SIDs in Users and Groups:
- Open Users and Groups as follows:
- On a Microsoft Windows NT 4.0-based computer, from the Start menu, point to Programs, point to Administrative Tools, and then click Users and Groups.
- On a Windows 2000-based computer, from the Start menu, point to Programs, point to Administrative Tools, and then click Computer Management. Users and Groups appears as a node under System Tools.
- Open each group to see the list of its members, and delete
any unresolved SIDs.
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
Problems caused by unresolved accounts can appear in many
ways, not just in FrontPage. To determine whether you have unresolved accounts
in file permissions, follow these steps:
- Right-click Start and then click Explore.
- Navigate to the folder that contains your Web content, and
right-click that folder.
- Click Properties.
- Click the Security tab. Look for accounts that do not display a friendly name but
instead display something like the following:
S-1-5-21-124525095-708259637-1543119021-15767
If you see something like this identifier, there is a problem
resolving the name for that account. It is possible that the domain is down, or
that the account was deleted rather than disabled.
For additional information, click the article number below to
view the article in the Microsoft Knowledge Base: 277752Â
(http://kbalertz.com/Feedback.aspx?kbNumber=277752/EN-US/
)
Security Identifiers for Built-In Groups Are Unresolved When Modifying Group Policy
APPLIES TO- Microsoft FrontPage 2000 Server Extensions
| kbaccounts kbpermissions kbprb kberrmsg kbpending KB260159 |
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
|
|
 |
|
 |
|
|
|
| |