Quantcast
Channel: SQL Server Setup & Upgrade forum
Viewing all 8133 articles
Browse latest View live
↧

AddCurrentUserAsSQLAdmin can only be specified for SQL Server 2008 R2 Express error during installation of SQL 2008 R2 Express

October 16, 2012, 1:22 am
$
0
0

I'm trying to install SQL Express 2008 R2 from the command line using the following command:
setup.exe /Action=Install /Features=SQL /QS /InstanceName=[instancename] /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" /AddCurrentUserAsSQLAdmin /SECURITYMODE=SQL /SAPWD=[strongpassword] /TCPENABLED=1 /IACCEPTSQLSERVERLICENSETERMS

Been working fine on all systems, until now where I'm getting the error "AddCurrentUserAsSQLAdmin can only be specified for SQL Server 2008 R2 Express."

Have tried to "google" and "bing" this error, however not been able to find a suitable solution.

Hope someone here can be of assistance.

Below full details from the "detail.txt" file:

2012-10-12 13:13:31 SQLEngine: --InputValidator: Checking AddCurrentUserAsSQLAdmin setting.
2012-10-12 13:13:31 Slp: Hosting object: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPublic failed validation
2012-10-12 13:13:31 Slp: Validation for setting 'ADDUSERASADMIN' failed. Error message: AddCurrentUserAsSQLAdmin can only be specified for SQL Server 2008 R2 Express.
2012-10-12 13:13:31 Slp: Error: Action "Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction" threw an exception during execution.
2012-10-12 13:13:31 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: AddCurrentUserAsSQLAdmin can only be specified for SQL Server 2008 R2 Express. ---> Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException: AddCurrentUserAsSQLAdmin can only be specified for SQL Server 2008 R2 Express. ---> Microsoft.SqlServer.Configuration.SqlEngine.ValidationException: AddCurrentUserAsSQLAdmin can only be specified for SQL Server 2008 R2 Express.
2012-10-12 13:13:31 Slp:    --- End of inner exception stack trace ---
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2012-10-12 13:13:31 Slp:    --- End of inner exception stack trace ---
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
2012-10-12 13:13:31 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
2012-10-12 13:13:31 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: AddCurrentUserAsSQLAdmin can only be specified for SQL Server 2008 R2 Express. ---> Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException: AddCurrentUserAsSQLAdmin can only be specified for SQL Server 2008 R2 Express. ---> Microsoft.SqlServer.Configuration.SqlEngine.ValidationException: AddCurrentUserAsSQLAdmin can only be specified for SQL Server 2008 R2 Express.
2012-10-12 13:13:31 Slp:    --- End of inner exception stack trace ---
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2012-10-12 13:13:31 Slp:    --- End of inner exception stack trace ---
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
2012-10-12 13:13:31 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
2012-10-12 13:13:31 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: AddCurrentUserAsSQLAdmin can only be specified for SQL Server 2008 R2 Express. ---> Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException: AddCurrentUserAsSQLAdmin can only be specified for SQL Server 2008 R2 Express. ---> Microsoft.SqlServer.Configuration.SqlEngine.ValidationException: AddCurrentUserAsSQLAdmin can only be specified for SQL Server 2008 R2 Express.
2012-10-12 13:13:31 Slp:    --- End of inner exception stack trace ---
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2012-10-12 13:13:31 Slp:    --- End of inner exception stack trace ---
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2012-10-12 13:13:31 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2012-10-12 13:13:32 Slp: Received request to add the following file to Watson reporting: C:\Documents and Settings\Master\Local Settings\Temp\tmp45F.tmp
2012-10-12 13:13:32 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2012-10-12 13:13:32 Slp: Inner exceptions are being indented
2012-10-12 13:13:32 Slp: 
2012-10-12 13:13:32 Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
2012-10-12 13:13:32 Slp:     Message: 
2012-10-12 13:13:32 Slp:         AddCurrentUserAsSQLAdmin can only be specified for SQL Server 2008 R2 Express.
2012-10-12 13:13:32 Slp:     Data: 
2012-10-12 13:13:32 Slp:       SQL.Setup.FailureCategory = InputSettingValidationFailure
2012-10-12 13:13:32 Slp:       DisableWatson = true
2012-10-12 13:13:32 Slp:     Stack: 
2012-10-12 13:13:32 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
2012-10-12 13:13:32 Slp:         at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
2012-10-12 13:13:32 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2012-10-12 13:13:32 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2012-10-12 13:13:32 Slp:     Inner exception type: Microsoft.SqlServer.Configuration.SqlEngine.ValidationException
2012-10-12 13:13:32 Slp:         Message: 
2012-10-12 13:13:32 Slp:                 AddCurrentUserAsSQLAdmin can only be specified for SQL Server 2008 R2 Express.
2012-10-12 13:13:32 Slp: 
2012-10-12 13:13:32 Slp: ----------------------------------------------------------------------
2012-10-12 13:13:32 Slp: 
2012-10-12 13:13:32 Slp: Error result: -2068578304
2012-10-12 13:13:32 Slp: Result facility code: 1204
2012-10-12 13:13:32 Slp: Result error code: 0

