RE: Weird Errors on Primary Site server and Central Site Server

On the Central site server, I have a entry for the child site The role for
this chield site is "SMS Compoanant Server", when I try to double click on
it, it syas that "Systems Management Server has lost a connection to the Site
server".

The same the other way, on the child, there is a entry for the central site
server, central site server also listed as a "SMS Compoanant Server".

How do I remove it?

Is it to do with the senders, under central, there is a sender for itself
AND the clhild server, also the other way around.

Thanks

"Sherry Kissinger [MVP-SMS]" wrote:

This is just a guess. Check Site Hierarchy, Central, Site Settings, Site
Systems. You should NOT have an entry for the child

Check Site Hierarchy, Child site(s), Site Settings, Site Systems. You should
NOT have an entry for the Central.

At least one of your errors looks like one of your sites is trying to
install SMS Components on a server which is already defined elsewhere in your
hierarchy.
--
Standarize. Simplify. Automate.


"Hens" wrote:

Hi All,

I have a central and primary site server, for some odd reason, it is
generating errors and I don’t know what to do anymore. The primary site
server is called PSS and central site server is called CSS. On the primary
site server, it is generating the following 2 errors every 2 hours on the
SMS_SITE_COMPONENT_MANGER:

ERROR1:
SMS Site Component Manager failed to configure site system
"\\centralsiteserver" to receive SMS server components.

Solution: Review the previous status messages to determine the exact reason
for the failure. SMS Site Component Manager cannot install any SMS server
components on this site system until the site system is configured
successfully. SMS Site Component Manager will automatically retry this
operation in 60 minutes. To force SMS Site Component Manager to immediately
retry this operation, stop and restart SMS Site Component Manager using the
SMS Service Manager.

ERROR2:
SMS Site Component Manager detected that site system "\\centralsiteserver "
is currently in use by SMS site CSS.

Possible cause: You accidentally configured SMS to use this site system as
part of this site and as part of site CSS.
Solution: Remove this site system from the list of site systems for this
site or for site CSS. The list appears in the Site Systems node of the SMS
Administrator console.

What I find very strange, if I go to the primary site server’s Site systems,
the primary site server is listed, but only shows the role of the central
sites server as SMS Component Server, if I double click on the central site
server, it tells me that “Systems Management Server has lost a connection the
site server”. This happens the other way around as well, on the central site
server, it shows the primary site server (PSS) as a SMS component server, but
get the same error when I try to open the properties of the primary site
server.

Data flows fine from the primary to the central.


On the actual cetral site server, I get the following errors on
SMS_SERVER_LOCATOR_POINT:

ERROR1:
SMS Site Component Manager successfully used the
SMS_SERVER_BOOTSTRAP_CENTRALSITESERVERservice to run the following program on
site system "\\centralsiteserver":

D:\SMS\bin\i386\slpsetup.exe /install /siteserver:centralsiteserver

The program failed for the following reason:

Child process "D:\SMS\bin\i386\slpsetup.exe /install
/siteserver:centralsiteserver /s" took too long to execute, and the process
(PID = 4320) was orphaned.

Possible cause: SMS Site Component Manager does not have sufficient access
rights to administer the site system.
Solution: Verify that the Site System Connection accounts are properly
configured to allow SMS to administer the site system.

SMS Site Component Manager cannot install component SMS_SERVER_LOCATOR_POINT
until the program runs successfully. If this problem persists and you cannot
fix it, refer to your SMS documentation or the Microsoft Knowledge Base for
further troubleshooting information.

ERROR2:
SMS Site Component Manager failed to reinstall this component on this site
system.

Solution: Review the previous status messages to determine the exact reason
for the failure. SMS Site Component Manager will automatically retry the
reinstallation in 60 minutes. To force SMS Site Component Manager to
immediately retry the reinstallation, stop and restart SMS Site Component
Manager using the SMS Service Manager.


Can anyone please help me?

Thanks a million

.

Relevant Pages

  • RE: Advanced client cannot auto discover management point
    ... then was to delete the site boundary from the central site and correctly ... have SMS clients that are getting site assignments, ... child site server. ...
    (microsoft.public.sms.admin)
  • RE: Automatic site code discovery was unsuccessful
    ... Have you looked in WINS yet for that SLP entry? ... we encountered an issue here that our clients in the central site cannot ... That's a server from the US and ... Those are two totally different SMS systems. ...
    (microsoft.public.sms.admin)
  • RE: Automatic site code discovery was unsuccessful
    ... I also checked WINS and even re-registered the server in there. ... Even though I thought with SMS 2003 SP3 and extended AD and advanced ... we encountered an issue here that our clients in the central site cannot ... auto discover the site code anymore. ...
    (microsoft.public.sms.admin)
  • RE: Automatic site code discovery was unsuccessful
    ... I also checked WINS and even re-registered the server in there. ... Even though I thought with SMS 2003 SP3 and extended AD and advanced ... we encountered an issue here that our clients in the central site cannot ... auto discover the site code anymore. ...
    (microsoft.public.sms.admin)
  • RE: Automatic site code discovery was unsuccessful
    ... I also checked WINS and even re-registered the server in there. ... Even though I thought with SMS 2003 SP3 and extended AD and advanced ... we encountered an issue here that our clients in the central site cannot ... auto discover the site code anymore. ...
    (microsoft.public.sms.admin)