Hi,

Is it okay to Upgrade a sql server 2005 to 2014 directly ??

Or do I need to upgrade it to 2008 & 2012 first ??

If no, then can I upgrade sql server 2008 to 2014 directly ?? Please advice. Thanks. 

Regards, Kunjay Shah

2009-09-29 08:24:49 SQLBrowser: sRegLocation = 'SOFTWARE\Microsoft\Microsoft SQL Server', regView = 'Wow6432', sSddl = '(A;CI;KR;;;[SQLServer2005SQLBrowserUser$ITISFIM])', bOptional = 'False'.
2009-09-29 08:24:49 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2009-09-29 08:24:49 Slp: Sco: Attempting to open registry subkey
2009-09-29 08:24:49 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server
2009-09-29 08:24:49 Slp: Sco: Attempting to replace account with sid in security descriptor (A;CI;KR;;;[SQLServer2005SQLBrowserUser$ITISFIM])
2009-09-29 08:24:49 Slp: ReplaceAccountWithSidInSddl -- SDDL to be processed:  (A;CI;KR;;;[SQLServer2005SQLBrowserUser$ITISFIM])
2009-09-29 08:24:49 Slp: Sco: Account name to be translated into SID: SQLServer2005SQLBrowserUser$ITISFIM
2009-09-29 08:24:49 Slp: Sco: Attempting to get account sid for user account SQLServer2005SQLBrowserUser$ITISFIM
2009-09-29 08:24:49 Slp: Sco: Attempting to get sid for user account SQLServer2005SQLBrowserUser$ITISFIM
2009-09-29 08:24:49 Slp: Sco: GetSidForAccount normalized accountName SQLServer2005SQLBrowserUser$ITISFIM parameter to SQLServer2005SQLBrowserUser$ITISFIM
2009-09-29 08:24:49 Slp: Sco: Account name is translated into: S-1-5-21-3278988706-2344661944-1675463508-1000
2009-09-29 08:24:49 Slp: Sco: Final security descriptor:  (A;CI;KR;;;S-1-5-21-3278988706-2344661944-1675463508-1000)
2009-09-29 08:24:49 Slp: Sco: Attempting to set security descriptor (A;CI;KR;;;S-1-5-21-3278988706-2344661944-1675463508-1000)
2009-09-29 08:24:49 Slp: Sco: Attempting to normalize security descriptor (A;CI;KR;;;S-1-5-21-3278988706-2344661944-1675463508-1000)
2009-09-29 08:24:49 Slp: Sco: Adding 'D:' DACL identifier to the input security descriptor (A;CI;KR;;;S-1-5-21-3278988706-2344661944-1675463508-1000)
2009-09-29 08:24:49 Slp: Sco: Attempting to replace account with sid in security descriptor D:(A;CI;KR;;;S-1-5-21-3278988706-2344661944-1675463508-1000)
2009-09-29 08:24:49 Slp: ReplaceAccountWithSidInSddl -- SDDL to be processed:  D:(A;CI;KR;;;S-1-5-21-3278988706-2344661944-1675463508-1000)
2009-09-29 08:24:49 Slp: ReplaceAccountWithSidInSddl -- SDDL to be returned:  D:(A;CI;KR;;;S-1-5-21-3278988706-2344661944-1675463508-1000)
2009-09-29 08:24:49 Slp: Sco: Attempting to normalize security descriptor D:(A;CI;KR;;;S-1-5-21-3278988706-2344661944-1675463508-1000)
2009-09-29 08:24:49 Slp: Sco: Attempting to replace account with sid in security descriptor D:(A;CI;KR;;;S-1-5-21-3278988706-2344661944-1675463508-1000)
2009-09-29 08:24:49 Slp: ReplaceAccountWithSidInSddl -- SDDL to be processed:  D:(A;CI;KR;;;S-1-5-21-3278988706-2344661944-1675463508-1000)
2009-09-29 08:24:49 Slp: ReplaceAccountWithSidInSddl -- SDDL to be returned:  D:(A;CI;KR;;;S-1-5-21-3278988706-2344661944-1675463508-1000)
2009-09-29 08:24:49 Slp: Prompting user if they want to retry this action due to the following failure:
2009-09-29 08:24:49 Slp: ----------------------------------------
2009-09-29 08:24:49 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2009-09-29 08:24:49 Slp: Inner exceptions are being indented
2009-09-29 08:24:49 Slp:
2009-09-29 08:24:49 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
2009-09-29 08:24:49 Slp:     Message:
2009-09-29 08:24:49 Slp:         Attempted to perform an unauthorized operation.
2009-09-29 08:24:49 Slp:     Data:
2009-09-29 08:24:49 Slp:       WatsonData = Microsoft SQL Server
2009-09-29 08:24:49 Slp:       DisableRetry = true
2009-09-29 08:24:49 Slp:     Inner exception type: System.UnauthorizedAccessException
2009-09-29 08:24:49 Slp:         Message:
2009-09-29 08:24:49 Slp:                 Attempted to perform an unauthorized operation.
2009-09-29 08:24:49 Slp:         Stack:
2009-09-29 08:24:49 Slp:                 at System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
2009-09-29 08:24:49 Slp:                 at System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
2009-09-29 08:24:49 Slp:                 at Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
2009-09-29 08:24:49 Slp:                 at Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
2009-09-29 08:24:49 Slp:                 at Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
2009-09-29 08:24:49 Slp: ----------------------------------------

