Error occurred in deployment step ‘Recycle IIS Application Pool’: Invalid namespace

Issue:

When I try to deploy a project built in Visual Studio 2017 for SharePoint 2019 on Windows Server 2019 Standard Edition. I got the same error as above.

Resolution:

Apparently, VS 2017 uses WMI to control IIS during a redeploy. Without the features enabled, I got the same “Invalid namespace” error.

The solution was to: open the Turn Windows Features on or off menu in the Control Panel (under Programs), and enable WMI compatibility. The path to the feature is:

Add a Web part section is not showing in Internet Explorer

Issue:

Add a Web part section is not showing in Internet Explorer for the Intranet sites.

Resolution :

To overcome this issue for the sharepoint intranet sites we need to set this site as to be open in compatibility mode. To do that follow the steps as given below.

  1. Go to Tool > Compatibility view settings
  2. Add the url of your site in the text box and then click Add.
  3. Check the box of Display intranet sites in compatibility mode
  4. Click close.
Compatibility View Settings

Let me know in comments if this helps or not.

Happy SharePointing!!!

TrickyCoder – Best practices for SharePoint a Document Management System – part 2

This post is a in the continuation with the previous post. If you have not read that you can read it at herehttps://trickycoder.com/trickycoder-best-practices-for-sharepoint-a-document-management-system-part-1/

CHECK OUT FEATURE

If the organisation requires the ability to co-author on Microsoft Office documents in the library, it is recommended not to turn on the ‘Require Check Out’ setting.

The function of this feature is to prevent alteration of a document by multiple individuals. This is a good feature to have when there is more than one person working on a specific project or to prevent another from making changes to completed work without consulting you about it first.

Key benefits:

  • Minimising data conflicts by turning on the require check out feature
  • Allowing for co-authoring of Microsoft Office documents when the require check out feature is turned off
  • Maintain data integrity.

DOCUMENT LIBRARY PERMISSIONS

In document libraries, the permissions recommended to be set up is to adhere to using SharePoint groups rather than granting users access directly to the library. This minimizes admin overhead from a permissions management perspective.

With this security model, users can be added/removed from the SharePoint group(s), which subsequently controls their access levels to the library, depending on the group’s assigned permission levels on the library. Without the need for folders, permissions can be set up directly on the document library (if the library is to have unique permissions different to the site level permissions), otherwise the library’s permissions can inherit from the defined permissions at the site level.

Key benefits:

  • Controlling who has access to specific content in document libraries using the SharePoint security model.

DOCUMENT LIBRARY VIEWS

The All Documents document library view is the default view that typically always has all the metadata properties in the library visible. This view is to be used for doing bulk tagging on the documents in the library, post the bulk upload of files. It can also be considered as the administrative view of the library.

Key benefits:

  • Improved content find-ability
  • Reporting of content
  • Enhanced user productivity
  • Bulk tagging of documents in the library post bulk upload.

CONFIGURE ALERTS

Alerts can be set up in a document library. They will inform you if someone is trying to change or delete your documents in some form or fashion. It will also keep you up to date on what has been added / changed in the document library through email notifications. The following are the available options to configure for the alert:

Key benefits:

  • Stay up to date with content updates in the document library
  • Enhance document library collaboration
  • Improve productivity.

Thanks and Happy SharePointing!!!

Courtesy: you can read the whole article here

TrickyCoder – Best practices for SharePoint a Document Management System – part 1

Companied who has adopted sharepoint as their document management system have some common issues for their document libraries, particularly in the case where a best practice is not followed for the document libraries.

The common issues that are faced are:

  • Usability
  • Lengthy URLs exceeding the URL length limitation
  • Navigation
  • Cost
  • Large libraries exceeding the 5,000 item list view threshold limit
  • Cannot co-author Microsoft Office documents
  • Data save conflicts. Security
  • User experience
  • File duplication
  • 1 Lonely View
  • Cannot sort and filter
  • Lost documents
  • Change is hard

Most of the times companies ask us to migrate thier Network share files to the SharePoint Document library.

To fullu take advantage of the SharePoint, it is always advise to convert the file share system to sharepoint using the best practices.

1. DOCUMENT VERSIONING

Enable library versioning to ensure a complete version history is kept and maintained. This allows document changes to be tracked, and provides a mechanism to allow users to restore from previous versions if required and view details on past changes made.

Key benefits:

  • Store Major and/or Minor versions on documents in the library, providing the option for restoring previous versions if/when required
  • Track changes on documents.

INDEXED COLUMNS

To improve the performance of a large list or library, you can index a column. An index on a column enables SharePoint to quickly analyse the data in that column, even when working with thousands or millions of items. For a view to quickly filter through a large number of items, the filter must be applied to a column that is indexed.

Key benefits:

  • Indexed columns in document libraries bypasses the 5,000 items list view threshold limit
  • Improved performance and helps manage large libraries.

DOCUMENT LIBRARY NAMING AND FILE NAMING CONVENTIONS

Document libraries must have a logical name to make the document management solution intuitive to use and ensure content is uploaded into the correct location. This would improve user adoption and collaboration.

File naming conventions are recommended to be named in a logical manner and short to ensure URL length limits are adhered to. It is highly recommended to not use any special characters in folder names, file names and also in document library names. Special characters such as ampersand, are not to be used. Always use alpha and numeric characters only.

Key benefits:

  • Logical naming of document libraries and file names improves navigation and makes the system more intuitive
  • Shorter and more user friendly URLs and no special characters used ensures continual system availability and functionality with improved usability.

STICK TO ONE TYPE OF CONTENT PER LIBRARY

To avoid hours of adding tags to bulk uploads, using one type of content per library can save time. This means organizing content distributed across different libraries can aid in reducing time required to tag documents in their corresponding libraries.

What are the benefits of implementing this best practice?

Key benefits:

  • Structure document libraries to store individual content types, shortening the time required to bulk tag documents
  • Improves content organisation and find-ability.

USE METADATA INSTEAD OF FOLDERS

Do not use folders to store content in document libraries because this can cause issues such as users misfiling documents, documents getting lost in nested folders, and it’s more time consuming to navigate around document libraries to locate content.

Tagging is preferable because it is more flexible. It also means you can view items by different classifications, which enriches the functionality of your library. Metadata provides the ability to view the list of files in the document library in different ways that allows you to find content quicker and also produces quality reports that is virtually impossible using folder structures.

Key benefits:

  • Better organisation of content
  • Ability to filter and group content using metadata
  • Provide useful reporting of content in document libraries
  • Improved content find-ability
  • Eliminates chances of documents getting lost in nested folders
  • Minimises chances of content getting misfiled.

For more of the best practice ideas visit the next post.