Solution: Survey app missing in SharePoint

Once in a while, you’ll want to use the survey web part for one reason or another. There are awesome tools like Yammer polls, Microsoft Forms, etc. but sometimes the only tool suitable for a specific use case is still the out-of-the-box SharePoint survey app.

If you search for it when adding a new app and get “We didn’t find a match here, but check out…” don’t fret. It’s tied to a site feature that apparently isn’t activate on your site. This applies to both on-prem and online/O365 environments.

To get the survey app as an option on your site, you’ll need to be a site owner who can activate the Team Collaboration Lists site feature (settings wheel > Site settings > Manage site features).

Once you activate it, your site will now be able to add these apps:

  • Document library
  • Custom list
  • Tasks
  • Picture library
  • Issue tracking
  • Survey
  • Discussion board
  • …and much more

Here’s a quick GIF demonstrating activation of the required feature:

Click to enlarge

Solution: PerformancePoint Dashboard Designer “Cannot download the application…missing required files”

I’m late to the game trying out PerformancePoint Services, a has-been dashboard and KPI service for SharePoint server that still exists in production for many on-prem farms running 2013/2016/2019. I’d venture to guess most would prefer the more modern and flexible Power BI (either Report Server or the online service via O365) to PerformancePoint Services but, alas, change takes time.

So, anyway, when I tried to open Dashboard Designer on a PerformancePoint list for the first time, I received the following error.

Cannot Start Application

Cannot download the application. The application is missing required files. Contact application vendor for assistance.

I had tried to open Dashboard Designer using Chrome and CrEdge (Chromium Edge) without luck. The downloaded designer.application file just gave me the issue seen above.

In the end I found, as with most dated tools and functions in the SharePoint world, some things only work in Internet Explorer (IE). This particular button, however, worked in both IE and Edge!

So copy your list’s URL, move over to Edge or IE, and try to launch it again from there. This worked well for me. Good luck!

Solution: SharePoint document library links/shortcuts to other documents go to a blank .aspx page

Today I ran across an issue where someone had created links within a classic document library that redirected users to documents stored in a different library. This is easy to do, but for some reason those links were now leading users to blank .aspx pages instead of the intended document.

Note that users weren’t taken to an “invalid” or “can’t be found” error page, but a completely blank page with a URL ending in .aspx. If you’re being redirected to anything other than a blank page the following solution probably won’t apply to you.

I figured out that, somehow, the library in question no longer had the “Link to a document” content type included. You normally can’t delete a content type that is in use, but with the right permissions and perhaps a migration tool or script, anything is possible. Without the content type on the library, the links that once worked under that content type now could not.

Important: The links are not necessarily broken – do not delete them. Once the content type is added again, they should work unless the original URLs have actually changed.

To re-add the link/shortcut content type to the library, follow these directions (same as if you were adding it for the first time):

1. Go to Library > Library Settings

Click to enlarge


2. Choose Advanced settings

3. Set Allow management of content types to Yes.

4. Click OK to save changes.

5. Under Content Types choose Add from existing site content types

6. Select Link to a Document and Add >.

Click to enlarge

7. Click OK.

Now check your links, and they should work!

Possible solution: “Sorry, something went wrong. The file is locked for exclusive use by…”

I recently ran into the following error when someone tried to edit a shared Excel file from OneDrive (we’re running SharePoint Server 2016).

“Sorry, something went wrong. The file {address} is locked for exclusive use by {name}.”

Troubleshooting

The user in question, who had it “locked for use,” had the file open in Excel (client, not online) when their computer unexpectedly shut down. This locked others from editing the file. The first few things you should try (stop if one of the steps fixes the issue):

  1. If the user still has it open, have them save and close out. If it really was checked out, check it in with their account.
  2. Make sure the user who has it locked has closed all office apps (Task Manager is a good way to see if anything is running in the background)
  3. Have that user restart their machine used to edit the file in the first place for good measure
  4. You can try waiting a day to see if the lock lifts overnight or after a few hours.

What worked for me

