Re: Installing a Secondary Site Fails

From: Luke Packard [MSFT] (lukep_at_online.microsoft.com)
Date: 12/30/04


Date: Thu, 30 Dec 2004 13:21:56 -0800

SMS can't resolve the name. Are you in advanced or standard security? Open
a cmd prompt under the context of the SMS Service account. If you're using
advanced security it is the machine account and you'll have to use a tool
like cmdasuser (search the net for it). From the cmd prompt can you
successfully connect to \\TPChicago\C$? If you still get error 53 then can
you ping TPChicago from the same cmd prompt? If not, you've got a name
resolution issue and should check to see if the system address is correct in
the netbios cache and in WINS. If this all checks out, restart SMS
Executive on the site server and see if you get the same errors. Please
report your findings.

-- 
Luke Packard [MSFT]
SMS 2003 Technical FAQ:
http://www.microsoft.com/technet/prodtechnol/sms/sms2003/techfaq/default.mspx
This posting is provided "AS IS" with no warranties, and confers no rights.
"dgw" <dgw@discussions.microsoft.com> wrote in message 
news:D5857129-B5FE-497A-832E-D024A90FF8F6@microsoft.com...
> Any other ideas?  I did what was suggested and still no luck.
>
> Thanks for the help.
>
> "Na Li" wrote:
>
>> In advanced security, the service account is the primary site's machine
>> account. You can use the following command line at the secondary site 
>> server
>> to grant it admin rights on secondary site server:
>>
>> net localgroup administrators /domain\primarysiteservercomputer name$ 
>> /add
>>
>> Thx.
>>
>> -- 
>> Na Li (MSFT)
>> nali@microsoft.com
>> Systems Management Server Group
>> --This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "dgw" <dgw@discussions.microsoft.com> wrote in message
>> news:611AED6D-E7E7-4011-B15E-2EFFC8F4A771@microsoft.com...
>> > What is the name of the service account?  The domain admin account that
>> the
>> > primary site is on has Admin rights to the secondary site server.  I 
>> > have
>> > cleared up all the errors.  The Primary site could not find the 
>> > Secondary
>> > site.  I am still getting the "Pending" state in my admin console for 
>> > the
>> > Secondary Site. I can connect to the admin share c$ from my primary 
>> > site.
>> >
>> > "dgw" wrote:
>> >
>> > > I am trying to install a sms 2003 sp1 secondary site remotely.  I 
>> > > have
>> tried
>> > > pushing the files over the WAN and by copying the setup folder to the
>> remote
>> > > machine.  I am having no luck.  In the admin console for my primary 
>> > > site
>> all
>> > > when I try to install the secondary site the "state" says pending. I 
>> > > am
>> using
>> > > advanced mode security.
>> > > Here is an error I am gettin in my sender log.  Is this the problem? 
>> > > If
>> so
>> > > what is the solution?
>> > >
>> > >
>> > > Created sending thread (Thread ID = 15EC) SMS_LAN_SENDER 12/29/2004
>> 11:07:40
>> > > AM 5384 (0x1508)
>> > > Trying the No. 1 address (out of 1) SMS_LAN_SENDER 12/29/2004 
>> > > 11:07:40
>> > > AM 5612 (0x15EC)
>> > > gethostbyname failed on TPChicago, WSA error =
>> > > 11001 SMS_LAN_SENDER 12/29/2004 11:07:42 AM 5612 (0x15EC)
>> > > Cannot retrieve the FQDN of server TPChicago from AD, Win32 error =
>> > > 53 SMS_LAN_SENDER 12/29/2004 11:07:44 AM 5612 (0x15EC)
>> > > There is no existing connection, Win32 error = 53 SMS_LAN_SENDER
>> 12/29/2004
>> > > 11:07:44 AM 5612 (0x15EC)
>> > > There is no existing connection, Win32 error = 53 SMS_LAN_SENDER
>> 12/29/2004
>> > > 11:07:44 AM 5612 (0x15EC)
>> > > Error during connection to \\TPChicago\C$ (53). SMS_LAN_SENDER
>> 12/29/2004
>> > > 11:07:44 AM 5612 (0x15EC)
>> > > Error is considered fatal. SMS_LAN_SENDER 12/29/2004 11:07:44 AM 5612
>> (0x15EC)
>> > > Cannot connect to server TPChicago at remote site CHI, won't try send
>> > > requests going to site CHI for an hour or until there are no active 
>> > > send
>> > > requests. SMS_LAN_SENDER 12/29/2004 11:07:44 AM 5612 (0x15EC)
>> > > Could not establish connection. SMS_LAN_SENDER 12/29/2004 11:07:44 AM
>> 5612
>> > > (0x15EC)
>> > > Attempt to connect failed. SMS_LAN_SENDER 12/29/2004 11:07:44 AM 5612
>> (0x15EC)
>> > >
>> > >
>>
>>
>> 


Relevant Pages

  • Re: SMS2003 Service Account Password Change
    ... You will see the SMS ... You state below that you are running your site in Advanced Security mode. ... You will read in this document that the SMS Service account is only required ... in Standard Security in SMS 2003 and not needed if you are running Advanced ...
    (microsoft.public.sms.admin)
  • Re: Admin Console Blank
    ... It "looks like" there is a security problem with the the user accessing the ... user to the SMD Admin group, but have you given the user any permissions to ... read SMS information? ... >>> from the remote consoles. ...
    (microsoft.public.sms.admin)
  • Re: Change SMS Service Account password
    ... > SMS administrator console to change all the passwords for the secondary ... there was a knowledge base article or a security white ... paper that recommended creating a second sms service account. ... you can change the password on smssvc1. ...
    (microsoft.public.sms.admin)
  • Re: Admin Console Blank
    ... The error message means "Access Denied" from WMI. ... Can you access to SMS namespace? ... Go to Security page. ... >> On the Admin UI console, ...
    (microsoft.public.sms.admin)
  • Re: Multiple Primary Sites in One Domain
    ... The schema is already extened so that shouldn't be an issue. ... > if you want to change the site architecture just for SMS.) ... > Phil, to install you do not require domain admin, schema admin, or ... > security) or the SMS service account full control to ...
    (microsoft.public.sms.setup)