Hi Community,

I have an sql 2014 enterprise environment that runs multiple database that are owned by different departments and applications running under the same instance.  We had recently a number of issues where a small number of databases consume all of the available resources on the server which as a result,  negatively effect all the other databases.

I have done some reading on Resource Governor and it seems that although it is not possible to limit resource per database,  it is possible to limit by user.  The idea is to have each user limited to let say 20% or the available resource.  My main concern is the actual implementation as there are quite a large number of users which will make the setting up and the maintenance of the feature a nightmare.

Is it possible to set up a single and global rule to limit the resource allocation? 

or are there any scripts available to set up the Resource Pools by importing data from a csv.  The idea would be to export the AD users from active directory to csv and then use it to create a Resource Pool for each user.

thanks in advance

We have a customer who is running a single SBS2011 Server.
Their sharepoint database has become to big for the SQL-Express server that was setup with SBS 2011 out of the box.

Is it possible to install SQL 2014 Standard on this server so that we can then move the database into SQL STD?

Hello! I was trying to install sql server 2012 on windows 2012 server standard, but at the end of the install process I get 3 errors and I haven't been unable to complete the installation. This is the main error:

Microsoft.VC80.CRT,version="8.0.50727.42", type="win32", processorArchitecture="x86", publicKeyToken="1fc8b3b9a1e18e3b".

Please refer to Help and Support for more information.

Error code: 1935

I've been pondering a particular configuration and am wondering if anyone else has some input on it.

If you have your Data, Logs, System and TempDB all in VMDK's and those VMDK's are formatted to 64K and then reside on Clustered Storage that is formatted as 4K, which is then running through a SAN controller that is reading and writing in 2MB chunks, is there value in formatting the SQL drives as 64K?  Also, would it be better to format the Clustered Storage as 64K?  Is this a situation in which formatting the SQL drives as 64K is becoming a moot point?

Hi, I've been asked to create a new SQL server and restore an old server's DBs to the new server.

I'd like to generate a list of the DB names using powershell to distribute to their creators, in case some of these DBs are no longer needed.

Can anyone point me in the right direction? Should be a common request I'd think.

Thanks,

Scott

Hi All, 

Having an issue updating SQL Server 2012 RTM Standard  to CU3.

I'm getting the following error from the Detail log on each try:

"Error: Failed to run patch request for instance: MSSQLSERVER (exit code: -2061893565)"

I've tried rebooting the server, ensuring the user running the installer is a local admin account, ran the repair wizard on the SQL install...Nothing seems to work.

I have two identical servers, the first has gone smoothly, this is bugging me...

Any thoughts?

==========================================================================================

Server: Dell R720XD, Dual E5-2643 CPU, 64Gb RAM, Windows Server 2008 R2 Enterprise x64, SQL Server 2012 RTM CU2 x64 Installed.

Overall summary:

Hi,

I have a WIN200R2 Core server on Hyper-V and I'd like to install SQL Server 2012 on it. I use the following command:

Setup.exe /qs /Action=install /Features=SQLEngine,IS,Conn /InstanceName=MSSQLServer  /SQLSYSADMINACCOUNTS="Contoso\kim_akers" /IAcceptSQLServerLicenseTerms

