Search Archives - Blog IT https://blogit.create.pt/category/search/ Create IT blogger community Wed, 04 Aug 2021 22:30:09 +0000 en-US hourly 1 https://wordpress.org/?v=6.9.1 How To Fix a Degraded Search Index Partition in a SharePoint 2013 farm https://blogit.create.pt/miguelisidoro/2018/10/07/how-to-fix-a-degraded-search-index-partition-in-a-sharepoint-2013-farm/ https://blogit.create.pt/miguelisidoro/2018/10/07/how-to-fix-a-degraded-search-index-partition-in-a-sharepoint-2013-farm/#comments Sun, 07 Oct 2018 19:30:30 +0000 https://blogit.create.pt/?p=7531 Hello, Recently, a customer reported problems with Search in a SharePoint 2013 farm. Instead of showing search results, the following error was being shown: The Problem To diagnose the problem, I opened Central Administration and the Search Service Application page indicated problems with the Index Partition component in the Search Service Application Topology. To further […]

The post How To Fix a Degraded Search Index Partition in a SharePoint 2013 farm appeared first on Blog IT.

]]> Hello,

Recently, a customer reported problems with Search in a SharePoint 2013 farm. Instead of showing search results, the following error was being shown:

The Problem

To diagnose the problem, I opened Central Administration and the Search Service Application page indicated problems with the Index Partition component in the Search Service Application Topology.

To further diagnose the problem, I opened up a PowerShell window (used the option “Run As Administrator” to ensure proper permissions) and executed the following commands:

$ssa = Get-SPServiceApplication -Name “Search Service Application”
Get-SPEnterpriseSearchStatus -SearchApplication $ssa -Detailed -Text

After execution, the result confirmed a problem with the Index Partition, showing the Index component with the Degraded state. According to Microsoft “The reason for the degraded status is typically a transient situation related to a restart or network issues” but from my experience it is not easy to understand why this happens.

The Solution

The solution was composed by two steps:

  • Reset the Search Index – this operation will clear all index content but will NOT delete any custom managed properties you may have created in the search service application
  • Perform a Full Crawl on Search Content Source to crawl and reindex all your content

Reset the Search Index

To reset the Search Index, I went to the Reset Index page in the Search Service Application in Central Administration and clicked the “Reset Now” button.

To confirm the Index Reset, I clicked “OK” in the popup message.

Perform a Full Crawl on Search Content Sources

After resetting the index, the search index data was deleted and to allow search results to be shown again, we need to perform a Full Crawl on all Content Sources in the farm. To do that, we must go to the Content Sources page in the Search Service Application in Central Administration and for each available Content Sources, select “Start Full Crawl”.

NOTE: If you have more than one Content Source, let the Full Crawl on the previous Content Source finish before starting to Full Crawl the next Content Source.

After the Full Crawl on all Content Sources finished, I returned to Central Administration and the Search Service Application page to check the Search Service Application status. The page now indicates a healthy status for all Search components.

To confirm that the problem is solved, I ran the same commands previously executed in the PowerShell window.

$ssa = Get-SPServiceApplication -Name “Search Service Application”
Get-SPEnterpriseSearchStatus -SearchApplication $ssa -Detailed -Text

After execution, the result confirms that the problem with the Index Partion is solved,
showing an Activate state in the Index component.

After the above steps, SharePoint sites started returning search results again!

Related Articles

If you want to convert your tenant’s root classic site into a modern SharePoint site, click here.

This solution should be also valid for SharePoint 2016 and SharePoint 2019. If you want to know all about the new features available in the new SharePoint Server release, click here.

To find a solution to a search crawling issue I recently found in a SharePoint 2016 farm, click here.

To learn why your business should migrate to SharePoint Online and Office 365, click here and here.

SharePoint 2019 RTM was recently announced! To learn all about SharePoint 2019 and all its features, click here.

If you are a SharePoint administrator or a SharePoint developer who wants to learn more about how to install a SharePoint 2019 farm in an automated way using PowerShell, I invite you to click here and here.

If you want to learn how to upgrade a SharePoint 2013 farm to SharePoint 2019, click here and here.

If you want to learn all the steps and precautions necessary to successfully keep your SharePoint farm updated and be ready to start your move to the cloud, click here.

If you learn how to greatly speed up your SharePoint farm update process to ensure your SharePoint farm keeps updated and you stay one step closer to start your move to the cloud, click here.

If SharePoint 2019 is still not an option, you can learn more about how to install a SharePoint 2016 farm in an automated way using PowerShell, click here and here.

If you are involved in a SharePoint upgrade and want to learn more about the upgrade process, click here and here.

If you are new to SharePoint and Office 365 and want to learn all about it, take a look at these learning resources.

If you are work in a large organization who is using Office 365 or thinking to move to Office 365 and is considering between a single or multiple Office 365 tenants, I invite you to read this article.

