| Author |
Message
|
| Ranodip Basu |
 Posted: Thu Dec 01, 2005 12:53 pm Post subject: (Deploy Error) BIP1510E:Unable to deploy configuration Data |
 |
|
Apprentice
Joined: 23 Sep 2004
Posts: 48
|
Hi All,
We have strucked out with a problem.We have modified one of our message flows and trying to deploy it to the broker.
Now an attempt to deploy it giving a error message -
BIP1510E: Unable to deploy configuration data.
An attempt was made to deploy configuration data to one or more brokers, but the Configuration Manager is already deploying to broker AWTST62. You can not deploy to a set of brokers if there is an earlier deploy outstanding to any broker in the set. The deploy operation was not performed.
So we tried to stop the broker and restart it.But still it's not working.Could you please give us some solution.
Ranodip |
|
| Back to top |
|
 |
| wschutz |
| Posted: Thu Dec 01, 2005 1:04 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
If you right click on the domain in the admin perspective, you can "cancel deployment". You should be able to redeploy then.
Of course, you need to understand why the deploy didn't happen in the first place? Is the config mgr running? Anything in the windows event log?
_________________
-wayne |
|
| Back to top |
|
|
| Ranodip Basu |
| Posted: Thu Dec 01, 2005 1:08 pm Post subject: |
|
|
Apprentice
Joined: 23 Sep 2004
Posts: 48
|
Hi all,
Really very sorry --- I forgot to mention that I am using WMQI 2.1 CSD 7.
Ranodip |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Dec 01, 2005 1:24 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Edit: remove double post I made 
_________________
-wayne
Last edited by wschutz on Thu Dec 01, 2005 4:53 pm; edited 1 time in total |
|
| Back to top |
|
|
| wbibrk |
| Posted: Thu Dec 01, 2005 1:29 pm Post subject: |
|
|
Apprentice
Joined: 09 Jul 2005
Posts: 46
|
Hi,
In 2.1, you have to cancel the deploy manually by deleting the entry from the ConfigMgr DB. Connect to the ConfigMgr DB from a DB2 command prompt and issue:
select count (*) from CBROKER where CSECTION='DPLING'
this should return you a value of 1 which is the deploy that is pending. You can then issue
delete from CBROKER where CSECTION='DPLING'
Then issue the deploy. However, you need to find out why the deploy failed in the first case. Ensure that the channels are running (for starters)
HTH |
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri Dec 02, 2005 5:28 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| wbibrk wrote: |
Hi,
In 2.1, you have to cancel the deploy manually by deleting the entry from the ConfigMgr DB |
 Don't mess around with the database unless you know what you're doing.
Issuing a forced deploy will cause any outstanding deploy locks to be released; Before you go hunting around the CM database, I'd recommend trying this type of deploy when you've worked out why the first deploy failed. |
|
| Back to top |
|
|
| Ranodip Basu |
| Posted: Fri Dec 02, 2005 9:48 am Post subject: |
|
|
Apprentice
Joined: 23 Sep 2004
Posts: 48
|
Hi All,
Thanks a lot for all of your supports and suggestions.
[b]Mqmatt[/b] you are right --- deleting record from config manager DB is really a risk.
But fortunately we have been able to delete the proper record from this database following the instructions given [b]by wbibrk[/b].
Now it is deploying fine .
Thanks again for all of your co-operation.................
Ranodip |
|
| Back to top |
|
|
|
|
