I was seeing this error when trying to check in a document after completing the required metadata in Word (via DIP). I found this post claiming the issue was due to the content type of the document containing a managed metadata field. Although that sounded far fetched, I ended up following the workaround instructions and adding a new managed metadata field directly to my library (Test with one term- test). I then deleted the field, and suddenly I could check my document in! Weird.
I also saw this error when I used the Specify default content feature of Document Sets – automatically creating a number of documents from templates, within a new set. I could not complete the metadata and check those documents in. When I turned off check in/out on the library, I could no longer get to the DIP properties in Word. The only way to set the document metadata was to use the edit form in SharePoint. I never got around this issue. If anyone has an ideas, please let me know.
There are a few circumstances under which you may come across this error :
We’re having a problem opening this location in File Explorer. Add this web site to your Trusted Sites list and try again
Here I will provide a solution for one of those – You are trying to open a SharePoint document library in explorer view while on the SharePoint server.
There is an excellent post here that provides a detailed description of the problem and solution, but to summarise, you need to install the Desktop Experience feature under User Interfaces and Infrastructure on the server.
Recently I set up Managed Navigation – navigation based on a Managed Metadata term set – in my Office 365 developer site. I came across a few problems so I’ll provide steps here that should help you circumnavigate those.
Using Publishing Navigation Settings
- Create new site collection or ensure you are dealing with a site collection that you have provisioned. This will overcome the strange issue reported here: http://community.office365.com/en-us/f/148/t/282769.aspx – “Sorry you don’t have access… (to update Navigation Settings.)”
- The publishing feature should be turned on so you can set global navigation via the Navigation settings, so either use the appropriate site template type or enable the publishing feature in your site collection.
- Under site administration settings, open the Term Store Management Tool and :
- Locate the Navigation term set under the site collection group
- Create new terms for each navigation link
- In the term’s Navigation tab select Simple Link or Header and then add the link address
- Go to Site Settings in site collection and click Navigation
- Choose Managed Navigation: The navigation items will be represented using a Managed Metadata term set and ensure your new term set is selected before saving the settings.
- Now you should see your managed navigation links displayed that the top of the page 🙂
Using Custom JS in master page to Create a Navigation Bar
Follow this blog post to generate reusable nav bar and embed into master page. In this scenario you don’t need the publishing feature and you create your own Navigation term set from scratch. I haven’t tried it yet but it looks pretty cool!
If you attempt to execute a PowerShell script on the SharePoint server and see : “Script cannot loaded. The file is not digitally signed. The script will not be executed on the system” or “… the execution of the script is disabled on the system…”
It means you either need to :
Sign the script OR
Set the PowerShell execution policy to allow you to execute unsigned scripts, e.g.
powershell.exe -executionpolicy bypass -file C:\script.ps1
If you want to make changes to a PowerShell script but you are always prompted to save as a new version, the file may be locked. Right click the script file and select Properties. Ensure the Read-Only checkbox is unchecked. If there is a Unblock button next to the Read Only property, click Unblock.
When using Visual Studio to package and deploy an event receiver to be associated with SharePoint list, you may come across this error:
Error occurred in deployment step ‘Activate Features’: <nativehr>0x80070002</nativehr>
This probably means that your List URL is incorrect in the receiver elements file. The format needs to be :
You may also see a Invalid Function error when you try to activate the feature manually in your site. Double check the URL of your list and ensure the list either exists or is being created at this URL prior to the receiver activation.
In SharePoint 2010 and 2013, it is a bit tricky to find the list of features to activate or deactivate so I thought I’d leave some breadcrumbs here for folks to follow:
In Central Admin click Application Management > Manage Web Application then click the relevant Web Application name to highlight it. Finally, in the ribbon, click Manage features.
In Central Admin click Application Management > Manage Web application features
If you can’t find the feature you are looking for in these lists, you have either:
Not installed the feature
Installed a feature scoped at a different level (i.e. not web application scope).
Thanks Stefan for your awesome post here (I’m a bit slow on the uptake but better late than never). I have used the ?IncludeVersions=TRUE to show all updates to InfoPath forms in a forms library. This seems to give users some sense of security (they don’t really believe versions are being tracked until they can SEE them).
You can also add multiple lists to one list view page and apply the filter. It will show the versions for all lists on the page. Good for a “versions” page rather then expecting users to find use the Version History menu option. Check out Stefan’s post to see how you can also use other filters with the versions query string parameter. Very very cool and super easy.