Cannot read environment variable PROCESSOR_ARCHITECTURE

[tj_wilkinson2]

Hello,

I'm trying to patch the java portion of Solution Manager 4.0 and get the following error when trying to connect the GUI to JSPM. Below is the error. I found a similar error posted in the forums a few months ago, but no solution.

I'm using JSPM 10 if that helps.

Any help is appreciated. Thank you.

~TJ

Trouble Ticket Report

Java Support Package Manager for SAP NetWeaver'04s

SID................: SM1

Hostname...........: usalsapd

Install directory..: /usr/sap/SM1

Database...........: DB2 UDB for AS/400

Operating System...: $(/J2EE/StandardSystem/CentralInstance/J2EEEngineInstanceHost/OpSysType)

JDK version........: 1.4.2 IBM Corporation

JSPM version.......: 7.00.10.1.1.5.10

System release.....: 630

ABAP stack present.: false

The execution ended in error.

Could not detect operating system.

Cannot read environment variable PROCESSOR_ARCHITECTURE.

Could not read environment variables from the operating system.

Input output exception has occurred: cmd.exe: not found.

More information can be found in the log file /usr/sap/SM1/DVEBMGS42/j2ee/JSPM/log/log_2007_03_23_15_16_52/JSPM_MAIN_1_01.LOG.

Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:

com.sap.sdt.jspm.phases.PhaseTypeJSPM

com.sap.sdt.jspm.gui.JspmUiException

Could not detect operating system.

JSPM_MAIN

JSPMPhases

NetWeaver Upgrade

SAPJup

Java Upgrade

[thomas_obermeier · Accepted solution]

Hi TJ,

Are you sure you did not start JSPM from Windows the very first time? To my knowledge the Windows related parts of JSPM detect the processor type by checking environment variable PROCESSOR_ARCHITECTURE.

Check whether entry <StringVariable name="OS/CODE"> in file /usr/sap/<SID>/<instance>/j2ee/JSPM/config/BOOTSTRAP.XML is like OS4 or WIN. Unfortunately, JSPM is not smart enough to repair this by itself (at least it was as far as I know). Therefore, you need to repair this entry manually.

Make sure you are familiar with the JSPM documentation, particularly where and how to start JSPM server and GUI, respectively.

HTH,

Thomas

[Former Member · Accepted solution]

Hi TJ,

Please patch JSPM via SDM. This error is corrected then.

Best Regards

Sezai

[tj_wilkinson2]

The original question I had has been answered - thank you Thomas - I am just having bigger problems now.

~TJ

[tj_wilkinson2]

I was able to finally get the JSPM started after modifying the .xml file to 'OS4', but nothing would deploy because the Java AS wouldn't start. That's why I went back to the SDM because a note I found said I needed to redeploy the UME pieces to fix the error I was getting.

That did not work, so I thought using the SDM to push out the rest of the support packs might fix the problem. That didn't work either ... now I'm stuck.

[tj_wilkinson2]

Everyone - I appreciate all of your responses. It seems at this point, the best option is to use the SDM. I have already patched the JSPM and I think it made things worse as my Java Application server won't even start anymore. I'm going to post another message about that to see if anyone's seen the error I'm getting there.

Thanks again.

~TJ

[thomas_obermeier]

Hi TJ,

If you plan to do other deployments than JSPM itself I disagree that using SDM is the best way. This is because JSPM takes some actions beyond SDM which you will miss then. Again: make sure you did not corrupt BOOTSTRAP.XML by starting JSPM once from Windows and make sure you follow the instructions of JSPM documentation. Tell us if you need help looking up the docu.

Regards,

Thomas

[Former Member]

Hi TJ,

might be applying JSPM-Patch first via SDM will enable JSPM to apply the SP-Stack.

Regards

Guido

[Former Member]

Hello TJ,

Does SDM work for you? My recent experience (on another platform) is that JSPM is more user-friendly, but not as mature as SDM... SDM shows more detailed info, or just successfully apply the patch which failed with JSPM.

Meanwhile please let OSS know... JSPM should work.

Best regards,

Victor