Joe,
Thanks. I followed your recommendation, but it fails because the extensions are missing (.pl and .exe). The result is:
C:\>"C:\Program Files\Business Objects\BusinessObjects Enterprise 6\perl\bin\perl" "C:\Program Files\Business Objects\BusinessObjects Enterprise 6\bin\scripts\wping"
Can't open perl script "C:\Program Files\Business Objects\BusinessObjects Enterprise 6\bin\scripts\wping": No such file or directory
If I add the extensions, the result is:
C:\>"C:\Program Files\Business Objects\BusinessObjects Enterprise 6\perl\bin\perl.exe" "C:\Program Files\Business Objects\BusinessObjects Enterprise 6\bin\scripts\wping.pl"
Can't open C:\/nodes/vmw2k/clusterlist.dat file at C:\Program Files\Business Objects\BusinessObjects Enterprise 6\bin\scripts\wping.pl line 22.
If I add the extensions and run from the “bin\scripts” directory the result is:
C:\Program Files\Business Objects\BusinessObjects Enterprise 6\bin\scripts>"C:\Program Files\Business Objects\BusinessObjects Enterprise 6\perl\bin\perl.exe" "C:\Program Files\Business Objects\BusinessObjects Enterprise 6\bin\scripts\wping.
pl"
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
This problem is definitely related to the spaces in the path, but I don’t think it’s the path I’m entering at the command prompt. After looking deeper, there seems to be a problem with both the wping.pl file and underlying system code. By changing one line, we were able get it partially working:
FROM:
$cmdline ="$ENV{'JAVA_HOME'}/bin/java com.bo.widiag.WPing @ARGV";
TO:
$cmdline ="\"$ENV{'JAVA_HOME'}/bin/java\" com.bo.widiag.WPing @ARGV";
We changed this line because the execution of the java was failing due to spaces. During execution, the variable $cmdline was being set to
C:\Program Files\Business Objects\ThirdParties\jdk_1.3.1/bin/java com.bo.widiag.WPing -c monitoring -u bo_monitor -p bo_monitor
…but after the change it became:
"C:\Program Files\Business Objects\ThirdParties\jdk_1.3.1/bin/java" com.bo.widiag.WPing -c monitoring -u bo_monitor -p bo_monitor
So, by making that change, the command output of wping.pl becomes:
C:\PROGRA~1\BUSINE~1\BUSINE~1\bin\scripts>"C:\PROGRA~1\BUSINE~1\BUSINE~1\perl\bi
n\perl.exe" wping2.pl -c monitoring -u bo_monitor -p bo_monitor
Starting WPing ...
Connecting to serverException in thread "main" java.lang.NoClassDefFoundError: j
avax/servlet/ServletRequest
at com.bo.widiag.WPing.main(WPing.java:86)
Timeout has been reached. WPing is now exiting.
C:\PROGRA~1\BUSINE~1\BUSINE~1\bin\scripts>
This is frustrating - especially when we followed BO’s installation instructions so carefully… 
Thanks for your help!,
Chris
cjweis (BOB member since 2003-10-02)