Friday, February 22, 2013

SharePoint 2013: Image Preview in Search Results - Part II

This is the second post on previewing images in SharePoint search results. The first post is here.

In the first post I demonstrated a way to display image previews in search results and resolved two problems. But what about the images in a Picture Libary? I didn't see them appear in search results as pictures until I added the file types. Shouldn't there be special results for Picture types?

UPDATE: Get the source files here


Previewing of Images Stored In Picture Libraries

Problem #1: Images in Picture Libraries Returned as Files or List Items
After going through the steps in Part I , even images stored in Picture Libraries are returned as files themselves. The hover works fine but you should be able to take advantage of the image result type.

Solution to Problem #1: Copy and Configure the Image Result Type

In your Search Center site collection select Site settings from the settings menu:

Under Site Collection Administration, click on Search Result Types:


Scroll down and find Image. Use the drop-down menu and select Copy:


On the Add Result Type page, select Picture Item udner What should these results look like?


Click Save:
Run a search for an item in a Picture Library:



 
There is a preview image right in the results! That's great but that didn't happen in image results from other types of libraries - onto Problem #2.
 
Problem #2: Image Search Results Not Consistent
Now the results from a Picture Library and non-Picture Library look different. It is not consistent for the user:

Solution to Problem #2: Modify the Display Template for the Result.
This time you need to edit the Item_Picture.html file.

Simply add an else statement to the if in the middle of the code:

 else {
           ctx.CurrentItem.csr_PreviewImage = ctx.CurrentItem.Path;
      }


(If you only see .js files, the .js code to  modify is at the bottom of this post)

Save the file and run a search again:

 


Now all images that are returned have a preview image in the results!!!!

But now the hover is the Picture Library List item hover, not the one I modified in the first post. So in the next and last post of this series I modify that hover to include a larger preview!



If you are not running search in a Search Center Site Collection and/or you only see .js files in your Search Display Templates, here is the resultant .js code to paste over after the render header in Item_Picture.js:

    if(!Srch.U.n(ctx.CurrentItem.PictureThumbnailURL) && !ctx.CurrentItem.IsContainer) {
     ctx.CurrentItem.csr_PathLength = Srch.U.pathTruncationLengthWithPreview;
                    ctx.CurrentItem.csr_PreviewImage = ctx.CurrentItem.PictureThumbnailURL;
       }
      else {
           ctx.CurrentItem.csr_PreviewImage = ctx.CurrentItem.Path;
      }



 

SharePoint 2013: Image Preview in Search Results - Part I

I was discussing SharePoint Search previews of images on Twitter with Jasper Oosterveld . The discussion made me look into image previews in search results. As a result, I looked at various options and functionality to this regard. I am splitting these posts into at least two parts so I can get part of my solution out as soon as possible. This post solves the previewing of images that are not in Picture Libraries.

UPDATE: Get the source files here

Previewing of Images Not Stored in Picture Libraries

Problem #1: Image Search Results Are List Items

When images are stored in "regular" document libraries such as Site Assets, they are uploaded as documents. When the library is crawled, the results are the actual list item and not the image itself. Even if you add the Image or Picture content type to the library and modify the item, the result is still treated like a list item.

Solution to Problem #1:  Add Image File Types to Search
The reason the images are coming back as items is because image file types such as .jpg and .gif are not in the list of the search file types.

So you need to go to Central Administration and modify the Search Service Application. On the left hand side click on File Types:


On the File Types page, click on New File Type:



Enter an image file type such as jpg and click ok:



Repeat the process for other image types you want to handle.

Now go to the document library that contains the images and select Library settings from the Library top ribbon:


On the Settings page, click on Advanced Settings:


Scroll down and find the Reindex Document Library button and click it:


In the dialog that appears, click Reindex Document Library:

Click OK on the Advanced Settings page.

Now return to your Search Service Application and run an incremental crawl on the main content source:


After the crawl is completed, the search results of the images should appear as their filename instead of a list item. That solves that problem but the hover is still the Default hover template and doesn't show an image preview.


Problem #2: Image Search Results Hover Doesn't Show Preview
Now that the search is crawling image types, the results display the image file but the hover is using the default item template and no image appears.
  

UPDATE: You do not need to go through the modification of the default hover although I did in the beginning before I figured out all that was happening. The overall cause of this issue is that Image result type uses the Default Item template and not the Picture template. My solutions in Part II and Part III explain how do implement this better.


Solution to Problem #2: Modify the Default Hover Panel Display Template
The solution here is to modify the hover display template that is being used for default items. This can be easily performed using SharePoint Designer 2013. Follow the steps to get to the Display Templates as I have outlined previously.
This time, edit the Item_Default_HoverPanel.html file. Replace the RenderBody section with the following code:

                <!--#_
                    if(ctx.CurrentItem.FileExtension == "jpg" || ctx.CurrentItem.FileExtension == "gif"){
_#-->
                        <div class="ms-srch-hover-imageContainer">
                            <img id="_#= ctx.CurrentItem.csr_id =#_" src="_#= $urlHtmlEncode(ctx.CurrentItem.Path) =#_" onload="this.style.display='block';" />
                        </div>
<!--#_
                }
                else {
_#-->
    <div id="_#= $htmlEncode(id + HP.ids.body) =#_" class="ms-srch-hover-body">
                    _#= ctx.RenderBody(ctx) =#_
                </div>
<!--#_
                }
