SharePoint Online Software Boundaries and Limits

Size limit and Number of items that can be synced

1.     You can sync up to 20,000 items in your One Drive for Business library. This includes folders and files.

2.   You can sync up to 5,000 items in a SharePoint library. This includes folders and files. These are the libraries that you find on various SharePoint sites, such as team sites and community sites. This also includes syncing other people's One Drive personal sites that you may have access to. You can sync multiple SharePoint libraries.

3.     In any SharePoint library, you can sync files of up to 2 GB

Character limit for files and folders

1. In SharePoint Online, file names can have up to 256 characters
2. Folder names can have up to 250 characters
3. When you sync One Drive for Business with SharePoint Online, a folder named "forms" isn't supported at the root level for a list or library. This occurs because "forms" is a hidden default folder that's used to store templates and forms for the library.
4. Any file that’s currently open by an application (for example, an Excel .xlsx file) can't be synced by One Drive for Business.
5. To sync the file, close any application where the file is currently being used, and then sync the file.
6. The following characters in file names aren't supported when you sync One Drive for Business with SharePoint Online: (\, /, :, *, ?, “, <, >, |, #, %, ~)

SharePoint Online Site Collection

1. SharePoint Online Site collection package details below:

• Small Business: a single Team Site Collection
• Midsize Business plans: limits 20 Team Site Collections
• Enterprise, Education, and Government: limits to 10,000 Team Site Collections

2. In all options, just single Public Web Site Collection can be created, 1TB for My sites, 2000 site/sub site per site collection

Developer Limits

Only Sandbox Solutions are designed to allow SharePoint developer to customize/develop on Office365/SharePoint Online

• No access to file/folder. It means you cannot use IO API commands
• Only be deployed at a site collection level scope (not farm scope)
• No access to web.config
• PDF Documents cannot be opened in the browser
• Restrictions to access security
• Cannot overuse system resources

Storage

The following table describes the limits for SharePoint Online in Office 365 Business Essentials and Office 365 Business Premium:

