Hi All,

I am trying to install SQL Server 2014 express edition on my Windows 7 64 Bit system, but unfortunately, everything I have tried so far has resulted in the same error.

Error: 1723 There is a problem with this Windows Installer package. A DLL required for this installation to complete could not be run. Contact your support personnel or package vendor.

I have tried all the possible solutions that I found online. So please refrain from posting a link to another blog or forum because chances are that I have already tried that.

Things that I have tried:

• Giving myself/Everyone "Full Control" over the folder C:\Users\username\AppData\Local\Temp
• Disabling .Net Framework 3.5 SP1 and then re-enabling.
• Installing sqlncli.msi manually from cmd with Administrative Privileges (Note that this too fails with the same error).
• Removing all instances and traces (registry values, folders, uninstalling) of SQL Server 2008 R2 installed previously on my machine. 
• Downloading SQL Server from Microsoft's website again (in case the previous installer was corrupted), performed checksum and validated the installer.
• Making sure that I have Service Pack 1 installed for my operating system.
• Resetting windows installer.

I am aware that there are multiple threads with the same issue, but none have been able to resolve this for me. 

It is really urgent for me to resolve this and install the package over the weekend. Any help would be really appreciated.

Note: I am unable to add the links to the log files as of now, but would do so ASAP.

Hi everyone,

  Following an upgrade to SQL Server 2012 which didn't succeed, someone recommended that I repair my actual SQL Server 2008 R2 SP2 setup.  The actual setup I have, which btw is running without any problem, is the following:

• SQL Server 2008 R2 SP2 CU1 Express Edition with advanced services  (Reporting Services is installed and active)
• Visual Studio 2010 SP1 Professionnal Edition
• Visual Studio 2008 SP1 Express Edition
• Windows VISTA SP2 Ultimate Edition

  My request is very simple.  Before repairing a SQL setup:

• Do I need to stop any services?
• Any other thing I should stop, uninstall or else?
• Do I launch the repair from the "Control Panel - Install/uninstall program" menu or can I just run the "SQL Server 2008 R2 SP2" setup file I just downloaded from the .NET.  I prefer asking because I thought that running this setup file under administrative rights could help avoiding privilege problems or else?

  Hope to hear from someone,

Stéphane

I have Win2008 Std 64-bit Server.  We previously had SQL Express 2005 (build 2047 SP1) 32-bit, and I successfully loaded "SQL Express 2005 plus SP4" (build 5000 SP4) on top if it (upgraded), and did the server reboot.  I then tried to apply SQL 2005 SP4 CU#2 (build 5259 SP4 CU-2) to the SQL Express on the server.  It failed, with below errors.  

