Sharepoint URL Query Parameters

Hi again,

Today I’m posting some useful URL query parameters for SharePoint, I’ll try to update this list because some times it’s very useful 🙂

  • Web Part Maintenance Page
  • User Information List
  • Open Page in edit mode
  • Quick Deploy List (Hidden)
  • Taxonomy List (Hidden)
  • Nintex Workflow History List (Hidden)
  • Get the version of the SharePoint server
  • Save site as a template
  • Sign in as a different user
  • Application page for registering SharePoint Apps
  • Enable SharePoint Designer
  • Welcome Page Setting
  • Force displaying the user profile in the site collection

Sharepoint 2013 search pagination and refinement panel not working with anonymous access.



Open the  visual studio 2013 new project and create new visual web part .


And  just  double Click the  SearchResultPage.ascx page and  paste  the  given code  like this .

<%@ Register TagPrefix=”wssawc” Namespace=”Microsoft.SharePoint.WebControls” Assembly=”Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>

<%@ Register TagPrefix=”SharePoint” Namespace=”Microsoft.SharePoint.WebControls” Assembly=”Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>

<%@ Register TagPrefix=”SearchWC” Namespace=”Microsoft.Office.Server.Search.WebControls” Assembly=”Microsoft.Office.Server.Search, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>

<div style=”float:left”>

<SearchWC:RefinementScriptWebPart ID=”RefinementScriptWebPart1″ runat=”server” ChromeType=”None” />



<div class=’ms-srch-siteSearchResults’>

<SearchWC:SearchBoxScriptWebPart ID=”SearchBoxScriptWebPart1″ PageTitlePrefix=”<%$Resources:Microsoft.Office.Server.Search, Search_Results_Page_Title%>” RenderTemplateId=”~sitecollection/_catalogs/masterpage/Display Templates/Search/Control_SearchBox.js” EmitStyleReference=”false” ShowNavigation=”true” ChromeType=”None” runat=”server” />

<SearchWC:ResultScriptWebPart ID=”ResultScriptWebPart1″ runat=”server” ChromeType=”None” UseSharedDataProvider=”true” ShowAdvancedLink=”false” ScrollToTopOnRedraw=”true” ShowUpScopeMessage=”true” />

<SearchWC:DataProviderScriptWebPart ID=”DataProviderScriptWebPart1″ runat=”server” ChromeType=”None” IgnoreStaleServerQuery=”true” ClientType=”SiteResultsQuery-All” QueryPropertiesTemplateUrl=”sitesearch://webroot” />



After that deploy the solutions .

Now  You can Use WepartZone And Page layouts  working Fine anonymous access

View original post

How to reset farm passphrase

Today I faced a problem, I have to add s server to an existing farm that I have not deployed and there is no documentation of the process, so is it not posible to obtain the passphrase, but you can reset the existing passphrase by using Powershell 🙂

So let’s begin!:

Get-Help Set-SPPassPhrase -Detailed

To easily reset your SharePoint Passphrase

$passphrase = ConvertTo-SecureString -String “mySharePoint2010password” -asPlainText -Force

Set-SPPassPhrase -PassPhrase $passphrase -Confirm

MOSS 2007: Error deploying solution

Yes, today I’ll post about MOSS2007, this problem is focused in a chain reaction in the farm, so let’s begin:

The farm consists in 3 servers, one for CA, another for Intranet and another one for Extranet. The problem is the following, we wanted to implement a new solution to the farm, but when we deployed the solution it gets an error.

Previously some people were digging on the server to know what is happening and accidentaly stopped the web application service (¡¡Error!!) in one of the servers and the service stuck on stopping state.

So, let’s begin how I face the problem:

First of all, I opened a CMD and go to the following directory: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12BIN

Next step is to stop the service by stsadm command:

  • stsadm -o provisionservice -action stop -servicetype SPWebService
  • Did IISReset
  • After that I could start it either from command line or from central admin. stsadm -o provisionservice -action start -servicetype SPWebService

If you receive a message error about this operation is already started by other process, try to restart the timer service in all SharePoint servers.

So first problem, solved, next one to solve is the non deployment of the solution. You need to go to Operations tab and go to deployment status, and manually start the deployment of the solution.

After some minutes, the deployment was in “Error” state, so I entered in the solution and I realized that was showing the following error message:

