SQL 2014 Backup Speed Issues

May 3, 2016, 10:46 pm

≫ Next: ##Patch Level & Hotfix Related Isuue##

≪ Previous: SQL 2014 MSA service account change

Hi All,

I have come across a very strange issue when backing up a database that's running on under SQL 2014. The backup runs at a small fraction of the speed of the drives capacity; to the point that the backups times out.

I can copy files on the same drive at normal speeds and even whilst the backup is executing without issues.

My question is this: Does SQL 2014 have any settings that can affect the read/write throughput of operations such as backups?

Your help will be appreciated.

Cheers,

Paul

↧

##Patch Level & Hotfix Related Isuue##

May 3, 2016, 8:07 am

≫ Next: Sql Serrver 2014 Developer installation by PS DSC

≪ Previous: SQL 2014 Backup Speed Issues

Hi,

I am having SQL 2008 R2 SP3 infra.

On top of that I am having the MS15-058 Patch/CU installed.

The Situation I am Facing That:

Then I removed the Patch/CU MS15-058.

Now In control Panel MS15-058 hotfix is not listing Out(Which Should not be as I already Removed It)

But In configuration Manger Or Registry it is still Pointing to MS15-058 Version.

NOTE: I restarted the machine Also.

Can any one Help me Out on this?

Then It will Be very Helpful.

Thanks In advance

Regards

Suman

↧

Sql Serrver 2014 Developer installation by PS DSC

April 25, 2016, 3:45 am

≫ Next: SQL Server 2012 SP1 Upgrade Path Question

≪ Previous: ##Patch Level & Hotfix Related Isuue##

Hi All,

I am installing Sql Server 2014 Developer edition by powershell dsc and getting below log file with error. I have given path of the sql setup.exe and ConfigurationFile.ini file in my code.

Script InstallSQLServer

