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 » IBM MQ Installation/Configuration Support » service can't be started

Post new topic  Reply to topic
 service can't be started « View previous topic :: View next topic » 
Author Message
louisa.p
PostPosted: Tue Sep 04, 2001 10:51 am    Post subject: Reply with quote

Novice

Joined: 03 Sep 2001
Posts: 14

I have followed the installation guide for Workflow 3.3. I have currently installed DB2 7.1, MQSeries v5.2.1, and MQSeries Workflow 3.3. I have finished the FMC configuration. It created a new service MQSeries Workflow 3.3 - FMC but cannot be started. When I try to start it manually, the following error reported.

MQSeries Workflow 3.3 Error Report

Report creation = 9/4/2001 10:20:56 AM
Related message = FMC31050E An error has occurred which has terminated processing.


Error location = File=e:v330srcfmcrrstx.cxx, Line=614, Function=FmcRRSTx::BeginGlobTx()
Error data = FmcTransXException, ReturnCode=2195

Anyone has a hint of what happened?
Thanks in advance.

Back to top
View user's profile Send private message
bower5932
PostPosted: Tue Sep 04, 2001 10:56 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA

I just did a quick search on an internal database, and I found a problem that looked very similar. Here is the resolution:

Problem was caused by the configuration of one of the configuration IDs, cust supplied the incorrect DB2 password. After they deleted the configuration, and reran the configuration supplying the correct DB2 password password, they were able to start that particular workflow configuration with no problems.

Hope this helps.....
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
louisa.p
PostPosted: Tue Sep 04, 2001 3:23 pm    Post subject: Reply with quote

Novice

Joined: 03 Sep 2001
Posts: 14

I tried the suggestion with loggin on with wrong password to db2. However, it doesn't seem like the solution for me. I am still experiencing the same error. I am wondering if there is any particular setting for db2 I need to set or any particular setting for the mqseries server to set in order for my runtime client to work for mqseries workflow? I really need to start up my MQSeries workflow server asap. I am stuck with this problem for awhile already and I still have no clue why my server doesn't start up. Any other hint will be greatly appreciated. Thanks.
Back to top
View user's profile Send private message
bower5932
PostPosted: Wed Sep 05, 2001 1:47 pm    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA

I'm afraid that you've already exceeded my MQWF knowledge. I have a co-worker that is more of an expert, but she is out today. I do know that she always runs:

fmczchk -d

and looks at the fmczchk.log file that it produces. I'd recommend that you do this and look for any errors that it throws out.
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
louisa.p
PostPosted: Thu Sep 06, 2001 3:40 pm    Post subject: Reply with quote

Novice

Joined: 03 Sep 2001
Posts: 14

Thanks for the suggestion.
Here is my output for the fmczchk command
FMC34010I: Configuration checker version 3.3.0.99 started.
FMC34120I: Command-line options specified: -d

