cancel
Showing results for 
Search instead for 
Did you mean: 

VDS not starting - SP5

Former Member
0 Kudos

Dear board,

after doing the installation of SP5 for VDS I was creating a configuration file for the HCM LDAP EXTRACT to IDM. When I start the server, the following error log is coming up.

erifying ACL configuration

Verifying joined group configuration

Verifying dynamic add group configuration

Verifying unlinked group configuration

Verifying provisioning group configuration

Verifying load balacing group configuration

Verifying failover group configuration

Verifying data sources configuration

Verifying forest configuration

Verifying Keystore configuration

Verifying LDAP deployments configuration

Verifying WS deployments configuration

Verifying rule configuration

Verifying method configuration

Verifying usergroups configuration

Verifying user configuration

Verifying cache configuration

Verifying event triggers

Verifying request queue configuration

Verifying proxy configuration

-


Starting server -


Failed starting server:

Exception starting Application - java.io.IOException: CreateProcess: C:\j2sdk1.4.2_19\jre\bin\java.exe -cp "C:\Program Files (x86)\SAP\IdM\Virtual Directory Server\lib\mvd.jar;C:\Program Files\Microsoft SQL Server 2005 JDBC Driver\sqljdbc.jar;C:\Program Files (x86)\SAP\IdM\Identity Center\Java;D:\NW IDM 7.1\opensaml-2.3.1-bin\opensaml-2.3.1\lib;D:\NW IDM 7.1\javamail-1.4.3\javamail-1.4.3\lib;D:\NW IDM 7.1\JNDI\jndi-1_2_1\lib;C:\Program Files (x86)\SAP\IdM\Virtual Directory Server\externals;C:\Program Files (x86)\SAP\IdM\Virtual Directory Server\lib\vdstools.jar;C:\Program Files (x86)\SAP\IdM\Virtual Directory Server\lib\vdsverifier.jar" "-DMX_SERVER_HOME=C:\Program Files (x86)\SAP\IdM\Virtual Directory Server" com.sap.idm.vds.MVDServer "C:\Program Files (x86)\SAP\IdM\Virtual Directory Server\configurations\HCM LDAP EXTRACT for IDM\HCM LDAP EXTRACT for IDM.xml" error=3

My research brought indications, that the path is not correctly identified. Looking for ideas what to check?

Kind regards and many thanks in advance,

R.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello,

The thing is SAP removed MxIDStoreRootDSEClass in SP5 and merged all the changes done in that class to the class MxRootDSEClass.

As the HCM extract template hasn't been changed, it has to be changed manually :

Double-click on 'Virtual Directory Server', the top line in the left pane, select the tab 'Classes' and set Root DSE Class to 'MxRootDSEClass' instead of 'MxIDStoreRootDSEClass'.

Save your configuration, update or start your VDS server and it should work !

Regards,

Hervé Montagnier.

sasi_reddy7
Participant
0 Kudos

Hi R H

Please award points to Hervé Montagnier and mark this thread as Answered since the suggestion by Hervé Montagnier solves this problem.

Thanks

Sasi

Former Member
0 Kudos

HI Herve,

you were totally correct, problem solved.

Kind regards,

R.H.

Former Member
0 Kudos

Thanks Hervé! You made my day!

BR

Michael

Answers (1)

Answers (1)

Former Member
0 Kudos

Did you install a 64bit software on a 32 bit processor?

Did you install javaruntime after the install of SAP IDM?

what is the sequence of your installation?

Make sure to have all parts of the presentation, application, database at recommended version/sp levels

especially the version of database and runtime environment.

Former Member
0 Kudos

Hi Franklin,

I am operating on a Windows Server 2003 x64 with SQL Server 2005, where both IDC, VDS and DB are on SP5. The Java runtime was installed before I installed VDS.

What can I do?

Kind regards,

R

Former Member
0 Kudos

check this note 1451454

where did you download the JDBC driver and what is the CLASSPATH for it

like default location ...
sqljdbc_1.2\enu\sqljdbc.jar

Also what is the path to

java.exe, JVM.dll, jdbc driver jar & JDBC driver names?

Edited by: Franklin Jayasim on Jul 21, 2010 8:50 PM

Former Member
0 Kudos

Hi Franklin,

thanks again for your message. Which section of the SAP note are you especially refering to?

I have downloaded the JDBC Drivers directly from Microsoft.com, the path is C:\Program Files\Microsoft SQL Server 2005 JDBC Driver\sqljdbc_1.2\enu\sqljdbc.jar. The path to the java.exe is C:\j2sdk1.4.2_17-x64\bin, jvm.dll is C:\j2sdk1.4.2_17-x64\jre\bin\server.

