on 02-23-2011 11:29 PM
Hi Guys, I am facing below issue when importing SAP Provisioning Framework in IDM. Please help!
23.02.2011 17:00:20 :I:Parsing arguments to syncutility
23.02.2011 17:00:20 :D:Operation type is IMPORT_TO_ROOT
23.02.2011 17:00:20 :D:Loading driver com.microsoft.jdbc.sqlserver.SQLServerDriver;com.microsoft.sqlserver.jdbc.SQLServerDriver;com.sap.dbtech.jdbc.DriverSapDB;org.gjt.mm.mysql.Driver;sun.jdbc.odbc.JdbcOdbcDriver;oracle.jdbc.driver.OracleDriver;COM.ibm.db2.jdbc.app.DB2Driver;COM.ibm.db2.jcc.DB2Driver;COM.ibm.db2.jdbc.net.DB2Driver
23.02.2011 17:00:20 :X:Found items in classpath:
23.02.2011 17:00:20 :X:- ".
23.02.2011 17:00:20 :X:-
23.02.2011 17:00:20 :X:- C:\Program Files (x86)\SAP\IdM\Identity Center\Java\imXport.jar
23.02.2011 17:00:20 :X:- C:\Program Files (x86)\SAP\IdM\Identity Center\Java\jh.jar
23.02.2011 17:00:20 :X:- C:\Program Files (x86)\SAP\IdM\Identity Center\Java\MIC-impexp.jar
23.02.2011 17:00:20 :X:- C:\Program Files (x86)\SAP\IdM\Identity Center\Java\xerces.jar
23.02.2011 17:00:20 :X:- C:\Program Files (x86)\SAP\IdM\Identity Center\Java\xalan.jar
23.02.2011 17:00:20 :X:- C:\Program Files (x86)\SAP\IdM\Identity Center\Java\xml-apis.jar
23.02.2011 17:00:20 :X:- C:\Program Files\Microsoft SQL Server 2005 JDBC Driver\sqljdbc_1.2\enu\sqljdbc.jar"
23.02.2011 17:00:20 :W:Failed loading class com.microsoft.jdbc.sqlserver.SQLServerDriver
23.02.2011 17:00:20 :D:Loaded JDBC Driver class: com.microsoft.sqlserver.jdbc.SQLServerDriver Version: 1.2
23.02.2011 17:00:20 :W:Failed loading class com.sap.dbtech.jdbc.DriverSapDB
23.02.2011 17:00:20 :W:Failed loading class org.gjt.mm.mysql.Driver
23.02.2011 17:00:20 :D:Loaded JDBC Driver class: sun.jdbc.odbc.JdbcOdbcDriver Version: 2.1
23.02.2011 17:00:20 :W:Failed loading class oracle.jdbc.driver.OracleDriver
23.02.2011 17:00:20 :W:Failed loading class COM.ibm.db2.jdbc.app.DB2Driver
23.02.2011 17:00:20 :W:Failed loading class COM.ibm.db2.jcc.DB2Driver
23.02.2011 17:00:20 :W:Failed loading class COM.ibm.db2.jdbc.net.DB2Driver
23.02.2011 17:00:20 :I:Creating connection to jdbc:sqlserver://wfmdeim01d:1433;databasename=mxmc_db;user=SPRINGSWF\imdadm;password==SQLNCLI10.1
23.02.2011 17:00:21 :I:Could not create connection to the database jdbc:sqlserver://wfmdeim01d:1433;databasename=mxmc_db;user=SPRINGSWF\imdadm;password==SQLNCLI10.1
23.02.2011 17:00:21 :X:Initialized log for com.sap.idm.ic.syncutil.utilities.ShowLogFileDlg. Log level is eXtended
thanks guys for pointing me in right direction. My issue was resolved by changing the string with updated password.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
regarding to the two following lines of the log, I have question:
23.02.2011 17:00:20 :I:Creating connection to jdbc:sqlserver://wfmdeim01d:1433;databasename=mxmc_db;user=SPRINGSWF\imdadm;password==SQLNCLI10.1
23.02.2011 17:00:21 :I:Could not create connection to the database jdbc:sqlserver://wfmdeim01d:1433;databasename=mxmc_db;user=SPRINGSWF\imdadm;password==SQLNCLI10.1
Why are you using user "imdadm" to access the database mxmc_db?
Have you tried to access with mxmc_rt (or one of the other special IDM-User) and the adequate password.
Kind regards,
Achim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Matt Pollicove: We are getting the same error message as well. We did point it to the right java and still the same, using MSSQL 2008 R2 Enterprise, using dynamic ports, JDBC 3, installing IDM 7.2 with AS JAVA 7.0
We checked the connection in the database and it is establishing, maybe you could help us where else to look.
Thanks
Tin
That's the problem Matt, the DB Administrator can't provide us the Dynamic ports. It is said that there is no dynamic port assigned and can't be given to us. The MSSQL Server is centrally managed. Do you think it is something to do with the dynamic ports?
We haven't tested the IDM UI interface yet, as there is no host:50000/idm, the applications are mounted on the portal.
Fahran,
I'm going to make a guess here and that the imdadm user referenced in the JDBC connection string matches up to mxmc_admin rather than mxmc_rt. I'm also going to assume that you're using MS SQL.
I recently had this issue myself and fixed it by making a change in the classpath in the MMC options. Please check this blog post (from yesterday!) that addresses it.
If the order of the JAR files does not apply, check to make sure you're using the 1.2 version of the jdbc driver.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.