Typically, you need to only review the runprobe.bat to determine the cause of the issue.
Most runprobe.bat files will first reference a probe_env.bat file which looks like this:
REM This file has been automatically generated.
REM Do not edit (any changes will be overwritten.)
set JAVA_HOME=%NIM_ROOT%\%NIM_JRE_HOME%
set JAVA_OPTS=-Xmx256m -Xms32m
set JAVA=%JAVA_HOME%\bin\java.ex
The runprobe.bat file will look like this (notice the call to probe_env.bat):
@echo off
call probe_env.bat
set TMP_LOG=%NIM_PROBE_NAME%.tmp
"%JAVA%" %JAVA_OPTS% -jar %NIM_PROBE_NAME%.jar %1 %2 %3 %4 %5 >%TMP_LOG% 2>&1
type %TMP_LOG% >> %NIM_PROBE_LOGFILE%
Attached are the actual examples described above. See the "Information" tab.