I would check if the engine is started correctly. What messages are returned when you start the engine in the command line?
It should end with somthing like
"Waiting for request..."

If not maybe the userId or the engineId in the command is not correct. Did you use ADMIN to create the Buld Definition and Build Engine?
Is your Buld Engine ID really "Local"?
Open the Build Engine in RTC from context menu and you can see the ID. This ID has to be set in the command. You can also check here if the engine is marked "Active".

I have seen this behavior when trying to run the build engine when a 1.4 jvm
is on the path. You get no output at all.

When you run jbe without any arguments, do you get a usage message?

Try specifically identifying the vm to use with the -vm option.

For example:

jbe -vm c:\packages\jdk1.5.0_13\bin\java.exe

This should print a usage message.

Hi
Just FYI:
Running jbe with the workshop db results in a crash with the errors as below. Using the -vm option to point to the java.exe included in the M5 server works ok.
ie.
C:\Jazz\TeamConcert-1.0M5-win32\jazz\buildsystem\buildengine>jbe -repository http://localhost:9080/jazz -userId build -engineId workshop.build.engine -sleepTime 3
crashes while
C:\Jazz\TeamConcert-1.0M5-win32\jazz\buildsystem\buildengine\eclipse>jbe -vm C:\Jazz\JazzTeamServer-1.0M5\jazz\server\win32\ibm-java2-i386-50\jre\bin\java.exe -repository http://localhost:9080/jazz -userId build -engineId workshop.build.engine -sleepTime 3

works.

Error messages:

"jbe has encountered a problem and needs to close.."
Error Signature:
AppName: jbe.exe AppVer:0.0.0.0 ModName:msvcrt.dll
ModVer:7.0.2600.2180 Offset:00037ea2

Technical info:

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="jbe.exe" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="jbe.exe" SIZE="28672" CHECKSUM="0xBB45DB5" MODULE_TYPE="WIN32" PE_CHECKSUM="0x12615" LINKER_VERSION="0x0" LINK_DATE="08/28/2007 21:12:02" UPTO_LINK_DATE="08/28/2007 21:12:02" />
<MATCHING_FILE NAME="plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.1.R33x_v20070828\eclipse_1020.dll" SIZE="69632" CHECKSUM="0xE3516DF0" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1DD62" LINKER_VERSION="0x0" LINK_DATE="08/28/2007 21:11:58" UPTO_LINK_DATE="08/28/2007 21:11:58" />
</EXE>
<EXE NAME="MSVCRT.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="msvcrt.dll" SIZE="343040" CHECKSUM="0x1BFAF375" BIN_FILE_VERSION="7.0.2600.2180" BIN_PRODUCT_VERSION="6.1.8638.2180" PRODUCT_VERSION="7.0.2600.2180" FILE_DESCRIPTION="Windows NT CRT DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft Windows Operating System" FILE_VERSION="7.0.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="msvcrt.dll" INTERNAL_NAME="msvcrt.dll" LEGAL_COPYRIGHT=" Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x57CD3" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="7.0.2600.2180" UPTO_BIN_PRODUCT_VERSION="6.1.8638.2180" LINK_DATE="08/04/2004 07:59:14" UPTO_LINK_DATE="08/04/2004 07:59:14" VER_LANGUAGE="English (United States) " />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="984576" CHECKSUM="0xF0B331F6" BIN_FILE_VERSION="5.1.2600.3119" BIN_PRODUCT_VERSION="5.1.2600.3119" PRODUCT_VERSION="5.1.2600.3119" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft Windows Operating System" FILE_VERSION="5.1.2600.3119 (xpsp_sp2_gdr.070416-1301)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT=" Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xF9293" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.3119" UPTO_BIN_PRODUCT_VERSION="5.1.2600.3119" LINK_DATE="04/16/2007 15:52:53" UPTO_LINK_DATE="04/16/2007 15:52:53" VER_LANGUAGE="English (United States) " />
</EXE>
</DATABASE>

I would guess that in the first case, you're getting a vm that is not
supported. At your cmd prompt in
C:\Jazz\TeamConcert-1.0M5-win32\jazz\buildsystem\buildengine, try typing
java -version

jbe only works with a 1.5 or newer vm

If you don't have a 1.5 or newer vm on your PATH, then you need to specify
the -vm argument to point at one. As you did in your second example.

---
Ryan Manwiller
Jazz Team Build