The specified file is larger than the maximum supported file size, Error while trying to upload a file in SharePoint 2010 site

Here we go with one more error message along with step-by-step resolution for the whole SharePoint community.

Problem description:

One of my departmental colleague is trying to upload a file in SharePoint site and getting the following error message:

Error message:

Server Error in ‘/’ Application

The specified file is larger than the maximum supported file size.

Imp notes:-

The error message is self explanatory for those who are well versed with the SharePoint functionality, but it is quite understandable to get the confusion for those who have recently migrated to this new SharePoint version, started learning SharePoint recently and so many reason.

But nothing to worry, that’s why I am here to provide the detail instructions as how we can resolve this issue completely.

Little background on this:-

If you are facing this error message then let me clear that this limit is already defined somewhere and that’s why you are getting this exception.

In SharePoint 2010, we have a central console from where we can control all the things which is termed as ‘Central Administration’

So let’s explore this central administration to find out this defined limit.

-Open the SharePoint 2010 Central Administration

-Application management

-manage web applications

-select the correct web application

-Top side- On the web application Ribbon

-click the down arrow and select General settings button

-Go to ‘maximum upload size’ section

By default its 50MB

-Enter the appropriate value as per your requirements and select OK

Note: This setting will be applicable for the complete web application i.e. applicable for all the site collections which are a part of that web application.

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…

Cannot find history for workflow with instanceId. It may have been removed from the database + Nintex 2010

One more NINTEX issue, today I am going to discuss some more details with respect to one workflow issue which has been configured using NINTEX.

Problem Description:

The “xxxname of the workflowxxx” workflow has ended unexpectedly for ‘xxxname of the itemxxx’.

“name of the workflow” failed to start.

Click here to view the workflow status.

As soon as we click on “click here to view workflow status” then we get the following exception.

Error Message:

Cannot find history for workflow with instanceId a39c080f-1215-47eb-7f7a-6242e3882e5e. It may have been removed from the database.

Troubleshooting done:

-Checked the SharePoint logs

-Checked the event logs

-Checked the NINTEX REPORTS based on that specific site collection

-Tried opening the site in Mozilla Firefox to debug by means of FIRBUG

-Checked the workflow history exist or not for that specific list

Resolution:

From the error message, we have a instance id of the list on which we are trying to check the workflow history.

Here are some links that I have referred to get the instance id:

http://blogs.technet.com/b/heyscriptingguy/archive/2010/09/22/use-powershell-to-manage-lists-views-and-items-in-sharepoint.aspx

http://geekswithblogs.net/bjackett/archive/2010/07/12/powershell-script-to-find-instances-of-running-sharepoint-workflow.aspx

http://blogs.flexnetconsult.co.uk/colinbyrne/2008/02/26/PowerShellSharePointThreeWaysToDeleteAListItemIDCAMLStringMatching.aspx

But the strange thing was the item did not exist, how did I find out this? It’s very simple…

Let’s do some analysis on the error message again!!!

The “xxxname of the workflowxxx” workflow has ended unexpectedly for ‘xxxname of the itemxxx’.

“name of the workflow” failed to start.

Click here to view the workflow status.

-now try to click on name of the workflow item

-as soon as we clicked on that item then we got the following error message:

File not found.

Troubleshoot issues with Microsoft SharePoint Foundation.

Correlation ID: xxxx-xxxx-xxxx-xxxxx

Date and Time: xxxx-xxxxxx

From the above exception, it’s very clear that the item does not exist.

Issue resolved. We are good now…

If you have any queries/questions regarding the above mentioned information then please let me know, also if you have any additional resolution/valuable inputs apart from the mentioned above then please share so that it would be valuable for the complete community… Thank you.

Loading this assembly would produce a different grant set from other instances in SharePoint Designer 2010

Environment entities:

-Windows server 2008 R2

-SQL server 2008

-SharePoint Server 2010 with SP1

-Client: Windows 7 + IE7.0

Problem Description: In SharePoint designer 2010, whenever I use the “Start Approval Process” action on new or existing workflows and try to publish it, it’s throwing the following error.

Error Message#1: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x80131401)

Checked the SharePoint logs and found the following error:

Error Message#2: Errors were found when compiling the workflow. The workflow files were saved but cannot be run.

