JSPM won't start (version 700 16.1)

[Former Member]

Hi

My JSPM was working, and now on the Windows server where I am running it after upgrading to version 700. 16.1, I am getting the following error in the command prompt window, (and no GUI screen appears):

C:\Documents and Settings\wfqadm>X:\usr\sap\WFQ\DVEBMGS42\j2ee\JSPM\StartGui.bat

java.lang.ClassNotFoundException: com.sap.sdt.gui.core.SDTGui

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

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 com.sap.sdt.server.core.admin.GuiManager.startAsMethod(GuiManager.java:172)

at com.sap.sdt.server.core.admin.GuiManager.startGui(GuiManager.java:109)

at com.sap.sdt.server.core.admin.SDTServerAdmin.startGui(SDTServerAdmin.java:814)

at com.sap.sdt.server.core.admin.SDTServerAdmin.start(SDTServerAdmin.java:583)

at com.sap.sdt.server.core.SDTServer.start(SDTServer.java:82)

at com.sap.sdt.server.core.SDTServer.main(SDTServer.java:54)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.sdt.util.misc.MethodCall.invoke(MethodCall.java:80)

at com.sap.sdt.util.misc.BootStrapper.start(BootStrapper.java:77)

at SDTGui.main(SDTGui.java:50)

On the Host directory /usr/sap/WFQ/DVEBMGS42/j2ee/JSPM/log/logxxxx there are the following files:

BOOTSTRAP_01.LOG *STMF WFQADM 635 Nov 12 00:04

JSPM.LOG *STMF WFQADM 5503 Nov 12 00:04

SAPJup.LOG *STMF WFQADM 1569 Nov 12 00:04

SAPJup.LOG

lang.Throwable.xinit>(Throwable.java:180)#Java###Tag with name found.#2#ControlUnit#JSPM# lang.Throwable.xinit>(Throwable.java:180)#Java###Creating control unit .#1#JSPM#

lang.Throwable.xinit>(Throwable.java:180)#Java###Could not process dialog because execution dialogs have been suppressed.#1#Jspm lang.Throwable.xinit>(Throwable.java:180)#Java###Starting execution of action with name and type .#2#Unit#JSPM#

Appreciate any suggestions on how to get it going again.

regards

Michael.

[Former Member]

I am having the same issue on our system after updating to JSPM SP22 we are not able to launch JSPM now.

We are also running on iseries. I know this original post was from awhile back and it does not appear to have been answered in this thread, I was wondering if anyone has had this issue and can help us to resolve it.

[Former Member]

Are you trying C:\Documents and Settings\wfqadm>X:\usr\sap\WFQ\DVEBMGS42\j2ee\JSPM\go.bat

? Regards.

[Former Member]

Hi Sergo,

The GO.BAT I run first on the host server (iSeries), the procedure may be different on other platforms-

As WFQADM -

QSH CMD('/usr/sap/WFQ/DVEBMGS42/j2ee/JSPM/go')

using Classic VM

Current log directory is /usr/sap/WFQ/DVEBMGS42/j2ee/JSPM/log/log_2008_11_12_00_04_12.

JSPM process will be submitted. Use StartGui.bat to connect from Windows.

CPC1221: Job 417704/WFQADM/JSPM submitted to job queue R3_42 in library R3WFQ400.

CPC2206: Ownership of object QZSHSYSTEM in QTEMP type *USRSPC changed.

Press ENTER to end terminal session.

[Former Member]

I cant understand you , first you say

on the Windows server where I am running it after upgrading to version 700. 16.1

after you say about iSeries ...

Can you explain situation ?

Regards.

[Former Member]

Hi Sergo,

Note 885063 explains the process for IBM iSeries/System i platform:

Starting JSPM: Two scripts are involved in starting JSPM on iSeries:

o On the iSeries host you start the JSPM server process with the command

QSH CMD('/usr/sap/<SID>/<Central instance name>/j2ee/JSPM/go')

The script will indicate that the server is waiting for a GUI process to connect.

o On Windows you start the GUI using script

\usr\sap\<SID>\<Central instance name>\j2ee\JSPM\StartGui.bat

As this by default connects to localhost you will have to specify the host you want to connect to on the first screen.

This worked fine before, now it is broken.

I guess if I wait long enough I will get an answer from SAP Support.

Regards

Michael.

Edited by: Michael Power on Nov 12, 2008 10:24 PM

[Former Member]

Ok, now situation are сlear, try to read your first post, you say only about windows ...

Are you trying reboot server ? Also after your trying to startGui.bat it ask you connect to server?

Wait answer from SAP .

Regards.

[Former Member]

Hi,

i assume that on windows you are executing the go.bat by logging in using user SIDadm (relevant SID user).

Regards

Christopher