A Responsive Blogger Website, That Take my blog to the next level.

I am a Software Developer, Learning and experementing with .Net Technology and try to put my Learning altogether here.


We have all sections related to .Net Technology, like .Net-C#, Asp.Net, MVC, jQuery, AngularJs, Sharepoint. Find out more...


Following are the some of the Advantages of using this Web site :-

  • Get Update about latest in .Net world.
  • Collection of Useful, Frequently used .Net Solutions.
  • It’s beautiful on every screen size (try resizing your browser!)
Showing posts with label SharePoint. Show all posts
Showing posts with label SharePoint. Show all posts

Home » Posts filed under SharePoint

by · · No comments :

Sleek SharePoint Pages!

Chandan Kumar
shared this article with you from Inoreader
In real-world projects I have noticed the following SharePoint Branding mistakes.
1. Inheriting a Publishing Page for a Fully Immersive UI where we don't actually use any Publishing functionalities like Page Layouts, Approval Workflow, Content Authoring etc.
2. Using Content Editor web part to dynamically invoke an HTML file there by delaying loading through unwanted SharePoint stuffs.
Incurred Costs
This will have immediate costs of:
· Increased Development Time
· Reduced Performance
· Increased Download Size
This will have future costs of:
  • Forcing client to purchase SharePoint Standard/Enterprise editions rather using the Free Foundation
Requirement Context
The requirement context here is to have a Fully Immersive Page without SharePoint Branding and allowing REST Operations.
Key Solution
I am providing a Key Solution which is:
1. Sleek in SharePoint Branding
2. Applicable for Fully Immersive Pages
3. Minimal SharePoint Contents loaded
4. SharePoint Foundation compatible
Steps
Open a SharePoint Designer and Choose Site Pages > Page ASPX option.

p1

Now, Open Designer and Go to Site Pages library.

image

You can see our page is listed there and the Content Type is of Wiki Page.  We don't worry about that since we are not using any Wiki Page functionalities.  Plus, our page is SharePoint Foundation compatible.\
image
You can also use HTML page instead of ASPX. In this case we need to change the Web Application property to allow HTML extensions to render instead of download & work with more challenges.
Now open the Page and choose Edit file option.

image

You will see the following page with read-only mode.

p2

Click on the Advanced Mode to edit the contents.
image
You will get the page in edit-mode as shown below.

p3


From the Immersive Page Perspective, We are expecting a Full Custom Page which does not require any SharePoint Branding or Ribbon elements. The above Page fits our requirement.
Following is the page content.
<%@ Page Language="C#" %>
<%@ Register tagprefix="SharePoint" namespace="Microsoft.SharePoint.WebControls" assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<meta name="WebPartPageExpansion" content="full" />
<meta http-equiv="X-UA-Compatible" content="IE=10″ />
<SharePoint:CssRegistration Name="default" runat="server"/>
</head>
<body>
<form id="form1″ runat="server">
</form>
Your HTML content goes here..
</body>
</html>
You can save the page and test in browser. You can see now the SharePoint Branding elements got removed.

image

You can View the source. The source looks simple.

p4

Now you are ready to use the above Page Template for building the Fully Immersive Page with Responsive Or Non-Responsive web design.  Full Control! Sleek! Faster!

html

image
You can also use HTML page instead of ASPX. In this case we need to change the Web Application property to allow HTML extensions to render instead of download & work with more challenges.
The Challenge
Now we need to use JSOM or REST API on the ASPX page. Clearly, we cannot use API because it will throw lot of security errors. The solution is to include the Form Digest tag.
Form Digest tag marks the page with right Security Contexts. This will allow the page to do POST requests to modify the contents in SharePoint.
Following would be the modified code.
<SharePoint:CssRegistration Name="default" runat="server"/>
<script src="/_layouts/15/init.js"></script>
<script src="/_layouts/15/MicrosoftAjax.js"></script>
<script src="/_layouts/15/sp.core.js"></script>
<script src="/_layouts/15/sp.runtime.js"></script>
<script src="/_layouts/15/sp.js"></script>
Add Form Digest value too.
<form id="form1″ runat="server">
<SharePoint:FormDigest runat="server"></SharePoint:FormDigest>
Your HTML content goes here..
</form>
The additional contents added ensure that the Page is protected to Post data through APIs.
image
Since we are hiding SharePoint Ribbon, it will hide the User Display Name & Gear Icon too.  If you require these, I would recommend creation of a Custom DIV and Add those Items manually.
Insert Test
Now let us really test an item insertion. You can use the following link for that.
http://www.jeanpaulva.com/index.php/2016/01/23/insert-using-rest-api/
References
SharePoint Pages http://bit.ly/1SKXOrI
SharePoint Editions & Features http://bit.ly/1K0UyY5
Form Digest http://bit.ly/1QIKzWB
Summary
In this article we have explored a sleek way of developing Fully Immersive SharePoint Pages.
View on the web
Inoreader is a light and fast RSS Reader. Follow us on Twitter and Facebook.
Read More
by · · No comments :

