| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Control Center not starting on Windows 2000 Server |
« View previous topic :: View next topic » |
| Author |
Message
|
| mkhadse |
 Posted: Sat Jun 08, 2002 6:25 am Post subject: Control Center not starting on Windows 2000 Server |
 |
|
Acolyte
Joined: 31 Dec 1969
Posts: 73
|
Control Center v2.0.2 was working fine after installation from the Console.
However when I try to start the control center, I get the following error.
Checked that ConfigMgr and Queue Manager are running.
Any help is greatly appreciated.
Thanks
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. |
|
| Back to top |
|
 |
| TorpedoSTu |
| Posted: Wed Jun 12, 2002 6:24 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2001
Posts: 73
|
If you've not fixed this already,
Make sure that the mq jar files (MA88) are in the classpath
Regs
Stu |
|
| Back to top |
|
|
| CodeCraft |
| Posted: Tue Jun 18, 2002 2:05 pm Post subject: |
|
|
Disciple
Joined: 05 Sep 2001
Posts: 195
|
Are you trying to run the CC on the W2K Server using Terminal Services? I think there are some issues with how T/S "partitions" user spaces which affects WMQI/MQ operation, and is essentially not supported.
You can always simply connect using TCP/IP! If this is not the issue, there are other possible causes, but it sounds like you have this working locally on the server console, so should not be related to classpaths, etc. |
|
| 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
|
|
|
|
