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.

Sharepoint 2013 Incoming Email Mails were stucked on SMTP Drop Folder

SharePoint Incoming Email Service Not Pickup the Mails from Drop folder

I have upgraded the Windows SharePoint Service 3.0(Standalone) which had incoming Email Service to SharePoint 2013 Server (Multi-farm Environment).

The upgrade was successfully completed and I configured the Incoming Email service based on the Microsoft Article but the mails were not picked from SMTP Drop folder to SharePoint.

I reconfigured many times but it was not solved. Finally I have followed the below article which resolved the issue and all the mails were picked from SMTP drop folder to SharePoint

https://netorg147440-public.sharepoint.com/Lists/Posts/Post.aspx?ID=3

Remove specific user from All Site collections in office 365 Tenant

 

Finally I got below script to remove user from all site collections in office 365 Tenant J

$credential = Get-Credential

$Adminurl = "https://XXXXX-admin.sharepoint.com"

Connect-SPOService -url $Adminurl -credential $credential

write-host "Connected" -foregroundcolor green

$sites = get-sposite

Foreach ($site in $sites)

{

Write-host "Removing users to $($site.URL)" -foregroundcolor yellow

Remove-SPOUser -Site $site.url -LoginName user@yourdomain.com

}

SharePoint 2016 preview Installation

I have completed Application SharePoint Farm for SharePoint 2016 Preview with dedicated Database Server. I would like to share the SharePoint 2016 installation experience to all. The details and steps are below

Hardware Requirement for SharePoint 2016

Scenario	Deployment Type	Processor	RAM	Hard Disk
Database server running a single SQL instance	Development or evaluation installation with the minimum recommended services	64-bit, 4 cores	12-16 GB	80 GB for system drive 100 GB for second drive
Database server running a single SQL instance	Pilot, user acceptance test running all available services	64-bit, 4 cores	12-16 GB	80 GB for system drive 100 GB for second drive and additional drives
Web server or application server in a three-tier farm	Development or evaluation installation with the minimum number of services	64-bit, 4 cores	12-16 GB	80 GB for system drive 80 GB for second drive
Web server or application server in a three-tier farm	Pilot, user acceptance test running all available services	64-bit, 4 cores	12-16 GB	80 GB for system drive 80 GB for second drive and additional drives

Server Type	Operating System	Installation Media	SP 2016 Prerequisites
Database	Windows Server 2012 R2	SQL Server 2014
SharePoint Server	Windows Server 2012 R2	SharePoint 2016 Preview	· Application Server Role, Web Server (IIS) Role · Microsoft SQL Server 2012 Native Client · Microsoft ODBC Driver 11 for SQL Server · Microsoft Sync Framework Runtime v1.0 SP1 (x64) · Windows Server AppFabric 1.1 · Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB2671763) · Microsoft Identity Extensions · Microsoft Information Protection and Control Client · Microsoft WCF Data Services 5.0 · Microsoft WCF Data Services 5.6 · Microsoft .NET Framework 4.5.2 · Update for Microsoft .NET Framework to disable RC4 in Transport Layer Security (KB2898850) · Visual C++ Redistributable Package for Visual Studio 2013

SharePoint 2016 Installation steps

Ø Install the SharePoint 2016 Prerequisites

Ø Install the SharePoint 2016

Ø Run the SharePoint 2016 product configuration Wizard

Ø Select appropriate Role in the Minimum role Topology(MinRoleTopology)

Ø Complete the SharePoint 2016 Product configuration Wizard

Install SharePoint 2016 prerequisites:

Run the Splash Setup and Click “install prerequisites “and follow the instructions to complete the prerequisites installations and restart the machines.

Install SharePoint 2016 Preview

Run the splash setup and click install SharePoint 2016 and follow the instructions to complete the installations.

SharePoint product configuration Wizard and Select MinRoleTopology

1. Run the configuration and follow the instruction

2. In the Minimum Role Topology Section select the appropriate Role. For my case I have selected Application Role and completed the configuration wizard

Roles	Descriptions
Front End	Services end user requests, optimized for low latency.
Application	Services the backend jobs or the requests triggered by backend jobs, optimized for high throughput.
Distributed Cache	Services distributed cache for the farm. Optionally, the server assigned to this role can load balance end user requests among the web front ends.
Search	Reserved for Search services.
Custom	Reserved for services to be isolated from other services, I.e. 3rd party, PerformancePoint, etc.
Single-Server Farm	Provisions all services on the server for a single server deployment. This role is provided for evaluation and development purposes.

Important: Single Server Farm is like a Standalone installation, so you could not join additional machines to this SharePoint Farm.