A chronicle of issues encountered in SharePoint

Month: March 2012 Page 1 of 2

Missing PDF icon images in SharePoint 2010

I inherited a SharePoint 2010 environment that had the PDF iFilter installed but was not showing the PDF icon for any of the PDF files.  It took a lot to resolve this issue, which is crazy.  It should’ve been simple.  So I’m writing about my adventures to spare you all from the anguish I faced.  I’ve broken up this message into five sections since it’s long.

1.  The Microsoft KB article does not suffice
2.  SharePoint Sharon’s article has a fatal flaw
3.  Zubair Alexander to the rescue
4.  Double quotes pain
5.  Conclusion

Microsoft KB article
I figured I would just use the Microsoft KB article for installing the PDF iFilter since it also covers setting up the display of the PDF icon.  However, it leaves a lot to be desired.  Namely, the first three bullet points at the end are either vague or inaccurate.   First, I had trouble with “Restart the SharePoint Server Search 14” but another article clued me in on that.  (I have posted the instructions at the end of this article.)  Second, you do not need to reboot the SharePoint servers in the farm for this procedure.  Besides, wouldn’t rebooting the farm thus restart the Search Service thus making Step 1 unnecessary?  Think about it.   And third, there is absolutely no need to create a Test site collection and a document library to see if the PDF icons are working.  It is correct on the fourth item to perform a Full crawl.  That’s one out of four though.  It’s time to blow past this KB article.  <sarcasm>Thanks Microsoft.</sarcasm>

SharePoint Sharon
Going back to my Google results, I found this article which makes several mistakes as well but one stands apart.  First, it gives the correct url to the Adobe website for downloading the icon but then states to download the 17 x 17 icon.  NO!  The good news is that the icon there is 16 x 16, which are the correct dimensions.   Fatal flaw: I copied the code there for the <Mapping> section of the docIcon.xml file but it contains the wrong characters.  (I’ll show you in the double quotes section below.)  It does correctly remind to restart IIS and to perform a Full Crawl but doesn’t mention restarting the Search Service at all.  Simply put, this article doesn’t cut it either.

Zubair to the Rescue
Zubair Alexander offers a very thorough article on this issue.  He offers several registry changes to make/confirm, he explains how to restart the Search service, and he offers several helpful troubleshooting steps.  One minor flaw: he doesn’t provide the link (like the other two articles cited) for getting the 16 x 16 Adobe icon.  He just says in Step 8 to copy it but doesn’t provide for how to get it.  [It’s here, by the way.]  Most importantly, it was his Troubleshooting Step 9 (with the bright red Gotcha! ) that ultimately resolved my problem.

Double-Quotes Pain
I had copied the <Mapping> code directly from SharePoint Sharon’s site.  Upon very close inspection, sure enough, it contained the wrong double-quotes.  Painful.  See below and look very closely.  The double quotes in the section for pdf are different than the quotes in the other sections.

docIcon.xml with INCORRECT double quotes

docIcon.xml with INCORRECT double quotes

So I deleted the double quotes you see above and replaced them with “correct” double quotes and voila – my SharePoint 2010 farm now correctly shows the PDF icon next to PDF documents.  Success!

docIcon.xml with the CORRECT double quotes

docIcon.xml with the CORRECT double quotes

Conclusion
The process, therefore, for setting up the Adobe iFilter for 64-bit on SharePoint 2010 is thus:

  1.  Install PDF iFilter 9.0 (64 bit) from http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025
  2. Download the 16 x 16 PDF icon from the Adobe web site http://www.adobe.com/misc/linking.html  or just right-click and Save this one:  pdf_icon   Then, copy it to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES\
  3. Add the following entry in docIcon.xml file, which can be found at: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML   [You may need to change the name of the .gif in the code below to match your exact file name.]
    <Mapping Key=”pdf” Value=”pdf_icon.gif” />
  4. Add pdf file type to Search.  Go into the Search Service Application, File Types page (found on the left-hand navigation) and add the pdf file type.
  5. Add pdf file type to the registry.  Navigate to the following location in regedit: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\ContentIndexCommon\Filters\Extension
  6. Right-click > Click New > Key to create a new key for .pdf
  7. Add the following GUID for the default value:
    {E8978DA6-047F-4E3D-9C78-CDBE46041603}
  8. Open a command prompt as Administrator.  We need to restart SharePoint search services.   Type the following lines, one at a time:
    net stop osearch14
    net start osearch14
  9. We now need to restart IIS.  In the command prompt window, simply type:
    iisreset
  10. Now, open Central Administration in SharePoint 2010, go to the Search Service Application, and perform a Full Crawl.

The Adobe PDF icon should now appear next to all PDFs.  If they do not, consider going back to Zubair’s site for his troubleshooting steps.  But first of all, make sure you have the correct double quotes in docIcon.xml.  That caused me a lot of grief and I want to make sure no one else struggles with it.

Disable and Hide Social Tags

SharePoint 2010 social tags

