PROC0004E error causes WebSphere Application Server V5 embedded queue manager startup failure
 Technote (troubleshooting)
 
Problem(Abstract)
When WebSphere® Application Server V5 is installed with embedded messaging on Windows® platforms, the following errors can occur when the application server or the jmsserver (for WebSphere Network Deployment) is started:

MSGS0117W: End Queue Manager trace failed with exception:
com.ibm.ws.process.exception.InvalidExecutableException: PROC0004E:
Executable: [endmqtrc] does not appear to be a valid executable.
Process could not be created.
at
com.ibm.ws.process.Win32ProcessImpl.create(Win32ProcessImpl.java:130)
at com.ibm.ws.process.ProcessFactory.create(Unknown Source)
...
MSGS0153E: The Queue Manager process strmqm could not be started -
error: com.ibm.ws.process.exception.InvalidExecutableException:
PROC0004E: Executable: [strmqm] does not appear to be a valid
executable. Process could not be created.
...
MSGS0001E: Starting the JMS Server failed with exception:
com.ibm.ws.process.exception.InvalidExecutableException: PROC0004E:
Executable: [strmqm] does not appear to be a valid executable. Process
could not be created.
at
com.ibm.ws.process.Win32ProcessImpl.create(Win32ProcessImpl.java:130)
at com.ibm.ws.process.ProcessFactory.create(Unknown Source)
...
WSVR0501E: Error creating component null [class
com.ibm.ws.messaging.JMSService]
com.ibm.ws.exception.RuntimeWarning: MSGS0001E: Starting the JMS Server
failed with exception:
com.ibm.ws.process.exception.InvalidExecutableException: PROC0004E:
Executable: [strmqm] does not appear to be a valid executable. Process
could not be created.
at com.ibm.ws.messaging.JMSService.start(JMSService.java:295)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl
.java:536)
 
Cause
The cause of the problem is that the setupCmdLine.bat is not properly configured to include the locations of the embedded MQ binaries during installation.

On a system where this problem occurs, the WAS_PATH is set up like this in setupCmdLine.bat:


SET WAS_PATH=%WAS_HOME%\bin;%JAVA_HOME%\bin;%JAVA_HOME%\jre\bin;%PATH%

On a system that is set up correctly, the WAS_PATH looks like this:

SET WAS_PATH=%WAS_HOME%\bin;%JAVA_HOME%\bin;%JAVA_HOME%\jre\bin;%PATH%;C:\Program Files\IBM\WebSphere MQ\bin;C:\Program Files\IBM\WebSphere MQ\java\bin;C:/Program Files/IBM/WebSphere MQ/WEMPS\bin

 
Resolving the problem
To correct the problem, edit setupCmdLine.bat, located in the Install_Root \bin directory. At the end of the line that begins with SET WAS_PATH, append the following:
;C:\Program Files\IBM\WebSphere MQ\bin;C:\Program Files\IBM\WebSphere MQ\java\bin;C:/Program Files/IBM/WebSphere MQ/WEMPS\bin

The setupCmdLine.bat is run automatically when startServer.bat is run. If the locations of the MQ binaries are not included on the WAS_PATH, WebSphere cannot find the strmqm executable, and the PROC0004E error occurs during the attempted startup of the embedded queue manager.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java Message Service (JMS)
Operating system(s): Windows
Software version: 5.1.1.2
Software edition:
Reference #: 1191896
IBM Group: Software Group
Modified date: Dec 1, 2004