If you want to know all about the latest SharePoint and Office 365 announcements from SharePoint Conference 2019, click here and here.

Hope this can help someone with the same problem!

Happy SharePointing!

The post How To Fix a Degraded Search Index Partition in a SharePoint 2013 farm appeared first on Blog IT.

]]> https://blogit.create.pt/miguelisidoro/2018/10/07/how-to-fix-a-degraded-search-index-partition-in-a-sharepoint-2013-farm/feed/ 6 SharePoint 2016: Problems crawling content and the “The crawler could not communicate with the server.” error message https://blogit.create.pt/miguelisidoro/2018/08/10/sharepoint-2016-problems-crawling-content-and-the-the-crawler-could-not-communicate-with-the-server-error/ https://blogit.create.pt/miguelisidoro/2018/08/10/sharepoint-2016-problems-crawling-content-and-the-the-crawler-could-not-communicate-with-the-server-error/#respond Fri, 10 Aug 2018 08:55:56 +0000 http://blogit.create.pt/miguelisidoro/?p=3734 Hello, Recently, after installing a SharePoint 2016 farm (to learn more on how to install a SharePoint 2016 farm in an automated way using PowerShell click here and here), I was configuring the Search Service Application in a customer’s SharePoint 2016 farm and got into a crawling error while trying to crawl the content of […]

The post SharePoint 2016: Problems crawling content and the “The crawler could not communicate with the server.” error message appeared first on Blog IT.

]]> Hello,

Recently, after installing a SharePoint 2016 farm (to learn more on how to install a SharePoint 2016 farm in an automated way using PowerShell click here and here), I was configuring the Search Service Application in a customer’s SharePoint 2016 farm and got into a crawling error while trying to crawl the content of one of the web applications that is configured to use a FQDN URL and https, for example https://intranet.contoso.com. This web application is using a Content Database that was migrated from SharePoint 2010 to SharePoint 2016.

The Problem

The error that was being thrown was during the Full Crawl of the Content Source was:

“The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error.”

Failed Attempts

When I saw this message, the first thought that crossed my mind was lack of permissions for the Default Content Access Account. The account was properly configured to have Full Read permissions on the web application and this was not the problem.

My next thought was that this could be a firewall problem and some ports necessary by the Search Service Application to properly crawl the web application content were not opened in the firewall (for a complete list of the necessary ports in a SharePoint 2016 installation, click here or here). However, after the firewall was properly configured, the error remained.

After some searching in the Internet, I tried without any success the following approaches:

  • Disabling the loopback check on the server
  • Disabling https for the web application
  • Creating a new empty web application with a FQDN URL and tried to crawl its contents
  • Resetting the search index
  • Deleting and recreating the content source

The Solution

After all the failed attempts, I was able to solve the problem by extending the web application to a non-FQDN URL (for example http://intranet) and configuring this URL as the start address in the Content Source in the Search Service Application. This URL is internal (the host is only configured in the server’s hosts file and is not configured in the DNS) and is being used for crawling purposes only.

Important detail: For the search results to be correctly presented, the newly added URL was configured in the Default Zone in Alternate Access Mappings (AAM) in Central Administration.

The goal here is to allow users to use the FQDN URL (ex: https://intranet.contoso.com) to access the SharePoint Portal and the search results to include this same URL.

If I had configured the non-FQDN URL in a non-Default zone in AAM, the search results would always include the non-FQDN URL instead of the FQDN URL that users use to access the SharePoint Portal. To learn all about using the Default Zone to crawl content and AAM, please read the following two fantastic articles by Brian Pendergrass:

I was able to configure a FQDN URL as the start address of a Content Source in the Search Service Application in one of my development environments without this problem, so I guess this behavior must be due to some infrastructure configuration in the customer’s environment which I have not yet been able to discover.
If I find a solution that allows the usage of a FQDN URL to be configured as the start address in the Content Source in the Search Service Application, I will update this post.

Hope this helps!

Related Articles

To learn why your business should migrate to SharePoint Online and Office 365, click here and here.

If you want to convert your tenant’s root classic site into a modern SharePoint site, click here.

In the meantime, new search capabilities have been introduced in SharePoint 2019. To learn more about them and all the new features in SharePoint 2019, click here.

If you are a SharePoint administrator or a SharePoint developer who wants to learn more about how to install a SharePoint 2019 farm in an automated way using PowerShell, I invite you to click here and here.

If you want to learn how to upgrade a SharePoint 2013 farm to SharePoint 2019, click here and here.

If you want to learn all the steps and precautions necessary to successfully keep your SharePoint farm updated and be ready to start your move to the cloud, click here.

If you learn how to greatly speed up your SharePoint farm update process to ensure your SharePoint farm keeps updated and you stay one step closer to start your move to the cloud, click here.

If SharePoint 2019 is still not an option, you can learn more about how to install a SharePoint 2016 farm in an automated way using PowerShell, click here and here.

If you are involved in a SharePoint upgrade and want to learn more about the upgrade process, click here and here.

If you are new to SharePoint and Office 365 and want to learn all about it, take a look at these learning resources.

If you want to know all about the latest SharePoint and Office 365 announcements from SharePoint Conference 2019, click here and here.

If you are work in a large organization who is using Office 365 or thinking to move to Office 365 and is considering between a single or multiple Office 365 tenants, I invite you to read this article.

Happy SharePointing!

The post SharePoint 2016: Problems crawling content and the “The crawler could not communicate with the server.” error message appeared first on Blog IT.

]]> https://blogit.create.pt/miguelisidoro/2018/08/10/sharepoint-2016-problems-crawling-content-and-the-the-crawler-could-not-communicate-with-the-server-error/feed/ 0 Azure Search Index with 2 datasources https://blogit.create.pt/ricardocosta/2017/11/10/azure-search-index-with-2-datasources/ https://blogit.create.pt/ricardocosta/2017/11/10/azure-search-index-with-2-datasources/#comments Fri, 10 Nov 2017 15:24:02 +0000 http://blogit.create.pt/ricardocosta/?p=1834 Recently I had the need to index documents stored in Azure Storage Blobs. Additionally I wanted to use the blob storage metadata also to add some information to those documents. Because I needed rich text information on the metadata I could use blob storage metadata directly. Se here why. So I had to use 2 […]

