ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » [SOLVED] Workflow 3.5 on Windows 2003

Post new topic  Reply to topic
 [SOLVED] Workflow 3.5 on Windows 2003 « View previous topic :: View next topic » 
Author Message
RichA
PostPosted: Thu Apr 15, 2004 7:10 am    Post subject: [SOLVED] Workflow 3.5 on Windows 2003 Reply with quote

Centurion

Joined: 14 Mar 2002
Posts: 102

We're trying to set up a workflow server on windows 2003, with workflow 3.5, MQ 5.3 CSD6 and interim fix IC39916c, what's occuring seems to be an MQ problem when we create the configuration. We are directed to the log @fmczqqm which informs us -
15/04/2004 15:44:18 FMC33752I Creating services for queue manager 'THWFQM' ...
15/04/2004 15:44:18 FMC33003I amqmdain refresh >> "c:\program files\ibm\mqworkflow\cfgs\thwf\log\thwfqm.log"
15/04/2004 15:44:18 FMC33063I Return code from amqmdain refresh >> "c:\program files\ibm\mqworkflow\cfgs\thwf\log\thwfqm.log" is: -4
15/04/2004 15:44:18 FMC33003I amqmdain crtchi THWFQM SYSTEM.CHANNEL.INITQ >> "c:\program files\ibm\mqworkflow\cfgs\thwf\log\thwfqm.log"
15/04/2004 15:44:19 FMC33063I Return code from amqmdain crtchi THWFQM SYSTEM.CHANNEL.INITQ >> "c:\program files\ibm\mqworkflow\cfgs\thwf\log\thwfqm.log" is: -4
15/04/2004 15:44:19 FMC33149E Return code from amqmdain crtchi THWFQM SYSTEM.CHANNEL.INITQ >> "c:\program files\ibm\mqworkflow\cfgs\thwf\log\thwfqm.log" is: -4
The queue manager is created but I think it's trying to tell us it can't create services that start when the queue manager starts, ie. channel initiator.
We are also unable to view the MQ Services explorer as it is reporting that we are unauthorised to administer mq and we should be in the mqm group, which the user we are trying to do this with is, it's a local administrator, all the groups are local the installation is local.
Further investigation led us to the MQ error logs and they report -
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thu April 15 15:07:37 GMT Daylight Time 2004 |
| Host Name :- MQDEV2KSRV (Windows Ver 5.2 Build 3790: ) |
| PIDS :- 5724B4100 |
| LVLS :- 530.6 CSD06 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- MS000003 |
| Application Name :- MQM |
| Component :- msntCompData::Initialize |
| Build Date :- Feb 11 2004 |
| CMVC level :- p530-06-L040211 |
| Build Type :- IKAP - (Production) |
| UserID :- Administrator |
| Process Name :- C:\WINDOWS\system32\mmc.exe |
| Process :- 00003788 |
| Thread :- 00000001 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| () |
| FDCSequenceNumber :- 0 |
| Arith1 :- 2147500058 8000401a |
| |
+-----------------------------------------------------------------------------+

MQM Function Stack
msntCompData::Initialize
xcsFFST

