MQSeries.net :: View topic - Problem with WF Config Utility during QM creation

trevor.johnson · Posted: Thu Sep 30, 2004 6:53 am Post subject:

Hey all, I'm having trouble getting a WF installation installed on my local Win 2000 box. I'm using WF 3.4.0.5 and attempting to just create a basic WF server and web client on my box to do some WSAD debugging. Here's the error I'm getting during QM creation:

FMC33149E Return code from runmqsc SNTYWFQM < "c:\PROGR~1\IBMWEB~1\qmgrs\sntywfqm\mqs\fmczcltc.mqs" >> "c:\program files\ibm websphere mq workflow\cfgs\fmc\log\sntywfqm.log" is: 10

Here's the contents of sntywfqm.log:
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.

Starting MQSC for queue manager FMCQM.

: *BEGIN CMVC */
: **************************************************************************
: *
: * Workfile: fmcccltc.mqs, v3-comm, fmv3
: * Last update: 01/04/11 08:10:44
: * SCCS path, id: /home/flowmark/vc/0/1/6/8/s.39 1.11
: *
: *************************************************************************/
: *END CMVC */
: *BEGIN COPYRIGHT */
: **************************************************************************
: *
: * Licensed Materials - Property of IBM
: * 5697-FM3 5655-A96
: * (C) Copyright IBM Corp. 1998, 1999
: * US Government Users Restricted Rights - Use, duplication or
: * disclosure restricted by GSA ADP Schedule Contract
: * with IBM Corp.
: *
: *************************************************************************/
: *END COPYRIGHT */
: *BEGIN DISCLAIMER */
: **************************************************************************
: * DISCLAIMER
: * ----------
: * This material contains programming source code for your consideration.
: * These examples have not been thoroughly tested under all conditions.
: * IBM, therefore, cannot guarantee or imply reliability, serviceability,
: * or function of these programs.
: * ALL PROGRAMS CONTAINED HEREIN ARE PROVIDED TO YOU "AS IS", WITHOUT ANY
: * WARRANTIES (EXPRESS OR IMPLIED) OR SUPPORT WHATSOEVER, INCLUDING BUT
: * NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
: * FOR A PARTICULAR PURPOSE.
: *************************************************************************/
: *END DISCLAIMER */
:
: *************************************************************************
: * Client channel definition (server connection) using TCP/IP *
: * at FMCQM *
: *************************************************************************
1 : DEFINE CHANNEL('FMCQM.CL.TCP') +
: CHLTYPE(SVRCONN) +
: TRPTYPE(TCP) +
: DESCR('Bi-directional channel to/from FMCQM TCPIP') +
: MAXMSGL(9999999) +
: MCAUSER('fmc') +
: REPLACE +
: RCVDATA(' ' ) +
: RCVEXIT(' ' ) +
: SCYDATA(' ' ) +
: SCYEXIT(' ' ) +
: SENDDATA(' ' ) +
: SENDEXIT(' ' ) +
: HBINT(5)
AMQ8014: WebSphere MQ channel created.
:
: *************************************************************************
: * Client channel definition (client connection) using TCP/IP *
: * to FMCQM *
: *************************************************************************
2 : DEFINE CHANNEL('FMCQM.CL.TCP') +
: CHLTYPE(CLNTCONN) +
: CONNAME('SHOISURB(14007)') +
: TRPTYPE(TCP) +
: DESCR('Bi-directional channel to/from FMCQM TCPIP') +
: MAXMSGL(9999999) +
: REPLACE +
: QMNAME('FMCQM') +
: RCVDATA(' ') +
: RCVEXIT(' ') +
: SCYDATA(' ') +
: SCYEXIT(' ') +
: SENDDATA(' ') +
: SENDEXIT(' ') +
: HBINT(5)
AMQ9516: File error occurred.

:
: *************************************************************************
: * Allow remote administration *
: *************************************************************************
3 : DEFINE CHANNEL('SYSTEM.ADMIN.SVRCONN') +
: CHLTYPE(SVRCONN) +
: REPLACE
AMQ8014: WebSphere MQ channel created.
:
3 MQSC commands read.
No commands have a syntax error.
One valid MQSC command could not be processed.

I would guess that I have something configured incorrectly within MQ that's making the queue manager creation fail out. But it appears to be configured correctly.

I have MQ v5.3 fp 7 installed along with DB2 v8.1.6. I am attempting to connect to an existing WF v3.4.0.5 runtime on a remote box. That connection seems to be working fine.

Any ideas? As an added incentive, I've got $5 paypal ready for anyone who can successfully fix this problem since I'm so frustrated with it!