The post Azure Search Index with 2 datasources appeared first on Blog IT.

]]> Recently I had the need to index documents stored in Azure Storage Blobs. Additionally I wanted to use the blob storage metadata also to add some information to those documents. Because I needed rich text information on the metadata I could use blob storage metadata directly. Se here why.

So I had to use 2 different data sources. One for the documents and another to the metadata. So I chose Azure Blob Storage and Azure Table Storage. This is the full diagram of the final solution:

The indexers are responsible for updating the index with the contents of the 2 different data sources. There is a very important field that in my case it’s called the UniqueIdentifier field because this field is marked with the key property. This is the field that uniquely identifies each document on the Azure Search Index.

And it’s this field that is responsible for correlating the items that come from one data source (documents from blob storage) and items that come from the other data source (records from table storage).

Every document inserted in blob storage has a custom metadata property named also UniqueIdentifier that will have a table storage record associated with the corresponding metadata.


// Retrieve storage account from connection string.
CloudStorageAccount storageAccount = CloudStorageAccount.Parse(
                CloudConfigurationManager.GetSetting("StorageConnectionString"));

// Create the blob client.
CloudBlobClient blobClient = storageAccount.CreateCloudBlobClient();

// Retrieve a reference to a container.
CloudBlobContainer container = blobClient.GetContainerReference("mycontainer");

// Create the container if it doesn't already exist.
container.CreateIfNotExists();

// Add some metadata to the container.
container.Metadata.Add("UniqueIdentifier", "bla bla bla");

The table storage records have these values stored on the RowKey and the indexer have a mapping instruction to map the origin (RowKey) to the destination (UniqueIdentifier). You can check this mapping instruction later in the indexer schema.

First of all I created the Index:

(I’ve highlighted the UniqueIdentifier field wiht the Key property set to TRUE)


