MP and SLP Active Directory Update problem

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

From: news.unisource.ch (a_at_b.com)
Date: 08/29/04

Next message: John Bell: "Re: security templates"
Previous message: Henry C: "Re: Rename Windows computer name. What happens to SMS2.0SP5 client ?"
Next in thread: Kim Oppalfens: "Re: MP and SLP Active Directory Update problem"
Reply: Kim Oppalfens: "Re: MP and SLP Active Directory Update problem"
Messages sorted by: [ date ] [ thread ]

Date: Sun, 29 Aug 2004 16:12:57 +0200

In the sitecomp Logs a habe the following mistake:

  Checking configuration information for server: SMS01.
SMS_SITE_COMPONENT_MANAGER 29.08.2004 16:09:38 1996 (0x07CC)
    SMS01 is the Default MP. SMS_SITE_COMPONENT_MANAGER 29.08.2004 16:09:38
1996 (0x07CC)
    MP Configuration for SMS01 is correct. SMS_SITE_COMPONENT_MANAGER
29.08.2004 16:09:38 1996 (0x07CC)
    Publishing SMS01 as a Management Point into Active Directory.
SMS_SITE_COMPONENT_MANAGER 29.08.2004 16:09:38 1996 (0x07CC)
    SMS-MP-SNL-SMS01 could not be updated, Win32 error = 5
SMS_SITE_COMPONENT_MANAGER 29.08.2004 16:09:38 1996 (0x07CC)
STATMSG: ID=4912 SEV=E LEV=M SOURCE="SMS Server"
COMP="SMS_SITE_COMPONENT_MANAGER" SYS=SMS01 SITE=SNL PID=1984 TID=1996
GMTDATE=Sun Aug 29 14:09:38.636 2004 ISTR0="cn=SMS-MP-SNL-SMS01" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
NUMATTRS=0 SMS_SITE_COMPONENT_MANAGER 29.08.2004 16:09:38 1996 (0x07CC)
    SLP Configuration for SMS01 is correct. SMS_SITE_COMPONENT_MANAGER
29.08.2004 16:09:38 1996 (0x07CC)
    Publishing SMS01 as an SLP into Active Directory.
SMS_SITE_COMPONENT_MANAGER 29.08.2004 16:09:38 1996 (0x07CC)
    SLP Class SMS-SLP-SNL-SMS01 already exists. Updating
SMS_SITE_COMPONENT_MANAGER 29.08.2004 16:09:38 1996 (0x07CC)
    SMS-SLP-SNL-SMS01 could not be updated, error 5.
SMS_SITE_COMPONENT_MANAGER 29.08.2004 16:09:38 1996 (0x07CC)
STATMSG: ID=4912 SEV=E LEV=M SOURCE="SMS Server"
COMP="SMS_SITE_COMPONENT_MANAGER" SYS=SMS01 SITE=SNL PID=1984 TID=1996
GMTDATE=Sun Aug 29 14:09:38.651 2004 ISTR0="cn=SMS-SLP-SNL-SMS01" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
NUMATTRS=0 SMS_SITE_COMPONENT_MANAGER 29.08.2004 16:09:38 1996 (0x07CC)

Why can't the server updated the records? The Admins und the system have
full control on the objects and containers... any idea?

Thanks

Marel

Next message: John Bell: "Re: security templates"
Previous message: Henry C: "Re: Rename Windows computer name. What happens to SMS2.0SP5 client ?"
Next in thread: Kim Oppalfens: "Re: MP and SLP Active Directory Update problem"
Reply: Kim Oppalfens: "Re: MP and SLP Active Directory Update problem"
Messages sorted by: [ date ] [ thread ]

Relevant Pages

Re: 2003 Migration
... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
(microsoft.public.windows.server.active_directory)
Re: i got 6 server in company which contains NT4 , windows 2000 , windowser 2003
... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
(microsoft.public.windows.server.active_directory)
Re: Urgent Advise - [WildPacket]
... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
(microsoft.public.windows.server.active_directory)
Re: NT to W2K3 Migration
... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
(microsoft.public.windows.server.active_directory)
Re: NT to W2K3 Migration
... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ... ensure that you have designed a DNS ...
(microsoft.public.windows.server.active_directory)