I want to be able to install SQL Server during an automated server build while NOT logged into the machine. I have it installing SQL Server 2012 using a config file and setting the sa password. The installation completes but does not use the configuration file.

Can SQL Server 2012 be installed this way?

I had SQL Server 2008 R2 installed on a Win7 box, and upgraded it to SQL Server 2014. All seems to have gone well, but in the programs menu I can see that SSMS 2008 R2 is still installed. For some reason, I seem to have SQL Server 2012 installed as well, which is clever as I never installed it! I don't know if this came with SQL Server 2014, but I now seem to havethree versions of SQL Server installed!

Is there any reason why the old versions weren't uninstalled? Surely once I've upgraded, I don't need all the old stuff. Can I safely uninstall anything related to 2008 R2 and 2012, or will this cause problems?

Thanks

FREE custom controls for Lightswitch! A collection of useful controls for Lightswitch developers (Silverlight client only). Download from the Visual Studio Gallery.

If you're really bored, you could read about my experiments with .NET and some of Microsoft's newer technologies athttp://dotnetwhatnot.pixata.co.uk/

Hello all,

I have migrated a SQL Server 2014 Standard Edition with CU4 to SQL Server 2014 BI Edition. The BI-Edition has been installed from the RTM-Media. Do I have to apply the cumulative update again?

All services show the correct edition (BI) and version number (CU4). So may I assume that everything is correct?

Thanks in advance and best regards,
Gerald

Hello. We recently noticed at my company that our SQL Server cluster has not had any Windows Updates for about 2 years, so the need to bring it to a current status was created. However, I am unsure of what the best practices or guidelines are when applying OS (Windows Server 2008-2012) patches to SQL servers. I've seen cases where a Windows patch degrades SQL Server performance and cases where Windows is kept up to date with patches without issues.

Could someone share their methodology for this topic? Or point me to resources where I can find related information?

Thank you.

Leroy G. Brown

Node1: Primary server (DB name: TestDB1) Node2: Secondary server(configured always on for DB name TestDB1) Node3: Fileshare server(for automatic failover) Always on: Always on configured with automatic failover(move immediately if any failover scenario)

Testing Scenario: Node1 shutdown(primary shutdown) We did Node1 shutdown and node2 became primary. But TestDB1 database not able to access on NOde2(whichis beacme Primary after shut Node1 shut down).

