SQL Server Denali is required to install integration services

Hi,
I've just installed a named instance of SQL Server 2014. I'm trying to create the SSISDB catalog and getting the following error.
"SQL Server Denali is required to install integration services"
I have 3 instances on my machine.
1. Default instance SQL Server 2012 SP1
2. Named instance SQL Server 2008 SP1
3. Named instance SQL Server 2014 SP1
The SSISDB creation works on the 2012 instance.

Microsoft SQL Server 2014 Setup Discovery Report
Product
Instance
Instance ID
Feature
Language
Edition
Version
Clustered
Configured
Microsoft SQL Server 2014
SQL2014
MSSQL12.SQL2014
Database Engine Services
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
SQL2014
MSSQL12.SQL2014
SQL Server Replication
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
SQL2014
MSAS12.SQL2014
Analysis Services
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
Management Tools - Basic
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
Management Tools - Complete
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
Client Tools Connectivity
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
Client Tools Backwards Compatibility
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
Client Tools SDK
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
Integration Services
1033
Developer Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2014
LocalDB
1033
Express Edition
12.0.2000.8
No
Yes
Microsoft SQL Server 2012
MSSQLSERVER
MSSQL11.MSSQLSERVER
Database Engine Services
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
MSSQLSERVER
MSSQL11.MSSQLSERVER
SQL Server Replication
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
MSSQLSERVER
MSAS11.MSSQLSERVER
Analysis Services
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
Management Tools - Basic
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
Management Tools - Complete
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
Client Tools Connectivity
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
Client Tools Backwards Compatibility
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
Client Tools SDK
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
BIDS
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
Integration Services
1033
Developer Edition
11.0.2100.60
No
Yes
Microsoft SQL Server 2012
LocalDB
1033
Express Edition
11.1.3000.0
No
Yes
Microsoft SQL Server 2008
SQL2008
MSSQL10.SQL2008
Database Engine Services
1033
Enterprise Edition
10.0.1600.22
No
Yes
Microsoft SQL Server 2008
SQL2008
MSSQL10.SQL2008
SQL Server Replication
1033
Enterprise Edition
10.0.1600.22
No
Yes

