Failed to modify security permissions on WMI namespace

Hello everyone,
I am trying to install a SQL server 2005 on a cluster but It does not succeed.
At the end of the installation in Configuring components ... of SQL Server
database services step, I recive the following message :
"SQL Server Setup failed to modify security permissions on WMI namespace
\\.\root\Microsoft\SqlServer\ServerEvents\Instance Name. To proceed, verify
that the account and domain running SQL server Setup exist, that the account
running SQL Server Setup has administrator privileges, and that the WMI
namespace exists on the destination drive."
I verified the points mentioned in this message and everything is right but
I can not finish the installation.
Has anybody experienced something similar?
Thank you for your help.
Best regards,
Juanjo
Since you have provided no details, it would be very difficult for anyone to
provide anything but the most generic responses.
You might want to post the output of the setup logs to determine a more
precise failure issue.
Sincerely,
Anthony Thomas

"Juanjo" <Juanjo@.discussions.microsoft.com> wrote in message
news:F3ED7933-4BCE-4CE0-B35B-CC83AF479343@.microsoft.com...
> Hello everyone,
> I am trying to install a SQL server 2005 on a cluster but It does not
succeed.
> At the end of the installation in Configuring components ... of SQL Server
> database services step, I recive the following message :
> "SQL Server Setup failed to modify security permissions on WMI namespace
> \\.\root\Microsoft\SqlServer\ServerEvents\Instance Name. To proceed, verify
> that the account and domain running SQL server Setup exist, that the
account
> running SQL Server Setup has administrator privileges, and that the WMI
> namespace exists on the destination drive."
> I verified the points mentioned in this message and everything is right
but
> I can not finish the installation.
> Has anybody experienced something similar?
> Thank you for your help.
> Best regards,
> Juanjo
|||Anthony, thank you very much for your suggestion.
Here I enclosed a piece of my failed SQL 2005 installation. In this piece of
log appears the error I received (LEGATO is the instance name):
"Error Code: 29516
MSI (s) (20!70) [14:00:16:607]: Product: Microsoft SQL Server 2005 -- Error
29516. SQL Server Setup failed to modify security permissions on WMI
namespace \\.\root\Microsoft\SqlServer\ServerEvents\LEGATO. To proceed,
verify that the account and domain running SQL Server Setup exist, that the
account running SQL Server Setup has administrator privileges, and that the
WMI namespace exists on the destination drive.
Error 29516. SQL Server Setup failed to modify security permissions on WMI
namespace \\.\root\Microsoft\SqlServer\ServerEvents\LEGATO. To proceed,
verify that the account and domain running SQL Server Setup exist, that the
account running SQL Server Setup has administrator privileges, and that the
WMI namespace exists on the destination drive.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_WMISecurity
PerfTime Start: Do_WMISecurity : Mon Jan 22 14:00:16 2007
<Func Name='Do_WMISecurity'>
Configuring ACL for WMI namespace
\\.\root\Microsoft\SqlServer\ServerEvents\LEGATO
ACL:
(A;CI;CCDCLCSWRPWPRCWD;;;BA)(A;CI;CCDCRC;;;S-1-5-21-119559289-1840127793-336618761-622849)
<Func Name='SecureWMINamespace'>
CoSetProxyBlanket failed to switch security level to IMPERSONATE
Error value: 2147942487 (0x80070057)
Failed to connect to namespace
Error value: 2147942487 (0x80070057)
<EndFunc Name='SecureWMINamespace' Return='-2147024809' GetLastError='0'>
Error Code: 0x8007734c (29516)
Windows Error Text: Source File Name: sqlca\sqlwmisecurityca.cpp
Compiler Timestamp: Tue Aug 9 01:14:18 2005
Function Name: Do_WMISecurity
Source Line Number: 158"
Thank you.
Juanjo
"Anthony Thomas" wrote:

