SkyDrive Pro increases storage

SkyDrive Pro increases storage and ease of sharing http://blogs.office.com/b/office365tech/archive/2013/08/27/skydrive-pro-increases-storage-and-ease-of-sharing.aspx

#Each user now gets 25 GB of SkyDrive Pro storage space (up from 7 GB).

#You can now increase users' SkyDrive Pro storage beyond the default 25 GB-up to 50 GB and 100 GB.

#With the new Shared with Me view, you can easily find documents others have shared with you.

SharePoint 2013 development environments

Create SharePoint 2013 development environments quickly on Azure http://blogs.msdn.com/b/sharepointdev/archive/2013/09/26/create-sharepoint-2013-development-environments-quickly-on-azure.aspx

this article talks about setting up Azure VMs for SharePoint development. All you would need is an MSDN subscription, and you could potentially leverage more than just this specific developer image explained in the article.

October 2013 Cumulative Update Packages

October 2013 Cumulative Update Packages for SharePoint Foundation 2013 and SharePoint Server 2013 have been released

October 2013 CU for SharePoint Foundation 2013 - KB 2825674 http://support.microsoft.com/kb/2825674

October 2013 CU for SharePoint Server 2013 - KB 2825647 http://support.microsoft.com/kb/2825647

Note: This is build 15.0.4551.1001 of the cumulative update package.

The named item cannot be displayed

Before we start troubleshooting on this, let’s try to understand the term-

What is meant by name item? - In this view, you can only display one or more named items in the workbook. A named item can be one of the following:

1)      A chart

2)      An Excel table

3)      A PivotTable report

4)      A PivotChart report

5)      Named range of cells.

How I encountered this error? – I have added an excel web access web part on my SharePoint site collection, modify the webpart and entered the details for workbook location and name item field by specifying tab7 inside the excel spreadsheet as I don’t want to display my spreadsheet in the EWA.

As soon as I clicked ok, the excel web access webpart throws an exception as follows:

The named item cannot be displayed. The name item is either not available in the workbook or was not selected as a name item for viewing when the workbook was published. The name item may also be located in a hidden range of cells or in a collapsed outline.

Action taken / troubleshooting done:

1.       Checked the status of excel service application and it was fine

2.       Checked the excel service status by means of Central Administration- services on server and it was fine too.

3.       Need to isolate the problem first- whether its farm specific or file specific or EWA web part specific.

4.       Checked the document library where all the excel documents were stored. Clicked on the dropdown of any excel file and selected ‘view in browser’ – it opens up fine!

5.       Came back to the excel web access webpart- modify it and remove the name item field and kept it blank – click apply & checked the results

6.       With the above action- the excel web access web part loads the excel file without any problems.

7.       So far so good! Still trying to find out the resolution!

Resolution:-

Change Published Items within a Workbook: -

When we initially published our workbook to Excel Services, we simply gave it a name and accepted the default values. Whenever we click the Save icon, rather than re-publishing the workbook, we’re merely saving the data back to the document library. The significance here is that when publishing a workbook to Excel Services, we have the option of specifying additional metadata, but when saving, the metadata is not changed. We received the error because the metadata did not contain details of our new named item.

1.       Open the excel file on your desktop (not from the SharePoint site, if you don’t have saved on the desktop then please save it.)

2.       On the top ribbon- click on File

3.       Click on Share

4.       Publish to Excel Services

5.       Current location

6.       Save as - automatically displays the contents of our Excel Workbooks document library

7.       Click Publish to Excel services to open the save as dialogue

8.       Excel Services Options button now appears in the bottom

9.       Excel Service Options button

10.   Here we need to define or overwrite metadata for the document

11.   In the Excel Services Options dialog’s Show tab, select Items In The Workbook from the drop-down list.

12.   Check the All Named Ranges and the All Charts options to ensure that they will be available for use by the EWA web part

13.   Click Save to complete the publishing process

That’s it- You are done!

Make the necessary changes inside the excel web access (EWA) and check the results.

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

The workbook cannot be opened - SharePoint 2013

I have configured the excel services in my environment perfectly by using Microsoft recommended articles but while testing, i have added the excel file inside excel web access webpart to check as the functionality is properly working or not but boom – as soon as the page loads – it throws an exception.

The workbook cannot be opened.

 

This problem can be occurring mainly because of two reasons:-

1)      Custom security settings

2)      Addition of new web application to the farm.

One thing we need to make sure – whenever we add any web application then make sure the proxy settings/connections should be default one. Other way will be- You need to manually check the excel service application proxy to make sure that the new web application is already a part of the existing set.

How to do this:-

1.       SharePoint 2013 Central Administration

2.       Application management

3.       Configure service application associations