I have a client that wanted the social media functionalities to completely disappear from their SharePoint environment.  I found a website that demonstrates how to do this, complete with screenshots, and some very good explanations.  I have nothing to add to their fine work.  Just follow their directions.

Note: their site takes a while to load (at least for me on the several times I’ve visited) so give it some time.

SharePoint Indexing Performance Tuning Tips

David M. Sterling has written an excellent blog entry on tuning indexing performance.  I feel it’s very important and needs to be shared.  [Snippet below.]

There are many factors involved in the SharePoint crawling process that can impact indexing performance. There are also some steps you can take to improve that. Here are the common causes and their resolution:

1.  Indexing Performace is set at reduced
2.  Number of connections
3.  Crawled systems are slow or hosted on remote networks
4. Overlapping crawls
… and seven more.

Click here to to read the full article.

Network Topology Add-In for Visio 2010

Spence Harbar mentioned this topic on his blog briefly but I didn’t fully understand what he was talking about.  I thought it was simply an add-in to Visio 2010 for SharePoint-specific shapes to incorporate into my next SharePoint network topology Visio.  I could always use more cute and helpful shapes in my Shapes menu.   I was wrong.

This add-in enables SharePoint administrators to create and publish dynamically refreshing Visio Services diagrams to monitor the performance of their infrastructure.

Use this add-in to simplify the maintenance and troubleshooting of your Microsoft SharePoint farm infrastructure.  This add-in delivers a near real-time, online view of the status of your SharePoint farm, its servers, and their services using Microsoft Visio 2010 and Visio Services in Microsoft SharePoint Server 2010.

Click here to download the add-in and the corresponding timer job that updates the content.

This is a value-add for us SharePoint administrators to offer both our business leaders and our IT bosses.

Another hidden feature: the user list

After finding the hidden “set up groups” page that was openly available in MOSS 2007, I was reminded of another feature from the past that’s now hidden, but available, in SharePoint 2010: the user list.   In a site collection or site, when you go to look at the Users, you are only given the various user groups to choose from but not a comprehensive list of ALL site users and their respective rights.  But it’s there.  Simply append this url:

…/_catalogs/users/simple.aspx

Note: This list is only visible to and accessible by administrators.

[The above information was gleaned from Tobias Zimmergren’s site.]

Setting up default groups in SharePoint 2010

In MOSS, you could use the “Set up groups” option within a site to create and assign the default Member, Owner, and Visitor groups.

In 2010, the “Set up groups” link does not appear.

The  “Set up Groups for this Site” page is hidden for SharePoint 2010.  You can still get to this page by url:

…/_layouts/permsetup.aspx

[The above was excerpted from this technet article.]

Set up RMS on client side

Once AD RMS is set up on the server, you need to set it up for the end users to actually use the AD RMS functionality.  This is a 2-step process:

1. Install/validate RMS client on client machines
2. Use RMS within Office apps (Word, Excel, PowerPoint, and Outlook)

RMS client on client machines

The AD RMS client comes installed out-of-the-box on Microsoft end-user operating systems Vista, Windows 7, and Windows 8 as well as the server operating systems of Windows Server 2008 and Server 2008 R2.  However, earlier versions of Windows (i.e. Windows XP or Windows Server 2003) require the manual installation of the RMS client.  [Note: the client is actually just one file: msdrm.dll (Microsoft Digital Rights Management -dot – dynamic link library) which can be found in the %windir%/system32 directory.]

If you need to install the AD RMS client manually, first determine the operating system platform, the service pack installed (if any), and the architecture (32-bit or 64-bit) of the machine where you want the client installed, then visit the Microsoft AD RMS client page to download the correct AD RMS client version.

RMS in Office apps on client machines

Once the proper RMS client is installed, you need to set up Office 2010 to use the RMS functionality.  Microsoft has posted a helfpul article called Information Rights Management in Office 2010 that covers the process pretty well.  Essentially, once RMS is set up, users simply need to click File, Info, and then select the restriction settings they want.  Piece of cake.  See below for Word 2010 Professional.

How to use IRM in Office 2010

Additionally, if you would like to add a ribbon command for Protecting documents in Word 2010, it’s a fairly elaborate process, honestly.  Check it out.  Some of your users will prefer this method (the ribbon command) while others will prefer the “standard” way of clicking Info from the File menu.  Either way, you’ll have covered both of your bases.

These instructions work for both Office 2010 and Office 2007 Professional versions, however, RMS will also work with Office 2003 Professional.  For Office 2003 Professional the process is simply to click the File menu, and select Permissions from the dropdown.  Then, simply follow the prompts.  You will be prompted for which users and/or groups are to have access followed by a screen where you select the individual permissions to be restricted.  See below.  Piece of cake.

Protecting Office 2003 Professional with AD RMS

 

Restrict Office 2003 with RMS

 

Final

After you have set up the client’s machines for the RMS client and you’ve set up Office 2010 to use RMS functionality, you’ll want to train the users on how to follow the process of protecting their documents, e-mails, spreadsheets, and powerpoints.  At that point, you will have completed the AD RMS mission.

