Error message when you install SQL Server 2005 on a Windows Server 2008-based RODC: "Failure creating local group SQLServer2005SQLBrowserUser$<ServerName>"

Article translations Article translations
Article ID: 947986 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

When you install Microsoft SQL Server 2005 on a Windows Server 2008-based read-only domain controller (RODC), you receive the following error message:
Failure creating local group SQLServer2005SQLBrowserUser$ServerName.
Additionally, the following error message is logged in the SQL Server Setup log file (SQLSetup0001_ComputerName_SQL.log):
Doing Action: Do_sqlGroup
PerfTime Start: Do_sqlGroup : Time Date
<Func Name='Do_sqlGroup'>
Failure creating local group SQLServer2005SQLBrowserUser$ServerName (50)
Error Code: 0x80070032 (50) Windows Error Text: The request is not supported.
Source File Name: sqlca\sqlsecurityca.cpp Compiler Timestamp: Time Date
Function Name: Do_sqlGroup
Source Line Number: 747
---- Context -----------------------------------------------
Setting status of unmanaged components and removing unmanaged resources
Error Code: 50
MSI (s) (94:38) [16:50:37:502]: I/O on thread 4052 could not be cancelled. Error: 1168
MSI (s) (94:38) [16:50:37:502]: I/O on thread 3244 could not be cancelled. Error: 1168
MSI (s) (94:38) [16:50:37:502]: I/O on thread 3676 could not be cancelled. Error: 1168
MSI (s) (94:38) [16:50:37:502]: I/O on thread 3740 could not be cancelled. Error: 1168
MSI (s) (94:38) [16:50:37:502]: I/O on thread 3056 could not be cancelled. Error: 1168
MSI (s) (94:38) [16:50:37:512]: I/O on thread 2728 could not be cancelled. Error: 1168
MSI (s) (94:38) [16:50:37:512]: I/O on thread 3200 could not be cancelled. Error: 1168
MSI (s) (94:38) [16:50:37:512]: I/O on thread 2716 could not be cancelled. Error: 1168
MSI (s) (94:38) [16:50:37:512]: I/O on thread 3064 could not be cancelled. Error: 1168
MSI (s) (94:38) [16:50:37:512]: I/O on thread 3988 could not be cancelled. Error: 1168
Note The SQL Server Setup log file is located in the %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\Log\Files folder.

CAUSE

This behavior occurs because you do not have Write permissions to add user groups on an RODC. An RODC is an exact replica of the primary domain controller.

STATUS

This behavior is by design.

Properties

Article ID: 947986 - Last Review: February 14, 2008 - Revision: 1.1
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Express Edition
  • Microsoft SQL Server 2005 Express Edition with Advanced Services
Keywords: 
kberrmsg kbexpertiseadvanced kbtshoot kbprb KB947986

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