SharePoint Server 2016 Release Candidate Single Server Installation Guide

Chandan Kumar
shared this article with you from Inoreader
SharePoint

In this article you will learn about SharePoint Server 2016 Release Candidate Single Server Installation Guide.

Index

  • Introduction
  • Hardware Requirement
  • Software Requirement
  • Prerequisites for SharePoint Server 2016 Beta 2
  • Steps to install Prerequisites for SharePoint Server 2016 Beta 2
  • Steps to install SharePoint Server 2016 Beta 2
  • Steps to run SharePoint Product Configuration Wizard

Introduction

SharePoint 2016 Installation guide document contains steps to install SharePoint Server 2016 Beta. Download SharePoint server 2016 Beta 2 using the following link.

Hardware Requirement

Hardware requirement varies according to installation scenario. Hardware requirement for web servers, application servers, and MinRole installations for different installation scenarios is as follows:

Installation scenario Deployment type and scale RAM Processor Hard disk space
Single server role that uses SQL Server Development or evaluation installation of SharePoint Server 2016 Beta 2 with the minimum recommended services for development environments. 12–16 GB 64-bit, 4 cores 80 GB for system drive

100 GB for second drive
Single server role that uses SQL Server Pilot or user acceptance test installation of SharePoint Server 2016 Beta 2 running all available services for development environments. 16–24 GB 64-bit, 4 cores 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 of SharePoint Server 2016 Beta 2 with a minimum number of services. 8–12 GB 64-bit, 4 cores 80 GB for system drive

80 GB for second drive
Web server or application server in a three-tier farm Pilot, user acceptance test, or production deployment of SharePoint Server 2016 Beta 2 running all available services. 12–16 GB 64-bit, 4 cores 80 GB for system drive

80 GB for second drive and additional drives

Table reference.

Software Requirement

Minimum software requirements for each server in the farm is as follows:

Server Operating System Installation Media .Net Framework
Database Server The 64-bit edition of Windows Server 2012 R2 Standard or Datacenter The 64-bit edition of Microsoft SQL Server 2014 Service Pack 1 (SP1) Microsoft .NET Framework version 4.5.2
SharePoint Server The 64-bit edition of Windows Server 2012 R2 Standard or Datacenter SharePoint Server 2016 Beta 2 Microsoft .NET Framework version 4.5.2
       
       

Prerequisites for SharePoint Server 2016 Beta 2

You need to install below listed prerequisites for SharePoint Server 2016 Beta 2.

  • Web Server (IIS) role
  • Application Server role
  • Microsoft .NET Framework version 4.5.2
  • Microsoft SQL Server 2012 Native Client
  • Microsoft WCF Data Services 5.6
  • Microsoft Information Protection and Control Client (MSIPC)
  • Microsoft Sync Framework Runtime v1.0 SP1 (x64)
  • Windows Server AppFabric 1.1
  • Cumulative Update Package 7 for Microsoft AppFabric 1.1 for Windows Server (KB 3092423)
  • Microsoft ODBC Driver 11 for SQL Server
  • Update for Microsoft .NET Framework to disable RC4 in Transport Layer Security (KB2898850)
  • Visual C++ Redistributable Package for Visual Studio 2012.
  • Visual C++ Redistributable Package for Visual Studio 2015.

Steps to install Prerequisites for SharePoint Server 2016 Beta 2

Follow below steps to install prerequisites for SharePoint Server 2016 Beta 2.

  1. Open Directory where SharePoint installation file is present.
  2. Right click on Prerequisite Installer file.
  3. Click on Run as Administrator option, it will open Microsoft SharePoint 2016 Products Preparation Tool.
  4. Click on Next Button.

    Accept

    Accept the terms of license agreement(s).

    Click Next

This will install all prerequisites mentioned in step 3.

  1. Once prerequisites will complete, you will get installation complete screen. Click on Finish Button.

    Note: Make sure that internet is working properly on your machine because all the prerequisites are installed from internet at the time of installation.

    OR

    You can install all prerequisites one by one using the following link.

Steps to install SharePoint Server 2016 Beta 2

Post installing all prerequisites, you have to follow below steps:

  1. Click on SharePoint Server 2016 installation link in SharePoint Server 2016 Beta 2 installer file.
  2. Now you will get a prompt for the Product Key.
  3. Enter Product Key and click on Continue button.
  4. Accept the license terms and click on Continue button.
  5. Now select file location for SharePoint Server and Search Server files.
  6. Click on Install Now button which will start installation.

Installation will complete in few minutes and after completing it you will get a window where you have option to run configuration wizard. If you select this option, configuration wizard will run after installation will complete or you can run configuration wizard manually.

Steps to run SharePoint Product Configuration Wizard

  1. When you run configuration wizard, it will start with below window.
  2. After clicking Next button on welcome screen, you may have to restart below 3 services:
    1. Internet Information Services
    2. SharePoint Administration Service
    3. SharePoint Timer Service

Click on yes if service restart needed and then continue with Configuration wizard.

  1. Now click on Create a new server farm if it is fresh installation else you can go with connect to an existing server farm (if you have already installed SharePoint).
  2. Post which you will get a screen to enter database server details and database access account details.
View on the web
Inoreader is a light and fast RSS Reader. Follow us on Twitter and Facebook.
Read More
by · · No comments :

The password supplied with the username Administrator was not correct ” Error while creating web application in SharePoint

Recently I encounter one error in SharePoint 2010,  I just change the password of admin user of  SharePoint 2010. After that when I open the Central administration it seems crash! because I didn’t change the password of each the Appool use by the admin group of share point  central administration. When I change it seems fine and working perfectly  but when I try to create a new web application on the farm it showed me erorr somethign like that.
Error :
The password supplied with the username .\Administrator was not correct. Verify that it was entered correctly and try again” Error while creating web application in SharePoint 2010.
but after lil search I found that to change the app pool password is not enough, we need to change it by power shall as well in share point server 2010
go to the power shall and enter the command with you credential.
stsadm -o updatefarmcredentials -userlogin <domain\username> –password<newpassword>.
When I run this command getting error : command line error, I am findinding solution

Today [28 March 2016] I found the solution. 

Resolved: Invalid error by stsadm command


I was trying to register custom profiledeletehandler by using stsadm command line utility. My command, code and assembly were perfect. But even then when I was trying to execute stsadm then it was displaying “The given assembly or codebase was invalid”.

Humnnn what could be the problem then after doing some research I came to know that I wrote the part of the command in notepad first and then copy/paste this part in command line. OMG, that was some encoding problem while copy/pasting the command.

Though if you delete the stsadm command and retype this in command line console then both (earlier & retyped) will look same. But this was only and major difference and solve the problem.

Solution: Please type the whole command by your own including each and everything.

Moral of the Story:

 1. Avoid copy/pasting the stsadm command from other application as you can be the victim of this type of problem.

 2. Always do check for PublicKeyToken values (If u are using assembly reference) twice and other spelling mistakes in stsadm command, as it can be the cause of these type of problems.
Read More
by · · No comments :

Activate Solution is Disabled (greyed out).

image


Solutions

Following are the solutions that we can try one-by-one:
  1. Restart Internet Explorer in Administrator Mode
  2. Ensure SharePoint User Code Host is running in Windows Services
  3. Ensure Microsoft SharePoint Foundation Sandboxed Code Service is started in Central Administration > Manage Services
Once applying the solution(s) the Activate button turned to be Enabled now. 
image
Read More
by · · No comments :

Error while creating web application in SharePoint 2013 : The password supplied with the username domainname\username was not correct.

Problem :

“The password supplied with the username .\Administrator was not correct. Verify that it was entered correctly and try again” Error while creating web application in SharePoint 2013



Solution:


I got that error while creating a new web application in SharePoint 2013. Actually recently we had changed the password of the administrator account. However we had to follow this extra step to get the things working properly.
Run the sharepoint powershell console as Administrator and run this command.
stsadm -o updatefarmcredentials -userlogin <domain\username> –password <newpassword>
Read More
by · · No comments :

SharePoint 2013 Central Administration Ribbons Grayed Out

Problem:


On SharePoint 2013 some ribbons from the Central Administration Area are grayed out. The user is a farm admin.
For example: New Web Application, New Service Application.



Solution:


Start SharePoint 2013 Central Administration from the Start Menu icon
- or -
run Internet Explorer as Administrator.


Read More