cancel
Showing results for 
Search instead for 
Did you mean: 

JDBCConnector_IDM_DataSource.xml failed to start

Former Member
0 Kudos

Hi Everyone,

I am trying to install Identity Management 7.1 on Composition Environment 7.2 (i.e. AS Java 7.2), where the O/S is Windows Server 2003 x64 R2 SP2 and the Database is MS SQL 2008. During the step where I am setting up the JDBC connection to the JMX layer, I am running into an issue with JDBC Custom DataSource. That is, once I enter the connection settings, NWA tells me that JDBCConnector_IDM_DataSource.xml fails to start.

Here's what I've done so far:

1. Looked at where NWA deployed the JDBC driver (version 3.0 since we are using AS Java 7.2 - SAP Note 639702), found that no file existed at the location (E:\usr\sap\<SID>\J00\j2ee\cluster\server0\.\temp\dbpool\_IdMSQL2008\sqljdbc.jar), and then copied the .jar file to the new location.

2. Restarted the instance, deleted the DataSource, and recreated it using the same settings as before.

3. Created a new Identity Center Configuration in Identity Center and had no problems during the connection tests.

4. Confirmed that the Data Source is labeled "IDM_DataSource"

All I have to work with in the Logs is the following error details:

SAP Logs:

Global operation [com.sap.engine.services.deploy.server.TransactionStatistics@44247d17] over [startApp] [application] finished with errors for [sap.com/JDBCConnector_IDM_DataSource.xml]ms on server [15]

server_00.log:

#2.0 #2010 10 04 15:14:53:885#0-400#Error#/System/Server/Services/Deploy#

com.sap.ASJ.dpl_ds.002038##sap.com/JDBCConnector_IDM_DataSource.xml#001E4F2F141C00D80000000900000DFC#7930950000000004#sap.com/tclmitsamuimainframe~wd#com.sap.engine.services.deploy#Administrator#2##8CAC4B45CFEB11DF90BE000000790446#80f9d296cfeb11dfcdc8000000790446#80f9d296cfeb11dfcdc8000000790446#0#Deploy Start Application Thread#Plain#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle#Global operation [com.sap.engine.services.deploy.server.TransactionStatistics@d39e6d1] over [startApp] [application] finished with errors for [sap.com/JDBCConnector_IDM_DataSource.xml]ms on server [15]#

#2.0 #2010 10 04 15:14:53:885#0-400#Error#/System/Server/Services/Deploy#com.sap.ASJ.dpl_ds.006362#BC-JAS-

DPL#deploy#001E4F2F141C00D80000000B00000DFC#7930950000000004#sap.com/tclmitsamuimainframe~wd#com.sap.engine.services.deploy#Administrator#2##8CAC4B45CFEB11DF90BE000000790446#80f9d296cfeb11dfcdc8000000790446#80f9d296cfeb11dfcdc8000000790446#0#Deploy Start Application Thread#Plain#com.sap.engine.services.monitor.mbeans.MonitorResourceBundle#Exception in application start or stop on remote node#

I'm not sure what else I can do to troubleshoot at this point. Does anyone know what I could have missed during the installation?

Accepted Solutions (1)

Accepted Solutions (1)

former_member2987
Active Contributor
0 Kudos

Douglas,

Two things come immediately to mind.

1. Is MSSQL 2008 in the PAM?

2. Are you using the correct drivers?

Hope this helps,

Matt

Answers (2)

Answers (2)

Former Member
0 Kudos

Matt,

I thought a bit about #2 and tried something else.Going back to SAP Note 639702, there is a tool called SAPCheckVersion.zip that you can extract to the directory containing sqljdbc.jar. When I run it with the driver that I downloaded from Microsoft, it gives me the following error:

E:\usr\sap\<SID>\SYS\exe\uc\NTAMD64\mssjdbc>SAPCheckVersion.cmd <hostname> sa <password>

-


Server : <hostname>

User : sa

Password : <password>

Exception in thread "main" java.lang.UnsupportedClassVersionError: com/microsoft

/sqlserver/jdbc/SQLServerDriver (Unsupported major.minor version 49.0)

at java.lang.ClassLoader.defineClass0(Native Method)

at java.lang.ClassLoader.defineClass(ClassLoader.java:539)

at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12

3)

at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)

at java.net.URLClassLoader.access$100(URLClassLoader.java:55)

at java.net.URLClassLoader$1.run(URLClassLoader.java:194)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(URLClassLoader.java:187)

at java.lang.ClassLoader.loadClass(ClassLoader.java:289)

at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)

at java.lang.ClassLoader.loadClass(ClassLoader.java:235)

at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:141)

at SAPCheckVersion.main(SAPCheckVersion.java:80)

When I try the tool with the JDBC driver that was included with CE 7.2, I get the following response:

E:\usr\sap\<SID>\SYS\exe\uc\NTAMD64\mssjdbc>SAPCheckVersion.cmd <hostname> sa <password>

-


Server : <hostname>

User : sa

Password : <password>

-


Found Microsoft JDBC Driver.

Driver version is : 1.2.2828.215

JDBC version: 3.0

-


No DataDirect JDBC Driver found. com.sap.nwmss.jdbc.sqlserver.SQLServerDriver

Assuming that the one included with CE is a working version, I made a copy and recreated the JDBC driver using this version of sqljdbc.jar. After restarting the SAP instance (as a precaution), I was able to successfully create the Data Source. Now the IDM UI looks like this:

SAP NetWeaver Identity Management

Welcome Log Off

Could not find entry in the context Could not find entry in the context Could not find entry in the context

I think the issue is now resolved, but I'm going to give it a day in case any other issues come up. I'm still unclear as why the output of the tool says Driver version is 1.2 when the JDBC version is 3.0 as well.

Former Member
0 Kudos

Hi Matt, thanks for the reply!

1. Windows 2K3 x64 + MS SQL Server 2K8 x64 has been on the PAM since 14.06.2010.

2. Are you referring to the JDBC driver? If yes, then I followed SAP Note 639702 and used the suggested driver (3.0) for releases based on SAP NetWeaver 7.20 and higher. If not, which driver are you referring to?

On a note related to #2, I have also copied the driver (sqljdbc.jar) to usr\sap\<SID>\SYS\exe\UC\NTAMD64\mssjdbc and tried to add the Data Source again after restarting the SAP instance. Same error.