23 October, 2013

Failed to download Excel Services chart

Playing with excel is day to day task! Excel services and its errors are full of excitement :)

Today we got one ticket that user is facing some problem while displaying excel document by means of excel web access webpart. Further probing, we came to know that he is trying to display some chart by means EWA and getting the error as mentioned below:

Failed to download Excel Services chart

There is no need to troubleshoot this error we have a predefined setting in the central administration so easy resolution!

Let me describe step by step so that there would be no confusion.

Resolution:
1)   Open the Central Administration
2)   Manage service applications
3)   Excel service application
4)   Click on it
5)   Manage trusted file location settings
6)   Click on the trusted location of that web application
7)   In the Workbook Properties section, there is a "Maximum Chart Size" setting that is "1" (meaning the maximum chart size is 1MB) by default.
8)   Increase that and then click OK.

That’s it, you are done! Check the site on which you were facing the problem and that should be resolved now.

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.

Product applies to:
1)   SharePoint Server 2010
2)   SharePoint Foundation 2010
3)   SharePoint Server 2013
4)   SharePoint Foundation 2013

22 October, 2013

The Compressed (zipped) Folder is invalid or corrupted

Issue: Whenever my client tried to open a .zip files from SharePoint it throws the below error message.

Background: One of my clients had zipped the .excel files in on his local desktop and uploaded to SharePoint site. There files contains the project level information and was needed to extract after two years. When he clicked the file to open from SharePoint had encountered the issue.

Now the task begins of a SharePoint admin.

Troubleshooting:

Tried to open the file from SharePoint site, no go.

Downloaded the file on desktop of the client, no go.

Tried the same steps at my end, no success.

Strange this accessing file on SharePoint server also does give the same error.

With the above basic stuff, it was clear that it is something to deal with the zip file itself as it doesn’t seems to be SharePoint issue anymore.

Being a digger try to dig some more in it and seems like something to deal with the excel documents zipped may be was in protected mode.

Client was having no clue for this.

Resolution: Tried to find the Repair tool on the internet and million thanks to Christina Marley who created a zip file repair utility which when ran has repaired the file and is available for download here. Christina MarleyChristina Marley


Asked the user to download the files and repair them with the utility.

However, you can also find some other relevant repairing tools which may provide the evaluation version or you may need to buy the licence version of the tool.


If you feel any difficulty in understanding the tool or have any query I would be happier to help you.
Applied to: SharePoint 2007, WinZip, and WinRAR. Windows XP.


21 October, 2013

Exception from HRESULT: 0x80041050

Error message: /sites/Sharepoint].xml" contains the following virus: "Reason:= ".

If you want to open this file, you'll need to clean the file using your own virus scanning software. Do you want to save the file to your computer and attempt to clean it.



Background: A user reported that he tried to open an InfoPath form from a SharePoint site and got the error message mentioned above. There is no error occurring when opening any other file. If he clicks yes, and saves the file on the local desktop, he gets the exception error:Exception from HRESULT: 0x80041050”

 Troubleshooting:

Tried opening the file on the same site, get error message.
Tried to download the file, get the exception error message.
Tried opening the other file on the same site and it is opening fine.
The only issue was with the one file.

Resolution:

Based on the TechNet article http://technet.microsoft.com/en-us/library/dd795107(v=office.12).aspx  


To determine whether or not the file is actually infected, you will need to look at the error message for the specific error code 0x80041050. This means that the item is virus-infected. If the item is virus-infected, either delete the infected item, or attempt to clean it using your virus scan application. If the item is not virus-infected, restart the content deployment job.

You can also try to look if there is Virus infected file in the SQL Content DB by running the following query:

Create a new query and run:Select *
from AllDocs
where (VirusStatus > 0) and (VirusStatus is not null)

If you get any results this is your issue!  (Given that you don't actually have some virus in that file.)
Run the next query: Update AllDocs
set VirusStatus = null
where (VirusStatus > 0) and (VirusStatus is not null)


Applies to: WSS 3.0, SharePoint 2007.
 

20 October, 2013

Event ID 5586

Issue: Event ID: 5586 Generated in the SharePoint server.

Error: Event ID 5586 generated in SharePoint server application event logs.

Event Type:      Error
Event Source:  Windows SharePoint Services 3
Event Category:            Database
Event ID:          5586
Date:                09/10/2013
Time:               10:24:22
User:                N/A
Computer:        ++++++++++++
Description:
Unknown SQL Exception 1035 occurred. Additional error information from SQL Server is included below.

Background:
As a part of daily health check on the server, I have noticed allot many occurrences of the event ID 5586 on multiple servers.

This is something occurs on regular intervals but not specific to one server.

By looking some of the reference on the internet I happened to find the TechNet Article which talk about the possible resolution of this error.

Resolution:
This error occurs in both the versions of the SharePoint i.e. 2007 and 2010; however in my case it was reported for the SharePoint 2007.



Great thanks to MS to keep the record of the most relevant event IDs and sharing the possible remedies

If you feel any difficulty in following any of resolution listed in the articles, do let me know. I would be more happy to help you put with.

Products Applies to:
1)      SharePoint 2007
2)      SharePoint Server 2010
3)      Windows Sever 2003
4)      Windows Server 2008
5)      SQL Server 2005 and SQL Server 2008.