{
  "@odata.context": "https://something.search.windows.net/$metadata#indexes/$entity",
  "@odata.etag": "\"0x8D477848BDEFA50\"",
  "name": "full-index",
  "fields": [
    {
      "name": "ClientCode",
      "type": "Edm.String",
      "searchable": false,
      "filterable": true,
      "retrievable": true,
      "sortable": true,
      "facetable": true,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "UniqueIdentifier",
      "type": "Edm.String",
      "searchable": false,
      "filterable": true,
      "retrievable": true,
      "sortable": false,
      "facetable": false,
      "key": true,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "ETag",
      "type": "Edm.String",
      "searchable": false,
      "filterable": false,
      "retrievable": false,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "Timestamp",
      "type": "Edm.DateTimeOffset",
      "searchable": false,
      "filterable": false,
      "retrievable": false,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "Key",
      "type": "Edm.String",
      "searchable": false,
      "filterable": false,
      "retrievable": false,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "Opportunity",
      "type": "Edm.String",
      "searchable": true,
      "filterable": false,
      "retrievable": true,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": "pt-Pt.lucene"
    },
    {
      "name": "OpportunityCode",
      "type": "Edm.String",
      "searchable": false,
      "filterable": false,
      "retrievable": true,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "DocumentExtension",
      "type": "Edm.String",
      "searchable": false,
      "filterable": true,
      "retrievable": true,
      "sortable": false,
      "facetable": true,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "DocumentType",
      "type": "Edm.String",
      "searchable": false,
      "filterable": true,
      "retrievable": true,
      "sortable": false,
      "facetable": true,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "ClientName",
      "type": "Edm.String",
      "searchable": true,
      "filterable": true,
      "retrievable": true,
      "sortable": true,
      "facetable": true,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": "pt-Pt.lucene"
    },
    {
      "name": "Year",
      "type": "Edm.Int32",
      "searchable": false,
      "filterable": true,
      "retrievable": true,
      "sortable": true,
      "facetable": true,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "Path",
      "type": "Edm.String",
      "searchable": false,
      "filterable": false,
      "retrievable": true,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "LocalPath",
      "type": "Edm.String",
      "searchable": false,
      "filterable": false,
      "retrievable": true,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "Name",
      "type": "Edm.String",
      "searchable": true,
      "filterable": false,
      "retrievable": true,
      "sortable": true,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": "pt-Pt.lucene"
    },
    {
      "name": "content",
      "type": "Edm.String",
      "searchable": true,
      "filterable": false,
      "retrievable": false,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": "pt-Pt.lucene"
    },
    {
      "name": "metadata_storage_content_type",
      "type": "Edm.String",
      "searchable": false,
      "filterable": false,
      "retrievable": true,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "metadata_storage_size",
      "type": "Edm.Int64",
      "searchable": false,
      "filterable": false,
      "retrievable": true,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "metadata_storage_last_modified",
      "type": "Edm.DateTimeOffset",
      "searchable": false,
      "filterable": false,
      "retrievable": true,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "metadata_storage_content_md5",
      "type": "Edm.String",
      "searchable": false,
      "filterable": false,
      "retrievable": true,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "metadata_storage_name",
      "type": "Edm.String",
      "searchable": false,
      "filterable": false,
      "retrievable": true,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "metadata_storage_path",
      "type": "Edm.String",
      "searchable": false,
      "filterable": false,
      "retrievable": true,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "metadata_author",
      "type": "Edm.String",
      "searchable": false,
      "filterable": false,
      "retrievable": true,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "metadata_content_type",
      "type": "Edm.String",
      "searchable": false,
      "filterable": false,
      "retrievable": true,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "metadata_creation_date",
      "type": "Edm.DateTimeOffset",
      "searchable": false,
      "filterable": false,
      "retrievable": true,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    },
    {
      "name": "metadata_last_modified",
      "type": "Edm.DateTimeOffset",
      "searchable": false,
      "filterable": false,
      "retrievable": true,
      "sortable": false,
      "facetable": false,
      "key": false,
      "indexAnalyzer": null,
      "searchAnalyzer": null,
      "analyzer": null
    }
  ],
  "scoringProfiles": [],
  "defaultScoringProfile": "",
  "corsOptions": null,
  "suggesters": [
    {
      "name": "temp-suggester",
      "searchMode": "analyzingInfixMatching",
      "sourceFields": [
        "ClientCode",
        "Opportunity",
        "ClientName",
        "Name"
      ]
    }
  ],
  "analyzers": [],
  "tokenizers": [],
  "tokenFilters": [],
  "charFilters": []
}

After the index was created I’ve created the container and uploaded my files. This is the corresponding data source:


{
  "@odata.context": "https://something.search.windows.net/$metadata#datasources/$entity",
  "@odata.etag": "\"0x8D526E01DDB35F4\"",
  "name": "opportunities-datasource",
  "description": "",
  "type": "azureblob",
  "subtype": null,
  "credentials": {
    "connectionString": null
  },
  "container": {
    "name": "opportunities",
    "query": null
  },
  "dataChangeDetectionPolicy": null,
  "dataDeletionDetectionPolicy": null
}

I’ve also create the Table Storage and inserted the metadata records. This is the data source:


{
  "@odata.context": "https://something.search.windows.net/$metadata#datasources/$entity",
  "@odata.etag": "\"0x8D526E01DB70AF2\"",
  "name": "ecmcreatemeta",
  "description": "",
  "type": "azuretable",
  "subtype": null,
  "credentials": {
    "connectionString": null
  },
  "container": {
    "name": "opportunities",
    "query": null
  },
  "dataChangeDetectionPolicy": null,
  "dataDeletionDetectionPolicy": null
}

And these are the indexers. The documents indexer:


{
  "@odata.context": "https://something.search.windows.net/$metadata#indexers/$entity",
  "@odata.etag": "\"0x8D477862D23289E\"",
  "name": "full-indexer-blob",
  "description": "",
  "dataSourceName": "opportunities-datasource",
  "targetIndexName": "full-index",
  "schedule": null,
  "parameters": {
    "batchSize": 10,
    "maxFailedItems": 10,
    "maxFailedItemsPerBatch": 10,
    "base64EncodeKeys": false,
    "configuration": {
      "dataToExtract": "contentAndMetadata",
      "failOnUnsupportedContentType": false,
      "indexedFileNameExtensions": ".pdf, .docx, .doc, .xlsx, .xls, .pptx, .ppt, .msg, .html, .htm, .xml, .zip, .eml, .txt, .json, .csv"
    }
  },
  "fieldMappings": [],
  "disabled": null
}