↧
Search

SQL Server 2012 on Windows Server 2012 with no GUI

October 16, 2012, 5:59 am
$
0
0
Is it possible to install and run SQL server 2012 on Windows Server 2012 with no GUI (not sure if this is the same as Core or not)?

Lee

↧
↧

Failed Security Update for SQL Server 2005 Service Pack 4 (KB2716429) WINXP

October 16, 2012, 5:21 am
$
0
0

Hi.  I am running Windows XP with the latest WSUS.  This update is failing to install on my machine.  I tried to manually download the update and install, but if fails as well. 

Event ID: 20
Category:  Installation
Descriptions:  INstallation Failure:  Windows failed to install the following update with error 0x80070643: Security Update for SQL Server 2005 Service Pack 4 (KB2716429)

Any help resolving this would be greatly appreciated.  I've searched the forums and google.  I did find a link for a failed install of SQL Server 2005 Service Pack 3 on the forums:

http://social.msdn.microsoft.com/Forums/eu/sqlsetupandupgrade/thread/7808954f-c80c-4a76-aa20-1b32b44779ab

The last post suggest some registry changes.  Wasn't sure if this might work for this or not.

Thanks!

↧

Can't install KB2716440. Installer cannot find my SQL Server instance

October 16, 2012, 7:03 am
$
0
0

I have SQL Server 2008 R2 SP1 installed (I'm at 10.50.2500). Trying to apply the KB2716440-patch.

However, when I get to step three, "Select Features" I can't select anything. If i click "Select All" and try to proceed I get the following error:

[Error Message]
There are no SQL Server instances or shared features that can be updated on this computer.
================================================================================

There is definitely a SQL Server instance on the server and as far as I can tell, the patch has not been applied.

↧

Problems after installing SP2 on SQL Server 2008 R2

October 16, 2012, 7:26 am
$
0
0

Hi, can anyone tell me the problems and issues you had after installing service pack 2 on SQL Server 2008 R2.

Thanks with regards.

Ersin

↧
↧

SQL Agent group not created by installer

October 16, 2012, 6:02 am
$
0
0

I am installing a SQL Server 2008R2 cluster on Windows 2008R2.

After installation, the Agent won't start. In the SQLAGENT.LOG I see:
Startup error: Unable to initialize error reporting system (reason: The EventLog service has not been started)

The group SQLServerSQLAgentUser$ComputerName$MSSQLSERVER was not created. Maybe that causes the error?
I do see the service account running the Agent was added to the required security policies.

When I add the service account to the local admin group, the Agent starts fine.

↧

Object reference not set to an instance of an object. error getting while getting installing sql server 2008 r2 on windows server 2008 r2 sp1

October 16, 2012, 9:42 am
$
0
0

Hi Team,

I am getting error while adding second instance to the same node while 1st instance installed without any error.

Object reference not set to an instance of an object. error getting while getting installing sql server 2008 r2 on windows server 2008 r2 sp1.

Please share if i am missing anything..

Santosh Singh

↧

SQL Server 2008 R2 SP1 Fails on Rule "Not clustered or the cluster service is up and online"

October 16, 2012, 10:23 am
$
0
0

We have a consolidated stand-alone server running multiple instances on SQL Server 2008 R2.  Some instances are RTM and some are SP1.  I created a new instance and wanted to upgrade it to SP1 but when I executed the installer the check screen failed on rule "Not clustered or the cluster service is up and online."

When I check out c:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20121015_130216\Detail.txt the pertinent section is below.

2012-10-15 13:02:59 Slp: Initializing rule      : Not clustered or the cluster service is up and online.
2012-10-15 13:02:59 Slp: Rule applied features  : ALL
2012-10-15 13:02:59 Slp: Rule is will be executed  : True
2012-10-15 13:02:59 Slp: Init rule target object: Microsoft.SqlServer.Configuration.Cluster.Rules.ClusterServiceFacet
2012-10-15 13:09:02 Slp: Unexpected error 
2012-10-15 13:09:02 Slp:    at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
   at Microsoft.SqlServer.Configuration.Cluster.Rules.WMIInterop.Service.ServiceCollection.ServiceEnumerator.MoveNext()
   at Microsoft.SqlServer.Configuration.Cluster.Rules.ClusterServiceFacet.Microsoft.SqlServer.Configuration.RulesEngineExtension.IRuleInitialize.Init(String ruleId)
   at Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.Execute(Boolean stopOnFailure)

2012-10-15 13:09:02 Slp: Rule initialization failed - hence the rule result is assigned as Failed

I tried searching a bit and found some discussion of WMI however when I check the authorities for WMI everything comes back OK.  Plus, like I said, we have instances on the server at SP1 already.

Any ideas are appreciated :-)

