Error Installing SharePoint Server 2013 on Windows Server 2012: Setup is unable to proceed due to the following error(s): This product requires Microsoft .Net Framework 4.5

I got this error when I was installing SharePoint Server 2013 for a client where they have already installed the Visual studio 2015 and SQL Server 2014 on Windows Server 2012.

While doing google for solving this error, I got this solution from a blog.

Open Windows PowerShell (Run as administrator) and run the following command to check which version of .NET framework is installed on the server :

• Set-Location ‘HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client’
• Get-ItemProperty -Path . | Select-Object Version

Then depending on the version installed and the OS you’re using, you need to uninstall the corresponding KB :

.NET Framework 4.6.1 : https://support.microsoft.com/en-us/kb/3102436
Windows Server 2012 : KB3102439
Windows Server 2012 R2 : KB3102467

.NET Framework 4.6 : https://support.microsoft.com/fr-fr/kb/3045560
Windows Server 2012 : KB3045562
Windows Sstscerver 2012 R2 : KB3045563

To uninstall the corresponding KB ->
• Press windows + R keys and type appwiz.cpl in run window.
• Click on View installed updates from left side menu under Control Panel Home link.
• Copy or type the KB Name in Search Programs and feature box on top right side.
• Select the KB and click on Uninstall the KB.
• Restart the Server and try to run SharePoint Server 2013 Setup again.

It works for me, hope it will work for you as well.

Cheers 🙂

Microsoft.SharePoint.Administration.SPDuplicateObjectException: An object of the type Microsoft.Office.Server.UserProfiles.SecondInteractiveMySiteInstantiationWorkItemJobDefinition named “MySite-Second-Instantiation-Interactive-Request-Queue” already exists under the parent Microsoft.SharePoint.Administration.SPWebApplication named “SharePoint – 80”. Rename your object or delete the existing object.

Solution : Open SharePoint 2013 Management Shell and run the following commands

$badjob = Get-SPTimerJob | where { $_.name -like “MySite-Second-Instantiation-Interactive-Request-Queue” }

$badjob.delete()

Make Text box read only in List form in SharePoint

Solution 1:

function MakeFieldReadOnly()
{
SPUtility.GetSPField(‘Name of your List Field’).MakeReadOnly();
}
_spBodyOnLoadFunctionNames.push(“MakeFieldReadOnly”);

Solution 2:

function SetReadOnlycolumn()
{
var elements=document.getElementById(‘Quantity_cxx18421-0fd5-48c8-8696-86a677b2b20d_$NumberField’);
elements.readOnly=true;
}

_spBodyOnLoadFunctionNames.push(“SetReadOnlycolumn()”);

Check SQL Server Connection from client without installing SSMS

Hi folks,

Often we face Issues to check connectivity between SQL Server and application server.

There is a trick built into Windows that allows you to test the connectivity without having to install SQL Server Management studio or any third party software. It works on both client and server operating systems just as well.

Solution:

Step 1: Right click on windows desktop and create a new file from menu.

CHkSQLConnectivity_1

Step 2: Change the file extension from .txt to .udl

chkSQLConnectivity_2

Step 3: Double click the .udl file. This will give you a Data Link Editor that allows you to test the connection. Enter or select the SQL server from dropdownlist. Enter credentials to connect to SQL Server and select database.

chkSQLConnectivity_3

Step 4: Click on test connection to verify the connection.

Hope this blog will help someone.

Cheers 🙂

SharePoint Server 2013 Config wizard failed at Step 8.

Sharepoint Server 2013 installations could go wrong when you install sharepoint 2013 in a machine which is not added to a domain. You will see the following error at step 8 of the configuration wizard.

“An exception of type System.ArgumentException was thrown.Additional exception information: The SDDL string contains an invalid sid or a sid that cannot be translated.Parameter name: sddlForm”

This error occures when sharepoint configuration try to create a UNCShare of a folder which is located at “C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Analytics_<GUID>”.

Solution :
1. Share the folder “C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server\Analytics_<GUID>” to everyone.
2. Add the WSS_Admin_WPG Group and give Full Permission to WSS_Admin_WPG group.
3. Rerun the configuration wizard.

cheers 😉

SharePoint 2010 User not able to save managed-metadata

SharePoint uses a hidden list called the TaxonomyHiddenlist to cache all the available taxonomy terms for a specific site collection.

The TaxonomyHiddenList is located on the root site of every site collection and contains all the terms and keywords used withing the current site collection at http://SharePointServer/lists/TaxonomyHiddenList.

SharePoint uses the list as a cache, by caching the terms in the hidden list there is no need to query the managed metadata service all the time. A taxonomy term is cached when a term has been used in a list.

By default NT AUTHORITY\Authenticated Users has read permissions to this list.
In this case the default permissions where somehow removed or never set.

The issue was resolved by granting NT AUTHORITY\Authenticated Users read access to the TaxonomyHiddenlist.

😉

Attach event receiver to list

$web = Get-SPWeb http://sharepointserver
$spList = $web.Lists[“SharePointListName”]
$spEvent.Name = “MyEventName”
$spEvent.Type = “ItemAdded”
$spEvent.Synchronization = “Asynchronous”
$spEvent.SequenceNumber = 3000
$spEvent.Assembly = “MyEvent.SharePoint.Event, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a5b2c962bb0989s4”
$spEvent.Class = “MyEvent.SharePoint.Event.PowerShellEventReceiver”
$spEvent.Update()
$spWeb.Dispose()