Whether you are SharePoint veteran or new I think it’s always worth to have installation problem and how to troubleshot. Below are my troubleshot collection when I install SharePoint 2016 preview.
Lab configuration:
Svr01
OS : Windows Server 2016 CTP 4 Active Directory, with Windows 2016 forest mode Svc02
OS: Windows Server 2016 CTP4 SQL Server 2016 RC1 SharePoint Server 2016 RC March 07, 2016 Problem #1: Wait on database engine recovery handle failed.
After announcement of SharePoint Server 2016 and Project Server 2016 RC in office blog post on January 20, 2016. The blog post contains link to download the RC bit. However the download link is no longer available, because today Microsoft release SharePoint 2016 and Project Server 2016 Trial. Yes, all previously downloadable link such as CTP, Beta, and RC are no longer available. Started from March 7, 2016 a new download for SharePoint Server 2016 and Project Server 2016 is available through: https://www.
I am personally not fan of Apple who wants to queue overnight for the first release of the device - but, I am a Microsoft’s fans. Especially when it deals with Microsoft SharePoint including the cloud version known as Office 365. Sometimes it is thrilling to get the first release, because we may encounter unexpected bug. In the past we saw some hiccup to early adopters of SharePoint patches. But who cares, the statistic still shows that the probability of this kind regression is low.
English After the 3 series of Progressive Solution Installation Package using Nuget, many are asking whether we can streamline the process to create the installation package. My answer is YES. Today I want to introduce Installation Package MsBuild which has been published through Nuget. To start using this tools, type in your Visual Studio package manager. So, what will it does? The InstallationPkgBuild will convert any .NET project (library, console, SharePoint etc.
Many of our folks in the field rely on SharePoint Farm Version number information in Central Administration to compare the patch level between servers. While this number is showing the latest SharePoint Foundation, it doesn’t always mean that you have a completely patched SharePoint farm. The reason, because Microsoft releases many different type of patches:
Cummulative updates (CU) Server packages (Uber packages) Public updates (PU) Stefan Gossner wrote an excellent blog about SharePoint patch terminology and the impact your farm patch level in “SharePoint Patching Demystified” .
Yes, starting from this month bi-monthly SharePoint CU will become a history. From July 2014 Microsoft will release CU every month - yes EVERY MONTH!. So forget about bi-monthly. With this change policy, we expect that Microsoft will be able to address problem more quickly. The drawback, we know there were incidents in the past that some patches / CU were not going well. Microsoft subsequently released updated patch after releasing the patch / CU.
English:
During the operation of our Reporting Service Server, one of our clients reported accidental reports unavailability. Following is the screen capture on his browser :
Accoding to server maintenance history, there was no action performed on that server. So, what can caused this sudden unavailability?
To investigate the issue, we activate ASP.NET debuging in web.config, and browse to the report page. And now we have more precise information that Microsoft.