05 August, 2013

Unable to display this webpart + navigation add link not working in SharePoint 2010

One of our users has opened a ticket that some default functionality is not working as expected. If somebody mentioned as ‘default functionality’ then it means out of box and no customizations at all. Furthermore, probed the user and gathered the details.

-Issue was farm wide i.e. across all web applications / all site collections

Problem description:
User was trying to add one of the existing list/libraries link by means of navigation,

here are the complete details to reproduce the issue:
-Open the site
-site actions
-site settings
-Look and Feel
-Navigation
- Select either global navigation or current navigation
-Add link
-Click on Browse
-Two panes will be reflected i.e. left pane and right pane
-if you select any entity from the left side then it has to show in the right side but you will get the following error in the right side.

Error Message:
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.
Correlation ID: xxxx-xxxx-xxxx-xxxxx

Resolution:
We have opened a ticket with Microsoft and got to know this is known issue and happening because of recently installed windows update: KB2844286

As per the information conveyed from them- "Both the SharePoint and .NET product groups are aware of the issue and they are in the process of fixing the patch"

Removing windows update: KB2844286 is the only solution at this time.

Once you remove the update then please restart the server. Thank you.

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.


If you have any other resolution apart from the above mentioned then request you to please share so that it would be beneficial for others as well.

Security token service is not available- SP2010

Security token plays an important role with respect to authentication purpose, if this stops functioning then you will start getting so many tickets regarding access as well as critical tickets which are dependent on the same as few other services are also dependent on this service i.e. security token.

Here is the Microsoft link which talks about in details on security token:

While doing the sanity check across all front ends, we have noticed the security token service exception in the event viewer logs with respect to one of the server.

Here are the details:
Error message: Security token service is not available.

Checked the IIS status and found all the application pools and websites were in stopped status.

Started all the SharePoint entities which were in stopped status.

Checked the rule again and it was not there in the HA (Health Analyzer) list anymore.

Issue resolved, we are good now. Thank you.

Few IMP points which are essential while troubleshooting this issue:

In our case, the security token service was working initially without any issues and the farm was already built properly. But in your case, if it’s a newly built farm then it might be a hotfix issue as per this Microsoft article:


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


Also-if you have a different resolution regarding the same issue then request you to share the same so that it would be useful to other as well. Thank you.

02 August, 2013

Expired sessions are not being deleted, Health Analyzer Error in SharePoint 2010

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 analyser- click on that warning and select ‘reanalyse 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


01 August, 2013

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…

30 July, 2013

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:



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.