FMC34012I: ===> General checks.
FMC34011I: Performing MQSeries Workflow Version 3.3.0 checks.
FMC34101I: The Operating System is Windows 2000 5.00 (Service Pack 1).
FMC34103I: Local time is 2001-09-06 16:24:35.
FMC34104I: Universal time coordinated (UTC) is 2001-09-06 23:24:35.
FMC34-DBG: Successfully loaded library c:winntsystem32wsock32.dll
FMC34301I: WinSock version: WinSock 2.0.
FMC34314I: The local IP address is 192.168.101.119.
FMC34131I: The MQSeries Workflow installation directory is c:mqwfbin.
FMC34154I: MQSeries Workflow Version 3.3.0.0 is installed.
FMC34143I: The default configuration is 'FMC' (from the general configuration profile).
FMC34121I: The current configuration is 'FMC'.
FMC34145I: The following configurations are available: FMC.
FMC34-DBG: Installation profile values:
FMC34-DBG: FolderName: 'IBM MQSeries Workflow'
FMC34-DBG: ConfigurationRootDirectory: 'C:MQWF'
FMC34-DBG: InstallationDirectory: 'C:MQWF'
FMC34-DBG: InstalledComponents: 'JWCLUMDRBPASI'
FMC34-DBG: Language: 'enu'
FMC34-DBG: VRM: '030300'
FMC34-DBG: General configuration profile values:
FMC34-DBG: DefaultConfigurationID: 'FMC'
FMC34-DBG: Current configuration profile values:
FMC34-DBG: RTSystemLogFile: 'c:mqwfcfgsfmclogfmcsys.log'
FMC34-DBG: RTErrorLogFile: 'c:mqwfcfgsfmclogfmcerr.log'
FMC34-DBG: RTExecutionServerOperationMode: 'Standalone'
FMC34-DBG: FMLConnectName: 'FMC.FMCGRP.FMCSYS,FMCQM'
FMC34-DBG: MQClusterMode: 'f'
FMC34-DBG: MQClusterName: 'FMCGRP'
FMC34-DBG: MQTransactionCoordinatorStartsQM: '0'
FMC34-DBG: MQTransactionCoordinatorPassword: '********'
FMC34-DBG: MQTransactionCoordinator: 'DB2ADMIN'
FMC34-DBG: MQBackupQueues: 'c'
FMC34-DBG: FMLClientChannelTable: 'c:mqwfchltabsmqwfchl.tab'
FMC34-DBG: FMLServerChannelTable: 'c:mqwfchltabsmqwfchl.tab'
FMC34-DBG: MQPort: '5010'
FMC34-DBG: MQCommunicationAddress: 'capitolhill'
FMC34-DBG: MQCommunicationProtocol: 't'
FMC34-DBG: MQPrincipal: 'fmc'
FMC34-DBG: LoadFDL: '0'
FMC34-DBG: CreateRuntimeDatabase: '0'
FMC34-DBG: RTDatabaseMQWorkflowUser: 'ADMIN'
FMC34-DBG: RTDatabasePassword: '********'
FMC34-DBG: RTDatabaseUserID: 'DB2ADMIN'
FMC34-DBG: RTDatabaseAdministratorPassword: '********'
FMC34-DBG: RTDatabaseAdministratorUserID: 'DB2ADMIN'
FMC34-DBG: RTDB2LocalInstance: 'DB2'
FMC34-DBG: RTDB2Instance: 'DB2'
FMC34-DBG: RTDatabaseInstanceIsRemote: '0'
FMC34-DBG: RTDatabaseAlias: 'FMCDB'
FMC34-DBG: RTDatabase: 'FMCDB'
FMC34-DBG: MQQueueManager: 'FMCQM'
FMC34-DBG: MQPrefix: 'FMC'
FMC34-DBG: System: 'FMCSYS'
FMC34-DBG: SystemGroup: 'FMCGRP'
FMC34-DBG: ConfiguredComponents: 'SI'
FMC34-DBG: User profile values:
FMC34-DBG: (none)
FMC34113I: Language specification is 'enu' (from the installation profile).
FMC34115I: The message catalog is c:mqwfbinfmckmenu.cat.
FMC34-DBG: LC_MESSAGES='', NLSPATH='C:MQWFBIN%N'
FMC34132I: The XPG4 locale is EN_US.IBM-1252.
FMC34133I: The ANSI code page is 1252, the OEM code page is 437.
FMC34134I: The locale file used is c:mqwfbinlocaleen_usibm-1252.lcl.
FMC34-DBG: LC_ALL='EN_US', LANG='', LOCPATH='C:MQWFBINLOCALE'

