I'm thinking, pure speculation that a single site might not exhibit this issue. Multiple sites being out of sync is a definite cause for alarm.
Thanks, Mark Sent from my iPhone > On Nov 6, 2013, at 6:25 PM, "Spinelli, Robert J" > <[email protected]> wrote: > > In order to resolve this issue, I had to upgrade the other 3 primaries to > SCCM 2012 R2. > > Even with the link being configured message on database replication, I was > able to create collections on Tier1/2 and they flowed back and forth. It > looks like a UI bug to me. That false status just hangs around forever until > the primary is also upgraded to R2. > > We have another lab that is being uprgraded tomorrow that is SCCM 2012 SP1 > CU2, and I’m curious to see if that also has the same issue/message. > > Thank you. > > Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, > 07310, United States| T: +1.201.595.6820 | C: +1.917.538.6192 | > [email protected] > > From: Spinelli, Robert J > Sent: Wednesday, November 6, 2013 9:46 AM > To: [email protected] > Subject: RE: SCCM 2012 R2 - Database replication - Link is being configured - > Hung > > Mark, already tried you’re articleJ. Very cool blog by the way. > > I think you have a few typos in it though: > > SELECT * FROM RCM_InitializationTracking WHERE ReplicationGroup = > ‘Configuration Data’ and SiteRequesting = ‘<SiteCode of failed site>’ > Should be > SELECT * FROM RCM_dRSInitializationTracking WHERE ReplicationGroup = > 'Configuration Data' and SiteRequesting = ‘<SiteCode of failed site>’ > > UPDATE RCM_InitializationTracking SET InitializationStatus =7 WHERE > RequestTrackingGUID = <Some GUID> > Should be > UPDATE RCM_dRSInitializationTracking SET InitializationStatus =7 WHERE > RequestTrackingGUID = <Some GUID> > > SELECT * FROM vLog > Should be > Select * FROM vlogs > > This whole replication is really a black hole, there are some articles, but > still very confusing. > > Here is another good article I found. > > http://blogs.technet.com/b/sudheesn/archive/2012/10/21/drs-initialization-in-configuration-manager-2012.aspx > > Thank you. > > Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, > 07310, United States| T: +1.201.595.6820 | C: +1.917.538.6192 | > [email protected] > > From: [email protected] [mailto:[email protected]] > On Behalf Of Mark Mears > Sent: Wednesday, November 6, 2013 9:30 AM > To: [email protected] > Subject: [mssms] RE: SCCM 2012 R2 - Database replication - Link is being > configured - Hung > > Robert, > Check out my post and see if that helps your situation. > http://www.cireson.com/sccm-tips/drs-replication-no-worky-2/ > > > Thanks, > > > Mark Mears > [email protected] > Phone: (757) 945-2651 > > <image001.png> > > <image002.jpg> Check out our System Center App Store: > www.cireson.com/app-store > > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Spinelli, Robert J > Sent: Wednesday, November 6, 2013 9:22 AM > To: [email protected] > Subject: [mssms] SCCM 2012 R2 - Database replication - Link is being > configured - Hung > > I upgraded my CAS (SCCM 2012 SP1, NO CU’s) in my lab to R2 and I see that > database replication has been hung at: > > Link is being configured – Initializing data between the parent site and > child site. > > It’s been like this for 8 hours, so something ain’t right. The CAS to the > child primary (SCCM 2012 SP1, NO CU’s) database replication is set for > active, only getting the message above on the primary back to the CAS. > > If I look at the Initialization Detail I see succeeded 100% and the times all > are current. I do see 2 Replication Groups which I believe are new to R2: > > CFD_Global > MDM_Global > > These 2 say succeeded, but are at 0% and have no client or parent > send/receive times. > > I’m running SCCM 2012 SP1 (NO CU) on the primary. The plan was to upgrade it > after the CAS, but I have the message above and need to resolve that first. > > Thank you. > > Robert Spinelli | CTS | GTI | 575 Washington Boulevard, Jersey City, NJ, > 07310, United States| T: +1.201.595.6820 | C: +1.917.538.6192 | > [email protected] > > This communication is for informational purposes only. It is not intended as > an offer or solicitation for the purchase or sale of any financial instrument > or as an official confirmation of any transaction. All market prices, data > and other information are not warranted as to completeness or accuracy and > are subject to change without notice. Any comments or statements made herein > do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries > and affiliates. This transmission may contain information that is > proprietary, privileged, confidential and/or exempt from disclosure under > applicable law. If you are not the intended recipient, you are hereby > notified that any disclosure, copying, distribution, or use of the > information contained herein (including any reliance thereon) is STRICTLY > PROHIBITED. Although this transmission and any attachments are believed to be > free of any virus or other defect that might affect any computer system into > which it is received and opened, it is the responsibility of the recipient to > ensure that it is virus free and no responsibility is accepted by JPMorgan > Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or > damage arising in any way from its use. If you received this transmission in > error, please immediately contact the sender and destroy the material in its > entirety, whether in electronic or hard copy format. Thank you. Please refer > to http://www.jpmorgan.com/pages/disclosures for disclosures relating to > European legal entities. > > > > This communication is for informational purposes only. It is not intended as > an offer or solicitation for the purchase or sale of any financial instrument > or as an official confirmation of any transaction. All market prices, data > and other information are not warranted as to completeness or accuracy and > are subject to change without notice. Any comments or statements made herein > do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries > and affiliates. This transmission may contain information that is > proprietary, privileged, confidential and/or exempt from disclosure under > applicable law. If you are not the intended recipient, you are hereby > notified that any disclosure, copying, distribution, or use of the > information contained herein (including any reliance thereon) is STRICTLY > PROHIBITED. Although this transmission and any attachments are believed to be > free of any virus or other defect that might affect any computer system into > which it is received and opened, it is the responsibility of the recipient to > ensure that it is virus free and no responsibility is accepted by JPMorgan > Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or > damage arising in any way from its use. If you received this transmission in > error, please immediately contact the sender and destroy the material in its > entirety, whether in electronic or hard copy format. Thank you. Please refer > to http://www.jpmorgan.com/pages/disclosures for disclosures relating to > European legal entities. > >