Feature	Description
Storage per user (contributes to total storage base of tenant)	500 megabytes (MB) per subscribed user
Storage base per tenant	10 GB + 500 MB per subscribed user + additional storage purchased For example, if you have 10,000 users, the base storage allocation is approximately 5 TB (10 GB + 500 MB * 10,000 users) You can purchase an unlimited amount of additional storage
Site collection storage limit	Up to 1 TB per site collection. (25 GB for trial). SharePoint admins can set storage limits for site collections and sites. The minimum storage allocation per site collection is 100 MB
List view threshold limit in site libraries, including files and folders	You can sync up to 5,000 items in site libraries, including folders and files
Site collections (#) per tenant	500,000 site collections (other than personal sites)
Sub sites	Up to 2,000 sub sites per site collection
File upload limit	2 GB per file
Number of external user’s invitees	There is no limit to number of external users you can invite to your SharePoint Online Site Collections

Read More

Could not load type ‘Microsoft.AnalysisServices.SpAddin.ReportGallery.ReportGalleryView’

Recently, I have installed the power pivot in SharePoint 2013 and then configured the power pivot service application in the Central Administration.

I tried creating a Pivot Gallery and it is successful. When I opened the pivot gallery library, it is showing the below error: 

I am sure some feature is not activated but couldn’t find it. Then, checked the Central Administration -> System Settings -> Manage Farm Solutions -> powerpivotwebapplicationsolution

This solution should be deployed to the web application in which have created the pivot gallery.

Happy learning! Please share this post if it helps you!

Read More

SharePoint 2013 / Office 365

I wanted to try some proof of concepts using SharePoint 2013 and been looking for various easy options to get the SP 2013.
Hence I wanted to list the easy ways to get SharePoint 2013 for the readers. Below is the list:

Office 365 Trial :

https://products.office.com/en-us/business/compare-office-365-for-business-plans

On-Premises Deployment:

https://www.microsoft.com/en-us/evalcenter/evaluate-sharepoint-server-2013

Windows Azure:

https://azure.microsoft.com/en-us/pricing/free-trial/?CR_CC=200256621&WT.mc_id=A24158309 

SharePoint Online:

https://products.office.com/en-us/SharePoint/compare-sharepoint-plans?legRedir=true&CorrelationId=08d4bcac-2e4e-4269-9981-1deb00da1ad9

SharePoint Rackspace:

http://sharepoint.rackspace.com/free-sharepoint-2013#chat 

Cloud Share:

http://www.cloudshare.com/cloudshare-template-library

This are the some of the easier ways to get the trial versions for SharePoint 2013. Please share this post if this is helpful. Happy Sharing!

Read More

OWA web parts in SharePoint 2013

When I tried finding the OWA web parts in the SharePoint 2013 OOTB web parts, I couldn't find the web parts and “Outlook Web App” category is also not available. I was thinking it is deprecated or not available in SharePoint 

2013.

After searching, I found the following solution.

Steps to add Outlook web parts

1.   Go to Web part Gallery.

2.   On Web part Gallery page, Click Files-> New Document -> New in the ribbon.

 3.   On New web part page (NewDWp.aspx), look for Microsoft.SharePoint.Portal.WebControls.OWA, select the web parts related to the outlook as shown below and populate gallery.

4.   Now, under Miscellaneous Category, you will see the web parts related to Outlook. 

Hope this helps you!

Read More

Site Administration in SharePoint 2013

In this article, we will have know how does Site Administration in SharePoint 2013 looks. Here is the screenshot of SharePoint 2013 site administration.

Read More

The Server could not complete your request SharePoint Designer 2013

Problem:

When I tried opening SharePoint 2013 site in SharePoint Designer, I got the following error:

When I clicked on Details, it opened another dialog and continuously pop up window is opening and not able to open the SharePoint site.

 Finally got an error message

Solution:

    1.   Go to Run -> type Inetmgr -> Open the IIS

    2.   In the Web Sites select “SharePoint Web Services” in the list

    3.   Click on the Authentication and Enable “Anonymous Authentication” as shown below:

   4.   After enabling this, I am able to open the SharePoint site in designer without any issues

Reason for the issue: Check this article http://support.microsoft.com/kb/2758431 

Read More

News feeds not working in SharePoint 2013 - microsoft.office.server.microfeed.microfeedexception

To know about Micro Blogging in SharePoint 2013, read this post.

When I tried to use the News Feed Feature in SharePoint 2013, it thrown exception:

microsoft.office.server.microfeed.microfeedexception

The below is the screenshot: 

 Solution:

As I mentioned in the earlier post about Micro blogging in SharePoint 2013, news feeds are related to User Profile Service.

Hence, we have to check two things which are related to User Profile Service in SharePoint 2013.

    1.   Check whether AppFabric Caching service is running with the service account which has elevated permissions. 

   2.   Next, check the account which is running the User Profile Service application:

     Open Central Administration -> Mange Service Applications -> User Profile S    Service is started and also check the permissions for the service

    

   Click on the User Profile service and in the permission section in the ribbon check whether the service account running this service has full control. 

 If all the above scenarios are properly configured in SharePoint farm, then the news feed will work properly as expected.

Feel free to comment and share this post if this helps you.

Read More

Migrate SharePoint 2010 to 2013

In this article, we will learn how to migrate SharePoint 2010 to SharePoint 2013. This migration is applicable for OOTB features migration not for Custom Solution migration to SharePoint 2013.

Steps:

      1. Change the Authentication mode of SharePoint 2010 application to Claims using the PowerShell command

$WebAppName = ""
$account = ""
$wa = get-SPWebApplication $WebAppName
Set-SPwebApplication $wa –AuthenticationProvider (NewSPAuthenticationProvider) –Zone Default

2.   We have to take the backup of solutions (WSP) from SP 2010 and deploy it in the SP 2013 farm. Use the following PowerShell command to back up the WSP

$farm = Get-SPFarm
$file = $farm.Solutions.Item("Backup.wsp").SolutionFile
$file.SaveAs("C:\Backup.wsp")

3.   Now, deploy the solution to the SP 2013 farm using the following command:

Add-SPSolution -LiteralPath "C:\Backup.wsp" 

(rebuilding the solution in Visual Studio 2012 is required sometimes)

     4.  Now take the backup of Content DB from SP 2010 and attach in SP 2013 database server

Note: This will automatically update the DB schema for SQL server 2012 (which is previously lower version in SP 2010)

    5.   Create a new web application in SP 2013 and after creating the web application detach the Content DB (which is newly created for SP 2013 now)

    6.   Now, attach the backup Content DB (taken from SP 2010) using the following command

Mount-SPContentDatabase -name -WebApplication 

Note: This will automatically update the Dictionary and other required update for SP 2013.

    7.   Now deploy the List templates and other backups from SP 2010 if required.

Note: This is applicable only for OOTB solutions. If you have custom solutions, then you have to re-build the code using Visual Studio 2012 and then deploy the solution.

Hope this helps you and please free to comment and share this post.

Read More

Audit Logging in SharePoint 2013

Audit Logging gives the following information in Site Collection:

1. Opening or downloading documents, viewing items in lists, or viewing item properties
2. Editing items
3. Checking out or checking in items
4. Moving or copying items to another location in the site
5. Deleting or restoring items
6. Editing content types and columns
7. Searching site content
8. Editing users and permissions

Below are the steps to achieve:                                                                 

       1. Go to Central Administration -> Manage Service Applications

    2. Choose Secure Store Service 
 

    3. Then Click on the Properties in the Ribbon

4. In the Enable Audit option Select the Check Box Audit Log Enabled (the default value is 30 days and it can be changed)

5. After enabling the Audit Logging in Central Administration, we have to configure the audit settings at the site collection level and below are the steps:

Go to Site Settings -> Site Collection Administration -> Site Collection Audit Settings 

Under this settings, select the settings as shown below:

 Now, Audit Logging is configured for the site and now you can view the following types of Reports.

Checking the Reports Generated for the Site Collection
Go to Site Collection Administration -> Audit Log Reports

Once you click on any reports, it will ask for the Report Save location. Select any of the Libraries to store the Report.

Example Report Generated Screenshot:

 

 Select an Library to store the Report and Click OK

Report Generated in Excel

Hope this article helps you in understanding the Audit Logging in SharePoint 2013. Please feel free to share and comment about this post if it helps you.

Read More

Unexpected error occurred while communicating with Administration Service

Scenario:

I ran into the following issue when attempting to access  Fast search features such as:

1. FAST Search keywords

2. Fast Search site promotion and demotion

3. Fast search user context

Solution:

I checked my Administrators group in the SP server. Fast Search ADMIN account configured is added in the Administrators group. Though I am unable to access these features.

Then found the resolution from a TechNet article.

1.   Create a group named FASTSearchKeywordAdministrators in the SP server (this group is not automatically created during default installation).

2.   Add the Fast Search ADMIN account (account configured for fast search) to this group.

Then tried accessing the features and everything works as expected.

Read More

Sign in as different user in SharePoint 2013

In all the versions of SharePoint, we have option for signing in as different user which helps us in various scenarios. Also, it helps in testing purposes.
But in SharePoint 2013, we do not have this option. 

In this article we will know how to achieve this:

1. When you log in to a SharePoint site, you don't have sign in as different user option which is shown as below:

2. To overcome this limitation either we have to sign in to the IE as different user and then we can log in to the SharePoint site as different user.
3. To achieve this in SharePoint (which is like option in older versions of SharePoint), we need to modify the welcome.ascx which is present in the 15 hive of SharePoint server.
4. Navigate to the below path and find the welcom.ascx file.
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\CONTROLTEMPLATES
5. Open the file in the visual studio or in the notepad and add the following code above the tag which has ID_RequestAcess as shown below:

<SharePoint:MenuItemTemplate runat="server" ID="ID_LoginAsDifferentUser" Text="<%$Resources:wss,personalactions_loginasdifferentuser%>"

Description="<%$Resources:wss,personalactions_loginasdifferentuserdescription%>"

MenuGroupId="100"

Sequence="100"

UseShortId="true"

/>

 6. Save the file and now refresh the site, you will see the SharePoint page with option "Sign in as different user" option as shown below:

 Hope this helps you. Please free to comment. It helps me to write more.

Read More

SharePoint 2013 Installation Steps

We will explore more on SP 2013 in our blog in the forthcoming posts. So, we will start with Installing SP 2013. 

You will have step by step screenshot for installing SP 2013 in the below document:

Happy Configuring!

Read More

The feature being activated is a Site scoped feature which has a dependency on a Site Collection scoped feature which has not been activated. Please activate the following feature before trying again: SharePoint Server Publishing Infrastructure f6924d36-2fa8-4f0b-b16d-06b7250180fa

Some times while activating the Publishing feature in SharePoint through the options in Site Settings we will get this error:
The feature being activated is a Site scoped feature which has a dependency on a Site Collection scoped feature which has not been activated. Please activate the following feature before trying again: SharePoint Server Publishing Infrastructure f6924d36-2fa8-4f0b-b16d-06b7250180fa

Reason:

The reason being the "SharePoint Server Publishing Infrastructure" feature has to be enabled at SITE COLLECTION level, then it has to be activated at SITE LEVEL enable the feature. So that we can create Publishing pages in SharePoint.

Solution:
It can be done in many ways (2 ways mentioned below):
1. We can use the Site Settings -> Site Collection Administration -> Site Collection Features to enable this feature.
2. Then Site Settings -> Site Administration -> Site Features -> Enable this feature.
3. We can also achieve this using STSADM command as shown below:

STSADM.EXE -o deactivatefeature -id f6924d36-2fa8-4f0b-b16d-06b7250180fa -url "http://SiteURLHere/" -force

Then,

STSADM.EXE -o activatefeature -id f6924d36-2fa8-4f0b-b16d-06b7250180fa -url "SiteURLHere" -force

Hope this helps you!

Read More

Export SharePoint Group to Excel using PowerShell

$siteUrl="SiteURLHere"
$groupName="GroupNametoExport"
$Output = @("GroupName|Name|Login|Email|Department|Title")
$web = Get-SPWeb $siteUrl
$site = $web.Site
$rootWeb = $site.RootWeb
$UserList = $rootWeb.Lists["User Information List"]
$web.SiteGroups[$groupName].Users|%{$user = $UserList.GetItemById($_.ID)
if($user -ne $null)
{
$JobTitle = $user["JobTitle"]
$Department = $user["Department"]
}
$Output += ($groupName+"|"+$_.Name+"|"+$_.UserLogin+"|"+$_.Email+"|"+$ Department +"|"+$JobTitle)
}
$rootWeb.Dispose()
$web.Dispose()
$site.Dispose()
$Output > "D:\MembersExport.csv"

Read More

Import Excel to SharePoint List using PowerShell

# Import the .csv file, and specify manually the headers, without column name in the file 
$contents = Import-CSV ‘C:\Input.csv' -header("Employee ID", "Employee Name")
# Web URL
$webURL = “SITEURL here”
$web = Get-SPWeb -Identity $webURL
$listName = "ListNameHere"
$list= $web.Lists["$listName"] 
# Iterate for each list column
foreach ($row in $contents )
{
    $item = $list.Items.Add();
    $item["Employee ID"] = $row.GroupName
    $item["Employee Name"] = $row.Permissions
    $item.Update()
}
Write-Host -ForegroundColor green "List Updated Successfully"
$web.Dispose()

Read More

Import Users from Excel to SharePoint using PowerShell

# Import the .csv file, and specify manually the headers, without column name in the file 
$userList=IMPORT-CSV C:\UserToUpload.csv -header("GroupName","UserName")

#Get the site name to the variable
$web = Get-SPWeb SiteURLHere

foreach ($user in $userList)
{
$groupName = $web.SiteGroups[$userList.group]
$user = $web.Site.RootWeb.EnsureUser($userList.user)
$groupName.AddUser($user)
}
Write-Host -ForegroundColor green "Users Added Successfully"
}
$Web.Dispose()