> Since you have provided no details, it would be very difficult for anyone to
> provide anything but the most generic responses.
> You might want to post the output of the setup logs to determine a more
> precise failure issue.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Juanjo" <Juanjo@.discussions.microsoft.com> wrote in message
> news:F3ED7933-4BCE-4CE0-B35B-CC83AF479343@.microsoft.com...
> succeed.
> account
> but
>
>
|||No, I have not yet seen this message.
Things I would check:
The account you logged in as has administrator privileges on both nodes.
That you typed in this account as the account with remote access.
That the default User Access Rights have not been overridden by Domain Level
GPOs.
Make sure you have sufficient free space on the system partition on all
nodes.
What version of the OS and SS2K5 are you installing?
Verify that the Local Domain Groups required by the setup program exist in
AD or the installation account has permission to create them during the
installation.
Take a look at this document:
http://support.microsoft.com/kb/910228/en-us
Sincerely,
Anthony Thomas

"Juanjo" <Juanjo@.discussions.microsoft.com> wrote in message
news:2F4A9A06-265A-4427-980E-64AEC5D1270B@.microsoft.com...
> Anthony, thank you very much for your suggestion.
> Here I enclosed a piece of my failed SQL 2005 installation. In this piece
of
> log appears the error I received (LEGATO is the instance name):
> "Error Code: 29516
> MSI (s) (20!70) [14:00:16:607]: Product: Microsoft SQL Server 2005 --
Error
> 29516. SQL Server Setup failed to modify security permissions on WMI
> namespace \\.\root\Microsoft\SqlServer\ServerEvents\LEGATO. To proceed,
> verify that the account and domain running SQL Server Setup exist, that
the
> account running SQL Server Setup has administrator privileges, and that
the
> WMI namespace exists on the destination drive.
> Error 29516. SQL Server Setup failed to modify security permissions on WMI
> namespace \\.\root\Microsoft\SqlServer\ServerEvents\LEGATO. To proceed,
> verify that the account and domain running SQL Server Setup exist, that
the
> account running SQL Server Setup has administrator privileges, and that
the
> WMI namespace exists on the destination drive.
> <Func Name='GetCAContext'>
> <EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
> Doing Action: Do_WMISecurity
> PerfTime Start: Do_WMISecurity : Mon Jan 22 14:00:16 2007
> <Func Name='Do_WMISecurity'>
> Configuring ACL for WMI namespace
> \\.\root\Microsoft\SqlServer\ServerEvents\LEGATO
> ACL:
>
(A;CI;CCDCLCSWRPWPRCWD;;;BA)(A;CI;CCDCRC;;;S-1-5-21-119559289-1840127793-336
618761-622849)[vbcol=seagreen]
> <Func Name='SecureWMINamespace'>
> CoSetProxyBlanket failed to switch security level to IMPERSONATE
> Error value: 2147942487 (0x80070057)
> Failed to connect to namespace
> Error value: 2147942487 (0x80070057)
> <EndFunc Name='SecureWMINamespace' Return='-2147024809' GetLastError='0'>
> Error Code: 0x8007734c (29516)
> Windows Error Text: Source File Name: sqlca\sqlwmisecurityca.cpp
> Compiler Timestamp: Tue Aug 9 01:14:18 2005
> Function Name: Do_WMISecurity
> Source Line Number: 158"
> Thank you.
> Juanjo
>
> "Anthony Thomas" wrote:
anyone to[vbcol=seagreen]
Server[vbcol=seagreen]
namespace[vbcol=seagreen]
verify[vbcol=seagreen]
WMI[vbcol=seagreen]
right[vbcol=seagreen]
|||I finally could have this SQL 2005 cluster installed. The cluster shared disk
from our SAN were not properly configured. These have been recreated.
Thank you very much for your help.
Best regards,
Juanjo
"Anthony Thomas" wrote:

> No, I have not yet seen this message.
> Things I would check:
> The account you logged in as has administrator privileges on both nodes.
> That you typed in this account as the account with remote access.
> That the default User Access Rights have not been overridden by Domain Level
> GPOs.
> Make sure you have sufficient free space on the system partition on all
> nodes.
> What version of the OS and SS2K5 are you installing?
> Verify that the Local Domain Groups required by the setup program exist in
> AD or the installation account has permission to create them during the
> installation.
> Take a look at this document:
> http://support.microsoft.com/kb/910228/en-us
> Sincerely,
>
> Anthony Thomas
>
> --
> "Juanjo" <Juanjo@.discussions.microsoft.com> wrote in message
> news:2F4A9A06-265A-4427-980E-64AEC5D1270B@.microsoft.com...
> of
> Error
> the
> the
> the
> the
> (A;CI;CCDCLCSWRPWPRCWD;;;BA)(A;CI;CCDCRC;;;S-1-5-21-119559289-1840127793-336
> 618761-622849)
> anyone to
> Server
> namespace
> verify
> WMI
> right
>
>

failed SQL Server Express installation

I have tried everything. The installation keeps failing and it seems to be a problem with WMI. Here is my installation summary and the error part of my wmidiag report. Can some one please help.

icrosoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Mon May 14 21:05:07 2007
PROHOMESTEVEMAC : The current system does not meet recommended hardware requirements for this SQL Server release. For detailed hardware requirements, see the readme file or SQL Server Books Online.
Machine : PROHOMESTEVEMAC
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.2047.00
Install : Successful
Log File : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_SQLSupport_1.log
--
Machine : PROHOMESTEVEMAC
Product : Microsoft SQL Server Native Client
Product Version : 9.00.2047.00
Install : Successful
Log File : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_SQLNCLI_1.log
--
Machine : PROHOMESTEVEMAC
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.2047.00
Install : Successful
Log File : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_SqlWriter_1.log
--
Machine : PROHOMESTEVEMAC
Product : MSXML 6.0 Parser
Product Version : 6.10.1129.0
Install : Successful
Log File : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_MSXML6_1.log
--
Machine : PROHOMESTEVEMAC
Product : SQL Server Database Services
Error : SQL Server Setup Failed to compile the Managed Object Format (MOF) file c:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
--
Machine : PROHOMESTEVEMAC
Product : SQL Server Database Services
Error : SQL Server Setup Failed to compile the Managed Object Format (MOF) file c:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
--
Machine : PROHOMESTEVEMAC
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.1.2047.00
Install : Failed
Log File : c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup Failed to compile the Managed Object Format (MOF) file c:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
Error Number : 29513
--

SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.

Time : Mon May 14 21:07:30 2007

List of log files:
c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_Core(Local).log
c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_SQLSupport_1.log
c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_SQLNCLI_1.log
c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_SqlWriter_1.log
c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_MSXML6_1.log
c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_SQL.log
c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_Datastore.xml
c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_.NET Framework 2.0.log
c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_Support.log
c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_Core.log
c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
c:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0027_PROHOMESTEVEMAC_SCC.log

