| Author |
Message
|
| sarasu |
 Posted: Thu Dec 06, 2007 3:06 pm Post subject: AMQ7626 XA Resource Manager Init... Failure |
 |
|
Master
Joined: 02 Feb 2006
Posts: 229
|
I am getting the same old error here!! I checked all the previous posts here....i tried to create a new XA Resource Manager in the properties of the QManager (FMCQM).....when i bounce the QManager again getting the same error. Also the db2swit.dll is there in the path.
Need help for installing server....
I am installing MQWF3.6, MQ5.3 CSD13 & DB2 8.1 SP 12.
ERROR as follows::
============
12/6/2007 15:51:36
AMQ6174: The library c:\program files\ibm\websphere mq
workflow\db2swit\db2swit.dll was not found. The queue manager will continue
without this module.
EXPLANATION:
The dynamically loadable file c:\program files\ibm\websphere mq
workflow\db2swit\db2swit.dll was not found.
ACTION:
Check that the file exists and is either fully qualified or is in the
appropriate directory.
-------------------------------------------------------------------------------
12/6/2007 15:51:36
AMQ7622: WebSphere MQ could not load the XA switch load file for resource
manager 'DB2 FMCDB'.
EXPLANATION:
An error has occurred loading XA switch file c:\program files\ibm\websphere mq
workflow\db2swit\db2swit.dll. If the error occurred during startup then the
queue manager will terminate. At all other times the queue manager will
continue without this resource manager meaning that it will no longer be able
to participate in global transactions. The queue manager will also retry the
load of the switch file at regular intervals so that the resource manager will
be able to participate again should the load problem be resolved.
ACTION:
Look for a previous message outlining the reason for the load failure. Message
AMQ6175 is issued if the load failed because of a system error. If this is the
case then follow the guidance given in message AMQ6175 to resolve the problem.
In the absence of prior messages or FFST information related to this problem
check that the name of the switch load file is correct and that it is present
in a directory from which it can be dynamically loaded by the queue manager.
The easiest method of doing this is to define the switch load file as a
fully-qualified name. Note that if the queue manager is still running it will
need to be restarted in order that any changes made to its configuration data
can be picked up.
----- amqtrmca.c : 256 --------------------------------------------------------
Thanks |
|
| Back to top |
|
 |
| vennela |
| Posted: Thu Dec 06, 2007 4:06 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
1. On your Windows desktop, right-click on the My Computer icon.
2. Select Manage to open the Computer Management console.
3. Select System Tools / Local Users and Groups / Users.
4. Right-click on the user ID MUSR_MQADMIN and select Properties.
5. Select the Member of tab, then Add.
6. Enter either Administrators, DB2ADMNS, or DB2USERS in the entry field and click OK.
7. Click OK to close the user properties panel.
8. Close the Computer Management console.
9. To activate the new settings effective, restart all WebSphere MQ processes. The most reliable way to do this is to reboot the machine.
Note: It is not necessary to make the user ID fmc a member of any of these groups because it only accesses the MQ resources and is not used to access DB2. The ″Local System″ account is used instead to access any DB2 databases. |
|
|
| Back to top |
|
|
| sarasu |
| Posted: Fri Dec 07, 2007 9:44 am Post subject: |
|
|
Master
Joined: 02 Feb 2006
Posts: 229
|
vennela,
Thanks for the reply...i did as you said.. but still my QMANAGER is not running.....The error logs of the QMANAGER are as follows..anything else i can do here to run the QMANAGER?
Error:
-------
Error code 20 starting FMCQM/Command Server WebSphere MQ service.
The service was unable to start FMCQM/Command Server. The error message
reported was as follows: Process could not be started - return code 20
Use WebSphere MQ Services to investigate why the service could not begin. If
recovery for this service is active, MQ will attempt to recover.
Thanks |
|
| Back to top |
|
|
| sarasu |
| Posted: Fri Dec 07, 2007 9:52 am Post subject: |
|
|
Master
Joined: 02 Feb 2006
Posts: 229
|
| Thanks vennela...My server started now..!! |
|
| Back to top |
|
|
| sarasu |
| Posted: Fri Dec 07, 2007 11:34 am Post subject: |
|
|
Master
Joined: 02 Feb 2006
Posts: 229
|
When i am trying to start the Runtime client..it is hangingup!!! reason is the channel initiator is not running..when i am trying to start this..i am getting the following error...
Error::
-------
Program cannot open queue manager object.
The attempt to open either the queue or queue manager object 'SYSTEM.CHANNEL.INITQ' on queue manager 'FMCQM' failed with reason code 2042.
Ensure that the queue is available and retry the operation.
---------------------
Unable to recover FMCQM/Channel Initiator WebSphere MQ service.
The WebSphere MQ service has attempted to recover FMCQM/Channel Initiator, but
all attempts have failed. There will be no more attempts to recover this
service.
Use WebSphere MQ Services to investigate why the service failed and could not
be restarted.
Need help....Thanks.. |
|
| Back to top |
|
|
|
|