_#-->
         
 

You may add more conditions for each file type you want to handle. You could also check the content type however, by default, the images loaded to Site Assets are documents. So if you want to capture all images I would use the file extension check.

Save those changes and then perform a search. Hover over the image results:


Voila!!! The hover shows a preview of the image!!!

But that's not all folks. If you have Picture Libraries you could have even better results and previews but then that change will negate the solution provided here. I discuss this functionality and customization in my Part II post.




Saturday, February 16, 2013

Windows Azure: Accessing Your SharePoint VM from a Local Browser

If you have created a Virtual Machine in Windows Azure for SharePoint and would like to be able to access the SharePoint site from your local browser instead of on the server itself via remote desktop, just follow these simple easy steps to make it happen.

First navigate to your Windows Azure management portal and select the Virtual Machines:
 
Select the SharePoint VM top open up the Dashboard. Click the ENDPOINTS link:

 
At the bottom of the Endpoints screen, click on ADD ENDPOINT. The Add Endpoint dialog appears.

 
Click the Next arrow on the the first page of the dialog wizard:

 
Enter a name and 80 for the ports. Click the Complete Check button:
 


 
The VM is updated with the endpoint which takes about 30-60 seconds:



 

 
When the update is complete, a green check mark appears next to the name. When this happens, click on the DASHBOARD link to return to the VM dashboard:
 
 


Back on the VM dashboard page, locate and copy the public virtual IP address located on the right hand side of the page under the quick glance section:
 
Using Windows Explorer on your local machine, navigate to C:\Windows\System32\drivers\etc. Locate the Hosts file and double click to open. Open with Notepad.


 
Inside the hosts file, paste the IP address and add the host name. The host name could be the server name, a host header name, and/or your SharePoint root URL. 
 
 
Open a browser on the local machine and enter http://hostname. When prompted enter your SharePoint VM credentials (don't forget the domain name). Your browser should render your SharePoint VM root site collection accordingly:


 

Tuesday, February 12, 2013

SharePoint 2013: SQL Server Reporting Services Service Not Appearing in Services on Server


I previously went through the process of building a Reporting Services Server in SharePoint 2013 Integrated mode which I documented in my post here.

The database team decided they wanted another dedicated Reporting Services Server added to our staging farm. Fine. Sure. No problem. I have the steps documented and we should probably just follow the ones for the Report Server.

So we both did that and I could not see SQL Server Reporting Services Service under Services on Server in SharePoint Central Administration. So I thought something was wrong. I tried several different things and reinstalling/repairing SQL Server 2012 and SQL Server 2012 SP1. I was banging my head.

Then I realized..wait a second...didn't I run some PowerShell commands before?? Yes I did. I just forgot to include them in the original post (which I just updated anyway).

So if you do not see SQL Reporting Services Service running on the Report Server, you need to register and start the SQL Server Reporting Services on the server using PowerShell commands within the SharePoint 2013 Management Shell (on the Report Server):

Install-SPRSService
Install-SPRSServiceProxy

get-spserviceinstance -all |where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance


 

Wednesday, February 6, 2013

SharePoint 2013: The license state for the current server doesn't match the farm's license state

PROBLEM/SCENARIO:

I needed to add a new server to our SharePoint 2013 staging environment. Upon running the SharePoint Configuration Wizard to connect to an existing farm, I received a Configuration Failed message:


Failed to connect to the configuration database.

The license state for the current server doesn't match the farm's license state.


I found a SharePoint 2010 blog post here that gave some insight. Essentially that post talked about reviewing the Properties column in the Config database and reviewing the Registry.

The properties in the database showed four (4) GUIDS:

<sFld type="Guid">ccd2be5b-dcb6-4fbe-8087-3e5c82244473</sFld>

<sFld type="Guid">52d457f6-ae45-4221-9bc5-1912a8861c00</sFld>

<sFld type="Guid">9ff54ebc-8c12-47d7-854f-3865d4be8118</sFld>

<sFld type="Guid">b7d84c2b-0754-49e4-b7be-7ee321dce0a9</sFld>

The registry also showed the same:


I figured that some of these should not be on there or that the new server did not have something. After some more digging I found a post on the MSDN forums here.

What that told me was that I was in the same boat and that there was some residue from SharePoint 2013 Preview version.The answer there was to rebuild the farm --- ahhhh. I didn't feel like going through all that trouble. That has got to be an easier way!!!


SOLUTION:

I found a way to determine which SharePoint products were installed by using the PowerShell code posted on the PhoeNIXBird Networks site here.


I figured out that all of the products that started with 2015 needed to be removed.

Therefore, I used msiexec /x along with each identifying number to remove the old Preview versions:


I had to repeat the process on each server that was currently in the "corrupted farm". I performed the same initial commands to make sure all of the old products were removed:


Next, I decided I should refresh the installed products on the farm just in case. That was also PowerShell but since it uses SharePoint cmdlets, I opened up the SharePoint Management Console to run the refresh:


This doesn't appear to do anything and is pretty quick.

Next, for good measure, I ran the SharePoint Configuration Wizard on the servers that I just removed the old Preview version from.

I was then able to run the SharePoint Configuration Wizard on the new server and have it join to the farm!!! Much less work than rebuilding the entire farm!!!


 

Matched Content