Similar Messages

  • SSIS: To run a SSIS package outside of SQL Server Data Tools you must install SCR - DP1 Connections of Integration Services or higher

    We have SSIS installed on a machine that is not part of a cluster but it is accessible by the cluster.
    Our job we have running on the cluster is failing with the following error:
    Error: 2014-01-31 09:14:37.52     Code: 0xC000F427     Source: SCR - DP1 Connections  
    Description: To run a SSIS package outside of SQL Server Data Tools you must install SCR - DP1 Connections of Integration Services or higher.  End Error
    Any advice or information on how to resolve this would be great.
    Many Thanks.

    Hi NessaBella,
    Integration Services service is not a cluster-aware service, and does not support failover from one cluster node to another. Therefore, in a clustered environment, Integration Services should be installed and started as a stand-alone service on each node
    in the cluster.
    Based on the error message, it seems that SSIS is not installed on the cluster node on which the job was running. Although SSIS is installed on a machine that is not part of the cluster and can be accessed by each cluster node, the SSIS service installed
    on a remote server cannot be used a cluster node. So, please install the shared feature SQL Server Integration Services on each cluster node. Besides, if certain packages need to run in 32-bit mode in certain jobs and the SQL Server installed is 64-bit version,
    you also need to install BIDS/SSDT on the cluster node to get the 32-bit runtime of SSIS.
    References:
    Integration Services (SSIS) in a Cluster
    Loading and Running a Remote Package Programmatically
    Regards,
    Mike Yin
    TechNet Community Support

  • Error "To run a SSIS package outside of SQL Server data tools you must install task name used in package of Integration service or highter.

    Hello Team,
    I am trying to execute a SSIS package from web page. When i try to do that i am getting following error.
    "To run a SSIS package outside of SQL Server data tools you must install <task name used in package> of Integration service or highter."
    In my machine Integration Services are installed and its service is also in running state.
    Please help me on this.
    Thanks,
    Ramesh
    Thanks, Ramesh Arige

    The SSIS package developed using SSIS 2008 Server R2 and Integrations Services 10.0 is exists in my machine. Is this wrong configuration, please help me on this.
    I am using the below code copied from CodeProject
    Thank you so much for responding.
    Ramesh
    Thanks, Ramesh Arige
    Which way are you using from the provided blog? Using 1) C# Code or 2) C# and Stored Procedure?
    Cheers,
    Vaibhav Chaudhari
    MCP, MCTS, MCSA (SQL Server 2012)

  • Unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1

    I am unable to get SQL Server Agent to run after installing SQL 2012 Standard with SP1. Log message is as follows:
    Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
    Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\xplog70.dll'.
    Error: 17750, Severity: 16, State: 0.
    Could not load the DLL xplog70.dll, or one of the DLLs it references. Reason: (null).

    Hi JFriedley,
    According to your error message, there might three reasons for this issue.
    xplog70.dll is corrupt, you need to check if you have any SQL Server running on same file version and same production
     edition. If xplog70.dll is corrupt, you can copy it from the new server where agent is running fine to your problematic server.
    Native client not installed properly. If you try applying any latest Service Pack or Cumulative Update then check if the SQL Server Agent can start, if that also doesn’t solve issue then try to reinstalling SQL Server Native client from SQL Server setup
    files.
    There is a similar issue about error 17750, you can review the following article.
    http://blogs.lostincreativity.com/sqldba/sqlserver-error-17750-could-not-load-the-dll-xpstar90-dll/
    Regards,
    Sofiya Li
    If you have any feedback on our support, please click here.
    Sofiya Li
    TechNet Community Support

  • SQL Server 2005 SP2 Failed to install the update

    I just purchased a Dell PC and during the start up one of the updates that tried to install was SQL Server 2005. I tried turning off my Anti Virus program and the install failed again. Everything I've read about this problem is too technical for me. Is
    there a simple way to fix this problem?

    I just purchased a Dell PC and during the start up one of the updates that tried to install was SQL Server 2005. I tried turning off my Anti Virus program and the install failed again. Everything I've read about this problem is too technical for
    me. Is there a simple way to fix this problem?
    I am curious which Windows update installs SQL server 2005. Were you installing any program which installed SQL 2005 as part of it ?
    Anyways you can share log file as asked by Alberto. Please also give more details whether SQL server was installed by you or machine or whether it was SQL 2005 update.
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

  • I installed visual studio 2010 in my windows 8.1 system.during the installation sql server 2008 r2 features were installed.so which version of sql server i need to install(2008 or 2008 r2)?

    hi,
    I installed visual studio 2010 in my windows 8.1 system.during the installation sql server 2008 r2 features were installed.so which version of sql server i need to install(2008 or 2008 r2)?
    regards,
    harsha.

    My guess is SQL Server 2008 R2.
    Check the following KB article for details:
    http://support.microsoft.com/kb/2681562
    Kalman Toth Database & OLAP Architect
    SELECT Video Tutorials 4 Hours
    New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

  • Installing SSMS 2012 after SQL Server 2008 R2 Express was installed (without tools)

    Hi everybody,
    This is a question in another forum I am frequent. Someone installed SQL Server Express 2008 R2 and he used the wrong exe, so he installed it without tools. Now he wants to install SSMS.
    It looks like SSMS 2012 wants to have SQL Server 2012 Express installed first.
    Can someone please confirm if it's possible to install just SSMS 2012 after SQL Server 2008 R2 Express was already installed and if possible, guide through the installation steps?
    Thanks a lot in advance.
    For every expert, there is an equal and opposite expert. - Becker's Law
    My blog
    My TechNet articles

    Hi Naomi,
    Agree with Shanky.
    I have tested the scenario you described. Everything works well, I successfully install SQL Server Management studio 2012 after SQL Server 2008 R2 Express (without tools) was already installed.
    Please note that we don’t need to install SQL Server 2012 Express first when installing SSMS 2012. For detailed installation steps of SQL Server 2008 R2 Express and SSMS 2012, you can review below blogs.
    How to Install SQL Server 2008 R2 (Express Edition)
    SQL Server Management Studio – A step-by-step installation guide
    In addition, we can use SSMS 2012 to manage SQL Server Express 2005 /2008 /2008 R2, the tool is backward compatible.
    Thanks,
    Lydia Zhang
    If you have any feedback on our support, please click
    here.
    Lydia Zhang
    TechNet Community Support

  • Sap4.7 and sql server 2000 on windows2003:when install di ,error:MDB-05039

    sap4.7 and sql server 2000 on windows2003:
    when install database instance ,there is a error,at change  tempdb
      MDB-05039:Unable to stop server dev ,
    please help !!!!

    Every time you start SQL Server it also creates a new tempdb. When you change the layout (physical structure, size) you have to restart SQL Server in order for these changes to take effect.
    It seems that the installation routine has changed the layout (it does that according to your input!) and is now trying to stop and restart SQL Server. When you run into this error, have you tried to stop and restart SQL Server manually? After that choose the Retry option of the installation routine. Just a guess...
    Do you have some more log information?
    Sven

  • How many sql server express instances i can install maximum in single system

    Hello Team,
    I want to install multiple sql express instances in single machine. My question is that how many instances of sql server express editions i can install in single machine ? 
    Thanks,
    Udaya Kumar
    udaya kumar

    For practical reasons as much as you like you probably would not exceed in any case 10 instances because after that resource crunch would start but any how you can read Max specification for SQL Server
    More accurate answer is "50 instances on a stand-alone server for all SQL Server editions."
    https://msdn.microsoft.com/en-us/library/ms143432.aspx
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • SQL Server cannot authenticate using Kerberos because the Service Principal Name (SPN) is missing, misplaced, or duplicated

    We are getting this below alert message, while using SCOM 2012 R2.  Anybody have any idea how to resolve this on the SQL box ?
    Thx...
    SQL Server cannot authenticate using Kerberos because the Service Principal Name (SPN) is missing, misplaced, or duplicated.
    Service Account: NT Service\MSSQL$SQLEXPRESS
    Missing SPNs:
    Misplaced SPNs: MSSQLSvc/mysqlbox.com:SQLEXPRESS - sqldbadmin
    Duplicate SPNs:

    To Fix this issue, You can check below links
    http://support.microsoft.com/kb/2443457/EN-US
    http://www.scomgod.com/?p=155
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"Mai Ali | My blog:
    Technical | Twitter:
    Mai Ali

  • Hyper-V windows 7 embedded standard VHD install integration services not working

    My existing VM (windows 7 embedded standard) is not letting me install integration services. Has anyone been able to do it, is there somewhere I can find this "integration disk" that will install this on this windows 7 edition? The current integration
    disk does not support windows embedded standard. 

    You are correct, there is no support for Embedded.
    The drivers would need to be incorporated into the image, just like any other drivers.  However, you cannot get driver installation files like you can with 3rd parties.
    In this case, the drivers are essentially becoming part of the kernel itself.
    I don't know about embedded 8 or 8.1 either.
    The better place to ask would be in the Windows Embedded forums on MSDN.
    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

  • Unable to install Integration Services for SQL Server 2005

    I'm not able to select "Integration Services Project" in Business Intelligence Development Studio (it is not in the templates below):
    When installing, it says that it is already installed. Why can't I see it in the project templates?

    Microsoft Visual Studio 2005
    Version 8.0.50727.867  (vsvista.050727-8600)
    Microsoft .NET Framework
    Version 2.0.50727 SP2
    Installed Edition: Professional
    Microsoft Visual Basic 2005   77626-009-0000007-41773
    Microsoft Visual Basic 2005
    Microsoft Visual C# 2005   77626-009-0000007-41773
    Microsoft Visual C# 2005
    Microsoft Visual C++ 2005   77626-009-0000007-41773
    Microsoft Visual C++ 2005
    Microsoft Visual J# 2005   77626-009-0000007-41773
    Microsoft Visual J# 2005
    Microsoft Visual Studio 2005 Tools for Applications   77626-009-0000007-41773
    Microsoft Visual Studio 2005 Tools for Applications
    Microsoft Visual Web Developer 2005   77626-009-0000007-41773
    Microsoft Visual Web Developer 2005
    Microsoft Web Application Projects 2005   77626-009-0000007-41773
    Microsoft Web Application Projects 2005
    Version 8.0.50727.867
    AnkhSVN - Subversion Support for Visual Studio   2.5.12440.9
    AnkhSVN - Subversion Support for Visual Studio 2.5.12440.9 
     * Ankh.Package 2.5.12440.9
     * Subversion 1.8.8 via SharpSvn 1.8008.3178.19
    SharpSvn is linked to: Apr 1.5.0, Apr-util 1.5.3, Cyrus Sasl 2.1.25, eXpat 2.0.1, OpenSSL 1.0.1g 7 Apr 2014, serf 1.3.4, SQLite 3.7.17, Subversion 1.8.8-SharpSvn-1.8.8, ZLib 1.2.8
    SharpSvn is optionally linked to: Berkeley DB 4.4.20, SharpPlink 1.8008.3178.19
    Hotfix for Microsoft Visual Studio 2005 Professional Edition - ENU (KB2938803)   
    Microsoft Visual Studio 2005 Professional Edition - ENU Service Pack 1 (KB926601)   
    Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB2251481)   
    Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB2538218)   
    Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB2548826)   
    Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB971090)   
    Security Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB973673)   
    SQL Server Reporting Services   
    Microsoft SQL Server Reporting Services Designers 
    Version 9.00.2047.00
    Update for Microsoft Visual Studio 2005 Professional Edition - ENU (KB932232)   

  • Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"

    I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
    Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
    I tried all the things below;
    * I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
    * I'm deleting all the keys related with Sql Server from Regedit.
    * Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
    Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
    * My firewall is already closed. And i have not any antivirus software.
    * I gave the permission for port 1433 on firewall.
    Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.

    Here's the ERRORLOG file which i found under the folder;
    Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
    2014-09-27 03:39:40.15 Server      Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) 
    Apr  2 2010 15:48:46 
    Copyright (c) Microsoft Corporation
    Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
    2014-09-27 03:39:40.15 Server      (c) Microsoft Corporation.
    2014-09-27 03:39:40.15 Server      All rights reserved.
    2014-09-27 03:39:40.15 Server      Server process ID is 5768.
    2014-09-27 03:39:40.15 Server      System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
    2014-09-27 03:39:40.15 Server      Authentication mode is MIXED.
    2014-09-27 03:39:40.15 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-09-27 03:39:40.15 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-09-27 03:39:40.15 Server      Command Line Startup Parameters:
    -m SqlSetup
    -f
    -Q
    -q Turkish_CI_AS
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    2014-09-27 03:39:40.18 Server      Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically.  After
    the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
    2014-09-27 03:39:40.18 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.18 Server      Detected 4 CPUs. This is an informational message; no user action is required.
    2014-09-27 03:39:40.31 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-09-27 03:39:40.32 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.
    2014-09-27 03:39:40.43 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.
    2014-09-27 03:39:40.45 Server      Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
    is required.
    2014-09-27 03:39:40.45 spid7s      Warning ******************
    2014-09-27 03:39:40.45 spid7s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-09-27 03:39:40.46 spid7s      Starting up database 'master'.
    2014-09-27 03:39:40.52 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.58 spid7s      SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
    2014-09-27 03:39:40.59 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:40.59 spid7s      Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
    2014-09-27 03:39:40.59 spid7s      Starting up database 'mssqlsystemresource'.
    2014-09-27 03:39:40.61 spid7s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
    2014-09-27 03:39:40.94 spid7s      Password policy update was successful.
    2014-09-27 03:39:40.94 spid8s      Starting up database 'model'.
    2014-09-27 03:39:40.95 spid7s      Server name is 'CAGATAY'. This is an informational message only. No user action is required.
    2014-09-27 03:39:41.21 spid8s      Clearing tempdb database.
    2014-09-27 03:39:41.21 spid10s     A new instance of the full-text filter daemon host process has been successfully started.
    2014-09-27 03:39:41.24 Server      A self-generated certificate was successfully loaded for encryption.
    2014-09-27 03:39:41.24 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    2014-09-27 03:39:41.24 Server      Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
    7806. This is an informational message only. No user action is required.
    2014-09-27 03:39:41.28 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
    to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2014-09-27 03:39:41.28 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2014-09-27 03:39:41.70 spid8s      Starting up database 'tempdb'.
    2014-09-27 03:39:41.86 spid7s      Warning ******************
    2014-09-27 03:39:41.86 spid7s      Attempting to change default collation to Turkish_CI_AS.
    2014-09-27 03:39:41.92 spid7s       index restored for master.syspriorities.
    2014-09-27 03:39:41.95 spid7s       index restored for master.sysbrickfiles.
    2014-09-27 03:39:41.96 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:41.96 spid7s       index restored for master.sysowners.
    2014-09-27 03:39:42.13 spid7s       index restored for master.sysdbreg.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s       index restored for master.sysschobjs.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.17 spid7s       index restored for master.syscolpars.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxlgns.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxsrvs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysnsobjs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.syscerts.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysrmtlgns.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysxprops.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysscalartypes.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysidxstats.
    2014-09-27 03:39:42.31 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysendpts.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysclsobjs.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysremsvcbinds.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysrts.
    2014-09-27 03:39:42.33 spid7s       index restored for master.sysasymkeys.
    2014-09-27 03:39:42.33 spid7s       index restored for master.syssqlguides.
    2014-09-27 03:39:42.44 spid7s       index restored for master.syssoftobjrefs.
    2014-09-27 03:39:42.47 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.48 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.49 spid7s       index restored for master.spt_values.
    2014-09-27 03:39:42.49 spid7s       index restored for master.MSreplication_options.
    2014-09-27 03:39:42.56 spid7s       index restored for tempdb.syspriorities.
    2014-09-27 03:39:42.56 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysowners.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysschobjs.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.59 spid7s       index restored for tempdb.syscolpars.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysnsobjs.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.syscerts.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysxprops.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysscalartypes.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysidxstats.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysclsobjs.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysremsvcbinds.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysrts.
    2014-09-27 03:39:42.62 spid7s       index restored for tempdb.sysasymkeys.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssqlguides.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssoftobjrefs.
    2014-09-27 03:39:42.75 spid7s       index restored for model.syspriorities.
    2014-09-27 03:39:42.75 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.75 spid7s       index restored for model.sysowners.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s       index restored for model.sysschobjs.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscolpars.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysnsobjs.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscerts.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysxprops.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysscalartypes.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysidxstats.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysclsobjs.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysremsvcbinds.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysrts.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysasymkeys.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssqlguides.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssoftobjrefs.
    2014-09-27 03:39:43.02 spid7s      Starting up database 'msdb'.
    2014-09-27 03:39:43.82 spid7s       index restored for msdb.syspriorities.
    2014-09-27 03:39:43.85 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.93 spid7s       index restored for msdb.sysowners.
    2014-09-27 03:39:43.99 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.09 spid7s       index restored for msdb.sysschobjs.
    2014-09-27 03:39:44.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.syscolpars.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.sysnsobjs.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.25 spid7s       index restored for msdb.syscerts.
    2014-09-27 03:39:44.25 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s       index restored for msdb.sysxprops.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.27 spid7s       index restored for msdb.sysscalartypes.
    2014-09-27 03:39:44.37 spid7s       index restored for msdb.sysidxstats.
    2014-09-27 03:39:44.41 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysclsobjs.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysremsvcbinds.
    2014-09-27 03:39:44.42 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysrts.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.sysasymkeys.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.syssqlguides.
    2014-09-27 03:39:44.59 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.74 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.85 spid7s       index restored for msdb.syssoftobjrefs.
    2014-09-27 03:39:44.89 spid7s       index restored for msdb.syspolicy_policies_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.sysproxies.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syscollector_execution_stats_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syssubsystems.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_primary_secondaries.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.sysdownloadlist.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_monitor_primary.
    2014-09-27 03:39:44.92 spid7s       index restored for msdb.sysoriginatingservers.
    2014-09-27 03:39:44.93 spid7s       index restored for msdb.log_shipping_monitor_history_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_monitor_error_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_secondary.
    2014-09-27 03:39:44.97 spid7s       index restored for msdb.log_shipping_secondary_databases.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.log_shipping_monitor_secondary.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysjobs.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_database_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.syscollector_blobs_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysjobsteps.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.logmarkhistory.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_session_statistics_internal.
    2014-09-27 03:39:45.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.12 spid7s       index restored for msdb.sysdtscategories.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.syspolicy_target_sets_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysschedules.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysdac_instances_internal.
    2014-09-27 03:39:45.33 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.50 spid7s       index restored for msdb.sysssispackages.
    2014-09-27 03:39:45.51 spid7s       index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
    2014-09-27 03:39:45.51 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysssispackagefolders.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysdac_history_internal.
    2014-09-27 03:39:45.53 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syscategories.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservers.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservergroups.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syspolicy_policy_category_subscriptions_internal.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysalerts.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysoperators.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syspolicy_system_health_state_internal.
    2014-09-27 03:39:45.63 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syscollector_config_store_internal.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s       index restored for msdb.sysmanagement_shared_server_groups_internal.
    2014-09-27 03:39:45.66 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysmanagement_shared_registered_servers_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.syscachedcredentials.
    2014-09-27 03:39:45.79 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.syscollector_collection_sets_internal.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.sysutility_ucp_dac_health_internal.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms_datatype.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysmail_profile.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysutility_ucp_managed_instances_internal.
    2014-09-27 03:39:45.83 spid7s       index restored for msdb.syspolicy_management_facets.
    2014-09-27 03:39:45.84 spid7s       index restored for msdb.sysutility_ucp_mi_health_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syscollector_collector_types_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syspolicy_configuration_internal.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_facet_events.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.sysmail_account.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_conditions_internal.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.sysutility_ucp_health_policies_internal.
    2014-09-27 03:39:45.88 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.syscollector_collection_items_internal.
    2014-09-27 03:39:45.90 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysmail_servertype.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
    2014-09-27 03:39:46.02 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_configuration_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.sysmail_server.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_policy_categories_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_object_sets_internal.
    2014-09-27 03:39:46.04 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysmail_configuration.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysdbmaintplan_databases.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.log_shipping_primary_databases.
    2014-09-27 03:39:46.39 spid7s      The default collation was successfully changed.
    2014-09-27 03:39:46.39 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2014-09-27 03:39:47.17 spid51      Changed database context to 'master'.
    2014-09-27 03:39:47.18 spid51      Changed language setting to us_english.
    2014-09-27 03:39:47.72 spid51      Setting database option RECOVERY to FULL for database model.
    2014-09-27 03:39:47.84 spid51      Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.84 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:48.27 spid51      Error: 15007, Severity: 16, State: 1.
    2014-09-27 03:39:48.27 spid51      '' is not a valid login or you do not have permission.
    2014-09-27 03:51:25.13 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:25.13 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:32.67 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:32.67 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:42.11 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:51:42.11 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:52:42.07 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:52:42.07 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:53:01.23 Logon       Error: 18461, Severity: 14, State: 1.
    2014-09-27 03:53:01.23 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
    2014-09-27 03:53:17.57 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:53:17.57 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:53:32.54 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:53:32.54 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:04.29 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:04.29 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:10.36 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:10.36 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:47.18 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:54:47.18 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    Resolve the error, please refer to the following links.
    Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
    could not register the SPN Kerberos:
    http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html  
    Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server

  • SQL Server Error when tryingt to install the CMS DB on SQL Server 2005 x64

    I am trying to install BOEXI R3 on w2k3 64-bit OS in a SQL Server 2005 x64 database, I am currently at the installation step where i Specify an exisiting CMS database. I created a System DSN and tested it, and it was successful. So when I got to the screen where I select my datasource I had to check use trusted connection because the datasource would not show up when Use DSN created by WOW64 option was checked. From there I could select the database I created. Oh yeah, I also made the application server local system account part of my DB admins group so it has full access to the database yet when I click next to connect I get a CMS Database Error: STU000226. here is what I have in my log:
    ThreadID     Message
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: findDFA_LLR:  (CmdLineDir) C:Documents and SettingsgsdadminDesktopBOEXI and BSM AnalyticsBOEXI R3 Full Version from SAPpackagedbcheck
    sqlrule.llr
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: Loading: database subsystem only
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: loading libary succeeded
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: DatabaseSubsystem::Init()
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:96): trace message: Creating the shared CWireObject::PropertyNameMap
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:118): trace message: Setting static property map
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:125): trace message: CWireObject::InitializeStaticPropertyMap() - reference count: 1
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: initializing subsystem succeeded
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: Loading: done loading subsystem - database subsystem only
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: DatabaseSubsystem::Connect()
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.DBConnectionManager.cpp:802): trace message: DBConnectionManager - Setting total target number of connections for pool 0 to 1.
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.SQLServerDatabase.cpp:119): trace message: SQLServer error found:  ErrorMessage( (Microsoft)[ODBC Driver Manager] Data source name not found and no default driver specified), ErrorCode(0)
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.dbutils.cpp:820): trace message: Caught DatabaseSubystem Error: BusinessObjects Enterprise CMS: Unable to connect to the CMS system database "BOEXI_CMS". Reason:  (Microsoft)[ODBC Driver Manager] Data source name not found and no default driver specified
    (Thu Apr 23 20:57:46 2009)     3024     3028     trace message: DatabaseSubsystem::Shutdown()
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:175): trace message: CWireObject::TerminateStaticPropertyMap() - reference count: 1
    (Thu Apr 23 20:57:46 2009)     3024     3028     (.wireobinit.cpp:182): trace message: Releasing
    static property map
    How do I get past this?

    The workaround was, I installed the SQL Server Client tools and created a System DataSource  and then had to create a user DataSource  (it is a quirk in the installer I guess) to get past this point in the installation. Now I have an even bigger problem. Everything but the CMS installed and the installer hung at the "Configuring the CMS" part. The installation finished but when I tried to log into the Central managment console I got this error:
    Error: Server GSD-RRPT-RDC:6400 not found or server may be down (FWM 01003) null
    I looked at the forums for the cause of this error and came to the conclusion that BOEXI does not support an installation on SQL Server 2005 when using Integrated Authentication to the SQL Server. See the engineers here disabled SQL Authentication for the SQL Server and  will not allow it.
    Is this true? Or is there a workaround to install the CMS using Integrated Authentication in the DataSource ?
    Thanks.

  • SQL Unattended installation failed... please specify correct command line to install sql server unattended. i want to install sql in Win XP 32 bit SP3...

    04/05/2014 19:31:03.156 ======================================================================
    04/05/2014 19:31:03.203 Setup launched
    04/05/2014 19:31:03.234 Attempting to determine media source
    04/05/2014 19:31:03.265 Media source value not specified on command line argument.
    04/05/2014 19:31:03.281 Setup is launched from media directly so default the value to the current folder.
    04/05/2014 19:31:03.312 Media source: c:\9fd8baca53072f532abe06daf8d0a91c\
    04/05/2014 19:31:03.328 Attempt to determine media layout based on file 'c:\9fd8baca53072f532abe06daf8d0a91c\mediainfo.xml'.
    04/05/2014 19:31:03.734 Media layout is detected as: Advanced
    04/05/2014 19:31:03.765 Media LCID is detected as: 1033
    04/05/2014 19:31:03.781 Local setup.exe not found, so continuing to run setup.exe from media.
    04/05/2014 19:31:03.828 /? or /HELP or /ACTION=HELP specified: false
    04/05/2014 19:31:03.859 Help display: false
    04/05/2014 19:31:03.890 Checking to see if we need to install .Net version 3.5
    04/05/2014 19:31:03.921 Determining the cluster status of the local machine.
    04/05/2014 19:31:03.953 The local machine is not configured as a cluster node.
    04/05/2014 19:31:04.000 Attempting to find media for .Net version 3.5
    04/05/2014 19:31:04.046 .Net version 3.5 is installed
    04/05/2014 19:31:04.078 RedistMSI::GetExpectedBuildRevision - Setup expects MSI 4.5.6001.22159 at the minimum
    04/05/2014 19:31:04.109 Attempting to get Windows Installer version
    04/05/2014 19:31:04.156 Windows Installer version detected: 4.5.6001.22299
    04/05/2014 19:31:04.187 RedistMSI::IsVistaRTM - Not Vista RTM build
    04/05/2014 19:31:04.234 Required version of Windows Installer is already installed
    04/05/2014 19:31:04.250 Attempt to initialize SQL setup code group
    04/05/2014 19:31:04.265 Attempting to determine security.config file path
    04/05/2014 19:31:04.296 Checking to see if policy file exists
    04/05/2014 19:31:04.343 .Net security policy file does exist
    04/05/2014 19:31:04.375 Attempting to load .Net security policy file
    04/05/2014 19:31:04.546 Processing entry ("MSVCM80", "Native")
    04/05/2014 19:31:04.593 Attempting to create .Net security code group node: MSVCM80
    04/05/2014 19:31:04.609 Processing entry ("MICROSOFT.SQLSERVER.CHAINER.SETUP", "Native")
    04/05/2014 19:31:04.656 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CHAINER.SETUP
    04/05/2014 19:31:04.671 Processing entry ("MICROSOFT.SQL.CHAINER.PACKAGE", "Native")
    04/05/2014 19:31:04.703 Attempting to create .Net security code group node: MICROSOFT.SQL.CHAINER.PACKAGE
    04/05/2014 19:31:04.718 Processing entry ("MICROSOFT.SQLSERVER.CHAINER.INFRASTRUCTURE", "Native")
    04/05/2014 19:31:04.765 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CHAINER.INFRASTRUCTURE
    04/05/2014 19:31:04.781 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.BOOTSTRAPEXTENSION", "Native")
    04/05/2014 19:31:04.796 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.BOOTSTRAPEXTENSION
    04/05/2014 19:31:04.843 Processing entry ("MICROSOFT.SQLSERVER.SETUP.CHAINER.WORKFLOW", "Native")
    04/05/2014 19:31:04.875 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.SETUP.CHAINER.WORKFLOW
    04/05/2014 19:31:04.890 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SQLCONFIGBASE", "Native")
    04/05/2014 19:31:04.921 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SQLCONFIGBASE
    04/05/2014 19:31:04.968 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SFC", "Native")
    04/05/2014 19:31:05.015 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SFC
    04/05/2014 19:31:05.046 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SETUPEXTENSION", "Native")
    04/05/2014 19:31:05.078 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SETUPEXTENSION
    04/05/2014 19:31:05.093 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.MSIEXTENSION", "Native")
    04/05/2014 19:31:05.109 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.MSIEXTENSION
    04/05/2014 19:31:05.125 Processing entry ("MICROSOFT.SQLSERVER.CHAINER.EXTENSIONCOMMON", "Native")
    04/05/2014 19:31:05.171 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CHAINER.EXTENSIONCOMMON
    04/05/2014 19:31:05.203 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SCO", "Native")
    04/05/2014 19:31:05.218 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SCO
    04/05/2014 19:31:05.250 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.CONFIGEXTENSION", "Native")
    04/05/2014 19:31:05.296 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.CONFIGEXTENSION
    04/05/2014 19:31:05.328 Processing entry ("MICROSOFT.SQLSERVER.DISCOVERY", "Native")
    04/05/2014 19:31:05.375 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.DISCOVERY
    04/05/2014 19:31:05.390 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.UIEXTENSION", "Native")
    04/05/2014 19:31:05.406 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.UIEXTENSION
    04/05/2014 19:31:05.421 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SSTRING", "Native")
    04/05/2014 19:31:05.468 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SSTRING
    04/05/2014 19:31:05.500 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.WIZARDFRAMEWORK", "Native")
    04/05/2014 19:31:05.531 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.WIZARDFRAMEWORK
    04/05/2014 19:31:05.562 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARDFRAMEWORK", "Native")
    04/05/2014 19:31:05.593 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARDFRAMEWORK
    04/05/2014 19:31:05.625 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARD", "Native")
    04/05/2014 19:31:05.671 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARD
    04/05/2014 19:31:05.687 Processing entry ("MICROSOFT.SQLSERVER.MANAGEMENT.CONTROLS", "Native")
    04/05/2014 19:31:05.703 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.MANAGEMENT.CONTROLS
    04/05/2014 19:31:05.718 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION", "Native")
    04/05/2014 19:31:05.750 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION
    04/05/2014 19:31:05.765 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.CONNECTIONINFO", "Native")
    04/05/2014 19:31:05.796 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.CONNECTIONINFO
    04/05/2014 19:31:05.828 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.RULESENGINEEXTENSION", "Native")
    04/05/2014 19:31:05.843 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.RULESENGINEEXTENSION
    04/05/2014 19:31:05.890 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.CLUSTER", "Native")
    04/05/2014 19:31:05.906 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.CLUSTER
    04/05/2014 19:31:05.937 Processing entry ("MSCLUSTERLIB", "Native")
    04/05/2014 19:31:05.968 Attempting to create .Net security code group node: MSCLUSTERLIB
    04/05/2014 19:31:05.984 Processing entry ("MICROSOFT.SQL.CHAINER.PACKAGEDATA", "Native")
    04/05/2014 19:31:06.000 Attempting to create .Net security code group node: MICROSOFT.SQL.CHAINER.PACKAGEDATA
    04/05/2014 19:31:06.015 Processing entry ("MICROSOFT.SQL.CHAINER.PRODUCT", "Native")
    04/05/2014 19:31:06.031 Attempting to create .Net security code group node: MICROSOFT.SQL.CHAINER.PRODUCT
    04/05/2014 19:31:06.078 Processing entry ("MICROSOFT.NETENTERPRISESERVERS.EXCEPTIONMESSAGEBOX", "Native")
    04/05/2014 19:31:06.093 Attempting to create .Net security code group node: MICROSOFT.NETENTERPRISESERVERS.EXCEPTIONMESSAGEBOX
    04/05/2014 19:31:06.125 Processing entry ("LANDINGPAGE", "Native")
    04/05/2014 19:31:06.156 Attempting to create .Net security code group node: LANDINGPAGE
    04/05/2014 19:31:06.187 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SLPEXTENSION", "Native")
    04/05/2014 19:31:06.250 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SLPEXTENSION
    04/05/2014 19:31:06.296 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.AGENTEXTENSION", "Native")
    04/05/2014 19:31:06.328 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.AGENTEXTENSION
    04/05/2014 19:31:06.359 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.POWERSHELLEXTENSION", "Native")
    04/05/2014 19:31:06.390 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.POWERSHELLEXTENSION
    04/05/2014 19:31:06.437 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SSISEXTENSION", "Native")
    04/05/2014 19:31:06.468 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SSISEXTENSION
    04/05/2014 19:31:06.484 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.ASEXTENSION", "Native")
    04/05/2014 19:31:06.515 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.ASEXTENSION
    04/05/2014 19:31:06.531 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.REPL_CONFIGEXTENSION", "Native")
    04/05/2014 19:31:06.578 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.REPL_CONFIGEXTENSION
    04/05/2014 19:31:06.625 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.MANAGEMENTTOOLSEXTENSION", "Native")
    04/05/2014 19:31:06.640 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.MANAGEMENTTOOLSEXTENSION
    04/05/2014 19:31:06.656 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SQLSERVER_CONFIGEXTENSION", "Native")
    04/05/2014 19:31:06.687 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SQLSERVER_CONFIGEXTENSION
    04/05/2014 19:31:06.703 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SNISERVERCONFIGEXT", "Native")
    04/05/2014 19:31:06.750 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SNISERVERCONFIGEXT
    04/05/2014 19:31:06.781 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SQLBROWSEREXTENSION", "Native")
    04/05/2014 19:31:06.812 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SQLBROWSEREXTENSION
    04/05/2014 19:31:06.828 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.RSEXTENSION", "Native")
    04/05/2014 19:31:06.859 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.RSEXTENSION
    04/05/2014 19:31:06.890 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.DMF", "Native")
    04/05/2014 19:31:06.906 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.DMF
    04/05/2014 19:31:06.937 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SMO", "Native")
    04/05/2014 19:31:06.953 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SMO
    04/05/2014 19:31:06.984 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SQLENUM", "Native")
    04/05/2014 19:31:07.015 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SQLENUM
    04/05/2014 19:31:07.031 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.FULLTEXT_CONFIGEXTENSION", "Native")
    04/05/2014 19:31:07.046 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.FULLTEXT_CONFIGEXTENSION
    04/05/2014 19:31:07.062 Processing entry ("FIXSQLREGISTRYKEY", "X86")
    04/05/2014 19:31:07.078 Attempting to create .Net security code group node: FIXSQLREGISTRYKEY
    04/05/2014 19:31:07.093 Processing entry ("FIXSQLREGISTRYKEY", "X64")
    04/05/2014 19:31:07.171 Processing entry ("FIXSQLREGISTRYKEY", "IA64")
    04/05/2014 19:31:07.218 Processing entry ("MICROSOFT.SQLSERVER.CHAINER.SETUP.RESOURCES", "Native")
    04/05/2014 19:31:07.250 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CHAINER.SETUP.RESOURCES
    04/05/2014 19:31:07.281 Processing entry ("MICROSOFT.SQLSERVER.CHAINER.INFRASTRUCTURE.RESOURCES", "Native")
    04/05/2014 19:31:07.312 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CHAINER.INFRASTRUCTURE.RESOURCES
    04/05/2014 19:31:07.359 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.BOOTSTRAPEXTENSION.RESOURCES", "Native")
    04/05/2014 19:31:07.390 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.BOOTSTRAPEXTENSION.RESOURCES
    04/05/2014 19:31:07.421 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SQLCONFIGBASE.RESOURCES", "Native")
    04/05/2014 19:31:07.437 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SQLCONFIGBASE.RESOURCES
    04/05/2014 19:31:07.484 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SFC.RESOURCES", "Native")
    04/05/2014 19:31:07.515 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SFC.RESOURCES
    04/05/2014 19:31:07.546 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SETUPEXTENSION.RESOURCES", "Native")
    04/05/2014 19:31:07.593 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SETUPEXTENSION.RESOURCES
    04/05/2014 19:31:07.609 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.MSIEXTENSION.RESOURCES", "Native")
    04/05/2014 19:31:07.640 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.MSIEXTENSION.RESOURCES
    04/05/2014 19:31:07.656 Processing entry ("MICROSOFT.SQLSERVER.CHAINER.EXTENSIONCOMMON.RESOURCES", "Native")
    04/05/2014 19:31:07.671 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CHAINER.EXTENSIONCOMMON.RESOURCES
    04/05/2014 19:31:07.718 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SCO.RESOURCES", "Native")
    04/05/2014 19:31:07.734 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.SCO.RESOURCES
    04/05/2014 19:31:07.765 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.CONFIGEXTENSION.RESOURCES", "Native")
    04/05/2014 19:31:07.796 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.CONFIGEXTENSION.RESOURCES
    04/05/2014 19:31:07.828 Processing entry ("MICROSOFT.SQLSERVER.DISCOVERY.RESOURCES", "Native")
    04/05/2014 19:31:07.843 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.DISCOVERY.RESOURCES
    04/05/2014 19:31:07.875 Processing entry ("MICROSOFT.SQLSERVER.CONNECTIONINFO.RESOURCES", "Native")
    04/05/2014 19:31:07.890 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONNECTIONINFO.RESOURCES
    04/05/2014 19:31:07.921 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.UIEXTENSION.RESOURCES", "Native")
    04/05/2014 19:31:07.953 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.UIEXTENSION.RESOURCES
    04/05/2014 19:31:07.968 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.WIZARDFRAMEWORK.RESOURCES", "Native")
    04/05/2014 19:31:07.984 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.WIZARDFRAMEWORK.RESOURCES
    04/05/2014 19:31:08.015 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARDFRAMEWORK.RESOURCES", "Native")
    04/05/2014 19:31:08.078 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARDFRAMEWORK.RESOURCES
    04/05/2014 19:31:08.140 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARD.RESOURCES", "Native")
    04/05/2014 19:31:08.171 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARD.RESOURCES
    04/05/2014 19:31:08.218 Processing entry ("MICROSOFT.SQLSERVER.MANAGEMENT.CONTROLS.RESOURCES", "Native")
    04/05/2014 19:31:08.265 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.MANAGEMENT.CONTROLS.RESOURCES
    04/05/2014 19:31:08.328 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.RESOURCES", "Native")
    04/05/2014 19:31:08.390 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.RESOURCES
    04/05/2014 19:31:08.453 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.CONNECTIONINFO.RESOURCES", "Native")
    04/05/2014 19:31:08.515 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.CONNECTIONINFO.RESOURCES
    04/05/2014 19:31:08.578 Processing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.RULESENGINEEXTENSION.RESOURCES", "Native")
    04/05/2014 19:31:08.625 Attempting to create .Net security code group node: MICROSOFT.SQLSERVER.CONFIGURATION.RULESENGINEEXTENSION.RESOURCES
    04/05/2014 19:31:08.671 Processing entry ("LANDINGPAGE.RESOURCES", "Native")
    04/05/2014 19:31:08.734 Attempting to create .Net security code group node: LANDINGPAGE.RESOURCES
    04/05/2014 19:31:09.062 Saved .Net security policy file
    04/05/2014 19:31:09.531 Strong name verification disabling is not required
    04/05/2014 19:31:09.578 /? or /HELP or /ACTION=HELP specified: false
    04/05/2014 19:31:09.593 Help display: false
    04/05/2014 19:31:09.609 Attempting to launch landing page workflow
    04/05/2014 19:31:09.625 Attempting to set setup mutex
    04/05/2014 19:31:09.640 Setup mutex has been set
    04/05/2014 19:31:09.656 Attempting to launch global rules workflow
    04/05/2014 19:31:09.687 Media source: c:\9fd8baca53072f532abe06daf8d0a91c\
    04/05/2014 19:31:09.703 Install media path: c:\9fd8baca53072f532abe06daf8d0a91c\x86\setup\
    04/05/2014 19:31:09.718 Media layout: Advanced
    04/05/2014 19:31:09.734 Attempting to get execution timestamp
    04/05/2014 19:31:09.765 Timestamp: 20140405_193103
    04/05/2014 19:31:09.781 Attempting to run workflow RUNRULES /RULES=GlobalRules
    04/05/2014 19:31:09.796 Attempting to launch process c:\9fd8baca53072f532abe06daf8d0a91c\x86\setup100.exe
    04/05/2014 19:31:37.546 Process returned exit code: 0x84BE0BC2
    04/05/2014 19:31:37.578 Workflow RUNRULES /RULES=GlobalRules returned exit code: 0x84BE0BC2
    04/05/2014 19:31:37.687 Attempting to determine security.config file path
    04/05/2014 19:31:37.750 Attempting to load .Net security policy file
    04/05/2014 19:31:37.781 Attempting to remove .Net security code group node
    04/05/2014 19:31:37.796 Removing entry ("MSVCM80", "Native")
    04/05/2014 19:31:37.812 Removing entry ("MICROSOFT.SQLSERVER.CHAINER.SETUP", "Native")
    04/05/2014 19:31:37.828 Removing entry ("MICROSOFT.SQL.CHAINER.PACKAGE", "Native")
    04/05/2014 19:31:37.843 Removing entry ("MICROSOFT.SQLSERVER.CHAINER.INFRASTRUCTURE", "Native")
    04/05/2014 19:31:37.859 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.BOOTSTRAPEXTENSION", "Native")
    04/05/2014 19:31:37.875 Removing entry ("MICROSOFT.SQLSERVER.SETUP.CHAINER.WORKFLOW", "Native")
    04/05/2014 19:31:37.906 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SQLCONFIGBASE", "Native")
    04/05/2014 19:31:37.921 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SFC", "Native")
    04/05/2014 19:31:37.937 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SETUPEXTENSION", "Native")
    04/05/2014 19:31:37.953 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.MSIEXTENSION", "Native")
    04/05/2014 19:31:37.968 Removing entry ("MICROSOFT.SQLSERVER.CHAINER.EXTENSIONCOMMON", "Native")
    04/05/2014 19:31:37.984 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SCO", "Native")
    04/05/2014 19:31:38.015 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.CONFIGEXTENSION", "Native")
    04/05/2014 19:31:38.031 Removing entry ("MICROSOFT.SQLSERVER.DISCOVERY", "Native")
    04/05/2014 19:31:38.046 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.UIEXTENSION", "Native")
    04/05/2014 19:31:38.062 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SSTRING", "Native")
    04/05/2014 19:31:38.078 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.WIZARDFRAMEWORK", "Native")
    04/05/2014 19:31:38.093 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARDFRAMEWORK", "Native")
    04/05/2014 19:31:38.109 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARD", "Native")
    04/05/2014 19:31:38.140 Removing entry ("MICROSOFT.SQLSERVER.MANAGEMENT.CONTROLS", "Native")
    04/05/2014 19:31:38.156 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION", "Native")
    04/05/2014 19:31:38.171 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.CONNECTIONINFO", "Native")
    04/05/2014 19:31:38.187 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.RULESENGINEEXTENSION", "Native")
    04/05/2014 19:31:38.203 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.CLUSTER", "Native")
    04/05/2014 19:31:38.234 Removing entry ("MSCLUSTERLIB", "Native")
    04/05/2014 19:31:38.250 Removing entry ("MICROSOFT.SQL.CHAINER.PACKAGEDATA", "Native")
    04/05/2014 19:31:38.265 Removing entry ("MICROSOFT.SQL.CHAINER.PRODUCT", "Native")
    04/05/2014 19:31:38.281 Removing entry ("MICROSOFT.NETENTERPRISESERVERS.EXCEPTIONMESSAGEBOX", "Native")
    04/05/2014 19:31:38.296 Removing entry ("LANDINGPAGE", "Native")
    04/05/2014 19:31:38.312 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SLPEXTENSION", "Native")
    04/05/2014 19:31:38.359 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.AGENTEXTENSION", "Native")
    04/05/2014 19:31:38.390 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.POWERSHELLEXTENSION", "Native")
    04/05/2014 19:31:38.406 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SSISEXTENSION", "Native")
    04/05/2014 19:31:38.421 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.ASEXTENSION", "Native")
    04/05/2014 19:31:38.437 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.REPL_CONFIGEXTENSION", "Native")
    04/05/2014 19:31:38.453 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.MANAGEMENTTOOLSEXTENSION", "Native")
    04/05/2014 19:31:38.468 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SQLSERVER_CONFIGEXTENSION", "Native")
    04/05/2014 19:31:38.484 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SNISERVERCONFIGEXT", "Native")
    04/05/2014 19:31:38.515 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SQLBROWSEREXTENSION", "Native")
    04/05/2014 19:31:38.531 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.RSEXTENSION", "Native")
    04/05/2014 19:31:38.546 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.DMF", "Native")
    04/05/2014 19:31:38.562 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SMO", "Native")
    04/05/2014 19:31:38.593 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SQLENUM", "Native")
    04/05/2014 19:31:38.640 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.FULLTEXT_CONFIGEXTENSION", "Native")
    04/05/2014 19:31:38.656 Removing entry ("FIXSQLREGISTRYKEY", "X86")
    04/05/2014 19:31:38.671 Removing entry ("FIXSQLREGISTRYKEY", "X64")
    04/05/2014 19:31:38.687 Removing entry ("FIXSQLREGISTRYKEY", "IA64")
    04/05/2014 19:31:38.703 Removing entry ("MICROSOFT.SQLSERVER.CHAINER.SETUP.RESOURCES", "Native")
    04/05/2014 19:31:38.718 Removing entry ("MICROSOFT.SQLSERVER.CHAINER.INFRASTRUCTURE.RESOURCES", "Native")
    04/05/2014 19:31:38.734 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.BOOTSTRAPEXTENSION.RESOURCES", "Native")
    04/05/2014 19:31:38.750 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SQLCONFIGBASE.RESOURCES", "Native")
    04/05/2014 19:31:38.781 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SFC.RESOURCES", "Native")
    04/05/2014 19:31:38.796 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SETUPEXTENSION.RESOURCES", "Native")
    04/05/2014 19:31:38.812 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.MSIEXTENSION.RESOURCES", "Native")
    04/05/2014 19:31:38.828 Removing entry ("MICROSOFT.SQLSERVER.CHAINER.EXTENSIONCOMMON.RESOURCES", "Native")
    04/05/2014 19:31:38.843 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.SCO.RESOURCES", "Native")
    04/05/2014 19:31:38.859 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.CONFIGEXTENSION.RESOURCES", "Native")
    04/05/2014 19:31:38.890 Removing entry ("MICROSOFT.SQLSERVER.DISCOVERY.RESOURCES", "Native")
    04/05/2014 19:31:38.906 Removing entry ("MICROSOFT.SQLSERVER.CONNECTIONINFO.RESOURCES", "Native")
    04/05/2014 19:31:38.921 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.UIEXTENSION.RESOURCES", "Native")
    04/05/2014 19:31:38.937 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.WIZARDFRAMEWORK.RESOURCES", "Native")
    04/05/2014 19:31:38.953 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARDFRAMEWORK.RESOURCES", "Native")
    04/05/2014 19:31:38.984 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.INSTALLWIZARD.RESOURCES", "Native")
    04/05/2014 19:31:39.000 Removing entry ("MICROSOFT.SQLSERVER.MANAGEMENT.CONTROLS.RESOURCES", "Native")
    04/05/2014 19:31:39.015 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.RESOURCES", "Native")
    04/05/2014 19:31:39.031 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.CONNECTIONINFO.RESOURCES", "Native")
    04/05/2014 19:31:39.046 Removing entry ("MICROSOFT.SQLSERVER.CONFIGURATION.RULESENGINEEXTENSION.RESOURCES", "Native")
    04/05/2014 19:31:39.062 Removing entry ("LANDINGPAGE.RESOURCES", "Native")
    04/05/2014 19:31:39.109 Saved .Net security policy file
    04/05/2014 19:31:39.125 Attempting to release setup mutex
    04/05/2014 19:31:39.156 Setup mutex has been released
    04/05/2014 19:31:39.171 Setup closed with exit code: 0x84C40013
    04/05/2014 19:31:39.187 ======================================================================

    Hello,
    There is a workaround posted for this error on the following threads:
    http://social.technet.microsoft.com/Forums/es-ES/ace2d644-dc82-424a-a608-4b4dc21065d4/setup-closed-with-exit-code-0x84c40013-silent-install-error-sql-server-2012-express-management?forum=sqlexpress
    http://social.msdn.microsoft.com/Forums/sqlserver/es-ES/0f5460d5-113f-4976-a43a-d2a7fdb7e304/sql-server-2008-developer-edition-install-fail-due-to-net-framework-35-missing?forum=sqlsetupandupgrade
    http://connect.microsoft.com/VisualStudio/feedback/details/472540/microsoft-sql-server-refuses-to-install
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

Maybe you are looking for

  • Process chain tables and tcodes

    Hi frinds, can any one send me the process chain tables and tcodes . plzz regards,. rajesh my mail id is [email protected]

  • Possible to block document when someone read it?

    Hi everyone, my client want a specific pdf file in the portal km to be blocked once someone read it, and unblocked when the person close the opened file. I did not found any pertinent infos on this, and I don't think it can be made without creating a

  • Unable to wirelessly connect to printer after switching ISP providers

    I recently moved and needed to change ISP providers.  My Mac is up and running wirelessly on the new network, but I can't seem to configure my HP printer.  Model: HP LaserJet P1102w.  Mac OS: X.  Problem details: Wireless icon blinks for several seco

  • Starting Weblogic server with eclipse.

    Hi, I am trying to start the web logic server through Hudson build.I have specified the goals in pom.xml and i am using cargo plugin (maven). When i build using Hudson. It builds the war file and copies to folder so when the weblogic starts it uses t

  • Airport outgoing ethernet cable

    Hi there, I'm thinking of buying the AirPort express, but there is one thing I would like to know. Is it possible to plug an ethernet cable in to get the AirPort connected, and then let another ethernet cable go out to still keep my MacBook connected