FMC34013I: ===> Admin Server found, checks started.
FMC34-DBG: Found c:mqwfbinfmcamain.exe
FMC34-DBG: Successfully loaded library c:progra~1sqllibbindb2cli.dll
FMC34-DBG: Successfully loaded library c:progra~1sqllibbindb2sys.dll
FMC34-DBG: Successfully loaded library c:progra~1sqllibbindb2app.dll
FMC34122I: Environment variable DB2_RR_TO_RS is set to 'YES'.
FMC34500I: ==> Database Manager configuration for DB2.
FMC34508I: Agent stack size is 96.
FMC34508I: Query heap size is 1500.
FMC34501I: ==> Database configuration for FMCDB.
FMC34528W: The database manager has not been started.
FMC34700I: ==> Service Control Manager configuration.
FMC34-DBG: Settings for service 'DB2NTSECSERVER':
FMC34-DBG: Service type: 16
FMC34-DBG: Start type: auto start
FMC34-DBG: Error control: normal
FMC34-DBG: Binary: "C:Program FilesSQLLIBbindb2sec.exe"
FMC34-DBG: Start name: LocalSystem
FMC34-DBG: Display name: DB2 Security Server
FMC34nnnI: Service DB2NTSECSERVER: Startup automatic, account LocalSystem
FMC34-DBG: Settings for service 'MQSeriesServices':
FMC34-DBG: Service type: 16
FMC34-DBG: Start type: auto start
FMC34-DBG: Error control: ignore
FMC34-DBG: Binary: C:Program FilesIBMMQSeriesbinamqsvc.exe
FMC34-DBG: Start name: LocalSystem
FMC34-DBG: Display name: IBM MQSeries
FMC34-DBG: Depends on: DB2NTSECSERVER
FMC34-DBG: Depends on: DB2
FMC34nnnI: Service MQSeriesServices: Startup automatic, account LocalSystem
FMC34-DBG: Settings for service 'DB2':
FMC34-DBG: Service type: 16
FMC34-DBG: Start type: auto start
FMC34-DBG: Error control: normal
FMC34-DBG: Binary: C:PROGRA~1SQLLIBbindb2syscs.exe
FMC34-DBG: Start name: .db2admin
FMC34-DBG: Display name: DB2 - DB2
FMC34-DBG: Depends on: LanmanServer
FMC34-DBG: Depends on: +NetBIOSGroup
FMC34nnnI: Service DB2: Startup automatic, account .db2admin
FMC34-DBG: Settings for service 'MQSeriesServices':
FMC34-DBG: Service type: 16
FMC34-DBG: Start type: auto start
FMC34-DBG: Error control: ignore
FMC34-DBG: Binary: C:Program FilesIBMMQSeriesbinamqsvc.exe
FMC34-DBG: Start name: LocalSystem
FMC34-DBG: Display name: IBM MQSeries
FMC34-DBG: Depends on: DB2NTSECSERVER
FMC34-DBG: Depends on: DB2
FMC34-DBG: Settings for service 'MQ Workflow - FMC':
FMC34-DBG: Service type: 16
FMC34-DBG: Start type: auto start
FMC34-DBG: Error control: normal
FMC34-DBG: Binary: c:mqwfbinfmcamain.exe
FMC34-DBG: Start name: .db2admin
FMC34-DBG: Display name: MQSeries Workflow 3.3 - FMC
FMC34-DBG: Depends on: MQSeriesServices
FMC34nnnI: Service MQ Workflow - FMC: Startup automatic, account .db2admin

FMC34013I: ===> Server message device found, checks started.
FMC34-DBG: Found c:mqwfbinfmccdfms.dll
FMC34-DBG: Services file is 'c:winntsystem32driversetcservices'
FMC34303I: TCP port fmclFMCQM114000 found at number 14000.
FMC34307I: The local listener for port 14000 is not running.
FMC34303I: TCP port fmclFMCQM5010 found at number 5010.
FMC34307I: The local listener for port 5010 is not running.
FMC34-DBG: CSD for MQSeries Server from profile is 'CSD00'
FMC34404I: The MQSeries Server 5.21.0.0 is installed.
FMC34-DBG: Using Registry to locate qm.ini files
FMC34nnnI: System for FMCQM is FMC.FMCGRP.FMCSYS
FMC34031I: Successfully loaded QM switch file library db2swit.dll.
FMC34nnnI: Settings for FMCQM from Queue manager FMCQM registry

FMC34025E: FmcAssertionException, Condition=*** Pre-condition failed in e:v330srcfmckstr.cxx(626): !IsNull() && !substr.IsNull() && ulStart > 0, Origin=File=e:v330srcfmckdbg.cxx, Line=143, Function=fmckRequire(const char*,const char*,unsigned int).

FMC34100I: Messages have been written to c:fmczchk.log.
FMC34999I: Configuration checker ended: 1 error(s), 1 warning(s), rc = 3.


Is it possible to ask your co-worker if she know about this error?

Thanks
Back to top
View user's profile Send private message
louisa.p
PostPosted: Thu Sep 06, 2001 4:17 pm    Post subject: Reply with quote

Novice

Joined: 03 Sep 2001
Posts: 14

Sorry, don't worry about that error. I just forgot to start the DB2 server. I have no error reported from this command after I started the DB2 server.
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 » IBM MQ Installation/Configuration Support » service can't be started
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.