Issues with SessionState?

Discussion in 'Windows / IIS' started by thirdboxcar, May 1, 2009.

  1. Hello,

    I have a gift card page I've inherited from another host. I'm fairly sure (I'm fairly new to asp, though) that the credit card orders will not process because my SessionState connection string is wrong.

    The error occurs when I submit info on the following page (which leads to a confirm page, which shows up fine, but the confirmation page does not):
    https://www.chowfoods.com/giftcards/index_bak.aspx

    The page will at least show up if I use the following in web.config, although it won't process the cards:
    <sessionState mode="InProc" stateConnectionString="tcpip=##.##.##.##" sqlConnectionString="Data Source=tcp:sql2k802.discountasp.net;Initial Catalog=SQL2008_623370_*****;User ID=SQL2008_623370_*****_user;Password=*****;" cookieless="false" timeout="20" />
    Using the above, I get the following error twice:
    Object reference not set to an instance of an object.
    Using the following code, which I've found all over the forums, throws up the error following the code snippet:
    <sessionState
    mode="SQLServer"
    allowCustomSqlDatabase = "true"
    sqlConnectionString="Data Source=tcp:sql2k802.discountasp.net;Initial Catalog=SQL2008_623370_*****;User ID=SQL2008_623370_*****_user;Password=*****;"
    cookieless="false"
    timeout="15" />
    The error:
    Server Error in '/' Application.
    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.
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.Web.HttpException: 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.

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:

    [HttpException (0x80004005): 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.]
    System.Web.SessionState.SqlPartitionInfo.GetServerSupportOptions(SqlConnection sqlConnection) +1811821
    System.Web.SessionState.SqlPartitionInfo.InitSqlInfo(SqlConnection sqlConnection) +96
    System.Web.SessionState.SqlStateConnection..ctor(SqlPartitionInfo sqlPartitionInfo) +429
    System.Web.SessionState.SqlSessionStateStore.GetConnection(String id, Boolean& usePooling) +205
    System.Web.SessionState.SqlSessionStateStore.DoGet(HttpContext context, String id, Boolean getExclusive, Boolean& locked, TimeSpan& lockAge, Object& lockId, SessionStateActions& actionFlags) +134
    System.Web.SessionState.SqlSessionStateStore.GetItemExclusive(HttpContext context, String id, Boolean& locked, TimeSpan& lockAge, Object& lockId, SessionStateActions& actionFlags) +48
    System.Web.SessionState.SessionStateModule.GetSessionStateItem() +117
    System.Web.SessionState.SessionStateModule.BeginAcquireState(Object source, EventArgs e, AsyncCallback cb, Object extraData) +487
    System.Web.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +66
    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155


    Version Information: Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082
    ----

    Is this because the right Session State isn't installed on the server? Or am I doing something wrong, and the problem isn't with DiscountASP.net?
     
  2. Bruce

    Bruce DiscountASP.NET Staff

    did you request support to install the session schema on your Database yet?
     
  3. Thank you, I realized that shortly after I posted.
     

Share This Page