Tag Archives: best and cheap sharepoint hosting

FREE ASP.NET Hosting for SharePoint :: How to Solve Stuck Deploying status in SharePoint 2010

Signs :

ahp banner sharepoint-01Typically we will properly deploy/update a remedy deal (that is usually, a remedy having a gaggle of graphic world-wide-web parts) inside our SharePoint 2010 farm. We all deployed/updated the solution from the order “Update-SPSolution –Identity <SolutionName>. wsp –LiteralPath <Solution Location>\<SolutionName>. wsp –GACDeployment –force” inside the SharePoint 2010 Administration Shell. When we attempted for you to up-to-date the solution, many of us approved that it option wasn’t up-to-date. We all noticed that the deployment reputation inside the SharePoint 2010 Middle Government the Rank was generally “deploying”.


The problem can be related with one of the items bellow

  • Microsoft company SharePoint Groundwork Workflow Timer Assistance is just not managing
  • SharePoint Timer service is just not managing


To check on the execution on the service on the point 1:

  • Open the SharePoint Middle Government Portal
  • Go to Take care of services on server, underneath Program Settings
  • Authenticate in the event the service “Microsoft SharePoint Groundwork Workflow Timer Service” is usually managing. Or even, start it

How to Solve Stuck Deploying status in SharePoint 2010

To check on the execution on the service on the point 2:

  • Open the Glass windows Products and services window to confirm the services which might be managing inside the server
  • Find the “SharePoint 2010 Timer” service as well as examine if it is managing
    How to Solve Stuck Deploying status in SharePoint 20102
  • In the event the service is just not managing, wide open the order range immediate
    – Form the order “net start sptimerv4” to start out the service as well as click Type in
    – If you receive “The service failed to start because of a logon inability. ”, edit the “Log On” account to make sure that the service identity account is usually put together effectively you need to the service

Immediately after making sure every one of the services are generally managing, release again the service.

Best Recommended SharePoint 2013 Hosting

ASPHostPortal.com is Perfect, suitable hosting plan for a starter in SharePoint. ASPHostPortal the leading provider of Windows hosting and affordable SharePoint Hosting. ASPHostPortal proudly working to help grow the backbone of the Internet, the millions of individuals, families, micro-businesses, small business, and fledgling online businesses. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability

SharePoint 2013 Hosting :: Duplicate Web Part Issue in SharePoint 2013

Today for something regarding one of the new features of SharePoint 13. There is the new attribute “ReplaceContent=TRUE” for the <File> element in <Module>.

Until SharePoint 2010, whenever we reactivate the PageLayout feature (the feature that provisions the page layouts in a master page gallery), web parts that have been added to the page layout are duplicated on the new page and we do not have a very standard solution to resolve this problem except for writing a feature receiver and removing the duplicated web parts.

ahp banner sharepoint-01
In SharePoint 2013 is the new attribute “ReplaceContent=TRUE” of the <File> element and if we use this when provisioning the page layout it overrides the existing web parts on the page layouts. So whenever we create a new page from the given page layouts, web parts are not duplicated.

    <Elements xmlns="http://schemas.microsoft.com/sharepoint/">  
      <Module Name="MyPageLayouts" Url="_catalogs/masterpage" RootWebOnly="TRUE">  
        <File Path="MyPageLayouts\MyPageLayout.aspx" Url="MyPageLayouts.Intranet/MyPageLayout.aspx" Type="GhostableInLibrary" ReplaceContent="TRUE">       
    <!—- All our web parts goes here -->  

Have a look at the preceding example, I have set the ReplaceContent=”TRUE”. Because of this whenever I change, add or delete a web part in this elements.xml file and I need to reactivate the feature, the web parts on the page layouts are not duplicated but they do get overridden.

Other Usage example

