I'm wrapping up the build of a brand new environment on a new domain we are migrating to and installing the last Secondary Site of 7. The destination servers of all the Secondary sites are all new 2012 R2 installations where I manually installed all pre-reqs, deployed the Secondary site from the console, and once complete added SUP & SMP. All 6 installed prior to this one went great with no issues. However, this last one is a pain even though I installed it the exact same way. It shows it completed successfully, but that's not the case. Below is a list of characteristics of the issue , what I've tried so far, and finally log info. I'm referring to the Secondary with issues as "TEX" and primary site as "ABC"
Characteristics of Secondary Site Issues (As it appears 24 hours after installation / deployment)
Installation completes successfully and under Sites its listed as "Active." All results within Installation Results pass except for 2 pre-req warnings
BITS & IIS6 WMI compatibility component for IIS7 are not installed or cannot be verified
Setup unable to establish a remote connection to WMI on secondary site
Site Status & Component Status lists do not contain and entries from "TEX" yet lists ones from the 6 other Secondaries
AD Forests / Publishing Status lists all 6 Secondaries + 1 Primary including TEX - however - the "Last Publishing Time" & "Last Publishing Status" are empty only for TEX
There are no entries for "TEX" within System Management container
In Monitoring / Database Replication, it states "Link is being configured" & "Initializing data between the parent site and child site".
Replication Analyzer
Inconsistent public keys - asks me to initiate public key transfer for target site TEX on source site ABC
File replication route is required for site-to-site communication and file replication route is missing for site ABC on site TEX
Replication initialization is aborted in site ABC for the replication groups: Secondary_Site_Replication_Configuration. RLA recommends reinitializing the above mentioned groups on site TEX. This may take several hours
A boundary group with ~200 IP Ranges is associated with the Secondary Site
Groups for local admins on TEX are the same as all other secondaries
Distribution is not working / processing anything to TEX although should be
What I've Tried to Resolve Issue
Uninstall Secondary Site then reinstall
Delete Secondary Site from console then manually uninstall all SCCM & SQL components, delete related files, registry entries, and even uninstalled roles / features; rebooted; then reinstalled all from scratch - same issue persists
Manually added server's hostname to System Management container delegating full access to it
Chosen to run all suggested actions in Replication Link Analyzer. After doing each, same issue appeared so had to skip rule to get it to continue
Used the commands "preinst.exe /keyforchild" and "preinst.exe /keyforparent" then copied the resulting files into the hman.inbox where they belonged. They were processed and disappeared but nothing changed
Considering uninstall / reinstall again but using a different site code. Only thing is that if that worked I feel I'd have some crap left over in database from old site code and don't want to jeopardize stability or performance
Log FIles
Below are individual log files as well as ZIPs of multiple ones taken from when I worked on it this afternoon.
Hey Guys / Niall -
I'm wrapping up the build of a brand new environment on a new domain we are migrating to and installing the last Secondary Site of 7. The destination servers of all the Secondary sites are all new 2012 R2 installations where I manually installed all pre-reqs, deployed the Secondary site from the console, and once complete added SUP & SMP. All 6 installed prior to this one went great with no issues. However, this last one is a pain even though I installed it the exact same way. It shows it completed successfully, but that's not the case. Below is a list of characteristics of the issue , what I've tried so far, and finally log info. I'm referring to the Secondary with issues as "TEX" and primary site as "ABC"
Characteristics of Secondary Site Issues (As it appears 24 hours after installation / deployment)
What I've Tried to Resolve Issue
Log FIles
Below are individual log files as well as ZIPs of multiple ones taken from when I worked on it this afternoon.
The site is 2012 R2 SP1 CU4 with all site servers running 2012 R2 OS. Any help or suggestions you could provide would be fantastic - Thank You!!
Share this post
Link to post
Share on other sites