- Dave
↧
Search

SQL Server 2008 install error: "Some or all identity references could not be translated"

October 22, 2009, 9:58 pm
$
0
0

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

↧
↧

Fail to install SSRS 2012

October 16, 2012, 1:53 pm
$
0
0

I am trying to add SSRS to an existing installation.

This is sql server 2012 + sp1 CTP on top of win server 2008R2 sp1.

The setup fails with error I cannot understand.

Here is the end of the summary log:

Detailed results:
  Feature:                       Reporting Services - Native
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Reporting Services
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20121016_215724\sql_rs_Cpu64_1.log
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2845.0&EvtType=sql_rs.msi%400x162A16FE%400x1639

Rules with failures:

Global rules:

Scenario specific rules:

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

------

The indicated report shows all is OK

The Details.txt log shows:

(01) 2012-10-16 21:31:50 Slp: 
(01) 2012-10-16 21:31:50 Slp: Error result: -2068052377
(01) 2012-10-16 21:31:50 Slp: Result facility code: 1212
(01) 2012-10-16 21:31:50 Slp: Result error code: 1639
(01) 2012-10-16 21:31:51 Slp: WER: Application level consent value 'False' was mapped to consent status 'WerConsentDenied'
(01) 2012-10-16 21:31:51 Slp: WER: Result of the submission:: 'WerDisabled'
(01) 2012-10-16 21:31:51 Slp: WER: Submitted 1 of 1 failures to the Watson data repository
(01) 2012-10-16 21:31:51 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2012-10-16 21:31:51 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\110
(01) 2012-10-16 21:31:51 Slp: Sco: Attempting to get registry value CustomerFeedback

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


here are the installed components I copy from the summary log:

Machine Properties:

  Machine name:                  SHUKON
  Machine processor count:       8
  OS version:                    Windows Server 2008 R2
  OS service pack:               Service Pack 1
  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 
  SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Database Engine Services                 1033                 Standard Edition     11.1.2845.0     No        
  SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            SQL Server Replication                   1033                 Standard Edition     11.1.2845.0     No        
  SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033                 Standard Edition     11.1.2845.0     No        
  SQL Server 2012                                                          Management Tools - Basic                 1033                 Standard Edition     11.1.2845.0     No        
  SQL Server 2012                                                          Management Tools - Complete              1033                 Standard Edition     11.1.2845.0     No        
  SQL Server 2012                                                          Client Tools Connectivity                1033                 Standard Edition     11.1.2845.0     No        
  SQL Server 2012                                                          Client Tools Backwards Compatibility     1033                 Standard Edition     11.1.2845.0     No        
  SQL Server 2012                                                          Integration Services                     1033                 Standard Edition     11.1.2845.0     No        

