Hi

I am currently working on a project to consolidate databases for two different application into two clusters.

Now to save more money, the company would like to consolidate both applications onto one SQL cluster with two instances running.

I am trying to work out CPU requirements and was wondering how best to go about this?

We have historical data about CPU usage per server but I am not very knowledgeable on how you would convert this.

If each server currently has different clock speed, amount of cores and threads, how do you calculate it to get a certain metric to compare against the new server?

Even if you have this metric, would it be inaccurate because other processes use CPU on each server?

Thank you

Sam

Hi,

I have a Windows7 64 bit machine.

I have installed Visual Studio 2010 professional on it. it gave an popup error message of microsoft .net framework cas policy manager has stopped working while installing, but when I clicked cancel it install the remaining tools. On the last screen it  showed error related to Microsoft SQL Server 2008 Express Service Pack 1 (x64).

I checked that Visual studio and TFS installed correctly.

My issue started when I tried to install SQl Server 2008R2. As I clicked on the SetUp.Exe, it again gave me error of microsoft .net framework cas policy manager has stopped workingand not going any further.

I tried below options to solve it, but nothing work-

a) Uninstall VS2010

b) Disable/Enable the .NET framework 3.5.1.

c) Apply a fresh copy of installation media.

d) Verify the .NET framework 3.5 with .NET setup verification tool.

Please suggest some solution for it.

--------------------------------------- Thanks, Apne Please use Marked as Answer if my post solved your problem and use Vote As Helpful if a post was useful.

I am unable to install SQL Server on my PC. At the end of installation it gives a failure in starting DataBase Engine. When i try to log in it gives a network related instance error.

I tried uninstalling from Add or Remove Program and installed again but again getting same error.

[ERROR LOG]

2015-10-24 07:59:10.94 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
    Feb 20 2014 20:04:26
    Copyright (c) Microsoft Corporation
    Express Edition (64-bit) on Windows NT 6.3 <X64> (Build 10240: )

2015-10-24 07:59:10.94 Server      UTC adjustment: 5:30
2015-10-24 07:59:10.94 Server      (c) Microsoft Corporation.
2015-10-24 07:59:10.94 Server      All rights reserved.
2015-10-24 07:59:10.94 Server      Server process ID is 1620.
2015-10-24 07:59:10.94 Server      System Manufacturer: 'LENOVO', System Model: '20255'.
2015-10-24 07:59:10.94 Server      Authentication mode is WINDOWS-ONLY.
2015-10-24 07:59:10.94 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2015-10-24 07:59:10.94 Server      The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
2015-10-24 07:59:10.94 Server      Registry startup parameters:
     -d C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\DATA\master.mdf
     -e C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\Log\ERRORLOG
     -l C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2015-10-24 07:59:10.94 Server      Command Line Startup Parameters:
     -s "SQLEXPRESS"
2015-10-24 07:59:11.31 Server      SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2015-10-24 07:59:11.31 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-10-24 07:59:11.31 Server      Detected 7383 MB of RAM. This is an informational message; no user action is required.
2015-10-24 07:59:11.31 Server      Using conventional memory in the memory manager.
2015-10-24 07:59:11.40 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2015-10-24 07:59:11.47 Server      Query Store settings initialized with enabled = 1,
2015-10-24 07:59:11.47 Server      The maximum number of dedicated administrator connections for this instance is '1'
2015-10-24 07:59:11.47 Server      This instance of SQL Server last reported using a process ID of 8028 at 10/24/2015 7:58:59 AM (local) 10/24/2015 2:28:59 AM (UTC). This is an informational message only; no user action is required.
2015-10-24 07:59:11.47 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-10-24 07:59:11.48 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2015-10-24 07:59:11.51 Server      Software Usage Metrics is disabled.
2015-10-24 07:59:11.51 spid11s     Starting up database 'master'.
2015-10-24 07:59:11.58 Server      CLR version v4.0.30319 loaded.
2015-10-24 07:59:11.62 spid11s     7 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-10-24 07:59:11.64 spid11s     0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-10-24 07:59:11.64 spid11s     Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2015-10-24 07:59:11.65 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-10-24 07:59:11.72 spid11s     SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-10-24 07:59:11.72 spid11s     SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-10-24 07:59:11.76 spid11s     SQL Trace ID 1 was started by login "sa".
2015-10-24 07:59:11.76 spid11s     Server name is 'RISHABH\SQLEXPRESS'. This is an informational message only. No user action is required.
2015-10-24 07:59:11.76 spid15s     Error: 17190, Severity: 16, State: 1.
2015-10-24 07:59:11.76 spid15s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2015-10-24 07:59:11.76 spid15s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2015-10-24 07:59:11.76 spid15s     Error: 17182, Severity: 16, State: 1.
2015-10-24 07:59:11.76 spid15s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2015-10-24 07:59:11.76 spid15s     Error: 17182, Severity: 16, State: 1.
2015-10-24 07:59:11.76 spid15s     TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2015-10-24 07:59:11.76 spid15s     Error: 17826, Severity: 18, State: 3.
2015-10-24 07:59:11.76 spid15s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2015-10-24 07:59:11.76 spid15s     Error: 17120, Severity: 16, State: 1.
2015-10-24 07:59:11.76 spid15s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Hi ALl,

