none
Secondary Site Still Pending

    Question

  • Hello.  I have looked through other threads but can't find an answer to my problem.  I am trying to create a secondary site over the wire to a domain controller in one of our districts.  We have done this before multiple times without failure.  But this time it just sits at Pending.  Some files copy to that server (SMS_Bootstrap.ini & SMS_Bootstrap.log), but that is it.  Here is the sender log file:

    Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes SMS_LAN_SENDER 11/11/2009 9:57:25 AM 3660 (0x0E4C)

    Passed the xmit file test, use the existing connection SMS_LAN_SENDER 11/11/2009 9:57:26 AM 41212 (0xA0FC)

    No package file, must be a site deinstall or a CD-based remote secondary site setup or upgrade or a monitoring job. SMS_LAN_SENDER 11/11/2009 9:57:26 AM 41212 (0xA0FC)

    Passed the xmit file test, use the existing connection SMS_LAN_SENDER 11/11/2009 9:57:26 AM 42836 (0xA754)

    No package file, must be a site deinstall or a CD-based remote secondary site setup or upgrade or a monitoring job. SMS_LAN_SENDER 11/11/2009 9:57:26 AM 42836 (0xA754)

    Cannot create the bootstrap ini file as \\STLSRV\D$\SMS_BOOTSTRAP.INI, Win32 error = 32 SMS_LAN_SENDER 11/11/2009 9:57:26 AM 42836 (0xA754)

    STATMSG: ID=3505 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_LAN_SENDER" SYS=SCCM SITE=FDL PID=2116 TID=42836 GMTDATE=Wed Nov 11 15:57:26.152 2009 ISTR0="STL"
    ISTR1="STLSRV" ISTR2="\\STLSRV\D$\SMS_BOOTSTRAP.INI" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_LAN_SENDER 
    11/11/2009 9:57:26 AM 42836 (0xA754)

    Restart time = 11/11/09 10:07:26 Central Standard Time SMS_LAN_SENDER 11/11/2009 9:57:26 AM 42836 (0xA754)

    Cannot retrieve the service account from the remote site server STLSRV SMS_LAN_SENDER 11/11/2009 9:57:26 AM 41212 (0xA0FC)

    Restart time = 11/11/09 10:07:26 Central Standard Time SMS_LAN_SENDER 11/11/2009 9:57:26 AM 41212 (0xA0FC)

    We have 0 active connections SMS_LAN_SENDER 11/11/2009 9:57:30 AM 3660 (0x0E4C)

    Checking for sending capacity.  Used 0 out of 5. SMS_LAN_SENDER 11/11/2009 9:57:30 AM 3660 (0x0E4C)

    Connecting to C:\Program Files\Microsoft Configuration Manager\inboxes\schedule.box\outboxes\LAN. SMS_LAN_SENDER 11/11/2009 9:57:30 AM 3660 (0x0E4C)

    No (more) send requests found to process. SMS_LAN_SENDER 11/11/2009 9:57:30 AM 3660 (0x0E4C)

    Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes SMS_LAN_SENDER 11/11/2009 9:57:30 AM 3660 (0x0E4C)

    We have 0 active connections SMS_LAN_SENDER 11/11/2009 9:57:30 AM 3660 (0x0E4C)

    Checking for sending capacity.  Used 0 out of 5. SMS_LAN_SENDER 11/11/2009 9:57:30 AM 3660 (0x0E4C)

    Connecting to C:\Program Files\Microsoft Configuration Manager\inboxes\schedule.box\outboxes\LAN. SMS_LAN_SENDER 11/11/2009 9:57:30 AM 3660 (0x0E4C)

    No (more) send requests found to process. SMS_LAN_SENDER 11/11/2009 9:57:30 AM 3660 (0x0E4C)

    Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes SMS_LAN_SENDER 11/11/2009 9:57:30 AM 3660 (0x0E4C)

    We have 0 active connections SMS_LAN_SENDER 11/11/2009 9:57:35 AM 3660 (0x0E4C)

    Checking for sending capacity.  Used 0 out of 5. SMS_LAN_SENDER 11/11/2009 9:57:35 AM 3660 (0x0E4C)

    Connecting to C:\Program Files\Microsoft Configuration Manager\inboxes\schedule.box\outboxes\LAN. SMS_LAN_SENDER 11/11/2009 9:57:35 AM 3660 (0x0E4C)

    No (more) send requests found to process. SMS_LAN_SENDER 11/11/2009 9:57:35 AM 3660 (0x0E4C)

    Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes SMS_LAN_SENDER 11/11/2009 9:57:35 AM 3660 (0x0E4C)

    Wednesday, November 11, 2009 4:05 PM