Package properties:
  Description:                   Microsoft SQL Server 2012 
  ProductName:                   SQL Server 2012
  Type:                          RTM
  Version:                       11
  SPLevel:                       0
  Installation location:         C:\Install\SQL2012\x64\setup\
  Installation edition:          Standard 


Thanks

-Yaniv

Yaniv Etrogi
site | blog | linked in | mail
Please click the Mark as Answer button if a post solves your problem! or Vote As Helpful

↧

Unable to upgrade from SQL 2012 evaluation version to enterprise edition after evaluation expired

July 25, 2012, 8:31 am
$
0
0

Hello,

My SQL 2012 evaluation version expired, I found out after server rebooted. I then download EE version from MSDN subscription (no key required). I followed this procedure http://technet.microsoft.com/en-us/library/cc707783.aspx to do the upgrade. Everything was passed, the key was provided automatically. The upgrade was completed successfully. But it is still evaluation version saying the evaluation is expired after the upgrade.

I also tried to follow a KB to configurationstate of commonfiles from 1 to 3, same result.

I have tried this on multiple machines, all same results. They are all on AlwaysOn cluster.

=============================Install log======================

Overall summary:
  Final result:                  Passed
  Exit code (Decimal):           0
  Start time:                    2012-07-25 08:00:20
  End time:                      2012-07-25 08:08:56
  Requested action:              EditionUpgrade

Cluster properties:
  Machine name: MVA-S56-VM-2
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered
  SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER1750        Database Engine Services                 1033                 Enterprise Evaluation Edition 11.0.1750.32    No       
  SQL Server 2012      .......n Edition 11.0.1750.32    No       
  SQL Server 2012                                                          Integration Services                     1033                 Enterprise Evaluation Edition 11.0.1750.32    No       

Machine Properties:
  Machine name:                  MVA-S56-VM-2
  Machine processor count:       1
  OS version:                    Windows Server 2008 R2
  OS service pack:               Service Pack 1
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  Yes

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered
  SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER1750        Database Engine Services                 1033                 Enterprise Evaluation Edition 11.0.1750.32    No       
  SQL Server 2012      MSSQLSERVER          MSSQL11.MSSQLSERVER1750        SQL Server Replication                   Enterprise Evaluation Edition 11.0.1750.32    No       

Package properties:
  Description:                   Microsoft SQL Server 2012
  ProductName:                   SQL Server 2012
  Type:                          RTM
  Version:                       11
  SPLevel:                       0
  Installation location:         \\10.60.141.152\e$\x64\setup\
  Installation edition:          Enterprise

User Input Settings:
  ACTION:                        EditionUpgrade
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120725_075649\ConfigurationFile.ini
  ENU:                           true
  FEATURES:                      BOL, SNAC_SDK, MDS, SNAC, BROWSER, WRITER
  HELP:                          false
  INDICATEPROGRESS:              false
  INSTANCENAME:                  MSSQLSERVER
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  UIMODE:                        Normal
  X86:                           false

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

Detailed results:
  Feature:                       Master Data Services
  Status:                        Passed

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       SQL Writer
  Status:                        Passed

Rules with failures:

Global rules:

There are no scenario-specific rules.

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

Any idea what the problem is? I don't want to uninstall then reinstall, as that would require to setup whole AlwaysOn again?

Thanks!

↧

SQL 2012 - Add Feature fails, tries to do Install

October 17, 2012, 9:29 am
$
0
0

Hello, few weeks ago I installed SQL 2012 complete, EXCEPT for Full Text Search.  Now I wanted to install TFS 2012, and have it use this SQL instance.  However TFS install fails, complains that Full Text Search is not installed on the SQL instance.

Fair enough.  Try to add the feature using the Install application..  It starts off ok, but as it progresses it seems to forget that it is doing just a feature addition, like it asks me for all the logon information, etc. It asks me for what components/features to install (and does not list that any are already installed). Then it complains that Master db already exists, etc.