I'm trying an automated install of SQL 2012 on WIndows 2012, but I keep running into this error (using a configuration.ini file generated by running through setup and grabbing it just before I clicked 'OK')

Contents of summary log:

Overall summary:
   Final result:                  Failed: see details below
   Exit code (Decimal):           -2068578304
   Exit facility code:            1204
   Exit error code:               0
   Exit message:                  The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
   Start time:                    2015-01-09 10:19:12
   End time:                      2015-01-09 10:20:07
   Requested action:              Install

Setup completed with required actions for features.
 Troubleshooting information for those features:
   Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Replication:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for FullText:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DQ:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for AS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   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 IS:              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 DREPLAY_CTLR:    SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DREPLAY_CLT:     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 Writer:          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.
   Next step for Browser:         SQL Server Setup was canceled before completing the operation. Try the setup process again.

 Machine Properties:
   Machine name:                  IDCSQLTST11
   Machine processor count:       2
   OS version:                    Future Windows Version
   OS service pack:              
   OS region:                     United States
   OS language:                   English (United States)
   OS architecture:               x64
   Process architecture:          64 Bit
   OS clustered:                  No

Product features discovered:
   Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered

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

Product Update Status:
   None discovered.

User Input Settings:
   ACTION:                        Install
   ADDCURRENTUSERASSQLADMIN:      false
   AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
   AGTSVCPASSWORD:                <empty>
   AGTSVCSTARTUPTYPE:             Automatic
   ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
   ASCOLLATION:                   Latin1_General_CI_AS
   ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
   ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
   ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
   ASPROVIDERMSOLAP:              1
   ASSERVERMODE:                  MULTIDIMENSIONAL
   ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
   ASSVCPASSWORD:                 <empty>
   ASSVCSTARTUPTYPE:              Manual
   ASSYSADMINACCOUNTS:            DOMAINAA\SQLADMINS
   ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
   BROWSERSVCSTARTUPTYPE:         Disabled
   CLTCTLRNAME:                  
   CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
   CLTSTARTUPTYPE:                Manual
   CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
   CLTSVCPASSWORD:                <empty>
   CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir
   COMMFABRICENCRYPTION:          0
   COMMFABRICNETWORKLEVEL:        0
   COMMFABRICPORT:                0
   CONFIGURATIONFILE:             E:\SQL_Server_2012_StandardEdition\ConfigurationFile.ini
   CTLRSTARTUPTYPE:               Manual
   CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
   CTLRSVCPASSWORD:               <empty>
   CTLRUSERS:                     DOMAINAA\user12345
   ENABLERANU:                    false
   ENU:                           true
   ERRORREPORTING:                false
   FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK
   FILESTREAMLEVEL:               0
   FILESTREAMSHARENAME:           <empty>
   FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
   FTSVCPASSWORD:                 <empty>
   HELP:                          false
   INDICATEPROGRESS:              false
   INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server
   INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server
   INSTALLSQLDATADIR:             <empty>
   INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server
   INSTANCEID:                    MSSQLSERVER
   INSTANCENAME:                  MSSQLSERVER
   ISSVCACCOUNT:                  NT Service\MsDtsServer110
   ISSVCPASSWORD:                 <empty>
   ISSVCSTARTUPTYPE:              Automatic
   MATRIXCMBRICKCOMMPORT:         0
   MATRIXCMSERVERNAME:            <empty>
   MATRIXNAME:                    <empty>
   NPENABLED:                     0
   PID:                           *****
   QUIET:                         true
   QUIETSIMPLE:                   false
   ROLE:                         
   RSINSTALLMODE:                 DefaultNativeMode
   RSSHPINSTALLMODE:              SharePointFilesOnlyMode
   RSSVCACCOUNT:                  NT Service\ReportServer
   RSSVCPASSWORD:                 <empty>
   RSSVCSTARTUPTYPE:              Manual
   SAPWD:                         <empty>
   SECURITYMODE:                  SQL
   SQLBACKUPDIR:                  <empty>
   SQLCOLLATION:                  Latin1_General_CI_AS
   SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
   SQLSVCPASSWORD:                <empty>
   SQLSVCSTARTUPTYPE:             Automatic
   SQLSYSADMINACCOUNTS:           DOMAINAA\SQLADMINS
   SQLTEMPDBDIR:                  F:\TempDB
   SQLTEMPDBLOGDIR:               <empty>
   SQLUSERDBDIR:                  E:\SQLData
   SQLUSERDBLOGDIR:               D:\SQLLog
   SQMREPORTING:                  false
   TCPENABLED:                    1
   UIMODE:                        Normal
   UpdateEnabled:                 true
   UpdateSource:                  MU
   X86:                           false

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

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

  Feature:                       SQL Server Replication
   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:                       Full-Text and Semantic Extractions for Search
   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 Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

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

  Feature:                       Reporting Services - Native
   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 - 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:                       Integration Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

  Feature:                       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:                       Distributed Replay Controller
   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:                       Distributed Replay 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:                       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:                       SQL Client Connectivity
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.

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

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

  Feature:                       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.

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

