In this article, I will explain how to
Migrate from Project Server 2013 to Project Server 2016 Step By Step?
Upgrade to Project Server 2016 Prerequisites
Before we get started, you should check the below Project Server 2016 Migration Prerequisites.
In Project Server 2013 Source Farm,
- Make sure that the current Project Server 2013 farm is at least patched to Service Pack1.
To get the latest SharePoint Cumulative Update installed check Find farm patch level / latest cumulative update that has been installed on SharePoint farm
- Specify the Web Application content databases.
- Specify the PWA instance with its ‘Project Web App‘ database.
- Take a full database backup for the PWA instance database.
- Take a full database backup for the Project content databases.
In Project Server 2016 Destination Farm,
- Prepare Project Server 2016 farm.
Check Install and Configure Project Server 2016
- Take a full database backup from the Content Database.
Note: In Project Server 2016, a single database (SharePoint Content Database) holds the project data and the content to facilitate the database operations, such as backup and restore, migration, etc.
In next section, I will explain the Project Server 2016 Migration prerequisites in details
Migrate from Project Server 2013 Prerequisites
Continue reading “Migrate to Project Server 2016 Step By Step”
In this article, I will be fixing this error
SharePoint 2013 setup unable to proceed due to the following errors: This Product Requires Microsoft .Net Framework 4.5
Continue reading “SharePoint 2013 setup unable to proceed : This Product Requires Microsoft .Net Framework 4.5”
In this article, I will answer the below CMIS questions
- What’s The CMIS?
- What’s the SharePoint CMIS Procedure?
- How to configure CMIS Procedure in SharePoint 2016?
What’s The CMIS?
CMIS stands for Content Management Interoperability Services. It’s a web service standard that allows different content management systems to inter-operate seamlessly over the Internet.
What’s The SharePoint CMIS Procedure?
The Content Management Interoperability Services (CMIS) Producer is a SharePoint feature that allows the applications to interact with SharePoint lists and document libraries programmatically by using the interfaces that are defined in the CMIS standard.
- CMIS is turned off by default on all on-premises sites.
- CMIS is available after the Content Management Interoperability Services (CMIS) Producer feature is activated.
- CMIS is not supported in SharePoint Online.
How to configure CMIS Procedure in SharePoint 2016?
To configure CMIS in SharePoint 2016, you should do the following: Continue reading “Configure Content Management Interoperability Services (CMIS) In SharePoint 2016”
In this article, we will explain How to programmatically
- Set a SharePoint Lookup Field (Single Value) via SSOM C#.
- Set a SharePoint Lookup Field (Multiple Values) via SSOM C#.
- Get a SharePoint SharePoint Lookup Field (Single Value) via SSOM C#.
- Get a SharePoint SharePoint Lookup Field (Multiple Values) via SSOM C#.
Continue reading “SharePoint Lookup Field Multiple Values Via C#”
Consider you need to install a new Cumulative Update or Service Pack on your current SQL Server, but you don’t know what’s the current update level that already installed in your environment!!
In this article, we will explain
How to detect the current Cumulative Update / Service Pack that was installed on SQL Server.
Detect the Current Cumulative Update / Service Pack Installed
You can use the ServerProperty as a system defined function to return the SQL Server Instance information like the ProductLevel and ProductUpdateLevel
The ProductLevel returns the version level of the SQL Server instance as the following.
- ‘RTM‘ = Original release version
- ‘SPn‘ = Service pack version
- ‘CTPn‘, = Community Technology Preview version
select SERVERPROPERTY('ProductLevel') as 'Product Level'
Continue reading “SQL Server: How to get the current installed update level”
In this article, I will show how to
Detect the SharePoint 2016 Edition and the Farm Build Number using C#.
Detecting the SharePoint Edition via c# is not just line of code as detecting the SharePoint Build Number!
To detect the SharePoint 2016 Edition, it requires knowing the corresponding SKU.
The Stock Keeping Unit (SKU) is a unique set of characters identification code for a particular product/service. Read more at SKU.)
Get SharePoint 2016 Edition using C#
Based on the installed product SKU, you can detect the corresponding SharePoint 2016 Edition via C# as the following:
Continue reading “Detect the Installed SharePoint 2016 Edition Using C#”
In this article, I will explain
How to detect the installed SharePoint Edition Using PowerShell?
Before you getting started, you should make sure that the current user has sufficient privilege to run PowerShell Script in SharePoint, Read more at Add-SPShellAdmin
Note: You can directly use the farm account to run this script.
There is a lot of articles talk about this topic, but the new here is detecting the SharePoint 2016 Edition based on the SKU ID. Continue reading “Detect the Installed SharePoint Edition Using PowerShell”