FP2000: "Cannot Open File" Error Message When Opening or Publishing Web (264954)

RESOLUTION

To resolve this issue, follow these steps:

1. Uninstall FrontPage 2000 Server Extensions.
2. Assign full control access rights to the Administrators and System groups in the document root folder and subfolders.
3. Assign Log on locally and Access this computer from network rights to the user account experiencing this behavior:
   1. Click Start, point to Programs, and then point to Administrative Tools (Common).
   2. Click User Manager for Domains.
   3. In the User Manager dialog box, click User Rights on the Policies menu.
   4. In the User Rights Policy dialog box, click to select the Access this computer from network check box in the Right box.
   5. Determine whether the user account experiencing this behavior is in the Grant To box.
   6. If the user account is not in the Grant To box, click the Add button.
   7. In the Add Users and Groups dialog box, select the user account, and then click Add.
   8. Click OK.
   9. In the User Rights Policy dialog box, click to select the Log on locally check box in the Right box.
   10. Determine whether the user account experiencing this behavior is in the Grant To box.
   11. If the user account is not in the Grant To box, click the Add button.
   12. In the Add Users and Groups dialog box, select the user account, and then click Add.
   13. Click OK.
   14. Click OK in the User Rights Policy dialog box.
   15. In the User Manager dialog box, click Exit on the User menu.
4. Reinstall FrontPage 2000 Server Extensions.
5. Open the root web in FrontPage 2000.
6. On the Tools menu, point to Security, and then click Permissions.
7. In the Permissions dialog box, click the Users tab.
8. Click to select the Everyone has browse access check box, click the Apply button, and then click OK.

For additional information about assigning full control access rights to the Administrators and System groups in the document root folder and subfolders, click the article number below to view the article in the Microsoft Knowledge Base: