Tag Archives: best hosting

SharePoint 2010 – ASPHostPortal.com :: Creating a Custom Login Page for FBA in SharePoint 2010


Today I will tell you how to Create a Custom Login Page for FBA in SharePoint 2010.  While as of late assisting my client with their Sharepoint 2010 FBA design, I went over an obviously baffling part of utilizing a custom ASP.NET form to handle the validation. Amid the advancement of custom login page, i came to realize that a large portion of documentation that is accessible on this theme, all that is needed is to give a URL to your structure in Central Administration. The inquiry is do you think it is just conceivable approach to do this by giving URL in Central Admin? The answer is NO. It is conceivable. Lets have some Tea and prepared to ride on this.


It would be incredible if things worked so effortlessly as simply hitting in a URL and the back-end wiring itself up naturally. Lets accept you have an essential ASP.NET form and you’ve arranged it in this way with standard control alongside expecting that you’ve set up the Asp.net Membership SQL database, designed the Membership and Role suppliers, rolled out the vital improvements in the web application, Secure Token Service and Central Admin web.configs and gone into Central Administration to arrange Forms Based confirmation (FBA in Sharepoint 2010),you’d find that all your endeavors would have been for nix – This structure would submissively approve your qualifications against the Membership database and afterward savagely provided for you a lapse when the structure endeavored to redirect you /_layouts/Authenticate.asp

Why this blunder comes? Reason:

A vanilla ASP.NET form inherits from System.web.ui.page – you are no one worth mentioning the extent that Club Sharepoint 2010 is concerned. Since an ASP.NET form has no clue how to make the obliged cases based validation token to pass along to Sharepoint to say that you truly are on “the rundown” and that you know this gentleman inside who can guarantee for you.


There is no API documentation on this. For this situation, to set your login structure page to inherit from the same class that the out-of-the-case Sharepoint FBA login structure executes: Microsoft.sharepoint.identityprovider.formssigninpage (you can discover this page in the/_forms sub organizer of any Sharepoint 2010 web application that has been set for FBA – 11574 for my situation.

Creating a Custom Login Page for FBA in SharePoint 2010

Presently everyonce thinks about polymorphism, we can get to all the Sharepoint FBA/Claims Auth token creation goodness out-of-the-case FBA structures get “free of charge” utilizing the enchantment of polymorphism.

Creating a Custom Login Page for FBA in SharePoint 20102

You can utilize your own altered expert page likewise in which your modified client control will be incorporated (I have made an expert page with name “Masterforcustomlogin” which contains tweaked html according to my prerequisite).

You can make an organizer likewise in _forms/ (Basically it requires to store pictures if your login page has)

By doing this, you can now adjust your prior FBA login structures to accommodate with the cases based auth necessities for Sharepoint 2010.

My Login page resembles this now (in the wake of performing above steps):

Creating a Custom Login Page for FBA in SharePoint 20103

Once you enter your credentials, you will be authenticated with your membership providers and able to logged in.

During this development, I observed one thing – When you enter your sharepoint site url into address bar it looks like :

Creating a Custom Login Page for FBA in SharePoint 20104

You can see “http://kirti-p:11574/_login/default.aspx?ReturnUrl=%2f_layouts%2fAuthenticate.aspx%3fSource%3d%252F&Source=%2F”. This _login folder is available in virtual directory of sharepoint site itself. When you select “Forms Authentication” from drop down this url will be changed and looks like:

Creating a Custom Login Page for FBA in SharePoint 20105

It says, while you are accessing Forms Authentication option it refere different master page.


You have to change master page entry accordingly. Thats it for custom login page.

SharePoint 2013 Hosting with ASPHostPortal.com :: How to fix “Microsoft SharePoint is not supported with version 4.0.30319.225 of the Microsoft .Net Runtime” in PowerGUI


banner promo-01

Today, i will tell you about fixing “Microsoft SharePoint is not supported with version 4.0.30319.225 of the Microsoft .Net Runtime” in PowerGUI. This porblem started when I attempt to run some Powershell command against Sharepoint in PowerGUI , I experience some slip message as beneath:

Remove-SPSite : Microsoft SharePoint is not supported with version 4.0.30319.225 of the Microsoft .Net Runtime.

At C:\SiteCreation.ps1:37 char:14

+ CategoryInfo : InvalidData: (Microsoft.Share…mdletRemoveSite:SPCmdletRemoveSite) [Remove-SPSite], PlatformNotSupportedException

The mistake message is really clear that Powergui attempt to run the Powershell command under .Net form 4.0 which is not backed by Sharepoint2010, Sharepoint2010 just help .Net 3.5.so in what capacity would I be able to change the settings so that Powershell does run under .Net3.5 in Powergui? The arrangement is really simple.


1. Open your windows explorer and explore to C:\program Files (x86)\powergui\ and open the configuration file Scripteditor.exe.config.

2. Change the supportedruntime form under Startup settings by deleting the version=”v4.0″ as underneath.

From :

<startup useLegacyV2RuntimeActivationPolicy=”true”>
<supportedRuntime version=”v4.0″ sku=”.NETFramework,Version=v4.0″ />
<supportedRuntime version=”v2.0.50727″ />

To :

<startup useLegacyV2RuntimeActivationPolicy=”true”>
<supportedRuntime version=”v2.0.50727″ />

3. Restart your PowerGUI and rerun your script. It works like a charm.

SharePoint 2013 Hosting – ASPHostPortal.com :: Including a Blog to an Existing Site (Without Creating a New Site)

Usually when you want a website in SharePoint 2013, you should produce a brand new website assortment or a subsite using the Website site template.

1dfvwsjbefAt times it would just be simpler (or great) to have a weblog correct in yet another web site for instance a team site or departmental website without the require for yet one more site selection or subsite to maintain. No problem.


You can easily include a weblog to an present website making use of PowerShell. Fire up the SharePoint 2013 Management Console and enter the subsequent command:

Enable-SPFeature -identity “BlogContent” -url <<the url of the site>>

2ntntjNext, navigate to the site in the browser and edit the home page:

3tbrtntnFrom the Insert tab on the top ribbon, click on Web Part:

4grjrjtySelect Posts from the Apps category and click on the Add button:

5trmjrymThe blog posts now appear on your home page:

6mtymtClick on the sample blog post:

7dfnfnYou now have a blog in your existing site without having a separate subsite!

SharePoint 2013 Hosting with ASPHostPortal.com – How To Migrate Content Database From SharePoint 2010 To SharePoint 2013

Migrate Content Database From SharePoint 2010 To SharePoint 2013

In this article, we will take you through the database migration process from SharePoint 2010 to SharePoint 2013. An overview of the SharePoint database migration process to a new server is available on the ShareGate website.


Step-by-step to migrate content database

  • Step 1 : Make two servers available for the process. Both the servers need to run on the same environment. For instance, Server 1 should run on Windows 2008, SQL server 2008 and include SharePoint 2010. Server 2 should run on Windows 2008, SQL server 2008 and include SharePoint 2013.
  • Step 2 : You must begin with backing up the data from Server 1. To do this,

a) While on SharePoint 2010, pick the database of the port you want to back-up. Right click and from the options that appear, click Tasks → Back Up.
b) In the subsequent window that opens, click ‘Add
c) Copy the location available under the ‘Destination’ field and save it a notepad for later use.

  • Step 3 : On server 2, launch SharePoint 2013 and create a new web application under any port. If you are not sure, pick port 88.
  • Step 4 : Once a new application has been created, perform the following steps:

a) Under Central Administration, select Application Management Manage Content Databases
b) Under the newly created web application, select ‘Remove content database checkbox’. Click OK and SAVE
c) Under the Content Database section, you should now see a message that reads, “There are no items to show in this view’

  • Step 5 : The next step is to restore the database from SharePoint 2010 to the new server. To accomplish this, copy the WSS_Content.bak file from Server 1 on to the desktop or any convenient location on the computer handling Server 2.
  • Step 6 : In SharePoint 2013, launch SQL Server 2008 and right click on the node titled Database and from the options, choose ‘Restore Database’.
  • Step 7 : A new ‘Restore Database’ window now opens. Here, select the ‘From Device’ radio button and browse through your system folders to select the WSS_Content.bak file that we had earlier copied in Step 5. Click OK
  • Step 8 : Next, under the ‘Options’ tab of the Restore Database window, check the box that reads, “Overwrite the existing database (WITH REPLACE)”. Press OK to continue. A message box appears that confirms the operation. Press OK to close this box.
  • Step 9 : Open SharePoint 2013 and navigate to Central Administration → Application Management → Manage Content Databases. You should now see the WSS_Content.bak file displayed here.
  • Step 10 : On the top of the window, you will see a message. Click on the ‘Start Now‘ link to continue.
  • Step 11 : In the subsequent window, click on the ‘Upgrade the site collection’ option. You will be shown a message box. Click ‘I’m Ready‘ to continue.
  • Step 12 : The upgradation process will now begin. This typically takes a few minutes. Once you are done, you will be shown a message that reads, “Upgrade Completed Successfully”

This completes the process. Your content database migration from SharePoint 2010 to SharePoint 2013 has been completed successfully.