When applying a Cumulative Update to your SharePoint 2016 Farm, you might run into troubles when executing PSConfig/PSConfigUI after installing the Binaries. The error that is logged in the Windows Event Log looks as follows:
The Execute method of job definition Microsoft.SharePoint.Administration.SPUpgradeJobDefinition (ID ..) threw an exception. More information is included below.
The upgraded database schema doesn't match the TargetSchema. (Correlation=..)
You can avoid this issue if you either
With detached or already upgraded Content Databases PSConfig/PSConfigUI should run successfully.
After a great SharePoint Saturday in Stockholm, you can find the slides for my session "What's new in SharePoint 2016" at docs.com: https://doc.co/EuAWoA
All kinds of cool SharePoint-contents, a lot of fellow MCM-colleagues - happy to be a speaker at the European SharePoint Conference 2016, taking place in Vienna from November 14-17. My Session will be about User Profile Synchronisation with SharePoint 2016 and Microsoft Identity Manager 2016. I hope to see many of you there.
I'm excited to talk at the largest Microsoft Technology Conference in Austria about "SharePoint 2016 Infrastructure/Upgrade" and "SharePoint 2016 Hybrid Solutions". If you want to get inside knowledge about the latest Microsoft Technologies (Windows Server 2016, SQL 2016, Exchange 2016, SharePoint 2016, PowerBI, Office365 etc.), get your ticket at www.techconference.at and come to Vienna from 20.-21.1.2016.
See you there.
As Beta 1 of SharePoint 2016 is already available, I developed a 3-day training "What's new in SharePoint 2016 for Admins" and a 5-day training "SharePoint 2016 Administration". Please contact me if you're interested in the TOC and for available training dates.
I'm proud to be a part of the first SharePoint Saturday in Munich on October 10th, 2015.
Come and join an awesome lineup of speakers (and me) for a lot of in depth Information on SharePoint 2013 and 2016.
My Session will be about the changes in the User Profile Sync Service in SP 2016.
Session details will be revealed soon…
Don't miss this free, all English event, registration starts on September 1st.
Today, at Ignite Conference in Chicago, Microsoft released some interesting facts about the new Version of SharePoint called "SharePoint 2016".
You need to use the "Single Server" option and can install SQL Server on the local machine.
Health Analyzer rules will take care of provisioning the services and will complain if a server doesn't meet the role expectations.
5000 items is no longer a threshold, file upload size changes to 10 GB
An item can keep its link even if it is moved to another site collection or renamed
Stay tuned, I will inform you about the other interesting stuff as soon as I can talk about it…
SharePoint 2013 comes with the new Script Editor WebPart which can be used on Wiki/WebPart/Publishing Pages to add Script Code to the page. Using it is fairly simple: add it to the page from the WebPart Catalog.
BUT MySites for example don't contain the Script Editor WebPart in the catalog:
To bring the Script Editor WebPart to the MySite WebPart Catalog (and therefore to all of the subsites like Blog etc.), you can
* download the file "MSScriptEditor.webpart" from any "Web parts" Gallery in your content sites (Settings | Site Settings)
* Now go to the "Web parts" Gallery on your MySite and upload the previously saved file "MSScriptEditor.webpart" to the gallery - change Title and Description and Group as needed ;-)
It was somehow clear that InfoPath doesn't have the brightest future after being the only part of Office 2013 that was not revised. Now it's official – InfoPath will be retired and there will be no future version: http://blogs.office.com/2014/01/31/update-on-infopath-and-sharepoint-forms/
I'm quite curious about what the new roadmap will be – SPC2014 will tell us…
The Community Site is a new template in SharePoint 2013 that allows us manage discussions and Q&A contents in a comfortable way. Unfortunately this template is not available for creation as a subsite (in the browser) of a Publishing Site – even if you add it to "Page Layouts and site templates":
Add subsite shows the following (I added "Team Site" just to make sure that the "Collaboration" tab is showing up):
Activating the feature "SocialSite" does the trick:
enable-spfeature -Identity 4326e7fc-f35a-4b0f-927c-36264b0a4cf0 -Url <<site collection>>
Now you will be able to create a Community Site as subsite of a Publishing Site:
My thoughts and findings about SharePoint 2016/2013/2010 and SQL Server