“A feature with ID GUID has already been installed in this farm. Use the force attribute to explicity re-install the feature.”

So what can we do? Again stsadm commands, so let’s go

We need to execute the following lines:

stsadm -o deploysolution -name Mysolution.wsp -immediate -force
stsadm -o execadmsvcjobs

After a few minutes, you can check the solution and see if all the solutions are already installed in the farm.

That’s all, good luck

Sharepoint 2013 Workflow Error

Hi after a long time, today I came here to post a problem that recently happened in one of our customers, so I will put you on situation:

We have a Sharepoint farm of 1 Front End, this farm is fully patched until CU December ’14, and we have installed in the Farm the Workflow farm. We were deploying the portal until an error came across after one of my colleagues tried to manually start a Workflow and receive the following error:

Lo sentimos, se ha producido un problema

Method ‘StartWorkflowOnListItem’ in type ‘Microsoft.Sharepoint.WorkflowServices.FabricWorkflowInstanceProvider’ from assembly ‘Microsoft.sharepoint.WorkflowServices’, Version=, culture=neutral, PublicKeyToken=71e9bce111e9429c’ does not have an implementation.

After some digging on Google, I realized that the root of this problem could be a bug, so we found that when we upgradeSharepoint Server, STS services does not updated properly and require a separate update, and there is a mismatch of STS and Sharepoint wchich cause this issue.

To solve the problem, we need to install the following security update “Update 2880963 for SharePoint Server 2013: May 13, 2014”.

Yes, you’re Reading right, a May ’14 update when I have the farm patched until CU December ’14, weird isn’t it?

I have to add, that I have installed the security update and it solved all the problems that we were having on this farm. So… go on!

Another piece of information: There is no need to restar the server after the update has been installed, try to start the WF once again and good luck.

Implement a custom iFilter in Sharepoint 2013

Today I’d faced a trivial problem but finally easy to solve, the problem was the following:

A customer uploads in a SharePoint document library several images files as jpg, png, etc… but he was complaining about that files in the document library were not indexed.

First I took a view to the search logs and apparently all was correctly, then I pointed the root cause to index file types in Search Service App, and boom, jpg files and png files were not included in Search.

After I included these two files types, all the items were indexed, but I realized that png files were not indexed at all, and these kind of files were launching in the search the following error:


So… what we can do? We already added the file type to Search, so next step? Easy answer… Powershell!!

Is rare to develop a custom iFilter, but the next step will help to make this:

We need to run the New-SPEnterpriseSearchFileFormat cmdlet, this adds a new file format and a corresponding file name extension to the search parsing system, so, let’s powershelling

$ssa = Get-SPEnterpriseSearchServiceApplication “Enterprise Search App”

New-SPEnterpriseSearchFileFormat –SearchApplication $ssa –FormatId png –FormatName PNGFiles –MimeType application/png

After registering the file format, restart the search service and launch a full crawl

Hope it helps!

The secure sockets layer (SSL) certificate sent by the server was invalid and this item will not be crawled

Error we faced today in a next production environment, we used a self signed certificate and we receive this error when we tried to crawl the app web:

The secure sockets layer (SSL) certificate sent by the server was invalid and this item will not be crawled


 Go to Central Administration > Application Management > Manage services on server >  Sharepoint Server Search and set it to ignore SSL warnings. Repeat full crawl of your content source again.

Or in powershell:

$searchService = Get-SPEnterpriseSearchService

if($searchService.IgnoreSSLWarnings -eq $false)


    Write-Host "3. Setting Ignore SSL Warnings to true..." -NoNewline

$searchService.IgnoreSSLWarnings = $true

    Write-Host "OK"


Hope it helps

Delete extended Web Application

Extended web applications are not listed in the web application list and cannot be deleted using the Delete Web Application link in Central Administration.

Use the following steps to delete extended web applications:

  1. Start Central Administration
  2. Go to Application Management
  3. Click Remove SharePoint from IIS Web Site


  1. You will get a page with a form similar to the following.


  1. Select the web application that the extended web app was extended from
  2. Select which extention/zone to delete
  3. Select whether to keep or delete the IIS Web site
  4. Finally click OK

Sharepoint Foundation 2013: Create Search Service App

How many of us had a fresh installation of SharePoint Foundation 2013 and tried to create the Search Service App trough Central Admin and didn't find it? I'm sure than more people than only me :)