Rules with failures:

Global rules:

Scenario specific rules:

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

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

Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
     Message:
         The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
     HResult : 0x84b40000
         FacilityCode : 1204 (4b4)
         ErrorCode : 0 (0000)
     Data:
       SQL.Setup.FailureCategory = InputSettingValidationFailure
       DisableWatson = true
     Stack:
         at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
         at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
     Inner exception type: Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException
         Message:
                 The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
         HResult : 0x87d00006
                 FacilityCode : 2000 (7d0)
                 ErrorCode : 6 (0006)
         Data:
           DirectoryPath = C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
           SettingName = CLTRESULTDIR
           WatsonData =  Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException@6

Hi,

Whenever we attempt to send mail through SQL database mail in SQL 2005, the server logs register following error:

Error: Exception Type:

Microsoft.SqlServer.Management.SqlIMail.Server.Common.BaseException

Message: Mail configuration information could not be read from the

Exception Type: System.IndexOutOfRangeException  

Later I have found some website refers to update the service pack and apply the latest cumulative update. The Service pack 4 was already applied in the server, hence I tried to apply the Cumulative update -3 alone as mentioned in the article 

https://support.microsoft.com/en-us/kb/2507769

But the CU has failed to update with the following error: The product instance SQL Tools has had update 5069 installed. You do not need to install this update. An update equal to or greater than 5320 should be downloaded.

Then I have found a GDR hot fix (KB2716429) which is a security update of SQL server 2005 has blocked the CU-3 update.

How to proceed from this moment?

Thanks

I am in the process of upgrading SQL Server databases and SSIS packages from 2008 to 2012; one of the packages uses a script component and refers to Microsoft.AnalysisServices.

This works in 2008 but on the 2012 server I am getting an error: "Exception has been
thrown by the target of an invocation" and if I open the package and script on the server it appears that it cannot resolve the reference.

"Warning 1 Namespace or type specified in the Imports 'Microsoft.AnalysisServices' doesn't contain any public member or cannot be found. Make sure the namespace or the type is defined and contains at least one public member. Make sure the imported element name doesn't use any aliases"

version 11.0 of the dll is in the C:\windows\assembly GAC, but I understand it may need to be in C:\Windows\Microsoft.NET\assembly\GAC_MSIL for 2012 - any advice on how I can get it there, please?

Thanks

R. Jones

Hi, 

I've recently upgraded to windows 10 and have installed SQL server 2012 Enterprise Edition but I cannot see the any of the apps that should show up in my Apps list. Any ideas?

Thanks in advance.  I have tried several things and others have experienced similar issues, but people either do not post their fix or the issue is never resolved.

We have 2 separate SQL installs running on Windows 2003 Enterprise Edition Service Pack 2 OS x86.  SQL is currently at 9.0.3175.  The installs of service pack 3 and 4 vboth fail.  The original issue reported the follwing in the summary.txt.

Product Installation Status

Product                   : SQL Server Database Services 2005 (MSSQLSERVER)

Product Version (Previous): 3073

Product Version (Final)   :

Status                    : Failure

Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB954606_sqlrun_sql.msp.log

Error Number              : 1635

Error Description         : Unable to install Windows Installer MSP file

To resolve this issue, the following artickle was done, which has moved me past this error and to a new error: http://blogs.msdn.com/b/sqlserverfaq/archive/2009/01/30/part-1-sql-server-2005-patch-fails-to-install-with-an-error-unable-to-install-windows-installer-msp-file.aspx?PageIndex=1#comments

This approach appear to even be the fix for a post here at Technet, but it does not work for me.

The summary.txt is now reading the following error:

