cancel
Showing results for 
Search instead for 
Did you mean: 

Dispatcher test failing - object not found

Former Member
0 Kudos

Hi all,

Just installed IdM 7.2 and patched all components including DB schema to SP09.

Env: Windows Server 2012 / MS SQL Server 2012 / NW 7.4 for UI

Using SAPJVM (64-bit) and pointing to sqljdbc4.jar. DB connection test is good.

Created a new Dispatcher and while testing, I see this error (MxDispatcherPrelog_Prelog.log):

[12.08.2014 04:40:05-162] - INFO - Prelog - First prelog line

[12.08.2014 04:40:11-164] - INFO - Prelog - Initialization done

[12.08.2014 04:40:11-164] - INFO - Prelog - Full dispatcher identifier:idm_dispatcher_01@<Server>/<IP>:1407843611164:394746

[12.08.2014 04:40:11-237] - INFO - Prelog - Dispatcher identifier prefix:idm_dispatcher_01@<Server>/<IP>

[12.08.2014 04:40:11-266] - TRACE - Prelog - Executing: GET_DISPATCHER #FieldsToReturn:null #Params:[idm_dispatcher_01] #InClause:[idm_dispatcher_01] #OrderBy:null

[12.08.2014 04:40:11-267] - DEBUG - Prelog - STATEMENT PREPARED: SELECT * FROM MC_DISPATCHER  WITH (NOLOCK)  WHERE MACHINE=?  PARAMETERS: idm_dispatcher_01

[12.08.2014 04:40:11-339] - TRACE - Prelog - Succesfull execution: GET_DISPATCHER

[12.08.2014 04:40:11-362] - FATAL - Prelog - Preparing dispatcher failed: Object not found

Error in console:

Running MxDispatcher_idm_dispatcher_01.

MxDispatcher version: 7.2.9.3 Built: 25.06.2014 15:26:15 (c) Copyright 2008 SAP

AG. All rights reserved.

Java VM: Sun Microsystems Inc.   Version: 1.6.0_17

Java home: C:\Program Files\Java\jre6

Java lib/ext: C:\Program Files\Java\jre6\lib\ext;C:\Windows\Sun\Java\lib\ext

CLASSPATH: C:\usr\sap\IdM\Identity Center\Java\mxdispatcher.jar;C:\Program Files

\Microsoft JDBC Driver 4.0 for SQL Server\sqljdbc_4.0\enu\sqljdbc4.jar;C:\Progra

m Files\Microsoft JDBC Driver 4.0 for SQL Server\sqljdbc_4.0\enu\sqljdbc4.jar

[12.08.2014 04:29:35-964] - Reading Db Info - STATEMENT PREPARED: SELECT INFOVALUE FROM MC_DBINFO where INFONAME='TYPENUM'

Full dispatcher identifier:idm_dispatcher_01@<Server>/<IP>:1407842978108:518063

Dispatcher identifier prefix:idm_dispatcher_01@<Server>/<IP>

com.sap.idm.db.exceptions.IdMDbException: Object not found

        at com.sap.idm.db.objutil.exec.MxObjectQueryExecUtil.get(MxObjectQueryExecUtil.java:69)

        at com.sap.idm.db.objutil.table.DispatcherUtil.get(DispatcherUtil.java:48)

        at com.sap.idm.db.objutil.table.DispatcherUtil.get(DispatcherUtil.java:36)

        at com.sap.idm.ic.services.dispatcher.MxDispatcher_DBCommonFacade.getDispatcher(MxDispatcher_DBCommonFacade.java:282)

        at com.sap.idm.ic.services.dispatcher.MxDispatcher.main(MxDispatcher.java:290)

Preparing dispatcher failed: Object not found

C:\Windows\system32>

Any ideas?

Regards,

Vivek

Accepted Solutions (1)

Accepted Solutions (1)

former_member2987
Active Contributor
0 Kudos

Hi Vivek,

I guess I'd do the standard tests:

1. Run time installed? Does it match the designtime version?

2. Did you define the driver in the MMC console?

3. Did you regenerate the dispatcher scripts?

If none of that is working, check to make sure the database is up and check the dispatcher's PROP file and make sure all paths are correct.

Matt

Former Member
0 Kudos

Thank you, Matt.

Yes, all the three mentioned tasks/ checks are done and good. Database is up. The SQL statements that you see in the logfile return results from the SQL tester of the console.

The PROP file seems to be good. From the contents below, is there anything obvious that I need to be concerned?

DISPATCHER_NAME=idm_dispatcher_01

MC_JDBCDRIVER=com.microsoft.sqlserver.jdbc.SQLServerDriver

MC_JDBCURL={DES3CBC}1:963076a2b6f4d07c-<encrypted_string>...

DSECLASSPATH=%DSE_HOME%/Java/DSE.jar:%DSE_HOME%/Java:%DSE_HOME%/Java/sapjco.jar:%DSE_HOME%/Java/sapjco3.jar:C:\\Program Files\\Microsoft JDBC Driver 4.0 for SQL Server\\sqljdbc_4.0\\enu\\sqljdbc4.jar

JDBCDRIVERS=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

DISP_CONN_STR_CHARSET=UTF-8

Regards,

Vivek

Former Member
0 Kudos

An update.. after replacing the encrypted string in the prop file with cleartext JDBC URL, the issue seems to be resolved.

Regards,

Vivek

former_member2987
Active Contributor
0 Kudos

Vivek,

Check your Keys.ini and make sure it's the same between your designtime system and your runtime system if they are on different servers.

Matt

Former Member
0 Kudos

Hi Matt,

They are on the same server/ folder.

Regards,

Vivek

former_member2987
Active Contributor
0 Kudos

Vivek,

Is keys.ini defined in netweaver?

Matt

Former Member
0 Kudos

Hi Matt,

The issue was that the SAPJVM was missing unrestricted jurisdiction (JCE) files. Once it was taken care of, encryption is looking good.

Regards,

Vivek Janardhan

former_member2987
Active Contributor
0 Kudos

Excellent news, Vivek!  Please mark your answer as correct so people will be able to learn from this in the future!

Regards,

Matt

Answers (0)