Are those lines prefixed with "Property"? Those can be ignored then. See sitectrl.log if there are any errors.Torsten Meringer | http://www.mssccmfaq.de

Hello, seen a similar post here but no resolution described in it... I am experiencing a problem with a secondary site R3 installation. The sites are not yet allowed to be published in AD so key exchanges where done manually during the initial installation. I then installed the needed 977384 patch on the seconday site server, and ran the R3 setup locally. No errors during the installation and everything seems fine, but on the primary it only shows as a R2 installation. I've tried re-installing R3, restarting the secondary site server, restarting the sccm console (this was a tip on another forum). The inboxes\sitectrl.box\sitectrl.ct0 says it's version 4.00.6487.2000... Update: Tried re-installing 977384 via command line as administrator which seemed to be a possible problem according to other articles I've found on this. Still no luck though.

Jason; as Torsten says, it was from the property part of the log. Sorry about that. There are a few errors in the MSI part though. I've copied the parts containing "error". theyre marked below in bold. Guess most of these are pretty irrelevant, the only one that sticks out is the SRSetRestorePoint that appears twice. The MSi part finishes with: Action ended 8:53:19: InstallFinalize. Return value 1. Action ended 8:53:19: INSTALL. Return value 1. ----------------------------------------------------------------------------------------- [8:52:46] CheckForSP2QFE() started. [8:52:46] CheckForSP2QFE() SP2 QFE found. [8:52:46] KB977384 [8:52:46] CheckForSP2QFE() completed successfully. Action ended 8:52:46: CheckForSP2QFE. Return value 1. MSI (c) (94:2C) [08:52:46:778]: Skipping action: ShowNonSoloError (condition is false) MSI (c) (94:2C) [08:52:46:778]: Skipping action: DisplayUninstallWarningsCA (condition is false) MSI (c) (94:2C) [08:52:46:778]: Skipping action: CheckForR2ParentCA (condition is false) MSI (c) (94:2C) [08:52:46:778]: Skipping action: SetNoR3ParentWarning (condition is false) MSI (c) (94:2C) [08:52:46:778]: Doing action: CCPSearch ----------------------------------------------------------------------------------------- DEBUG: Error 2836: The control EULADialog_Next on the dialog EULADialog can not take focus Internal Error 2836. EULADialog, EULADialog_Next Action 8:52:51: EULADialog. Dialog created ----------------------------------------------------------------------------------------- ******* Product: C:\Install\R3\CONFIGMGR2007R3.MSI ******* Action: INSTALL ******* CommandLine: ********** MSI (s) (64:D4) [08:53:16:340]: Machine policy value 'DisableUserInstalls' is 0 MSI (s) (64:D4) [08:53:16:340]: Machine policy value 'LimitSystemRestoreCheckpointing' is 0 MSI (s) (64:D4) [08:53:16:340]: Note: 1: 1715 2: Microsoft System Center Configuration Manager 2007 R3 MSI (s) (64:D4) [08:53:16:340]: Calling SRSetRestorePoint API. dwRestorePtType: 0, dwEventType: 102, llSequenceNumber: 0, szDescription: "Installed Microsoft System Center Configuration Manager 2007 R3". MSI (s) (64:D4) [08:53:16:340]: The call to SRSetRestorePoint API failed. Returned status: 0. GetLastError() returned: 127 MSI (s) (64:D4) [08:53:16:356]: File will have security applied from OpCode. ----------------------------------------------------------------------------------------- MSI (s) (64:D4) [08:53:16:574]: Skipping action: NoSMS (condition is false) MSI (s) (64:D4) [08:53:16:574]: Skipping action: CheckSoloCA (condition is false) MSI (s) (64:D4) [08:53:16:574]: Skipping action: CheckForSP2QFE (condition is false) MSI (s) (64:D4) [08:53:16:574]: Skipping action: ShowNonSoloError (condition is false) MSI (s) (64:D4) [08:53:16:574]: Skipping action: DisplayUninstallWarningsCA (condition is false) MSI (s) (64:D4) [08:53:16:574]: Skipping action: CheckForR2ParentCA (condition is false) MSI (s) (64:D4) [08:53:16:574]: Doing action: CCPSearch ----------------------------------------------------------------------------------------- MSI (s) (64:D4) [08:53:16:668]: Calling SRSetRestorePoint API. dwRestorePtType: 0, dwEventType: 102, llSequenceNumber: 0, szDescription: "Installed Microsoft System Center Configuration Manager 2007 R3". MSI (s) (64:D4) [08:53:16:668]: The call to SRSetRestorePoint API failed. Returned status: 0. GetLastError() returned: 127 MSI (s) (64:D4) [08:53:16:668]: Server not locked: locking for product {5CF55004-EEC4-406F-AF05-2291F1395388} -----------------------------------------------------------------------------------------

This is finally solved. My solution was: Uninstall KB977384 patch, uninstall R3, wait for replication to primary, re-install KB977384 with elevated privileges, re-install R3 with elevated privileges, verify replication and correct version in console on primary. Something must've gone wrong with the initial 977384 installation, since the uninstall/re-install of it seems to have been the trick. Thanks for you help and tips on this! //John

Update: Ran the KB977384 installation with /l*v as well to check for errors. No errors reported from that installation. Still not reported as R3 anc sitectrl.ct0 still says <31>

Hope, you are folowing top to down approach while doing the upgrades to R3.Anoop C Nair

I replied on the myITForum thread: http://www.myitforum.com/forums/tm.aspx?high=&m=227956&mpage=1#228007. "On an R3 sitein the sitectrl.ct0 file, the value in angle brackets after IsR2CapableRTM should be 63. If it is still 31, then R3 did not successfully install. By default, R3 creates an install log file in the user initiating the install's temp directory. You can also directly run the MSI with the /l*v option to create a log file in the location of your choosing (make sure you do this from an elevated command prompt though). You should check this log file for any errors. Also, as you recommended on the TechNet forums, make sure you run the installation elevated. Once this value flips to 63, give it some replication time and then close and re-open your console."Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Can you post the actual snippet of the log? No KMS is involved with ConfigMgr.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Yes, parent is R3

Ok, might be getting somewhere now. According to the install log it says "SiteDefinitonPropertyValue = 63", and ends with "installation success or error status: 0" But here are some lines I'm wondering about; At the beginning of the installation log it states "InvalidProductKeyDialog_Text = The product key is not valid." and in the next section below PID key is present? Does the product key validate against the primary site or KMS perhaps? It also states "NoR3OnParent = Setup has detected that the parent site for this site may not have Configuration Manager R3 installed." Further down the line it states "ParentNotR3 = 0" though? Also, sitectrl.ct0 still says 31....

Hello Torsten, Yes they are prefixed with "property". No errors at all in sitectrl.log