Right from the beginning Microsoft is playing a very important role in publishing knowledge base article which are very useful for the whole community.

Resolution: http://support.microsoft.com/kb/2557533

As per this article, we can increase this default value to 7000 by using the following command:

$app = get-spwebapplication http://portal.sharepoint2010.com

$app.UserDefinedWorkflowMaximumComplexity = 7000

$app.Update ()

Again the best practices are saying we need to take every step by considering the farm performance as the maximum limit is 10000 and you cannot increase more than that so it’s better if we restructure our workflows with respect to reusability.

If you have any queries/questions regarding the above mentioned information then please let me know. If you have any additional resolution or valuable inputs which would be useful for the whole SharePoint community then please share…

Thank you.

Product Applies To:
-SharePoint Server 2010
-SharePoint Foundation 2010

Object reference not set to an instance of an object + Unable to display this webpart + Error while executing webpart in SharePoint 2010

Problem Description: XSLT list views do not work / TIMEOUT FOR XML TRANSFORMATIONS

Error Message#1: Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator.

Error Message#2: Error while executing web part: System.NullReferenceException: Object reference not set to an instance of an object.

Debugging SP Logs:

0x1578 SharePoint Foundation         Web Parts                     89a1

High     Error while executing web part: System.NullReferenceException: Object reference not set to an instance of an object.     at System.Xml.Xsl.XslCompiledTransform.Load(MethodInfo executeMethod, Byte[] queryData, Type[] earlyBoundTypes)     at Microsoft.Xslt.STransform.GetCompiledTransform()     at Microsoft.SharePoint.WebPartPages.BaseXsltListWebPart.LoadXslCompiledTransform(WSSXmlUrlResolver someXmlResolver)     at Microsoft.SharePoint.WebPartPages.DataFormWebPart.GetXslCompiledTransform()     at Microsoft.SharePoint.WebPartPages.DataFormWebPart.PrepareAndPerformTransform(Boolean bDeferExecuteTransform)

Resolution:  After analysing the complete SharePoint environment, we realized that if this issue started recently so there must be some changes happened with respect to the updates. When we checked the updates then we found that there are some windows updates got installed recently but difficult to find out the culprit.

Here it comes the MICROSOFT as a LIFE SAVER and remove your headache by means of this issue. Millions Thanks to Microsoft once again!!!

Please refer the following Microsoft TechNet thread:

http://social.msdn.microsoft.com/forums/windowsazure/ru-ru/871a0661-05d0-4f3a-b66d-2504552142bd/error-while-executing-web-part-systemnullreferenceexception-object-reference-not-set-to-an

ALSO- http://support.microsoft.com/kb/2872441

Overall conclusion is:

If you want to get rid of this issue then please refer the following steps:

-Uninstalled this update: Windows KB2844286

-Hide the update

-reboot the server

Thank you very much for reading this article.

If you would like to share some updates from your side with respect to this issue (any new resolution, any new findings, new easy resolution apart from the above mentioned) then please share so that it would be useful for the whole community. 

The content databases in this cluster are full. You cannot add more web sites until you change the content database web site capacity settings or add more content databases

SharePoint capacity planning plays a very vital role with respect to any farm, whether it’s a small farm, medium farm or large farm. Today I am going to share some details and troubleshooting steps regarding one issue that I faced recently.

Problem Description: we have received the following error message while creating the site collection.

Error Message: The content databases in this cluster are full. You cannot add more web sites until you change the content database web site capacity settings or add more content databases.

Troubleshoot issues with Microsoft SharePoint Foundation.

Troubleshooting done: From the above error message, 2 points comes into the picture i.e. database size and number of site collections exist in a single database.

-Based on analysis, we found out that total site collections exist are 100 and size of the database was 67GB.

-checked the managed databases section in central administration with respect to that web application under which we are trying to create a site collection. We found out that somebody has changed the maximum site collection limit to 100 and that’s why we were facing that error message.

Resolution:

Please refer the following steps to get rid of this error message:

-Central administration

-Application management

-manage databases

-select the appropriate web application from the top

-change the maximum site collection limit to 15000 and warning set to 9000.

That’s it. After this we are able to create site collections without any issues.

If you have any queries/issues 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.