The workbook cannot be opened or we are sorry, we couldn’t open your workbook.

The workbook cannot be opened  or we are sorry, we couldn’t open your workbook.

Issue: We are sorry we could not open your work book or sorry, but to open this workbook your computer must be running a supported version of Microsoft excel

Solutions: there could be many reasons of the issue. I am providing the solution for the  most common.

Error: We are sorry we could not open your work book

 

 

You can use following cmdlets to get this issue resolved

$webApplication = Get-SPWebApplication –Identity <URL of the Web application>

$webApplication.GrantAccessToProcessIdentity("<insert service account>")

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

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.

·        it might be the reason that  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

 

I hope the above information will help you to resolve the issue, in case of 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.

Uninstall of Cumulative Updates for SharePoint

Uninstall of Cumulative Updates for SharePoint

I am posting this topic because I am getting many questions from SharePoint Techies that they want to uninstall the CU updated to their farms.

Is it possible: There is no easy way to uninstall a cumulative update package for SharePoint. SharePoint updates are really a one-way street: you can only go forward with them and there's no way to uninstall, roll back, or remove them once you've started the installation process

Reasons: The reason for this is that there are two components to the update process

1)   updating the SharePoint bits installed on each SharePoint server

2)   updating the schemas and configuration of the farm's databases in its SQL Server instances. 

If you uninstall the bits from your SharePoint servers, those databases are still going to be functioning at the level of the applied CU and will not work with your servers

 


I hope the above information will help you to resolve the issue, in case of 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.

How to Increase of Quota templates

How to Increase of Quota templates

Please follow the below steps to change the quota templates in sites.

1.    Verify that you have the following administrative credentials:

·         You must be a member of the Farm Administrators group.

2.    On the Central Administration home page, click Application Management.

3.    On the Application Management page, in the Site Collections section, click Specify quota templates.

4.    On the Quota Templates page, in the Template Name section, in the Template to modify list, select the template that you want to change.

5.    In the Storage Limit Values section, specify the values that you want to apply to the template.

·         If you want to modify the amount of data that can be stored in the database, leave the Limit site storage to a maximum of check box selected, and then type the new storage limit, in megabytes, in the box.

·         If you want an e-mail message to be sent to the site collection administrator when a storage threshold is reached, select the Send warning E-mail when site storage reaches check box, and then type the threshold, in megabytes, in the box.

6.    In the Sandboxed Solutions With Code Limits section, specify the values that you want to apply to the template.

·         If you want to limit the maximum resource usage points per day for sandboxed solutions that contain code, type the new limit in the Limit maximum usage per day to box. The default limit is 300 points.

·         If you want an e-mail message to be sent to the site collection administrator when the usage per day threshold is reached, select the Send warning e-mail when usage per day reaches check box, and then type the threshold, in points, in the box.

7.    Click OK.

 Article from MS: http://technet.microsoft.com/en-gb/library/cc263480%28v=office.14%29.aspx

 

I hope the above information will help you to resolve the issue, in case of 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 super reader account utilized by the cache does not have sufficient permissions to SharePoint databases

The super reader account utilized by the cache does not have sufficient permissions to SharePoint databases

Issue: The super reader account utilized by the cache does not have sufficient permissions to SharePoint databases

Cause: This means that the cache accounts for your web application aren’t properly set and that there will be a lot of cache misses. If a cache miss occurs the page the user requested will have to be build up from scratch again. Files and information will be retrieved from the database and the file system and the page will be rendered. This means an extra hit on your SharePoint and database servers and a slower page load for your end user.

Solution: The domain\super user account needs to have a User Policy set for that gives it Full Control to the entire web application. In order to do this you perform the following steps:

1.     Go to Central Administration

2.     Go to Application Management

3.     Go to Manage Web Application

4.     Select the web application we’re talking about

5.     Click User Policy

6.     Add Users

7.     Click Next

8.     Fill in domain\superuser

9.     Select Full Control

10.  Click OK 

The domain\super reader account needs to have a User Policy set for that gives it Full Read to the entire web application. In order to do this you perform the following steps:

1.     Go to Central Administration

2.     Go to Application Management

3.     Go to Manage Web Application

4.     Select the web application we’re talking about

5.     Click User Policy

6.     Add Users

7.     Click Next

8.     Fill in domain\super reader

9.     Select Full Read

10.  Click OK

1.    If you are using classic mode authentication run the following cmdlets on one of your SharePoint servers:

$w = Get-SPWebApplication "http://<server>/"

$w.Properties["portalsuperuseraccount"] = "domain\superuser"

$w.Properties["portalsuperreaderaccount"] = "domain\superreader"

$w.Update()

2.    If you are using claims based authentication run these cmdlets on one of your SharePoint servers:

$w = Get-SPWebApplication "http://<server>/"

$w.Properties["portalsuperuseraccount"] = "i:0#.w|domain\superuser"

$w.Properties["portalsuperreaderaccount"] = "i:0#.w|domain\superreader"

$w.Update()

After you've run these Power Shell cmdlets you need to perform an IISRESET to finish it off.

Reference from MS:http://technet.microsoft.com/en-us/library/ff758656.aspx.

 


I hope the above information will help you to resolve the issue, in case of 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.