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<http://www.osiatis.com/> [cid:[email protected]][Signature Ecosia DFAN]<http://www.digitalforallnow.com/> De : [email protected] [mailto:[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]> [mailto:[email protected]] On Behalf Of Stephen Owen Sent: 02 September 2015 19:24 To: [email protected]<mailto:[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. [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