Product                   : Database Services (MSSQLSERVER)
Product Version (Previous): 3175
Product Version (Final)   :
Status                    : Failure
Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB955706_sqlrun_sql.msp.log
Error Number              : 2902
Error Description         : MSP Error: 2902  The installer has encountered an unexpected error. The error code is 2902. Operation ixfAssemblyCopy called out of sequence.

Searches for this error are very broad and nothing specific to SQL.  Here is a copy of the error from the sqlrun_sql.msp.log.

MSI (s) (24:B8) [13:18:44:538]: Executing op: AssemblyCopy(SourceName=Smo.dll|Microsoft.SqlServer.Smo.dll,SourceCabKey=Microsoft.SqlServer.Smo.DC8FC6AD_FB4A_4A81_8366_0ED2594F1AEA,DestName=Microsoft.SqlServer.Smo.dll,Attributes=20480,FileSize=1603424,PerTick=32768,,VerifyMedia=1,,,,,ComponentId={653612B2-2738-4F92-936D-65DE042BD1BB},IsManifest=1,,,AssemblyMode=0,)
MSI (s) (24:B8) [13:18:44:538]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:538]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:554]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:554]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:554]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:554]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:554]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:554]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:554]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:554]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:554]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:570]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:570]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:570]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:570]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:570]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:570]: Transforming table Error.

MSI (s) (24:B8) [13:18:44:570]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (24:B8) [13:18:44:570]: Product: Microsoft SQL Server 2005 -- Error 2902. The installer has encountered an unexpected error. The error code is 2902. Operation ixfAssemblyCopy called out of sequence.

Error 2902. The installer has encountered an unexpected error. The error code is 2902. Operation ixfAssemblyCopy called out of sequence.

Has anyone ever seen this before?  I inherites these SQL Servers and would also like to know what could have caused the issue, but obviously I want to install the latest SP for SQL first.  

Any help or assistance would be greatly appreciated.  Thanks. 

We have an issue on our SQL Server 2005 which can be addressed by KB937745. The explanatory article (https://support.microsoft.com/en-us/kb/937745) says that we need to install this update on top of Service Pack 2. However, we have Service Pack 4 installed. My question is: can we install KB937745 update on top of Service Pack 4 without any harm to SQL Server?

SQL Server version: 9.00.5069.00, SP4,  Developer Edition

Windows version: Windows Server 2003, Standard Edition, SP2

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

Please refer to my other post: Team Foundation Server 2013 Update 4 - Completely crashing

The issue resolved itself, but basically TFS appeared to have triggered a state where SQL Server was unusable to the point an Administrator couldn't even restart the SQL services, and no one could connect to any of the databases.  We had to restart the server, and connectivity was available for a short while before the issue reoccurred.  All event logs related to TFS point to the fact it couldn't connect to the database, I couldn't find any indication as to why SQL Server went into that state.

Can you please help me troubleshoot what actually caused the issue (via my SQL Logs or Windows logs) so I can prevent it from happening again?  What would you like for me to share?

Thanks, Jibba

Missing SQL Server service local groups

Hello all , 
I am having issues with upgrade from SQL Server 2008 R2 to SQL2014 with error "no mapping between account names and security IDs was done" and the reason for the error is the following SQL server local groups that were created during the setup (SQL2008 R2) are not found on the servers local groups. 
Can anybody help to identify the right fix for this issue ? 
SQLServerMSSQLUser$<servername>$MSSQLSERVER 
SQLServerSQLAgentUser$<servername>$MSSQLSERVER 
SQLServerReportServerUser$<servername>$MSRS10_50.MSSQLSERVER 
SQLServerFDHostUser$<servername>$MSSQLSERVER 

Thanks 
Naz 
DBA

Thanks. Here is the log:

Hello,

I'm trying to install SQL Server 2008 R2 Enterprise (downloaded from MSDN subscription).  Everything seems to go smooth until I get to "Server Configuration".  I'm using aDomain User account I created called "SQLServerAgentAcc" for all SQL services.  When I click Use the same account for all SQL Server Services and put in the account name and password I get an error.  The message says:

"The credentials you provided for the SQL Server Agent is invalid"

"The credentials you provided for the Analysis Services is invalid"

"The specified credentials for the SQL Service Services are invalid"

I know for a fact the password and account name is correct.  I've even logged in with the Domain Account to make sure it actually works.  For some reason I keep getting this error.  Can someone please help me out?

System/network Setup:

Server 1

Domain Controller

Service accounts (including SQLServiceAgentAcc)

Server 2

SQL server 2008

Server 3

SharePoint 2010 (not installed yet)Each server has 2tb of hard drive space, 8gb memory, quad core processors.