28836 00:40:38 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
28837 00:40:38 (0) ** INFO: WMI ADAP status: .............................................................................................. 2.
28838 00:40:38 (0) ** => The WMI ADAP process is processing a performance library (2).
28839 00:40:38 (0) ** Some WMI performance classes could be missing at the time WMIDiag was executed.
28840 00:40:38 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
28841 00:40:38 (0) ** - ROOT/MICROSOFT/SQLSERVER, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
28842 00:40:38 (0) **
28843 00:40:38 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 1 ERROR(S)!
28844 00:40:38 (0) ** - ROOT/MICROSOFT/SQLSERVER, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
28845 00:40:38 (0) **
28846 00:40:38 (0) ** WMI GET operations: ................................................................................................. OK.
28847 00:40:38 (0) ** WMI MOF representations: ............................................................................................ OK.
28848 00:40:38 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
28849 00:40:38 (2) !! WARNING: WMI ENUMERATION operation errors reported: ................................................................. 1 WARNING(S)!
28850 00:40:38 (0) ** - Root/Default, InstancesOf, 'SystemRestore' did not return any instance while AT LEAST 1 instance is expected.
28851 00:40:38 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\SR.MOF'
28852 00:40:38 (0) **
28853 00:40:38 (2) !! WARNING: WMI EXECQUERY operation errors reported: ................................................................... 1 WARNING(S)!
28854 00:40:38 (0) ** - Root/Default, 'SELECT * FROM SystemRestore' did not return any instance while AT LEAST 1 instance is expected.
28855 00:40:38 (0) **
28856 00:40:38 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
28857 00:40:38 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
28858 00:40:38 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
28859 00:40:38 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
28860 00:40:38 (0) ** WMI static instances retrieved: ..................................................................................... 988.
28861 00:40:38 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
28862 00:40:38 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
28863 00:40:38 (0) ** -
28864 00:40:38 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
28865 00:40:38 (0) ** DCOM: ............................................................................................................. 3024.
28866 00:40:38 (0) ** WINMGMT: .......................................................................................................... 5.
28867 00:40:38 (0) ** WMIADAPTER: ....................................................................................................... 0.
28868 00:40:38 (0) ** => Verify the WMIDiag LOG at line #19321 for more details.
28869 00:40:38 (0) **
28870 00:40:38 (0) ** # of additional Event Log events AFTER WMIDiag execution:
28871 00:40:38 (0) ** DCOM: ............................................................................................................. 0.
28872 00:40:38 (0) ** WINMGMT: .......................................................................................................... 1.
28873 00:40:38 (0) ** WMIADAPTER: ....................................................................................................... 0.
28874 00:40:38 (2) !! WARNING: => Verify the WMIDiag LOG at line #28428 for more details.
28875 00:40:38 (0) **
28876 00:40:38 (0) ** 2 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
28877 00:40:38 (0) ** => This error is typically a WMI error. This WMI error is due to:
28878 00:40:38 (0) ** - a missing WMI class definition or object.
28879 00:40:38 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
28880 00:40:38 (0) ** You can correct the missing class definitions by:
28881 00:40:38 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
28882 00:40:38 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
28883 00:40:38 (0) ** (This list can be built on a similar and working WMI Windows installation)
28884 00:40:38 (0) ** The following command line must be used:
28885 00:40:38 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
28886 00:40:38 (0) ** - a WMI repository corruption.
28887 00:40:38 (0) ** Under Windows XP SP2, you can validate the repository consistency
28888 00:40:38 (0) ** by executing the following command:
28889 00:40:38 (0) ** i.e. 'WMIDiag CheckConsistency'
28890 00:40:38 (0) ** Note: Under Windows XP SP2, when the repository is checked and detected INCONSISTENT,
28891 00:40:38 (0) ** a new repository is automatically re-created based on Auto-Recovery mechanism.
28892 00:40:38 (0) ** Note that some information can be lost during this process (i.e. static data, CIM registration).
28893 00:40:38 (0) ** However, the original repository is located at 'C:\WINDOWS\SYSTEM32\WBEM\Repository.001'.
28894 00:40:38 (0) ** The computer must be rebooted for the system to work with the re-created repository.
28895 00:40:38 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
28896 00:40:38 (0) ** otherwise some applications may fail after the reconstruction.
28897 00:40:38 (0) ** This can be achieved with the following command:
28898 00:40:38 (0) ** i.e. 'WMIDiag ShowMOFErrors'
28899 00:40:38 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
28900 00:40:38 (0) ** ALL fixes previously mentioned.
28901 00:40:38 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
28902 00:40:38 (0) **
28903 00:40:38 (0) ** -
28904 00:40:38 (0) ** WMI Registry key setup: ............................................................................................. OK.
28905 00:40:38 (0) ** -
28906 00:40:38 (0) ** -
28907 00:40:38 (0) ** -
28908 00:40:38 (0) ** -
28909 00:40:38 (0) **
28910 00:40:38 (0) ** -
28911 00:40:38 (0) ** WMI REPORT: END --
28912 00:40:38 (0) ** -
28913 00:40:38 (0) **
28914 00:40:38 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\STEVE HOFER\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_XP.CLI.SP2.32_PROHOMESTEVEMAC_2007.05.15_00.37.32.LOG' for details.
28915 00:40:38 (0) **
28916 00:40:38 (0) ** WMIDiag v2.0 ended on Tuesday, May 15, 2007 at 00:40 (W:59 E:6 S:1).

Check out http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=124864&SiteID=1 and http://blogs.msdn.com/echarran/archive/2006/01/03/509061.aspx, both have information about handling WMI problems.

Mike