Cannot find SQL Server 2008 instance

I have installed SQL server 2008 Developer edition on my laptop. When I open SSMS I cannot find the installed instance under the Server Name group and When I choose the Browse More option and go to Database engine, the instance name does not show up. Will
appreciate any suggestions.
Thanks
akoranteng

>>I see two instances of SQL Server 2008 when i issue the commands you suggested to me
I don't why you have two instances, may be you installed two different instances.
I think local servers list is obtained by reading the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server \Instance Names\SQL
Sometimes (don't know why may it is SQL browser service or something else messed up) you don't see a locally installed instance on the drop down list. Just
type in the instance name manually inside the textbox for server name and you should be able to connect

Similar Messages

  • Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"

    I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
    Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
    I tried all the things below;
    * I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
    * I'm deleting all the keys related with Sql Server from Regedit.
    * Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
    Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
    * My firewall is already closed. And i have not any antivirus software.
    * I gave the permission for port 1433 on firewall.
    Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.

    Here's the ERRORLOG file which i found under the folder;
    Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
    2014-09-27 03:39:40.15 Server      Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) 
    Apr  2 2010 15:48:46 
    Copyright (c) Microsoft Corporation
    Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
    2014-09-27 03:39:40.15 Server      (c) Microsoft Corporation.
    2014-09-27 03:39:40.15 Server      All rights reserved.
    2014-09-27 03:39:40.15 Server      Server process ID is 5768.
    2014-09-27 03:39:40.15 Server      System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
    2014-09-27 03:39:40.15 Server      Authentication mode is MIXED.
    2014-09-27 03:39:40.15 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-09-27 03:39:40.15 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-09-27 03:39:40.15 Server      Command Line Startup Parameters:
    -m SqlSetup
    -f
    -Q
    -q Turkish_CI_AS
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    2014-09-27 03:39:40.18 Server      Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically.  After
    the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
    2014-09-27 03:39:40.18 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.18 Server      Detected 4 CPUs. This is an informational message; no user action is required.
    2014-09-27 03:39:40.31 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-09-27 03:39:40.32 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2014-09-27 03:39:40.43 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2014-09-27 03:39:40.45 Server      Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
    is required.
    2014-09-27 03:39:40.45 spid7s      Warning ******************
    2014-09-27 03:39:40.45 spid7s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-09-27 03:39:40.46 spid7s      Starting up database 'master'.
    2014-09-27 03:39:40.52 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.58 spid7s      SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
    2014-09-27 03:39:40.59 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:40.59 spid7s      Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
    2014-09-27 03:39:40.59 spid7s      Starting up database 'mssqlsystemresource'.
    2014-09-27 03:39:40.61 spid7s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
    2014-09-27 03:39:40.94 spid7s      Password policy update was successful.
    2014-09-27 03:39:40.94 spid8s      Starting up database 'model'.
    2014-09-27 03:39:40.95 spid7s      Server name is 'CAGATAY'. This is an informational message only. No user action is required.
    2014-09-27 03:39:41.21 spid8s      Clearing tempdb database.
    2014-09-27 03:39:41.21 spid10s     A new instance of the full-text filter daemon host process has been successfully started.
    2014-09-27 03:39:41.24 Server      A self-generated certificate was successfully loaded for encryption.
    2014-09-27 03:39:41.24 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    2014-09-27 03:39:41.24 Server      Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
    7806. This is an informational message only. No user action is required.
    2014-09-27 03:39:41.28 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
    to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2014-09-27 03:39:41.28 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2014-09-27 03:39:41.70 spid8s      Starting up database 'tempdb'.
    2014-09-27 03:39:41.86 spid7s      Warning ******************
    2014-09-27 03:39:41.86 spid7s      Attempting to change default collation to Turkish_CI_AS.
    2014-09-27 03:39:41.92 spid7s       index restored for master.syspriorities.
    2014-09-27 03:39:41.95 spid7s       index restored for master.sysbrickfiles.
    2014-09-27 03:39:41.96 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:41.96 spid7s       index restored for master.sysowners.
    2014-09-27 03:39:42.13 spid7s       index restored for master.sysdbreg.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s       index restored for master.sysschobjs.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.17 spid7s       index restored for master.syscolpars.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxlgns.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxsrvs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysnsobjs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.syscerts.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysrmtlgns.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysxprops.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysscalartypes.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysidxstats.
    2014-09-27 03:39:42.31 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysendpts.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysclsobjs.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysremsvcbinds.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysrts.
    2014-09-27 03:39:42.33 spid7s       index restored for master.sysasymkeys.
    2014-09-27 03:39:42.33 spid7s       index restored for master.syssqlguides.
    2014-09-27 03:39:42.44 spid7s       index restored for master.syssoftobjrefs.
    2014-09-27 03:39:42.47 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.48 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.49 spid7s       index restored for master.spt_values.
    2014-09-27 03:39:42.49 spid7s       index restored for master.MSreplication_options.
    2014-09-27 03:39:42.56 spid7s       index restored for tempdb.syspriorities.
    2014-09-27 03:39:42.56 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysowners.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysschobjs.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.59 spid7s       index restored for tempdb.syscolpars.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysnsobjs.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.syscerts.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysxprops.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysscalartypes.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysidxstats.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysclsobjs.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysremsvcbinds.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysrts.
    2014-09-27 03:39:42.62 spid7s       index restored for tempdb.sysasymkeys.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssqlguides.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssoftobjrefs.
    2014-09-27 03:39:42.75 spid7s       index restored for model.syspriorities.
    2014-09-27 03:39:42.75 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.75 spid7s       index restored for model.sysowners.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s       index restored for model.sysschobjs.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscolpars.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysnsobjs.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscerts.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysxprops.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysscalartypes.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysidxstats.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysclsobjs.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysremsvcbinds.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysrts.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysasymkeys.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssqlguides.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssoftobjrefs.
    2014-09-27 03:39:43.02 spid7s      Starting up database 'msdb'.
    2014-09-27 03:39:43.82 spid7s       index restored for msdb.syspriorities.
    2014-09-27 03:39:43.85 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.93 spid7s       index restored for msdb.sysowners.
    2014-09-27 03:39:43.99 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.09 spid7s       index restored for msdb.sysschobjs.
    2014-09-27 03:39:44.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.syscolpars.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.sysnsobjs.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.25 spid7s       index restored for msdb.syscerts.
    2014-09-27 03:39:44.25 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s       index restored for msdb.sysxprops.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.27 spid7s       index restored for msdb.sysscalartypes.
    2014-09-27 03:39:44.37 spid7s       index restored for msdb.sysidxstats.
    2014-09-27 03:39:44.41 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysclsobjs.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysremsvcbinds.
    2014-09-27 03:39:44.42 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysrts.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.sysasymkeys.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.syssqlguides.
    2014-09-27 03:39:44.59 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.74 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.85 spid7s       index restored for msdb.syssoftobjrefs.
    2014-09-27 03:39:44.89 spid7s       index restored for msdb.syspolicy_policies_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.sysproxies.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syscollector_execution_stats_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syssubsystems.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_primary_secondaries.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.sysdownloadlist.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_monitor_primary.
    2014-09-27 03:39:44.92 spid7s       index restored for msdb.sysoriginatingservers.
    2014-09-27 03:39:44.93 spid7s       index restored for msdb.log_shipping_monitor_history_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_monitor_error_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_secondary.
    2014-09-27 03:39:44.97 spid7s       index restored for msdb.log_shipping_secondary_databases.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.log_shipping_monitor_secondary.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysjobs.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_database_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.syscollector_blobs_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysjobsteps.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.logmarkhistory.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_session_statistics_internal.
    2014-09-27 03:39:45.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.12 spid7s       index restored for msdb.sysdtscategories.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.syspolicy_target_sets_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysschedules.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysdac_instances_internal.
    2014-09-27 03:39:45.33 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.50 spid7s       index restored for msdb.sysssispackages.
    2014-09-27 03:39:45.51 spid7s       index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
    2014-09-27 03:39:45.51 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysssispackagefolders.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysdac_history_internal.
    2014-09-27 03:39:45.53 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syscategories.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservers.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservergroups.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syspolicy_policy_category_subscriptions_internal.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysalerts.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysoperators.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syspolicy_system_health_state_internal.
    2014-09-27 03:39:45.63 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syscollector_config_store_internal.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s       index restored for msdb.sysmanagement_shared_server_groups_internal.
    2014-09-27 03:39:45.66 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysmanagement_shared_registered_servers_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.syscachedcredentials.
    2014-09-27 03:39:45.79 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.syscollector_collection_sets_internal.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.sysutility_ucp_dac_health_internal.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms_datatype.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysmail_profile.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysutility_ucp_managed_instances_internal.
    2014-09-27 03:39:45.83 spid7s       index restored for msdb.syspolicy_management_facets.
    2014-09-27 03:39:45.84 spid7s       index restored for msdb.sysutility_ucp_mi_health_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syscollector_collector_types_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syspolicy_configuration_internal.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_facet_events.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.sysmail_account.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_conditions_internal.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.sysutility_ucp_health_policies_internal.
    2014-09-27 03:39:45.88 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.syscollector_collection_items_internal.
    2014-09-27 03:39:45.90 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysmail_servertype.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
    2014-09-27 03:39:46.02 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_configuration_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.sysmail_server.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_policy_categories_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_object_sets_internal.
    2014-09-27 03:39:46.04 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysmail_configuration.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysdbmaintplan_databases.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.log_shipping_primary_databases.
    2014-09-27 03:39:46.39 spid7s      The default collation was successfully changed.
    2014-09-27 03:39:46.39 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2014-09-27 03:39:47.17 spid51      Changed database context to 'master'.
    2014-09-27 03:39:47.18 spid51      Changed language setting to us_english.
    2014-09-27 03:39:47.72 spid51      Setting database option RECOVERY to FULL for database model.
    2014-09-27 03:39:47.84 spid51      Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.84 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:48.27 spid51      Error: 15007, Severity: 16, State: 1.
    2014-09-27 03:39:48.27 spid51      '' is not a valid login or you do not have permission.
    2014-09-27 03:51:25.13 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:25.13 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:32.67 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:32.67 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:42.11 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:51:42.11 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:52:42.07 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:52:42.07 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:53:01.23 Logon       Error: 18461, Severity: 14, State: 1.
    2014-09-27 03:53:01.23 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
    2014-09-27 03:53:17.57 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:53:17.57 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:53:32.54 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:53:32.54 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:04.29 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:04.29 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:10.36 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:10.36 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:47.18 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:54:47.18 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    Resolve the error, please refer to the following links.
    Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
    could not register the SPN Kerberos:
    http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html  
    Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server

  • Cannot install SQL Server 2008 R2 on Widows 7 Pro

    I've tried unsuccesfully to install SQL Server 2008 R2 on my laptop running Windows 7 Pro.
    I previously installed Visual Studio 2010 and downloaded the SQL Server 2008 R2 disk image, burned the disk and then tried to install SQL Server.
    I get a "Microsoft .NET Framework" unhandled exception dialog box with the following detail message:
    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.
    ************** Exception Text **************
    System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral,
    PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified. (C:\Users\Louis\AppData\Local\Microsoft_Corporation\LandingPage.exe_StrongName_ryspccglaxmt4nhllj5z3thycltsvyyx\10.0.0.0\user.config line 5) ---> System.IO.FileNotFoundException:
    Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
    File name: 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
       at System.Configuration.TypeUtil.GetTypeWithReflectionPermission(IInternalConfigHost host, String typeString, Boolean throwOnError)
       at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.Init(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
       at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.InitWithRestrictedPermissions(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
       at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory..ctor(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
       at System.Configuration.RuntimeConfigurationRecord.CreateSectionFactory(FactoryRecord factoryRecord)
       at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
       --- End of inner exception stack trace ---
       at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
       at System.Configuration.BaseConfigurationRecord.GetSection(String configKey, Boolean getLkg, Boolean checkPermission)
       at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
       at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
       at System.Configuration.ConfigurationManager.GetSection(String sectionName)
       at System.Configuration.ClientSettingsStore.ReadSettings(String sectionName, Boolean isUserScoped)
       at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection properties)
       at System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
       at System.Configuration.SettingsBase.GetPropertyValueByName(String propertyName)
       at System.Configuration.SettingsBase.get_Item(String propertyName)
       at System.Configuration.ApplicationSettingsBase.GetPropertyValue(String propertyName)
       at System.Configuration.ApplicationSettingsBase.get_Item(String propertyName)
       at Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings.get_WindowPlacement()
       at Microsoft.SqlServer.Configuration.LandingPage.LandingPageForm.OnLoad(EventArgs e)
       at System.Windows.Forms.Form.OnCreateControl()
       at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
       at System.Windows.Forms.Control.CreateControl()
       at System.Windows.Forms.Control.WmShowWindow(Message& m)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
       at System.Windows.Forms.ContainerControl.WndProc(Message& m)
       at System.Windows.Forms.Form.WmShowWindow(Message& m)
       at System.Windows.Forms.Form.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4952 (win7RTMGDR.050727-4900)
        CodeBase:
    file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    LandingPage
        Assembly Version: 10.0.0.0
        Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
        CodeBase: file:///E:/x86/LandingPage.exe
    System.Windows.Forms
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    System
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    System.Drawing
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    Microsoft.SqlServer.Configuration.Sco
        Assembly Version: 10.0.0.0
        Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
        CodeBase:
    file:///E:/x86/Microsoft.SqlServer.Configuration.Sco.DLL
    Microsoft.SqlServer.Chainer.Infrastructure
        Assembly Version: 10.0.0.0
        Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
        CodeBase:
    file:///E:/x86/Microsoft.SqlServer.Chainer.Infrastructure.DLL
    System.Xml
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
    Accessibility
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
    Microsoft.SqlServer.Management.Controls
        Assembly Version: 10.0.0.0
        Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
        CodeBase:
    file:///E:/x86/Microsoft.SqlServer.Management.Controls.DLL
    System.Configuration
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    For example:
    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.
    ////  End of message.
    I have all the updates on my laptop per Microsoft Update.
    Any ideas what is wrong?

    Hello,
    Please try the solution posted in the following thread:
    http://social.msdn.microsoft.com/Forums/en/sqlkjsetupandupgrade/thread/35356bf2-6db7-4785-a104-bc62d18913f7
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • 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

  • Getting Frequent time out while Connecting to SQL server 2008 Instance installed on VmWare

    Hi,
    I have a production SQL server Database with default instance. when I connect this instance from 10 attempts it get connected only 5-6 times. I connect this through SSMS. Some of jobs also getting failed due to login time out expired. please help in this.
    Product is SQL server 2008 Enterprise Edition
    Thank You
    Yogesh Arora

    Yogesh Arora
    Have you checked Event Viewer and ERROR.LOG?
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • 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

  • Tons of Cannot Find SQL Server errors in ULS log

    Background: I inherited the maintenance of this farm. The previous consultant migrated the client from WSS 3.0 to 2013 by way of 2007 MOSS and 2010 (unsure of version). I do not know if there was a "temporary" SQL server used during this process
    that no longer exists. It seems likely given all of the errors regarding a missing SQL server.
    The current 2013 Enterprise farm contains 1 WFE and 3 App servers, 2 of which comprise the search topology. There is one SQL server, not aliased. All machines are VMs. One of the search servers (App) is on a different ESXi host. The timer job that is creating
    all of the ULS errors is running on the WFE. Beyond that, the farm has these symptoms:
    It "works" albeit very slowly. Crawl rate of 2-7 dps for both external file shares and the SP content (both with and without Task Offloading / Chimney Offloading enabled). It seems to frequently recycle or take an otherwise long time to render
    in the browser (any page). Finally, it  spews tens of thousands of errors 24x7 on the WFE saying a SQL server (unnamed) cannot be contacted via Named Pipes.
    Specifically: "Unknown SQL Exception 53 occurred. Additional error information from SQL Server is included below.  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)".
    The next error in the sequence is: "An internal error occurred while running a timer job: 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) at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject,
    UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)..."
    This is followed by an error such as this: "There was an internal error invoking the timer job '{E4DDC92E-0056-4E7E-BD3F-1CF5670ACB7D}' for service '{6105D588-FB34-4F1C-82F6-479D7FE146EA}'."
    Of course, each time the timer job mentioned is different. 
    One more error appears consistently with these although not as frequently: "The Execute method of job definition Microsoft.SharePoint.Diagnostics.SPDiagnosticsMetricsProvider (ID 36e6942a-9a80-440f-94a4-e4a606362734) threw an exception. More information
    is included below.  Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.  This could be because the pre-login handshake failed or the server was unable to respond back in
    time.  The duration spent while attempting to connect to this server was - [Pre-Login] initialization=21276; handshake=0;"
    I have been troubleshooting this for days but am not making much progress. How can I determine just what SQL server it says it cannot find and where that server name is stored? It seems like it has to be part of the Timer job configuration since the two
    things are related.

    Hi,
    Thanks for your sharing and have a good day.
    Jason
    Jason Guo
    TechNet Community Support

  • Cannot Restore SQL Server 2008 Server Backup

    PLEASE HELP!!!
    Please I did an Sql database backup for my application server, has some issues with my application data and tried restoring the database but kept getting the error........
    PLEASE MY COMPANY IS HELD TO RANSOM AS WE NEED THE MOST RECENT BACKUP TO WORK!!!

    Thank you Shanky_621 for replying.
    The error is:
    "SQL Server :: Object Cannot Be Cast From DBNull To Other Types"
    Dont use GUI to restore database.This issue can come sometimes when your login is not administrator in SQL Server, instead use below query
    RESTORE FILELISTONLY
    FROM disk= 'AdventureWorks2008R2_Backup'--this would be your backup location
    -- Restore the files for MyAdvWorks.
    RESTORE DATABASE MyAdvWorks--your database name
    FROM AdventureWorks2008R2_Backup
    WITH RECOVERY,
    MOVE 'AdventureWorks2008R2_Data' TO 'D:\MyData\MyAdvWorks_Data.mdf',
    MOVE 'AdventureWorks2008R2_Log' TO 'F:\MyLog\MyAdvWorks_Log.ldf'
    GO
    --specifiy drive where you want to restore database and kjust replace mdf and ndf with name you like in above script
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Sql Server 2008 - problems after incorrect installation of SSIS component

    During the addition of SSIS component to an existing installation of Sql Server 2008 the setup has been made using Sql Server 2008 R2 media.
    Now SSMS shows the following error during the connection to the instance :
    Method not found: 'Int32.Microsoft.SqlServer.Management.Sdk.Sfc.ISfcDomain.GetLogicalVersion()'
    I've tried to remove R2 components and to repair the existing 2008 installation.
    At the moment 2008 R2 Native client and Setup are still present in the list of Programs and Features.
    From previous comments I understand this method is in a Sql Server 2008 R2 assembly, so it seems that SSMS is running as R2 but is using 2008 libraries.
    How can I correct this ?
    Thanks.

    Hello,
    Be careful uninstalling now SQL Server 2008 R2 components. If you uninstall shared components that are SQL Server 2008
    R2 components the whole SQL Server 2008 instance will be unusable. For more information about having SQL Server 2008 and SQL Server 2008 R2 installed on the same computer, please read the following article:
    http://msdn.microsoft.com/en-us/library/ee210714(v=sql.105).aspx
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • SQL server 2008 R2 doesnt work in win 8.1

    Hi,
    I have installed SQL server 2008 R2 in windows 8 64 bit machine and it was working fine. 2 days back i upgrade the OS to windows 8.1 and the process went smooth. Now when i start the SQL server, I couldn't able to login.
    When I checked the service, i wonder that there are no SQL server 2008 instance running the services list.
    Regards, Anbu.

    Try to install the SQL Server After the upgrade. You will get an alert saying this version not fit to the OS and an option to continue in the installation or aboard. You can chose to continue (on your
    own responsibility and after you have read the link information!).
    please inform us if this worked ;-)
    * i prefer to re-install OS and never to use upgrade. it is always good to clean things up, and upgrade an OS is a big step fit with cleaning our old OS.
    [Personal Site] [Blog] [Facebook]

  • SQL SERVER 2008 R2 SP2 APPLYING AFTER GEETING ERROR

    HI,
    I had updated 2008 R2 (RTM) VERSION to sp2.After that I was unable to open the SQL server instance and getting error messege
    Like "Error: 18401
    Login failed for user '<abc><login name><abc>'. Reason: Server is in script upgrade mode. Only administrator can connect at this time."
    note : here i am the Administrator.

    Hello,
    The following post may be useful:
    http://blogs.msdn.com/b/sqlserverfaq/archive/2010/03/31/unable-to-connect-to-sql-server-2008-instance-after-applying-sp1.aspx
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • CF 9 Enterprise - SQL Server 2008 SLOW

    Hello all-
    We've been running CF8 standard on a 32 bit Windows Server 2003 box.  Everything is fine and dandy.
    We are upgrading to CF9 Enterprise on a 64 bit Windows Server 2008 r2 box, but things are not going well.
    Both of these servers are connecting to the same database, on the same SQL Server 2008 instance.
    I am having some fairly serious slowdowns in our SQL queries on our new CF9 box.  Queries that are taking 30 milliseconds on the old server, are taking 250+ milliseconds on the new server.  This is happening between different databases, different queries, etc.  This new server is just a whole lot slower when connecting to the exact same SQL Server.
    I've pinged our database server from both CF servers- no difference.  (Both are 0 ms)
    The old server is running version 2000.86.3959 of the SQL Server driver (2/17/2007).
    The new server is running version 6.01.7600.16385 (7/13/2009)
    Any ideas as to what could be causing the slowdown?
    Thanks,
    Karl
    Message was edited by: karlkrist to add sql server driver versions

    I've never encountered this problem, I'm not using CF9 or SQL 20008; but here are some things to investigate.
    1. Are there any differences in the way your datasources are configured in CF between the two servers.  For example, do you have the "Maintain Connections" option enabled on one server's datasource, but not the other? 
    2. You might try using an alternate JDBC driver to see if this issue is caused by the drivers.  Microsoft produces as JDBC driver for SQL server and I think there may be open source options. 
    Microsoft's JDDB driver:
    http://www.microsoft.com/downloads/details.aspx?FamilyID=99b21b65-e98f-4a61-b811-19912601f dc9&displaylang=en

  • Is 'SQLCMD.EXE' the SQL Server 2008 executable to be added to a Firewall 'Inbound Rule' to allow remote access?

    I would like to add a new Firewall 'Inbound Rule' to allow remote access by
    SQL Server 2008.    
    SQL Server Management Studio shows two TCP/IP instances, both of which are Enabled. 
    One uses port 1433 and the other uses ‘TCP Dynamic Ports’.
      In  SQL Server, the server has ‘Allow remote connections to this server’ checked.
    My Firewall allows port 1433 for the one TCP/IP instance. 
    Since the other instance is dynamic, I would like to add a new
    Firewall 'Inbound Rule' to allow the SQL Server executable to run.
    I’ve read that the SQL Server executable is commonly named SQLSERVR.EXE, but there is no such file on my laptop. 
    I’m assuming the executable that needs to be added to the Firewall 'Inbound Rule'
    is SQLCMD.EXE (in the path C:\Program Files\Microsoft SQL Server\100\Tools\Binn). 
    Can anyone please confirm this?  (I'm running Windows 7).  Thanks.

    Hi Bontrager,
    Firstly, please run
    Discovery Report to the detect the existing SQL Server 2008 instance. If SQL Server 2008 is installed properly on your machine, the sqlservr.exe should exists in C:\Program Files\Microsoft SQL Server\MSSQL10.<instance_name>\MSSQL\Binn.
    Secondly, if SQL Server 2008 is configured to use dynamic port, it is difficult to configure the firewall to enable access to the correct port number because the port selected might change every time that the Database Engine is started.
    Therefore, if a firewall is used, please reconfigure the SQL Server 2008 to use the static TCP port by using SQL Server 2008 Configuration Manager. 
    For more information, please review this
    article. After that, you can add the port number in firewall inbound rule.
    Thirdly, if you want to connect to  SQL Server 2008 from outside the firewall by instance name, SQL Server Browser should be turned on and you'll have to allow the SQL Server Browser through the firewall, which is UDP port 1434.
    Reference:
    https://msdn.microsoft.com/en-us/library/cc646023.aspx
    http://stackoverflow.com/questions/10539900/opening-ports-sql-server-instances
    Thanks,
    Lydia Zhang
    Lydia Zhang
    TechNet Community Support

  • Error 18452 "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication" on SQL Server 2008 R2 Enterprise Edition 64-bit SP2 clustered instance

    Hi there,
    I have a Windows 2008 R2 Enterprise x64 SP2 cluster which has 2 SQL Server 2008 R2 Enterprise Edition x64 SP2
    instances.
    A domain account "Domain\Login" is administrator on both physcial nodes and "sysadmin" on both SQL Server instances.
    Currently both instances are running on same node.
    While logging on to SQL Server instance 2 thru "Domain\Login" using "IP2,port2", I get error 18452 "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication". This happened in the past
    as well but issue resolved post insatllation of SQL Server 2008R2 SP2. This has re-occurred now. But it connects using 'SQLVirtual2\Instance2' without issue.
    Same login with same rights is able to access Instance 1 on both 'SQLVirtual1\Instance1' and "IP1,port1" without any issue.
    Please help resolve the issue.
    Thanks,
    AY

    Hello,
    I Confirm that I encountred the same problem when the first domain controller was dow !!
    During a restarting of the first domain controller, i tried to failover my SQL Server instance to a second node, after that I will be able to authenticate SQL Server Login but Windows Login returns Error 18452 !
    When the firts DC restart finishied restarting every thing was Ok !
    The Question here : Why the cluster instance does'nt used the second DC ???
    Best Regards     
    J.K

  • SQL Server 2008 R2 - Cannot remove 50th instance with command line uninstall

    I have reached the 50 instance SQL Server limit on my Microsoft Server 2008.  I have tried to remove an existing instance using the command line below but it still is reporting that "No more transforms are available because the maximum 50 has been
    reached." and the uninstall is hanging on Select Features.  Some of the instances on this server are for SQL Server 2008 and some are for R2.  Where do I go from here?
    "C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\setup.exe" /Action=Uninstall /FEATURES=SQL /INSTANCENAME=myinstance

    "C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\setup.exe" /Action=Uninstall
    /FEATURES=SQL /INSTANCENAME=myinstance /Q
    Try this..
    /Q = Quite Mode.. 
    Chetan ================================================================== ================================================================ This posting is provided &quot;AS IS&quot; with no warranties, and confers no rights. Please remember to
    click &quot;Mark as Answer&quot; and &quot;Vote as Helpful&quot; on posts that help you. This can be beneficial to other community members reading the thread.

Maybe you are looking for

  • Submitting a Form in a Spry Tabbed Region

    I have a spry tabbed region with 6 tabs. I have constructed a menu which targets and opens the specific tab using the ?tab=4 type notation.  I have also created links between tabs using the same notation.  All works fine. I have a form in one tab whi

  • How do I make a button in Photoshop for Muse?

    Three months ago I found this info, and I've made a dozen buttons. Can't remember how to do it. I've spent all afternoon trying to find the info. All I get is how to place a button. How do I make it?

  • You have an Amazon wish list button available as an add on and I can't successfully install it.

    I've tried adding it on from the Amazon site and also from the Firefox "add-ons" page. It shows the install bar moving across, says do I want to restart Firefox. I click to restart, it restarts and the button isn't there. With the Amazon toolbar, I d

  • Automatic run for incoming payment

    Hi all, is there any possibility to run an automatic incoming payment the way F110 works for outgoing payments. If there is, how does it work? Thanks and regards Claudia.

  • Regarding SAP PP Mapping

    Dear Sir,               My requirement is that, I have a mother coil,Mmetal Sheet) which has to be cut into no. of smaller coil (baby Coil). Along with baby coil some wastage will also will be produced.The Baby coil is being used in the process order