Re: Error 4912 in SMS Hiearchy Manager and Site Components

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Mark McClure (mrkmcclure_at_excite.com)
Date: 04/06/04 

Date: Tue, 06 Apr 2004 18:01:57 -0400

Does it make sense that he would not have extended the schema when it
is trying to "change an already existing object?"

I had the same issue and it turned out that the SLP folder under
SYSTEM MANAGEMENT needed rights added to it after SMS created it. The
rights didn't pass through for some reason.

- Mark

On Thu, 4 Mar 2004 14:40:01 -0800, "Jeff Harbaugh [MSFT]"
<jeffharb@online.microsoft.com> wrote:

>These errors indicate that you do not have your AD Schema Extended. If you
>are in AD you can run extadsch.exe from the bin\i386 directory. Make sure
>the user running it has schema admin rights. Also you need to make sure your
>AD has allow schema updates. If you are not in ad you can ignore. Also if
>you wish to not extend the ad schema you can ignore this warnings. They are
>only warnings and not errors.
>
>--
>Thanks
>Jeff Harbaugh [MSFT]
>
>This posting is provided "AS IS" with no warranties, and confers no rights.
>
>"DanO" <anonymous@discussions.microsoft.com> wrote in message
>news:71c501c40227$e5100930$a401280a@phx.gbl...
>> Hello Everyone,
>>
>> TIA for any help I get on this issue.
>>
>> I am attempting to install SMS 2003 for evaluation
>> purposes. However, after the install has completed, I
>> looked at the Site Status, component status, and I have
>> two critical errors. Hiearchy manager has twelve errors,
>> Site Components has eleven.
>>
>> Error type = Milestone
>> Error message= 4912
>>
>> Description is:
>> Systems Management Server cannot update the already
>> existing object "cn=SMS-SLP-NMS-DEXTER" in Active
>> Directory.
>>
>> On the DC, I checked security settings and I have full
>> control for the 'cn=SMS-SLP-NMS-DEXTER' object for both
>> the local machine account and the current user I am logged
>> in as. In fact, I even temporarily added the system and
>> user accounts Domain Admins group to try and ensure that
>> security was not keeping me out, but it didn't help.
>>
>> Any ideas?
>>
>> Thanks!
>> DanO
>>

Relevant Pages

  • Re: Trouble Extending Schema
    ... Schema master using the Schema admin account. ... I really don't think it's an issue with permissions here. ... > I'm trying to find out why it won't let me extend the directory. ... > correct permission when creating the SMS System Management container. ...
    (microsoft.public.sms.setup)
  • Re: HELP!! Weird SMS SP2 problem
    ... Managament container (you must extend the schema to use it). ... SMS services. ... more than creating the System Management container. ...
    (microsoft.public.sms.setup)
  • Re: SMS 2003 sp3 Hardware and Software Inventories Not Taking Plac
    ... in with an ID which has the rights to extend the schema. ... I've usually run it from the member server which was destined to be the SMS/configmgr server. ... company out there blew up their AD with a schema extension and something hit the fan somewhere, so all documentation regarding schema extensions had to have these paranoia steps put in. ... the only other thing is to confirm that your ConfigMgr server has rights to the System Management ou in AD Users and computers. ...
    (microsoft.public.sms.inventory)
  • RE: Component Status Errors
    ... If you have not extended the schema, I would go to the SMS Management ... un check each box for each component), extend the schema and then re-install ... > "System Management" container, and all child objects in Active Directory. ...
    (microsoft.public.sms.setup)
  • Re: upgrade a Windows 2003 DC to R2
    ... >> when doing adprep forestprep. ... >> A previous schema extension has defined the attribute value as ... >> Adprep cannot extend your existing schema ...
    (microsoft.public.windows.server.active_directory)