After migration of web application server to virtual environment we have the error several times per hour. Please, help to understand what’s wrong. Database server has been placed in virtual environment. If stop web applications and start them again the problem disappears. Error description: Unable to connect to the database session SQL Server. Connection string (server='server name', database='SharedServices_DB') was returned by an instance of the IPartitionResolver type 'Microsoft.Office.Server.Administration.SqlSessionStateResolver, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'. at System.Web.SessionState.SqlSessionStateStore.ThrowSqlConnectionException(SqlConnection conn, Exception e) System.Web.SessionState.SqlSessionStateStore.DoGet(HttpContext context, String id, Boolean getExclusive, Boolean& locked, TimeSpan& lockAge, Object& lockId, SessionStateActions& actionFlags) System.Web.SessionState.SqlSessionStateStore.GetItemExclusive(HttpContext context, String id, Boolean& locked, TimeSpan& lockAge, Object& lockId, SessionStateActions& actionFlags) System.Web.SessionState.SessionStateModule.GetSessionStateItem() System.Web.SessionState.SessionStateModule.BeginAcquireState(Object source, EventArgs e, AsyncCallback cb, Object extraData) System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Thank you, Patrick! But I saw these links ant it doesn't work. Ann.

Ok, one time I got also a strange issue when migrating machines to another environment. Sporadically, SharePoint was not able to connect to SQL Server. After a while we checked the firewall status between the front-end and back-end. We noticed that sometimes SQL Server opens a different port than the ports defined in the standard SQL range. So the issue was related to the firewall between the two machines. If you have a firewall between two machines, try to check the rules and if traffic is blocked. Hope this helps, patrick follow my blog http://patrick.lamber.blogspot.com to get additional tips and information about SharePoint, Project and ASP.NET

Hi, did you find the solution to your problem? Could you let us know? Best regards, Patrick follow my blog http://patrick.lamber.blogspot.com to get additional tips and information about SharePoint, Project and ASP.NET

I set in web.config sharepoint application <sessionState mode="InProc" cookieless="false" timeout="30" /> instead of <sessionState mode="SQLServer" timeout="60" allowCustomSqlDatabase="true" partitionResolverType="Microsoft.Office.Server.Administration.SqlSessionStateResolver, ....MH