Solution Manager 7 Install Error on Create Java Users-UserCheck createJSF

[Former Member]

Hi, SDN expert.

I am installing Solution Manager 7.0.

Just spent few hours on troubleshooting Import ABAP and Import Java Dump step. Now, I got another createJSF user error on Create Java Users step (Phase 31 of 44).

First, I got a warning on: Execution of the command "C:\usr\sap\SM1\DVEBMGS00\exe\jlaunch.exe UserCheck.jlaunch com.sap.security.tools.UserCheck message (as shown below):

I read a post that it may be relating to I install Solution Manager 7.0 in Window Server 2008 R2, it caused an OS validation check error shown below. I also read a related post it is about the SAPJSF user password. But I still can't find the root cause and the solution yet.

=============================

Execution of the command "C:\usr\sap\SM1\DVEBMGS00\exe\jlaunch.exe UserCheck.jlaunch com.sap.security.tools.UserCheck "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\install\lib;C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\install\sharedlib;C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\install" -c sysnr=00 -c ashost=ISBDCAPP101 -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u SAPJSF -p XXXXXX -r SAP_BC_JSF_COMMUNICATION_RO -user_type system -message_file UserCheck.message" finished with return code -3. Output:

Usage : C:\usr\sap\SM1\DVEBMGS00\exe\jlaunch.exe [-options] <arg0> <arg1> ... <argn>

Launch the specified java program

options : [-file=<property file>] (default=jlaunch.properties)

[-nodename=<node name>] (default=jlaunch)

[-app=<application name>] Standalone application

-> <property file> = <application name>.properties

-> <SAP profile> = <application name>.pfl

[pf=<SAP profile>] (default=jlaunch.pfl)

[-parent=<pid of the parent process>] (default=0)

[-tracefile=<filename>] (default=dev_jlaunch)

Critical Error

Can't read program properties

-> Internal program error (rc = -1)

========================================================

Thanks for all helpful advices,

KC

Edited by: KC on Jul 14, 2011 4:26 AM

[Former Member · Accepted solution]

Detail logs:

===================

WARNING 2011-07-14 03:52:32.984

Unable to get information about path
LABEL.ASC\ using GetVolumeInformation. Operating system error message: The specified path is invalid.

INFO 2011-07-14 03:52:39.315

Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.15.xml'.

INFO 2011-07-14 03:52:39.600

Execute step

Component W2K_ServicePack_Check|ind|ind|ind|ind

Preprocess of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|1|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0

INFO 2011-07-14 03:52:45.429

Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.12.xml'.

INFO 2011-07-14 03:52:45.640

Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/statistic.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/statistic.35.xml'.

INFO 2011-07-14 03:52:45.935

Execute step createJSF of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Doublestack|ind|ind|ind|ind|3|0

INFO 2011-07-14 03:52:46.379

Removing file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\UserCheck.jlaunch.

INFO 2011-07-14 03:52:46.381

Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\UserCheck.jlaunch.

INFO 2011-07-14 03:52:46.395

Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\UserCheck.log.

INFO 2011-07-14 03:52:46.495

Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS.

INFO 2011-07-14 03:52:46.504

Output of C:\usr\sap\SM1\DVEBMGS00\exe\jlaunch.exe UserCheck.jlaunch com.sap.security.tools.UserCheck "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\install\lib;C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\install\sharedlib;C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\install" -c sysnr=00 -c ashost=ISBDCAPP101 -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u SAPJSF -p XXXXXX -r SAP_BC_JSF_COMMUNICATION_RO -user_type system -message_file UserCheck.message is written to the logfile C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/UserCheck.log.

WARNING 2011-07-14 03:52:49.483

Execution of the command "C:\usr\sap\SM1\DVEBMGS00\exe\jlaunch.exe UserCheck.jlaunch com.sap.security.tools.UserCheck "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\install\lib;C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\install\sharedlib;C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\install" -c sysnr=00 -c ashost=ISBDCAPP101 -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u SAPJSF -p XXXXXX -r SAP_BC_JSF_COMMUNICATION_RO -user_type system -message_file UserCheck.message" finished with return code -3. Output:

Usage : C:\usr\sap\SM1\DVEBMGS00\exe\jlaunch.exe [-options] <arg0> <arg1> ... <argn>

Launch the specified java program

options : [-file=<property file>] (default=jlaunch.properties)

[-nodename=<node name>] (default=jlaunch)

[-app=<application name>] Standalone application

-> <property file> = <application name>.properties

-> <SAP profile> = <application name>.pfl

[pf=<SAP profile>] (default=jlaunch.pfl)

[-parent=<pid of the parent process>] (default=0)

[-tracefile=<filename>] (default=dev_jlaunch)

Critical Error

Can't read program properties

-> Internal program error (rc = -1)

INFO 2011-07-14 03:52:49.489

Removing file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\dev_UserCheck.

ERROR 2011-07-14 03:52:49.495

CJS-30197 . DIAGNOSIS: For more details see output of log file:

ERROR 2011-07-14 03:52:49.520

FCO-00011 The step createJSF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Doublestack|ind|ind|ind|ind|3|0|createJSF was executed with status ERROR ( Last error reported by the step :. DIAGNOSIS: For more details see output of log file:).

===================================================

[Former Member · Accepted solution]

Hi,

I checked the log file: C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/UserCheck.log.

The error seems caused by this jlaunch.exe: Usage : C:\usr\sap\SM1\DVEBMGS00\exe\jlaunch.exe [-options] <arg0> <arg1> ... <argn>

