JSPM does not start

[Former Member]

Hi Guys,

  I just upgrade sap portal from nw 7.02 to 7.3 in windows 2008 Cluster with Oracle 11.2 , it went ok but now I want to start JSPM to deploy EHP1 , but It doesnt start and I get below error message, any help will be appreciate.

An error has occurred during the execution of the JSPM_MAIN phase.

Cannot initialize application data. Error occurred while trying to get the INSTANCE_NAME parameter value from the instance number: 21 on host: ALFJEPSTGDB1 via SAPCONTROL the web service API. See SAP Note 1401712 for further information. com.sap.engine.services.webservices.jaxrpc.exceptions.SOAPFaultException: Invalid parameter

ct 26, 2012 4:56:39 PM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been started.
Oct 26, 2012 4:56:39 PM [Info]: Phase type is com.sap.sdt.jspm.phases.PhaseTypeJSPM.
Oct 26, 2012 4:56:39 PM [Info]: Starting Initialize dialog...
Oct 26, 2012 4:56:39 PM [Info]: Detecting system parameters...
Oct 26, 2012 4:56:39 PM [Info]: You can find additional information in log file D:\usr\sap\PIQ\J22\j2ee\JSPM\log\log_2012_10_26_16_56_30\DETECT_SYSTEM_PARAMETERS_01.LOG.
Oct 26, 2012 4:56:40 PM [Error]: com.sap.sdt.util.diag.WrapperIOException: Macro /J2EE/StandardSystem/CentralInstance/WorkingDirectory has an invalid value.

Oct 26, 2012 4:56:40 PM [Error]: com.sap.sdt.util.diag.WrapperIOException: Macro /J2EE/StandardSystem/CentralInstance/WorkingDirectory has an invalid value.

Oct 26, 2012 4:56:40 PM [Error]: com.sap.sdt.util.xml.XMLException
Oct 26, 2012 4:56:40 PM [Error]: Could not create variable handler JspmLogCollector1296121481568714585.
Oct 26, 2012 4:56:40 PM [Error]: Exception has occurred during the execution of the phase.
Oct 26, 2012 4:56:40 PM [Error]: com.sap.engine.services.webservices.jaxrpc.exceptions.SOAPFaultException: Invalid parameter
Oct 26, 2012 4:56:40 PM [Error]: Error occurred while trying to get the INSTANCE_NAME parameter value from the instance number: 21 on host: ALFJEPSTGDB1 via SAPCONTROL the web service API. See SAP Note 1401712 for further information.
Oct 26, 2012 4:56:40 PM [Error]: Cannot initialize application data.
Oct 26, 2012 4:56:40 PM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been completed.
Oct 26, 2012 4:56:40 PM [Info]: Start time: 2012/10/26 16:56:39.
Oct 26, 2012 4:56:40 PM [Info]: End time: 2012/10/26 16:56:40.
Oct 26, 2012 4:56:40 PM [Info]: Duration: 0:00:01.178.
Oct 26, 2012 4:56:40 PM [Info]: Phase status is error.

Thanks for the support & help 

[Former Member · Accepted solution]

Hi Mar V,

This is the issue because of sapstartsrv service. Either this service is not running or running with incorrect permissions. Please do folloing to get rid of this issue:

1. Sotp sap system.

2. Kill sapstartsrv service.

3. start sap system.

Do this on all instances.

Regards, Premlesh

[Former Member · Accepted solution]

Thank you soooo much Premlesh, It made it to work

[Former Member · Accepted solution]

This didn't work to the NW7.3 install we just downloaded and installed.

JSPM doesn't work right out of the box of af fresh brand new NW7.3 installation.

Turns out SAP changed how sapcontrol works a year ago and still haven't updated JSPM accordingly in the images you download from SWDC.

Software quality assurance, where are you?

Solution: Change DEFAULT.pfl: change SDEFULT to DEFAULT.

See Note :

1600846 JSPM/SUM calls sapcontrol without user credentials

Also make sure you have moved the backup profiles from the SYS/profile

directory.

Also see the note 1565645 SAP composite note: sapcontrol

to start services.

sapcontrol -nr <instance number> -function RestartService

[Former Member · Accepted solution]

This seems to be an issue with the profile parameter or environment variables.

Please check the same

[Former Member]

Hi Mar V,

Here is the solution of your issue -

Solution

If you face problems during the instance detection of the SAP system, check the following:

• Make sure that the SAP start service is running on each of the instances on each host in your SAP system.
• If you have a kernel with version lower than the listed versions and the update/upgrade tool was unable to detect all your instances, get a newer SAP KERNEL archive for your release and apply it manually as described in SAP Note 1122058.

Following these steps will solve your issue.

Regards,

Ashutosh Shukla