Unable to install SQLExpress 2008 R2 using installer class

Algemene discussie Unable to install SQLExpress 2008 R2 using installer class

  • Donnerstag, 3. November 2011 13:55
     
      Enthält Code

    Hi,

       In our Application we are creating a setup. We need SQL to be installed in the client machine if it is not installed. I have created a installer class. Through this installer class we are trying to install SQL. New instance is created but When I try to connect it in the Management studio it throws the Following Error:

     

    Cannot connect to 'Instance Name'

    ADDITIONAL INFORMATION:

    Login failed for user 'DomainName\UserName'. Reason: Server is in single user mode. Only one administrator can connect at this time. (Microsoft SQL Server, Error: 18461)

           I can install SQL through command prompt, Console application without any probelm. The problem occurs only when I try to install using InstallerClass. We used Even ConfigurationFile.ini, but that doesn't help us.  Below is the code We used in InstallerClass:

         Dim info As New System.Diagnostics.ProcessStartInfo("cmd.exe")
         info.FileName = "cmd.exe"
         info.Arguments = "/c" & " C:\Users\parameswari\Desktop\SQL.exe /Q /ACTION=INSTALL /FEATURES=SQLEngine,REPLICATION /INSTANCENAME=BUSACT5 /SQLSVCACCOUNT=" & ChrW(34) & "NT AUTHORITY\System" & ChrW(34) & " /SQLSVCSTARTUPTYPE=" & ChrW(34) & "Automatic" & ChrW(34) & " /IACCEPTSQLSERVERLICENSETERMS=" & ChrW(34) & "True" & ChrW(34) & " /SQLSYSADMINACCOUNTS=" & ChrW(34) & "DD\parameswari" & ChrW(34)
         Dim process As New System.Diagnostics.Process
         process.StartInfo = info
         process.Start()
         process.WaitForExit()
         process.Close()
    

     Below is the ERRORLOG:

    2011-11-03 16:58:49.49 Server      Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (Intel X86) 

    Apr  2 2010 15:53:02 

    Copyright (c) Microsoft Corporation

    Express Edition on Windows NT 6.1 <X86> (Build 7601: Service Pack 1)

     

    2011-11-03 16:58:49.49 Server      (c) Microsoft Corporation.

    2011-11-03 16:58:49.49 Server      All rights reserved.

    2011-11-03 16:58:49.49 Server      Server process ID is 268.

    2011-11-03 16:58:49.49 Server      Authentication mode is MIXED.

    2011-11-03 16:58:49.49 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.BUSACT8\MSSQL\Log\ERRORLOG'.

    2011-11-03 16:58:49.50 Server      Registry startup parameters: 

    -d c:\Program Files\Microsoft SQL Server\MSSQL10_50.BUSACT8\MSSQL\DATA\master.mdf

    -e c:\Program Files\Microsoft SQL Server\MSSQL10_50.BUSACT8\MSSQL\Log\ERRORLOG

    -l c:\Program Files\Microsoft SQL Server\MSSQL10_50.BUSACT8\MSSQL\DATA\mastlog.ldf

    2011-11-03 16:58:49.50 Server      Command Line Startup Parameters:

    -m SqlSetup

    -f

    -Q

    -q SQL_Latin1_General_CP1_CI_AS

    -T 4022

    -T 4010

    -T 3659

    -T 3610

    -d c:\Program Files\Microsoft SQL Server\MSSQL10_50.BUSACT8\MSSQL\Template Data\master.mdf

    -l c:\Program Files\Microsoft SQL Server\MSSQL10_50.BUSACT8\MSSQL\Template Data\mastlog.ldf

    2011-11-03 16:58:49.56 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.

    2011-11-03 16:58:49.56 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

    2011-11-03 16:58:49.56 Server      Detected 2 CPUs. This is an informational message; no user action is required.

    2011-11-03 16:58:49.75 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.

    2011-11-03 16:58:49.75 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.

    2011-11-03 16:58:49.81 Server      Node configuration: node 0: CPU mask: 0x00000003:0 Active CPU mask: 0x00000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

    2011-11-03 16:58:49.84 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.

    2011-11-03 16:58:49.85 spid7s      Warning ******************

    2011-11-03 16:58:49.85 spid7s      SQL Server started in single-user mode. This an informational message only. No user action is required.

    2011-11-03 16:58:49.85 spid7s      Starting up database 'master'.

    2011-11-03 16:58:49.95 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.

    2011-11-03 16:58:50.07 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'BUSACT8'.

    2011-11-03 16:58:50.08 spid7s      Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.

    2011-11-03 16:58:50.08 spid7s      Starting up database 'mssqlsystemresource'.

    2011-11-03 16:58:50.11 spid7s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.

    2011-11-03 16:58:51.55 spid7s      Password policy update was successful.

    2011-11-03 16:58:51.80 spid8s      Starting up database 'model'.

    2011-11-03 16:58:51.84 spid7s      Server name is 'DDPRO67WIN7NX86\BUSACT8'. This is an informational message only. No user action is required.

    2011-11-03 16:58:51.84 spid7s      Informational: No full-text supported languages found.

    2011-11-03 16:58:52.41 Server      A self-generated certificate was successfully loaded for encryption.

    2011-11-03 16:58:52.45 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\BUSACT8 ].

    2011-11-03 16:58:52.63 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.

    2011-11-03 16:58:52.64 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x490, state: 16. 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.

    2011-11-03 16:58:53.12 spid8s      Clearing tempdb database.

    2011-11-03 16:58:53.16 Server      The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/DDPRO67WIN7NX86.DD.SERV:BUSACT8 ] for the SQL Server service. 

    2011-11-03 16:58:53.22 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.

    2011-11-03 16:58:55.09 spid8s      Starting up database 'tempdb'.

    2011-11-03 16:58:57.21 spid7s      Recovery is complete. This is an informational message only. No user action is required.

    2011-11-03 17:11:19.55 Logon       Error: 18461, Severity: 14, State: 1.

    2011-11-03 17:11:19.55 Logon       Login failed for user 'DD\parameswari'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]

    2011-11-03 17:11:36.83 Logon       Error: 18456, Severity: 14, State: 8.

    2011-11-03 17:11:36.83 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]

    2011-11-03 18:49:57.17 Logon       Error: 18456, Severity: 14, State: 8.

    2011-11-03 18:49:57.17 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]

    2011-11-03 18:50:14.77 Logon       Error: 18461, Severity: 14, State: 1.

    2011-11-03 18:50:14.77 Logon       Login failed for user 'DD\parameswari'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]

               Please guide us to solve this issue, past one week we are with this same issue. Waiting for your valuable reply.

    Thanks,

    Parameswari

     

     

     

     

Alle Antworten