FYI.  The install files (SP4 and CU#2) have been successfully appliled to other machines.  I have already recopied the files over, and same error.

FYI-2.  I see a CONNECT write-up on same issue - no answer.

http://connect.microsoft.com/SQLServer/feedback/details/635149/cu-1-on-sql-server-2005-express-sp4-fails-to-install

Time: 05/18/2011 19:07:25.767

KB Number: KB2489409

Machine: SPNC222S

OS Version: Server 4.0 Service Pack 2 (Build 6002)

Package Language: 1033 (ENU)

Package Platform: x86

Package SP Level: 4

Package Version: 5259

Command-line parameters specified:

Cluster Installation: No

**********************************************************************************

Prerequisites Check & Status

SQLSupport: Passed

**********************************************************************************

Products Detected                         Language  Level  Patch Level       Platform  Edition

SQL Server Database Services 2005 (SQLEXPRESS)  ENU       SP4    2005.090.5000.00  x86       EXPRESS

SQL Server Tools and Workstation Components 2005  ENU       SP3           9.3.4035  x86       EXPRESS

**********************************************************************************

Products Disqualified & Reason

Product                                   Reason

SQL Server Tools and Workstation Components 2005  The product instance SQL Tools does not have prerequisite update 5000 installed. Update 5259 is dependent on prerequisite update 5000. Exit setup and refer to the Knowledge Base article to find the prerequisite patch. Install the prerequisite and rerun the installation.

**********************************************************************************

Processes Locking Files

Process Name          Feature               Type          User Name                  PID

MSSQL$SQLEXPRESS      SQL Server Database Services  Service                                  5072

**********************************************************************************

Product Installation Status

Product                   : SQL Server Database Services 2005 (SQLEXPRESS)

Product Version (Previous): 5000

Product Version (Final)   :

Status                    : Failure

Log File                  : C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2489409_sqlrun_sql.msp.log

SQL Express Features      :

Error Number              : 2709

Error Description         : MSP Error: 2709  The installer has encountered an unexpected error. The error code is 2709. The specified Component name ('SxSComp.4726A3114E714980AA23A8BA9E4330D6') not found in Component table.

----------------------------------------------------------------------------------

Product                   : SQL Server Tools and Workstation Components 2005

Product Version (Previous): 4035

Product Version (Final)   :

Status                    : NA

Log File                  :

SQL Express Features      :

Error Description         : The product instance SQL Tools does not have prerequisite update 5000 installed. Update 5259 is dependent on prerequisite update 5000. Exit setup and refer to the Knowledge Base article to find the prerequisite patch. Install the prerequisite and rerun the installation.

----------------------------------------------------------------------------------

**********************************************************************************

Summary

     One or more products failed to install, see above for details

     Exit Code Returned: 2709

Hi All

I have a question about Service Packs and Cumulative Updates for SQL 2008 R2.

Do you need to apply them in the order that they are released? Or can you just apply the latest Service Pack and Cumulative Update?

Regards

Hi Team,

I have been looking whether my SQL Server 2005 (Enterprise Edition) - SP4 instance is licensed version or not on windows server 2003 standard edition. This instance was installed few year back, is there any way to find out the whether my SQL Server software is licenced or not.

Thanks,

Dathuraj

Dathuraj

I am attempting to do a silent install of SQL Server 2008r2 EXPRESS that includes SQL Server Management Studio. I am failing to get Management Studio as part of the install. My command is:

C:\Users\Root\Desktop\SQLServer2008r2\SQLEXPRWT_x64_ENU.exe /QS /INSTANCENAME=MSSQLSERVER /ACTION=Install /FEATURES=SQL,BC,Conn,ADV_SSMS /SAPWD=Password1! /SECURITYMODE=SQL /TCPENABLED=1 /ADDCURRENTUSERASSQLADMIN /SQLSVCSTARTUPTYPE=Automatic /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" /AGTSVCACCOUNT="NT AUTHORITY\SYSTEM" /IACCEPTSQLSERVERLICENSETERMS

This is based on docs here:

https://technet.microsoft.com/en-us/library/ms144259%28v=sql.105%29.aspx?f=255&MSPPError=-2147217396#Feature

which show that the /FEATURES= parameter should include ADV_SSMS to get SQL Server Management Studio. 

I will post contents of various install logs in separate messages below. Any ideas why the Management Studio is not getting installed?

Hello team,

We were installing SQL Server 2014 as a part of setting up our SharePoint 2013 environment.

In the "installation section" the setup failed giving the following error:

Cannot use file 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer.mdf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size.

We checked the details of the E: partition as follows by running command "Fsutil fsinfo ntfsinfo e:" --

Bytes Per Sector  :               512
Bytes Per Physical Sector :       4096
Bytes Per Cluster :               4096

Now we are not sure if the formatting has gone wrong or any other thing. For reference, the error log is as follows:

2015-06-02 07:07:39.71 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
	Feb 20 2014 20:04:26
	Copyright (c) Microsoft Corporation
	Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.3 <X64> (Build 9600: )

2015-06-02 07:07:39.71 Server      UTC adjustment: -4:00
2015-06-02 07:07:39.71 Server      (c) Microsoft Corporation.
2015-06-02 07:07:39.71 Server      All rights reserved.
2015-06-02 07:07:39.71 Server      Server process ID is 3100.
2015-06-02 07:07:39.71 Server      System Manufacturer: 'IBM', System Model: 'System x3550 M3 -[7944AC1]-'.
2015-06-02 07:07:39.71 Server      Authentication mode is MIXED.
2015-06-02 07:07:39.71 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2015-06-02 07:07:39.72 Server      The service account is 'domain\sql_services'. This is an informational message; no user action is required.
2015-06-02 07:07:39.72 Server      Registry startup parameters:
	 -d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
	 -e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
	 -l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2015-06-02 07:07:39.72 Server      Command Line Startup Parameters:
	 -s "MSSQLSERVER"
	 -m "SqlSetup"
	 -Q
	 -q "SQL_Latin1_General_CP1_CI_AS"
	 -T 4022
	 -T 4010
	 -T 3659
	 -T 3610
	 -T 8015
2015-06-02 07:07:39.98 Server      SQL Server detected 2 sockets with 4 cores per socket and 8 logical processors per socket, 16 total logical processors; using 16 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2015-06-02 07:07:39.98 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-06-02 07:07:39.98 Server      Detected 16372 MB of RAM. This is an informational message; no user action is required.
2015-06-02 07:07:39.98 Server      Using conventional memory in the memory manager.
2015-06-02 07:07:40.26 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2015-06-02 07:07:40.30 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2015-06-02 07:07:40.32 Server      Query Store settings initialized with enabled = 1,
2015-06-02 07:07:40.32 Server      The maximum number of dedicated administrator connections for this instance is '1'
2015-06-02 07:07:40.33 Server      Node configuration: node 0: CPU mask: 0x000000000000ffff:0 Active CPU mask: 0x000000000000ffff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-06-02 07:07:40.35 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.
2015-06-02 07:07:40.35 Server      Lock partitioning is enabled.  This is an informational message only. No user action is required.
2015-06-02 07:07:40.38 Server      Database Mirroring Transport is disabled in the endpoint configuration.
2015-06-02 07:07:40.38 spid8s      Warning ******************
2015-06-02 07:07:40.39 spid8s      SQL Server started in single-user mode. This an informational message only. No user action is required.
2015-06-02 07:07:40.39 spid8s      Starting up database 'master'.
2015-06-02 07:07:40.47 Server      CLR version v4.0.30319 loaded.
2015-06-02 07:07:40.49 Server      Software Usage Metrics is disabled.
2015-06-02 07:07:40.70 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-06-02 07:07:40.81 spid8s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-06-02 07:07:40.81 spid8s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-06-02 07:07:40.88 spid8s      SQL Trace ID 1 was started by login "sa".
2015-06-02 07:07:40.90 spid8s      Server name is 'INTRAUATDB2013'. This is an informational message only. No user action is required.
2015-06-02 07:07:40.91 spid17s     Password policy update was successful.
2015-06-02 07:07:40.96 spid17s     A self-generated certificate was successfully loaded for encryption.
2015-06-02 07:07:40.96 spid17s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2015-06-02 07:07:40.96 spid17s     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.
2015-06-02 07:07:40.96 spid17s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2015-06-02 07:07:40.96 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2015-06-02 07:07:40.98 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/IntraUATDB2013.***.****.com ] for the SQL Server service. Windows return code: 0x2098, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2015-06-02 07:07:40.98 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/IntraUATDB2013.***.****.com:1433 ] for the SQL Server service. Windows return code: 0x2098, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2015-06-02 07:07:42.48 spid18s     A new instance of the full-text filter daemon host process has been successfully started.
2015-06-02 07:07:42.66 spid8s      Starting up database 'msdb'.
2015-06-02 07:07:42.67 spid11s     Starting up database 'mssqlsystemresource'.
2015-06-02 07:07:42.69 spid11s     The resource database build version is 12.00.2000. This is an informational message only. No user action is required.
2015-06-02 07:07:42.83 spid11s     Starting up database 'model'.
2015-06-02 07:07:43.09 spid11s     Clearing tempdb database.
2015-06-02 07:07:43.60 spid11s     Starting up database 'tempdb'.
2015-06-02 07:07:43.71 spid8s      Recovery is complete. This is an informational message only. No user action is required.
2015-06-02 07:07:43.81 spid51      Changed database context to 'master'.
2015-06-02 07:07:43.81 spid51      Changed language setting to us_english.
2015-06-02 07:07:44.03 spid51      Setting database option RECOVERY to FULL for database 'model'.
2015-06-02 07:07:44.09 spid51      Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-06-02 07:07:44.12 spid51      Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
2015-06-02 07:07:44.13 spid51      Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
2015-06-02 07:07:44.14 spid51      Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-06-02 07:07:44.26 spid51      Setting database option NEW_BROKER to ON for database 'tempdb'.
2015-06-02 07:07:44.30 spid51      Setting database option NEW_BROKER to ON for database 'msdb'.
2015-06-02 07:07:44.43 spid51      The file "tempdev" has been modified in the system catalog. The new path will be used the next time the database is started.
2015-06-02 07:07:44.44 spid51      The file "templog" has been modified in the system catalog. The new path will be used the next time the database is started.
2015-06-02 07:07:44.59 spid51      Changed database context to 'master'.
2015-06-02 07:07:44.59 spid51      Changed language setting to us_english.
2015-06-02 07:07:44.86 spid51      Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-06-02 07:07:44.88 spid51      Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-06-02 07:07:44.90 spid51      Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2015-06-02 07:07:44.94 spid51      Using 'xpstar.dll' version '2014.120.2000' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2015-06-02 07:07:44.96 spid51      Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-06-02 07:07:44.97 spid51      Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-06-02 07:07:46.11 spid51      Changed database context to 'master'.
2015-06-02 07:07:46.11 spid51      Changed language setting to us_english.
2015-06-02 07:07:46.27 spid51      Error: 5179, Severity: 16, State: 1.
2015-06-02 07:07:46.27 spid51      Cannot use file 'F:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer_log.ldf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size.
2015-06-02 07:07:46.27 spid51      Error: 5179, Severity: 16, State: 1.
2015-06-02 07:07:46.27 spid51      Cannot use file 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer.mdf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size.
2015-06-02 07:07:46.27 spid51      Error: 5179, Severity: 16, State: 1.
2015-06-02 07:07:46.27 spid51      Cannot use file 'F:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer_log.ldf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size.
2015-06-02 07:07:46.27 spid51      Error: 5179, Severity: 16, State: 1.
2015-06-02 07:07:46.27 spid51      Cannot use file 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer.mdf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size.
2015-06-02 07:07:46.27 spid51      Error: 1802, Severity: 16, State: 4.
2015-06-02 07:07:46.27 spid51      CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
2015-06-02 07:42:06.49 spid51      Error: 5179, Severity: 16, State: 1.
2015-06-02 07:42:06.49 spid51      Cannot use file 'F:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer_log.ldf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size.
2015-06-02 07:42:06.49 spid51      Error: 5179, Severity: 16, State: 1.
2015-06-02 07:42:06.49 spid51      Cannot use file 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer.mdf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size.
2015-06-02 07:42:06.49 spid51      Error: 5179, Severity: 16, State: 1.
2015-06-02 07:42:06.49 spid51      Cannot use file 'F:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer_log.ldf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size.
2015-06-02 07:42:06.49 spid51      Error: 5179, Severity: 16, State: 1.
2015-06-02 07:42:06.49 spid51      Cannot use file 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Data\ReportServer.mdf', because it is on a volume with sector size 2097152. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size.
2015-06-02 07:42:06.49 spid51      Error: 1802, Severity: 16, State: 4.
2015-06-02 07:42:06.49 spid51      CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
2015-06-02 07:48:37.45 Logon       Error: 18461, Severity: 14, State: 1.
2015-06-02 07:48:37.45 Logon       Login failed for user 'domain\sql_admin'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
2015-06-02 07:49:43.17 Logon       Error: 18461, Severity: 14, State: 1.
2015-06-02 07:49:43.17 Logon       Login failed for user 'domain\sql_services'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
2015-06-02 07:49:43.19 Logon       Error: 18461, Severity: 14, State: 1.
2015-06-02 07:49:43.19 Logon       Login failed for user 'domain\sql_services'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
2015-06-02 08:01:23.49 Logon       Error: 18461, Severity: 14, State: 1.
2015-06-02 08:01:23.49 Logon       Login failed for user 'sa'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]

