Get crawled property name for your column

 

I was desperately trying to find what is the crawled property name of my column scheduling end date. 

I stumbled across this helpful powershell

Function Get-CrawledPropertyNames([string]$DocURL){ 
$DocURL = $DocURL.Replace("%20"," ")
$webfound = $false
$weburl = $DocURL
while ($webfound -eq $false) {
    if ($weburl.Contains("/")){
    $weburl = $weburl.Substring(0,$weburl.LastIndexOf("/"))
    $web = get-spweb -identity $weburl -ea 0
    if ($web -ne $null){
        $webfound = $true
    }
    }else{
    Write-Host -ForegroundColor Red "The Web could not be found"
    return -1
    }
}
$web.GetFile($DocURL).item.xml.Replace("' ", "' `n").Replace("`" ", "`" `n")
} 

#To use enter the url of a file within a doucment library  Get-CrawledPropertyNames http://sites/doc/file.pdf

Got it from this link.

http://gallery.technet.microsoft.com/scriptcenter/Get-Crawled-Property-names-9e8fc5e0

Creating your own VHD for SP2013

 

Go to Hyper-V.

Click New VHD.

After installing basic OS we need to install AD.

Using following link install AD.

http://www.rackspace.com/knowledge_center/article/installing-active-directory-on-windows-server-2008-r2-enterprise-64-bit

Open Server Manager. To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.

In Computer Information, click Configure Remote Desktop.

In the System Properties dialog box, under Remote Desktop, click one of the following options:

• Allow connections from computers running any version of Remote Desktop (less secure). Use this option if you do not know the version of Remote Desktop Connection that will be used to connect to this server.
• Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure). Use this option if you know that the users who will connect to this server are running Windows Vista or Windows Server 2008.

Review the information in the Remote Desktop dialog box, and then click OK twice.

Make sure to give 2 processors

http://absolute-sharepoint.com/2013/01/microsoft-sharepoint-server-2013-encountered-an-error-during-setup.html

AD and SharePoint users sync

Lot of times we encountered the problem where for testing we add users in AD and they do not get access to site the same time and even after doing User Profile Synchronization job run, we could not solve the problem.

Turns out the below blog helped.

http://blog.randomdust.com/index.php/2013/06/sharepoint-2013-claim-expiration-and-ad-sync/

Page cannot be displayed error while creating Web application

While creating a new web application, a 404 'Page not found' error is displayed and the web application is only provisioned on the local server

After a number of web applications have been created in the SharePoint 2010 farm, further attempts to create a new web application through Central Administration result in the following:

The creation process results in a 'Page cannot be displayed' message.

The web application is only provisioned on the Central Administration server.

But if you try to create a site collection on this newly created web app, it fails. Reason is it is not completely done.

After struggling this for a while I found you can resolve by increasing the Shutdown time limit in IIS to a greater value.

Steps

1. Go to application pool of Central Administration.
2. Right click on it and go to Advanced Settings
3. In the Process Model section, increase the shutdown time limit to 200 for example.
4. It is a good idea to restart IIS now.
5. After searching on net for a while I found that the reason is during the web application creation process IIS is reset and by default. It allows the "Shutdown time limit" which by default is 90 seconds. Sometimes this might not be enough. And hence it forcibly shuts down in 90 seconds.

Server Error in ‘/’ Application. Runtime Error in SharePoint

Open web.config file


1. C:\inetpub\wwwroot\wss\virtualdirectories\” modify the web.config file

a. In customErrors tag set mode="Off" to "On
b. In SafeMode tag set CallStack="true" to false
c. In Compilation tag Debug="false" to true

2.If still you are facing default error page then follow below change
In the layouts directory underneath the SharePoint root directory or 14 hive – C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS

a. In customErrors tag set mode="Off" to "On
b. In SafeMode tag set CallStack="true" to false
c. In Compilation tag Debug="false" to true