Required Microsoft Sql Server 2005 Server Roles for JDBC Connection

Hi!
I have developed a database in MS SQL Server 2005, to which I would require only bulkadmin server role from an external java application, because I only need to update rows, insert values or use select queries in the database.
The problem is that, using either the Microsoft JDBC Driver 1.1 or the Java JDBC ODBC Driver and the Windows XP Data Base (ODBC) configurations, I need a user with sysadmin server role inside Sql Server, otherwise JDBC won't connect to the database using the selected user. Even if I leave the sql login with setupadmin or any server role lower than sysadmin, the connection is refused.
Is there no way to connect using JDBC to MS Sql Server 2005 other than granting the connected user sysadmin rights? My code looks as follows:
String driver = "com.microsoft.sqlserver.jdbc.SQLServerDriver";
String url = "jdbc:sqlserver://FIREBLADE\\SQLEXPRESS";
String user = "username";
String password = "password$$";
Connection conn;
Class.forName(driver);
conn = DriverManager.getConnection(url,user,password);
if (conn != null)
System.out.println("\nSQL Server Connection established ...\n");
I have heard that Java JDBC connections to Microsoft require high-level access, and if that's the case I would rather migrate my database to MySql.
Any informed answer is more than welcome. Thanks for reading my post!

Well i personally prefer usage of open source MS SQL SERVER 2k jdbc driver called jtds instead of the driver provided by MS themselves(which is proproteriry) as i had similar problem which i personally encountered when i was using it.
go through the below link for further info.
http://jtds.sourceforge.net/
REGARDS,
RaHuL

