SQL Server 2008 Installation Error

I found this error when i am try to Install SQL Server 2008 on Windows 8
TITLE: Microsoft SQL Server 2008 Setup
The following error has occurred:
Error getting file attributes for 1392. Please make sure that the drive is formatted and accessible.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1600.22&EvtType=0xF45F6601%25401201%25401
BUTTONS:
OK

Hi,
Did you check what the message ask you to?
Are you using local disk for the installation? Are you trying to install on a disk different from the OS disk (C:\) ?
Please try to give more information.
[Personal Site] [Blog] [Facebook]

Similar Messages

  • SQL server 2008 Installation media

    HI all,
    I am trying to install SQL server 2008 express, and in the "SQL Server Installation Center" i select "New SQL Server stand-alone installation or Add features to an existing installation" After selecting that option a window pops up and prompt me to "Browse for SQL Server 2008 Installation Media"
    Now, what exactly is "SQL Server 2008 Installation Media"? how am i suppose to locate/browse the installation media on my computer?
    i am totally new to SQL server and i am self-learning it from a book, the problem is that the book does not explain where to browse for instillation media!
    my system info:
    Windows 7 Home premium
    64-bit OS
    AMD 2.60 GHz
    6.00 GB RAM

    This is a solution for Windows 7 users who used the Web Platform Installer (I'm going to call it WPI).
    1 - Make sure you have power shell installed.
    2 - Install the sql 2008 SP1.  google it and download it.  
    Now comes the detailed part...
    You have to get a hold of the installation files without using WPI.   The WPI stores the installer executable on your computer and you have to run it and then get a hold of the directory it extracts before it deletes it.    You need to locate the WPI installation file and then run it manually.  Mine was located at...
    C:\Users\**username**\AppData\Local\Microsoft\Web Platform Installer\installers\SQLExpressAdv\12A6B9C2237817DEEEB3DCE22AFFA25B6794850C
    Of course you substitute your own username.   You may need to reveal hidden folders.   If you can't find it try running a search for the SQLExpressAdv folder. 
    In that folder you will find a file named "SQLEXPRADV_x64_ENU.exe" or something close to it. Run it and either on the first or second step you will see it extract a bunch of files.   Don't go any further after it runs that extraction.   Go to that folder and copy all the contents it extracted to a new folder and whamo.   That's where you will point your sql browse box to.   
    Now you can uninstall, set up servers,  whatever it is you were trying to do.  
    -N8 

  • Windows Installer - SQL Server 2008 Express Errors

    I am working with an application that was developed for an XP machine.  One of my peers took the old Windows application and using Visual Studio 2010 upgraded the application to work on a Windows 7 machine.  We are creating the installer (.exe
    and .msi) files within Microsoft Visual Studio 2010, but we are having different issues on different machines that we try to run the setup.exe file on.
    On our company computers with Windows 7, the setup.exe file runs and works properly.
    On our customers computer with Windows 7, received the following error: "an error occurred attempting to install SQL Server 2008 Express Service Pack 1." 
    On non-company/non-customer machines, we tried two Windows 7 machines.  One machine had no issues and everything installed perfectly and the other received this error: "Component SQL Server 2008 Express has failed to install."
    User pressed Yes to reboot the computer.
    After the reboot, the setup.exe file was run and there were no more errors.  The application was installed properly.
    Within the Installer we have four boxes checked under Properties - Prerequisites:
    Microsoft .NET Framework 4 (x86 and x64)
    Microsoft .NET Framework 4 Client Profile (x86 and x64)
    SQL Server 2008 Express
    Windows Installer 3.1
    If anyone can help with why the installer is causing issues on some computers and not on others as well as why the issues by computer are different that would be very helpful!
    Thank you!

    Hi,
    Please refer to this article for troubleshooting installation of
    SQL Server Express:
    http://social.technet.microsoft.com/wiki/contents/articles/1146.sql-server-express-troubleshoot-installation.aspx
    Check Summary.txt in the <SQLInstallFolder>\100\Setup Bootstrap\Log and see if you need to apply the Hotfix in the
    KB 957453.
    Thanks.
    Tracy Cai
    TechNet Community Support

  • SQL Server 2008 Installation on Windows 7

    I tried to install SQL Server 2008 on a Windows 7 Home Premium 64 bit (Enterprise Edition Trial Edition). The system check was ok and the installation started successfully but at the end there were some errors. In the logfile there were stacktraces describing failures trying write operations on the registry. What can I do to install SQL Server 2008 on my operating system?

    Hello ChunSong Feng,
    thanks for your advice. Herewith I send you the text parts from detail.txt with the detailed error description. The whole file is too big to send as content.
    Thanks in advance:
    2009-11-17 21:05:10 Slp: ReplaceAccountWithSidInSddl -- SDDL to be returned:  D:(A;CI;KR;;;S-1-5-21-2556463381-1186548668-390171815-1028)
    2009-11-17 21:05:10 Slp: Prompting user if they want to retry this action due to the following failure:
    2009-11-17 21:05:10 Slp: ----------------------------------------
    2009-11-17 21:05:10 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    2009-11-17 21:05:10 Slp: Inner exceptions are being indented
    2009-11-17 21:05:10 Slp:
    2009-11-17 21:05:10 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
    2009-11-17 21:05:10 Slp:     Message:
    2009-11-17 21:05:10 Slp:         Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:05:10 Slp:     Data:
    2009-11-17 21:05:10 Slp:       WatsonData = Microsoft SQL Server
    2009-11-17 21:05:10 Slp:       DisableRetry = true
    2009-11-17 21:05:10 Slp:     Inner exception type: System.UnauthorizedAccessException
    2009-11-17 21:05:10 Slp:         Message:
    2009-11-17 21:05:10 Slp:                 Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:05:10 Slp:         Stack:
    2009-11-17 21:05:10 Slp:                 bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
    2009-11-17 21:05:10 Slp:                 bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
    2009-11-17 21:05:10 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
    2009-11-17 21:05:10 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
    2009-11-17 21:05:10 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
    2009-11-17 21:05:10 Slp: ----------------------------------------
    2009-11-17 21:05:28 Slp: User has chosen to cancel this action
    2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
    2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
    2009-11-17 21:05:44 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:05:45 Slp: Watson bucket for exception based failure has been created
    2009-11-17 21:05:45 SQLBrowser: SQL Server Browser Install for feature 'SQL_Browser_Redist_SqlBrowser_Cpu32' failed with cancel exception: Microsoft.SqlServer.Configuration.Sco.ScoException: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen. ---> System.UnauthorizedAccessException: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
       bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
       bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
       bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
       bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
       bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
       --- Ende der internen Ausnahmestapelüberwachung ---
       bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
       bei Microsoft.SqlServer.Configuration.Sco.SqlRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.SetSecurityDescriptorByLocation(String sRegLocation, RegistryView regView, String sSddl, Boolean bOptional)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.ApplyRegPermissions(XmlNodeList xmlNodeListRegPermissions, Dictionary`2 dictionaryGroups, Dictionary`2 dicLocationFragments)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ApplyRegCommonPermissions(XmlElement xmlRootPermissions, Dictionary`2 dictionaryGroups, Dictionary`2 dicLocationFragments)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ApplyPermissions(String sXmlPermissionsFile, String sBrowserPrincipal)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ConfigStaticProperties(SqlBrowserPublicConfig publicConfigSqlBrowser)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ExecConfigNonRC(SqlBrowserPublicConfig publicConfigSqlBrowser)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.SelectAndExecTiming(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbPublicConfig)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.ExecWithRetry(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbPublicConfig).
    2009-11-17 21:05:45 SQLBrowser: The last attempted operation: Der '(A;CI;KR;;;[SQLServer2005SQLBrowserUser$UTAS-URMEL])'-Zugriffssteuerungseintrag wird dem Registrierungsschlüssel 'SOFTWARE\Microsoft\Microsoft SQL Server' in der 'Wow6432'-Sicht hinzugefügt, um den SQL Server Browser-Dienst zu konfigurieren..
    2009-11-17 21:05:45 Slp: Fehler bei der Konfigurationsaktion für Feature SQL_Browser_Redist während der Zeitangabe ConfigNonRC und Szenario ConfigNonRC.
    2009-11-17 21:05:45 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:05:45 Slp: Fehler bei der Konfigurationsaktion für Feature SQL_Browser_Redist während der Zeitangabe ConfigNonRC und Szenario ConfigNonRC.
    2009-11-17 21:05:45 Slp: Microsoft.SqlServer.Configuration.Sco.ScoException: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen. ---> System.UnauthorizedAccessException: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:05:45 Slp:    bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
    2009-11-17 21:05:45 Slp:    bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
    2009-11-17 21:05:45 Slp:    --- Ende der internen Ausnahmestapelüberwachung ---
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.Sco.SqlRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.SetSecurityDescriptorByLocation(String sRegLocation, RegistryView regView, String sSddl, Boolean bOptional)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.ApplyRegPermissions(XmlNodeList xmlNodeListRegPermissions, Dictionary`2 dictionaryGroups, Dictionary`2 dicLocationFragments)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ApplyRegCommonPermissions(XmlElement xmlRootPermissions, Dictionary`2 dictionaryGroups, Dictionary`2 dicLocationFragments)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ApplyPermissions(String sXmlPermissionsFile, String sBrowserPrincipal)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ConfigStaticProperties(SqlBrowserPublicConfig publicConfigSqlBrowser)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ExecConfigNonRC(SqlBrowserPublicConfig publicConfigSqlBrowser)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.SelectAndExecTiming(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbPublicConfig)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.ExecWithRetry(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbPublicConfig)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.Install(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbPublicConfig)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
    2009-11-17 21:05:45 Slp: Ausnahme: Microsoft.SqlServer.Configuration.Sco.ScoException.
    2009-11-17 21:05:45 Slp: Quelle: Microsoft.SqlServer.Configuration.Sco.
    2009-11-17 21:05:45 Slp: Meldung: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen..
    2009-11-17 21:05:45 Slp: Innere Ausnahme:
    2009-11-17 21:05:45 Slp:  Ausnahme: System.UnauthorizedAccessException.
    2009-11-17 21:05:45 Slp:  Quelle: mscorlib.
    2009-11-17 21:05:45 Slp:  Meldung: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen..
    2009-11-17 21:05:45 Slp: Completed Action: SqlBro
    2009-11-17 21:05:50 Slp: Prompting user if they want to retry this action due to the following failure:
    2009-11-17 21:05:50 Slp: ----------------------------------------
    2009-11-17 21:05:50 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    2009-11-17 21:05:50 Slp: Inner exceptions are being indented
    2009-11-17 21:05:50 Slp:
    2009-11-17 21:05:50 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
    2009-11-17 21:05:50 Slp:     Message:
    2009-11-17 21:05:50 Slp:         Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:05:50 Slp:     Data:
    2009-11-17 21:05:50 Slp:       WatsonData = 100
    2009-11-17 21:05:50 Slp:       DisableRetry = true
    2009-11-17 21:05:50 Slp:     Inner exception type: System.UnauthorizedAccessException
    2009-11-17 21:05:50 Slp:         Message:
    2009-11-17 21:05:50 Slp:                 Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:05:50 Slp:         Stack:
    2009-11-17 21:05:50 Slp:                 bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
    2009-11-17 21:05:50 Slp:                 bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
    2009-11-17 21:05:50 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
    2009-11-17 21:05:50 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
    2009-11-17 21:05:50 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
    2009-11-17 21:05:50 Slp: ----------------------------------------
    2009-11-17 21:05:57 Slp: User has chosen to cancel this action
    2009-11-17 21:05:58 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    2009-11-17 21:05:59 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2009-11-17 21:05:59 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    2009-11-17 21:05:59 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
    2009-11-17 21:05:59 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2009-11-17 21:05:59 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
    2009-11-17 21:06:17 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:06:17 Slp: Watson bucket for exception based failure has been created
    2009-11-17 21:06:17 SSIS: Failed to set registry permission on key 'SOFTWARE\Microsoft\Microsoft SQL Server\100' to SID 'S-1-5-21-2556463381-1186548668-390171815-1029'. Error: 'Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.'
    2009-11-17 21:06:17 Slp: ReplaceAccountWithSidInSddl -- SDDL to be returned:  D:(A;OICI;KR;;;S-1-5-21-2556463381-1186548668-390171815-1029)
    2009-11-17 21:06:17 Slp: Prompting user if they want to retry this action due to the following failure:
    2009-11-17 21:06:17 Slp: ----------------------------------------
    2009-11-17 21:06:17 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    2009-11-17 21:06:17 Slp: Inner exceptions are being indented
    2009-11-17 21:06:17 Slp:
    2009-11-17 21:06:17 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
    2009-11-17 21:06:17 Slp:     Message:
    2009-11-17 21:06:17 Slp:         Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:06:17 Slp:     Data:
    2009-11-17 21:06:17 Slp:       WatsonData = SSIS
    2009-11-17 21:06:17 Slp:       DisableRetry = true
    2009-11-17 21:06:17 Slp:     Inner exception type: System.UnauthorizedAccessException
    2009-11-17 21:06:17 Slp:         Message:
    2009-11-17 21:06:17 Slp:                 Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:06:17 Slp:         Stack:
    2009-11-17 21:06:17 Slp:                 bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
    2009-11-17 21:06:17 Slp:                 bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
    2009-11-17 21:06:17 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
    2009-11-17 21:06:17 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
    2009-11-17 21:06:17 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
    2009-11-17 21:06:17 Slp: ----------------------------------------
    2009-11-17 21:06:24 Slp: User has chosen to cancel this action
    2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
    2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
    2009-11-17 21:06:47 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:06:47 Slp: Watson bucket for exception based failure has been created
    2009-11-17 21:06:47 SSIS: Failed to set registry permission on key 'SOFTWARE\Microsoft\Microsoft SQL Server\100\SSIS' to SID 'S-1-5-21-2556463381-1186548668-390171815-1029'. Error: 'Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.'
    2009-11-17 21:06:47 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib
    2009-11-17 21:06:47 Slp: ReplaceAccountWithSidInSddl -- SDDL to be returned:  D:(A;OICI;KR;;;S-1-5-21-2556463381-1186548668-390171815-1029)(A;CI;KR;;;LU)(A;CI;KR;;;MU)
    2009-11-17 21:06:47 Slp: Prompting user if they want to retry this action due to the following failure:
    2009-11-17 21:06:47 Slp: ----------------------------------------
    2009-11-17 21:06:47 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    2009-11-17 21:06:47 Slp: Inner exceptions are being indented
    2009-11-17 21:06:47 Slp:
    2009-11-17 21:06:47 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
    2009-11-17 21:06:47 Slp:     Message:
    2009-11-17 21:06:47 Slp:         Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:06:47 Slp:     Data:
    2009-11-17 21:06:47 Slp:       WatsonData = Perflib
    2009-11-17 21:06:47 Slp:       DisableRetry = true
    2009-11-17 21:06:47 Slp:     Inner exception type: System.UnauthorizedAccessException
    2009-11-17 21:06:47 Slp:         Message:
    2009-11-17 21:06:47 Slp:                 Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:06:47 Slp:         Stack:
    2009-11-17 21:06:47 Slp:                 bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
    2009-11-17 21:06:47 Slp:                 bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
    2009-11-17 21:06:47 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
    2009-11-17 21:06:47 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
    2009-11-17 21:06:47 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
    2009-11-17 21:06:47 Slp: ----------------------------------------
    2009-11-17 21:06:52 Slp: User has chosen to cancel this action

  • Microsoft sql server 2008 installation issue

    Iam new to microsoft sql server.i have installed microsoft sql sever.
    and if i go through following
    All programs-->Microsoft SQL Server 2008-->Configuration tools-->Sql server configuration manager-->Sql server services
    --> it is showing as the remote procedure call failed (0x800706be)
    My pc is windows 7 32 bit .to make it run wt is need to be done................plz help.

    Hi
    Please Refer
    Balmukund's Link.. Service Pack Upgrade Should fix your Issue,
    check
    http://thesqldude.com/2012/12/05/sql-server-2012-configuration-manager-wmi-error-remote-procedure-call-failed-0x800706be/
    Balmukund Lakhani
    Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    This posting is provided "AS IS" with no warranties, and confers no rights.
    My Blog |
    Team Blog | @Twitter
    | Facebook
    Author: SQL Server 2012 AlwaysOn -
    Paperback, Kindle
    1 hour 13 minutes ago
    Reply
    |
    Quote
    |
    Propose as answer
    |
    Report as abuse
    Balmukund
    Microsoft
    (MSFT)
    Nag Pal MCTS/MCITP (SQL Server 2005/2008) :: Please Mark Answer/vote if it is helpful ::

  • SQL Server 2008 installation

    hey guys,
    I am trying to install data services 4.0 on a windows server with MS SQL database as the repository database. So, my plan was to install MS SQL 2008 first, then IPS, then data services. But i am facing a problem in installation of MS SQL itself. I installed MS SQL with following features - database engine, client tools and management tools. The installation process was smooth and the sql server services (server and agent) both startup just fine. I installed a custom instance for the same.
    But problem is when I open the management studio and try to connect to the database engine, it does not connect, I choose database engine as the server type, local hostname as the server name and windows authentication as the authentican type but it fails with the following error:
    TITLE: Connect to Server
    Cannot connect to <myservername>.
    ADDITIONAL INFORMATION:
    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
    For help, click: http://go.microsoft.com/fwlink?ProdName=MicrosoftSQLServer&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
    BUTTONS:
    OK
    Any clues as to what is causing this ??? Or is it normal at this stage of installation ?? anything to do with a odbc connection ?  I am confused. I have already tried to reinstall the server, no good, nothing in the event logs either.
    Thanks,

    resolved with following:
    In the TCP/IP Properties dialog box, on the IP Addresses tab, several IP addresses appear in the format IP1, IP2, up to IPAll. One of these is for the IP address of the loopback adapter, 127.0.0.1. Additional IP addresses appear for each IP Address on the computer. Right-click each address, and then click Properties to identify the IP address that you want to configure.
    If the TCP Dynamic Ports dialog box contains 0, indicating the Database Engine is listening on dynamic ports, delete the 0.u201D
    Once I deleted those zeros and put in 1433 for TCP ports on each IP address, voila!

  • SQL Server 2008 Installation Failure

    On a Windows XP (SP3 DEU) box, which has Visual Studio 2005, Visual Studio 2008, all .net versions, and SQL Server Express 2005 installed, SQL Server Express 2008 R2 installation failed with
    AclPermissionsFacet
    Checks if the SQL Server registry keys are consistent.
    Failed
    The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation about how to fix registry keys.
    Detail_GlobalRules.txt contains
    2010-10-11 17:13:09 Slp: ------------------------------------------------------------
    2010-10-11 17:13:11 Slp: Could not fix registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM\CLSID\{3B476D30-A401-11D2-AAD4-00C04F990171}.
    2010-10-11 17:13:11 Slp: System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
    2010-10-11 17:13:11 Slp:    bei Microsoft.SqlServer.Configuration.FixSqlRegistryKey.Program.ContainsInheritedAce(Byte[] securityDescriptor)
    2010-10-11 17:13:11 Slp:    bei Microsoft.SqlServer.Configuration.FixSqlRegistryKey.Program.FixRegistryKey(String keyName)
    2010-10-11 17:13:11 Slp:    bei Microsoft.SqlServer.Configuration.FixSqlRegistryKey.Program.FixRegistryKeyAndSubKeys(RegistryKey key)
    2010-10-11 17:13:11 Slp: Could not fix registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM\CLSID\{3B476D3A-A401-11D2-AAD4-00C04F990171}.
    2010-10-11 17:13:11 Slp: System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
    2010-10-11 17:13:11 Slp:    bei Microsoft.SqlServer.Configuration.FixSqlRegistryKey.Program.ContainsInheritedAce(Byte[] securityDescriptor)
    2010-10-11 17:13:11 Slp:    bei Microsoft.SqlServer.Configuration.FixSqlRegistryKey.Program.FixRegistryKey(String keyName)
    2010-10-11 17:13:11 Slp:    bei Microsoft.SqlServer.Configuration.FixSqlRegistryKey.Program.FixRegistryKeyAndSubKeys(RegistryKey key)
    2010-10-11 17:13:12 Slp: ------------------------------------------------------------
    2010-10-11 17:13:12 Slp: Rule 'AclPermissionsFacet' detection result: AreSqlAclPermissionsCanonical= False
    The two registry keys had broken ACLs (in regedit > permissions, they were shown as "Everyone, Full Access" but on Advanced view, no ACEs showed up.
    I removed the "Everyone" setting and re-enabled inheritance from HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM.
    This resolved this problem.

    In case if you haven't fix this:
    Steps
    Located HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server in registry
    Right click and go to Permission
    Click on Advance
    Tick on both check box (I. Inherit from parent the permission... II. Replace permission entries on all child objects...), click
    OK
    Click OK again
    That fixed mine, hopefully it does the same to yours

  • Crystal Reports Server 2008 Installation Error

    Good day,
    My name is Dominic Hung and I work at Business Objects.  One of my clients is coming across an installation error on their evaluation of CRS 2008 and is detailed as follows:
    They currently have the actual report writer (Crystal Reports 2008) on a desktop PC.  It's not installed on the server.
    We have the MySQL ODBC loaded on the local desktop as well as the server that is hosting CR2008 Server.
    The credentials (userid/password) used in both the desktop and server's ODBC configuration is READ ONLY.
    During the installation wizard for CR2008 Server, I key in the userid & password that I use when we create reports, but I receive an error stating that
    CMS database error: STU000226
    BusinessObjects Enterprise CMS: Unable to connect to the CMS system database "esc:10.127.214.22:3306".  Reason: Database access error. Reason access denied for user 'jdcherry'@'% to database 'esc'
    This is where everything stops and they can't go further. They are not sure why they are receiving the "access denied" error as shown above.  They have no problem connecting to the MySQL database when they create a report using CR2008, the CR2008 SERVER won't accept my credentials during the installation.
    QUESTIONS: 
    The "jdcherry" UserID (which I use) is READ ONLY on the MySQL database that's hosted on the Linux box.  Does the userID have to have higher priviledges than just READ ONLY in order to validate the database credentials? 
    If so, what level of access is required?
    Does the installation of CR Server update any of the tables that are stored on the MySQL database?
    Do we need to install the Crystal Reports 2008 on the server in order for Crystal Reports 2008 SERVER to work?
    What other workarounds can be done for the client?  The windows server they have Crystal Reports Server 2008 installed on has web services enabled but are continuing to come across issues.  Any insight for the client would be greatly appreciated.

    Does the userID have to have higher priviledges than just READ ONLY in order to validate the database credentials?
    The userID used when installing CRS must have dba previleges (create/drop tables) on the schema.
    Does the installation of CR Server update any of the tables that are stored on the MySQL database?
    You should create a new schema/DSN for the CMS db. The installation of CRS creates 8 new tables.
    Do we need to install the Crystal Reports 2008 on the server in order for Crystal Reports 2008 SERVER to work?
    No
    All this information is in the BOE XI3.0 Installation Guide.

  • SQL Server 2005 Installation Error

    I am installine ECC6 on SQL Serer 2006. I have started the SQL Server installation, using the SQL4SAP.vbs and after about 10 minutes the installation stops with an error. I am pointed to a fine Summary.txt but the details in the file do not give a clue on the problem:
    Machine         : SAPDEMO
    Product         : SQLXML4
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLXML4_1.log
    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 Dec 03 09:09:38 2007
    List of log files:
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Core(Local).log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLSupport_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLNCLI_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_OWC11_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SqlWriter_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BackwardsCompat_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_MSXML6_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLSupport_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLNCLI_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_OWC11_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BOL_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BackwardsCompat_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLXML4_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Datastore.xml
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework 2.0.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_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\SQLSetup0004_SAPDEMO_.NET Framework 2.0 LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Upgrade Advisor.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Upgrade Advisor LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Windows Installer.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Windows Installer LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SNAC.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Support.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SCC.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_WI.log

    Hi Rajeev,
    Indeed it was a typo error I am attempting SQL Server 2005.
    I am using the 32 bit installation, that has been checked.
    Here are the details from C:\Windows\SQL4SAP.log
    Customized installation of SQL Server 2005 for SAP *
    Log File: C:\WINDOWS\SQL4SAP.log
    Script started 03/12/2007 08:46:25 on SAPDEMO
    System settings:
      Win32_Processor.Name=Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz
      Win32_Processor.Name=Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz
      Win32_ComputerSystem.SystemType=X86-based PC
      Win32_OperatingSystem.OSType=18
      Win32_OperatingSystem.Version=5.2.3790
      Win32_OperatingSystem.ServicePackMajorVersion=2
      Win32_OperatingSystem.Caption=Microsoft(R) Windows(R) Server 2003, Standard Edition
      Win32_OperatingSystem.ProductType=3
      Win32_OperatingSystem.OSProductSuite=272
      Win32_OperatingSystem.OSLanguage=1033
    Windows version:
      OSVersion         = 5.2
      OSFamily          = Windows2003
      OSServicePack     = 2
      OSEdition         = Server
      OSSystemType      = X86
      OSProductSuite    = Terminal Server
      OSMsiVersion      = 3.1.4000.4042
      OSMdacVersion     = 2.82.3959.0
      OSLanguage        = English – United States
      OSLanguageID      = 1033
    Environment on SAPDEMO:
      userDir           = C:\Documents and Settings\Administrator\
      tmpDir            = C:\DOCUME1\ADMINI1\LOCALS~1\Temp\1\
      rootDir           = C:\WINDOWS\
      prgDir            = C:\Program Files\
      prgDirX86         = \
    SQL4SAP version:
      version:          ' v3.2.44    Mar 2007: SQL2005 SP2, Windows2003 SP2
      size:             86124
      created:          30/11/2007 16:59:31
      modified:         20/03/2007 13:36:44
      exe:              C:\WINDOWS\system32\cscript.exe
      script:           C:\SAP_CD\CD2\SQL4SAP.vbs
      C:                C:
    Script path:
      myRoot            = C:\SAP_CD\CD2\
      myDir             = C:\SAP_CD\CD2\x86\
      myDirUNC          = C:\SAP_CD\CD2\x86\
    Script settings:
      SqlAuthInstall    = False
      SilentInstall     = False
      DeEditionOnly     = False
      DeEditionPossible = False
      SapItMsgBox       = False
      SilentRtmSetup    = True
    Service Account:
      "C:\SAP_CD\CD2\x86\SqlCmd\GetSidName.exe" S-1-5-18 =>NT AUTHORITY\SYSTEM
      OSSystemAccount= NT AUTHORITY\SYSTEM
    03/12/2007 08:46:28
    Input Box "Select SQL Server instance"
    No SQL Server instance was found.
    SQL Server Native Client               not installed
    SQL Server 2005 Client Tools           not installed
    Enter a new or existing instance name.
    - for a Default Instance, enter:     (default)   or   .
    - for a Named Instance, enter:       <SID>
    To install SQL Client Tools Only, press Cancel.
    Result: (default)
    Registry settings (1/2):
    HKLM\SOFTWARE\Microsoft\DataAccess\FullInstallVer
    READ: 2.82.3959.0
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
    READ: 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
    WRITE(REG_DWORD): 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
    READ: 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
    WRITE(REG_DWORD): 4
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion\Version
    READ:
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion\PatchLevel
    READ:
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup\CurrentVersion\CurrentVersion
    READ:
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup\CurrentVersion\CSDVersion
    READ:
    03/12/2007 08:46:32
    Message Box "Confirmation"
    You have chosen to install the new instance
    SQL Instance:       (default)
    SQL Version:        9.00.3042
    SQL Edition:        2005 Enterprise Edition
    SQL Collation:      SQL_Latin1_General_CP850_BIN2
    Authentication:     Windows only
    Login sa:           random password, login disabled
    =======================================
    The installation may take 15 minutes or longer
    =======================================
    Do you want to start the installation now?
    Result: vbOK
    03/12/2007 08:46:34
    installing SQL Server 2005 Enterprise Edition on X86 - build 9.00.1399 ...
      Log File:    C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
      Command:     "C:\SAP_CD\CD2\x86\EnterpriseEdition\Servers\setup.exe" /qn USERNAME="SAP ISV Royalty Licensing Program" ADDLOCAL=Connectivity,SQL_Tools90,SQLXML,Tools_Legacy,SQL_Documentation,SQL_BooksOnline,SQL_Data_Files,SQL_FullText PERSEAT=50 INSTANCENAME=MSSQLSERVER SQLCOLLATION=SQL_Latin1_General_CP850_BIN2 AGTAUTOSTART=1 SQLACCOUNT="NT AUTHORITY\SYSTEM" AGTACCOUNT="NT AUTHORITY\SYSTEM" SQLBROWSERACCOUNT="NT AUTHORITY\SYSTEM" DISABLENETWORKPROTOCOLS=0 SAPWD=xxxxxxxxxxxxxxxx
      Return Code: 1605
    03/12/2007 08:48:41
    Log file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
    Microsoft SQL Server 2005 9.00.1399.06
    ==============================
    OS Version      : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
    Time            : Mon Dec 03 08:46:48 2007
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_1.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_1.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server VSS Writer
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SqlWriter_1.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_2.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_2.log
    Machine         : SAPDEMO
    Product         : Microsoft SQL Server 2005 Books Online (English)
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_BOL_1.log
    Machine         : SAPDEMO
    Product         : SQLXML4
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLXML4_1.log
    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 Dec 03 08:48:39 2007
    List of log files:
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Core(Local).log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SqlWriter_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_MSXML6_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_2.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_BOL_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLXML4_1.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Datastore.xml
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework 2.0.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_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\SQLSetup0003_SAPDEMO_.NET Framework 2.0 LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Upgrade Advisor.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Upgrade Advisor LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Windows Installer.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Windows Installer LangPack.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SNAC.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Support.log
         C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SCC.log
    service MSSQLSERVER does not exist
    03/12/2007 08:48:41
    Message Box "Installation failed"
    The unattended installation failed.
      Installation Step: SQL Server - build 9.00.1399
      Return Code:       1605
      Log File:          C:\WINDOWS\SQL4SAP.log
    Check the log file above!
    See also SAP note 896566 for known issues
    Result: vbOK
    Registry settings (2/2):
    HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL\MSSQLSERVER
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg0
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg1
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg2
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg3
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg4
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg5
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg6
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg7
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg8
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg9
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg10
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg11
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg12
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg13
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg14
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg15
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg16
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg17
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg18
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg19
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg20
    READ:
    HKLM\SOFTWARE\Microsoft\MSSQLSERVER\Setup\SQLPath
    READ:
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
    WRITE(REG_DWORD): 4
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
    WRITE(REG_DWORD): 4
    03/12/2007 08:48:47
    Quit script with return code 1

  • Sql server 2012 installation error

    can someone please tell me why i am getting an error when i am trying to install sql 2012 SP1. it when i get to the installation  it says "sql server Setup has encountered the following error. hexadecimal value 0x00, is an invalid character.Line
    1, position 51471. error code 0x84B10001.

    Hi vijatkumar.ptl,
    According to your description and your error message, when you install SQL Server 2012, check if splinters of an MSDE instance (Microsoft Desktop Engine) was left over from other program. If this hidden instance exists, and the installer perform the RunDiscoveryAction
    process, the issue will occur. So I recommend you manually remove a Microsoft SQL Server
     Desktop Engine instance (MSDE) by using Add/Remove Programs in Control Panel, and so on, then reinstall again.
    There is a similar issue about SQL Server 2012 setup issue, you can refer to the following posts.
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/72fbd726-730b-4aef-9db1-aeb8bfb5d334/sql-2012-setup-issues-hexadecimal-value-0x00-is-an-invalid-character
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/f37e18eb-f1ab-4106-83f6-8bbf04d6a41a/setup-failed-0x84b10001-sql-2012-hexadecimal-value-0x00-is-an-invalid-character-line-1-position?forum=sqlsetupandupgrade
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • SQL SERVER 2014 Installation error

    Hi, I'm having great difficulty in installing SQL server 2014 developer edition 64- bit . When I use to run setup it says sql server boot strapper.dll is missing although it is present inside the folder and when I opened the sql setup bootstrapper.dll it
    gives the error "This file doesn't have a program associated with it for performing this action".  ? I've attached the snapshot of the error as well.
    Needs immediate help.

    Hello,
    Are you trying to install from a network share/location? Could you try to copy the media to a folder on the c:\ drive.
    If the media is an .ISO file, please unzip it using WinRAR and install from that folder on the C:\ drive.
    If the above does not help, could you try to download the media again.
    The following article may be useful.
    http://www.sqlcoffee.com/SQLServer2014_0005.htm
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • SQL Server 2008 R2 setup error

    installing the above, I get an error just before the end of the setup saying - Attempted to perform an unathorized operation.  Click retry or cancel.
    Any ideas why this is doing this?

    Hello,
    Please try the following resources:
    http://blogs.msdn.com/b/petersad/archive/2009/08/08/sql-server-2008-could-not-fix-registry-key-issue-and-how-to-resolve.aspx
    http://social.technet.microsoft.com/Forums/sqlserver/en-US/3649e3f7-e726-4bc7-854f-0b436756dad0/sql-server-2008-installation-problem
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/61d56f64-2575-4a58-9503-84579476afaf/sql-server-2008-setup-error-attempted-to-perform-an-unauthorized-operation
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/cfab9cdd-eb89-4e70-a255-4f4bff3def8e/sql-server-2008-r2-setup-fails-with-error-attempted-to-perform-an-unauthorized-operation
    If the above resources do not help, please share with us the Detail.txt log file. The following
    article may help you locate the file:
    http://technet.microsoft.com/en-us/library/ms143702(v=sql.105).aspx
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • SQL Server 2008 is the worst installation experience ever

    Sorry but you guys have really messed up with SQL Server 2008 installation.
    I've been using SQL server since 6.5, so I would classify as a fan.  We were looking at upgrading from 2005, which I was quite pleased with.
    The installation experience is the worst I've ever experienced.  I am a computer expert, and I couldn't figure out how to install it properly.  Why is it that when I downloaded SQL Server Management Studio Express 2008, it seems as though it wants
    to install the full database?  Why is it when I was asked if I wanted to install a new version of SQL Server 2008 or use a previous install, when I chose previous install, it said that an instance ID was missing, but there was no way to specify anything
    else?  It drove me crazy.
    Why are there so many requirements and restrictions for the installation, when all I want to do is install Management Studio?  It's intolerable and makes me never want to upgrade to 2008.  Why is the process so terrible when Microsoft is supposed
    to have the best UE people in the business? 
    You guys did a really terrible job on this one.

    We have not tried to cluster 2012.  We used to cluster; however, we were not prepared to manage the added complications.  The result was that our non-clustered servers had better uptime.  We used to joke about how many 8s we were
    getting with our cluster.  (To be fair, it did not help that we had a 7x24 SLA with only 8-5 staff.  When the cluster fails to failover, it can be a long time before it is fixed.  We eventually got the kinks worked out.)  
    I understand the frustration.  Excellence and stability can be achieved, but product lifecycles can punish those who seek such qualities.  Product changes and shorter support lifecycles produce revenue for MS, so I don't see this getting better. 
    There will be a new OS, new SQL, and a new set of problems the next time around. 
    I expect things to get worse until we get pushed into the cloud.  A stable environment in the cloud is profitable for MS and clients.  I do not think this is the case now outside the cloud.  Upgrading applications to remain
    on supported products is very costly.  And about the only business benefit of the upgrade is that the product remains on a supported platform and gets security updates.  Sort of sound like that blackmail virus?  I'd rather pay to have a
    patch for new features and focus on application upgrades that improve business processes.  Now bug fixes can require a major version change - which will have new bugs.  I'm ranting because of some head pounding
    I've done this week due to a hard coded limitation introduced in SQL 2012 by design.  I'll replace the process, but I wonder how long it will work as my SQL related PSH often breaks with a new version of something.  I'll
    stop now. Where'd my Prozac go?  Next week is new week, life is good, everything will work,.... 
    PS I actually enjoy the work and think MS products are decent; however, our environment does seem to be more frail and less stable due to MS product changes - even if the products are getting better.  Better is worse - what an odd thought. 
    Randy in Marin

  • Cannot install SQL Server 2008 R2 Developer on Windows 8.1

    I am unable to install SQL Server 2008 R2 Developer edition on Windows 8.1 Enterprise evaluation and about 3/4 of the way through the installation I get this error msg:
    TITLE: SQL Server 2008 R2 Setup
    The following error has occurred:
    Attempted to perform an unauthorized operation.
    Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.4000.0&EvtType=0x88792597%25400xBB814387
    This is my log file:
    Overall summary:
    Final result: User cancelled
    Exit code (Decimal): 0
    Exit message: User cancelled
    Start time: 2014-04-23 23:49:10
    End time: 2014-04-24 00:03:44
    Requested action: Install
    Machine Properties:
    Machine name: PC
    Machine processor count: 2
    OS version: Future Windows Version
    OS service pack:
    OS region: United States
    OS language: English (United States)
    OS architecture: x64
    Process architecture: 64 Bit
    OS clustered: No
    Product features discovered:
    Product Instance Instance ID Feature Language Edition Version Clustered
    Package properties:
    Description: SQL Server Database Services 2008 R2
    ProductName: SQL Server 2008 R2
    Type: RTM
    Version: 10
    SPLevel: 1
    Installation location: F:\My Files\My Downloads\EXISTING\SQLServer2008R2Dev\SQLFULL_ENU\x64\setup\
    Installation edition: DEVELOPER
    User Input Settings:
    ACTION: Install
    ADDCURRENTUSERASSQLADMIN: False
    AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
    AGTSVCPASSWORD: *****
    AGTSVCSTARTUPTYPE: Manual
    ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Backup
    ASCOLLATION: Latin1_General_CI_AS
    ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config
    ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Data
    ASDOMAINGROUP: <empty>
    ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log
    ASPROVIDERMSOLAP: 1
    ASSVCACCOUNT: NT AUTHORITY\SYSTEM
    ASSVCPASSWORD: *****
    ASSVCSTARTUPTYPE: Automatic
    ASSYSADMINACCOUNTS: PC\computername
    ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Temp
    BROWSERSVCSTARTUPTYPE: Disabled
    CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\ConfigurationFile.ini
    CUSOURCE:
    ENABLERANU: False
    ENU: True
    ERRORREPORTING: False
    FARMACCOUNT: <empty>
    FARMADMINPORT: 0
    FARMPASSWORD: *****
    FEATURES: SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,OCS
    FILESTREAMLEVEL: 2
    FILESTREAMSHARENAME: MSSQLSERVER
    FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
    FTSVCPASSWORD: *****
    HELP: False
    INDICATEPROGRESS: False
    INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
    INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
    INSTALLSQLDATADIR: <empty>
    INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
    INSTANCEID: MSSQLSERVER
    INSTANCENAME: MSSQLSERVER
    ISSVCACCOUNT: NT AUTHORITY\NetworkService
    ISSVCPASSWORD: *****
    ISSVCSTARTUPTYPE: Automatic
    NPENABLED: 0
    PASSPHRASE: *****
    PCUSOURCE:
    PID: *****
    QUIET: False
    QUIETSIMPLE: False
    ROLE: <empty>
    RSINSTALLMODE: DefaultNativeMode
    RSSVCACCOUNT: NT AUTHORITY\SYSTEM
    RSSVCPASSWORD: *****
    RSSVCSTARTUPTYPE: Automatic
    SAPWD: *****
    SECURITYMODE: <empty>
    SQLBACKUPDIR: <empty>
    SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
    SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
    SQLSVCPASSWORD: *****
    SQLSVCSTARTUPTYPE: Automatic
    SQLSYSADMINACCOUNTS: PC\computername
    SQLTEMPDBDIR: <empty>
    SQLTEMPDBLOGDIR: <empty>
    SQLUSERDBDIR: <empty>
    SQLUSERDBLOGDIR: <empty>
    SQMREPORTING: False
    TCPENABLED: 0
    UIMODE: Normal
    X86: False
    Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\ConfigurationFile.ini
    Detailed results:
    Feature: Database Engine Services
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: SQL Server Replication
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Full-Text Search
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Analysis Services
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Reporting Services
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Integration Services
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Client Tools Connectivity
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Management Tools - Complete
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Management Tools - Basic
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Client Tools SDK
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Client Tools Backwards Compatibility
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Business Intelligence Development Studio
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: SQL Server Books Online
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Microsoft Sync Framework
    Status: Passed
    MSI status: Passed
    Configuration status: Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\SystemConfigurationCheck_Report.htm
    I tried installing as adminstrator and in compatability mode with Windows 7/Vista but that didn't work. Trying to install from the dvd or from the extracted files in my drive made no difference.
    I am now wondering if there is a download link for SQL Server 2008 R2 Developer edition with SP2 included (i.e. not just SP2 but the whole application (5GB+) otherwise I am not sure how to install this.

    Hello,
    1. Please refer to solution provided in below thread
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/61d56f64-2575-4a58-9503-84579476afaf/sql-server-2008-setup-error-attempted-to-perform-an-unauthorized-operation?forum=sqlsetupandupgrade
    2. Make sure you stop antivirus services during running the setup.Make sure you Right click on setup.exe file and select run as administrator.
    If above does not works include below as well
    3. Please verify WMI service is started.
    If WMI is started, consider to repair WMI.
    http://windowsxp.mvps.org/repairwmi.htm
    Reference
    Link
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Issues installing SQL Server 2008 instance - Install fails

    Hi there,
    I have a server windows server 2008 R2 standard.
    While doing an Enterprise to Standard downgrade, I have removed enterprise edition of SQL Server 2008, rebooted and while installing standard edition, I get the below error saying "You
    SQL server 2008 installation completed with failures. Some or all identity references could not be translated"
    Bit of background. This server has another express instance of SQL Server 2008. I have used local system account, network service as well as our general SQL service account, but I get the error
    towards the end of the installation and it fails saying “Some or all identity references could not be translated.”
    I am installing a named instance with the same name as before but fails. I have tried creating a test instance that fails too. Any ideas? I have also run the clean up utility but no joy.
    Cheers
    Faltaf

    Hi FAltafB,
    According to your description, you come across the error that some or all identity references could not be translated. Please help to post SQL Server setup error log for analysis. By default, SQL Server setup summary and detail logs located in C:\Program
    Files\Microsoft SQL Server\100\Setup Bootstrap\Log.
    Based on my research, this issue could be due to the incomplete uninstallation for previous installation. Another cause could be that you are installing SQL Server after your machine becomes a domain controller.
    To troubleshoot the issue, please pay attention to the points below.
    1. Make sure you have administrative rights on the computer, uninstall all the components related with SQL Server 2008 enterprise from the control panel and delete registry keys mentioned in the article:
    http://blogs.msdn.com/b/sreekarm/archive/2010/03/15/sql-express-is-not-installed-properly-steps-to-be-taken-before-reinstall-again.aspx
    2. Use
    SQL Server 2008 R2 Best Practice Analyzer to detect if SQL Server is installed on a domain controller. If SQL Server is installed on a domain controller, please demote your machine from being a domain controller and install the SQL Server again since it
    is not recommended to install SQL Server on a domain controller.
    Regards,
    Michelle Li

Maybe you are looking for

  • Apple TV (1st Gen) Not showing under devices in iTunes

    I have a New iMac and I have used time machine to restore data from my old iMac. Everything other than iTunes is fine. In iTunes (10.4) all of my library is fine, however, my 1st gen Apple TV fails to appear under Devices. I've checked various suppor

  • Payment processing fees

    Can anyone tell me how BT can charge a "payment processing fee" when there is no payment due?  I queried this last month and was promised a refund by none other than one of these forum moderators. True to form, despite the promise being made in writi

  • Best way to pass values btwn servlets?

    i have to pass multiple values from one servlet to the next, when the user submits a form. i don't know how many, or even the names of the parameters until the user submits the form. right now, i send them as hidden fields when the form is submitted.

  • Portal Best Practices

    Hi folks, I've seen this link to SAP Portal Best Practices:  [http://help.sap.com/bp_epv260/ep_en/index.htm|http://help.sap.com/bp_epv260/ep_en/index.htm] here in SDN but it isn't working (The page cannot be found - HTTP Error 404 - File or directory

  • Assigning faces is harder than assigning keywords

    I'm organizing photos on my mother-in-law's computer and thought I'd use the faces feature to identify family members.  It is not working well.  It finds faces for some people, but for others it gives around 200 mostly incorrect matches.  Marking the