And the metadata indexer:


{
  "@odata.context": "https://something.search.windows.net/$metadata#indexers/$entity",
  "@odata.etag": "\"0x8D47784D3CE80DF\"",
  "name": "full-indexer-meta",
  "description": "",
  "dataSourceName": "ecmcreatemeta",
  "targetIndexName": "full-index",
  "schedule": null,
  "parameters": {
    "batchSize": null,
    "maxFailedItems": 0,
    "maxFailedItemsPerBatch": 0,
    "base64EncodeKeys": false,
    "configuration": {}
  },
  "fieldMappings": [
    {
      "sourceFieldName": "PartitionKey",
      "targetFieldName": "ClientCode",
      "mappingFunction": null
    },
    {
      "sourceFieldName": "RowKey",
      "targetFieldName": "UniqueIdentifier",
      "mappingFunction": null
    }
  ],
  "disabled": null
}

That is the RowKey UniqueIdentifier mapping function. That is how Azure Search will map the records from table storage to documents inside the index.

The post Azure Search Index with 2 datasources appeared first on Blog IT.

]]> https://blogit.create.pt/ricardocosta/2017/11/10/azure-search-index-with-2-datasources/feed/ 1 Using KeywordQuery with CSOM SharePoint Online https://blogit.create.pt/ricardocosta/2017/10/25/using-keywordquery-with-csom-sharepoint-online/ https://blogit.create.pt/ricardocosta/2017/10/25/using-keywordquery-with-csom-sharepoint-online/#comments Wed, 25 Oct 2017 14:27:12 +0000 http://blogit.create.pt/ricardocosta/?p=1744 string username = "***********"; string pwd = "*********"; string siteURL = "**********"; ClientContext context = new ClientContext(siteURL); Web web = context.Web; SecureString pass = new SecureString(); foreach (char c in pwd.ToCharArray()) pass.AppendChar(c); context.Credentials = new SharePointOnlineCredentials(username, passWord); try { KeywordQuery query = new KeywordQuery(context); query.QueryText = "ContentType:Factura AND PrecoOWSCURR>10000"; query.RowLimit = 10; query.RowsPerPage = 10; […]

The post Using KeywordQuery with CSOM SharePoint Online appeared first on Blog IT.

]]> string username = "***********"; string pwd = "*********"; string siteURL = "**********"; ClientContext context = new ClientContext(siteURL); Web web = context.Web; SecureString pass = new SecureString(); foreach (char c in pwd.ToCharArray()) pass.AppendChar(c); context.Credentials = new SharePointOnlineCredentials(username, passWord); try { KeywordQuery query = new KeywordQuery(context); query.QueryText = "ContentType:Factura AND PrecoOWSCURR>10000"; query.RowLimit = 10; query.RowsPerPage = 10; SearchExecutor search = new SearchExecutor(context); ClientResult<ResultTableCollection> results = search.ExecuteQuery(query); context.ExecuteQuery(); foreach (var resultRow in results.Value[0].ResultRows) { Console.WriteLine("{0}", resultRow["Title"]); } } catch (Exception e) { Console.WriteLine(e.ToString()); Console.ReadKey(); }

The post Using KeywordQuery with CSOM SharePoint Online appeared first on Blog IT.

]]> https://blogit.create.pt/ricardocosta/2017/10/25/using-keywordquery-with-csom-sharepoint-online/feed/ 2 the European SharePoint Conference 2015 was great! https://blogit.create.pt/andrevala/2015/11/14/the-european-sharepoint-conference-2015-was-great/ https://blogit.create.pt/andrevala/2015/11/14/the-european-sharepoint-conference-2015-was-great/#comments Sat, 14 Nov 2015 00:02:05 +0000 http://blogit.create.pt/andrevala/?p=1941 The fourth edition of the European SharePoint Conference has now finished and it was bigger and better than ever. It took place in the wonderful city of Stockholm, in Sweden, from November 9th to November 12th. Like in previous years, the first day was dedicated to pre-conference full-day tutorials and the conference actually started in […]

The post the European SharePoint Conference 2015 was great! appeared first on Blog IT.

]]> The fourth edition of the European SharePoint Conference has now finished and it was bigger and better than ever. It took place in the wonderful city of Stockholm, in Sweden, from November 9th to November 12th. Like in previous years, the first day was dedicated to pre-conference full-day tutorials and the conference actually started in the second day. It featured a large exposition floor for sponsors to present their products and services, and also a community area with soapbox sessions during session intermissions and meals. The conference got over 1,500 delegates from over 50 different countries.

