Another object in this farm already contains the same ID

Cannot attach databases with same ID to different web applications

Databases with same internal ID cannot be attached web applications even if the databases have different name. If we try attach the database with same id, we would be get “another object in this farm already contains the same ID” as shown in below image.

We ran below commands to find and delete the database 

Get-SPDatabase | where{$_.Name -eq "webappliction Name"}

Remove-SPcontentdatabase –identity “ID of the DB”

The database attached successfully after we removed the existing database.

Cannot connect to the configuration database

When I open SharePoint Central admin and Application Portal got the following Message “Cannot connect to the configuration database”

I checked and confirmed the below are looks good as per Microsoft link but the issue is exist.

•        SQL Services are up and Running
•        The SharePoint and SQL Server are talking together
•        Nothing Database in Suspect Mode
•        No Port Blocking in Firewall
•        SharePoint Account had proper Permission in SQL

Finally found that the Application Pool account was locked due to some reason which caused the “Cannot connect to the configuration database” issue.

The Central admin and Application Portals are working fine after the Application Pool account unlocked for my incident.

Event ID 6801 - FIMSynchronizationService

Issue:

The AD Manager Property Value are not synced with SharePoint 2010 though SP UPS Service configured properly and got the below Event log messages

Event Id 6801 - FIMSynchronizationService “More than one DN Specified for the Same Profile”

Event ID 6801- FIM Synchronization Service “ Exception while trying to Migrate user  test\ramu  to thetest\ramu, The user does not exist or not unique”

Cause:

The NETBIOS (test\ramu) is different from Domain Name (thetest\ramu) which caused the issue.

Resolution:

The default configuration of the User Profile Service Application does not include the NetBIOS namespace.

The User Profile Service application setting has been changed by ran the below commands

$UPA = Get-SPServiceApplication –id “User Profile Service Application ID”

$UPA.NetBIOSDomainNamesEnabled=1

$UPA.Update()

No Help Collection was found and unfortunately help seems to be broken in SharePoint 2016

No Help Collection was found and unfortunately help seems to be broken in SharePoint 2016

I got “No Help Collection was found” in Help Setting Page, also I got “Unfortunately Help Seems to be Broken” Message when Navigated to Help Page in SharePoint 2016 Site.

The issue has been resolve after the Help collection installed in the Server. Run the below commands for installation and verification.

Install-SPHelpCollection –All

Get-Sphelpcollection

Note: The installation of Helpcollection will take 5 to 10mins. Please Run Get-Sphelpcollection Command after installation.