Answers

  • Usually when secondary sites stay pending it's because you didn't grant the two servers the appropriate permissions on one another. Since you are using a domain controller as a secondary site I assume your primary has to be in the domain admins group since that's the only way to grant local admins on a DC. Personally I would NEVER use a DC as a secondary site server.

    You must add the computer account of the primary site server to the local Administrators group on the new secondary site server computer before performing this procedure. Alternatively, you can use an account with administrative permissions in the address properties to the secondary site server computer

    http://technet.microsoft.com/en-us/library/bb633289.aspx

    http://technet.microsoft.com/en-us/library/bb632850.aspx


    John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
    • Proposed as answer by Abhishek.Joshi Thursday, November 12, 2009 3:52 AM
    • Marked as answer by Jie-Feng Ren Friday, November 27, 2009 1:37 PM
    Thursday, November 12, 2009 1:51 AM
    Moderator

All replies

  • Hi,

    Do you have any errors in the hman.log file. It will report errors related to creating the secondary site package.
    Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
    Wednesday, November 11, 2009 6:26 PM
    Moderator
  • STATMSG: ID=3505 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_LAN_SENDER" SYS=SCCM SITE=FDL PID=2116 TID=42836 GMTDATE=Wed Nov 11 15:57:26.152 2009 ISTR0="STL"
    ISTR1="STLSRV" ISTR2="\\STLSRV\D$\SMS_BOOTSTRAP.INI" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_LAN_SENDER 

    can you check ... what is this 3505 message id?

    Also  hopeing that there is no issue of DNS and network connectivity
    Abhishek Joshi http://blogcastrepository.com/blogs/abi/default.aspx http://blogcastrepository.com/members/Abhishek.aspx
    Wednesday, November 11, 2009 9:03 PM
  • Usually when secondary sites stay pending it's because you didn't grant the two servers the appropriate permissions on one another. Since you are using a domain controller as a secondary site I assume your primary has to be in the domain admins group since that's the only way to grant local admins on a DC. Personally I would NEVER use a DC as a secondary site server.

    You must add the computer account of the primary site server to the local Administrators group on the new secondary site server computer before performing this procedure. Alternatively, you can use an account with administrative permissions in the address properties to the secondary site server computer

    http://technet.microsoft.com/en-us/library/bb633289.aspx

    http://technet.microsoft.com/en-us/library/bb632850.aspx


    John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
    • Proposed as answer by Abhishek.Joshi Thursday, November 12, 2009 3:52 AM
    • Marked as answer by Jie-Feng Ren Friday, November 27, 2009 1:37 PM
    Thursday, November 12, 2009 1:51 AM
    Moderator
  • Besides, you need to check despool.log to see if any error prompt. Check if the second site cannot pulish its site imformation to AD domain service. You also need to grand secondary site computer account full permission to system management container.

    http://technet.microsoft.com/en-us/library/bb632591.aspx

    HTH.


    Jie-Feng Ren - MSFT
    Thursday, November 12, 2009 9:53 AM
  • Well I tried a complete deinstall, rebooted potential secondary site (domain controller), cleaned up the files that the initial install had placed on that server.  Then I tried to add a new secondary site again, same results.  Since this secondary site is a domain controller, and the primary site computer is a member of domain admins, I can't figure out why this doesn't work.  We haven't done anything different from the other 6 secondary sites that we have.  Any other log files I can look at to help determine why this won't work?  We really need to get this secondary site up and running.  Thanks again for all of your help thus far.

    Curt
    Thursday, November 12, 2009 1:14 PM
  • Check if the second site cannot pulish its site imformation to AD domain service. You also need to grand secondary site computer account full permission to system management container.

    neither of these will keep the install from completing.


    John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
    Thursday, November 12, 2009 3:00 PM
    Moderator
  • Have you managed to make any progress on this cdehaan?? I have what seems to be the exact same problem, initiate the install using the push method and it reports that it could not create the BOOTSTRAP.INI file and that it could not locate the remote service account. All this is popping up in the sender.log

    BOOTSTRAP.INI file does get created and parent computer account is in the domain admins group. All looks as should be but for some reason not working.
    Wednesday, November 18, 2009 2:54 AM
  • As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios.

     If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.

     In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.

     Thanks!


    Jie-Feng Ren - MSFT
    Friday, November 27, 2009 1:37 PM
  • Check if the second site cannot pulish its site imformation to AD domain service. You also need to grand secondary site computer account full permission to system management container.

    neither of these will keep the install from completing.


    John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum


    As Jie says, you need to give permissions over the Systems Management container. Although the installation will complete, the communications won't. The Hman.log file on the secondary site server will show that the secondary site server is failing to create the necessary objects in the Systems Management container. Upon creating the permissions, the component will, on its next cycle, create the objects and eventually the secondary site server will no longer show as pending.

    Tuesday, January 25, 2011 6:54 PM