Happy

Integrating AD RMS with SharePoint 2010

After I finally got AD RMS up and running, the next task was then to integrate it with SharePoint 2010.  This seemed simple:

1.  Go into Central Admin in SharePoint 2010 on a Web Front End (WFE) Server,

2.  Click Security,

3. In the section Information Policy, click Configure information rights management,

Configure IRM in SharePoint 2010

4. Choose one of the three options:

  • Do not use IRM on this server
  • Use the default RMS server specified in Active Directory
  • Use this RMS server (it then allows you to type in the url for your AD RMS server)

My initial choice was the third option.

Configure IRM for SharePoint 2010

I typed in my AD RMS url and then clicked the OK button.  It failed.  I double-checked the url and it was right.  What could be the problem??  After careful reading of Google’s findings on the subject, I chose the second option (“use the default RMS server specified in Active Directory”)… and it failed again.  After going back to Google again, I found this article about integrating SharePoint 2007 with IRM which gives the important steps of Permissions – you must enable the SharePoint 2010 WFEs to access the AD RMS server certificate.  Got it.  Here are the steps from the above article by David Lim which are as relevant to SharePoint 2010 as they were to SharePoint 2007.

  • Log on to the AD RMS server as a local administrator
  • Click Start, and then click Computer
  • Navigate to c:\Inetpub\wwwroot\_wmcs\Certification
  • Right-click ServerCertification.asmx, click Properties, and then click the Security tab
  • Click Advanced, click Edit, select the Include inheritable permissions from this object’s parent check box, and then click OK two times
  • Click Edit
  • Click Add
  • Click Object Types, select the Computers check box, and then click OK
  • Type the name of the SharePoint web front-end server, and then click OK twice.
  • Repeat the above three steps for other web front-end servers
  • Click OK to close the ServerCertification.asmx Properties sheet. By default the Read & Execute and the Read permissions are configured
  • Reset IIS

Now you can go back into Central Admin on a WFE, Security section, Configure information rights management, and select the 2nd option: Use the default RMS server specified in Active Directory.

Configure IRM for SharePoint 2010

It should work this time.  For me it did.

Final Step:  After you take these above steps, site and document library administrators are able to enable IRM on any document library to which they have the appropriate permissions.

How to re-install AD RMS

I inherited a partial installation of AD RMS.  The previous IT guy had simply installed the AD RMS and IIS roles on the box and assigned a url for the cluster.  Unfortunately, it was not the correct url so I needed to “remove the cluster” which sounded like a total mess.  Since AD RMS had not been in production yet (and thus no certificates had been issued and no documents protected) it made perfect sense to just delete everything and start from scratch.  I looked high and low on the Internet for the information I am about to provide.  I wasn’t successful in finding much help on the matter so I’m sharing my steps with you here.

Just so you know, when you install the AD RMS server role on Windows Server 2008 R2 (which runs the AD RMS installation wizard), it reaches out and creates several things in your enterprise:

1.  It creates a Service Connection Point (SCP) in Active Directory

2.  It creates two databases in SQL Server (configuration and logging)

3.  It integrates with IIS on the server and/or installs the IIS server role if it wasn’t installed already

For any reason, if the installation needs to be performed again, you need to clean up all of these touch points. 

First, remove the AD RMS and the IIS server roles.  You also need to clean up the databases that are created in SQL Server (configuration and logging) by taking them offline and then deleting them in SQL Server Management Studio.  Then, remove the SCP created by AD RMS in Active Directory (see the posting just previous to this one).

Reboot the machine.

When it comes back up, simply Add the following roles: AD Rights Management Service and IIS and follow the wizard.

AD RMS installation error

Error Msg: Attempt to configure Active Directory Rights Management Server failed. The AD RMS installation could not determine the certificate hierarchy. If the AD RMS service connection point (SCP) you need to use is registered in Active Directory but is not valid, revise it to make it valid, or create a new SCP, and install AD RMS again…

If you are receiving this error, it’s probably because of a previous installation (or failed installation) of AD RMS.  When AD RMS is installed, the wizard reaches out to your Active Directory controller and creates a Service Connection Point (SCP) there.  Later attempts to install will fail because they cannot overwrite the existing SCP.  You’ll simply need to delete it.  A poster named Sally.Mark contributed the below which worked for us:

Just wanted you to know that I was able to solve this problem. For anyone else who may someday come across this problem. What I did to solve it was, on AD computer, I opened the run command and then ran  ADSIedit.msc.   The ADSI edit MMC window popped up and I browsed down to Configuration and then expanded the first node, then expanded Services and then I deleted the SCP that said  CN=RightsManagementServices.  I deleted the whole thing and subfolders and then I went back and reinstalled AD RMS on my server. This time it worked perfectly.

Source: http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/4feaa2d2-afb2-4d7c-8414-fdf44a13d0bb/

 

 

 

Page 1 of 2

Powered by WordPress & Theme by Anders Norén