Hi guys, I've got some updated info on the process here, under this post.
https://social.technet.microsoft.com/Forums/en-US/c526baa5-6369-447e-96ac-0060db160421/running-testdbupgrade-from-r2-cu3-to-r2-sp1-fatal-sql-error?forum=configmanagergeneral To answer some questions, the DB is healthy, SCCM works, no issues there. When running /testDBUpgrade from my 2012 r2 CU3 database copy, I had the same issue. I've applied CU 4 now to my SCCM clone and still don't see those columns created. I'm about to try CU 5 and see if that is the one update which creates the missing columns. I have a sneaky suspicion that it will. On Thu, Sep 3, 2015 at 9:19 AM, Jason Sandys <[email protected]> wrote: > “I always recommand going to the latest CU before upgrading to the latest > service pack > > Same goes with SQL and Windows” > > > > Sorry, not trying to bash, but there is no technical basis for this > recommendation. There been a couple of exceptions for very specific > circumstances, but these truly only applied to a very, very small > percentage of installations. > > > > J > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *LEROY Mathieu > *Sent:* Thursday, September 3, 2015 4:10 AM > *To:* [email protected] > *Subject:* RE: [mssms] Nasty SQL Errors when upgrading from R2 to R2 SP1 > > > > I always recommand going to the latest CU before upgrading to the latest > service pack > > Same goes with SQL and Windows > > > > > > Cordialement, > > > > Mathieu Leroy > > Consultant > > > > *T* : +33 3 28 02 53 57 ― *M* : +33 6 21 63 74 15 ― *F* : +33 3 28 02 53 > 06 > > 24 rue Papin - BP 50488 - 59664 Villeneuve d'Ascq Cedex > > *email* : [email protected]― *web* : www.osiatis.com > > > > [image: cid:[email protected]][image: Signature Ecosia DFAN] > <http://www.digitalforallnow.com/> > > > > > > > > *De :* [email protected] [ > mailto:[email protected] <[email protected]>] *De > la part de* Andrew Craig > *Envoyé :* jeudi 3 septembre 2015 09:38 > *À :* [email protected] > *Objet :* RE: [mssms] Nasty SQL Errors when upgrading from R2 to R2 SP1 > > > > Hi, > > > > Have you checked your SQL DB health? Are you running over remote > connections? Have you checked your SQL Logs? > > Is the DEVICE_COMPUTERSYSTEM_DATA table there and healthy and are the > columns mentioned in there? > > > > Can you execute the Stored Procedure from SSMS? > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Stephen Owen > *Sent:* 02 September 2015 19:24 > *To:* [email protected] > *Subject:* [mssms] Nasty SQL Errors when upgrading from R2 to R2 SP1 > > > > Hi guys, > > > > Running the SP2 Upgrade on my R2 system (then will apply the R2 patch, > and then CU1) and getting nasty errors on upgrade with. > > > > [image: Inline image 1] > > > > The error mentions multiple invalid column names when trying to run this > step. Fortunately for me, I'm using Kubisys on a copy of my > infrastructure, so this hasn't taken down production. Still, with my > upgrade slotted for tomorrow, I'd like to know how to fix this. > > > > I'm upgrading from SCCM 2012 R2 RTM, applying SP1 to get up to date. Do > you think I ought to apply one of the CU first? > > > > Thanks > > > > Stephen Owen > > > > > > > >