{

GetScript

{

$sqlInstances=gwmiwin32_service-computerNameNodeName| ? { $_.Name-match"mssqlserver*"-and$_.PathName-match"sqlservr.exe"} | %{$_.Caption }

$res=$sqlInstances-ne$null-and$sqlInstances-gt0

$vals=@{Installed=$res; InstanceCount =$sqlInstances.count}

$vals

}

SetScript

{

Write-Verbose"Drive letter for iso is: $setupDriveLetter"

# run the installer using the ini file

$cmd="C:\Installs\SQL2014Developer64bit\setup.exe /ConfigurationFile=C:\Installs\SQL2014Developer64bit\ConfigurationFile.ini /SQLSVCPASSWORD=syntel@123 /AGTSVCPASSWORD=syntel@123 /SAPWD=syntel@123"

Write-Verbose"Running SQL Install - check %programfiles%\Microsoft SQL Server\120\Setup Bootstrap\Log\ for logs..."

Invoke-Expression$cmd|Write-Verbose

}

TestScript

{

$sqlInstances=gwmiwin32_service-computerNameNodeName| ? {$_.Name-match"mssqlserver*"-and$_.PathName-match"sqlservr.exe"} | %{$_.Caption }

$res=$sqlInstances-ne$null-and$sqlInstances-gt0

if($res)

{

Write-Verbose"SQL Server is already installed"

}

else

{

Write-Verbose"SQL Server is not installed"

}

$res

}

Error part of the log is given below.

Please suggest, how can I fix it.

(01) 2016-04-25 02:24:15 Slp: Error: Action "Microsoft.SqlServer.Configuration.UIExtension.StartAction" threw an exception during execution.
(01) 2016-04-25 02:24:25 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Thread was being aborted. ---> System.Threading.ThreadAbortException: Thread was being aborted.
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.ShowActiveObjectTemplate.Show(String moniker)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Start(String moniker, Predicate`1 pageFilter)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.StartAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    --- End of inner exception stack trace ---
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
(01) 2016-04-25 02:24:25 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Thread was being aborted. ---> System.Threading.ThreadAbortException: Thread was being aborted.
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.ShowActiveObjectTemplate.Show(String moniker)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Start(String moniker, Predicate`1 pageFilter)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.StartAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    --- End of inner exception stack trace ---
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
(01) 2016-04-25 02:24:25 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Thread was being aborted. ---> System.Threading.ThreadAbortException: Thread was being aborted.
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.ShowActiveObjectTemplate.Show(String moniker)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Start(String moniker, Predicate`1 pageFilter)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.StartAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    --- End of inner exception stack trace ---
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
(01) 2016-04-25 02:24:25 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Thread was being aborted. ---> System.Threading.ThreadAbortException: Thread was being aborted.
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.ShowActiveObjectTemplate.Show(String moniker)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Start(String moniker, Predicate`1 pageFilter)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.UIExtension.StartAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    --- End of inner exception stack trace ---
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
(01) 2016-04-25 02:24:25 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
(01) 2016-04-25 02:25:11 Slp: Received request to add the following file to Watson reporting: C:\windows\TEMP\tmp72C9.tmp
(07) 2016-04-25 02:25:11 Slp: Search for updates completed as 'Succeeded', number of updates found: 0
(01) 2016-04-25 02:25:11 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2016-04-25 02:25:11 Slp: Inner exceptions are being indented
(01) 2016-04-25 02:25:11 Slp:
(01) 2016-04-25 02:25:11 Slp: Exception type: System.InvalidOperationException
(01) 2016-04-25 02:25:11 Slp:     Message:
(01) 2016-04-25 02:25:11 Slp:         Showing a modal dialog box or form when the application is not running in UserInteractive mode is not a valid operation. Specify the ServiceNotification or DefaultDesktopOnly style to display a notification from a service application.
(06) 2016-04-25 02:25:11 Slp:
(06) 2016-04-25 02:25:11 Slp: Microsoft Update Details:
(06) 2016-04-25 02:25:11 Slp:   Category ID searched on Microsoft Update:          892C0584-8B03-428f-9A74-224FCD6887C0
(06) 2016-04-25 02:25:11 Slp:   Major version of the Windows Update Agent:         8
(06) 2016-04-25 02:25:11 Slp:   Minor version of the Windows Update Agent:         0
(06) 2016-04-25 02:25:11 Slp:   Version of Wuapi.dll:                              7.9.9600.18235
(06) 2016-04-25 02:25:11 Slp:
(06) 2016-04-25 02:25:11 Slp: Completed Action: SearchUpdatesAction, returned True
(01) 2016-04-25 02:25:11 Slp:     HResult : 0x80131509
(01) 2016-04-25 02:25:12 Slp:     Stack:
(01) 2016-04-25 02:25:12 Slp:         at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
(01) 2016-04-25 02:25:12 Slp:         at Microsoft.SqlServer.Configuration.UIExtension.ShowWizard.ShowUserInterface()
(01) 2016-04-25 02:25:12 Slp:         at Microsoft.SqlServer.Configuration.UIExtension.ShowActiveObjectTemplate.ThreadStart(Object obj)
(01) 2016-04-25 02:25:27 Slp: SQM Service: Sqm does not have active session.

Thanks

Uttam

Thanks UK

↧

SQL Server 2012 SP1 Upgrade Path Question

May 4, 2016, 8:00 am

≫ Next: SSMS on windows Server 2012R2, Connect To Server dialog has a long lag of about 3 seconds per character typed

≪ Previous: Sql Serrver 2014 Developer installation by PS DSC

Hello,

I have a question about how to proceed with the SQL Server 2012 Service Pack 1 upgrade path. I would like to upgrade to SQL Server 2012 Service Pack 3. I found this link which lists all of the latest updates. https://technet.microsoft.com/en-us/sqlserver/ff803383.aspx

So should I start with SQL Server Service Pack 1 and update to CU16? Then install Service Pack 2 and CU11? Then Service 3 pack? Can someone please advise. I would appreciate any help. I am a newbie here so please excuse my ignorance.

Reezie

↧

SSMS on windows Server 2012R2, Connect To Server dialog has a long lag of about 3 seconds per character typed

December 16, 2015, 7:05 am

≫ Next: New CALs to my SQL 2008 server

≪ Previous: SQL Server 2012 SP1 Upgrade Path Question

In a new installation of SQL Server 2008R2 Standard in a windows Server2012R2, we have mixed-mode authentication enabled. Using Windows authentication, we are able to authenticate using SQL Management Studio as expected. Using SQL authentication, SQL Management Studio will not let me authenticate. Two strange symptoms:

Typing in the password field on the SQL Management Studio Connect To Server dialogue has a long lag of about 3 seconds per character typed
Authentication fails, even though the password is entered correctly

Using SQL Authentication and using another SSMS that is installed in a different server we are able to connect to the instance.

Any Idea in what to do in this cases?

↧

New CALs to my SQL 2008 server

May 4, 2016, 8:00 am

≫ Next: remote Named Pipes not functional 2014 & 2016 RC3 now

≪ Previous: SSMS on windows Server 2012R2, Connect To Server dialog has a long lag of about 3 seconds per character typed

I have a "SQL Server 2008" with 20 CALs. Now I am installing a new ERP and need a total of 40 user licenses. But now,May/2016, there are not "SQL 2008 user CAL" to buy.

Can I buy "SQL 2014 user CAL" and use to access my "SQL Server 2008"?

↧

remote Named Pipes not functional 2014 & 2016 RC3 now

May 4, 2016, 9:41 am

≫ Next: SQL SErver 2012 Setup fails for wrong install log path

≪ Previous: New CALs to my SQL 2008 server

Hi Folks

remote Named Pipes in a side-by-side 2014 Express & 2016 RC3 installation (on Windows 2012 Server) is not functional (programmatically).

Details:

13.0.1400.361 RC3 Developer Edition (64-bit) - 2016

12.0.4449.0 SP1 Express Edition (64-bit) - 2014

(I've done several dozen of installs over the last 20 years, so I'd like to think I have a handle on this, but can't figure this one out.)

Named Pipes was functional (remotely for 2014), but after the install of 2016, this protocol is not functional remotely (no error message, just times out now for both 2014 and 2016). Named Pipes works locally (on the Windows 2012 Server for both 2014 and 2016).

My firewall settings:

Write-host ========= SQL Server Ports ===================

Write-host Enabling SQLServer default instance port 1433

New-NetFirewallRule -DisplayName "Allow SQLServer inbound TCP Port 1433" –Direction inbound –LocalPort 1433 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow SQLServer outbound TCP Port 1433" –Direction outbound –LocalPort 1433 -Protocol TCP -Action Allow

Write-host Enabling Dedicated Admin Connection port 1434
New-NetFirewallRule -DisplayName "Allow SQL Admin inbound TCP Port 1434" -Direction inbound –LocalPort 1434 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow SQL Admin outbound TCP Port 1434" -Direction outbound –LocalPort 1434 -Protocol TCP -Action Allow

Write-host Enabling conventional SQL Server Service Broker port 4022
New-NetFirewallRule -DisplayName "Allow SQL Server Service Broker inbound TCP Port 4022" -Direction inbound –LocalPort 4022 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow SQL Server Service Broker outbound TCP Port 4022" -Direction outbound –LocalPort 4022 -Protocol TCP -Action Allow

Write-host Enabling Transact-SQL Debugger/RPC port 135
New-NetFirewallRule -DisplayName "Allow Transact-SQL Debugger/RPC inbound TCP Port 135" -Direction inbound –LocalPort 135 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow Transact-SQL Debugger/RPC outbound TCP Port 135" -Direction outbound –LocalPort 135 -Protocol TCP -Action Allow

Write-host Enabling Named Pipes port 445
#SQLServer 2016
New-NetFirewallRule -DisplayName "Allow SQLServer 2016 inbound Named Pipes Port 445" –Direction inbound -Program "c:\Program Files\Microsoft SQL Server\MSSQL13.INTTIMEKEEPING\MSSQL\Binn\sqlservr.exe" –LocalPort 445 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow SQLServer 2016 outbound Named Pipes Port 445" –Direction outbound -Program "c:\Program Files\Microsoft SQL Server\MSSQL13.INTTIMEKEEPING\MSSQL\Binn\sqlservr.exe" –LocalPort 445 -Protocol TCP -Action Allow
#SQLServer 2014
New-NetFirewallRule -DisplayName "Allow SQLServer 2014 inbound Named Pipes Port 445" –Direction inbound -Program "c:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Binn\sqlservr.exe" –LocalPort 445 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow SQLServer 2014 outbound Named Pipes Port 445" –Direction outbound -Program "c:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Binn\sqlservr.exe" –LocalPort 445 -Protocol TCP -Action Allow

Write-host ========= Analysis Services Ports ==============

Write-host Enabling SSAS Default Instance port 2383
New-NetFirewallRule -DisplayName "Allow SSAS Default Instance inbound TCP Port 2383" -Direction inbound –LocalPort 2383 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow SSAS Default Instance outbound TCP Port 2383" -Direction outbound –LocalPort 2383 -Protocol TCP -Action Allow

Write-host Enabling SQL Server Browser Service port 2382
New-NetFirewallRule -DisplayName "Allow SQL Server Browser Service inbound TCP Port 2382" -Direction inbound –LocalPort 2382 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow SQL Server Browser Service outbound TCP Port 2382" -Direction outbound –LocalPort 2382 -Protocol TCP -Action Allow

Write-host ========= Misc Applications ==============
Write-host Enabling HTTP port 80
New-NetFirewallRule -DisplayName "Allow HTTP inbound TCP Port 80" -Direction inbound –LocalPort 80 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow HTTP outbound TCP Port 80" -Direction outbound –LocalPort 80 -Protocol TCP -Action Allow

Write-host Enabling SSL port 443
New-NetFirewallRule -DisplayName "Allow SSL inbound TCP Port 443" -Direction inbound –LocalPort 443 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Allow SSL outbound TCP Port 443" -Direction outbound –LocalPort 443 -Protocol TCP -Action Allow

Write-host Enabling port for SQL Server Browser Service's 'Browse
New-NetFirewallRule -DisplayName "Allow SQL Browser inbound UDP Port 1434" -Direction inbound –LocalPort 1434 -Protocol UDP -Action Allow
New-NetFirewallRule -DisplayName "Allow SQL Browser outbound UDP Port 1434" -Direction outbound –LocalPort 1434 -Protocol UDP -Action Allow
#==end of script==

I've tried all of the developer and admin logins directly from SSMS w/o issue.

I've tried every support url that seemed relevant (like http://stackoverflow.com/questions/9945409/how-do-i-fix-the-error-named-pipes-provider-error-40-could-not-open-a-connec)

Are there any "triage utilities" like Oracle's TNS Ping (for SQL Server 2014 and 2016)?

I'm not seeing anything in the Windows Event Log on the Windows Server 2012.

Thanks

Rob

Rob K

↧

SQL SErver 2012 Setup fails for wrong install log path

May 4, 2016, 9:15 am

≫ Next: issue with applying sp3 to MS SQL 2008 R2

≪ Previous: remote Named Pipes not functional 2014 & 2016 RC3 now

Hi,

my default directory for "Program Files" is on "D:\", when I install SQLServer 2012 SE on my Windows 10 it fails saying can't find the installer log file on "'C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20160504_164014' infact this path is on D:\ I can't find anyway to make it change on correct path: any idea?

↧

issue with applying sp3 to MS SQL 2008 R2

May 4, 2016, 10:00 am

≫ Next: separate servers Dev/Prod...

≪ Previous: SQL SErver 2012 Setup fails for wrong install log path

I am working on migrating one sql server to a cloud server. I installed MS sql on the server but have not restored the sql database from the backup yet. Can I installed sp3 before restoring the database? When I tried to install sp3, it kept telling me that the instance ID is missing. Does it mean the database is not there which caused instance ID missing?

Please advise!

↧

separate servers Dev/Prod...

April 25, 2016, 5:01 am

≫ Next: [SQL] SQL 2014 Backup Speed Issues

≪ Previous: issue with applying sp3 to MS SQL 2008 R2

Hello,
The present architecture is that there is one sql server 2008 R2 (ServerA ) which has the DEV database as well as the Prod database.
There are SSIS packages that run every 30 minutes or so...

1-
Do you think it is a good idea to have one server i.e. ServerD for Dev, another one i.e. ServerU for UAT and leave the current one (ServerA) as is but remove the Dev database.

2-
Should the SSIS/ETL be done on the same server as the production i.e. ServerA or should that be a separate server too? i.e. ServerS?

3-
There is also SSAS. should they be on another server?

Thanks

↧

[SQL] SQL 2014 Backup Speed Issues

May 3, 2016, 10:46 pm

≫ Next: Upgrade SQL from 2008 to 2014

≪ Previous: separate servers Dev/Prod...

Hi All,

I can copy files on the same drive at normal speeds and even whilst the backup is executing without issues.

My question is this: Does SQL 2014 have any settings that can affect the read/write throughput of operations such as backups?

Your help will be appreciated.

Cheers,

Paul

↧

Upgrade SQL from 2008 to 2014

May 4, 2016, 3:42 pm

≫ Next: Complete remove/uninstall sql server 2014 by command

≪ Previous: [SQL] SQL 2014 Backup Speed Issues

I am trying to upgrade from SQL 2008 to SQL 2014 so that I can use my crm program. The crm people tried to remove SQL 2008 for me but it would not uninstall. Anyone have any idea how to get it to uninstall so I can upgrade?

Thank you in advance for any assistance.

Leslie

↧

Complete remove/uninstall sql server 2014 by command

May 4, 2016, 2:16 am

≫ Next: Need MSSQL Server 2012 STD Edition Server CAL details

≪ Previous: Upgrade SQL from 2008 to 2014

Hi All,

I want to uninstall/remove sql server 2014 completely. I tried the below command for this but some of the below sql component did not uninstall perperly.

Microsoft SQL Server 2014(64-bit)
Microsoft SQL Server 2014 RS Add-in for SharePoint
Microsoft SQL Server 2014 Setup(English)

Command:

ExeFullPath>Setup.exe /Action=Uninstall /FEATURES=SQL,AS,RS,IS,Tools /INSTANCENAME=MSSQLSERVER /QUIET

Someone please help me to modify the above command to uninstall above three component as well.

Thanks UK

↧

Need MSSQL Server 2012 STD Edition Server CAL details

May 5, 2016, 4:12 am

≫ Next: SQL Services - Built in account or different account

≪ Previous: Complete remove/uninstall sql server 2014 by command

Please let me know during which scenario MSSQL Server 2012 STD Edition-Server/CAL software should be installed or used.

Also is there any way to identify whether installed SQL Server 2012 STD Edition 64-bit is Per Core or Server/CAL

Thanks and Regards,

Nikhil Desai

↧

SQL Services - Built in account or different account

March 9, 2016, 1:03 am

≫ Next: SQL server 2014

≪ Previous: Need MSSQL Server 2012 STD Edition Server CAL details

Please let me know that as per best practices under which service account should sql services (database engine, agent, integration,reporting, analysis etc) should run

1 Local System

2. Local Service

3. Network Service

4. Local Administrator Windows account

5. Domain admin account

Regards,

Nikhil P Desai

↧

SQL server 2014

May 5, 2016, 10:02 am

≫ Next: SQL Server 2012 installer missing 767e6.msi file

≪ Previous: SQL Services - Built in account or different account

How do I activate SQL 2014 trial version?

↧

SQL Server 2012 installer missing 767e6.msi file

May 5, 2016, 10:11 am

≫ Next: Delete all SQL files?

≪ Previous: SQL server 2014

I did try running Setup.exe /q /ACTION=Repair to fix the install errors but it didn't work...

Here is the output from the summary.txt

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

Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2147024894
Exit facility code: 7
Exit error code: 2
Exit message: C:\Windows\Installer\767e6.msi
Start time: 2016-05-05 09:45:52
End time: 2016-05-05 09:46:36
Requested action: Repair
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0x7B2055F0%400xB7EAF00B&EvtType=0x7B2055F0%400xB7EAF00B

Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS_SHP: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for RS_SHPWFE: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for DQC: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Conn: 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 SDK: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BC: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BIDS: 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 BOL: SQL Server Setup was canceled before completing the operation. Try the setup process again.

Machine Properties:
Machine name: OCHIN008
Machine processor count: 4
OS version: Windows 7
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 2008 R2 Client Tools Connectivity    1033 10.51.2500.0 No
SQL Server 2008 R2 Client Tools SDK    1033 10.51.2500.0 No
SQL Server 2012 Management Tools - Basic    1033 Standard Edition 11.1.3128.0 No
SQL Server 2012 Management Tools - Complete    1033 Standard Edition 11.1.3128.0 No
SQL Server 2012 Client Tools Connectivity    1033 Standard Edition 11.1.3128.0 No
SQL Server 2012 Client Tools Backwards Compatibility 1033 Standard Edition 11.1.3128.0 No
SQL Server 2012 Client Tools SDK    1033 Standard Edition 11.1.3128.0 No
SQL Server 2012 Reporting Services - SharePoint 11.1.3128.0 No

Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: J:\upgrades\Microsoft\SQL2012_SP1\x64\setup\
Installation edition:

User Input Settings:
ACTION: Repair
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASCONFIGDIR: Config
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20160505_094524\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
ENU: true
FAILOVERCLUSTERGROUP: <empty>
FAILOVERCLUSTERNETWORKNAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTANCENAME: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
QUIET: true
QUIETSIMPLE: false
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: <empty>
UIMODE: Normal
X86: false

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

Detailed results:
Feature: Reporting Services - SharePoint
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: Reporting Services Add-in for SharePoint Products
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: Data Quality Client
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: Client Tools 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: 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: Client Tools 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: Client Tools Backwards Compatibility
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 Server Data Tools
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: Setup Support Files
Status: Passed

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: Documentation Components
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:

There are no scenario-specific rules.

Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20160505_094524\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: System.IO.FileNotFoundException
Message:
C:\Windows\Installer\767e6.msi
HResult : 0x80070002
Data:
DisableWatson = true
Stack:
at Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetSummaryInformationStringProperty(ServiceContainer context, String pathToMsi, SummaryInformationStreamPropertySet propertyId)
at Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetInstalledSummaryInformationStringProperty(ServiceContainer context, String productCode, SummaryInformationStreamPropertySet propertyId)
at Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia, InstallAction pkgAction)
at Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)