I don't know if I answered all of your questions.

Kind regards,

Richard

Former Member
0 Kudos

R.H,

I was looking at the "post configuration step" from the install guide

have you done that correctly.

Former Member
0 Kudos

Hi Franklin,

I followed the post installation tasks. In the meantime, I have pointed to a JVM my WebAS JAva is using on this system. The startup message changed. It looks like the JRE 1.4.2.17-x64 is not compatible....

Any idea?

R.

"C:\Program Files (x86)\Java\jre6\bin\java.exe" -cp "C:\Program Files (x86)\SAP\IdM\Virtual Directory Server\lib\mvd.jar;C:\Program Files (x86)\SAP\IdM\Identity Center\Java;D:\NW IDM 7.1\opensaml-2.3.1-bin\opensaml-2.3.1\lib;D:\NW IDM 7.1\javamail-1.4.3\javamail-1.4.3\lib;D:\NW IDM 7.1\JNDI\jndi-1_2_1\lib;C:\j2sdk1.4.2_17-x64\bin;C:\j2sdk1.4.2_17-x64\jre\bin\server;C:\Program Files\Microsoft SQL Server 2005 JDBC Driver\sqljdbc_1.2\enu\sqljdbc.jar;D:\NW IDM 7.1\db-derby-10.6.1.0-bin\db-derby-10.6.1.0-bin\lib\derbyclient.jar;C:\Program Files (x86)\SAP\IdM\Virtual Directory Server\externals;C:\Program Files (x86)\SAP\IdM\Virtual Directory Server\lib\vdstools.jar;C:\Program Files (x86)\SAP\IdM\Virtual Directory Server\lib\vdsverifier.jar" "-DMX_SERVER_HOME=C:\Program Files (x86)\SAP\IdM\Virtual Directory Server" com.sap.idm.vds.MVDServer "C:\Program Files (x86)\SAP\IdM\Virtual Directory Server\configurations\HCM LDAP EXTRACT for IDM\HCM LDAP EXTRACT for IDM.xml"

MVDServer version: 7.10.SP05.Patch0-126425 - Rev:126425Copyright 2007 SAP AG. All rights reserved

Java VM: Sun Microsystems Inc. Version: 1.6.0_20

Java home: C:\Program Files (x86)\Java\jre6

Java lib/ext: C:\Program Files (x86)\Java\jre6\lib\ext;C:\WINDOWS\Sun\Java\lib\ext

CLASSPATH: C:\Program Files (x86)\SAP\IdM\Virtual Directory Server\lib\mvd.jar;C:\Program Files (x86)\SAP\IdM\Identity Center\Java;D:\NW IDM 7.1\opensaml-2.3.1-bin\opensaml-2.3.1\lib;D:\NW IDM 7.1\javamail-1.4.3\javamail-1.4.3\lib;D:\NW IDM 7.1\JNDI\jndi-1_2_1\lib;C:\j2sdk1.4.2_17-x64\bin;C:\j2sdk1.4.2_17-x64\jre\bin\server;C:\Program Files\Microsoft SQL Server 2005 JDBC Driver\sqljdbc_1.2\enu\sqljdbc.jar;D:\NW IDM 7.1\db-derby-10.6.1.0-bin\db-derby-10.6.1.0-bin\lib\derbyclient.jar;C:\Program Files (x86)\SAP\IdM\Virtual Directory Server\externals;C:\Program Files (x86)\SAP\IdM\Virtual Directory Server\lib\vdstools.jar;C:\Program Files (x86)\SAP\IdM\Virtual Directory Server\lib\vdsverifier.jar

Exception: Could not load external 'MxIDStoreRootDSEClass' or one of its referenced classes

Shutting down...

Could not load external 'MxIDStoreRootDSEClass' or one of its referenced classes

Server stopped

Former Member
0 Kudos

I told you way back its a java run time issue,

look at the JRE version for 64 bit it will solve your problem.

Former Member
0 Kudos

Hi Franklin,

just to be sure that I understand: You suggest to switch to a 32-bit JRE instead of the 64bit?

Kind regards,

R.

Former Member
0 Kudos

Hi R.H,

Hervé Montagnier answer is on target , that should resolve the problem.

NO I did not mean to say change it to 32BIt , I was saying something to do with the JRE conflict, I was thinking may be you might not have installed the correct JRE version for 64 bit.

Please do update if "Hervé Montagnier" helped resolve the issue.

Cheers