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

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

Document set in sharepoint 2010

Normally banks will maintain customer’s information. They will provide customers basic info, internet banking, mobile banking, debit card facilities to their customers, they maintain separate documents for each.

We will use the same feature using Document set in SharePoint 2010.

How to enable Document Sets?

Document sets by default won't be enabled in SharePoint 2010. It's a feature and has to be enabled manualy. Then document sets Content type has to be customized (if required). After that it can be attached to Document libraries. First keep all project document templates (BasicInformation document, PhoneBanking document, InternetBanking Document, Debitcard Document) ready.

Create these documents in my documents folder.

 

Login to SharePoint 2010 site -> Site settings -> Site Administration -> Site Collection Features ->

Document Sets -> Activate.

Site Settings -> Galleries -> Site Content types -> Document Set Content Types -> Document Set.

Select Document Set Settings.

Under Default Content section select the templates. Click "Add new default content" to select and upload more template documents.

Now upload the documents that u created earlier as shown below

Now we'll create new document library. If you want to attach to existing document library then skip this step.

Open the document library -> Library (Tab) -> Library Settings.

Under General Settings select Advanced Settings. We need to enable allow management of content types setting.

Under Content types Select Yes for "Allow management of content types?" and save/Click Ok.

Now in the library settings page Content types section will be shown. Select "Add from existing site content types".

Under "Select Content types" section select "Document Set" and Add. Now click Ok.

 

Repeat the same steps and add another

Microsoft SharePoint Designer 2010 Download

SharePoint Designer 2010 is the tool of choice for the rapid development of SharePoint applications. Using SharePoint Designer, advanced users and developers alike can rapidly create SharePoint solutions in response to business needs. Advanced users can compose no-code solutions that encompass a variety of common scenarios, from collaborative sites and web publishing to Line-Of-Business data integration, business intelligence solutions, and human workflows, leveraging the building blocks available in SharePoint in an easy to use environment. In addition, developers can use SharePoint Designer 2010 to get a quick start on SharePoint development projects.​

This is the 32-bit edition of SharePoint Designer 2010. It is the recommended configuration for most users

http://www.microsoft.com/en-in/download/details.aspx?id=16573


This download is the 64-bit edition of SharePoint Designer 2010. The 32-bit edition is suggested for most users

http://www.microsoft.com/en-in/download/details.aspx?id=24309

SharePoint 2013 Installation and Training

Microsoft releases a major version of SharePoint every three years. There are some downsides to this approach, but one definite upside is that when the releases do come around, those of us who work with SharePoint every day tend to get a bit excited.

So it was with much anticipation that I took a close look at the recently released SharePoint 2013 Preview. My initial take is that this is a significant release with a ton of great new features to talk about.

SharePoint 2013 Installation on Windows Server 2012

If you are looking for the installation of SharePoint 2013 then please refer the following link: http://www.codeproject.com/Articles/440608/SharePoint-2013-Installation-on-Windows-Server-201

 

Detailed and description explanation with some nice screenshots by Jean Paul. Thanks to Jean for publishing such wonderful article.

Next thing come to my mind is about training. After the installation, if we need to learn the basics of each feature and functionality then it is very important to know the functioning of that feature and that can be learn by means of valuable training which has been provided by Microsoft as well as Stefen Gobner.

SharePoint 2013 training for IT pros

http://technet.microsoft.com/en-us/sharepoint/fp123606.aspx

 

http://blogs.technet.com/b/stefan_gossner/archive/2012/10/30/sharepoint-2013-training-for-it-pros.aspx

Metalogix Content Migration and Upgrade for Microsoft SharePoint Server 2010

Microsoft’s SharePoint Products and Technologies have brought robust Enterprise Content Management and Collaboration capabilities to an increasing number of organizations in recent years. The popularity of the previous versions, such as Windows SharePoint Services 2.0 and 3.0, SharePoint Portal Server 2003 and Microsoft Office SharePoint Server (MOSS) 2007, led many organizations to deploy SharePoint to various business units, frequently on a large scale.

Many organizations are now looking toward the SharePoint 2010 wave of products, including SharePoint Foundation 2010 and Microsoft SharePoint Server 2010, because of key functionality improvements in the software. These include the integration of the Office ribbon into SharePoint sites, a more scalable services architecture, document management improvements, enterprise taxonomy and many more.

Unfortunately, the migration path provided by Microsoft does not always address organizations’ needs.

The out-of-box upgrade approaches available from Microsoft suffer from fairly significant limitations.

These approaches:

·         Do not support gradual upgrades

·         Do not support granular migration

·         Do not allow administrators to reorganize content during migration

·         Have limited support for 32-bit source systems

·         Do not support upgrades from SharePoint 2003 directly to SharePoint 2010

These limitations present organizations looking to upgrade to SharePoint 2010 with significant planning challenges that will limit both proof of concept and full implementations. Organizations must also ensure that the upgrade approach they select will not jeopardize the content on the existing platform.

Fortunately, Metalogix has released version 4 of SharePoint Site Migration Manager (SSMM 2010), a tool to migrate content from legacy SharePoint 2003/2007 technologies directly to SharePoint 2010.

SSMM 2010 allows organizations to take advantage of SharePoint’s new features without putting their valuable content at risk. SSMM 2010 provides significant advantages over existing migration tools and techniques, allowing for flexible migration between SharePoint versions and farms, granular migration, Power Shell support, reorganization of sites, templates, and databases during the process, as well as many other enhanced capabilities. Unlike some content migration options, SSMM 2010 uses only SharePoint’s fully supported APIs to migrate content, which ensures that it will not affect existing support agreements with Microsoft.

Key Benefits

·         Migrates SharePoint Sites, Lists and Libraries between Servers with full fidelity.

·         Upgrade from SharePoint 2003 and SharePoint 2007 to SharePoint 2010.

·         Re-Organize and re-template your SharePoint Content.

·         Manage your upgrade with zero downtime.

·         Migrate to the cloud or hosted SharePoint environments and reduce infrastructure costs.

Supported Source Systems

·         SharePoint Portal Server (SPS) 2003

·         Windows SharePoint Services (WSS) v2

·         Microsoft Office SharePoint Server (Moss) 2007

·         Windows SharePoint Services (WSS) v3

·         SharePoint Server 2010

·         SharePoint Foundation 2010

·         SQL Server 2000, 2005, and 2008 Unattached SharePoint databases (Read Only)

·         Microsoft Online Services (MOS) [a.k.a BPOS, Exchange Online, or SharePoint Online ] Standard and Dedicated Versions

Key Features

Easy to Use

Run your migration with a tree-based, copy-and-paste-style user interface that is similar to the familiar Windows File Explorer.

Reorganize or re-template sites during migration

Re-define site structure while migrating. Split Sites and Site collections into multiple targets and re-template Sites. Administrators and content owners can define what content is migrated.

Migrate all list types

Migrate Document Libraries, Issues, Tasks, Contacts, Announcements, Discussions and Custom Lists while preserving views, metadata, and user-edit information.

Retain your valuable data

Preserve all views, version chains, metadata, and user-edit information.

Migrate Permissions

Map and migrate site permissions from WSSv2/SPS 2003 and WSSv3/MOSS 2007 to SharePoint 2010 easily.

Migrate Web Parts

Migrate all out-of-the-box and custom web parts from WSSv2/SPS 2003 and WSSv3/MOSS 2007 sites to SharePoint 2010.

Connect to multiple sites

Connect to multiple SharePoint sites, across any number of servers, for easy consolidation or distribution of your SharePoint data.

Work remotely

Do all the heavy lifting for your SharePoint migration from the convenience of your own machine. SharePoint Site Migration Manager connects to any SharePoint site that you can access with your browser -- even those outside your organization’s intranet.

PowerShell Enabled

Access and extend all SharePoint Site Migration Manager Functionality via PowerShell commandlets, to script and automate all migration functionality.

Migrate from live sites and unattached content databases

SharePoint Site Migration Manager provides native capabilities to migrate directly from unattached content databases to live sites, eliminating the need to build temporary farms. Simply point to an unattached database extracts the data directly and migrate it into a live SharePoint 2010 environment.

Distribute the Workload

Use SSMM to delegate and distribute migration efforts across the organization to individual departments or content owners. This reduces IT workload, enhances buy-in on the new target system, and improves decision-making in terms of content re-organization. You can manage a distributed workload because SharePoint Site Migration Manager reads and writes only to the supported SharePoint APIs, so content is security trimmed properly. Content owners simply need read access to their source sites using the SSMM client, along with write access to their new target locations.

Latest Version

SharePoint 2010

SharePoint Foundation 2010

Microsoft SharePoint Server 2010

SharePoint Site Migration Manager 2010

How to start the Trace service

The Windows SharePoint Services Tracing (SPTrace) service is used by Windows SharePoint Services 3.0 to manage trace output of the call stack. When trace logging is enabled, administrators can specify the path used to store the trace logs. This log file is reused by many applications that are built on top of Windows SharePoint Services 3.0.

The Microsoft SharePoint Foundation Tracing (SPTrace) service is a required service on all Microsoft SharePoint Foundation servers. If this service is stopped, error messages are not logged on the server.

How to Start the Trace service:

1. Log on to the SharePoint Foundation server as an administrator.

2. In a Command Prompt window, type the following at the command prompt:

3. net start SPTrace

I hope the above mentioned information will be helpful to you to get some insight regarding SharePoint tracing service. In case of any issues/queries regarding the mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, thank you

SharePoint 2010 versions

This article contains a list of SharePoint 2010 version numbers and related updates.

KB Article	SP Version Number	Description
2536599	14.0.6106	SP2010 Server – June 2011 CU
2536601	14.0.6106	SP2010 Foundation – June 2011 CU
2460045	14.0.6029	SP2010 Server – Service Pack 1
2460058	14.0.6029	SP2010 Foundation – Service Pack 1
2512800	14.0.5138	SP2010 Server – April 2011 CU
2512804	14.0.5138	SP2010 Foundation – April 2011 CU
2475878	14.0.5136	SP2010 Server – February 2011 CU
2475880	14.0.5136	SP2010 Foundation – February 2011 CU
2459257	14.0.5130	SP2010 Server – December 2010 CU
2459125	14.0.5130	SP2010 Foundation – December 2010 CU
2394320	14.0.5128	SP2010 Server – October 2010 CU
2394323	14.0.5128	SP2010 Foundation – October 2010 CU
2352342	14.0.5123	SP2010 Server – August 2010 CU
2352346	14.0.5123	SP2010 Foundation – August 2010 CU
2259686	14.0.5114	SP2010 Server – June 2010 CU
2028568	14.0.5114	SP2010 Foundation – June 2010 CU