The programme team did a great job going through over 700 session submissions and putting together a stellar lineup of great speakers while also broadening the scope of the conference to include Office 365 and Microsoft Azure along with the SharePoint-related content. Congratulations to Wim Dierickx, Göran Husman, Adis Jugo and Nicki Borell. I was on the programme team last year and I know how hard it is to select the sessions and speakers, and put together a compelling programme.

The first keynote was delivered by Seth Patton, Jeff Tepper and Bill Baer, and this fact alone demonstrates how much Microsoft is invested in connecting with the community. The keynote was mostly focused on:

  • Usage and adoption statistics for Office 365
  • New and improved features that recently rolled out in Office 365
  • Near future roadmap for Office 365
  • What’s New in SharePoint Server 2016

Regarding usage and adoption, Office 365 has some impressive statistics:

  • Over 75,000 customers which account for more than 160 million users
  • 200% monthly active user growth
  • 7 Billion Office documents stored in OneDrive for Business, team sites and other SharePoint portals, which represents a 500% year-on-year growth in content
  • Runs on 30,000 servers, with 20,000 SQL databases, on 19 datacenters around the world.

As for new features and near future roadmap for Office 365, Jeff Tepper and Bill Baer shared that:

  • OneDrive for Business will now have a new rock-solid sync client (which has been in preview for a few weeks) and already has mobile apps for all devices. It recently got a revamped UI with a better browsing and sharing experience, and better tooling for IT management.
  • SharePoint Online has rolled-out improvements in collaboration, co-authoring and external sharing features.
  • The new Office 365 groups and their tight integration with Outlook 2016 is helping people to be more productive, adapting the technology to the users and not the other way around.
  • Delve and the Office Graph are also evolving, with new APIs and the new analytics features that are now in development.

The biggest announcement was the release of a second and last beta version of SharePoint Server 2016 before the end of the month, which will be nearly feature complete. The new features of SharePoint Server 2016 were already known since Microsoft Ignite a few months back, but it was still interesting to hear about the enhanced mobile experience, robust and cloud inspired infrastructure, and the compliance and data loss prevention features.

My session was about “Content Recommendation with SharePoint Search” and I think it was well received by the 100 or so attendees in the room, but having to deliver a session on the afternoon of the last day usually means I’m not going to enjoy the conference because I’ll be too worried fine tuning the slides and demos, and practicing the presentation until almost the end. If you’re interested in the presentation contents check the slide deck on SlideShare.

Nevertheless, I still managed to attend a few sessions by really good presenters:

  • Radi Atanassov (@RadiAtanassov) presented a great session on Office 365 Dev Patterns and Practices.
  • Chris O’Brien (@ChrisO_Brien) gave some fantastic tips on what you should and shouldn’t do when developing for Office 365.
  • Marius Constantinescu (@c_marius) showed us how to use Lightswitch to build cloud business apps in Visual Studio.
  • Nuno Costa (@ndocosta) and João Oliveira (@joaopcoliveira), fellow Portuguese Microsoft guys, delivered a brilliant talk on Office 365 governance with PowerShell and CSOM.
  • Rodrigo Pinto (@ScoutmanPt), fellow Portuguese MVP, got to present two great sessions: one on PowerShell Desired State Configuration and another one on techniques to migrate full trust solutions to the add-in model.
  • Edin Kapic (@ekapic) made complex topics such as authentication and authorization seem simple as he showed how to build a custom claims provider for SharePoint. Pretty epic stuff.
  • Knut Relbe-Moe (@sharePTkarm) dove deep into the Office 365 group and filled a room even on the last session slot of the conference.

It was a nice surprise to find Pedro Serrano and Daniel Pereira from Cave Digital showing off their Smart Governance product in the expo floor, and Alex Ferreira (@alexaem) and Tiago Duarte (@tduarte85) attending the conference. It’s always great meeting Portuguese friends when we’re far away from home.

Overall it was a great experience and the team in charge of the organization has done a tremendous job. If I had to point out three highlights of the event, those would be:

  • The venue for the awards gala, which was absolutely fantastic, and the venue for the conference. It will be very hard to top that next year.
  • The networking opportunities.
  • The speaker and session lineup, which included top Microsoft executives.

Next year the European SharePoint Conference will take place in Vienna, Austria, on November 14-17, and I hope I can be there again.

The post the European SharePoint Conference 2015 was great! appeared first on Blog IT.

]]> https://blogit.create.pt/andrevala/2015/11/14/the-european-sharepoint-conference-2015-was-great/feed/ 2 European SharePoint Conference 2015 https://blogit.create.pt/andrevala/2015/04/10/european-sharepoint-conference-2015/ https://blogit.create.pt/andrevala/2015/04/10/european-sharepoint-conference-2015/#comments Fri, 10 Apr 2015 21:33:54 +0000 http://blogit.create.pt/andrevala/?p=1841 The programme for the European SharePoint Conference 2015 was announced yesterday and guess what? I’ll be presenting a session on day 3 (November 12th) about Content Recommendation with SharePoint Search! You’ll also find my good friend and SharePoint MVP Rodrigo Pinto, as well as Nuno Oliveira Costa and João Oliveira, from Microsoft Portugal, among the […]