Regards, Nayan

Hi,

I downlaoded SQL Server Express 2014 and double click to install it. The file decompress box appears. When it finished, it closed and then no other dialog / instructions appears. 

I checked the SQL log file at TEMP folder and found that it attempted to remove .Net security code group node and then close the setup with code 0x00000000

Seems I cannot upload the whole log file here thus I copied some below:

Hello Guys,

We have two nodes and of course some clustered disks {data, logs, etc..}

We will migrate to new Storage >> please correct me if i'm wrong but the simplest way is to

1. Stop the SQL Services and start the storage migration

2. Add the new Storage to the Clustered SQL Instance (from the failover manager)

3. Remove the old storage from the SQL Instance (from the failover manager)

4. Assign the old driver letters to the new storage

5. start the SQL Services ..

----------------------------------------------------------------

Friend of mine told me this is wrong. and i should after "step 2" i need to de-attach all SQL Databases and after step 4.. i should reattach them all again to make sure. 

I don't understand why ! i will be using the same driver letters and no need to re attach them again ! 

Thanks in advance :)

Hi,

I am using windows 8 and I have only one user in laptop. While installing SQL 2014, I am getting an error (Missing System Administrator). Under SQL Server Agent and SQL Server Database I have select the system user and gave the password but still I am getting the error.