Once we are in this situation, we have two possible options

  • Use SharePoint Wizard to create Search Service App
  • Use Powershell

The first option I prefer to discard it, obvious is obvious 😛

So, in the next lines I will post the code I use to create Search Service App

We have to type the account used for the AppPools, the name of the search servce application and the name of the AppPool, as it can be seen I the code, it has been take it from other blog (Thanks :))

[string]$farmAcct = "DomAppPool"
[string]$serviceAppName = "SearchServiceApplication"

Function WriteLine
Write-Host -ForegroundColor White “————————————————————–”

# ———————————————————————
Function ActivateAndConfigureSearchService
# Based on this script :

Write-Host -ForegroundColor White ” –> Configure the SharePoint Foundation Search Service -“, $env:computername
Start-SPEnterpriseSearchServiceInstance $env:computername
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance $env:computername
$appPool = Get-SPManagedAccount -Identity $farmAcct

New-SPServiceApplicationPool -Name AppServicesAppPool -Account $appPool -Verbose
$saAppPool = Get-SPServiceApplicationPool -Identity AppServicesAppPool
$svcPool = $saAppPool
$adminPool = $saAppPool

$searchServiceInstance = Get-SPEnterpriseSearchServiceInstance $env:computername
$searchService = $searchServiceInstance.Service
$bindings = @(“InvokeMethod”, “NonPublic”, “Instance”)
$types = @([string],

$values = @($serviceAppName,

$methodInfo = $searchService.GetType().GetMethod(“CreateApplicationWithDefaultTopology”, $bindings, $null, $types, $null)
$searchServiceApp = $methodInfo.Invoke($searchService, $values)
$searchProxy = New-SPEnterpriseSearchServiceApplicationProxy -Name “$serviceAppName – Proxy” -SearchApplication $searchServiceApp

catch [system.exception]
Write-Host -ForegroundColor Yellow ” ->> Activate And Configure Search Service caught a system exception”
Write-Host -ForegroundColor Red “Exception Message:”, $_.Exception.ToString()


That’s all!

Crawl Database stuck in “Recovering”

Today I faced a problem very weird, suddenly one of the crawl databases of the farm stuck in “Recovering Status”. So what happened? No idea, but I have to fix it 🙂 One advantage was that the farm was a preproduction environment so I could work without installation windows and son on. The first thing I checked was the free space on the hard drive, were remaining 4 gb of space, but my suspicious about the hard drive were there. I tried to shrink the log file, but how the database was in recovering It has been blocked by SQL. For my surprise when I access to the search application service on the front-end I discovered that was not possible to connect t the crawl component, so… I thought: Has to be the free space in disk drive… How was enough space in the hard drive were the databases were stored, I decided to take Offline the Crawl database and take it online again…. Problem solved!! So keep in mind, if you do not have enough space in disk, the crawl database will stuck in recovering… But my action do not ends here, I was thinking about if it was not possible to have more space, what could I do? TechNet has the answer: If the SQL Server runs out of space during a crawl, use the following steps to resume the crawl processing:

  1. From each server with a SharePoint Crawl Component, stop the ‘SharePoint Server Search 14’ and ‘SharePoint 2010 Timer’ services from either the Services snap-in (services.msc) or from a command prompt using ‘net stop osearch14’ and ‘net stop spTimerV4’
  2. From SQL Server Management Studio, detach the affected Crawl Store DB(s)
  3. Move the database and/or log (e.g. the .mdf, .ldf, and .ndf) files for the affected Crawl Store DB(s) to a drive path that provides sufficient space for growth
  4. From SQL Server Management Studio, re-attach the affected Crawl Store DB(s)
  5. From each server with a SharePoint Crawl Component, start the ‘SharePoint Server Search 14’ and ‘SharePoint 2010 Timer’ services from either the Services snap-in (services.msc) or from a command prompt using ‘net start osearch14’ and ‘net start spTimerV4’

After restarting the Search and Timer services on all servers running a crawl component as noted above, the crawl(s) should fully recover from the disk space condition and continue with normal processing. However, if the crawl was stopped as a troubleshooting measure, it is advised to let the ‘Stopping’ process complete as usual (which may require a significant amount of time for large crawls). Hope it helps!