SharePoint foundation 2013 Offline Installation

I was trying today to install SharePoint foundation 2013. The Prerequisites Installer could not download the dependencies, i did not search why and i wanted to perform an offline installation.

Solution :

  1. Download all the prerequisites.
  2. Extract the sharepoint installer : sharepoint.exe /extract:”C:\SharePoint2013\prerequisiteinstallerfiles”
  3. Copy the downloaded prerequisites to “C:\SharePoint2013\”
  4. Run again the prerequisiteinstaller.

 

Microsoft .NET Framework 4.5

(Full Stand alone package)

http://go.microsoft.com/fwlink/?LinkId=225702
Windows Management Framework 3.0 http://www.microsoft.com/en-us/download/details.aspx?id=34595
Microsoft SQL Server 2008 R2 SP1 Native Client http://www.microsoft.com/en-us/download/details.aspx?id=26728
Windows Identity Foundation (KB974405) http://go.microsoft.com/fwlink/p/?LinkID=226830
Windows Identity Extensions http://go.microsoft.com/fwlink/?LinkID=252368
Microsoft Sync Framework Runtime v1.0 SP1 (x64) http://go.microsoft.com/fwlink/p/?LinkID=224449
Windows Server AppFabric http://go.microsoft.com/fwlink/?LinkId=235496

 

 

Microsoft Information Protection and Control Client http://go.microsoft.com/fwlink/p/?LinkID=219568
Microsoft WCF Data Services 5.0 http://www.microsoft.com/en-us/download/details.aspx?id=29306
Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB2671763  

http://www.microsoft.com/en-us/download/details.aspx?id=29241

 

 

Advertisements

SharePoint 2013 Foundation Installation : This product requires Microsoft .Net Framework 4.5

I was trying to install SharePoint 2013 Foundaiton on a Windows Server 2012 R2. Microsoft says that only a SP1 pack is installable on a Windows Server 2012 R2.

I run the prerequisites and installed the dependencies offline including .Net Framework 4.5.

Problem :

When i start the installation i get this error :

This product requires Microsoft .Net Framework 4.5

It was very weird because when i try to add the .Net Framework 4.5 Feature, The Server Manager shows that it is already installed.

 

 

 

 

 

 

 

 

 

 

 

 

Solution :

My first thought was : maybe i am missing some updates. I checked The Microsoft Updates center and everything was up-to-date… and that is the Problem, Sharepoint 2013 is since 2013, and having a very up-to-date Server could cause issues.

I checked the .Net Framework Version :

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

And i found that the 4.7 version was installed. To Uninstall it i had to uninstall the Update KB3186539 .

Open the Windows Update Center and search for this KB.

Be carefull : The KB depends on which version of .Net framework you found, search for “The .NET Framework XX.XX offline installer for Windows” and you will find which KB is related to it and just uninstall it.

SharePoint does not overwrite documents with the same name, he creates a new one!

I always thought that SharePoint overwrites files with the same name(of course when you check this checkbox).

Unfortunately it is not the case, SharePoint does not “overwrites” it, he deletes the documents and creates a new one while keeping the name.

Who says a new item, says a new ID….The problem is if you have an application who is based on the document’s IDs…

The solution is to change your code and use the document URL(FileLeafRef Property) instead of the ID.

 

SandBox solution : provision publishing page with custom web parts

 

In my last article i talked about provisioning publishing pages with a module on sandboxed solutions.

Today i will talk about adding custom WebParts to a provisioned publishing page.

On farm solutions we need only type of the WebPart and the import error message. But on sandbox we need to specify the id of the solution that deployed the WebPart :

sandboxWP

 

 

 

 

 

You can find the solution ID on the manifest file of the package.

 

Sandbox Solution : Provision publishing page

Last year while working with sandboxed solution for SharePoint 2010, i faced a problem while creating a module to provision publishing pages with WebParts.

Problem :

I used this code :

module

 

 

 

 

I added this module on a feature, but when i activate the feature i get :

  1. The page is draft
  2. The WebPart is not added.

Solution :

This approach assume that the file “page.aspx” will be copied on the 14 folder on the feature folder. However SandBoxed solutions do not have access to root folder.

The solution is to use a file which is already on the SharePoint root folder :

sandboxModule

 

 

 

What i changed is the “SetupPath” , this property is used to specify a physical path to a folder that contains a file to include on the module.

I will use the file “SiteTemplates\SPS\default.aspx” so i set SetupPath to “SiteTemplates\SPS” and the Path of the file to “default.aspx”.

And now everything is working fine 🙂

 

User Profile property not appearing in search

Hello Everybody.

Today i am going to talk about a problem i got twice(on sharepoint 2010 and 2013).

It is about some user profile properties that are not crawled.

Solution :

Well you have to check 4 important things :

  • At least one user profile has informations on this field/property.
  • You selected “Everyone” on user policy : when you edit each user profile on central admin.
  • The property is Searchable : user profile service application -> Manager user properties
  • The crawled property is mapped to “ContentsHidden” managed propery(in addition of your managed property)

Example :

If you want to crawl the Manager property you have to :

  • Edit some user profiles to fill their Manager, and make sure you chose “Everyone”

Everyone

  • Make sure that the user profile property “manager” is searchable
    searchable

 

 

  • Map the crawled property People:Manager to the managed property  “ContentsHidden” (if the crawled property is not yet created perform a full crawl)

    mapped

I hope that my article will help you.