So I have this site that is 100% totally dead, cant access the pages, admin area, nothing. Normally if it is a Web part you can access the admin area and the maintenance page. But this site is just dead. I get this exception in the log: Exception Type: System.Web.HttpException Exception Message: Unable to connect to SQL Server session database. The connection string (server='BVSQL\Sharepoint', database='BVSP_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'. Other site-collections works just fine, and Central Administration and the Shared Services Site also works. Could it be the site collection content db thats fried?? -- Christian

Hi,I am also getting the same error. did you get any solution for the same. Please update me if you have got the solution for the same.Thanks in Advance.Sunil

Oh, this was a long time ago, but I believe my problem happened in some rare cases where the session of the logged in user got screwed up. I remember closing the browser and in some casesdeleting all cookies for the particular site seemed to rectify the problems and let me get on the site again. Also when I received the error other users seemed to view the site without any problems. Again pointing to problems with the session/state. I don't know if it was a bug in SharePoint or something I did wrongwhen developing Web Parts against the SharePoint API. It's been a LOONG time since I have seen this error. Hope this helps... -- Christian

Hi Christian,Thanks for your response. I don't think its the problem with respect to web part, because I configured two site on the same server, where my database is on the other server. One of the site is working fine and the other site is not working. when i saw the eventlog I am getting the below error:Unable to use SQL Server because ASP.NET version 2.0 Session State is not installed on the SQL server. Please install ASP.NET Session State SQL Server version 2.0 or above. The connection string (server='DBServerName', database='SharedServices1_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'.and the web.config file you can see the session configuration as<sessionState mode="SQLServer" timeout="60" allowCustomSqlDatabase="true" partitionResolverType="Microsoft.Office.Server.Administration.SqlSessionStateResolver, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />where the session state is ASP.NET Session State Partitioning, I think i may need to enable the sql server session state on the sql server.I deleted the site and created again and mean time I ran the below command, which worked for me.aspnet_regsql -S <SQLServerName> -U <Login ID> -P <Password> ssaddI think it may be a bug in the sharepoint. Thank you.Thanks in Advance,Sunil

In response to the above,I Still I faced the same problem, when creating the workflow. and below is the solution.1. On my SQL Server 2005 Management Studio, 2. Goto Security --> Logins --> you can find the user that represents web server, DOMAIN\MACHINE$.2. Right-click the DOMAIN\MACHINE$, choose User Mapping.3. Map the SharedServices1_DB. check the roles db_owner and public.4. Click OK.This would be better solution to resolve the issue.Sunil

In response to the above,I Still I faced the same problem, when creating the workflow. and below is the solution. 1. On my SQL Server 2005 Management Studio, 2. Goto Security --> Logins --> you can find the user that represents web server, DOMAIN\MACHINE$.2. Right-click the DOMAIN\MACHINE$, choose User Mapping.3. Map the SharedServices1_DB. check the roles db_owner and public.4. Click OK.This would be better solution to resolve the issue. Sunil That was the problem. I want to thank you very much for posting this correct solution. Thank you!

Thanks. I was getting this error. I don't know why either but I was not developing a web part at the time. I had just added a new content type through the browser. I closed my browser out and everything is fine now. Clint