SQL connection string failed for $ password

Hi Team,
I am not able to connect to SQL DB when password contains $ symbol. Please help me to open connection for this scenenrio.
$sqlconstr = "Data Source=Server1;Initial Catalog=DB;User ID=User;pwd='$$XXXXX0';"
$sqlconn = New-Object system.Data.SqlClient.SqlConnection
$sqlconn.connectionstring = $sqlconstr
$sqlconn.open()

Thanks I tried below string & it worked
$sqlconstr = 'Data Source=Server1;Initial Catalog=DB;User ID=User;pwd=$$XXXXX0;'

Similar Messages

SCCM Console issue, SQL connectivity login failed for SCCM machine account

Hi ,
As part of resolving the corrupt SCCM 2012 R2 environment, we have uninstalled the site from the Standalone primary site and restored it from the last backup. The database is on remote server on SQL 2012 SP1. Only Site recovery is run.
Post the restoration on unable to launch the SCCM console, Error Could not connect to the site.
When I checked the logs in the log file SmsProv.log in the program filles\Microsoft Configuration manager\logs, the error is as below
*~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspobjectquery.cpp(6260) : SQL Connection attempt timed out~ SQL Error: [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'XXXX\ABBC$'.~*~*
*~*~SQL Connection attempt timed out [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'XXXX\ABBC$'.~*~*
<*><*> CANT CONNECT TO SQL, RETURNING ERROR <*><*>
Regards
Leela

Duplicate post.
https://social.technet.microsoft.com/Forums/en-US/6b26502b-ac07-426c-abe4-6cfdaa45b33b/sccm-console-launch-fails-sql-connectivity-issue-with-sccm-machine-account?forum=configmanagergeneral
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'

Hi,
We have exadata x3-2. I am seeing this error in alert log file frequently.
The db version: 11.2.0.3 On RAC on Linux 5.8 x86-64Bit
Errors in file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc:
ORA-01017: invalid username/password; logon denied
[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
ORA-02063: preceding 2 lines from HIS_CUST
The file /d01/oracle/TEST/11.2.0/admin/TEST1_dbtest/diag/rdbms/prod/TEST1/trace/TEST1_reco_11909.trc
Contains many repeated lines like below
*** 2015-01-21 06:34:40.209
ERROR, tran=21.24.51311, session#=1, ose=0:
ORA-01017: invalid username/password; logon denied
[Oracle][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed for user 'RECOVER'. {28000,NativeErr = 18456}
ORA-02063: preceding 2 lines from HIS_CUST
Could any please help why is this happening.
Thanks

Hi,
You have customers who are running distributed transactions using a gateway which need to be rolled back. However, the gateway has not been correctly configured for distributed transactions. To roll back a transaction on the SQL*Server database a connection is made as the user defined in the parameter HS_FDS_RECOVERY_ACCOUNT in the gateway init<sid>.ora file but this user has not been created in the SQL*Server database with the password defined in HS_FDS_RECOVERY_PWD. This user also needs to own the transaction log table.
I assume you are using the Database Gateway for SQL*Server (DG4MSQL) as the Database Gateway for ODBC (DG4ODBC) doesn't support distributed transaction.
If you have access to My Oracle Support have a look at this note -
How to Setup DG4MSQL to Use Distributed Transactions (Doc ID 227011.1)
Otherwise, check the Gateway documentation.
Regards,
Mike

Connection verification failed for data source using mySQL

Hi,
I having problem with mySQL datasource and getting the above error. This is only happening in our staging server. We are using ColdFusion 8 running JRUN4 and trying to connect to mySQL v 5.1.41. I tried adding DSN from my localhost using ColdFusion 9 developer edition and I am able to connect without error.I know that mysql server, username & password is valid. I can access the mysql also using mySQL gui tool from different pc and it works fine. I'm believe that this has something to do with mySQL driver? Can somebody shed some light on how can I fix my DSN connection problem? Thank you.
here's the error:
Connection verification failed for data source: forum
com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** java.net.ConnectException MESSAGE: Connection timed out: connect STACKTRACE: java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at java.net.Socket.(Socket.java:366) at java.net.Socket.(Socket.java:208) at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:173) at com.mysql.jdbc.MysqlIO.(MysqlIO.java:267) at com.mysql.jdbc.Connection.createNewIO(Connection.java:2739) at com.mysql.jdbc.Connection.(Connection.java:1553) at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266) at coldfusion.server.j2ee.sql.pool.JDBCPool.createPhysicalConnection(JDBCPool.java:589) at coldfusion.server.j2ee.sql.pool.ConnectionRunner$RunnableConnection.run(ConnectionRunner. java:67) at java.lang.Thread.run(Thread.java:619) ** END NESTED EXCEPTION ** Last packet sent to the server was 0 ms ago.

http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=6ef0253
HTH
Tim Carley
www.recfusion.com
[email protected]

Connection verification failed for data source:

Hi,
I having problem with mySQL datasource and getting the above error. This is only happening in our staging server. We are using ColdFusion 8 running JRUN4 and trying to connect to mySQL v 5.1.41. I tried adding DSN from my localhost using ColdFusion 9 developer edition and I am able to connect without error.I know that mysql server, username & password is valid. I can access the mysql also using mySQL gui tool from different pc and it works fine. I'm believe that this has something to do with mySQL driver? Can somebody shed some light on how can I fix my DSN connection problem? Thank you.
here's the error:
Connection verification failed for data source: forum
com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** java.net.ConnectException MESSAGE: Connection timed out: connect STACKTRACE: java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at java.net.Socket.(Socket.java:366) at java.net.Socket.(Socket.java:208) at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:173) at com.mysql.jdbc.MysqlIO.(MysqlIO.java:267) at com.mysql.jdbc.Connection.createNewIO(Connection.java:2739) at com.mysql.jdbc.Connection.(Connection.java:1553) at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:266) at coldfusion.server.j2ee.sql.pool.JDBCPool.createPhysicalConnection(JDBCPool.java :589) at coldfusion.server.j2ee.sql.pool.ConnectionRunner$RunnableConnection.run(Connect ionRunner.java:67) at java.lang.Thread.run(Thread.java:619) ** END NESTED EXCEPTION ** Last packet sent to the server was 0 ms ago.