4.       Ensure the excel service application check box is tick with respect to that new web application

So far so good! – If still the error persists then I would recommend you to check the SharePoint logs to get the clarity on the exact root cause.

Regarding my case, I did the same and figured it out that it’s a permission issue. Let me tell you one thing very confidently those 9 out of 10 cases are based on permissions issue only.

So how to resolve this? Let me guide you step by step so that there would be no confusion.

Resolution:-

1)      Go to any of your SharePoint 2013 Server

2)      Start

3)      All programs

4)      SharePoint 2013 products

5)      SharePoint 2013 management Shell

6)      Make sure you run this console as “Administrator”

7)      Execute the following commands

$webApp = Get-SPWebApplication "WebApplication URL"

$webApp.GrantAccessToProcessIdentity("Excel Service Account Name")

What you need to change in this –

Web application URL - Please enter the web application URL where you are facing the problem.

Note: this is not a site collection URL but root URL underneath your site exist.

Example: http://sharepointgalaxy.com/sites/sharepoint2013

If you look at the above URL then here is the isolation:

http://sharepointgalaxy – web application URL

/sites – wildcard variable

/sharepoint2013- site collection name

Second change you need to do inside the PowerShell command is:

Excel service account name – this should be in the format domain name/excelserviceaccname

Now the question is – how to find out this excel service account name?

1)      Central Administration

2)      Security

3)      Configure service accounts

4)      Click on the dropdown

5)      Select the excel service account which is running the excel service application

That’s it- you are done! In case of any queries/questions then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

SharePoint 2013 - Trusted file location Error

As working in the support industry, we use to get lot of tickets on daily basis so out of that we get one ticket today which was based on excel web part error-

You do not have permissions to open this file on Excel Services. Make sure that the file is in an Excel Services trusted location and that you have access to the file.

From the above error message, it seems very clear to the SharePoint Administrators/IT experts who are handling the SharePoint environments/providing support to the SharePoint Infrastructure.

Let me explain the resolution step by step so that they would be no confusion but still in case of any queries/questions then please feel free to contact me so that I can resolve your issue / guide you in appropriate directions.  Thank you.

Resolution:-

1.       Open the SharePoint 2013 central administration

2.       Application management

3.       Manage service applications

4.       Excel services service application

5.       Click on it

6.       It will open ‘manage excel services application page’

7.       Click on trusted file locations

8.       Add trusted file location

9.       Inside the Address filed, enter the document library URL where the excel documents are stored

10.   Select children trusted

11.   Keep all the other values as it if you don’t have any specific requirements

12.   Click OK

That’s it- You are done! – Go back to your page where the excel web access webpart was throwing the error, refresh the page and check the results!

Thank you.  Happy SharePoint to all of you

create site + delete site - SharePoint 2013

Site collection is a very important part by which you actually started building the whole house. Creation of list, libraries, record center, management, usage analysis, reports & so many things- bottom line is you need a site collection. When you create a site collection then its requirement proper management also which involves permissions part (not going to discuss in this article but FYI) so let’s start!

In this article, we will concentrate on site collection guidelines:

·         Site creation by GUI as well as by PowerShell

·         Site Deletion by GUI as well as by PowerShell

Site collection will already be created underneath the web application and there can be so many site collections present in a single web app. So site collections can be created by two ways-

1)       GUI i.e. Central Administration

2)       Command prompt i.e. PowerShell

Let’s try to understand step by step each section in detail-

Create site collection by using – Central Administration

1)       SharePoint 2013 Central Administration

2)       Application management

3)       Create site collections

4)       Select the appropriate web application from the top dropdown underneath you want to create the site collection

5)       Provide title, description ,URL and template selection as per your requirements

6)       Provide the names for primary and secondary site admins as per your requirements

7)       Apply appropriate quota

8)       Click OK

9)       Site collection will be created.

10)   That’s it- you are done!

Create site collection by using – PowerShell

New-SPSite -Url "<URL for the new site collection>" -OwnerAlias "<domain\user>" -Template $template

As we have understood the creation part, let’s try to understand the site deletion part by using the same ways-

1.       Site deletion by Central Administration.

2.       Site deletion by PowerShell.

Site Deletion by using – Central Administration

1.       SharePoint 2013 Central Administration

2.       Application management

3.       Delete site collections

4.       Select the appropriate web application from the top dropdown underneath you want to delete the site collection

5.       Select the appropriate site collection

6.       Click OK

7.       Read the warning

8.       On the delete site page

9.       Click on Delete

Site deletion by using PowerShell

Remove-SPSite -Identity "<URL>" –GradualDelete

Where-

·         URL stands- URL of the site collection

