Baris's SharePoint Blog

I got this error while I was trying to install the Cumulative Updates August 2013. The reason for this error is that the baseline for all updates is the first Cumulative Update in March. I checked my build version of the farm and found out that I've installed the RTM version. If this doesn't solve your problem you can try to start the ubersrv2013-kbxxxxxx-fullfile-x64-glb.exe with the parameter PACKAGE.BYPASS.DETECTION.CHECK=1 like: ubersrv2013-kbxxxxxx-fullfile-x64-glb.exe PACKAGE.BYPASS.DETECTION.CHECK=1 ( Do not forget to start the command as farm administrator ) This bypassed all checks so that you can force the installation. Ressources : SharePoint 2013 Build Numbers and CU's

There are lots of stuff in the web around how to create a FAQ in SharePoint. In this post I'll show you some tricks what you can do with additional OOB SharePoint tools to have also some search and some style within your FAQ to impress your customer. It also shows you the power of SharePoint as a developer platform. The requirements for our FAQ are: Easy to maintain Easy to search content Add documents as links in FAQ Grouped FAQ content Export FAQ when needed into a report To understand this post you should have some basic know-how about: SharePoint Lists SharePoint List Views HTML, CSS JavaScript (SharePoint Client API) SharePoint WebParts CAML or you just follow the instructions. The following image shows us the final page. Final FAQ Pag Our FAQ page has a FAQ list and a document library. This is useful if you want to link on some documents in your FAQ. The page has a list WebPart with a special grouped view and also2 quick searches fo...

I got this error while installing SharePoint 2013 with AutoSPInstaller. STS Call Claims Windows: Failed to get cookie value handler type / object Opening the logs I saw following error messages: This error was also caused when I tried to use Get-SPSite -Limit All As the error says that it is a claims problem I first checked the SharePoint Security Token Service but the web service was fine. When I browse the web service, the page is rendered without errors: After: Check if Windows Web Services Pool has started Check if "Claims To Windows Token Service" has started Check if IIS checkbox "enable for 32bit Applications" is checked Provisioning the Security Service again Check if the "Claims To Windows Token Service" is running under Localsystem account Check if in IIS > Windows Authentication "Enable Kernel Mode Authetication" is enabled And Reinstalling SharePoint I got still the same error. Then I decided to debug...

For the last SharePoint 2013 Installation I used the AutoSPInstaller. After putting all required files into the PrerequisiteInstallerFiles folder and starting the Installation the .Net 4.5 Framework installed continuously and rebooted the server. After some digging I found out that SharePoint requires .Net 4.5 Version 4.5.50709 but I had a lower version installed. You can see the installed version number in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full Just download the newest .Net 4.5 installer here  and install it manually or put the offline installer into the PrerequisiteInstallerFiles folder.

Found this useful site in the microsoft homepage. It contains multiple videos for SharePoint and Office 13 developers: http://msdn.microsoft.com/en-US/office/apps/fp123626