(This is from book https://www.microsoft.com/learning/en-us/book.aspx?id=16016 )

I receive the following error message:

Hello good day,

i tryed to install a program called maxiXplorer. but every time during the installation the following error comes up: cannot open database requested by the login. the login failed.  

the list in the error is the very long with lost of text i cannot upload a picture at this moment :-(  you have to verify my account?



i have had contact with my service guys who give my this programm and he could not help my from where he was sitting. (600km away)

can i upload a picture some way to this text? 

Summary.txt file is copied below.

I'm attempting to install SQL Server 2012 using a remote unattended installation via PowerShell. The below result, exit code and the text I've highlighted near the bottom and recopied directly below this sentence appear to be the primary information.

The requested operation cannot be completed.
The computer must be trusted for delegation and the current user account must be configured to allow delegation.

Additional Info:

     The installation using the configurationfile works great locally (no errors).
     Upon installing via PowerShell remotely, the installation continues for approx 2minutes, process starts, then dies out.

Summary.txt File Output of Failed Installation

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068774911
  Exit facility code:            1201
  Exit error code:               1
  Exit message:                  There was an error generating the XML document.
  Start time:                    2015-05-29 15:18:50
  End time:                      2015-05-29 15:20:12
  Requested action:              Install
  Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0xE0C083E6%400xB2215DAC&EvtType=0xE0C083E6%400xB2215DAC

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for SNAC:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for SNAC_SDK:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for Writer:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
  Next step for Browser:         SQL Server Setup was canceled before completing the operation. Try the setup process again.


Machine Properties:
  Machine name:                  MBSQLCLX002
  Machine processor count:       32
  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  Configured

Package properties:
  Description:                   Microsoft SQL Server 2012 
  ProductName:                   SQL Server 2012
  Type:                          RTM
  Version:                       11
  Installation location:         C:\_installs\2012-dev-x64\x64\setup\
  Installation edition:          Developer

  Slipstream:                    True
  SP Level                       2

Product Update Status:
  User selected not to include product updates.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      false
  AGTSVCACCOUNT:                 mhs\svcsqlagent
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Manual
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             c:\_installs\2012-dev-x64\configurationfile.ini
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    false
  ENU:                           true
  ERRORREPORTING:                false
  FEATURES:                      SQLENGINE, SSMS, ADV_SSMS
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server
  INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server
  INSTALLSQLDATADIR:             D:\
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server
  INSTANCEID:                    MSSQLSERVER
  INSTANCENAME:                  MSSQLSERVER
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  NPENABLED:                     0
  PID:                           *****
  QUIET:                         true
  QUIETSIMPLE:                   false
  ROLE:                          
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  F:\MSSQL11.MSSQLSERVER\MSSQL\Backup
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 mhs\svcsqlserver
  SQLSVCPASSWORD:                *****
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           MHS\IS Database Security Group, MHS\SQLServices, MHS\IS Database Interns
  SQLTEMPDBDIR:                  D:\MSSQL11.MSSQLSERVER\MSSQL\DATA
  SQLTEMPDBLOGDIR:               E:\MSSQL11.MSSQLSERVER\MSSQL\Log
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               E:\MSSQL11.MSSQLSERVER\MSSQL\Log
  SQMREPORTING:                  false
  TCPENABLED:                    0
  UIMODE:                        Normal
  UpdateEnabled:                 false
  UpdateSource:                  Slipstream
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150529_151759\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Management Tools - Complete
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       Management Tools - Basic
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       SQL Client Connectivity
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       SQL Client Connectivity SDK
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       SQL Writer
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       SQL Browser
  Status:                        Failed: see logs for details
  Reason for failure:            Setup was canceled for the feature.
  Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150529_151759\SystemConfigurationCheck_Report.htm

Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented

Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException
    Message: 
        There was an error generating the XML document.
    HResult : 0x84b10001
        FacilityCode : 1201 (4b1)
        ErrorCode : 1 (0001)
    Data: 
      DisableWatson = true
    Stack: 
        at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.SerializeObject(String rootPath, Object objectToSerialize, Boolean saveToCache)
        at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.FlushCache(Boolean removeAllCachedObj)
        at Microsoft.SqlServer.Configuration.SetupExtension.DatastoreCacheFeatureConfigEventHandler.InConfigurationActionExecutionEventHandler(Object sender, FeatureConfigScenarioEventArgs eventArgs)
        at Microsoft.SqlServer.Chainer.Infrastructure.NotificationHandler.Invoke(Object notification, Object[] objectArray)
        at Microsoft.SqlServer.Configuration.ConfigExtension.ConfigFeatureActionListener.InConfigurationActionExecutionEventHandler(ActionKey key, TextWriter loggingStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionMetadata.NotifyInExecution(ActionKey actionRunning, TextWriter loggingStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
        at Microsoft.SqlServer.Chainer.TimingConfigAction.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
    Inner exception type: System.InvalidOperationException
        Message: 
                There was an error generating the XML document.
        HResult : 0x80131509
        Stack: 
                at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)
                at System.Xml.Serialization.XmlSerializer.Serialize(TextWriter textWriter, Object o)
                at Microsoft.SqlServer.Chainer.Infrastructure.DataStoreService.SerializeObject(String rootPath, Object objectToSerialize, Boolean saveToCache)
        Inner exception type: System.Security.Cryptography.CryptographicException
            Message: 
                        The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.

            HResult : 0x80090345
            Stack: 
                        at System.Security.Cryptography.ProtectedData.Protect(Byte[] userData, Byte[] optionalEntropy, DataProtectionScope scope)
                        at Microsoft.SqlServer.Common.SqlSecureString.WriteXml(XmlWriter writer)
                        at System.Xml.Serialization.XmlSerializationWriter.WriteSerializable(IXmlSerializable serializable, String name, String ns, Boolean isNullable, Boolean wrapped)
                        at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterAgentConfigurationPublic.Write6_AgentConfigurationPublic(String n, String ns, AgentConfigurationPublic o, Boolean isNullable, Boolean needType)
                        at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterAgentConfigurationPublic.Write7_AgentConfigurationPublic(Object o)

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?