·         Gradualdelete-reduces the load on the system.

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Blocked file types for SharePoint Online + SharePoint 2013

SharePoint Online / Office 365

Extensions	File types
.ashx	ASP.NET Web handler file.
.asmx	ASP.NET Web Services source file
.asp	Active Server Pages
.aspq	Active Server Pages
.axd	ASP.NET source file
.cshtm	ASP.NET web page
.chtml	ASP.NET web page
.json	JavaScript Object Notation file
.rem	Blackberry Encrypted Data file
.shtm	HTML file that contains server-side directives
.shtml	HTML file that contains server-side directives
.soap	Simple Object Access Protocol file
.stm	HTML file that contains server-side directives
.svc	Windows Communication Foundation (WCF) service file
.vbhtm	ASP.NET Razor web page
.vbhtml	ASP.NET Razor web page
.xamlx	Visual Studio Workflow service file

SharePoint 2013 Blocked file types:

Extensions	File types
.ade	Microsoft Access project extension
.adp	Microsoft Access project
.asa	ASP declarations file
.ashx	ASP.NET Web handler file.
.asmx	ASP.NET Web Services source file
.asp	Active Server Pages
.bas	Microsoft Visual Basic class module
.bat	Batch file
.cdx	Compound index
.cer	Certificate file
.chm	Compiled HTML Help file
.class	Java class file
.cmd	Microsoft Windows NT command script
.com	Microsoft MS-DOS program
.config	Configuration file
.cnt	Help Contents file
.cpl	Control Panel extension
.crt	Security certificate
.csh	Script file
.der	DER Certificate file
.dll	Windows dynamic-link library
.exe	Executable file
.fxp	Microsoft Visual FoxPro compiled program
.gadget	Windows Gadget
.grp	SmarterMail group file
.hlp	Help file
.hpj	Hemera Photo Objects Image File
.hta	HTML program
.htr	Script file
.htw	HTML document
.ida	Internet Information Services file
.idc	Internet database connector file
.idq	Internet data query file
.ins	Internet Naming Service
.isp	Internet Communication settings
.its	Internet Document Set file
.jse	JScript Encoded script file
.json	JavaScript Object Notation file
.ksh	Korn Shell script file
.lnk	Shortcut
.mad	Shortcut
.maf	Shortcut
.mag	Shortcut
.mam	Shortcut
.maq	Shortcut
.mar	Shortcut
.mas	Microsoft Access stored procedure
.mat	Shortcut
.mau	Shortcut
.mav	Shortcut
.maw	Shortcut
.mcf	Multimedia Container Format
.mda	Microsoft Access add-in program
.mdb	Microsoft Access program
.mde	Microsoft Access MDE database
.mdt	Microsoft Access data file
.mdw	Microsoft Access workgroup
.mdz	Microsoft Access wizard program
.ms-one-stub	Microsoft OneNote stub
.msc	Microsoft Common Console document
.msh	Microsoft Agent script helper
.msh1	Microsoft Agent script helper
.msh1xml	Microsoft Agent script helper
.msh2	Microsoft Agent script helper
.msh2xml	Microsoft Agent script helper
.mshxml	Microsoft Agent script helper
.msi	Microsoft Windows Installer package
.msp	Windows Installer update package file
.mst	Visual Test source files
.ops	Microsoft Office profile settings file
.pcd	Photo CD image or Microsoft Visual Test compiled script
.pif	Shortcut to MS-DOS program
.pl
.prf	System file
.prg	Program source file
.printer	Printer file
.ps1	Windows PowerShell Cmdlet file
.ps1xml	Windows PowerShell Display configuration file
.ps2	Windows PowerShell Cmdlet file
.ps2xml	Windows PowerShell Display configuration file
.psc1	Windows PowerShell Console file
.psc2	Windows PowerShell Console file
.pst	Microsoft Outlook personal folder file
.reg	Registration entries
.rem	ACT! database maintenance file
.scf	Windows Explorer command file
.scr	Screen saver
.sct	Script file
.shb	Windows shortcut
.shs	Shell Scrap object
.shtm	HTML file that contains server-side directives
.shtml	HTML file that contains server-side directives
.soap	Simple Object Access Protocol file
.stm	HTML file that contains server-side directives
.svc	Windows Communication Foundation (WCF) service file
.url	Uniform Resource Locator (Internet shortcut)
.vb	Microsoft Visual Basic Scripting Edition (VBScript) file
.vbe	VBScript Encoded Script file
.vbs	VBScript file
.vsix	Visual Studio Extension
.ws	Windows Script file
.wsc	Windows Script Component
.wsf	Windows Script file
.wsh	Windows Script Host settings file
.xamlx	Visual Studio Workflow service file