I’ll like to share one more scenario related to this, I have a sandbox solution that I am deploying on Office 365. I was uploading my package file (.wsp) to the Solution Gallery and activating it. In my package I have one feature that is deploying my CSS file in the master page gallery since I do not have file system access. I had a change in CSS file, I did the change, packaged the solution, deactivated the solution first, uploaded it to the solution gallery and activated it. But my CSS changes are not reflected. Then I remembered the “ReplaceContent” attribute and I used it in the module element while provisioning the CSS file and wonder happened? It worked like a charm.

Feel free if you have some thoughts on this or please share your experience. Thanks :)

Best Recommended SharePoint 2013 Hosting


ASPHostPortal.com is Perfect, suitable hosting plan for a starter in SharePoint. ASPHostPortal  the leading provider of Windows hosting and affordable SharePoint Hosting. ASPHostPortal proudly working to help grow the backbone of the Internet, the millions of individuals, families, micro-businesses, small business, and fledgling online businesses. ASPHostPortal has ability to support the latest Microsoft and ASP.NET technology, such as: WebMatrix, WebDeploy, Visual Studio 2015, .NET 5/ASP.NET 4.5.2, ASP.NET MVC 6.0/5.2, Silverlight 6 and Visual Studio Lightswitch, ASPHostPortal guarantees the highest quality product, top security, and unshakeable reliability, carefully chose high-quality servers, networking, and infrastructure equipment to ensure the utmost reliability



46. Click on SharePoint 2013 Products ...  from all apps

SharePoint 2013 Hosting :: How To Insert Items Into a SharePoint Host Web List Using SharePoint Hosted APP

This article explains how to insert items into a SharePoint Host web list using SharePoint hosted APP.  I would like to share the code to insert items into a host web list using JavaScript.
Use the following JavaScript code to insert an Item:


