Expired sessions

Today we are going to discuss one of the errors that we have noticed in SharePoint Health Analyzer. as per that exception, here is the reflected information.

Exact Exception: Expired sessions are not being deleted from the ASP.NET Session State database.

Mentioned explanation: If expired sessions are not deleted, the server that hosts the ASP.NET Session State database may run out of disk space and the SharePoint farm may cease to function.

Remedy reflected: Connect to the server that hosts the ASP.NET Session State database, start the SQL Server Agent service, and verify that a DeleteExpiredSessions job is registered for the database. If you are using SQL Server Express, the SQL Server Agent service is not available. For more information about this rule, http://technet.microsoft.com/library/ff805085.aspx

Troubleshooting done:

Checked the timer job status named ‘State Service Delete Expired Sessions’

How we have checked this:

-Open SharePoint 2010 central administration

-Monitoring

-Timer Jobs

-Review Job definitions

-Check the job ‘State Service Delete Expired Sessions’

-By default it runs on hourly basis, so we have executed ‘Run now’ but that didn’t result any output.

Checked the stored procedure named ‘DeleteExpiredSessions’ is exist or not.

How we have checked this:

-Login to the SQL SERVER BOX by using farm account

-expand the list of databases

-look out for Session State database

-Expand the same database

-expand programmability

-expand stored procedures and you will find that above mentioned stored procedure name in that list.

-if it’s not listed there then we need to create that stored procedure.

Once you find that stored procedure then simply right click on it and execute it.

After this, simply go to the central administration-health analyzer- click on that warning and select ‘reanalyze now’ option. That’s it.

Issue Resolved.

If you have any inputs regarding the above mentioned information then please share so that it would be useful for the whole SharePoint community.

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:

SharePoint Server 2010

SharePoint Foundation 2010

Reference: http://technet.microsoft.com/library/ff805085.aspx

The specified file is larger than the maximum supported file size-SharePoint 2010

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 a39c080f-1215-47eb-7f7a-6242e3882e5e. It may have been removed from the database.

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.

SHAREPOINT DESIGNER START APPROVAL PROCESS ISSUE

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.