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:

How to recover SharePoint 2013 Databases from Suspect Mode ?

What is Suspect Mode ?

Suspect mode might be caused by many reasons like unavailable or corrupted database files, hardware failure etc.

Steps to recover database from the Suspect mode:

Pre-Requisites

Make sure a user who is performing the below given steps has the administrator rights for the sql server/

  1. Open SQL Server Management Studio with Run as Administrator
  2. Run the following query one by one
  3. EXEC sp_resetstatus ‘SharePoint_Config’;
  4. ALTER DATABASE SharePoint_Config SET EMERGENCY
  5. DBCC checkdb(‘SharePoint_Config’)
  6. ALTER DATABASE SharePoint_Config SET SINGLE_USER WITH ROLLBACK IMMEDIATE
  7. DBCC CheckDB (‘SharePoint_Config’, REPAIR_ALLOW_DATA_LOSS)
  8. ALTER DATABASE SharePoint_Config SET MULTI_USER
  9. DBCC CheckDB (‘SharePoint_Config’)

You might need to repeat these steps for each one of the affected databases.

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

Enjoy this blog? Please spread the word :)