The post European SharePoint Conference 2015 appeared first on Blog IT.

]]> The programme for the European SharePoint Conference 2015 was announced yesterday and guess what? I’ll be presenting a session on day 3 (November 12th) about Content Recommendation with SharePoint Search! You’ll also find my good friend and SharePoint MVP Rodrigo Pinto, as well as Nuno Oliveira Costa and João Oliveira, from Microsoft Portugal, among the speakers.

The conference will take place in Stockholm, Sweden, from November 9th to November 12th, and has a fantastic session lineup from some of the best speakers in the business. The programme team did a great job putting it together. I know how hard it is to select 100 breakout sessions and 8 full-day tutorials out of several hundred candidates to build a balanced and interesting session lineup.

If you have not attended in previous years, I highly recommend it. It’s well worth it.
You still have 7 days to grab the ticket at Super Early Booking Rate (ends on April 17th) so, if you’re considering attending, don’t wait!

I’ll see you there!

The post European SharePoint Conference 2015 appeared first on Blog IT.

]]> https://blogit.create.pt/andrevala/2015/04/10/european-sharepoint-conference-2015/feed/ 1 Querying SharePoint Search from PowerShell https://blogit.create.pt/andrevala/2014/12/11/querying-sharepoint-search-from-powershell/ https://blogit.create.pt/andrevala/2014/12/11/querying-sharepoint-search-from-powershell/#comments Thu, 11 Dec 2014 15:32:13 +0000 http://blogit.create.pt/andrevala/?p=1791 FAST Search for SharePoint 2010 (FS4SP) is a really powerful, flexible and scalable enterprise search engine. However, when compared with the search landscape in SharePoint 2013, it feels like a separate product, an add-on to SharePoint 2010 that gives you a more powerful alternative to the out-of-the-box search engine. When using FS4SP in a production […]

The post Querying SharePoint Search from PowerShell appeared first on Blog IT.

]]> FAST Search for SharePoint 2010 (FS4SP) is a really powerful, flexible and scalable enterprise search engine. However, when compared with the search landscape in SharePoint 2013, it feels like a separate product, an add-on to SharePoint 2010 that gives you a more powerful alternative to the out-of-the-box search engine.

When using FS4SP in a production environment, you need a separate farm just for FAST. That is, you need a set of servers where you install FS4SP and then you connect that FAST farm to a SharePoint farm, by means of two Search Service Applications. These FAST servers don’t have SharePoint installed on them and they have their own PowerShell snap-in that allows you to perform a whole bunch of administration tasks on FS4SP.

Suppose you want to query your search index, for testing or maintenance purposes, in PowerShell. The easiest solution would be to open your SharePoint 2010 Administration PowerShell console, and use the Server Side Object Model to create a new KeywordQuery object and invoke the Execute method on it. You can find many blog posts that teach how to do this. Here’s one example. If, for some reason, you need to run that PowerShell script from one of the FAST servers it won’t work because these servers don’t have SharePoint installed and are not part of the SharePoint farm, hence you can’t use the Server Object Model.

In this case, you’ll need to use the search web service, which can be called from any server as long as it can communicate with the SharePoint farm. The script below shows how you can do this.

$WebApplicationURL = "http://myserver:9999"
$SearchServiceURL = "/_vti_bin/search.asmx"

# Create a proxy to call the search web service
$SearchWS = New-WebServiceProxy -Uri ($WebApplicationURL + $SearchServiceURL) -UseDefaultCredential

# Build the query XML. You can use FQL or KQL.
$queryXml = @"
<QueryPacket Revision="1000">
  <Query>
    <Context>
      <QueryText language="en-US" type="FQL">SharePoint</QueryText>
    </Context>
    <SupportedFormats Format="urn:Microsoft.Search.Response.Document.Document" />
    <ResultProvider>FASTSearch</ResultProvider>
    <Range>
      <StartAt>1</StartAt>
      <Count>100</Count>
    </Range>
    <EnableStemming>On</EnableStemming>
    <EnableSpellCheck>Off</EnableSpellCheck>
    <IncludeSpecialTermsResults>true</IncludeSpecialTermsResults>
    <IncludeRelevantResults>true</IncludeRelevantResults>
    <ImplicitAndBehavior>true</ImplicitAndBehavior>
    <TrimDuplicates>true</TrimDuplicates>
    <Properties>
      <Property name="Rank" />
      <Property name="Title" />
      <Property name="Author" />
      <Property name="Write" />
      <Property name="Path" />
    </Properties>
  </Query>
</QueryPacket>
"@

# call the web service
$results = $SearchWS.QueryEx($queryXml)