Also make sure your firewall has the required port open (1433
default) and if you are running 2003 on the SQL box, especially if
you ran the security Wizard, make sure the IPSec is allowing the CF
box to communicate with it, and vise verse.

Error in OFR : "No database connection string set for connection group"

Hi all..
In OFR, Batches Fail To Export When Line Pairing is Enabled and Batch Remains in State 750 With Error "No database connection string set for connection group".
I have followed all steps associated to line pairing with database still my batch is not exported..
Any help is appreciated..
Thanks in advance

Hi,
in case you haven't done this already: for this problem we'd really need you to open a CSS message.
From your problem description it sounds likely that LCA routines and liveCache user don't fit together. Please check the solution of note 811207 to see if that assumption is correct.
Furthermore: liveCache 7.5 and SCM 4.0 are not released together (yet). When using SCM 4.0 only liveCache versions 7.4.03 Build XX are released. This it seems you're current combination is not supported!
Please take a look at PAM (Produkt Availability Matrix) on the SAP Service Marketplace to see which combinations have been released.
Kind regards,
Roland
Message was edited by: Roland Mallmann

Connection verification failed for data source on port 1433

Trying to set up a DSN for a SQL Server database on a new computer and it's failing every time.
Connection verification failed for data source: csf
java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]Error establishing socket to host and port: SANDYPC:1433. Reason: Connection refused: connect
The root cause was that: java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]Error establishing socket to host and port: SANDYPC:1433. Reason: Connection refused: connect
Now, when I installed CF 11, it installed on port 8500. However, when I try changing the port in the setup to 8500, I get this error:
Connection verification failed for data source: csf
java.sql.SQLException: Timed out trying to establish connection
The root cause was that: java.sql.SQLException: Timed out trying to establish connection
I cannot find anything online on how to fix this! HELP!!!

Hi,
Is that SQL Express edition? If so perhaps TCP protocol is not enabled. Is Windows firewall turned on? Check port 1433 is open.
Normally you would not create a datasource to apache port 8500, that is a web server not database server port.
HTH, Carl.

SCOM 2012 - SQL Connection strings

Hey SCOM gurus
Wonder if you can help?
I need to change my SCOM 2012 Management Server 'SQL Connection strings' to use a load balancer dns name of 'sql-listener'. Can anyone suggest how this might be done? (basically we now have a SQL 2014 Cluster in the background).
thanks
Karen

Hello,
You must change the database name in the registry, more information : https://technet.microsoft.com/en-us/library/hh278848.aspx?f=255&MSPPError=-2147217396

TCP connectivity check failed for subnet

