• This email address is being protected from spambots. You need JavaScript enabled to view it.

    Recent items


Luca Costante

Luca Costante

In these days I'm working on a Custom Claim Provider that assign claims reading data from the User Profiles, SharePoint Groups, Custom DataBases, LDAP, etc.

Today I've a strange problem: when I use the People Picker, the system found the item (into the DB) ma not shows it (see the image below).

The problem is on a miss-match from the URL schema specified into the method FillClaimTypes (that is called when you enable the Farm feature that turn on your Custom Claim Provider and sets the allowed URLs) and the URL schema assigned to your claim.

I've resolved assigning the same schema URL and now all works fine.


If you have a slowly (virtual) machine, you can ran into an issue when creating a new SharePoint 2013 web application.

Everything appeared to be going correctly until the dialog box displayed "Internet Explorer cannot display the webpage". 

If you make some check, you can observe that:

  • in IIS the Application Pool and Site were both created as well
  • some virtual directorys are empty
  • the content database is not created

The problem is a time out in IIS.

You need to increase the time on IIS in order to give to SharePoint the time to create all components. To do that, you need to

  1. Open IIS Manager and select the SharePoint Central Administration Application Pool (many thanks This email address is being protected from spambots. You need JavaScript enabled to view it.for the tests)
  2. On the right hand side of the window click Select Application Pool Defaults
  3. Change the following 3 Process Model time settings from 90 to 400
    1. Ping Maximum Response Time
    2. Shutdown Time Limit
    3. Startup Time Limit

Now, you are able to create correctly the web applications.


File Explorer SharePoint features is a very useful function that enables users to open a document library as if it is a normal folder (network folder).

This would give the user access to normal file operations such as edit, copy, move etc.


If you click on the button into the ribbon the following error message "We’re having a problem opening this location in File Explorer. Add this web site to your Trusted Sites list and try again." appears and the library does not open in File Explorer:


After searching a bit in the Internet, I found that I have to start the WebClient service.

The first thing you need to do is to ensure that you have already installed the Desktop Experience feature in your Windows Server. If it’s your case, you can follow the steps below to do it:

  • Go to Run, type Server Manager and press Enter
  • Select Features and then select Add Features
  • Expand "User Interface And Infrastracture"
  • Select Desktop Experience and select Add Required Features on the popup screen
  • Click Next then click Install
  • Restart your computer
  • Go to Windows services and Start (with authomatic settings) WebClient service.
Friday, 04 April 2014 07:51

Windows Azure: configure endpoints

Windows Azure is the Cloud platform of Microsoft.

I've a virtual machine with windows server 2012 R2 and SharePoint 2013 and I use it to prepare demos, to share environment with my team, make tests, etc. Very often I need to navigate my test environment with a public url and I use the Fully Qualified Domain Name of the machine.

The problem generally is to have on the same URL more sites that need to be available. The solution is to use:

  • alternate access mapping (AAM) on SharePoint with a particula port (>1024)
  • Add the binding for the site on IIS  with the same port specified on the AAM
  • allow that port on the Windows Firewall.

At this point, the last action to is to go on the azure web platform, select the virtual machine and you need to add an endpoint where you are mapping a public port (that will be used through the internet) with the port specified in IIS and on the AAM.

Et voila, now you can navigate the site via internet by a specific port.
For each site that you need to navigate by internet, you need to make the previous steps with a different port.

Note: if you have "Timeout error" when you surf the site via Internet, you need to check that on the Windows Server Firewall is added the exception for the port that the site is using.

Tuesday, 04 March 2014 22:46

How to use and configure large lists


we need to store into lists a lot of elements. All developers that know SharePoint knows that in the OOB views there is the limit of 5000 items.
I want suggest these recommendations to create a definition for a list that have a lot of elements:

  • allow the folders and create an event receiver in order to store the items into the folders (maximum 5000 items for each folder)
  • enable one o more indexed columns (not on the ID field and the best fields are text fields). Each column that will be used for where condition or $filter condition need to enabled as indexed column
  • if you are quering on lookup column, you must use this

<FieldRef Name='ColumnName' LookupId='TRUE' /><Value Type='Integer'   >LOOKUP_ITEM_ID</Value>

In the case that you have already the list and you have exceeded the threshold, these are the steps for the work around:

  • from the central administration, modify the threshold value up to the current list count on the current web application
  • add the indexed column
  • create a view that contains less of 5000 items (for example with where condition on created date)
  • from the central administration, reset the threshold value to 5000 on the current web application

In the case that you want to use the REST API on the list, remember that all fields that you need to apply $filter condition, need to defined as indexed column, otherwise you'll have the error "Internal server error".

