SharePoint 2013: Excel web access web part Errors and Resolutions


If you have recently migrated from SharePoint 2010 to SharePoint 2013 or if you are configuring excel web access web part for SharePoint 2013 with named component, you might notice that you Excel web access web parts are showing some error or not showing any data even after you add your excel file location to Trusted locations in excel service application.

There are multiple reasons behind this behavior of excel web access web part.
  1. If you are getting error "Workbook cannot be opened" as shown in below image, It is related to permissions to the service account used for Excel services. As all your excel files are stored in Content DB, service account used for Excel service should be having access to all respective web applications.



You can use following cmdlets to get this issue resolved

$webApplication = Get-SPWebApplication –Identity <URL of the Web application>
$webApplication.GrantAccessToProcessIdentity("<insert service account>")

You have to perform this action for all your web applications using excel web access web parts
  1. You see the error "We're sorry, we couldn't open your workbook. It is possibly corrupt or using a file format that's not supported. Do you want to try and open this file in excel?" as shown in below image.



This error is very miss leading at times. There are chances that your excel file is corrupt but you better be sure about this.
To verify
  1. Download the file to local system and open it in excel. If it does not open correctly then you can say it is  corrupt and need to be changed.
  2.  If it opens correctly then nothing is wrong with file, you have to check for other resolution.

In case "b" it might be the fact that you have not started Excel web service on all your web front end servers. Once you start the excel web service on all your web front end servers. This issue will be gone.


  1. After getting rid off above issues, you notice nothing is coming up in excel web part not even error. It is showing sort of blank. This could happen to the web part if you are running RTM build for SharePoint 2013. If you have configured the excel web access web part with "Named component" you will get this error in SharePoint 2013 RTM. This is a known issue and is resolved in March 2013 PU for SharePoint 2013.

Comments

Post a Comment

Popular posts from this blog

Clearing the Configuration Cache for SharePoint

Clearing the Configuration Cache for SharePoint Perform the below steps on all the servers in the farm. 1. Stop the Timer service Start  ->  services.msc  ->   SharePoint Timer Service  (SPTimerV4) ->  Stop 2. Browse to  %SystemDrive%\ProgramData\Microsoft\SharePoint\Config\GUID Note: The  Program Data  folder is a hidden file There could be more than 2 folders in this location. 3. Open the folder named as GUID’s with ‘-’ (dashed filename for the folder). Example -  1f8c67d2-2cd9-4196-ab1a-d1a2daed2aa7 4. Arrange the files by Type. You would find few xml files and a file named  cache.ini . 5. Delete all files except cache.ini (DO NOT DELETE THIS FILE - cache.ini) 6. Reset cache.ini (If you open this file, you will find a number like this – 3400261. Change the value in cache.ini to 1) 7. Start the Timer service Start  ->  services.msc  ->   SharePoint Timer Service  (SPTimerV4) ->  Start. 8. Note: The file system cache
Read more

SharePoint 2013 REST API CRUD Operations

Image
Introduction  SharePoint   2013 has greatly expanded the REST services available to developers. With this, we have much more SharePoint functionality exposed via JSOM and Web Services .  The goal of this article is to provide how to perform basic create, read, update, and delete (CRUD) operations on lists and list items with the REST services. SharePoint REST endpoint Overview: The following table contains typical REST endpoint URL examples to get you started working with SharePoint data. Prepend http://server/site/_api/ to the URL fragments shown in the table to construct a fully qualified REST URL. Below is a list of the basic commands used to get List Items from a SharePoint List through the SharePoint 2013 REST Services. URL endpoint Description Supported HTTP Method /_api/Web/Lists/ getbytitle('listname') Getting a list details by its title and updating it as well. Ifanyone changes your list title, your code will break. G
Read more

Add List Item Attachments to Task Form using Nintex Workflow and Forms

Image
DECEMBER 19, 2017  ~  NICOLE PRESTBY I had a requirement from a client recently to show all list item attachments on the various task forms in an approval process – which, if you think about it, makes total sense. With any project, we always have a common goal of making the user experience as seamless as possible for our users and approvers. So, why wouldn’t we provide all pertinent information needed (including related documents) to complete the requested review and approval, right there on the task form? I found  a post  on Nintex Connect which walks through meeting this requirement by leveraging  a custom action  created by Nintex Technical Evangelist,  Vadim Tabakman . But, what if you don’t have access to deploy a custom action to your SharePoint environment? In this case, I actually didn’t have access to the client’s server. So, I decided to come up with a solution that would produce a similar outcome, without the need for any custom actions. The Workflow Get Att
Read more