How to configure the Integration when using a load balanced HTTPS URL

How to configure the Integration when using a load balanced HTTPS URL

Follow the sections in HPE Content Manager Governance and Compliance SharePoint App Installation Guide that describe how to configure the Integration for HTTPS.

Then the following steps need to be performed on each Content Manager Workgroup Server (WGS) where the SharePoint Integration component has been installed from the HPE Content Manager_SharePoint2013AppIntegration_x64.msi:

  1. Ensure the HPE Content Manager SharePoint Configuration tool is not running on any of the WGS

  2. Open IIS Manager and add a HTTP binding to the HPE Content Manager SharePoint Server site

  3. Open the web.config file under the Integration install folder and modify webHttpBinding section to be as follows:


        <binding name="wbBind" maxBufferSize="2147483647" maxReceivedMessageSize="2147483647">

            <security mode="TransportCredentialOnly">

                <transport clientCredentialType="Windows"/>




  4. Perform an IIS reset on the WGS

On one of the Integration WGS open the HPE Content Manager SharePoint Configuration tool as administrator and complete the configuration steps making sure to add the machine name and the HTTP URL of each WGS in the farm on the Workgroup Servers tab.

Clarifying the dependency on the client-side object model (CSOM)

HPE Content Manager 8.30 Patch 1 Build 9088 SharePoint Integration

With the release of Content Manager 8.30 Patch 1 it was announced that the SharePoint integration would now require CSOM version 16 to be installed as a prerequisite.

Subsequent to this announcement a number of our customers have expressed concerns around the impact this would have on their other SharePoint applications that relied on CSOM version 15. This is particularly the case in SharePoint 2013 environments. 

In some scenarios, customers would have to install both CSOM 15 and 16 if they we’re running other applications on the same SharePoint server.

While Microsoft does not explicitly say this is an unsupported environment they recommend against running different versions of CSOM on the same server.

In an effort to clarify this situation and ensure consistency across all of our versions the HPE Engineering team has therefore decided to revert to CSOM 15 with the release of HPE Content Manager 8.3 Patch 3 in December, 2016. This will bring the HPE Content Manager 8.3x SharePoint Integration in line with our other releases which all depend on CSOM version 15.

Future versions of HPE Content Manager will be examining the new features of CSOM version 16 and will most likely be re-introduced when Microsoft stops supporting SharePoint 2013.

Customers who are currently on HPE Content Manager 8.3 Patch 1 or 2 and believe they have CSOM related issues should contact the HPE Support team via for further assistance.

Configuring SharePoint 2016 for Apps

Warning, this blog contains a PowerShell script. These scripts can lead to irreversible issues with your environment, so be sure to test thoroughly in your various environments before running any script in your production environment.

So, since my last blog I've proven that even a bloke like me can get an environment stood up and configured from "go to whoa"!

But setting up SharePoint 2016 didn't go all that well, the initial install was smooth and without issue. However, when it came to configuring the App URL's I was met with an error message that I simply couldn't work out!

No matter what I done to get the appURLs configured, I was met with this error message!

No matter what I done to get the appURLs configured, I was met with this error message!

All the necessary services were running on the server, SQL accounts setup correctly... the lot! Ugh! I was at the point where I wanted to simply roll back the snapshot and try again... until I done some reading. A young man by the name of Soreddy Manjunath found the solution and even provided a bit of code to help get the Service applications for AppManagement and Subscription Service Settings up and running.

The services you need running are obviously the App Management Service and the Microsoft SharePoint Foundation Subscription Settings Service. If they are running and you're still finding no joy, then try an "IISRESET". 

Failing that, the solution I used from Soreddy sorted me right out. Running his supplied PowerShell script (in an elevated ISE instance on the SP server) should resolve your issue. Just remember to replace the "CORP\Svc.AppsAccount" line with your farm administrator account and you're golden!

Hope it helps!

Installation Woes

If you're like me and love to have everything organised perfectly before setting off on adventures (like preparing environments or going fishing), then you may have run into this issue when attempting to install your shiny new SharePoint 2013 instance.

Imagine if you will, a fresh new environment with Windows Server 2012 R2 and SQL Server 2014 and you, a fresh faced and enthusiastic employee who has been tasked with installing a brand new copy of SharePoint 2013 on it.

So you do your best to get everything sorted, your MSI's are all lined up and ready to go. You have gone ahead and made sure that all the Windows Updates are installed so you're on the front foot and not leaving any of the software open to vulnerabilities. You've also installed all of the SharePoint pre-requisites and followed all of the steps in your HPE Content Manager Installation Guide. You're ready to go, so you fire up Setup.exe from your SharePoint cd and then this...

After running Windows Update on my new environment and installing all the pre-requisites... I was greeted with this message.

After running Windows Update on my new environment and installing all the pre-requisites... I was greeted with this message.

AAAAARGH!!!! Ok, calm down. Breathe in, breathe out.

I'll just go check my Server Manager to see if its installed...

.Net 4.5... you ARE installed!

.Net 4.5... you ARE installed!

Ahhhhh, ok - so it IS installed. What the heck SharePoint! It's at this stage that I should tell you, do not, I repeat - DO NOT - uninstall 4.5 and try to reinstall. This will result in your servers GUI components being uninstalled as a part of the process and you'll be left with no server UI upon restart.

