Solution manager with MaxDB 64bit NW7

[Former Member]

I am able to successfully complete ABAP stack and getting erro in "creating java user" step

INFO 2009-11-03 06:59:36.582

Output of F:\usr\sap\CBM\DVEBMGS02\exe\jlaunch.exe UserCheck.jlaunch com.sap.security.tools.UserCheck "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\install\lib;C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\install\sharedlib;C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\install" -c sysnr=02 -c ashost=TDSM -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u J2EE_GUEST -r SAP_J2EE_GUEST -locked -message_file UserCheck.message is written to the logfile C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/UserCheck.log.

WARNING 2009-11-03 06:59:39.247

Execution of the command "F:\usr\sap\CBM\DVEBMGS02\exe\jlaunch.exe UserCheck.jlaunch com.sap.security.tools.UserCheck "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\install\lib;C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\install\sharedlib;C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\install" -c sysnr=02 -c ashost=TDSM -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u J2EE_GUEST -r SAP_J2EE_GUEST -locked -message_file UserCheck.message" finished with return code -3. Output:

Usage : F:\usr\sap\CBM\DVEBMGS02\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 2009-11-03 06:59:39.258

Removed file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\dev_UserCheck.

ERROR 2009-11-03 06:59:39.265

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

Applied sapnote 1126481

Manually created sapjsf id and try to skip error step (sapinst SAPINST_SKIP_ERRORSTEP=true

) by changing keydb file, doesn't help

OS: Windows 2008 Enterprise (SAP not supported) still trying - Is this reason? seems sapjsf is known issue

Any other checks I should be doing?

Thanks for your help

[Former Member]

I was just having the same problem with SQL Server on Windows 2008 R2. I went out and got all the latest kernel patches above SP 80 as mentioned and copied them into the kernel. This fixed my SICK error. I was getting the exact same error message mentioned above when I called t-code SICK.

[Former Member]

Yes .. I got the same error on Windows Server 2008 x64 R2 Enterprise Edition

Here is output of SICK transaction

SAP System Check

OS release Windows NT 6.1 7600 2x AMD64 Level 6 (Mod 26 Step 5) is not supported with this kernel (701)

Severe problems were detected during initial system check.

Please, do not use that system before fixing these problems.

Here is kernel version .. looks like kernel upgrade is only option before going on

-

---

disp+work information

-

---

kernel release 701

kernel make variant 701_REL

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

compiled for 64 BIT

compilation mode UNICODE

compile time Feb 24 2009 23:27:20

update level 0

patch number 32

source id 0.032

UPDATE : Successfully completed installation with kernel upgrade to patch version 80 for 701

Edited by: Kirankumar Rajput on Feb 17, 2010 6:43 PM

[Former Member]

hello,

did you fix the problem... I've check the SAP PAM and the operating system is supported

please tell me what did you do...

regards

[Former Member]

Also ,

There is some thing wrong with the ddic or j2ee_guest user....from the below section of logs...

Files\sapinst_instdir\SOLMAN\SYSTEM\ADA\CENTRAL\AS\install" -c sysnr=02 -c ashost=TDSM -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u J2EE_GUEST -r SAP_J2EE_GUEST -locked -message_file UserCheck.message is written to the logfile C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/UserCheck.log.

Thnaks

R.

[Former Member]

Hi,

Provide the C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/ADA/CENTRAL/AS/UserCheck.log. file.

Thnaks

R.

[Former Member]

Here is the user check log:

Usage : F:\usr\sap\CBM\DVEBMGS02\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)

*I forgot to mention: When I logged into ABAP, I am getting SICK dump about operating system compatible.* Is this causing java user failure? Is there anyway we can acknowledge, so that dump won't occur.

Runtime Errors START_CALL_SICK

Date and Time 03.11.2009 16:11:57

-

---

-

---

Short text

Database inconsistency: Start Transaction SICK.

-

---

-

---

What happened?

The current program had to be terminated because of an

error when installing the R/3 System.

The error occurred when initializing the R/3 System.

-

-

---

-

---

What can you do?

Please call the Transaction SICK. The list generated here

contains an installation error.

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

-

---

-

---

Error analysis

The error probably occurred when installing the

R/3 system.

Error text of the first reported error:

"OS release Windows NT 6.1 7600 4x AMD64 Level 6 (Mod 30 Step 5) is not

supported with this kernel (700)".

-

---

Edited by: Nagendra Dandeboyina on Nov 4, 2009 1:05 PM

[Former Member]

Error text of the first reported error: | | "OS release Windows NT 6.1 7600 4x AMD64 Level 6 (Mod 30 Step 5) is not | | supported with this kernel (700)". | ---------------------------------------------------------------------------------------------------- Edited by: Nagendra Dandeboyina on Nov 4, 2009 1:05 PM

Check your OS/DB/R3 for the availability [service.sap.com/pam]

If you have updated the kernel after installation then revert back and give a go.

[Former Member]

login abap stack, and run SICK tcode and check where u have errors.

put sick output here .

[Former Member]

Hello,

Were you able to resolve this problem ?

I am trying to install solution manager 7.0 EhP1 NW 7.01 on Win2008R2/mssql2008R2 and I am facing the same problem. UserCheck log shows the same error. Installation terminates at 'create java users' phase.

Thanks

[Former Member]

Hi,

If your getting the error "OS not supported", then 1 of the solutions is to patch the kernel manually to the latest SP. This helps..

Rgds,

Soujanya

[Former Member]

Upgrade the kernel to latest level to resolve the issue.

[Former Member]

how should I update the kernel patch manually ,,, I`ve downloaded the latest kernel patch as a ( .SAR ) file ,,,

but what should I do with the .sar file or where should I put it ????

thanks in advance.