we did below command as well net start clussvc /fq --on NOde2 (it showing that "requested service already started). in command line if we typ--> Cluster node ( status showing ---->Node1 down,Node2 UP)

Question: In order to access the TestDB1 database on Node2, what should we do? Is there any configuration change?

Note: After Node1 shutdown, Node2 instance is up and running, but not able to access the TestDB1 database.(TestDB1 database showin not synchronized)

thanks

Hi,

I still have an issue of installing SQL Management Studio 2012 or even any version, so it gives me errors and i don't know what to so with that. Many people saw that issue and no body could fix it, i really need your help and why SQL Management Studio can't be installed in my Windows 7 64 bit

Thanks so much

Raed

Hi - would really appreciate some help in troubleshooting my install, I've checked online for this error msg but couldn't find response related to SQL.

I had previously unistalled the trial edition & now received the above error when trying to install the developer edition on Windows XP SP 3, 32 bit, local system.

The log file is below:

Overall summary:
  Final result:                  SQL Server installation failed. To continue, investigate the reason for the

failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
  Exit code (Decimal):           -2068643839
  Exit facility code:            1203
  Exit error code:               1
  Exit message:                  SQL Server installation failed. To continue, investigate the reason for the

failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
  Start time:                    2009-10-23 10:14:29
  End time:                      2009-10-23 11:21:49
  Requested action:              Install
  Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup

Bootstrap\Log\20091023_100631\Detail.txt
  Exception help link:          

http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.r

ll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0x2659EC32%400x1447BB73

Machine Properties:
  Machine name:                  MAIN
  Machine processor count:       1
  OS version:                    Windows XP
  OS service pack:               Service Pack 3
  OS region:                     Australia
  OS language:                   English (United States)
  OS architecture:               x86
  Process architecture:          32 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                              

   Language             Edition              Version         Clustered

Package properties:
  Description:                   SQL Server Database Services 2008
  SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
  ProductName:                   SQL2008
  Type:                          RTM
  Version:                       10
  SPLevel:                       0
  Installation location:         D:\x86\setup\
  Installation edition:          DEVELOPER

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      False
  AGTSVCACCOUNT:                 SQLAGENT
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Manual
  ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Config
  ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Data
  ASDOMAINGROUP:                 <empty>
  ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log
  ASPROVIDERMSOLAP:              1
  ASSVCACCOUNT:                  SQLAS
  ASSVCPASSWORD:                 *****
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            MAIN\Peta Gray
  ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup

Bootstrap\Log\20091023_100631\ConfigurationFile.ini
  ENABLERANU:                    False
  ERRORREPORTING:                False
  FEATURES:                     

SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,SDK,SSMS,ADV_SSMS,SNAC_SDK,OCS
  FILESTREAMLEVEL:               2
  FILESTREAMSHARENAME:           MSSQLSERVER
  FTSVCACCOUNT:                  SQLFullText
  FTSVCPASSWORD:                 *****
  HELP:                          False
  INDICATEPROGRESS:              False
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    MSSQLSERVER
  INSTANCENAME:                  MSSQLSERVER
  ISSVCACCOUNT:                  SQLIS
  ISSVCPASSWORD:                 *****
  ISSVCSTARTUPTYPE:              Automatic
  MEDIASOURCE:                   D:\
  NPENABLED:                     0
  PID:                           *****
  QUIET:                         False
  QUIETSIMPLE:                   False
  RSINSTALLMODE:                 DefaultNativeMode
  RSSVCACCOUNT:                  MAIN\SQLRS
  RSSVCPASSWORD:                 *****
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  Latin1_General_CI_AS
  SQLSVCACCOUNT:                 SQLDE
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           MAIN\Peta Gray
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  False
  TCPENABLED:                    0
  X86:                           False

  Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup

Bootstrap\Log\20091023_100631\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x1447BB73
  Configuration error description: Some or all identity references could not be translated.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup

Bootstrap\Log\20091023_100631\Detail.txt

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x1447BB73
  Configuration error description: Some or all identity references could not be translated.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup

Bootstrap\Log\20091023_100631\Detail.txt

  Feature:                       Full-Text Search
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x1447BB73
  Configuration error description: Some or all identity references could not be translated.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup

Bootstrap\Log\20091023_100631\Detail.txt

  Feature:                       Analysis Services
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       Reporting Services
  Status:                        Failed: see logs for details
  MSI status:                    Passed
  Configuration status:          Failed: see details below
  Configuration error code:      0x1447BB73
  Configuration error description: Some or all identity references could not be translated.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup

Bootstrap\Log\20091023_100631\Detail.txt

  Feature:                       Integration Services
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       Client Tools Connectivity
  Status:                        Failed: see logs for details
  MSI status:                    Failed: see details below
  MSI error code:                0xEA235729
  MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup

Bootstrap\Log\20091023_100631\sql_tools_Cpu32_1.log
  MSI error description:        
  Configuration status:          Failed: see details below
  Configuration error code:      0x1447BB73
  Configuration error description: Some or all identity references could not be translated.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup

Bootstrap\Log\20091023_100631\Detail.txt

  Feature:                       Management Tools - Complete
  Status:                        Failed: see logs for details
  MSI status:                    Failed: see details below
  MSI error code:                0xEA235729
  MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup

Bootstrap\Log\20091023_100631\sql_tools_Cpu32_1.log
  MSI error description:        
  Configuration status:          Failed: see details below
  Configuration error code:      0x1447BB73
  Configuration error description: Some or all identity references could not be translated.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup

Bootstrap\Log\20091023_100631\Detail.txt

  Feature:                       Management Tools - Basic
  Status:                        Passed
  MSI status:                    Passed
  Configuration status:          Passed

  Feature:                       Client Tools SDK
  Status:                        Failed: see logs for details
  MSI status:                    Failed: see details below
  MSI error code:                0xEA235729
  MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup

Bootstrap\Log\20091023_100631\sql_tools_Cpu32_1.log
  MSI error description:        
  Configuration status:          Failed: see details below
  Configuration error code:      0x1447BB73
  Configuration error description: Some or all identity references could not be translated.
  Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091023_100631\Detail.txt

  Feature:                       Business Intelligence Development Studio
  Status:                        Passed
  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\20091023_100631\SystemConfigurationCheck_Report.htm


I've got the following failure from the Details.txt file:

2009-10-23 11:03:38 Slp: Running Action: Install_sql_tools_Cpu32_Action
2009-10-23 11:03:38 Slp: Target package: "D:\x86\setup\sql_tools.msi"
2009-10-23 11:04:10 Slp: InstallPackage: MsiInstallProduct returned the result code 1602.
2009-10-23 11:04:12 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091023_100631\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2009-10-23 11:04:13 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091023_100631\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2009-10-23 11:04:13 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091023_100631\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2009-10-23 11:04:32 Slp:
2009-10-23 11:04:35 Slp: Watson bucket for Msi based failure has been created
2009-10-23 11:04:35 Slp: No retry-able MSI return code detected.
2009-10-23 11:04:35 Slp: Checkpoint: INSTALL_SQL_TOOLS_CPU32_ACTION
2009-10-23 11:04:35 Slp: Completed Action: Install_sql_tools_Cpu32_Action, returned False
2009-10-23 11:04:35 Slp: Error: Action "Install_sql_tools_Cpu32_Action" failed during execution.

&

2009-10-23 11:10:08 Slp: Running Action: PostMsiTimingConfigAction
2009-10-23 11:10:08 Slp: Sco: Attempting to get feature configuration state for feature SQL_SNAC_SDK, version
2009-10-23 11:10:08 Slp: Sco: Attempting to get feature flag ConfigurationState for feature SQL_SNAC_SDK
2009-10-23 11:10:08 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2009-10-23 11:10:08 Slp: Sco: Attempting to open registry subkey
2009-10-23 11:10:08 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\100\ConfigurationState
2009-10-23 11:10:08 Slp: Sco: Attempting to get registry value SQL_SNAC_SDK
2009-10-23 11:10:08 Slp: Sco: Attempting to set feature configuration state FailedConfigured for feature SQL_SNAC_SDK


Any ideas on where to start / what to look for would be great.

thanks a lot

Peta

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,

I earlier had two instances on SQL Express Edition on the official laptop. Thereafter, I installed the enterprise edition of SQL Server 2014 some days ago but installed just the Engine and created an instance. But now that I am trying to add features to the same, i.e. SSAS & SSRS I find the installation stuck up at Analysis Services Configuration stage reflecting the error that the default directories for Data, Log, Temp & Backup are invalid.

Any way to resolve the error?

Furthermore, since I am currently using the laptop off-site could it be an error for not being in connection with the domain.

In addition to the same I have also found the folders in "C:\Program Files\Microsoft SQL Server\MSSQL12.<Instance>\MSSQL" requiring special permission first for access, however does allow the same upon click of Continue (Administrator) button.

Any help shall be highly obliged.

Thanks in advance.

012-12-04 10:16:11.54 spid5s      Starting u_Tables.SQL at  04 Dec 2012 10:16:11:543
2012-12-04 10:16:11.54 spid5s      This file creates all the system tables in master.
2012-12-04 10:16:11.55 spid5s      drop view spt_values ....
2012-12-04 10:16:11.58 spid5s      Creating view 'spt_values'.
2012-12-04 10:16:11.69 spid5s      drop table spt_monitor ....
2012-12-04 10:16:11.70 spid5s      Creating 'spt_monitor'.
2012-12-04 10:16:11.72 spid5s      Grant Select on spt_monitor
2012-12-04 10:16:11.73 spid5s      Insert into spt_monitor ....
2012-12-04 10:16:11.75 spid5s      Error: 25641, Severity: 16, State: 0.
2012-12-04 10:16:11.75 spid5s      For target, "package0.event_file", the parameter "filename" passed is invalid. Target parameter at index 0 is invalid
2012-12-04 10:16:11.75 spid5s      Error: 912, Severity: 21, State: 2.
2012-12-04 10:16:11.75 spid5s      Script level upgrade for database 'master' failed because upgrade step 'u_tables.sql' encountered error 25641, state 0, severity 16. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2012-12-04 10:16:11.76 spid5s      Error: 3417, Severity: 21, State: 3.
2012-12-04 10:16:11.76 spid5s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.

Any suggestions what can be done? - Im am able to start the service with net start mssql$sql2012 /t902 and when starting it without /t902, i get 3547 Error.

We have purchased a Sql Server 2012 license. How can I download the installation media? Only download I found was the evaluation copy. Should I download this, install it and update the license?

Hello,

I am trying to upgrade the SQL 2008R2 Servers to SP3 in my environment. Would like to do this silently via SCCM.

Have tried some reference links, one of the link is : 

https://slecluyse.wordpress.com/2012/06/19/sql-server-2008-r2-upgrading-to-service-pack-1-silently/

But following this give an error :

#############################################################################

#############################################################################

Please advise how could i create a silent upgrade package for SP3 to be deployed via SCCM.

Hi

i need to create a lab with this scenario: 

windows server 2008r2 + sql 2005 + sql 2008 + sql 2012

**this is for lab testing purposes**

i need this because some of our clients use this weird scenario 

is there any special install instructions to make this work? or just install the default one version after another starting from 2005?

Thanks!

Guy

This morning I requested a number of hotfixes for SQL Server 2012 SP2 CU 3 & 4, but none of the links appear to be working.  Whether I use proxy or not, I am getting Page Not Found or timeout for 134.170.185.70.  I have already tried IE 11 and Google Chrome to no avail.

Going to outside DNS Lookup websites, it appears the website is down for everybody and not just me.

Here's one of the links currently not working:

http://hotfixv4.microsoft.com/SQL%20Server%202012/sp2/SQLServer2012_SP2_CU4_3007556_11_0_5569_/11.0.5569.0/free/481684_intl_x64_zip.exe

Can anybody else confirm if there's an issue with the website?

Diane

Hello,

Is it possible to downgrade SQL 2012 Business intelligence server to Standard?

hi,

we have tried to deploy the SQL Server 2012 to our development machines with SCCM 2012 without success.

Commandline parameters or Configuration.ini in either case the installation failed without any useful errorlog.

Exists any howto which covers this scenario?

regards

genne

Login failed for user 'CS\XXXXXXXXXXX'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: <local machine>]
Clearing tempdb database.