So who is to blame? Well, you've gone and gotten ahead of yourself. By installing the Windows Updates you have inadvertently installed Microsoft .Net 4.6 (or even 4.6.1) which has caused the SharePoint 2013 pre-requisite checker to fail.

Removing an update will result in the 4.6.x components to be removed, thus allowing you to proceed.

Got 4.6.1? Get rid of KB3102467 (on Windows 2012 R2)

Got 4.6.1? Get rid of KB3102467 (on Windows 2012 R2)

A big thanks to the community over at for the fix here.
You can check out the full thread (and KB references for other OS's) here:

New Library Experience in O365

Currently there is a problem with the way the new list experience mode renders the Ribbon items for the HPE Content Manager SharePoint Governance and Compliance App. Some are repeated and do not correctly launch the associated dialog.

In addition if certain SharePoint site columns created by the Configuration Tool are added to a list with either the ‘Default experience set by my administrator’ or ‘New experience’ option selected, there will be an error when trying to browse the list.

The workaround is to make sure the list is set to use the ‘Classic experience’ option.

User Profile Sync status... where's that?

Are you having trouble locating the User Profile Synchronization status?

 Head over to your Central Admin page and select "Manage services on server" from the System Settings section

Find the User Profile Synchronization Service, hit "Start". You should be taken to a new page where you can confirm your farm account password. From there, hit OK and you're away!

If you're still unable to get the service started, check out this handy web site for a possible solution.

Having an "Identity Crisis"?

In HPE Content Manager 9.0 we have altered the application configuration tool's Permissions tab to omit some identity fields.

Alas, it hasn't been removed... its merely been "relocated" (get it?)

You can now find the fields on the Configuration Access Control page, which is available from the App Start page, under the Security section.

More information about CAC can be found in your User Guide on page 258.

Troubleshooting “App Configuration Settings are Invalid” error

1. Verifying your App Id

  • Browse to “<<Your site Url>>/ _layouts/15/appinv.aspx
  • Type in the AppId you specified in your configuration tool and perform a look up. Confirm the details are correct. If no information is returned then this means the app id is invalid. Fix the AppId in the configuration tool and reconfigure, otherwise proceed to the next stepVerifying your Issuer Id.
  • Execute the command on the SharePoint Management Shell


  • Note down the value for the RegisteredIssuerName
  • Here is how it looks like:  RegisteredIssuerName          : 11111111-1111-1111-1111-111111111111@6b98f2ce-acc3-4238-a027-d88f7e139207.
  • Your IssuerId will be the Guid before “@”. If this Id doesn’t match the one you entered in the Configuration tool, fix this and reconfigure, otherwise proceed to the next step.Verifying your certificate

2. Verifying your certificate

  • Check the permissions to the certificate location (on the SharePoint Server as well as on the HPRM Server)
  • Ensure that the password you specified is correct
  • Check in the ULS log for any authentication errors. If you don’t find any useful information, go to Central Administration à Monitoring àConfigure diagnostic logging.  Expand the SharePoint Foundation category and select the following items:  App Auth, Application Authentication, Authentication Authorization and Claims Authentication. Set the logging and trace level to Verbose for these and save your changes and resave the default site collection url. Look for any errors in the ULS again. If you find a certificate expiration error follow these steps to reregister the token issuer
  • Execute the command on a SharePoint Management Shell and note down the Id of the trusted security token issuer


  • Remove the token issuer by executing this command Remove-SPTrustedSecurityTokenIssuer   -Id  <<Your Id here>>
  • Remove the trusted root authority by executing Remove-SPTrustedRootAuthority -Id HPRecordsManagerTrust
  • Follow the installation guide for setting up High Trust, provide details about your new certificate when prompted.
  • Reregister a new App Id
  • Use this new App Id in the App Configuration settings and regenerate the app
  • Remove the existing app from all the site collections and from your app catalog.
  • Upload this new app to the app catalog and add it to your default site collection.
  • Close and reopen the Configuration tool
  • Specify the default site collection url and save

8.3 patch 1 requires version 16 of the SharePoint client components

8.3 patch 1 for the SharePoint governance and compliance app requires an update to the Microsoft Client Components.  Version 16 is the minimum required version (this was omitted from the product documentation).

If you do not upgrade the client components, you will see issues manifesting in the configuration tool, web services and application pages with the following error:

Could not load file or assembly 'Microsoft.SharePoint.Client, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.

The resolution to this issue is to install version 16 of the client components.  This can be downloaded from here:

Configuration pages fail after a recent Windows Update

Windows update KB3134814 ( makes an update to Internet Explorer that causes some controls on SharePoint configuration pages to fail. This will effect the SharePoint Governance and Compliance App versions 8.1.X, 8.2.X and 8.3.0

For example, on the Default Integration Settings page, if you try to select a record type, no value is entered in the control regardless of what value you select. 


This problem was first reported on the column mapping page.

For users of 8.3, the imminent 8.3 patch 1 resolves the issue.  For users of earlier versions, we plan to release a hotfix in the coming weeks.  In the meantime, for users who need to perform configuration, do not download this update (or remove it if you have it already).