hi
im trying to add a node to my 11.2 grid infrastructure and the cluster verification is returning error
Check: TCP connectivity of subnet "152.15.123.0"
Source Destination Connected?
inode2:127.0.0.1 inode2:152.15.123.4 failed
Result: TCP connectivity check failed for subnet "152.15.123.0"
this happens when i run cluvfy with pre nodeadd option, there is no other failure ...
any idea what it could be ?

Hello Buddy,
Please note that inode2:127.0.0.1 is using loopback IP, please check your network configuration and retry the cluvfy operation.
Cheers,
Rodrigo Mufalani
www.mufalani.com.br/blog

RAC - Cluvfy - TCP connectivity check failed for subnet

Hi ...this is Oracle RAC 10.2.0.4.0 .. has anyone witnessed this check failure or is able to comment on how I should debug the same
./runcluvfy.sh stage -post hwos -n all -verbose
Check: TCP connectivity of subnet "172.30.182.0"
Source Destination Connected?
sekiazu0230:172.30.182.67 sekiazu0231:172.30.182.68 failed
sekiazu0230:172.30.182.67 sekiazu0231:172.30.182.68 failed
Result: TCP connectivity check failed for subnet "172.30.182.0"
Interface information for node "sekiazu0230"
Name IP Address Subnet Gateway Def. Gateway HW Address MTU
en0 172.30.182.67 172.30.182.0 172.30.182.67 172.30.182.1 1E:40:3D:1C:96:02 1500
en0 172.30.182.67 172.30.182.0 172.30.182.67 172.30.182.1 1E:40:3D:1C:96:02 1500 ===> Duplicated ?
en1 172.30.190.48 172.30.190.0 172.30.190.48 172.30.182.1 1E:40:3D:1C:96:03 1500
en2 10.252.34.9 10.252.34.0 10.252.34.9 172.30.182.1 1E:40:3D:1C:96:04 65390
Thank you for all feedback
Steve

Hello Buddy,
Please note that inode2:127.0.0.1 is using loopback IP, please check your network configuration and retry the cluvfy operation.
Cheers,
Rodrigo Mufalani
www.mufalani.com.br/blog

Java.sql.SQLException: Login failed for user 'ccms'.

Windows Server 2003 R2 Enterprise x64 Edition service pack 1
SQL Server 2000 Enterprise edition 32 bit, SP4 : 2000.8.00.2039
jdbc driver: jtds
connection string: jdbc:jtdsqlserver://ZH-DATA-4:1434/[dbname];instance=[instance name]
the connectivity works fine...almost.
I have 2 identical sql servers one of which is linked to the other via a linked server config which for one particular query gives back the error I give in the subject of this thread:
java.sql.SQLException: Could not get the data of the row from the OLE DB provider 'SQLOLEDB'
if I run the exact same sql string in query analyser it runs with no problem.
if have similar queries also running from java which use the linked server and these do not give an error. I am at a loss as to explain why this is happening.
the query in question joins together a number of views which reference the linked server.
I have tried everything I can think of including recreating the views and linked server definition.
If all is OK in query analyser, how can it fail when called over jbdc (especially when all other db requests succeed) ?

refer below link
http://blog.soapplied.com/2013/06/websphere-distributed-transactions-with.html

How to create SQL Connections String using JSP

Hi, Dear I wrote sample Jsp program(Create a table and Inserted to Table) using SQLConnection
I got this Error, how to rectify please help me?
This is my Connection String
<%
String driver = "com.microsoft.sqlserver.jdbc.SQLServerDriver";
     Class.forName(driver).newInstance();
     Connection con=null;
     ResultSet rst=null;
     Statement stmt=null;
     try
          String url=java.sql.DriverManager.getConnection("jdbc:sqlserver://10.1.5.6:1433;Database=manickaraj;User=sa; Password=test*");
          con=DriverManager.getConnection(url);
          stmt=con.createStatement();
     catch(Exception e)
System.out.println(e.getMessage());
     if(request.getParameter("action") != null)
          String CategoryName=request.getParameter("Category1");
          String Description=request.getParameter("Description1");
String Status=request.getParameter("Status1");
          stmt.executeUpdate("insert into Category(CategoryName,Description) values('"+CategoryName+"','"+Description+"','"+Status+"')");
          rst=stmt.executeQuery("select * from Category");