Bits:

• Windows 2003 Server Std SP2
• SQL Server 2008 SP3

SQL Server has been running without issue.  Installed on another SS2K8 SP3 and worked fine.

Any assistance would be appreciated as this issue is causing problems for my user applications.

Thank You

Mark Covian

Hi All,

Can anyone shed some light on this? I've been searching answer on the web but with no luck. basically i got the following error in the sql error log while i was trying to intall SQL Server 2008 R2 Express.

2012-01-03 11:58:26.26 spid7s      Starting up database 'master'.
2012-01-03 11:58:26.28 spid7s      Error: 5178, Severity: 16, State: 1.
2012-01-03 11:58:26.28 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.QSRNVIVO9\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 3072. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2012-01-03 11:58:26.28 spid7s      Error: 5178, Severity: 16, State: 1.
2012-01-03 11:58:26.28 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.QSRNVIVO9\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 3072. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2012-01-03 11:58:26.30 spid7s      Error: 5178, Severity: 16, State: 1.
2012-01-03 11:58:26.30 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.QSRNVIVO9\MSSQL\Template Data\mastlog.ldf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 3072. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2012-01-03 11:58:26.30 spid7s      Error: 5178, Severity: 16, State: 1.
2012-01-03 11:58:26.30 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.QSRNVIVO9\MSSQL\Template Data\mastlog.ldf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 3072. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.

Below is some details about the machine.

Machine processor count:       2
  OS version:                    Windows Vista Home Premium
  OS service pack:               Service Pack 2
  OS region:                     United States
  OS language:                   German
  OS architecture:               x86
  Process architecture:          32 Bit
  OS clustered:                  No

C drive has 200GB+ free space and is formatted with 'Allocation unit size' = 4096 bytes

Also, chkdsk initially found a file system problem but it had been fixed by running the 'chkdsk /F' command.

Thanks,

Kevin