| Author |
Message
|
| run |
 Posted: Mon Jan 12, 2009 11:12 am Post subject: Deployment issue |
 |
|
Apprentice
Joined: 14 May 2007
Posts: 45
Location: Newyork, USA
|
Hi,
I'm getting this error when trying to cancel a deployment (i have had "deployment in progress" for 2 days now.
"BIP423S: The message could not be found in resource bundle BIPv610. Inserts: {0} {1} {2} {3} {4} {5}"
This is a dev system..
Can somebody please help me
Thanks |
|
| Back to top |
|
 |
| run |
| Posted: Mon Jan 12, 2009 11:15 am Post subject: |
|
|
Apprentice
Joined: 14 May 2007
Posts: 45
Location: Newyork, USA
|
I had tried to cancell the deployment, Restart the execution group, tried to remove the deployed children nothing works. Restarted the broker and the execution group and the server.  |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jan 12, 2009 11:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
BIP errors below 1000 are Toolkit BIPs and not Runtime BIPs.
You need to look at the Runtime log to see if there are additional errors. |
|
| Back to top |
|
|
| run |
| Posted: Mon Jan 12, 2009 12:02 pm Post subject: |
|
|
Apprentice
Joined: 14 May 2007
Posts: 45
Location: Newyork, USA
|
| There are know known error's linked to that issue or any.Further I even updated my toolkit to the latest 6.1.0.3 version. But did not help |
|
| Back to top |
|
|
| ImSoTired |
| Posted: Mon Jan 12, 2009 12:37 pm Post subject: |
|
|
Novice
Joined: 17 Apr 2007
Posts: 20
Location: Lima, Perú
|
Hey, i've got the same problem  , nothing appears in the syslog, user trace, service trace for agent of config mgr, std of each execution group. Any advice?? A deployment in progress message don't disappear even after a broker restart. I'm a broker domain with WMB v6.1.0.3 in an AIX Box....  |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Mon Jan 12, 2009 2:26 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
I searched the forum for "BIP423S" and found this related article: http://www.mqseries.net/phpBB/viewtopic.php?t=46127
To summarize:
| contact admin wrote: |
Just to close this thread: I did not find any solution, so I recreated the domain from scratch.
I'm sure there are less drastic measures that would have worked, but I did not have the time to try things that might have worked. |
Perhaps opening a PMR with IBM would help further. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 13, 2009 12:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rekarm01 wrote: |
| Perhaps opening a PMR with IBM would help further. |
It's going to be a dark day when IBM can't help with their own product.
Please post your solution for the benefit of future readers when you obtain it. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue Jan 13, 2009 4:27 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
I'm pretty sure the error is in the ConfigMgr.
Just took a look through the CM's repository logic. The actual code path is missing presumed buried with MQSI 2.0, but there is one possibility where a 423 error code could be thrown.
It's an internal situation related to deployment and a slightly screwed up database.
Recreating the domain should fix the problem, but I'd recommend raising a PMR. |
|
| Back to top |
|
|
| run |
| Posted: Tue Jan 13, 2009 9:50 am Post subject: |
|
|
Apprentice
Joined: 14 May 2007
Posts: 45
Location: Newyork, USA
|
I just teared down everything and got broker,config all back. I should have tried to recreate a Domain connection I suppose.
Thanks,
EVERYBODY |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Tue Jan 13, 2009 12:39 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| mqmatt wrote: |
Just took a look through the CM's repository logic. The actual code path is missing presumed buried with MQSI 2.0, but there is one possibility where a 423 error code could be thrown.
It's an internal situation related to deployment and a slightly screwed up database. |
I couldn't find my documentation for MQSI 2.0, but I did find something from WMQI 2.1, for what it's worth.
| Code: |
BIP0423E The resource is locked.
Explanation: The requested resource is currently locked by another user.
User Response: No user action required. |
|
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Jan 14, 2009 4:03 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Wow, retro... that looks about right.
We got rid of check out/check in the CM in WBIMB v5, but there's still some locking code there to enable deployments to work as you'd expect. But there's obviously a bug, as the error should no longer be exposed... hence the need for a PMR  |
|
| Back to top |
|
|
|
|