Now that you’ve confirmed the individual who had the file locked can’t really have it open or locked, you can try the solution that worked for me. At the bottom of this post, I’ve listed more ideas I tried that might work for you.

  1. Open the user’s OneDrive in SharePoint Designer (the address may resemble https://mysites.COMPANY.org/personal/USERNAME)
  2. Navigate via “All Files” via the left nav to the file in question. It probably has a padlock icon on it.
  3. Right-click the file name and select “Edit File in Advanced Mode”
  4. Save the file in SharePoint Designer.

I can’t explain why this worked, I know it’s completely illogical, but it worked.

Here’s a thread on SharePoint’s user voice regarding this error.

What might work for you

Here are some things you can try that were not successful for me (but might work for you):

  • I tried copying the file and deleting the original but could not delete it (in browser, PowerShell, or SharePoint Designer)
  • I tried this PowerShell solution and it told me who had it “checked out,” and when it would expire which was helpful, but it was unable to release the lock
    • P.S. I waited for the expiration, but it renewed itself
  • I tried checking it in via browser and SharePoint Designer (because it appeared checked out) but got a message saying it wasn’t
    Click to enlarge
  • From the owner’s OneDrive (where the file was stored/created) I disabled check-out requirement via Site Contents –> Library Settings –> Versioning settings
    Click to enlarge

Solution: “The embed code is invalid because the source of the embed content is not allowed” error when embedding Microsoft Stream video in SharePoint

A user recently ran into the following error when attempting to embed a Microsoft Stream video on a SharePoint 2016 site:

“The embed code is invalid because the source of the embed content is not allowed.”

To resolve this, you must be a site collection administrator.

Go to site settings and select “HTML Field Security” under “Site Collection Administration.”

By default, SharePoint allows embeds from YouTube, Bing, Vimeo, and Microsoft but we need to add web.microsoftstream.com to the list.

Now try to embed your video again, and it will work.

SharePoint search results showing wrong title

I recently ran into the issue of a document appearing in search results that didn’t use the name field OR the title field. I was perplexed by this until checking the search schema for the “Title” field. In an attempt to be helpful, there’s a property called MetadataExtractorTitle that was given higher preference than the actual title field. To fix this, I simply had to bump it down the list a bit.

Scenario

The document in question is a SharePoint Governance meeting agenda named SP Governance – 2017-11-17.

It appeared correctly in its library, which is to be expected:

And a look at its properties revealed there was no Title value, meaning it would default to the document name.

However, when searching for “SP” I found the document listed as “Agenda.” This was used because the MetadataExtractorProperty found “Agenda” within the document as a potential title (as the first line of the document).

Solution

Note: You must be at least a site collection administrator.

Go to Site Settings at the top level of the site collection for the document library.

Choose “Search Schema” under Site Collection Administration (not just “Schema” under search – that’s only site level)

Search for title and edit the property

Move “MetadataExtractorTitle” down until it’s beneath ows_Title. Click OK when finished.

Click to enlarge

Checking your work

After fixing the schema, go back to the document library and re-index it to check. (Library Settings –> Advanced Settings –> Reindex Document Library)

This will have the library re-crawled during the next incremental crawl (interval depends on administrator settings). Alternatively, you could trigger it immediately or run a full crawl.

Once the crawl has run, try your search again. Your items should now have a correct title when appearing in search results.

Run Google Chrome as a different user to test

In an on-prem environment, it’s convenient to be able to run Chrome as a test user with general permissions instead of my admin permissions. This possibility makes it so I don’t need to remote to another machine or log out and in with another account just for a simple check.

Using Internet Explorer? Here’s how to do the same with that.

If you have a shortcut to Chrome on your desktop (not your task bar), skip ahead to step two.

1. Search “Chrome” from the start menu, right click and select “Open File Location”

2. Hold “Shift” on your keyboard and right-click the Internet Explorer icon. Select “run as different user”

3. Enter the credentials for the second user (your screen/prompt may look different) and click OK/Login. In some cases, you may be prompted to enter these more than once.

Chrome will now run as if the other user is logged in.

You can also use the “Check permissions” feature in SharePoint to see which groups a user belongs to for a site or resource, and which abilities/privileges they have.

Run Internet Explorer (IE) as a different user to test

It’s often helpful in our on-prem environment to be able to run IE as a test user with general permissions instead of my admin permissions. This possibility makes it so I don’t need to remote to another machine or log out and in with another account just for a simple check.

Using Google Chrome? Here’s how to do the same with that.

If you have a shortcut to IE on your desktop (not your task bar), skip ahead to step two.

  1. Search “IE” from the start menu, right click and select “Open File Location”

2. Hold “Shift” on your keyboard and right-click the Internet Explorer icon. Select “run as different user”

3. Enter the credentials for the second user (your screen/prompt may look different) and click OK/Login. In some cases, you may be prompted to enter these more than once.

IE will now run as if the other user is logged in.

You can also use the “Check permissions” feature in SharePoint to see which groups a user belongs to for a site or resource, and which abilities/privileges they have.

Check permissions for an individual or group in SharePoint

If you want to see which groups a user belongs to, or how an individual is granted (or restricted) access to a particular site or resource, use the “Check permissions” button in Site Settings –> Site Permissions (or any advanced permissions page).

SharePoint 2016 example of checking permissions
SharePoint Online example of checking permissions (see specific allowances)

“The selected file doesn’t contain template elements” error in Microsoft Flow

I recently tried to use the “Populate a Microsoft Word template” step in Microsoft Flow (currently in preview) to insert text into content controls, but ran into the error above.

The selected file doesn’t contain template elements.

The issue was that my content controls in the template were of rich text format and date. This preview step currently only supports plain text, combo box, and dropdown content controls.

Plain text, combo box, and drop down are the only supported content controls as of the publishing of this post.

So for all of your text fields, make sure you use the correct (plain text) control:

Once I replaced my rich text content controls with plain text, the content controls showed up in Flow as options for populating:

To keep this organized, I recommend giving each content control a title (in its properties) so you can easily identify each field when in Flow (select content control, then “Properties” from developer tab).

Remember, you’ll only see supported content type fields in Flow. Even if you have a date content control, you won’t be able to populate it using Flow.