Seems like it is attempting to do a full install?  Does "feature addition" work - anyone have success trying this on SQL 2012?

I guess only option at moment is full uninstall/reinstall (ugh)?

↧

unable to connect error when trying to connect to SS2012 on server from SSMS2012 on PC

October 17, 2012, 9:11 am
$
0
0

Newly installed named instance of SQL Server 2012 with Mixed Authentication on Windows Server 2008 R2 x64:

                   SQL2012 is the instance name and it is listening on port 1080. 

I restarted the service after changing the port #.

SSMS2012 running on a desktop Windows 7 x64 machine discovers the new database server but cannot connect, either as Server6 or as Server6\SQL2012:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

Per this article http://msdn.microsoft.com/en-us/library/ms177440.aspx  I checked the SQL Server Network Configuration. The TCP/IP protocol was enabled; however, in the IP2 section, the IP address is the server's address on our LAN but the TCP Port was blank and dynamic ports was 0.  I deleted the 0 and changed the TCP Port to 1080, saved, and restarted the services; but then SSMS no longer even discovers the server!  So that change made things worse.

What haven't I done correctly?


↧
↧

sqlserver.exe memory usage after installation

October 17, 2012, 11:45 am
$
0
0
Hi, during installation of SQL Server 2008 R2 Standard on a machine running Windows 2008 R2 Enterprise, specifically where the installer says SqlEngineConfigAction_install_startup_Cpu64, the RAM usage jumps from 2.65 GB to 25.9 GB.  After installation, and even after a full server reboot, sqlserver.exe stays at 25.9 GB used.  The server is a brand-new 48 core opteron with 32 GB memory, and is sitting at 82% physical memory used without any databases installed.  The machine we're migrating from is a virtual server with SQL 2008 R2 Std on Win 2008 R2 Ent and it did not display this behaviour.  Is there something I can change?
↧

Upgrade

October 17, 2012, 9:09 am
$
0
0

Hi,

How to upgrade SQL Server 2008 (10.0.5500) to (10.0.5512). Any hotfix, patch?

Thanks

↧
Search

About SQL 2008 R2 Install

October 17, 2012, 8:53 am
$
0
0

Hello

I have Problem in my SQL Install

i am installed it 3 days ago and then uninstall again

but now i cant install it

it setup support files

then close

↧

Installiong on a server core edition

October 17, 2012, 3:51 pm
$
0
0
Is there a way to run the SQL setup on one machine with a switch that allows me to just to build the installation file so that I can then do the install on a core server machine supplying the config file?

Lee

↧
↧

SQL Server Core Editions

October 17, 2012, 3:48 pm
$
0
0

On my volume license page I see two different flavors of SQL server for Standard and Datacenter editions

SQL Server Standard 2012

SQL Server Standard 2012 Core

etc.

What's the difference? ... Licensing Model?

Lee

↧

SQL Server Express Setup failure

October 17, 2012, 10:51 am
$
0
0

I am trying to install SQL Server 2008 R2 Express on a Windows XP Home 32bit edition machine.

I have already installed SQL Server 2005 in this machine.

I keep getting the following error:

TITLE: SQL Server Setup failure.
------------------------------

SQL Server Setup has encountered the following error:

The name 'ldlᓃ-b.dlldlᓃ' contains characters that are not valid for a Culture or Region.
Parameter name: cultureName.

I downloaded and tried SQL Server 2012 Express but still the same error.

Has anyone have idea on what could be wrong?


↧

not able to integrate sql server reporting service to sharepoint 2010 to create Powerview reports

October 18, 2012, 3:24 am
$
0
0

Hi,

i am trying to configure report server 2012  in sharepoint enterprise 2010 in the Central Administration -->General ApplicationSetting-->

SQL Server Reporting Services (2008 and 2008 R2)  under this tab its not allowing me to configure Report server 2012 and if i'll configure here report server 2008 or 2008 r2 it gets configured. But when  i am trying to create the PowerView Report its throwing an error:

This functionality is not supported on the version of the Report Server specified in Central Administration.

 Can anybody suggest me how to configure Report server 2012 so that i can  create Powerview reports.



↧
Viewing all 8133 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>