var hostWebUrl;
var appWebUrl;
// This code runs when the DOM is ready and creates a context object which is needed to use the SharePoint object model
$(document).ready(function ()
hostWebUrl = decodeURIComponent(manageQueryStringParameter(‘SPHostUrl’));
appWebUrl = decodeURIComponent(manageQueryStringParameter(‘SPAppWebUrl’));
//Insert method
//This function is used to get the hostweb url
function manageQueryStringParameter(paramToRetrieve)
var params =
var strParams = “”;
for (var i = 0; i < params.length; i = i + 1)
var singleParam = params[i].split(“=”);
if (singleParam[0] == paramToRetrieve)
return singleParam[1];
//Insert List Item to SP host web
function InsertItemToList()
var ctx = new SP.ClientContext(appWebUrl);//Get the SharePoint Context object based upon the URL
var appCtxSite = new SP.AppContextSite(ctx, hostWebUrl);
var web = appCtxSite.get_web(); //Get the Site
var list = web.get_lists().getByTitle(listName); //Get the List based upon the Title
var listCreationInformation = new SP.ListItemCreationInformation(); //Object for creating Item in the List
var listItem = list.addItem(listCreationInformation);
listItem.set_item(“Title”, “Title1″);
listItem.update(); //Update the List Item
//Execute the batch Asynchronously
Function.createDelegate(this, success),
Function.createDelegate(this, fail)
function success()
alert(“Item added successfully”);
function fail(sender, args)
alert(‘Failed to get user name. Error:’ + args.get_message());

In the AppManifest.xml file provide write permission to the SiteCollection.


This article explored how to insert list items into a host web list from a SharePoint Hosted app using JavaScript.

SharePoint 2013 Hosting – ASPHostPortal.com :: Missing Server Side Dependencies

After an installation of SharePoint 2013 (upgrade or even if from bare metal), you may begin to see errors that state “Missing Server Site Dependencies” in which SharePoint says that there are [MissingWebPart] errors in the Administration Database.


One of the most common you will see is “[MissingWebPart] WebPart class [28c23aec-2537-68b3-43b6-845b13cea19f] is referenced [x] times in the database :

So you may wonder why Microsoft would do this to us? Turns out it is simply that certain features have not been installed yet (i.e. Services). So how do you determine what EXACTLY in the Web Part is causing the issue? Well you may have thought “I’ll just go to the content DB and look at the WebParts table” – aha – in 2013, you’ll find that table is gone (it is now called AllWebParts). Using a simple SQL Select you can get the title of the web part that’s missing.

Open up SQL Server Management Studio and open the database. Once there, expand the databases in the object explorer until you see the database names. Make a note of the SharePoint_AdminContent_<GUID> database (provided you have NOT renamed it). FYI – this applies to ANY content database; the Admin is to match the message above.

Now click New Query to create a new query window then enter the following SQL:

use [SharePoint_AdminContent_<GUID>]
select DirName,LeafName from dbo.AllDocs where id in
 (select tp_PageUrlID from dbo.AllWebParts where

Where ‘SharePoint_AdminContent_<GUID>‘ is your database name.

This query will return the results of the pages where the web parts were found – in the case of [28c23aec-2537-68b3-43b6-845b13cea19f], the query will show you that it’s the Search Web Parts found on the Search Administration pages:

2efbetnJust in case you can’t see the images, the query above returned “SearchAdministration.aspx” and “SearchFarmDashBoard.aspx”

Now you may ask, why not just select the Web Part from the AllWebParts table – that’s because it won’t tell you what it is, just the ID. For example:

USE [SharePoint_AdminContent_<GUID>]
select * from dbo.AllWebParts where

Simply returns the ID’s of pages that the Web Part is on. It won’t tell you the name. Now in the above example, it is pretty easy to see what is missing – the Search Service has not been created so the components are not installed yet.

To find something a little more obscure, once you’ve identified one of the pages the Web Part is on, you can use the old ?contents=1 at the end of the page URL to see the web parts on it.


SharePoint 2013 Hosting :: Migrate to OneDrive on Office 365 from Google Drive

So you’ve finally decided to jump straight into the deep end and move over to OneDrive I’m sure you’ve had the idea in the back of your head for quite some time. Google Drive was fine for the time being but the OneDrive’s added functionalities probably ended up getting the best of you. Yet one question remains: how do I proceed? This article will walk you through this procedure:

  1. Set up your source folder.
  2. Connect to the destination
  3. Choose files you want to migrate
  4. Easily migrate your files to OneDrive
Even though we was primarily designed for SharePoint to SharePoint migrations, it also supports importing from network drives, file shares and file systems.

Where do you start your OneDrive Migration?

The first step is to have the source set up correctly. Most Google Drive users already have a ‘mapped Goggle folder’ on their PC. If it is not the case, here is how to set one up:

You can simply download it to your machine by clicking on Download Google Drive located in the settings menu or from the Install on your machine icon on the left, depending on the version of Google Drive you are using.

Once you have clicked on the download button, the installer will be downloaded to your machine. Once the process is completed, you can simply open it so the installation can begin.

After Google Drive has been installed, enter your credentials to synchronize it with your account.

At that point, the Drive is completely configured. In your case, you will be able to use it just as another folder in your C: Drive (or the selected drive during the installation)


Start your Migration to OneDrive with Sharegate

The Import is a breeze, and connect to the desired destination site. Then, select the destination library or the location where you want to copy the content.


Hand pick the content you want to migrate

Once the destination has been chosen, simply select the desired content to be imported while keeping the original authors and timestamps. Simply Awesome.


A migration so simple, a child could do it

As you can see, it is a very simple process. The great thing is that any end user can run this operation as long as he has full control over the destination library.

image_4Finally, do not worry about your PowerShell script. I will gladly review it before you start your migration. I hope this will help you on your journey to the cloud!


SharePoint 2013 Hosting :: How to Migrate DocRead from SharePoint 2010 to SharePoint 2013

How to migrate DocRead from SharePoint 2010 to SharePoint 2013

If you are considering migrating your SharePoint Farm to SharePoint 2013 (from SharePoint 2010) then please read through this article for steps on how to achieve this. Before proceeding, it’s important that you read ‘migrating between editions’ to understand how this effects your licensing.

Preparing your SharePoint 2013 Farm :

It is important to know that we only support migrations that have followed Microsoft’s recommended approach.

Note: We don’t support migrations that have been completed using custom code, or by using 3rd party migration tools such as those offered by AvePoint and Metalogix.

If you do wish to use one of these approaches then it may still be possible to migrate your DocRead data but it would require one of our DocRead developers to work with you as a chargeable piece of work.

Before you start the migration :

Before you start the migration you will need to download the latest version of DocRead for both 2010 and 2013. It’s very important that you are migrating from the one version of DocRead to another with the same build number. (e.g “v2.5″). If you aren’t running the latest version of DocRead on SharePoint 2010 you will need to carry out an upgrade which is detailed in our Installation Guide. Once you have completed the upgrade – it’s important to test DocRead to ensure that it is still fully operational and working as expected on SharePoint 2010.

Migration Steps (Central Admin) :

  • Complete the build and testing of your new SharePoint 2013 Farm.
  • Install but do not configure the latest version of DocRead for SharePoint 2013 onto your new Farm. (you will also need a license key by this stage).
  • Install but do not configure the latest version of the DocRead Scheduler onto your new Farm.
  • Attach and upgrade all of the content databases that DocRead was used on previously (please refer to the Technet guide).
  • If you are using SharePoint Global Audiences with DocRead it’s also necessary migrate your User Profile Service App and Metadata Service App which is detailed here.
  • Once this is complete, please test that your Farm is operational and specifically ensure that the Site Collections, Webs, Libraries / Lists, Groups, Audiences and Documents now exist with the same content as they had for SharePoint 2010.

Do a full back-up your SharePoint 2013 Farm.

  • Back-up your 2010 DocRead database and restore it to the SQL Server that you will be using for production and make a note of the Database name and Server Name.
  • Navigate to Central Admin > Collaboris Settings > Database Settings and enter the ‘SQL Server’ and ‘Database Name’ that you noted in the step above. Click ‘Ok’
  • Navigate to Central Admin > Collaboris Settings > Licensing  and enter your license key and click ‘Add’. Click ‘Ok’
  • Navigate to Central Admin > Collaboris Settings > Global Settings and add all of the Web Applications that contain sites where DocRead is activate. (Please note, even if they appear to look the same, it’s important to remove all and the re-add them as the internal ID’s will differ). Click ‘Ok’.

Disable the following DocRead timer jobs by going to Central Admin > Monitoring > Review Job Definitions :

  • DocRead audiences synchronisation job
  • DocRead readership processing job
  • DocRead SharePoint synchronisation job
  • DocRead Worker job
  • DocSurvey Stats Job (optional)
  • Migration Steps (Site Collection)
  • That’s all you need to do in Central Admin for now. The next phase is deactivate and uninstall the old 2010 Features and activate the new 2013 Features.
  • You can download the ‘upgrade Powershell script from here.
  • Once downloaded, open Powershell script with Notepad and edit the Datasource, Database (DocRead database) and user credential (if required).

Save the updates

  • Execute the Powershell script file (click right mouse button and select ‘Run with Powershell’.
  • IMPORTANT: The script only reactivates DocRead basic features. If any additional features were activated before you should reactivate them manually.
  • Post Migration Steps (Central Admin) :
  • Perform an IISReset on all of your machines in the production Farm.
  • Restart the SharePoint Timer job on all machines in the production Farm (see step 12 above for a list).
  • Perform a “Process Reading Tasks” in each DocRead enabled web and ensure that all the tasks are a present as before.
  • Configure the DocRead Scheduler as specified in the Installation Guide.
  • Scheduler a regular backup of the DocRead database.