Can anyone please help me how to resolve this.

Thanks in advance.

NRC

Hi,

I know there's an option in the SSMS to remove the hook at the option

"Prevent Saving changes that require table re-creation".

But how can I set the option silent. I mean for instance at the setup or by a secret T-SQL command or setting a value in a hidden file? I don't want the user to open the options dialog.

Help would be appreciated. Thanks

EDIT:

Hi, thanks to all answers.

I found a way to solve this after I stumbled over the word "registry" in some community.

Then I logged the registry by a tool and alas there was it. So the thing is to set

the registry entry by our own setup after installing the SSMS.

when i m trying to install SQl Server 2008 R2 the following errors are occurred

cannot find service{0}.

Parameter name:MSSQLServerADHelper100

I am using SQL Server 2008 R2. I'd like to set up a reporting server with SSRS but I cannot find out how to install it. Please help.

Thanks

Dear Expert,

This is my first question to this forum and poor in english.

I had made certain application with Back end MS SQL 2008 Express.

Few of My client needs to run the same application in their portable Drive (Ext. HDD).They have intention to work on on application in window PC or Laptop.

I came to know about MS sql local DB 2012 which has no installation issue and start its services as and when require.

But I m not finding the way how to run / deploy my application along with MS SQL local DB.

Please help.