%>
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: 5 in the jsp file: /CategoryAction.jsp
Generated servlet error:
C:\Documents and Settings\manickaraj\.netbeans\5.5\apache-tomcat-5.5.17_base\work\Catalina\localhost\SampleJsp\org\apache\jsp\CategoryAction_jsp.java:61: incompatible types
found : java.sql.Connection
required: java.lang.String
An error occurred at line: 5 in the jsp file: /CategoryAction.jsp
Generated servlet error:
          String url=java.sql.DriverManager.getConnection("jdbc:sqlserver://10.1.2.4:1433;Database=manickaraj;User=sa; Password=test*");
          ^
1 error
     org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
     org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)
     org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
     org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:368)

package shop;
import java.sql.*;
import java.sql.Connection;
import java.sql.SQLException;
import java.sql.Statement;
import javax.naming.InitialContext;
import javax.sql.DataSource;
public class DAClass {
     private static Connection conn;
     private static ResultSet rs;
     private static PreparedStatement ps;
     public static void connect(String dsn, String un, String pwd) {
          try {
               //access or Mysql odbc connectivity
               //Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
               //conn=DriverManager.getConnection("jdbc:odbc:"+dsn,un,pwd);
               //mysql
               //Class.forName("com.mysql.jdbc.Driver");
               //conn=DriverManager.getConnection("jdbc:mysql://127.0.0.1:3306/eshop?user=root&password=root");
            InitialContext ctx = new InitialContext();
     DataSource ds = (DataSource) ctx.lookup("jdbc/eshop");
      conn = ds.getConnection();
     //DataSource ds = (DataSource)ctx.lookup("java:comp/env/jdbc/MySQLDB")
          catch(Exception e) {
               //return "not soory";
     public static boolean chkPwd(String un, String pwd) {
          try {
               boolean b=false;
               ps=conn.prepareStatement("select * from cust_info where cust_name=? and cust_pwd=?");
               ps.setString(1,un);
               ps.setString(2,pwd);
               rs=ps.executeQuery();
               while(rs.next()) {
                    b=true;
               return b;
          catch(Exception e) {
               return false;
}changed the code like this other part is same.implemented connection pooling but still its too lazy loding can you guide me?

SQLException thrown by the physical connection: Login failed for user

Hi Experts,
I am creating a custom data source on Visual Administrator (2004s 7.01 SP3) for SQL 2008 with a named instance. Using Logon, System databases are getting connected. But Visual Administrator throws the below exception trace while attempting to connect to any custom created databases.
Please help me to resolve this.
Thanks in Advance,
Nikhil

java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during runtime changes of application "sap.com/JDBCConnector_QIDB.xml". [id = ConfigError]
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:705)
     at sun.reflect.GeneratedMethodAccessor647.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.rmi.RemoteException: Error occurred while making runtime changes with application sap.com/JDBCConnector_QIDB.xml; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 3640850:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot start DataSource "QIDB".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1549)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1825)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.application.RuntimeTransaction.finalActions(RuntimeTransaction.java:286)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:339)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.makeRuntimeChanges(DeployCommunicatorImpl.java:344)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:685)
     at sun.reflect.GeneratedMethodAccessor647.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'xxxx'.
     at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:193)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.init(ConnectionHashSet.java:168)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.<init>(ConnectionHashSet.java:134)
     at com.sap.engine.services.connector.jca.AdapterCache.open(AdapterCache.java:294)
     at com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:316)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1540)
     ... 40 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user 'xxxx'.
     at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
     at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(Unknown Source)
     at com.microsoft.sqlserver.jdbc.TDSParser.parse(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(Unknown Source)
     at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
     at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:163)
     ... 45 more
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.makeRuntimeChanges(DeployCommunicatorImpl.java:346)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:685)
     ... 28 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 3640850:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot start DataSource "QIDB".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1549)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1825)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.application.RuntimeTransaction.finalActions(RuntimeTransaction.java:286)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:339)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.makeRuntimeChanges(DeployCommunicatorImpl.java:344)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.updateDataSourceApplication(DataSourceManagerImpl.java:685)
com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:316)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1540)
     ... 40 more

Sql Connection String Problem

Hi , hope you all are fine. I am new to JDBC. need to connect to MS SQL Server 2000 using JSP. i am having trouble in connection string. I have MS SQL Server 2000 installed on my Machine and for Login i am using Window Auth mode(not using username=sa etc) i am using Windows XP Proffessional. i have put these files in the lib folder of my application
msbase.jar
mssqlserver.jar
msutil.jar
Connection driver i am using is
Class.forName(
"com.microsoft.jdbc.sqlserver.SQLServerDriver");Please if u can help me in building connection String... Your help is always appriciated.
regards
Adee

