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 » WebSphere Message Broker (ACE) Support » BIP1350E: The current operation has timed out.

Post new topic  Reply to topic
 BIP1350E: The current operation has timed out. « View previous topic :: View next topic » 
Author Message
Deepak Batra
PostPosted: Mon Aug 12, 2002 1:08 am    Post subject: BIP1350E: The current operation has timed out. Reply with quote

Apprentice

Joined: 25 Feb 2002
Posts: 31

Hi Friends

I need urgent solution for my problem :
I had installed MQSI 2.1 on windows NT 4.0

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.


I had tried out to stop and start configmgr , username server still facing same error . also i had checked out the status of my QMGR which is running .

I will appreciate if anyone can tell me some tricks to solve .

Regards
Deepak
Back to top
View user's profile Send private message
pankajg
PostPosted: Mon Aug 12, 2002 7:38 am    Post subject: Reply with quote

Acolyte

Joined: 11 Oct 2001
Posts: 53

Deepak

U amy try these :-

1. check the channels/ listeners between ur Qmgr & the config Mgr - Qmgr
2. Bring down all components ,then restart the machine.
_________________
Regards
Pankaj
Back to top
View user's profile Send private message Send e-mail
Deepak Batra
PostPosted: Mon Aug 12, 2002 9:06 pm    Post subject: Reply with quote

Apprentice

Joined: 25 Feb 2002
Posts: 31

pankajg wrote:
Deepak

U amy try these :-

1. check the channels/ listeners between ur Qmgr & the config Mgr - Qmgr
2. Bring down all components ,then restart the machine.


Hi

Thanks for reply . see i have tried out all . can the problem be due to the database(DB2) . i am using DB2 database for config manager . i had find out in my event viewer i am getting some database problems . if u find anything else please tell me .

Regards
Deepak
Back to top
View user's profile Send private message
pankajg
PostPosted: Tue Aug 13, 2002 5:53 am    Post subject: Reply with quote

Acolyte

Joined: 11 Oct 2001
Posts: 53

Batra

DB2 is not a problem , infact i also use DB2.

The following should help...u.

0. Open ur NT task Mgr window. Sort the prococess names by alphabets .
Keep an eye on all processes starting with - b . as config mgr starts a bipservice.exe & bipconfigmgr.exe.

1. Start ur config mgr & parallely keep looking at the NT task window , u will see that bipconfigmgr.exe appears momentarily & then disappears .

2 Delete the config mgr using mqsideletconfigmgr command , clearing the DB's of the tables created by the mqsi ( avoid deleteing the DB itself )

3. Recreate the config mgr , using ur old DBs.

4. Make sure that u have defined the ODBC sources to the broker DB's &
Msg repo in the System DSN tab .

5. start the config mgr & Try to connect ,,,it shoould work...

Best wishes
_________________
Regards
Pankaj
Back to top
View user's profile Send private message Send e-mail
Bayer6
PostPosted: Thu Aug 15, 2002 3:43 pm    Post subject: Reply with quote

Newbie

Joined: 15 Aug 2002
Posts: 1

Hi Pankaj,

i followed your advice since i experienced the same error. But it did not help.

The bipconfigmgr.ex disappears after a few seconds every time i start ConfigMgr.
I am getting the same Error BIP1350E when trying to connect the Control Center to the Configuration Manager.

I am running a ruther odd environment due to clients defaults:

- Win2k
- MQSI 2.0.1
- MQS 5.2
- MA88 Supportpac (with old com.ibm.mq.jar --> V5.1) with

Control Center, ConfigMgr and Broker all on the same node.

Could anyone please give me some hint on how to keep bipconfigmgr.ex running? Or is the problem something else?

Thanks in advance for your help

bayer
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 » WebSphere Message Broker (ACE) Support » BIP1350E: The current operation has timed out.
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.