Similar Messages

  • Is Distributed Transaction Coordinator services of the application role are required by SQL Server 2012 for clustering and support of SharePoint 2013.

    All I want to know is if Distributed Transaction Coordinator services of the application role are required by SQL Server 2012 for clustering and support of SharePoint 2013.
    I have been planning and deploying my companies first Windows Server 2012/SQL Server 2012 Always On cluster and Always On Availability Groups Multi-Subnet cluster and instances for SharePoint 2013, and I will be brutally honest, the documentation on either
    the MSDN and TechNet leave alot to be desired. Continually finding links in the documentation will take me from a Windows 2012 reference to a page talking about Windows Server 2008 or R2, The differences of which there are so many when it comes to configurations,
    settings, roles, services when working with SQL Server 2012. I have been confused, frustrated, screaming mad, with all the misdirection in this documentation.  The documentation takes me windows 2008 R2 which is different than 2012!
    Tired and trying to pick myself up off the floor!
    Greg
    Gman

    In general, DTC is not required for SQL 2012.  But, since you are asking specifically about SharePoint, it would be better to ask in a SharePoint forum.  They would be more likely to know those situations where FTC might be needed by SharePoint. 
    .:|:.:|:. tim

  • SQL Server roles for migration

    What specific SQL Server roles must be granted to the user connecting from Oracle SQL Developer in order to perform a migration? The SQL Developer Users Guide only says "This user must have DBA access to the Microsoft SQL Server database". I work in an extremely large environment with many separate DBA groups who are reluctant to grant the sysadmin role to anyone not in their group. I want to make sure I ask for all the necessary permissions at the same time so I only have to go through this fight once.
    Thanks
    Ron

    Hi Ron,
    Thats wrong. When we put together the SQL Developer Migration Workbench. One of the main things that we thought about was your exact situation.
    Today, we dont need SA/dba privs to capture a database, or any specific roles. We capture what we can see from the system tables. So, if you have access to object (like executing a sp) but dont have privs to see the source, then we cant capture it. Like wise with all other objects too.
    So, connect to your database, capture it and convert it, but always be aware of the role you are doing it as. You will only get what that user can see.
    Barry

  • Configuration manager requires microsoft sql server 2008 sp2 with cumulative update 9 or higher

    Hi,
    I have this error during setup of SCCM 2012 R2 to a sql server. Patch level is higher then what is mentioned in popup.
    Please advise.
    Note: build of SQL is 10.50.4000
    J.
    Jan Hoedt

    Thanks. There is no c:\configmgrprereq.log but there is a configmgrsetup.log:
    INFO: setupdl.exe: Finish  $$<Configuration Manager Setup><12-16-2013 13:33:10.799-60><thread=1660 (0x67C)>
    CWmiRegistry::GetStr: Failed to get string value MSSQLSERVER  $$<Configuration Manager Setup><12-16-2013 13:34:56.756-60><thread=3068 (0xBFC)>
    Failed to retrieve SQL Server instance name[MSSQLSERVER].  $$<Configuration Manager Setup><12-16-2013 13:34:56.761-60><thread=3068 (0xBFC)>
    WARNING: failed to retrieve port number for SQL.ourcompany.com.  $$<Configuration Manager Setup><12-16-2013 13:34:56.763-60><thread=3068 (0xBFC)>
    WARNING: failed to retrieve port number for SQL.ourcompany.com.  $$<Configuration Manager Setup><12-16-2013 13:34:56.763-60><thread=3068 (0xBFC)>
    INFO: Registered type SQL.ourcompany.com MASTER for SQL.ourcompany.com master  $$<Configuration Manager Setup><12-16-2013 13:34:56.763-60><thread=3068 (0xBFC)>
    INFO: Registered type SMS Master for SQL.ourcompany.com master  $$<Configuration Manager Setup><12-16-2013 13:34:56.764-60><thread=3068 (0xBFC)>
    INFO: Registered type SQL.ourcompany.com SCCM2012R2 for SQL.ourcompany.com SCCM2012R2 $$<Configuration Manager Setup><12-16-2013 13:34:56.764-60><thread=3068 (0xBFC)>
    INFO: Registered type SMS ACCESS for SQL.ourcompany.com SCCM2012R2 $$<Configuration Manager Setup><12-16-2013 13:34:56.764-60><thread=3068 (0xBFC)>
    *** [08001][14][Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid connection.  $$<Configuration Manager Setup><12-16-2013 13:35:57.478-60><thread=3068 (0xBFC)>
    *** [01000][14][Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Invalid Instance()).  $$<Configuration Manager Setup><12-16-2013 13:35:57.478-60><thread=3068 (0xBFC)>
    *** Failed to connect to the SQL Server, connection type: SQL.ourcompany.com MASTER.  $$<Configuration Manager Setup><12-16-2013 13:35:57.479-60><thread=3068 (0xBFC)>
    *** [08001][14][Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid connection.  $$<Configuration Manager Setup><12-16-2013 13:36:58.135-60><thread=3068 (0xBFC)>
    *** [01000][14][Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Invalid Instance()).  $$<Configuration Manager Setup><12-16-2013 13:36:58.135-60><thread=3068 (0xBFC)>
    *** Failed to connect to the SQL Server, connection type: SQL.ourcompany.com MASTER.  $$<Configuration Manager Setup><12-16-2013 13:36:58.136-60><thread=3068 (0xBFC)>
    Could the error be related to other prereqs not met?
    Jan Hoedt

  • Connecting to SQL Server 2000 with MS SQL Server Driver for JDBC

    Hi,
    I am brand new to JDBC . I have installed JDBC driver (for JDBC 2.0) from the Microsoft site and made relevant changes to the class path variable to include the driver paths, as suggested in the driver help documnnts. I have written a simple java code to register. But i get "class NotFound" error.
    here's my code. What am I doing wrong? Thnaks for the help....
    class Test {
         public Test() throws Exception {
              // Get Connection
         //     Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
         DriverManager.registerDriver (new com.microsoft.jdbc.sqlserver.SQLServerDriver());
              Connection conn = DriverManager.getConnection("jdbc:microsoft:sqlserver://SQL1:1433",myuser,mypwd);
              if (conn != null) {
                   System.out.println();
                   System.out.println("Successful Connection");
                   System.out.println();
                   // Meta Data
                   DatabaseMetaData meta = conn.getMetaData();
                   System.out.println("\n Driver Information");
                   System.out.println("Driver Name: " + meta.getDriverName());
                   System.out.println("Driver Version: " + meta.getDriverVersion());
                   System.out.println("\n Database Information");
                   System.out.println("Database Name: " + meta.getDatabaseProductName());
                   System.out.println("Database Version: " + meta.getDatabaseProductVersion());
         } //Test
         public static void main(String [] args) throws Exception {
              Test test = new Test();
    }

    Hi MoD,
    This is the exact command I used for compiling
    C:\>javac -classpath "c:\java;c:\Program Files\Microsoft SQL Server 2000 Driver
    for JDBC\lib\mssqlserver.jar;c:\Program Files\Microsoft SQL Server 2000 Driver f
    or JDBC\lib\msbase.jar;c:\Program Files\Microsoft SQL Server 2000 Driver for JDB
    C\lib\msutil.jar" c:\java\Test.java
    To Execute I used
    C:\>java -classpath "c:\java;c:\Program Files\Microsoft SQL Server 2000 Driver
    for JDBC\lib\mssqlserver.jar;c:\Program Files\Microsoft SQL Server 2000 Driver f
    or JDBC\lib\msbase.jar;c:\Program Files\Microsoft SQL Server 2000 Driver for JDB
    C\lib\msutil.jar" c:\java\Test
    In fact it kept thrwing up the Class Not Found error for the above commands.
    But as U suggested I removed the classpath and executed both javac and java commands without classpath clause , and guess what it worked for the line
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    (i.e., it dint throw any exception like before). So can I assume that driver is successfully registered?
    I tried using Jcreator for compile and run. But I got the same error msg as the commands given above with calsspath caluse. Is there a way around for this to make it work from an external editing tool like Jcreator apart from removing the classpath option from the JDKTool optional setting(doing this did not help for me)
    Also one last favor: How do I connect with the trusted connection option? (i.e. it should use already logged in windows authentification login)
    Thanks for all U'r help. I appreciate it very much.
    Suma

  • Do we need to create ODBC connection on sql server-cube for OLAP connection?

    need to create olap connection sql server cube .....?

    Hi Wafa,
    Thanks for quick reply.
    Actually i don't have username or password.if you don't mind can you share me the document of this thread: 1623999 - How to make a connection to Microsoft SQL Server Analysis
    Services in Business Objects Enterprise 4.0
    please i want to fixed this issues so help me
    Regards
    Mustafa

  • Urgent Clarification - Microsoft SQL Server JDBC Driver Problem

    Hi,
    Can somebody tell me how to create a connection Pool in weblogic 7 using Microsoft
    SQL Server Driver for JDBC.(should be XADataSource).
    I mean the pool should be created using com.microsoft.jdbcx.sqlserver.SQLServerDataSource
    class.
    The error message i am getting is "Unknown source" during providing targets for
    the connection pool.
    Thanks in advance,
    Rahul.

    <JDBCConnectionPool
    DriverName="com.microsoft.jdbcx.sqlserver.SQLServerDataSource"
    Name="SQL2000JDBC"
    Properties="serverName=nc-answline-w2k;url=jdbc:microsoft:sqlserver;dataSourceName=SQL2000JDBC;user=test;databaseName=test;selectMethod=curosr;userName=test;password=test;portNumber=1435"
    URL="jdbc:microsoft:sqlserver"/>
    Try this is your config.xml and make sure you have mssqlsriver first thing in classpath.
    Thanks,
    Mitesh
    Rahul wrote:
    Hi,
    Can somebody tell me how to create a connection Pool in weblogic 7 using Microsoft
    SQL Server Driver for JDBC.(should be XADataSource).
    I mean the pool should be created using com.microsoft.jdbcx.sqlserver.SQLServerDataSource
    class.
    The error message i am getting is "Unknown source" during providing targets for
    the connection pool.
    Thanks in advance,
    Rahul.

  • 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

  • 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.

  • 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

  • Is there a way to convert Crystal Reports to Microsoft SQL Server 2005 reporting services?

    Post Author: Lourdes Hernandez
    CA Forum: General
    Our department has always worked with and we love Crystal Reports. Unfortunately, certain reports now need to be converted to Microsoft SQL Server 2005 reporting services which from what I read I think they are *.rdl reports. Does Crystal reports have any way around this? I would have to learn this other tool when I'm already so happy with Crystal. I was thinking If I could just code the report in crystal and export it in a specific format that would be compatible Microsoft, the problem would be solved.
    Any ideas would be greatly appreciated.

    Post Author: bettername
    CA Forum: General
    Ditto!
    There are some software packages to convert from CR to RS, but none work 100% AFAIK, and will require manual tuning.
    Seems like a big hassle and learning curve just to get reports published via another method - I know I'd put up huge resistance if they tried to take my CR away from me!

  • 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]

  • Regarding Microsoft SQL Server 2000 Driver for JDBC (2.2.0019)

    I have downloaded and installed Microsoft SQL Server 2000 Driver for JDBC (2.2.0019). Now i have to configure it for my development purpose. Can i use this driver for my development purpose or not. If yes does it create any kind of problem in future when i change the platform. My development should not depend on driver and database.
    Can i use any other driver provided by sun microsystem. If yes let me know where can i download and configure it.
    Waiting for the updates ASAP

    See, the bridge, being a type 1 driver has
    river has all the inherent limitations of that type
    drivers, due to the extra levels the data must
    passthrough inthe journey between the DB and the
    client. Also the use of native code.. makes it
    unsuitable to be used in applets.. the odbc should be
    configured in the client for this driver to work. etc.
    etc.
    It may be stable and useful for some
    for some applications.. but for sccenarios where one
    needs the solution tobe platform independent, ...By definition that would be the case. Of course the odbc-bridge does work on Windows, Solaris and Linux. So what other platform were you thinking about?
    ... less dependent on the user configuration,The bridge doesn't need any configuration. Or at least not any more than any other driver. The ODBC driver of course does need configuration.
    ...needs the minimum preparations from theuser, and above all give
    the fastest response time for him, the bridge cannot
    beat type 4 drivers. You are going to have to provide a link for that particular performance quote. Given that performance is impact most severely by requirements then design and finally by round trip time to the database I doubt that for applications (rather than benchmarks) that any difference is going to be significant.
    the problem i think was my use of
    my use of 'commercial' that u pointed out..
    anyway.. u are of course right if what u intended was
    stability only. but what i intended with that word was
    different .. sorry for creating the confusion.
    And it still seems like you are implying that it is not suitable for deployment in production systems. And as I pointed out I did deploy it in a large scale production system.
    I am not saying that type 4 drivers do not have a place nor that they do not have advantages, but their mere existance does not prove that they are a better choice for all installations.

  • MS SQL 2008 R2 Named instance: Login failed. Microsoft SQL server, Error: 18452) - Tryig to access using the FQDN assigned for the backup network card.

    Hi,
       I have a windows 2008 R2 Enterprise servers with standalone MS-SQL 2008 R2 named instance.  The server is having two networks, once production and the second for backup. The server FQDN is resolving to the production IP. The backup NIC
    DNS dynamic update is disabled and an "A" record is registered with the dns.  While trying to connect to the instance using the management studio:
    Successfuly able to connect using the instance name, the production hostname, production IP and backup IP. 
    but while trying to connect to the insance using the backup hostname getting the below error:
    "Login failed. The login is an untrusted domain and cannot be used with windows authentication. (Microsoft SQL server, Error: 18452) "
    This is required for the backup tool to get connected using the backup FQDN of the server.
    Should I need to create a host name alias,  request you to kindly assist me with the best recommedation to fix this.
    http://blogs.msdn.com/b/dbrowne/archive/2012/05/21/how-to-add-a-hostname-alias-for-a-sql-server-instance.aspx

    Hi,
    It might be a kerberos issue.  Check that there are valid SPN's registered using the setspn utility - http://technet.microsoft.com/en-us/library/cc731241.aspx
    Thanks, Andrew
    My blog...

  • Can I use Microsoft SQL Server Management Studio version 11.0 to write SQL queries for "SQL Server Compact 4.0 Local Database"

    Hi, Can I use Microsoft SQL Server Management Studio version 11.0 to write SQL queries for "SQL Server Compact 4.0 Local Database" ?
    When I use Connect Object Explorer, the "Connect to Server" dialog box which pops up has only 4 selections in the Server Type Drop Down List. They are Database Engine, Analysis Services, Reporting Services & Integration Services. I have read
    somewhere that there should be a compact database option. but I do not see it.
    What I would like to do is use free form SQL Queries against the tables in "SQL Server Compact 4.0 Local Database" .
    Once I have validated these queries, then I will use them in my Visual Studio 2012 C#, ASP.NET application. I created the Local Database using Visual Studio 2012 for use by my application.
    Thank you for your help..
    diana4

    Hello,
    With SSMS 2005 we have had the Option to work with SQL CE database files, but not with higher Version of SSMS.
    You can use the free SQL CE Toolbax instead; see
    http://sqlcetoolbox.codeplex.com/
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

Maybe you are looking for

  • I have a big Manufacturing problem with my i phone 5  what to do now?

    Dear sir , I want to Complain for my new i phone 5 that I get it on last December its only work for three month only with out any bad using my monitor is freezed and i cant use the phone when i sent to the dealer they inform me thet mobile have a man

  • Patching CRM online only

    Hi all We have a CRM 2007 (ABAP only). We want to patch the middleware only without the Mobile Clients on the laptops of the sales representatives. Could someone tell me please which components I can patch without having to patch the CRM Mobile Clien

  • How can I get my Black Macbook keyboard to light up

    have seen in many different cases that the Black Macbook keyboard has been light up. I want to know how i can do that even though the MBP's have a sensor to make it light up but any way that i can make mine light up?

  • Iphone SIM usage to other phone

    Hi,I got iphone 4 and would like to put its micro SIM into other GSM phone (with SIM adapter), can anyone comment if it will work. We have some restriction to use iphone @ workpace hence thought to use it differently. Thanks

  • How can i change my facetime camera settings on skype?

    But not from skype-prefrences-video/audio i need more advanced settings like brightness etc.