| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Control Center Error: BIP1350E |
« View previous topic :: View next topic » |
| Author |
Message
|
| ryzor |
 Posted: Fri Jan 30, 2004 12:15 am Post subject: Control Center Error: BIP1350E |
 |
|
Apprentice
Joined: 31 Dec 2001
Posts: 42
|
Hi guys can you please help me out...
i'm trying to log into the Control Center MQSI v2.1 and i get the below error message .... it just started happening now but yesterday i was able to log in successfully ... i have restarted the Broker and the ConfigManager ...and even rebooted the machine! ...  ( this is on my production machine ) and help will be highly appreciated.
Error Msg.....
BIP1350E: The current operation has timed out.
One or more requests have been sent to the Configuration Manager to process the current operation, but no reply has been received for the last request sent.
Either your request has queued up behind a long-running request by another user, or the Configuration Manager has stopped. Check that it is up and running then retry the operation. Because the link to the Configuration Manager is via MQSeries, it is important to note that the original operation may have fully completed, or have partly completed, even though no reply was received in the allotted time. The results of the retried operation should indicate this, and will determine subsequent actions. For example, if a check-in operation timed out then the update may have occurred, but the object may still be locked. A subsequent check-in would then fail with a locked response. The action would then be to unlock the object.
Thanx - Ryzor |
|
| Back to top |
|
 |
| CoolDude |
| Posted: Fri Jan 30, 2004 5:34 am Post subject: |
|
|
Apprentice
Joined: 17 Jan 2004
Posts: 39
|
Try increasing the MQSI_TIMEOUT Environment Variable.
Thanks,
_________________
Correct Me from Wrong . If i am correct Appreciate Me  |
|
| Back to top |
|
|
| kirani |
| Posted: Fri Jan 30, 2004 1:47 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Log on to your Config Mgr machine and find out what's going on with bipconfigmgr.exe process. Is it taking any CPU cycles, etc? Try starting the control center on the server itself and see if you are able to connect. Also, look for any errors in the EVent Viewer. IF this does not help then try to capture the traces by enabling the trace on the Config Mgr service using mqsichangetrace command.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Missam |
| Posted: Sat Jan 31, 2004 9:44 am Post subject: |
|
|
Chevalier
Joined: 16 Oct 2003
Posts: 424
|
Its Woking Yesterday and not working today
What are the changes you did from yesterday |
|
| 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
|
|
|
|
