Cascade Skyline - with Microsoft Logo and Project Support header - author Brian Smith

Project Server 2013 and SharePoint 2013: SP1 download deactivated

Project Server 2013 and SharePoint 2013: SP1 download deactivated

  • Comments 10

*** Update 4/22 SP1 re-release

Stefan's blog has the full download links for SP1  http://blogs.technet.com/b/stefan_gossner/archive/2014/04/22/sp1-for-sharepoint-2013-has-been-rereleased.aspx

And patch again to avoid the lost resources issue - unless you also load April CU. http://support.microsoft.com/kb/2933444

***

As a precaution due to a recently discovered issue both the SharePoint 2013 and Project Server 2013 Service Pack 1 (SP1) downloads have been temporarily made unavailable.  I will post more information when I have it. 

The KB articles for Project Server 2013 http://support.microsoft.com/kb/2817434 and SharePoint 2013 - http://support.microsoft.com/kb/2817429 have been updated with:

“We have recently uncovered an issue with this Service Pack 1 package that may prevent customers who have Service Pack 1 from deploying future public or cumulative updates. As a precautionary measure, we have deactivated the download page until a new package is published.”

The April Cumulative Update is due out next week, and I will be sure to cover in the Cumulative Update release what impact this issue might have, both for customers who have already loaded SP1 and those who have yet to load it..

Leave a Comment
  • Please add 5 and 7 and type the answer here:
  • Post
  • Hi Brian

    We have already deployed SP1 on our production. Do you mean the fix for this issue will be part of April 2014 CU ? or we have to wait further. ?

    Thanks,

    Mustaq Hussain.

  • Currently you know as much as me Mustaq.  There is no issue with the Service Pack that you need to be concerned about - but from what I know this could impact loading future patches (such as the April CU I presume).  With the timing coming so close to the April CU release there certainly will not be a 'fix' for this in the April CU - and once I know more about how this will impact users who have already downloaded and installed SP1, and how users who have not installed yet should proceed I will share.

    Best regards,

    Brian.

  • Im having trouble finding any "official" information confirming that the slipstreamed SP1 media from MS is NOT affected. Twitter says its not, but i can hardly rely on unconfirmed tweets. Any solid info om this?

  • I can confirm Andreas, that this does not affect the slipstream versions available via MSDN and other Microsoft sites.

    Best regards,

    Brian

  • Brian, thanks for your updates. I see you mention that the installation media from MSDN with SP1 already slipstreamed is unaffected by the recall. Is the issue with the source of the SP1 update or the process by which it was installed? If someone created their own slipstreamed installation using the downloaded SP1 files, would they be affected?  What about a new installation of SP2013 where the RTM SP2013 bits were installed, then the SP1 bits were installed, prior to ever running the SharePoint configuration wizard?

  • Hi Michael, I don't have the answers to your questions quite yet.  The issue relates to the ability to apply new patches, and as I understand it this does not affect Project Server at this time - but some of the other parts of the SharePoint family - so I haven't hit the issue personally (in which case I'd have far more details to share).  I'll see if I can get more information. I suspect the issue is with the binary loading rather than the DB version stamp - so may not make any difference when the config wizard is run.  One other advantage of our slipstreams is they can be loaded on Server 2012 R2 as the pre-reqs engine is updated too.

    Best regards,

    Brian

  • LTNS brian.. also Project Online is the future!

  • Early indications are that contrary to what I was led to believe the April CU will not install if you have SP1 already installed. More as I have it...

    Best regards,

    Brian

  • I have more now - and a false alarm - a couple of other installs worked just fine - and Adrian had also installed with no issues.  My bad install was on a server which I think had a pre-release SP1 so that is not something any of you should see.

    Best regards and sorry for the panic,

    Brian.

    P.S. Full release blog posting shortly...

  • Hello Brian, does your team has an update on the situation with SP1 availability?

Page 1 of 1 (10 items)