I'll see where the error is coming from. There is a variable which stores java location withing bundled jre.
Are you in position to tell what is your HQ installation path? I believe there is something weird in that path and this '\bin\java' is interpreted as command argument. These errors comes so early that there may not be anything usable in agent logs, but you could check it. Maybe it gives some hint.
I have tried this and it works, however I took the lazy route and just cut and pasted the changes.
there seem to be a couple of typo's in the last change. the first is the first -D%AG NT_INSTALL which should read -D%AGENT_INSTALL the second is due to a line cut a _ is missing in the last AGENT_BUNDLE
it should read +set CLIENT_CMD="%HQ_JAVA_HOME%\bin\java" -Djava.net.preferIPv4Stack=true -D%AGENT_INSTALL_HOME_PROP%="%AGENT_INSTALL_HOME%" -D%AGENT_BUNDLE_HOME_PROP%="%AGENT_BUNDLE_HOME%" -cp "%CLIENT_CLASSPATH%" %CLIENT_CLASS%
With a 2003 server there is another problem in wrapper.conf
I have never sussed out a proper way to get it to accept the HQ_JAVA_HOME setting, it invariably assumes the default even when it clearly knows better everywhere else. I have taken to setting the default to be where my HQ_JAVA_HOME is, which works.
Brain dead was the idea of putting spaces in a directory name in the first place.