| Author |
Message
|
| Nizam |
 Posted: Wed Sep 22, 2004 5:44 pm Post subject: Execution Group (Restricted Access) |
 |
|
Disciple
Joined: 10 Feb 2004
Posts: 160
|
WBIMB 5.0 with csd 04 on windows 2000 server.
I was trying to deploy a set of flows to a broker to the default execution group several times. Everything was deploying fine initially but then suddently the default exection group disappeared and all I see is Execution Group(Restricted Access).
When I try to create the execution group with name 'default', I get a message that i cannot create a duplicate execution group.
Now the broker does not allow me to create any execution group.
Any suggestions....
Thank you.
Nyzam. |
|
| Back to top |
|
 |
| kirani |
| Posted: Wed Sep 22, 2004 10:15 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Did someone change your security settings?
_________________
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 |
|
|
| waugh |
| Posted: Thu Sep 23, 2004 4:30 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 225
|
| I saw the exact problem about 3 months back, i do not remember what exactly i did, but its something to do with CBROKER, CEG tables. can you post the exact message you see when you try to create a new execution group? |
|
| Back to top |
|
|
| Nizam |
| Posted: Thu Sep 23, 2004 5:12 am Post subject: |
|
|
Disciple
Joined: 10 Feb 2004
Posts: 160
|
This is what I see when I create an execution group
BIP1776S: Unexpected exception in the Configuration Manager ACLGroupEntry class getExecutionGroupUUID method; exception text: 'java.lang.NullPointerException', 'null'.
While attempting a database operation on the configuration repository, an exception was caught by the Configuration Manager ACLGroupEntry class getExecutionGroupUUID method. The database operation did not complete successfully. The exception text is: java.lang.NullPointerException, null.
The exception text may indicate that the DB2 JDBC Driver could be found; check that the system CLASSPATH variable contains access to the DB2 runtime classes. If the DB2 classes are present in the CLASSPATH or if the exception text indicates a different problem, please contact your IBM support center.
If i try to create a default execution i see this
BIP1160E: Duplicate name 'default' for ExecutionGroup label within configuration repository.
An error occurred when attempting to save ExecutionGroup label 'default' to the configuration repository because another ExecutionGroup label already exists with the same name.
Rename the ExecutionGroup label and retry the operation.
____________________________________________________________
BIP1711W: ExecutionGroup is not accessible or does not exist.
An attempt was made to register for information on the ExecutionGroup with UUID 'eabd6a2b-ff00-0000-0080-f05118d88c3e', but either the user who asked for the information does not have sufficient authority to do so or the ExecutionGroup does not exist.
Ensure that the user of the application that issued the request has sufficient authority to view the ExecutionGroup. If the user has sufficient authority and the object exists, attempt to retry the operation. If the problem persists please turn on Configuration Manager tracing to capture the error and contact your IBM support center. |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Mon May 23, 2005 9:01 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Any update on this issue.
We are getting same errors.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon May 23, 2005 9:04 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| venkat kurra wrote: |
Any update on this issue.
We are getting same errors. |
Which ones?
Did someone change your security settings?
Did your configuration manager log any additional error messages in the Application Log?
Did you try restarting your ConfigMgr? Are there messages piling up on ConfigMgr SYSTEM.BROKER.* queues?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Mon May 23, 2005 9:48 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
When i try to create an Execution group:
BIP1776S: Unexpected exception in the Configuration Manager ACLGroupEntry class getExecutionGroupUUID method; exception text: 'java.lang.NullPointerException', 'null'.
While attempting a database operation on the configuration repository, an exception was caught by the Configuration Manager ACLGroupEntry class getExecutionGroupUUID method. The database operation did not complete successfully. The exception text is: java.lang.NullPointerException, null.
The exception text may indicate that the DB2 JDBC Driver could be found; check that the system CLASSPATH variable contains access to the DB2 runtime classes. If the DB2 classes are present in the CLASSPATH or if the exception text indicates a different problem, please contact your IBM support center.
Any how Execution group created.
If i try to deploy a bar file:
BIP1549E: Unable to find required execution group document in the configuration repository.
When deploying configuration data, the document for execution group 'c654d43b-0301-0000-0080-a689f690d13e' could not be found in the configuration repository. Another document has referenced this document, and it is required for the successful completion of the deploy operation. The referencing broker document is of type 'null'.
The execution group document 'c654d43b-0301-0000-0080-a689f690d13e' is not available. This is an internal error. Contact your IBM support center.
No messages on the toolkit event log .
If i try to delete an Execution group:
BIP1549E: Unable to find required execution group document in the configuration repository.
When deploying configuration data, the document for execution group 'c654d43b-0301-0000-0080-a689f690d13e' could not be found in the configuration repository. Another document has referenced this document, and it is required for the successful completion of the deploy operation. The referencing broker document is of type 'null'.
The execution group document 'c654d43b-0301-0000-0080-a689f690d13e' is not available. This is an internal error. Contact your IBM support center.
Execution group deleted.
We see the follwoing informational message every day,
Security policy in the Group policy objects has been applied successfully.
I am not aware of any changes with the system security. I will double check with our system admins.
No application errors at the time of creating an executiongroup,bar deploy or deleating an exectuion group.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Mon May 23, 2005 9:54 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
| Quote: |
| Did you try restarting your ConfigMgr? Are there messages piling up on ConfigMgr SYSTEM.BROKER.* queues? |
Yes, We rebooted also.
I can see messages on SYSTEM.BROKER.EXECUTIONGROUP.REPLY
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Mon May 23, 2005 10:29 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
The following application error might be right before this issue,
( ConfigMgr ) Unprocessable response received by Configuration Manager on input queue SYSTEM.BROKER.ADMIN.REPLY.
A message was received by the Configuration Manager on input queue SYSTEM.BROKER.ADMIN.REPLY, but the message was not a response to an outstanding broker request. Either this message has erroneously appeared on queue SYSTEM.BROKER.ADMIN.REPLY, or a Message Brokers Toolkit user has deployed configuration data to a broker with the 'forced' option which removes details of any outstanding deploy request. The message has been written to the WebSphere Business Integration dead letter queue.
Look at the message on the dead letter queue to establish which application sent the message. If the message was a reply from a broker to which a deploy was subsequently cancelled, then it can be
Dead letter queue had this undelivered message
Any idea?
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon May 23, 2005 10:50 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Stop the configuration manager.
Clear the filled queue.
Start the config mgr.
Open a PMR with IBM.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Mon May 23, 2005 11:24 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Jeff,
No luck with stopping the configuration manager,clear the queue and start the configuration manager.
Finally i got an answer from IBM, saying that the configuration database was correpted.
We don't have any clue why it was correpted. So we need to delete and recreate both broker and configuration with new database tables.
This is a sandbox(Lab server) that's why we don't have any database backup to make things easy.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| Natalia |
| Posted: Tue Apr 04, 2006 4:11 pm Post subject: Please Help!! ( ConfigMgr ) Unprocessable response received |
|
|
Newbie
Joined: 04 Apr 2006
Posts: 5
|
I have ConfigMgr on Win and Broker on Linux Red Hat. Deployment fails with this error:
( ConfigMgr ) Unprocessable response received
by Configuration Manager on input queue 'SYSTEM.BROKER.ADMIN.REPLY'.
A message was received by the Configuration Manager on input queue 'SYSTEM.BROKER.ADMIN.REPLY', but the message was not a response to an outstanding broker request. This message has erroneously appeared on queue 'SYSTEM.BROKER.ADMIN.REPLY'.
The message has been written to the WebSphere MQ dead letter queue. Look at the message on the dead letter queue to establish which application sent the message. If the message was a reply from a broker to which a deploy was subsequently cancelled, then it can be safely ignored. Otherwise correct the application. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 04, 2006 4:13 pm Post subject: Re: Please Help!! ( ConfigMgr ) Unprocessable response recei |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Natalia wrote: |
| Look at the message on the dead letter queue to establish which application sent the message. If the message was a reply from a broker to which a deploy was subsequently cancelled, then it can be safely ignored. Otherwise correct the application. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Natalia |
| Posted: Tue Apr 04, 2006 4:23 pm Post subject: |
|
|
Newbie
Joined: 04 Apr 2006
Posts: 5
|
| I think it was complaining about ConfigMgr, so I re-created everything and will try again in a few minutes. Oh, Thank you for responding... I will let you know. |
|
| Back to top |
|
|
| Natalia |
| Posted: Wed Apr 05, 2006 5:02 am Post subject: Wnen you install MQ you should not specify the domain? |
|
|
Newbie
Joined: 04 Apr 2006
Posts: 5
|
Just to make sure:
You have to be local account on Win and when you insatll MQ, you should not specify any domain controllers, correct?
Still re-installing everything... |
|
| Back to top |
|
|
|
|