MQM Trace History
{ xcsGetWorkPath
} xcsGetWorkPath rc=OK
{ InitProcessInitialisation
-{ xcsReleaseThreadMutexSem
-} xcsReleaseThreadMutexSem rc=OK
} InitProcessInitialisation rc=OK
{ xcsCreateThreadMutexSem
} xcsCreateThreadMutexSem rc=OK
{ DLLMain
-{ MCSInitCriticalSection
-} MCSInitCriticalSection rc=OK
-{ InitializeGCS
--{ MCSInitCriticalSection
--} MCSInitCriticalSection rc=OK
-} InitializeGCS rc=OK
} DLLMain rc=Unknown(1)
{ msntNamespaceOwner::RegisterNamespace
} msntNamespaceOwner::RegisterNamespace rc=OK
{ msntNamespaceOwner::RegisterNamespace
} msntNamespaceOwner::RegisterNamespace rc=OK
{ xcsInitialize
-{ xcsRequestThreadMutexSem
-} xcsRequestThreadMutexSem rc=OK
-{ xihCheckThreadList
-} xihCheckThreadList rc=OK
-{ xcsInitGlobalSecurityData
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsGetNTGroupSID
---{ xcsTimedLookupAccountName
---} xcsTimedLookupAccountName rc=OK
--} xcsGetNTGroupSID rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xcsInitGlobalSecurityData rc=OK
-{ InitPrivateServices
--{ xcsCreateThreadMutexSem
--} xcsCreateThreadMutexSem rc=OK
--{ xcsForcePSAPILoaded
---{ xcsDliHookPSAPI
---} xcsDliHookPSAPI rc=OK
---{ xcsDliHookPSAPI
---} xcsDliHookPSAPI rc=OK
---{ xcsDliHookPSAPI
---} xcsDliHookPSAPI rc=OK
---{ xcsDliHookPSAPI
---} xcsDliHookPSAPI rc=OK
--} xcsForcePSAPILoaded rc=OK
-} InitPrivateServices rc=OK
-{ xcsCreateNTSecurityAtts
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsInitGlobalSecurityData
--} xcsInitGlobalSecurityData rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xcsCreateNTSecurityAtts rc=OK
-{ xcsGetWorkPath
-} xcsGetWorkPath rc=OK
-{ xxxInitialize
--{ xcsGetMem
--} xcsGetMem rc=OK
--{ xcsCreateThreadMutexSem
--} xcsCreateThreadMutexSem rc=OK
--{ xcsGetWorkPath
--} xcsGetWorkPath rc=OK
--{ xcsGetMem
--} xcsGetMem rc=OK
-} xxxInitialize rc=OK
-{ xcsReleaseThreadMutexSem
-} xcsReleaseThreadMutexSem rc=OK
} xcsInitialize rc=OK
{ msntCompData::Initialize
-{ lpiQMUserInit
--{ zutUserInit
---{ xcsCheckAuthorization
----{ xcsInitGlobalSecurityData
----} xcsInitGlobalSecurityData rc=OK
----{ xcsCheckCurrentUserAuthorization
----} xcsCheckCurrentUserAuthorization rc=OK
---} xcsCheckAuthorization rc=OK
--} zutUserInit rc=OK
-} lpiQMUserInit rc=OK
-{ xcsFFST

I'm a bit stuck for ideas now. Any help would be appreciated.


Last edited by RichA on Fri Apr 16, 2004 11:30 am; edited 1 time in total
Back to top
View user's profile Send private message MSN Messenger
manoj
PostPosted: Thu Apr 15, 2004 10:55 am    Post subject: Reply with quote

Master

Joined: 30 Jan 2002
Posts: 237
Location: Virgina

I think you need to have "mqm" group in the Domain
_________________
-manoj
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger
RichA
PostPosted: Thu Apr 15, 2004 1:07 pm    Post subject: Reply with quote

Centurion

Joined: 14 Mar 2002
Posts: 102

There is no domain, it's all local.
Back to top
View user's profile Send private message MSN Messenger
clindsey
PostPosted: Thu Apr 15, 2004 2:44 pm    Post subject: Reply with quote

Knight

Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx

Based on the return code 2147500058 (0x8000401a) which is from
CoCreateInstance, it looks like there is a problem with your MUSR_MQADMIN account or password. Can you perform any functions from the MQSeries Explorer?

I would try the following steps in order. Test after each step.
Code:

1. Open a Windows command prompt, and change to direcrory <MQTOP>\bin. Run "amqmsrvn -regserver"

2. From the same directory, run "regsvr32 amqmspsn.dll"

3. Ensure MUSR_MQADMIN is not disabled and password is not set to expire

4. Change pwd to musr_mqadmin, then sync new password with dcomcnfg.
   - Run "dcomcnfg"
   - Scroll down and select "IBM MQSeries Service"
   - Click the Properties button
   - Click the Identity tab and plug in the new password and OK



Charlie
Back to top
View user's profile Send private message
RichA
PostPosted: Fri Apr 16, 2004 6:58 am    Post subject: Reply with quote

Centurion

Joined: 14 Mar 2002
Posts: 102

Thanks muchly for that, we were unable to use the MQSeries Explorer. The first step fixed it -
amqmsrvn -regserver
I'm interested in knowing what did that actually do?
Back to top
View user's profile Send private message MSN Messenger
clindsey
PostPosted: Fri Apr 16, 2004 7:37 am    Post subject: Reply with quote

Knight

Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx

Amqmsrvn is the Windows Service for WebSphere MQ.
Sometimes during intallation, the registration step to set amqmsrvn up as a DCOM object fails for any number of reasons. This command invokes the DCOM registration manually so MQ can run as a service under user MUSR_MQADMIN.

Charlie
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » [SOLVED] Workflow 3.5 on Windows 2003
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.