I ran this jlaunch.exe in command prompt, and found that Windows NT 6.1 (Windows Server 2008 R2) is not on the supported OS list. I am looking at the jlaunch patch information now.

====================================================

C:\usr\sap\SM1\DVEBMGS00\exe>jlaunch.exe

-

---

.

jlaunch information

-

---

kernel release 700

kernel make variant 700_REL

DBMS client library

compiled on NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00

compiled for 64 BIT

compilation mode UNICODE

compile time Jan 23 2008 20:12:02

update level 0

patch number 128

source id 0.144

-

---

supported environment

-

---

database (SAP, table SVERS) 700

operating system

Windows NT 5.0

Windows NT 5.1

Windows NT 5.2

Windows NT 6.0

-

---

jlaunch patch information

-

---

( 0.126) CST Patch Collection 35 2007 (note 1088712)

( 0.128) NI: TCP connect fails with EINVAL on AIX (note 1087831)

[Former Member · Accepted solution]

Hi KC,

It is a common case that some of the installation data gets deleted during installation because of some cron jobs running on the host.

Do the following:

Unpack J2EEINSTALL.SAR archive from the <Java DVD>\J2EE_OSINDEP\J2EE-INST location and copy the contents to C;\program files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\install directory

Now start sapinst and continue with the old installation.

Let me know if this works, or else i will give you another work around.

Regards,

SBK

[Former Member · Accepted solution]

HI, SBK.

I extracted the J2EEINSTALL.SAR files. I compared the size and number of files with C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\install folder. They are exactly the same.

Probably it is something else causing error. Any idea?

Thanks,

KC

[Former Member · Accepted solution]

Another possible solution would be to create manually the user SAPJSF in the ABAP stack of the solman system in client 001 with role SAP_BC_JSF_COMMUNICATION_RO or SAP_BC_JSF_COMMUNICATION_RO. After this

you could bypass that stage in the keydb.xml file following one of the two described ways :

1.- Run ./sapinst SAPINST_SKIP_ERRORSTEP=true

2.- Or change 'keydb.xml' => change to OK the status of step "createJSF"

Search in keydb.xml for something like :

<fld name="STEPKEY">

<strval><![CDATA[ NW_Onehost ind ind ind ind 0 0 NW_Onehost_System

ind ind ind ind 1 0 NW_CI_Instance ind ind ind ind 11 0 NW_CI_Instance_

Doublestack ind ind ind ind 3 0 createJSF]]>

</strval>

</fld>

<fld name="STATUS">

<strval><![CDATA [[ERROR]]]>

</strval>

</fld>

and change [CDATA[[ERROR]]] to [CDATA[[OK]]]

Ensure to take a copy of original keydb.xml file, this will be useful if something went wrong and we need to revert.

If you created correctly SAPJSF user in the ABAP stack of solman the use can proceed with the above step.

Regards,

SBK

[Former Member · Accepted solution]

I got this SAP System Check error when I login to Solution Manager SM1via SAP GUI.

OS release Windows NT 6.1 7601 Service Pack 1 4x AMD64 Level 6 (Mod 44 Step 2) is not supported with this kernel (700).

I think the current kernel doesn't support Window Server 2008 R2 (Windows NT 6.1 7601 Service Pack 1 4x AMD64).

I did a search and found that someone downloaded and patched with SAPEXE_278-20001354.SAR (Kernel part 1) and SAPEXEDB_278-20001361.SAR (kernel part 2) to solve the same issue.

I visited SMP, I found that there are there are a lot of kernel part II SARs, not sure it is recommended to apply all patches or just one. (SAP KERNEL 7.00 64-BIT UNICODE -> Windows Server on x64 64bit -> MS SQL SERVER)

Can you confirm which patches I should download and apply to fix this issue? What are the steps to apply the patches? Do I need to start a fresh installation,and select the new kernel patches (considering I cannot proceed with this error now)?

I think I need to fix this kernel incompatibility issue and rerun the installation again. Is that right?

Thanks,

KC

[Former Member · Accepted solution]

KC,

I could see that you are installing Solution Manager 7.0, may I know as to why you are installing a old version when Solution Manager 7.0 EHP1 and Solution Manager 7.1 is available.

I would strongly recommend you to install any of the latest solman version and they come with additional features.

Regards,

SBK

[Former Member · Accepted solution]

The server is currently installed with Window Server 2008R2 and MS SQL 2005.

I plan to install both Solution Manager and SAP ECC 6.0 EhP4 IDES in the same server.

Unfortunately, I a told that SAP ECC 6.0 EhP4 IDES installation only works with MS SQl 2005 server. I only can upgrade to MS SQL 2008 /2008 R2 after installation.

Actually, I couldn't find Solman 7.1 in my company licensed application components catalog.

Since I just need Solution Manager to generate Solution Key for SAP IDES installation. I decided to install Solman 7.0, and later upgrade to 7.0 EHP1 (if necessary) when IDES installation and MS SQL 2005is upgraded to 2008R2.

Maybe I should have install Solman 7.0 EHP1. directly with Ms SQL server 2005 at the first place. Can I (I never check in details)?

We will probably just use Solman to generate solution keys and simple maintenance optimizer.

Thanks,

KC

[Former Member · Accepted solution]

Hi,

After apply the latest patches for kernel 700, this problem resolved by itself when I resume the installation.

Thanks,

KC

[Former Member · Accepted solution]

Good to know that your issue got fixed.

Regards,

SBK

[Former Member]

Thanks for all the helpful advices.

KC