# process the results
if ($results -ne $null -And $results.Tables["RelevantResults"] -ne $null)
{
    # check the result count (this page) and the total result count (all pages)
    $resultCount = $results.Tables["RelevantResults"].Rows.Count
    $totalCount = $results.Tables["RelevantResults"].ExtendedProperties["TotalRows"]
    Write-Host "Retrieved $resultCount (from a total of $totalCount) results."
   
    # write the title of each result in the console window
    foreach ($row in $results.Tables["RelevantResults"].Rows)
    {
        Write-Host $row["Title"]
     }
}

The post Querying SharePoint Search from PowerShell appeared first on Blog IT.

]]> https://blogit.create.pt/andrevala/2014/12/11/querying-sharepoint-search-from-powershell/feed/ 2 FAST Search Tip #1: Enabling Stemming in PowerShell https://blogit.create.pt/andrevala/2012/04/25/fast-search-tip-1-enabling-stemming-in-powershell/ https://blogit.create.pt/andrevala/2012/04/25/fast-search-tip-1-enabling-stemming-in-powershell/#respond Wed, 25 Apr 2012 07:15:31 +0000 http://blogcreate.azurewebsites.net/andrevala/?p=201 Recently, I’ve been working with FAST Search for SharePoint 2010 and, although it’s a great search platform with pretty impressive features, I believe there are still too many manual installation and configurations steps, and too many of those features are only accessible through PowerShell. Don’t get me wrong, PowerShell is great and, by far, the […]

The post FAST Search Tip #1: Enabling Stemming in PowerShell appeared first on Blog IT.

]]> Recently, I’ve been working with FAST Search for SharePoint 2010 and, although it’s a great search platform with pretty impressive features, I believe there are still too many manual installation and configurations steps, and too many of those features are only accessible through PowerShell. Don’t get me wrong, PowerShell is great and, by far, the best way to deploy your solution to the client’s environment, but a little more graphical UI wouldn’t hurt.

According to FAST Search’s TechNet documentation, you can use the Set-FASTSearchMetadataManagedProperty cmdlet to configure the main settings of a managed property. Among other things, you can enable stemming for a specific managed property. Here’s how it’s done:

$title = Get-FASTSearchMetadataManagedProperty –Name title
Set-FASTSearchMetadataManagedProperty –ManagedProperty $title –StemmingEnabled $true

The problem is that this doesn’t work. The StemmingEnabled argument is actually ignored by the cmdlet so, we need to use a different approach. This is the right way:

$title = Get-FASTSearchMetadataManagedProperty –Name title
$title.StemmingEnabled = 1
$title.update()

Although Microsoft is yet to update TechNet’s documentation, it has published a support article in its knowledge base (KB2468430) which describes this very solution.

The post FAST Search Tip #1: Enabling Stemming in PowerShell appeared first on Blog IT.

]]> https://blogit.create.pt/andrevala/2012/04/25/fast-search-tip-1-enabling-stemming-in-powershell/feed/ 0 Integrate SharePoint Server 2007 with Search Server 2008 https://blogit.create.pt/raulribeiro/2008/09/01/integrate-sharepoint-server-2007-with-search-server-2008/ https://blogit.create.pt/raulribeiro/2008/09/01/integrate-sharepoint-server-2007-with-search-server-2008/#respond Mon, 01 Sep 2008 05:29:00 +0000 http://blogcreate.azurewebsites.net/raulribeiro/?p=961 If you have a client that needs a SharePoint 2007 Farm, with for example one SharePoint front-end and a index server, Microsoft recommends that you install, in the index server, Search Server 2008.  But to integrate this two products, you need to install the Infrastructure Update (Microsoft SharePoint Team Blog) on each server on the farm. […]

The post Integrate SharePoint Server 2007 with Search Server 2008 appeared first on Blog IT.

]]> If you have a client that needs a SharePoint 2007 Farm, with for example one SharePoint front-end and a index server, Microsoft recommends that you install, in the index server, Search Server 2008.

 But to integrate this two products, you need to install the Infrastructure Update (Microsoft SharePoint Team Blog) on each server on the farm.

To install Infrastructure Update, you should start on the Central Administration Server, then a message will appear saying that if you have more servers in the farm, you should install Infrastructure Update on them an then return to the Central Administration Server and continue with the installation.

In one of the my Infrastructure Update installations there was a strange problem with one of the servers and the installation was failing. After research and looking into SharePoint logs i discovered that it's necessary to have the Windows SharePoint Services Web Application start in all SharePoint Servers for the Infrastructure Update to be installed successfully.

At last if you have clients that only wants to use WSS 3.0 you should install Search Server 2008 Express, because it installs WSS 3.0 and also the Search Server index capabilities.

The post Integrate SharePoint Server 2007 with Search Server 2008 appeared first on Blog IT.

]]> https://blogit.create.pt/raulribeiro/2008/09/01/integrate-sharepoint-server-2007-with-search-server-2008/feed/ 0