See these links for more details


today I'm working with a new project and the specification from the project is to develop a new application with SharePoint 2013 Foundation.

I've already a virtual machine but with SharePoint 2013 Enterprise.

I've two basic possibility:

  1. create a new virtual machine
  2. uninstall the Enterprise version of SharePoint and install the Foundation.

I've used the second approach. So I've uninstalled SharePoint 2013 Enterprise version and immediately after I've installed the Foundation version.

Just during the Wizard, I've received some errors: "dll not found", "files from feature not found", etc.

The problems stem from the fact that into the "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\" folder there are the definitions of both versions of SharePoint. Infact, when you uninstall SharePoint, the uninstaller does not remove the files and the folders into the path.

To make a clean installation, I've:

  • removed both versions
  • turned off the machine
  • mounted the vhd and removed the folder "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\" (It cannot be removed when the machine is turned on)
  • installed the SharePoint Foundation version
  • launched the wizar.

Finally, I've an installation and an usage without errors.

You may have encountered a warning similar to the following when browsing web sites with IE or Chrome:

"The Web site wants to run the following add-on: 'Name ActiveX Control' from 'Microsoft Corporation'. If you trust the Web site and the add-on and want to allow it to run, click here..."

The problem occurs only on PC that has Microsoft Lync installed. Infact, the browser needs the rights to execute a Microsoft dll (Name.dll) in order to display the presence icon.

I've also tried to disable the feature from the web application settings but it not resolve the problem.

If your application doesn't need of this feature and you want to disable this warning, you need to override the SharePoint OOB script that request the add-on. These are the steps to fix the problem:

  • Edit the master page
  • immediately under the body tag, add the follow script.

Show/Hidden javascript code

View source
    function ProcessImn()
    { }
    function ProcessImnMarkers()
    { }

That is it.

Saturday, 23 November 2013 13:48

Resize VHD free space

Many thanks to This email address is being protected from spambots. You need JavaScript enabled to view it. for the solution of the problem.

If you are working with SharePoint and if you are developing by virtual machine then probably you may think to use a SSD (mine 128gb) to contain the VHD file and speedup your work. This is my case but the VHD dynamic expansion causes this

The principal problem is the impossibility to start up the virtual machine because it gives me a critical error and i cannot fix this problem (probably deleting some big files) internally.

Then I found this solution to resize and compact the VHD:

  • Start CMD as administrator
  • Prompt:diskpart
  • select vdisk file=<your drive>:\<your path>\<filename>.vhd   (ex. F:\MyVM\win8.vhd)attach vdisk readonly
  • compact vdisk
  • detach vdisk

Good. After this, the vhd size is passed from 110gb to 109.6gb. Not a good result, but I re-launched the VM and it was started. Just the time to find and delete some big files (first of all old content db). I repeated the step to reduce the size of VHD and

Enjoy it! Risatona

Tuesday, 19 November 2013 11:10

Enable mobile access to anonymous zone

SharePoint 2010 has two visualization types:

  • Desktop
  • Mobile

For the mobile view, the system provide to read the user agent and redirect the requestes to a system pages that after redirect the requestes to the mobile views (for the lists, doc libraries, etc.).

If you wanto to give the desktop view also to the mobile terminal to the anonymous zones, with the OOB settings you have an access denied because the system redirect your requestes to a system pages that is under permission. If you try to access to the public portal with a mobile terminal (with a desktop terminal you don't have problems), you receive the popup for the credentials.

So, to enable the view also for the mobile terminal, you need to modify the web.config file for each Web Front End.

Under the section

Show/Hidden xml code

View source
              <result type="System.Web.Mobile.MobileCapabilities, System.Web.Mobile, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>

Friday, 25 October 2013 17:24

Another "special" thanks to Windows Updates

Some days ago, my collegue This email address is being protected from spambots. You need JavaScript enabled to view it. told me that his SkyDrive Pro cannot sync the new folder on the SharePoint.

He received the error "Sorry, we can't sync this library because it's hosted on a sharepoint 2010 server". I've sayed him that it could be a skydrive problem or that he is not a good programmer :P but today I've received the some errors.

After some searches, I've found that the problem encourred after some windows updates (on SkyDrive Pro application).

In my mind I think: "how is possible that after the windows updates, one time some SharePoint doesn't work and now the SkyDrive".

The first clean solution is to uninstall the updates. In my case they are 6 and are all called with KB2825633. I've closed the SkyDrive Pro and reopen it (without restarting windows) and now I'm able to sync my document library.




Page 2 of 5