I am currently utilizing a cloud server with SQL 2012 Web Edition.  I am planning on moving my application to a dedicated server at a data center.  The data center can deliver the machine with 2012 Windows Server for $15/mo.  The data center has inquired with their MS partner about SQL and have quoted outrageous licensing fees.  They are not familiar with the Web edition.  How does the data center acquire a license for the Web Edition so it can be loaded on my dedicated server?

SQL Server Web edition is designed to support internet-facing workloads and enables organizations to rapidly deploy web pages, applications, websites and services. Available via SPLA – ask your service provider for more information.

Hello All,

I've a SQL server 2014 setup on a server recently. Can I add a new(second) instance to the SQL server (already running one instance)? Any help/documentation is greatly appreciated.

Thanks

Hello,

I have build a setup in Visual Studio. An Installer dll is also used.

At the  public override void Commit(System.Collections.IDictionary savedState) method (custom action) of the installer I run the following :

Process.Start(sqlExe, prms);

where sqlExe is the setup.exe file and prms = "/q /ACTION=Install /INSTANCENAME=xxxx_1 /FEATURES=SQL /IACCEPTSQLSERVERLICENSETERMS /SECURITYMODE=SQL /SAPWD=xxxx /SQLSVCACCOUNT=\"NT AUTHORITY\\SYSTEM\" /AGTSVCACCOUNT=\"NT AUTHORITY\\SYSTEM\" /ASSVCACCOUNT=\"NT AUTHORITY\\SYSTEM\" /RSSVCACCOUNT=\"NT AUTHORITY\\SYSTEM\" /SQLSYSADMINACCOUNTS=BUILTIN\\ADMINISTRATORS /ENABLERANU /NPENABLED=1 /TCPENABLED=1";

The setup finishes ok but when I try to access the SQL Server from management studio I get the error : Login failed for user 'xxxxx'. Reason: Server is in single user mode. Only one administrator can connect at this time. (Microsoft SQL Server, Error: 18461)

If I run the same SQL Server installation from an application it works fine.

Any idea why this is happening?

Thank you

Yannis

Not long ago I realized that the WSUS database and related files on my server were about to overwhelm the partition (O/S partition) where they were originally installed. Realizing this was a problem that was only going to get worse I decided to relocated the WSUS files and databases to a larger partition on the same server.  To do this I used the Microsoft instructions (How to Move WSUS Content and Database Files to a Different Volume) to move the content and the databases to the new partition.  Everything seemed to go as planned.

Apparently I must've messed up somewhere along the line because the SUSDB.mdf files on the original drive (C-Drive) appear to still be in use, and the SUSDB.mdf files on the new, larger drive (E-Drive) aren't being touched.  There does appear to be current activity in the E:\WSUS\WsusContent\ folder, but the "Modified date" of the .mdf file located in E:\WSUS\SUSDB\UpdateServicesDbFiles directory hasn't changed since I moved it (two months ago).

As an added "gotcha", soon after I tried to move the WSUS files I started encountering problems with my backups (which are dependent on Microsoft's VSS service to complete normally).  A server reboot would clear up backup problems for a few days, then after a few days backups would start failing again.  A review of my server's log files revealed a bunch of MSSQL$MICROSOFT##SSEE errors (3197, 3198, and 18264).

So I feel like I'm up against some problems here related to MYSQL and VSS that are over my head.  Can anyone help me clear these up?  Many advance thanks.

SBS 2011 Standard, SP1, 64-Bit

Joe

Hello dear gurus,

We have a critical cluster with Windows Server 2008 R2 SP1 on board and a SQL clustered instance installed there with SQL Server 2008 R2 SP1. Since a maintenance window is very short we are going to upgrade this instance till SQL Server 2008 R2 SP3. Besides that change should be implemented very soon by a customer's demand. The only problem is that the operating system (OS) has never been patched. Could you please advise if there are really critical OS patches without which a SQL Server instance will not work after the upgrade? And if there are some what OS patches should be installed first?

Thank you for replies in advance.