Baris's SharePoint Blog

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.

If you have this error, it is probable a Kerberos issue. Try to set the SPN of you SQL Service Account. Find out which user runs the SQL Service on your database server. Find out the port (Standard 1433) FQDN of the database server Use SetSpn -a MSSQLSvc/NX5015.swiss.group4net.com:1433 Reference: "Cannot Generate SSPI Context" error message, Poisoned DNS on MSDN

Short & handy (Get-SPWeb http://yoursite).Lists["Listname"].Items | % { $_.ParentList.GetItemById($_.ID).Delete() }

I've never really understood Alternate Access Mapping called AAM. But when I started to use UAG and the SharePlus App it was necessary to understand the concept of AAM better. I will not talk about how to configure AAM or the bindings in the IIS. There are lots of stuff out there. I want you to undestand the concept. So I want to tell you how I made me understand AAM. There are three features of  AAM Internal URL Public URL Zone The internal URL is the URL that the SharePoint Server understands & accepts The public URL is the URL that the clients outside in the world knows A Zone  is a logical container for a public URL with a name like "Interner" or "Extranet". It does nothing really special. You have 5 zones in SharePoint, means a max. of 5 public urls. Explain AAM with some analogies My name is Ihsan Baris. So when someone calls me "Baris" or "Ihsan" I'll respond to him. Some friends and my brother are ca...

The Problem I had to change the farm administrator because the IT decided not to use a single account as local admin anymore. So I changed the farm account with powershell and adapted all the services. The only think was that I had forgot to delete the account from the managed accounts list. Weeks passed and I stumbled over the account in the managed accounts list. When I tried to open the link " Security " -> " Configure managed accounts " I got an exception. The error was obvious. The account which was deleted from the AD could not be resolved. 1.Try I created the user again in the AD. After that the error in UI disappeared but when I tried to deleted the managed account from the list, I got following error. 2. Try It seemed that there some services still reference this account. The first thing was to check the IIS Application Pool accounts. Then I checked twice the settings in the CA " Security " -> " Configure Service...

Turns out that the search service has problems when anonymous authetication is on. I have a custom tool to test my search, that connects to the search service and performs queries. Every time I tried to query the service I got this error. I could not easily disable anonymous authetication on my server because we used it for some sites. This article helped me to find a solution:  The SharePoint Search Service and Anonymous Access (Trinkit Blog)

You get the following error when you try to add a custom WebPart in to your site: " Type is not registered as safe " Error Message This means that you: Don't have an web.config entry for your dll have a wrong web.config entry for your dll The 2nd reason is more often, especially when you develop a WebPart in Visual Studio and change the default Class or NameSpace names. Steps to solve the problem 1. Check your web.config This step is only to check if there is a web.config entry when you deploy your solution. For this deploy your solution into the farm. Open your web.config file in (C:\inetpub\wwwroot\wss\VirtualDirectories\youwebapp\web.config). Search after "<SafeControls>" and check if your dll is listed there and if so check if all parameters like PublicKeyToken, NameSpace or DLLName are correct Safe Control Entry in Web.Config Tip : If oyu deployed your assembly into the GAC, you can check the "PublicKeyT...