Linux Smconsole java.io.IOException Cannot run program "null\system32\tasklist.exe" error

book

Article ID: 4129

calendar_today

Updated On:

Products

CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On

Issue/Introduction

A console error happens when I start smconsole with policy server not running. If the policy server is running and I start smconsole, it comes up fine. 
The console error happens when I click the stop button. 

Notice that it is looking at Windows for tasklist.exe 

java.io.IOException: Cannot run program "null\system32\tasklist.exe": error=2, No such file or directory 
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041) 
at java.lang.Runtime.exec(Runtime.java:617) 
at java.lang.Runtime.exec(Runtime.java:450) 
at java.lang.Runtime.exec(Runtime.java:347) 
at com.netegrity.sm.smconsole.ServerConnection.isPolicyServerRunningOnWindows(ServerConnection.java:138) 
at com.netegrity.sm.smconsole.ServerConnection.getAuthenticationServerRunning(ServerConnection.java:76) 
at com.netegrity.sm.smconsole.StatusBean.getAuthenticationServerRunning(StatusBean.java:55) 
at com.netegrity.sm.smconsole.SmConsoleImpl.allServicesStopped(SmConsoleImpl.java:1297) 
at com.netegrity.sm.smconsole.SmConsoleImpl.actionPerformed(SmConsoleImpl.java:3708) 
at java.awt.Button.processActionEvent(Button.java:409) 
..... 
Caused by: java.io.IOException: error=2, No such file or directory 
at java.lang.UNIXProcess.forkAndExec(Native Method) 
at java.lang.UNIXProcess.<init>(UNIXProcess.java:135) 
at java.lang.ProcessImpl.start(ProcessImpl.java:130) 
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1022) 
... 30 more 

Cause

Code is not properly detecting Linux OS and is trying to run Windows executable, tasklist.exe, on Linux.

Environment

Policy Server 12.52 SP01 CR05 Build 2112Non-Windows OSNOTE: This defect affects 12.52 SP01 CR05 through 12.52 SP01 CR07

Resolution

This is a known defect and is tracked through Defect DE203493.

If you are experiencing the same issue, please open a ticket with Single Sign-on support and submit the details your environment.  Support and engineering will need to verify if the issue is the same.