| Author |
Message
|
| vennela |
 Posted: Fri Jan 17, 2003 8:05 am Post subject: Web client logon fails with 2058 |
 |
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Code: |
| FMC00013E Communication error - Failing Action: Connect_to_QM, Reason Code: 2058, Failing Object: WEBQMGR.: com.ibm.workflow.api.FmcException: |
I have a new configuration for web-client and the Logon fails. The Web-client is on another box. fmcautil from this box works fine but web-client doesn't.
---
Venny
Last edited by vennela on Mon Jul 26, 2004 6:15 am; edited 1 time in total |
|
| Back to top |
|
 |
| kriersd |
| Posted: Fri Jan 17, 2003 11:33 am Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Start with the Webclient.properties file.. Look for these settings and make sure they are correct.
AgentLocator=LOC_LOCATOR
AgentConfiguration=XXXXX
Good luck
Dave
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| jet |
| Posted: Tue Jan 21, 2003 11:15 am Post subject: |
|
|
Apprentice
Joined: 04 Dec 2002
Posts: 49
Location: New York
|
2058 is the reason code on an NQCONN or MQCONNX call, the value specificed for the QMgrName parameter is not valid or not known. It also occurs if the praameter pointer is not valid (not easy to dectect thou).
This reason code can also occur if an MQ client application attemps to connect to a queue manager within an MQ-client queue-manager group and either:
Q-mgr groups are not supported
or there is not Q-mgr group with the sepcified name...
So looks like the web client cant find the Q mgr name. |
|
| Back to top |
|
|
| amittalekar |
| Posted: Tue Jan 21, 2003 12:04 pm Post subject: |
|
|
Disciple
Joined: 03 Apr 2002
Posts: 166
Location: VA, USA
|
| 2058 error code can also mean that the webclient installable user has not permissions (authorizations) to access Qmanager. Solution is to add the webclient installable USER to mqm group. |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Jan 22, 2003 9:40 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
This tunrned out to be a permissions problems. The WAS admin was not able to open the channel table file (in /var/fmc/chltabs ).
Thanks
Venny |
|
| Back to top |
|
|
| CP |
| Posted: Mon Jul 26, 2004 4:50 am Post subject: Communication error - Failing Action:Reason Code: 2058 |
|
|
Novice
Joined: 15 Jul 2004
Posts: 16
|
Hello,
I got the similar error when I was trying to log on through webclient to one of our development server. The queuemanager is running and client session is active. It is throwing FMC00013E with reason code 2058. I checked the channel tab file, it has got
-rw-rw---- 1 mqm mqm
Is there any permissions problem like Venny had, or my userID is missing in MQM Group as Amit's comment.
WebClient properties file is with correct AgentLocator and ConfigID. For some reason, it is not able to communicate the Workflow Server. Can anybody help me out in this.
Thanks,
CP. |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Jul 26, 2004 5:16 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Have you tried fmcautil from the web client box? What does it say? |
|
| Back to top |
|
|
| CP |
| Posted: Mon Jul 26, 2004 5:37 am Post subject: |
|
|
Novice
Joined: 15 Jul 2004
Posts: 16
|
| fmcautil on webclient is saying System started. When I queried on System commands menu, Administration and execution servers are active. |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Jul 26, 2004 6:20 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
What user started the application server?
Did you try bouncing the application server after the QMGR is started? |
|
| Back to top |
|
|
| CP |
| Posted: Mon Jul 26, 2004 6:27 am Post subject: [SOLVED] Reason Code 2058. |
|
|
Novice
Joined: 15 Jul 2004
Posts: 16
|
I figured out that, my channel tab file is pointing to different box. My bad. Thanks for all your help. Now I am able to use webclient.
Thanks,
CP. |
|
| Back to top |
|
|
|
|