↧

Delete all SQL files?

May 6, 2016, 5:54 am

≫ Next: SQL Server 2012 - Analysis, Intergration, Reporting Services are disabled

≪ Previous: SQL Server 2012 installer missing 767e6.msi file

Hi, I've istalled "Visual Studio" in 2015 and "SQL 2012" in 2016. I just uninstalled and removed all SQL files dated from 2016. (ok ..my bad, not the smartest thing to do). Problem now is that I can install SQL 2014 but I am not able to create a password.... I do not seem to get to go through all steps in the installation. I till have SQL files from when I installed VS in 2015. Should these be deleted as well or will this affcect VS or will the new instlllation take care of this?

Any tips or ideas what to do?

↧

SQL Server 2012 - Analysis, Intergration, Reporting Services are disabled

November 28, 2012, 11:26 pm

≫ Next: Connect with analysis services in sql server management studio 2012

≪ Previous: Delete all SQL files?

I have installed SQL Server 2012 and when I try to connect to Analysis Services is disabled. The same goes for Integration Services and Reporting Services. The only 2 options for connection are Database Engine and Azure Storage.

I already checked the SQL Configuration Manager and all services are running. I also turn off the firewall just in case it was blocking the services.

Any ideas what might be wrong?

Thank you!

↧

Connect with analysis services in sql server management studio 2012

May 6, 2016, 8:04 am

≫ Next: Installing SQL Server 2012 Web Edition Service Pack 2

≪ Previous: SQL Server 2012 - Analysis, Intergration, Reporting Services are disabled

i want to Connect with analysis services in sql server management studio 2012 but when i go to object explorer and select connect

i only have data base engine and analysis services is grey i cant pick it . i opened the SQL SERVER CONFIGURATION MANAGER i didn't find the sql server analysis services to make it run ???

so when i open sql server data tools 2012 to create may cube it doesn't deployed ,

help me please .

↧