Secondary Site installs to wrong server!
-
Monday, March 12, 2012 4:50 PM
Hello Everyone,
I have a secondary site that was originally installed onto a DC (SITESERVERDC), later due to space constraints a second server was added to the same secondary site to act as the DP (SITESERVERCCM). I needed to upgrade SITESERVERDC from 2k3 to 2k8r2. Since the pyshical site was connected to the primary via fiber I de-installed (deleted) the site so that I could remove the SITESERVERDC from the mix. Once the upgrade was complent I re-created the site and set it to install to SITESERVERCCM.
- When the secondary site installs it installs to SITESERVERDC!?!?!
- The Secondary Site status never changes from "Pending"
- I see smsexec.exe and sitecomp.exe installed and running on SITESERVERDC
- I see nothing happen on SITESERVERCCM
- I have trying copying the sitectr file manually to the Primary server, this changes the status to active but the server will not respond to any other config cmds or component installs.
I'm baffled! I have ensured DNS and other IP connectivity. I hope someone out there has some ideas.
Thanks,
Patrick
All Replies
-
Monday, March 12, 2012 5:07 PMModeratorCheck the sender.log despool.log and hman.log on both site servers. Also check the secure key exhange settings.
Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund
-
Monday, March 12, 2012 5:27 PM
I see the boot strapper copy occur in sender.log to the wrong server. There are no errors or attempts to copy anything to the SITESERVERCCM.
I also see no errors in the hman.log
As far as secure key exhange our SCCM install does not use native mode and I have 24 other sites functioning properly.
-
Monday, March 12, 2012 5:52 PM
I stand corrected... i did find the following in the sender.log on SITESERVERDC.
Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes SMS_LAN_SENDER 3/12/2012 11:48:53 AM 2724 (0x0AA4)
Trying the No. 1 address (out of 1) SMS_LAN_SENDER 3/12/2012 11:48:53 AM 5032 (0x13A8)
FQDN for server BRSDCCM is BRSDCCM.sch.brsd.edc SMS_LAN_SENDER 3/12/2012 11:48:53 AM 5032 (0x13A8)
There is no existing connection, Win32 error = 5 SMS_LAN_SENDER 3/12/2012 11:48:53 AM 5032 (0x13A8)
There is no existing connection, Win32 error = 5 SMS_LAN_SENDER 3/12/2012 11:48:53 AM 5032 (0x13A8)
Error during connection to \\BRSDCCM.sch.brsd.edc\SMS_SITE (5). SMS_LAN_SENDER 3/12/2012 11:48:53 AM 5032 (0x13A8)
Error is considered fatal. SMS_LAN_SENDER 3/12/2012 11:48:53 AM 5032 (0x13A8)
Cannot connect to server BRSDCCM.sch.brsd.edc at remote site ISC, won't try send requests going to site ISC for an hour or until there are no active send requests. SMS_LAN_SENDER 3/12/2012 11:48:53 AM 5032 (0x13A8)
There is no existing connection, Win32 error = 5 SMS_LAN_SENDER 3/12/2012 11:48:54 AM 5032 (0x13A8)
There is no existing connection, Win32 error = 5 SMS_LAN_SENDER 3/12/2012 11:48:54 AM 5032 (0x13A8)
Error during connection to \\BRSDCCM\SMS_SITE (5). SMS_LAN_SENDER 3/12/2012 11:48:54 AM 5032 (0x13A8)
Error is considered fatal. SMS_LAN_SENDER 3/12/2012 11:48:54 AM 5032 (0x13A8)
Cannot connect to server BRSDCCM at remote site ISC, won't try send requests going to site ISC for an hour or until there are no active send requests. SMS_LAN_SENDER 3/12/2012 11:48:54 AM 5032 (0x13A8)
Could not establish connection. SMS_LAN_SENDER 3/12/2012 11:48:54 AM 5032 (0x13A8)
Attempt to connect failed. SMS_LAN_SENDER 3/12/2012 11:48:54 AM 5032 (0x13A8)
Restart time = 3/12/2012 11:53:54 AM Mountain Daylight Time SMS_LAN_SENDER 3/12/2012 11:48:54 AM 5032 (0x13A8) -
Monday, March 12, 2012 5:56 PMModeratorError 5 is Access denied. Did you use the same site code when reinstalling the secondary site? Is the primary site server member of the local admin group on the secondary and is the secondary site server member of the site2siteconnection group on the primary site server?
Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund
-
Monday, March 12, 2012 6:03 PM
Okay so I added the SITESERVERDC to the local group "SMS_SiteToSiteConnection_ISC" on the Primary SCCM server and that appears to correct the above error in the sender.log.
The site has gone active on its own.
It appears the problem with the site staying in pending mode is directly related to the fact that I am creating the site and telling the wizard to install onto SITESERVERCCM but instead SCCM installs the site to SITESERVERDC. Which means the wrong server is added to the needed security groups.
- Edited by pfitchie Monday, March 12, 2012 6:06 PM
-
Monday, March 12, 2012 6:37 PMand Yes I am using the same site code when recreating the site.

