When adding the Content Search Web Part to a site for the first time, the web part took a while to load, then displayed the error:
One or more of the following resource files failed to load: /_catalogs/masterpage/display templates/language files/en-GB/customstrings.js?ctag=322$$15.0.4569.1000
To look for the missing file I went to Site Settings, then Master page and page layouts, which is under the heading Web Designer Galleries. On that page I navigated through Display Templates -> Language Files. I could see that for some reason the en-GB folder was missing.
The fact that the folder was missing was odd because I’d used the Content Search Web Part before within the Site Collection. Anyway, to resolve the error I created the en-gb folder and copied customstrings.js from the en-us folder and pasted it into en-gb.
In SharePoint 2010 it was easy to switch between languages using the user menu within SharePoint. To switch language In SharePoint 2013 open Control Panel -> Language and click Add a language.
Once you’ve added the required languages switch between them by moving the language you want to use to the top of the list.
Close and re-open your browser for the change to be recognised.
When you install SharePoint Server 2013 the Distributed Cache service is configured to use 10% of the RAM on the server. Half of the 10% is used for caching and the other half is used for memory management. If you add RAM to the server you need to manually re-configure the Distributed Cache service to make use of the extra RAM.
To check the current RAM allocation run the command below from an elevated SharePoint 2013 Management Shell, replacing the server name as necessary.
Get-AFCacheHostConfiguration -ComputerName ServerName -CachePort “22233”
Calculate the new Distributed Cache service cache size for a 24 GB SharePoint Server as follows:
10% of 24 GB = 2.4 GB
Divide 2.4 GB by 2 = 1.2 GB
Convert 1.2 GB to MB = 1229 MB
Stop the Distributed Cache service on each host using Central Administration -> System Settings -> Manage services on server.
Run the command below from an elevated SharePoint 2013 Management Shell on one host at a time, replacing the cache size as necessary.
Update-SPDistributedCacheSize -CacheSizeInMB CacheSize
Start the Distributed Cache service on each host using Central Administration -> System Settings -> Manage services on server.
The SharePoint 2010 CSV Bulk Taxonomy TermSet Importer/Exporter enables the import and export of taxonomies from the SharePoint Term Store. It’s available on CodePlex and supports SharePoint 2010. I like to use the tool to move taxonomies between development, test and live environments. In this post I’ll show how to recompile the tool to support SharePoint 2013.
Download the source code from this page. Extract the zip file and open the solution in Visual Studio 2012. From Solution Explorer, right click on the project and select properties.
Change the target Framework to .NET Framework 4.
From Solution Explorer, expand References and right click on Microsoft.SharePoint and choose Remove. Repeat for Microsoft.SharePoint.Taxonomy.
On your SharePoint server navigate to C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\ISAPI. Copy Microsoft.SharePoint.dll and Microsoft.SharePoint.Taxonomy.dll. Paste them into the route folder containing the source code.
In Solution Explorer right click on References and choose Add Reference. Click Browse and navigate to the folder containing the two dlls. Add both the dlls to the project.
Right click on the Solution and choose Build Solution.
Copy the contents of the Debug folder to your SharePoint server and use the tool as described on CodePlex.
SQL Server Reporting Services (SSRS), when integrated into SharePoint 2013 enables reports to be sent to users via email. From the report click Manage Subscriptions.
On the following screen click Add Subscription. You can configure the report options and click OK to save.
If you’ve not configured SSRS you may receive an error in the Application Event log on the SharePoint server hosting the SSRS service application. This could take the form:
The Report Server Email extension failed to read its configuration settings from the rsreportserver.config configuration file. The extension is not available to users. (Application: SQL Server Reporting Services Service Application, CorrelationId: …)
The web page may also fail to load, with an error like the one below.
If you encounter this error, open the SQL Server Reporting Services Service Application from Central Administration. Next, open e-mail settings and configure the SMTP server. Finally, open Provision subscriptions and alerts, enter the appropriate account details and click Ok.
Following a migration to SharePoint 2013, one user had the error whereby every time they loaded SharePoint they were confronted with the error “Error: User Settings Not Initialized”.
In order to fix the error, open the User Profile Service Application from Central Administration. Next, click on Manage User Profiles and search for the affected user. Choose Edit My Profile.
Scroll down to the bottom of the profile screen and select Always use my personal settings and select the appropriate locale. Next, tick Use language and regional settings. Click save and close.
The error should now have been resolved. You can go back into the user profile and reset the two options you just changed.
Within SharePoint 2013 you have the ability to create an Asset Library. This is a special type of SharePoint library, which is optimised for the storing of image, audio, or video files. If you’re not familiar with this type of library take a look at this TechNet article.
One of the nice features of the Asset Library is the keywords column. This enables you to assign metadata in the form of keywords, which can help with the discovery of library items using search. For example, an image of an car could have the keywords transport or vehicle assigned to it. Then, if a user searched for car, transport, or vehicle they would find the image.
I’m going to show the configuration required to enable searching for items using keywords. Firstly, open the Asset Library settings and check the name of the keywords column.
Next, navigate to Central Administration and open the Search Service Application from Application Management > Manage service applications. Open the Search Schema.
Click on Crawled Properties and enter keywords, then click the green arrow to search.
Click on the managed property called Keywords. On the page that loads, tick the Searchable box and click Ok to save the changes. Now, re-index the Asset Library, open the library settings, then Advanced settings.
Once the crawl has completed you’ll be able to search for images using keywords.