Re: Site Component Manager used by two sites

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

The most common mistake which causes this, is incorrectly configured
senders.

There are 2 things to configure for site-to-site:
1) Senders, and
2) Addresses.

Sender should be the Site Server itself.
Addresses should be the destination site.

If you configure a sender with the destination site netbios name, you will
end up with this error. Go to "Site -> Hierarchy -> Site Code -> Site
Settings -> Senders"; and remove all senders, but the one on the Site
Server.

--

Thanks,
David James [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.



"Kim Oppalfens" <kim@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:MPG.1d2b0c698e9905c9989f95@xxxxxxxxxxxxxxxxxxxxxxx
> In article <08945070-1061-483A-88A9-E55100224C22@xxxxxxxxxxxxx>,
> ITCSMS@xxxxxxxxxxxxxxxxxxxxxxxxx says...
>> Hi,
>>
>> Can someone please explain and help me how to solve this error message
>> (below) appearing from a primary site server which I'm trying to connect
>> to
>> the Central Parent Site?
>>
>> ************************************************************
>>
>> Central-Site Server Name: SMSCENT01
>> Site Code: CEN
>>
>> Primary Site Server Name: SMSPRI01
>> Site Code: PRI
>>
>> System Status Message from Primary site:
>>
>> Component: SMS_SITE_COMPONENT_MANAGER
>> Site Code: PRI
>> Severity: Error
>>
>> Message1 (ID 1048):
>>
>> SMS Site Component Manager detected that site system "\\SMSCENT01" is
>> currently in use by SMS site CEN.
>>
>> Possible cause: You accidentally configured SMS to use this site system
>> as
>> part of this site and as part of site CEN.
>> Solution: Remove this site system from the list of site systems for this
>> site or for site SUV. The list appears in the Site Systems node of the
>> SMS
>> Administrator console.
>>
>> Message2 (ID 1028)
>>
>> SMS Site Component Manager failed to configure site system "\\SMSCENT01"
>> to
>> receive SMS server components.
>>
>> ***********************************************************
>>
>> Thanks
>>
>>
> Seems like you are trying to make one site system perform roles in 2
> different sites, without a more detailed explanation of what you are
> doing it is a bit difficult to help you any further. Since this,
> according to your post, seems to be related to connecting 2 sites
> together I am guessing that you are somehow misconfiguring your sender,
> but that is just a guess.
>
> --
> Kim Oppalfens
> MVP SMS
> Computacenter Belgium


.

Relevant Pages

  • Re: Site system on remote DC and machine accounts
    ... Did you verify outside SMS that the site server machine account can access ... to open a cmd prompt under localy system and then do a net use to the admin$ ... > I want to install site system roles on this remote Ad 2003 DC, ...
    (microsoft.public.sms.setup)
  • Adding a second Site Server on A DC
    ... I have my primary SMS 2003 Site server on a DC, ... The are groups SMS created in AD, ... The site system is turned off, not connected to the network, ... configured to use Advanced Security, then the Site Server's machine account ...
    (microsoft.public.sms.admin)
  • Re: Bandwidth Limits
    ... SMS perfmon counters: ... The total number of bytes this sender has attempted to send since it began ... |>> Where, the site server, or remote machine? ...
    (microsoft.public.sms.admin)
  • Re: Bandwidth throttling
    ... throttling on a standard SMS 2003 sender works between the site server and distribution point server 1/2 way around the globe.. ... sms 2003 doesn't use the standard sender from the site server to the dp. ...
    (microsoft.public.sms.setup)
  • Re: Service Manager (2003) Not Starting - Unable to communicate w/site
    ... > with the Service Manager - "unable to communicate with site server". ... It shows errors with the Site System ... It shows the account attempting to log on to the ... > *thought* that the SMS Service account would be used for the site server ...
    (microsoft.public.sms.setup)