| Author |
Message
|
| donovang |
 Posted: Tue Nov 06, 2001 10:22 am Post subject: |
 |
|
Newbie
Joined: 23 Aug 2001
Posts: 9
Location: Ireland
|
I'm getting BIP1536 when deploying to a broker. The deploy appears OK, I get bips 2056,4040 and 4045 first, but the 1536 after... This is on MQSI V2.0.2, config manager on NT and broker on Solaris.
Full Error text is :
BIP1536S: Configuration Manager unable to register for internal subscriptions with broker QM2.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker QM2 was not successful. This means that the Control Center Operations view may not reliably show the correct status of the resources assigned to broker QM2. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem.
Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before attempting to deploy to this broker again. If this problem persists, contact your IBM support center.
I deleted the broker from control centre and the physical broker and recreated them, but the problem persisted.
Any help appreciated........ |
|
| Back to top |
|
 |
| shcherb |
| Posted: Wed Nov 14, 2001 7:40 am Post subject: |
|
|
Apprentice
Joined: 12 Sep 2001
Posts: 34
|
Hi,
I got the same error on Windows NT 4.0 Server after several BIP2066. Is it internal support for this product available at all ?
Vladimir |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Nov 14, 2001 3:03 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I just checked one of our internal databases, and the BIP1536 pointed to the UserName server and permissions not being setup correctly. If you are running a UserName server, I'd start looking there to make sure things are configured correctly. Hope this helps. |
|
| Back to top |
|
|
| donovang |
| Posted: Fri Nov 16, 2001 5:24 am Post subject: |
|
|
Newbie
Joined: 23 Aug 2001
Posts: 9
Location: Ireland
|
| We're not using Pub/Sub, so we don't have a UserName Server. IBM are helping us out with this directly, so I'll update if I get a resolution.... |
|
| Back to top |
|
|
| TonyD |
| Posted: Fri Nov 16, 2001 6:44 am Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
| I think there was a reference in the 'Problem Solving' Supportpac to this message. |
|
| Back to top |
|
|
| hutulas |
| Posted: Mon Nov 19, 2001 5:43 am Post subject: |
|
|
Newbie
Joined: 18 Nov 2001
Posts: 5
|
We had a similar problem and fixed it by having the same userid on the NT Configuration manager as the userid that the broker is using on UNIX.
Hope this helps
Scott H. |
|
| Back to top |
|
|
| donovang |
| Posted: Thu Nov 22, 2001 5:59 am Post subject: |
|
|
Newbie
Joined: 23 Aug 2001
Posts: 9
Location: Ireland
|
| It looks like the case of the username that is running our config manager was the problem. It was put in as uppercase in NT and lowercase on unix. We created the same username in uppercase on the SunOS machine and redeployed without getting the error message. |
|
| Back to top |
|
|
|
|