Read More

Add Users to SharePoint Group using PowerShell

#Get the site name to the variable
$web = Get-SPWeb SitURLHere
#Get the group name to the variable
$groupName = $web.SiteGroups["Group Name Here"]
#Assign user to variable
$user = $web.Site.RootWeb.EnsureUser(“User ID Here”)
#Add user to group 
$groupName.AddUser($user)
Write-Host -ForegroundColor green "User Added Successfully";

Read More

Create Site Collection in Separate Content Database in SharePoint

Problem:

When a “Site Collection” is created in a web application, then the proceeding Site Collections created in the same “Web Application” will use the Same Content DB.

This creates problems in the following scenarios:

1. Size of the one Site Collection grows large then it will affect the other Site Collection too. The
reason being maximum size of a Content DB for a Site Collection with good performance is 200 GB
(referred some MSDN articles).

2.  During migration/archival/splitting of content DB.

Solution:

The solution for the above problem is to “Create Site Collections with Separate Content DB for each Site Collection”.

But by default SharePoint allows you to create new site collections in the Same Content DB which is used by the web application (one created first – Top Level Site Collection)

Using Central Administration page:

1.   Suppose that we have created a Top Level Site Collection with content DB named “WSS_Content_1000”. Now our scenario is to create a new site collection in the same web application with different content db.

2. Now navigate to Central Admin -> Application Management -> SharePoint Web Application Management -> Content databases

3. By using the option Add a content database in the menu, create a new content DB named “WSS_Content_1050”

 6. Now, you can see the database (WSS_Content_1000) in the stopped state: 

 7. Now, try creating a new Site Collection in the same web application. “Your new site collection will be forced to create in the Content DB which is available in the web application” (in our case it is WSS_Content_1050).

8. Now, change the status of the first content db to Ready state.

9. Now to check whether our new site collection is created in different db’s go to Central Administration -> Application management -> Site collection list. “You can see two site collections in two different databases” as shown below:

     ØTop level site collection created in WSS_Content_1000 db

     ØTop level site collection created in WSS_Content_1050 db

10. As shown in the above screenshot, we are able to create a new site collection with a new Content DB using the above method.

Read More