Hi , hope you all are fine. I am new to JDBC. need to
connect to MS SQL Server 2000 using JSP. i am having
trouble in connection string. I have MS SQL Server
2000 installed on my Machine and for Login i am using
Window Auth mode(not using username=sa etc) i am
using Windows XP Proffessional. i have put these
files in the lib folder of my application
msbase.jar
mssqlserver.jar
msutil.jarExcellent.
Connection driver i am using is
Class.forName(
com.microsoft.jdbc.sqlserver.SQLServerDriver");Please if u can help me in building connection
String... Your help is always appriciated.
regards
AdeeRead this:
http://support.microsoft.com/kb/313100
%

SQl Server Installation failing for Database Engine and Its Services

Hi,
I was trying to install SQL SERVER 2008 R2 on VM having 500 GB hard disk and 16 GB RAM.
OS is Windows Server 2008
But it fails for Database Engine.
Installation Details are as Below.
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068119551
Exit facility code: 1211
Exit error code: 1
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2014-10-13 18:41:01
End time: 2014-10-13 19:26:32
Requested action: Install
Log with failure: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0x476BF04A%400xBB814387
Machine Properties:
Machine name: KVS-IN-WFAN092
Machine processor count: 4
OS version: Windows Server 2008 R2
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: di-softwareSoftwaresSQLSQL_2008_R2_Enterprisex64setup
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITYNETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CONFIGURATIONFILE: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITYLOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server
INSTALLSHAREDWOWDIR: C:Program Files (x86)Microsoft SQL Server
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:Program FilesMicrosoft SQL Server
INSTANCEID: SQLServer
INSTANCENAME: SQLSERVER
ISSVCACCOUNT: NT AUTHORITYNetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITYNETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: KRONOSENGsuperuser
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20141013_183354SystemConfigurationCheck_Report.htm
And Error in log file are maily as below.
2014-10-13 19:26:27 Slp: Completed Action: SqlBrowserConfigAction_install_Startup_Cpu32, returned True
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11
dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "SqlBrowserConfigEngAction_install_Startup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: SqlBrowserConfigEngAction_install_Startup_Cpu64 The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested
for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "SqlEngineConfigAction_install_startup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: SqlEngineConfigAction_install_startup_Cpu64 The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 11 dependant features. The feature is tested
for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_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-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "AgentInstall_AgentInstallStartup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: AgentInstall_AgentInstallStartup_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-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_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-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_Startup_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_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-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "FulltextConfigAction_install_startup_Cpu64" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: FulltextConfigAction_install_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-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There
are 11 dependant features. The feature is tested for results: ValidateResult, Result." did not pass as it returned false and true was expected.
2014-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Install_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-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu64_Install_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-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Action "ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_StartupFinalize_postmsi" will return false due to the following conditions:
2014-10-13 19:26:27 Slp: Condition "Feature dependency condition for action: ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_Install_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-10-13 19:26:27 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result
2014-10-13 19:26:27 Slp: Completed Action: PostMsiTimingConfigAction, returned True
2014-10-13 19:26:27 Slp: Completed Action: ExecuteStandardTimingsWorkflow, returned True
2014-10-13 19:26:27 Slp: ----------------------------------------------------------------------
2014-10-13 19:26:27 Slp: Running Action: ExecuteExtendedTimingsWorkflow
Thanks,
Mahesh

I have uploaded detail.txt at below url.
http://m.uploadedit.com/b041/1413264342685.txt
Hi Mahesh,
According to log file, I find the message ‘The setup100.exe.config file was not found, therefore the DTSWizard and SQLWatson app config files were not replaced’. It seems that the SQL Server setup file is not complete. Please check that if the SQL Server
setup file is corrupted, if it is corrupted, please download it again and reinstall SQL Server 2008 R2.
However, if there’s no problem with the setup file, please check that if there is third-party software such as anti-virus software on your computer blocking the process of SQL Server installation. In addition, make sure that you choose ‘Run as administrator’
to launch the setup and configure SQL Server service accounts appropriately with administrator permission during the installation.
For more details about this error, please review the following similar thread.
http://answers.flyppdevportal.com/categories/sqlserver/sqlsetupandupgrade.aspx?ID=ad794a97-09ae-4aae-9d68-0b06f9af3e16
Thanks,
Lydia Zhang

SQL connection string failed for $ password

Similar Messages

Maybe you are looking for