|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
IBM MQ Workflow 3.6 service is not getting started |
« View previous topic :: View next topic » |
Author |
Message
|
golam_m |
Posted: Wed Nov 30, 2005 6:25 am Post subject: IBM MQ Workflow 3.6 service is not getting started |
|
|
Apprentice
Joined: 10 Oct 2005 Posts: 48
|
Hi All,
I have installed DB2 8.2, websphere MQ 5.3 and MQ Workflow 3.6 in my windows XP machine. I have created a Configuration called FMC. But I am not able to start the Workflow 3.6 service for the same. I get the following alerts in the event viewer when I try to start the service.
1. FMC31020E The server could not be started.
2. FMC31000E A database error occurred. SQL code: -998.
I want to let you know in advance that TP_MON_NAME is also set to mqmax.
Please help.
Thanks!
Golam |
|
Back to top |
|
 |
kotha |
Posted: Wed Nov 30, 2005 9:12 am Post subject: |
|
|
Partisan
Joined: 12 Mar 2005 Posts: 333
|
You have two different versions in the same system??. is 5.3 service running? if so, stop it and start the 3.6. If you still get the problem, look at your DB configuration with MQworkflow 3.6. |
|
Back to top |
|
 |
hos |
Posted: Thu Dec 01, 2005 12:27 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002 Posts: 470
|
From the readme file:
2.2.1 XA-Coordination problems on Windows
If using DB2 8.1 FP7a or DB2 8.2 on Windows, you may encounter
problems when starting the MQ Workflow administration server. If you
receive an SQL 998 Reasoncode 9, but no subcode, then there might be
a permission problem between DB2 and WebSphere MQ. To fix this, you
must make the WebSphere MQ administration user ID MUSR_MQADMIN a
member of the DB2 users group (e.g. DB2USERS) or, if that group does
not exist, make the user ID a member of the Administrators group.
After changing the permissions you need to reboot your machine. |
|
Back to top |
|
 |
golam_m |
Posted: Thu Dec 01, 2005 8:50 pm Post subject: |
|
|
Apprentice
Joined: 10 Oct 2005 Posts: 48
|
Hi Hos/Pachyderm,
Thank you very much for your urgent help. It worked after adding DB2ADMNS group to the MUSR_MQADMIN user.
Thanks!
Golam |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|