| Author |
Message
|
| venkat kurra |
 Posted: Thu Apr 20, 2006 9:04 am Post subject: Configuration Manager service ID for WBIMB 5.0 |
 |
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
We created the configuration manager(WBIMB) with a local ID on Windows 2003 server. The service has been running for couple of months with out any issue.
As documented that ID is a member of all necessary groups.
Last week we installed Support Pack1 for Windows 2003.
All of the sudden the toolkit getting authorization errors and found a security error in the Application log(Event Viewer),
( ConfigMgr ) Error in call NetUserGetLocalGroups() to the NT security domain with return code 1722.
A component of WebSphere Business Integration Message Brokers is attempting to call the NT security domain. The security subsystem returned an error code.
Check NT security subsystem documentation for the reported error. Restart the relevant service component (UserNameServer, or Configuration Manager). Ensure that a Domain Controller, either Primary or Backup, is available.
We could not stop the service(Stopping for ever) and finally killed bip service. When we start the service, it may works for couple of hours and fails or failing immediately. It's not consistent.
IBM recommended to use domain-id instead of local. Then I changed the configuration manager service runs under a domain-ID. So far so good.
There should be a problem with local-id Vs Win2K3 SP1.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Apr 20, 2006 9:12 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I've heard rumors before of this happening to other people... But only rumors, I don't have anything more specific.
Did you try applying FP7 of WMBIMB?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Thu Apr 20, 2006 9:28 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
| Quote: |
| Did you try applying FP7 of WMBIMB? |
No, We have stable environment(we feel) with CSD4.
Don't want to tuch the product unless we have to upgrade to add new features or to resolve un-covered issues.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 20, 2006 9:53 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
But you felt it important to update Windows...?
It's just as important to update Broker to newer FixPacks as it is your Operating System, and for exactly the same reasons.
I can't say for sure that applying FP7 will fix this and allow you to use a local user again - but it's at least somewhat likely.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Thu Apr 20, 2006 10:23 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Jeff,
Server(Windows) team install Microsoft Patch in a monthly basis. They are up to date to protect windows servers from out side world(virus) or to support latest applications.
When we open a cahnge for the upgrade then the first question is Why do we need this?
If we make the change(WMQ/WBIMB) it will impact all our customers(100s of application). We know that the new version should work like before.
Even we will not go forward with production releases/dead lines and other application changes. Getting an outage date and work with all application areas is a big deal.
That's why we should show some thing why we are going to the latest version. Most of the time we open a ticket for IBM and get some answer says about " CSDx or Refresh pack y or hot fix z fix the problem".
IBM resolution for Configuration Manager security error is to cahnge the service ID(domain-id). It's a simple change to fix the issue.
One day FP7 may be a soultion for some other issue and then we will be upgraded to the latest version.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 20, 2006 10:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So your organization has different standards for upgrading OSes than they do applications. OSes get upgraded on general principles, and applications only get upgraded for some specific reason or another.
Running the risk of an outage that is directly related to not having an application fix in place, that affects all of your customers, is acceptable to your management.
And running the risk that an OS update made "just because" could break your applications and affect all your customers is also acceptable to your management.
But running the risk that an application fix made "just because" could break your applications and affect all your customers is not acceptable to your management. The same risk, however, when you have a specific fix in mind, is acceptable to your management.
I guess we can see why I'm not in management.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
