CU4 threw up some horric errors, rolling back my snapshot to try CU5
instead.

I am SO, SO happy that I didn't try this upgrade in production.

On Wed, Sep 2, 2015 at 2:30 PM, Erno, Cynthia M (ITS) <
[email protected]> wrote:

> I had to manually download and install to avoid errors.
>
>
>
> *Cynthia Erno*
>
> Data Center Hosting, Windows Unit
>
>
>
> *Office of Information Technology Services (ITS)*
>
> 50 Wolf Rd.,  Albany, NY 12204
>
> (518) 408-5506 [email protected]
>
> L3 DCH WIN      ç   Windows Server group ITSM
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Jason Sandys
> *Sent:* Wednesday, September 02, 2015 2:21 PM
> *To:* [email protected]
> *Subject:* RE: [mssms] Nasty SQL Errors when upgrading from R2 to R2 SP1
>
>
>
> That’s a true statement for large environments with very large numbers of
> deployments; i.e., this isn’t a general recommendation but is instead a
> targeted recommendation that is N/A for the vast majority of organizations.
>
>
>
> J
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Sean Pomeroy
> *Sent:* Wednesday, September 2, 2015 1:51 PM
> *To:* [email protected]
> *Subject:* Re: [mssms] Nasty SQL Errors when upgrading from R2 to R2 SP1
>
>
>
> I thought I read somewhere recently that it's actually recommended to
> apply CU5 first.
>
>
>
> On Wed, Sep 2, 2015, 1:26 PM Stephen Owen <[email protected]> wrote:
>
> 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
>
>
>
>
>
>



Reply via email to