|Take a look at FAQ #140 at this site to see if that is the problem you are seeing. If that is not it, and you are using the IBM WebSphere SDK for Web Services 1.3.1 SR1 then:
Look at FAQ #6 at this site for a description of the algorithm that SE
is using when it examines the registry in order to find the Current Version
IBM WebSphere SDK for Web Services 1.3.1 SR1 does not create the registry
entries for which ServletExec is looking.
In our tests, that brand/version of SDK creates the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\IBM WebSphere SDK for Web Services
So the problem is that IBM changed the
registry entries between their 1.3.0 and 1.3.1 versions, and ServletExec is
still looking for the old registry keys.
This problem can be worked around by manually creating the registry
entries for which SE is looking, with the proper variable values as described
by the algorithm.
In the case of IBM WebSphere SDK for Web Services 1.3.1 for example,
you would create a Registry Key:
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Java Development Kit
and give it a "CurrentVersion" string value of 1.3
Then you would create a Registry Key beneath that:
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Java Development Kit\1.3
and give it a "JavaHome" string value that is the absolute path to the
folder that contains the "bin" and "lib" folders for IBM's JDK.
For instance, in our tests with IBM WSDK 1.3.1 that location was: