FP2002: Error Message: Could Not Initialize Role Upgrading Server Extensions

Article translations Article translations
Article ID: 298968 - View products that this article applies to.
This article was previously published under Q298968
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
Expand all | Collapse all

SYMPTOMS

When you install or upgrade to FrontPage 2002 Server Extensions, you receive one of the following error messages:
Error: Could not initialize role 'Admin'.
-or-
Error: Could not initialize role 'Browser'.
The event viewer contains the following error messages
Microsoft FrontPage Server Extensions:
Error #e0064 Message: Error creating group "OWS_1234567890_admin"

Microsoft FrontPage Server Extensions:
(OS Error #2296 Message: )
-or-
Microsoft FrontPage Server Extensions:
Error #e0064 Message: Error creating group "OWS_1234567890_browser"

Microsoft FrontPage Server Extensions:
(OS Error #2296 Message: )
where 1234567890 is a number specific to the site.

CAUSE

This problem can occur when you attempt to upgrade or extend a site on a Backup Domain Controller or any other system that restricts the creation of local groups. When you extend a site, the extensions create a group for admin and automatically add the user account to administer the site. Because the server does not allow for the creation of local groups, the error message appears.

WORKAROUND

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To work around this problem, prevent the FrontPage Server Extensions from creating and using local groups to access the Web site. To do this, follow these steps:
  1. On the Windows Start menu, click Run.
  2. In the Open box, type Regedt32.exe and click OK.
  3. Select the following subkey:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\All Ports
  4. On the Edit menu, click Add Value.
  5. In the Value Name box, type NoMachineGroups; in the Data Type box type REG_SZ. Click OK.
  6. In the String Editor dialog box, in the String box, type 1 and then click OK.
  7. On the Registry menu, click Exit.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

In Windows Registry, the NoMachineGroups value specifies whether roles are implemented as local machine groups. When this value is set to 1, local machine groups are disabled. To enable local machine groups, set NoMachineGroups to the devault value, 0 (zero). This value is a global property only. You must set this property before extending any virtual server.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
310932 FP2002: Where to Find the SharePoint Team Services Administrator's Guide

REFERENCES

For additional information about how to use the Event Viewer, click the article number below to view the article in the Microsoft Knowledge Base:
289508 OFFXP: How to Read Office Application Error Reporting Signature

Properties

Article ID: 298968 - Last Review: February 28, 2014 - Revision: 1.1
APPLIES TO
  • Microsoft FrontPage 2002 Server Extensions
Keywords: 
kbnosurvey kbarchive kbbug kbpending KB298968

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com