The System Monitoring Plug-in for Microsoft SQL Server

Hello all,
I have EM 11g monitoring all of my Oracle dbs - love it.
I am playing around with SQL plugin and wanted to know a few things:
1. does this need to be licensed
2. does the plug in monitor the actual databases or just at the instance level (performance of the engine only)
3. I was able to add the plug-in and everything seems good to go until i got to the following step in the documentation:
Adding Instances for Monitoring
Follow these steps to add the plug-in target to Grid Control for central monitoring and management:
+1.From the Agent home page where the plug-in was deployed, select the Microsoft SQL Server target type from the Add drop-down list, then click Go. The Add Microsoft SQL Server page appears.+
for the life of me, i can't figure out where to find the "Add drop-down list". Please help.!

Yes it needs to be licensed
Regards
Rob
http://oemgc.wordpress.com

Similar Messages

  • SYSTEM MONITORING PLUG-IN FOR MICROSOFT SQL SERVER - Licencing Cost

    Hi,
    We have license for Oracle 10g OEM. We are planning to implement SYSTEM MONITORING PLUG-IN FOR
    MICROSOFT SQL SERVER. Do we need to Buy separate license for this Plugin.
    Ritesh

    On <http://www.oracle.com/us/corporate/pricing/price-lists/index.html> in the technology pricelist
    check for "System Monitoring Plug-in for Non Oracle Databases"

  • Unable to open the physical file "D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\abc.mdf". Operating system error 2: "2(The system cannot find the file specified.)".

    hi,
    am running the below command for moving sql serevr mdf and ldf files  from one  drive to another : c  drive to d drive:
    but am getting the below error
    SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\abc.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
    use master
    DECLARE @DBName nvarchar(50)
    SET @DBName = 'CMP_143'
    DECLARE @RC int
    EXEC @RC = sp_detach_db @DBName
    DECLARE @NewPath nvarchar(1000)
    --SET @NewPath = 'E:\Data\Microsoft SQL Server\Data\';
    SET @NewPath = 'D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\';
    DECLARE @OldPath nvarchar(1000)
    SET @OldPath = 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\';
    DECLARE @DBFileName nvarchar(100)
    SET @DBFileName = @DBName + '.mdf';
    DECLARE @LogFileName nvarchar(100)
    SET @LogFileName = @DBName + '_log.ldf';
    DECLARE @SRCData nvarchar(1000)
    SET @SRCData = @OldPath + @DBFileName;
    DECLARE @SRCLog nvarchar(1000)
    SET @SRCLog = @OldPath + @LogFileName;
    DECLARE @DESTData nvarchar(1000)
    SET @DESTData = @NewPath + @DBFileName;
    DECLARE @DESTLog nvarchar(1000)
    SET @DESTLog = @NewPath + @LogFileName;
    DECLARE @FILEPATH nvarchar(1000);
    DECLARE @LOGPATH nvarchar(1000);
    SET @FILEPATH = N'xcopy /Y "' + @SRCData + N'" "' + @NewPath + '"';
    SET @LOGPATH = N'xcopy /Y "' + @SRCLog + N'" "' + @NewPath + '"';
    exec xp_cmdshell @FILEPATH;
    exec xp_cmdshell @LOGPATH;
    EXEC @RC = sp_attach_db @DBName, @DESTData, @DESTLog
    go
    can anyone pls help how to set the db offline. currently  i  stopped the sql server services from services.msc and started the  sql server agent.
    should i stop both services for moving from one drive to another?
    note: I tried teh below solution but this didint work:
    ALTER DATABASE <DBName> SET OFFLINE WITH ROLLBACK IMMEDIATE
    Update:
    now am getting the message :
    Msg 15010, Level 16, State 1, Procedure sp_detach_db, Line 40
    The database 'CMP_143' does not exist. Supply a valid database name. To see available databases, use sys.databases.
    (3 row(s) affected)
    (3 row(s) affected)
    Msg 5120, Level 16, State 101, Line 1
    Unable to open the physical file "D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\CMP_143.mdf". Operating system error 2: "2(The system cannot find the file specified.)".

    First you should have checked the database mdf/ldf name and location by using the command
    Use CMP_143
    Go
    Sp_helpfile
    Looks like your database CMP_143 was successfully detached but mdf/ldf location or name was different that is why it did not get copied to target location.
    Database is already detached that’s why db offline failed
    Msg 15010, Level 16, State 1, Procedure sp_detach_db, Line 40
    The database 'CMP_143' does not exist. Supply a valid database name. To see available databases, use sys.databases.
    EXEC @RC = sp_attach_db @DBName, @DESTData, @DESTLog
    Attached step is failing as there is no mdf file
    Msg 5120, Level 16, State 101, Line 1
    Unable to open the physical file "D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\CMP_143.mdf". Operating system error 2: "2(The system cannot find the file specified.)"
    Solution:
    Search for the physical files(mdf/ldf) in the OS and copy to target location and the re-run sp_attach_db with right location and name of mdf/ldf.

  • Diagnostic Pack and System monitoring plug-in for host.

    Is it correct to say that the ´Operating System Monitoring´ feature of the Oracle DB Diagnostic Pack discards the need of installing a System Monitoring Plug-in for Host in those servers where I have both Oracle DB and Diagnostic Pack for Oracle DB already installed?

    On <http://www.oracle.com/us/corporate/pricing/price-lists/index.html> in the technology pricelist
    check for "System Monitoring Plug-in for Non Oracle Databases"

  • JDBC for microsoft Sql server giving erro

    hello,
    I am getting an class not found exception when i am trying to load the JDBC Driver for microsoft SQL Server.
    //Driver d = (Driver)Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver").newInstance();
    // Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver"); // 2005 version
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver"); // 2000 version
    I have tried all these 3 methods still i am getting this error
    C:\Documents and Settings\rshekdar>java -jar D:\NetBeansProjects\HelloWorldApp\dist\HelloWorldApp.jar
    Hello World!
    exception caught in class for namecom.microsoft.jdbc.sqlserver.SQLServerDriver
    java.lang.ClassNotFoundException: com.microsoft.jdbc.sqlserver.SQLServerDriver
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:169)
    at helloworldapp.Main.main(Main.java:28)
    here is my classpath
    C:\Documents and Settings\rshekdar>set classpath
    CLASSPATH=.;C:\Program Files\Sybase\Jaguar CTS 3.5\html\classes;C:\Program Files\Sybase\Jaguar CTS 3.5\java\classes;C:\Program Files
    \Sybase\Shared\PowerBuilder\classes.zip;C:\Program Files\Java\jdk1.6.0_10\lib;C:\Program Files\Java\jre1.6.0_06\lib\ext\QTJava.zip;C
    :\Program Files\Java\jdk1.6.0_10;C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar;C:\Program Files\Mic
    rosoft SQL Server 2000 Driver for JDBC\lib\msbase.jar;C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar;
    can anyone tell me whats wrong here please i have tried all that i could possibly do. I cannot see anything wrong here, maybe a fresh set of eyes could. Any help given would be highly appreciated.

    Sorry, I didn't see your first first post of your CLASSPATH... I lost in the stack-trace (silly me ;-)
    C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar;
    C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar;
    C:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar;Yep, They look like they might be Sequel JDBC drivers to me... So open each of those jars in your zip-utility (winzip or whatever) and see if any of them contain the missing class: com.microsoft.jdbc.sqlserver.SQLServerDriver OR anything which looks similar... Are you certain the 2K and 05 class names are the same?
    And If the required class does exist then Q: Does java -jar use the CLASSPATH environment variable at all? ... If I was implementing it wouldn't... too "tacky"... I'd respect the classpath in the manifest, and an explicit -cp switch, but I wouldn't trust the system environment variable to point me to the "correct" required classes... not in a pink fit.
    I hope that helps some... these problems can be just sooooo frustrating!
    Cheers. Keith.

  • JDriver for microsoft sql server 2000

    "Hi, Currently, I am using your JDriver for microsoft SQL server 2000 for evaluation purposes and confront the following problem: (1) using utils.dbping C:\student\work>java utils.dbping mssqlserver4 sa "" ywu**** Success!!! ****You can connect to the database in your app using: java.util.Properties props = new java.util.Properties(); props.put("user", "sa"); props.put("password", ""); java.sql.Driver d = (java.sql.Driver)Class.forName("weblogic.jdbc.mssqlserver.Driver").newInstance(); java.sql.Connection conn = d.connect("jdbc:weblogic:mssqlserver4:ywu", props) // This mode is superior, especially in serverside classes because // it avoids DriverManager calls are class synchronized, and will // bottleneck any other JDBC in the server, even already-running // connections, because all JDBC drivers use DriverManager.println() // to log info and exceptions, and that call is also class synchronized. // For repeated connecting, a single driver instance can be re-used.**** or **** Class.forName("weblogic.jdbc.mssqlserver4.Driver").newInstance(); java.sql.Connection conn = DriverManager.getConnection("jdbc:weblogic:mssqlserver4:ywu", "sa", "");**** or **** java.util.Properties props = new java.util.Properties(); props.put("user", "sa"); props.put("password", ""); props.put("server", "ywu"); Class.forName("weblogic.jdbc.mssqlserver4.Driver").newInstance(); java.sql.Connection conn = DriverManager.getConnection("jdbc:weblogic:mssqlserver4", props);It seems that everything is fine, but(2) set up connection pool to MS SQL server, the weblogic server prints out error messages during the server goes up:<Jun 18, 2001 5:51:22 PM EDT> <Error> <JDBC Connection Pool> <Cannot startup connection pool "newSQLconn" weblogic.common.ResourceException:Could not create pool connection. The DBMS driver exception was:Driver

    Hi,
    I was having the same problem and to solve it u have to point your classpath to
    mssqlserver4v65.jar in the lib directory of your wl installation, in my case i
    did:
    set classpath=%classpath%;%WL_HOME%\lib\mssqlserver4v65.jar
    I hope it helps.
    Yuanqing Wu <[email protected]> wrote:
    "Hi, Currently, I am using your JDriver for microsoft SQL server 2000
    for evaluation purposes and confront the following problem: (1)
    using utils.dbping C:\student\work>java utils.dbping
    mssqlserver4 sa "" ywu**** Success!!! ****You can connect to the database
    in your app using: java.util.Properties props = new java.util.Properties();
    props.put("user", "sa"); props.put("password", ""); java.sql.Driver
    d = (java.sql.Driver)Class.forName("weblogic.jdbc.mssqlserver.Driver").newInstance();
    java.sql.Connection conn = d.connect("jdbc:weblogic:mssqlserver4:ywu",
    props) // This mode is superior, especially in serverside classes because
    // it avoids DriverManager calls are class synchronized, and will
    // bottleneck any other JDBC in the server, even already-running //
    connections, because all JDBC drivers use DriverManager.println() //
    to log info and exceptions, and that call is also class synchronized.
    // For repeated connecting, a single driver instance can be re-used.****
    or
    **** Class.forName("weblogic.jdbc.mssqlserver4.Driver").newInstance();
    java.sql.Connection conn = DriverManager.getConnection("jdbc:weblogic:mssqlserver4:ywu",
    "sa", "");**** or **** java.util.Properties props = new java.util.Properties();
    props.put("user", "sa"); props.put("password", ""); props.put("server",
    "ywu"); Class.forName("weblogic.jdbc.mssqlserver4.Driver").newInstance();
    java.sql.Connection conn = DriverManager.getConnection("jdbc:weblogic:mssqlserver4",
    props);It
    seems that everything is fine, but(2) set up connection pool to MS SQL
    server, the weblogic server prints out error messages during the server
    goes up:<Jun 18, 2001 5:51:22 PM EDT> <Error> <JDBC Connection Pool>
    <Cannot startup connection pool "newSQLconn" weblogic.common.ResourceException:Could
    not create pool connection. The DBMS driver exception was:Driver

  • How to monitor Log Backups for MS SQL Server

    Hello all.
    We are running Solution Manager 7.1 on SP Stack 10 and have downloaded the latest template content.
    When configuring the templates for DB monitoring, we noticed that although there is a metric that monitors the age of the last DB backup, there is no such metric to monitor the age of the last successful Log backup, or even a metric to alert us on a failed backup / log backup.
    Has any of you ever had to create a custom metric to monitor either the age of the latest successful log backup for MS SQL Server, or a custom metric to alert on failed backups / log backups?
    If yes, could you provide some instructions on how to create such a metric?
    Thank you in advance for your answers.
    Phevos

    Divyanshu, thank you for your answer.
    I had a similar idea to check the DB log file for failed log backups. The problem is that when I opened the log file from the dbacockpit, I found no errors/warnings for the days that our log backups did not run or failed. Here is a small part of that log to show you what I mean. In this example, the log backup was not running from 25th of July until the 28th of July when we fixed the log backups again, after receiving a disk space warning (log disk drive was almost full):
    The last successful log backup is mentioned in the log: "20140724091524    Backup    Log was backed up"
    Then as the days go by, there is no backup failure entries whatsoever to look for them in the log:
    20140725000023    spid18s    This instance of SQL Server has been using a process ID of 1304 since 5/27/2014 11:50:00 PM (local) 5/28/2014 6:50:00
    20140725000023    spid18s    AM (UTC). This is an informational message only; no user action is required.
    20140726000020    spid21s    This instance of SQL Server has been using a process ID of 1304 since 5/27/2014 11:50:00 PM (local) 5/28/2014 6:50:00
    20140726000020    spid21s    AM (UTC). This is an informational message only; no user action is required.
    20140727000023    spid22s    This instance of SQL Server has been using a process ID of 1304 since 5/27/2014 11:50:00 PM (local) 5/28/2014 6:50:00
    20140727000023    spid22s    AM (UTC). This is an informational message only; no user action is required.
    20140728000022    spid17s    This instance of SQL Server has been using a process ID of 1304 since 5/27/2014 11:50:00 PM (local) 5/28/2014 6:50:00
    20140728000022    spid17s    AM (UTC). This is an informational message only; no user action is required.
    Until finally on the 28th we restored the log backup functionality:
    20140728042814    Backup    Log was backed up. Database: XXX, creation date(time): 2010/12/22(16:45:29)
    So, I find it difficult to deduce an appropriate string to look for in the log, in order to generate an alert when my log backups are not working.
    Any suggestions? Am I looking at the wrong place perhaps?

  • Metric for Microsoft SQL Server

    I'm looking for the Metrics Reference Manual for Microsoft SQL Server. Can't find it on the documentation site

    Please check at http://download-west.oracle.com/docs/cd/B16240_01/doc/em.102/b28748/toc.htm

  • BEA WebLogic jDriver for Microsoft SQL Server

    Will BEA continue to support current and future installations of WebLogic jDriver for Microsoft SQL Server 2000 even though BEA recommends to use the JDBC driver available from Microsoft? A written response is necessary in order to determine our future product development direction.
    Thank you for your attention regarding this matter.

    Actually, this driver is already documented as deprecated. We intended to remove it from a future
    release (most likely, the release after WLS 8.1).
    The plan is to ship another driver out-of-the-box. We have been evaluating various drivers
    for features, quality, and performance. We are pushing very hard to have this replacement
    driver available in 8.1SP01, which will also ship with the WLI/Portal/WLW GA (announced to
    ship in July). The most likely candidate is already in testing both at the WLS level and
    with the layered products. It also did quite well in an internal performance comparison.
    "Joseph Weinstein" <[email protected]_this> wrote in message news:[email protected]_this...
    >
    >
    Peter Foskaris wrote:
    Will BEA continue to support current and future installations of WebLogic jDriver for Microsoft SQL Server 2000 even though
    BEA recommends to use the JDBC driver available from Microsoft? A written response is necessary in order to determine our future
    product development direction.
    >>
    Thank you for your attention regarding this matter.Hi. We intend to deprecate it. We may or may not fix bugs that are found in it in future, and will likely
    not do any more development on it, such as implementing any JDBC 2.0 methods. It will be in
    our next major release (8), but may not be in future ones.
    Joe Weinstein at BEA

  • Best driver available for MicroSoft SQL server?

    Hi,
    I am using MS-SQL server for my application server.
    Which driver should i use for it?
    Right now I am using ODBC driver.
    Please suggest me a few links where i could get the best driver(thin driver) for SQL server.
    regards
    suri

    Hi,
    best driver available for MicroSoft SQL server?i-net software has written a solid JDBC driver based on TDS. The trial version is limited to a single connection. http://www.inetsoftware.de/English/Produkte/JDBC_Overview/ms.htm
    jTurbo provides jdbc driver for MS SQL Server (www.jTurbo.com).
    Merant technologies also provides jdbc driver for MS SQL Server. Find more details at http://www.microsoft.com/sql/downloads/2000/jdbc.asp.Microsoft licenses MERANT's JDBC driver for SQL Server 2000.
    I cannot comment which one is the best driver. It depends on your project requirements and the buget alloted.
    Hope this helps.
    Good Luck.
    Gayam.Srinivasa Reddy
    Developer Technical Support
    Sun Micro Sysytems
    http://www.sun.com/developers/support/

  • Free JDBC 4.0 driver for Microsoft Sql Server database

    Is there any free JDBC 4.0 driver for Microsoft Sql Server database? The jTDS driver is JDBC 3.0 driver. http://jtds.sourceforge.net/

    Sooooooo...
    what's wrong with the driver provided by Microsoft themselves? Which is JDBC 4. And free.

  • Reporting Services for Microsoft SQL Server 2008 R2 (RTM) - 10.50.1617.0

    Hello,
    We are currently running:
    Microsoft SQL Server 2008 R2 (RTM) - 10.50.1617.0 (Intel X86)   Apr 22 2011 11:57:00   Copyright (c) Microsoft Corporation  Standard Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 2) (Hypervisor)
    We would like to know what is required to configure Reporting Services for Microsoft SQL Server 2008 R2 Standard.  Is their a cost associated?  I need to inform our IT people what is needed.
    Looking forward to your reply, Linda

    Double post:
    http://social.msdn.microsoft.com/Forums/en-US/3e6c5d4e-228e-4a95-b017-4c20ec61cae4/reporting-services-sql-server-express-2008-r2?forum=sqlreportingservices
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • JDBC for Microsoft SQL Server 2000

    Hello,
    I have installed Microsoft SQL Server 2000 to establish a connection with JDK 1.4.1 and run the following code:
    import java.sql.Connection.*;
    import java.sql.*;
    public class Connect
    private java.sql.Connection con = null;
    private final String url = "jdbc:microsoft:sqlserver://";
    private final String serverName= "localhost";
    private final String portNumber = "1433";
    private final String databaseName= "cbi";
    private final String userName = "sa";
    private final String password = "";
    // Informs the driver to use server a side-cursor,
    // which permits more than one active statement
    // on a connection.
    private final String selectMethod = "cursor";
    // Constructor
    public Connect(){}
    private String getConnectionUrl()
    return url+serverName+":"+portNumber+";databaseName="+databaseName+";selectMethod="+selectMethod+";";
    private java.sql.Connection getConnection()
    try
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    con = java.sql.DriverManager.getConnection(getConnectionUrl(),userName,password);
    if(con!=null)
    System.out.println("Connection Successful!");
    catch(Exception e)
    e.printStackTrace();
    System.out.println("Error Trace in getConnection() : " + e.getMessage());
    return con;
    Display the driver properties, database details
    public void displayDbProperties()
    java.sql.DatabaseMetaData dm = null;
    java.sql.ResultSet rs = null;
    try
    con= this.getConnection();
    if(con!=null)
    dm = con.getMetaData();
    System.out.println("Driver Information");
    System.out.println("\tDriver Name: "+ dm.getDriverName());
    System.out.println("\tDriver Version: "+ dm.getDriverVersion ());
    System.out.println("\nDatabase Information ");
    System.out.println("\tDatabase Name: "+ dm.getDatabaseProductName());
    System.out.println("\tDatabase Version: "+ dm.getDatabaseProductVersion());
    System.out.println("Avalilable Catalogs ");
    rs = dm.getCatalogs();
    while(rs.next())
    System.out.println("\tcatalog: "+ rs.getString(1));
    rs.close();
    rs = null;
    closeConnection();
    else
    System.out.println("Error: No active Connection");
    catch(Exception e)
    e.printStackTrace();
    dm=null;
    private void closeConnection()
    try
    if(con!=null)
    con.close();
    con=null;
    catch(Exception e)
    e.printStackTrace();
    public static void main(String[] args) throws Exception
    Connect myDbTest = new Connect();
    myDbTest.displayDbProperties();
    but, I received the error that ClassNotFoundException: com.microsoft.jdbc.sqlserver.SQLServerDriver, No active Connection.
    I added the 3 .jar files msbase.jar,mssqlserver.jar and msutil.jar to the System variables but it is not working. Is there any syntax for adding these .jar files to the System Variables?
    Please, help me and give me the solution for establishing the connection and loading the driver class. If I am doing anything wrong then please, tell me the right step.
    I am developing a project on Java and I have very little time left to accomplish it. Please help me.
    Thankyou.

    I had already given the .jar files to the User variables and System Variables but the driver class is still not loading. I had simply given the .jar file name for instance, msbase.jar;mssqlserver.jar;msutil.jar and also tried the path of .jar files i.e., C:\Microsoft SQL Server\-----------\lib\msbase.jar;C:\-------------lib\mssqlserver.jar;C:\----------------\lib\msutil.jar; but, both ways are not working. When I installed the MS SQL Server 2000 then in the lib folder, the 3 JAR files were not installed then, I downloaded a driver for MS SQL Server 2000 Driver for JDBC sp2, then, the JAR files were installed. Then, I copied those files to the lib folder of MS SQL Server and gave that path to the User and System Variables but it didn't work then I gave the original path of files where they are installed i.e., of the Driver's path which I downloaded from Microsoft but still now, my problem is not solved. Please help me.

  • Failed to install Hotfix 4311 for Microsoft SQL Server 2008 (KB2494094) (64-bit)

    I have a cluster install at SQL version 10.0.4272.  I want to upgrade this to 10.0.4311.  When I go through install on passive node it fails with message of "The patch installer has failed to update the shared features.  To determine
    the reason for failure, review the log files".  When I review detail.txt I see error lines below.  The OS is Windows Server 2008 R2 Enterprise 64-bit.
    2014-07-15 18:18:34 Slp: Error: Action "SqlEngineConfigAction_patch_configrc_Cpu64" failed during execution.
    2014-07-15 18:18:34 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_ConfigRC_postmsi" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_ConfigRC_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant
    features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Sco: Attempting to get instance feature flag UpgradeIncomplete for feature MPT_AGENT_CORE_CNI, instance MSSQL10.MSSQLSERVER
    2014-07-15 18:18:34 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey 
    2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\UpgradeIncompleteState
    2014-07-15 18:18:34 Slp: Sco: Attempting to get registry value MPT_AGENT_CORE_CNI
    2014-07-15 18:18:34 Slp: Sco: Attempting to get feature configuration state for feature MPT_AGENT_CORE_CNI, instance MSSQL10.MSSQLSERVER
    2014-07-15 18:18:34 Slp: Sco: Attempting to get instance feature flag ConfigurationState for feature MPT_AGENT_CORE_CNI, instance MSSQL10.MSSQLSERVER
    2014-07-15 18:18:34 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey 
    2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\ConfigurationState
    2014-07-15 18:18:34 Slp: Sco: Attempting to get registry value MPT_AGENT_CORE_CNI
    2014-07-15 18:18:34 Slp: The FeatureConfigState of MSI feature MPT_AGENT_CORE_CNI has been adjusted to patch configuration.
    2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_ConfigRC_postmsi" failed during execution.
    2014-07-15 18:18:34 Slp: Action "AgentConfigAction_patch_RC_Cpu64" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: AgentConfigAction_patch_RC_Cpu64 The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant features. The feature is tested for results:
    ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Error: Action "AgentConfigAction_patch_RC_Cpu64" failed during execution.
    2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_ConfigRC_postmsi" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_ConfigRC_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64. There
    are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Sco: Attempting to get instance feature flag UpgradeIncomplete for feature SQL_Replication_Core_Inst, instance MSSQL10.MSSQLSERVER
    2014-07-15 18:18:34 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey 
    2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\UpgradeIncompleteState
    2014-07-15 18:18:34 Slp: Sco: Attempting to get registry value SQL_Replication_Core_Inst
    2014-07-15 18:18:34 Slp: Sco: Attempting to get feature configuration state for feature SQL_Replication_Core_Inst, instance MSSQL10.MSSQLSERVER
    2014-07-15 18:18:34 Slp: Sco: Attempting to get instance feature flag ConfigurationState for feature SQL_Replication_Core_Inst, instance MSSQL10.MSSQLSERVER
    2014-07-15 18:18:34 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey 
    2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\ConfigurationState
    2014-07-15 18:18:34 Slp: Sco: Attempting to get registry value SQL_Replication_Core_Inst
    2014-07-15 18:18:34 Slp: The FeatureConfigState of MSI feature SQL_Replication_Core_Inst has been adjusted to patch configuration.
    2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_ConfigRC_postmsi" failed during execution.
    2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_ConfigRC_postmsi" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_ConfigRC_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature
    is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Sco: Attempting to get instance feature flag UpgradeIncomplete for feature SQL_FullText_Adv, instance MSSQL10.MSSQLSERVER
    2014-07-15 18:18:34 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey 
    2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\UpgradeIncompleteState
    2014-07-15 18:18:34 Slp: Sco: Attempting to get registry value SQL_FullText_Adv
    2014-07-15 18:18:34 Slp: Sco: Attempting to get feature configuration state for feature SQL_FullText_Adv, instance MSSQL10.MSSQLSERVER
    2014-07-15 18:18:34 Slp: Sco: Attempting to get instance feature flag ConfigurationState for feature SQL_FullText_Adv, instance MSSQL10.MSSQLSERVER
    2014-07-15 18:18:34 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey 
    2014-07-15 18:18:34 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\ConfigurationState
    2014-07-15 18:18:34 Slp: Sco: Attempting to get registry value SQL_FullText_Adv
    2014-07-15 18:18:34 Slp: The FeatureConfigState of MSI feature SQL_FullText_Adv has been adjusted to patch configuration.
    2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_ConfigRC_postmsi" failed during execution.
    2014-07-15 18:18:34 Slp: Action "FulltextConfigAction_patch_configrc_Cpu64" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: FulltextConfigAction_patch_configrc_Cpu64 The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature is tested for results:
    ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Error: Action "FulltextConfigAction_patch_configrc_Cpu64" failed during execution.
    2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 10 dependant
    features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi" failed during execution.
    2014-07-15 18:18:34 Slp: Action "cluster_group_cluster_patch_startup_Cpu64" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: cluster_group_cluster_patch_startup_Cpu64 The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 10 dependant features. The feature is tested
    for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Error: Action "cluster_group_cluster_patch_startup_Cpu64" failed during execution.
    2014-07-15 18:18:34 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant
    features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi" failed during execution.
    2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64. There
    are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Startup_postmsi" failed during execution.
    2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_Startup_postmsi" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_Startup_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature
    is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_Startup_postmsi" failed during execution.
    2014-07-15 18:18:34 Slp: Action "FulltextConfigAction_patch_startup_Cpu64" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: FulltextConfigAction_patch_startup_Cpu64 The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature is tested for results: ValidateResult,
    Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Error: Action "FulltextConfigAction_patch_startup_Cpu64" failed during execution.
    2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are
    10 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi" failed during execution.
    2014-07-15 18:18:34 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2
    dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi" failed during execution.
    2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64.
    There are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_StartupFinalize_postmsi" failed during execution.
    2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_StartupFinalize_postmsi" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_StartupFinalize_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features.
    The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_StartupFinalize_postmsi" failed during execution.
    2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Finalize_postmsi" failed during execution.
    2014-07-15 18:18:34 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_Finalize_postmsi" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_Finalize_postmsi The condition tests feature: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant
    features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_Finalize_postmsi" failed during execution.
    2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Finalize_postmsi" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Finalize_postmsi The condition tests feature: SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64. There
    are 3 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Patch_Finalize_postmsi" failed during execution.
    2014-07-15 18:18:34 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_Finalize_postmsi" will return false due to the following conditions:
    2014-07-15 18:18:34 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_Finalize_postmsi The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64. There are 3 dependant features. The feature
    is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
    2014-07-15 18:18:34 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
    2014-07-15 18:18:34 Slp: Error: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Patch_Finalize_postmsi" failed during execution.
    2014-07-15 18:18:39 Slp: Error result: -2068643839
    2014-07-15 18:18:39 Slp: Result facility code: 1203
    2014-07-15 18:18:39 Slp: Result error code: 1
    2014-07-15 18:18:39 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
    2014-07-15 18:18:39 Slp: Sco: Attempting to open registry subkey 
    2014-07-15 18:18:39 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
    2014-07-15 18:18:39 Slp: Sco: Attempting to get registry value DW0201
    2014-07-15 18:18:40 Slp: Submitted 1 of 1 failures to the Watson data repository

    Hello,
    Please read the following support article:
    http://support.microsoft.com/kb/2216468/en-us
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Driver for Microsoft SQL SERVER 2008 (MII 12.0.X)

    Hi,
    we have MII 12.0.11 and we need to access a database on Microsoft SQL Server 2008.
    I need a suggestion on the driver  choice...because the Microsoft JDBC  drivers for SQL Server 2008  on the following links officially need at least JDK 5...and for what I know our MII version is based on Netweaver 7.0 on Java 1.4.
    http://www.microsoft.com/downloads/en/details.aspx?FamilyID=99b21b65-e98f-4a61-b811-19912601fdc9&displaylang=en
    http://www.microsoft.com/downloads/en/details.aspx?FamilyID=%20a737000d-68d0-4531-b65d-da0f2a735707&displaylang=en
    We are currently using this driver (with database on Microsoft  SQL Server 2005)
    http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c47053eb-3b64-4794-950d-81e1ec91c1ba
    which, on the contrary, doesn't support SQL Server 2008.
    I don't know how to proceed...
    Thanks in advance
    Mauro

    Try Microsoft SQL Server 2005 JDBC Driver 1.2
    [Connect MII 12.0 to SQL server 2008|Connect MII 12.0 to SQL server 2008]

Maybe you are looking for