Error on SessionContext.Current

During my login script, I get the following error on SessionContext.Current. I cannot seem to find any documentation on this function. Is it possible that this is caused by a configuration issue with my system or is there something I have to do before I call this function?

System.InvalidOperationException was unhandled by user code
Message="Operation is not valid due to the current state of the object."
Source="iManage.WorkSite.Web"
StackTrace:
at iManage.WorkSite.Web.SessionState.get_Provider()
at iManage.WorkSite.Web.SessionContext.get_Current()
at MasterPage.btnLogin_Click(Object sender, ImageClickEventArgs e) in c:\Project\TTA\MasterPage.master.cs:line 48
at System.Web.UI.WebControls.ImageButton.OnClick(ImageClickEventArgs e)
at System.Web.UI.WebControls.ImageButton.RaisePostBackEvent(String eventArgument)
at System.Web.UI.WebControls.ImageButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Find more posts tagged with

Comments

dabird

Can you explain what specifically you are trying to accomplish in your app? Clearly you are not going through our login page, and I am wondering why you are trying to use SessionContext.

The SessionState.Provider has not been initialized in your code, and this is what caused the error. I wouldn't expect you to know that, as this is private initialization that WSW handles when the app starts. We don't provide documentation on this.

If you can explain what you are trying to accomplish, perhaps I can point you in a different direction or give you the necessary code to properly initialize SessionContext.

Joe_Purdom

We are using our own login which is found on each page. The source code was pulled from a previous version of the application. The original source works on the internet, however it does not work on my system. So, I can only assume that there is an issue with my configuration.

dabird

In btnLogin_Click event, you need to initialize the SessionState before using it:

C# example
using iManage.WorkSite.Web;


SessionState.Init(SessionState.Mode.AspNet);

Joe_Purdom

Thank you, that worked. Although I had to add a check to see if SessionState.Provider was null since I only needed to initialize it when the provider is null otherwise the code you gave me throws an error.

Joe_Purdom

So I had to modify what I just posted. Here is my full login script as it stands now.

protected void btnLogin_Click(object sender, ImageClickEventArgs e)
{
// Get the sessioncontext object
SessionContext sessionContext;

try
{
sessionContext = SessionContext.Current;
}
catch
{
SessionState.Init(SessionState.Mode.AspNet);
sessionContext = SessionContext.Current;
}

// Query the timezone from the browser (see the form var in our default.aspx),
// Set it to the SessionContext object
sessionContext.TimezoneOffset = 5; //int.Parse(timezoneInfo);

string servername = ConfigurationManager.AppSettings["servername"];
string database = ConfigurationManager.AppSettings["database"];
string webDatabase = ConfigurationManager.AppSettings["webDatabase"];
string username = txtUID.Text;
string password = txtPWD.Text;
string target = ConfigurationManager.AppSettings["target"];

try
{
// This internally calls NRTSession.Login
sessionContext.ServerName = servername;
sessionContext.Login(username, password, false); //<-- Line #73

// Get Worksite specific principle object, and change HttpContext user to Worksite user.
HttpContext.Current.User = new WorkSitePrincipal(new WorkSiteIdentity(sessionContext));

// If applicable, set these options for 508 compliance and multi-language cookies.
UserOptions.SetEnable508MenusCookie(sessionContext.UserSettings.Section508MenuEnabled);
UserOptions.SetPreferredLanguageCookie(sessionContext.UserSettings.PreferredLanguage);

// Change the current culture to user specific culture (for date and time)
Thread.CurrentThread.CurrentCulture = new CultureInfo(Localization.Current.LCID);
sessionContext.Dms.LocaleID = Localization.Current.LCID;

// write cookie with company (pulled from userid --> c4alias)
// read from profile.js

string strCookieName = "Company";
string strCookieExpires = "365";

// create user object
//IDSNWSW.Components.User user = new IDSNWSW.Components.User();
IDSN.Components.User user = new IDSN.Components.User();
string strCookieValue = user.getCompanyAlias(username);

double dblExpires = Convert.ToDouble(strCookieExpires);
HttpCookie objCookie =
HttpContext.Current.Response.Cookies[strCookieName];
if (objCookie == null)
{
objCookie = new HttpCookie(strCookieName, strCookieValue);
objCookie.Expires = DateTime.Now.AddDays(dblExpires);
HttpContext.Current.Response.Cookies.Add(objCookie);
}
else
{
if (!objCookie.HasKeys)
{
objCookie.Value = strCookieValue;
objCookie.Expires = DateTime.Now.AddDays(dblExpires);
HttpContext.Current.Response.Cookies.Add(objCookie);
}
}

// Now, you may redirect to appropriate destination
HttpContext.Current.Response.Redirect(target);
}

catch (Exception ex)
{
//*** DEBUG - show error
//lblLogin.Text = ex.StackTrace;
//show logon failed message
//lblLogin.Visible = true;
}
}

My new error occurs on Line #73, sessionContext.Login().

System.NullReferenceException was caught
Message="Object reference not set to an instance of an object."
Source="iManage.WorkSite.Web"
StackTrace:
at iManage.WorkSite.Web.WebSettings.GetImanageSetting(String key)
at iManage.WorkSite.Web.WebSettings.get_GlobalOptionFilePath()
at iManage.WorkSite.Web.Options.Load()
at iManage.WorkSite.Web.Options.get_Current()
at iManage.WorkSite.Web.SessionContext.get_affinityCookieBuilder()
at iManage.WorkSite.Web.SessionContext.Login(String userID, String password, Boolean requireAdminAuthentication)
at MasterPage.btnLogin_Click(Object sender, ImageClickEventArgs e) in c:\Project\TTA\MasterPage.master.cs:line 73

dabird

It looks like you are missing the iManage.WorkSite config section in your web.config, or more specifically, the OptionsPath setting:


<iManage.WorkSite>
 <!--
 iManage WorkSite related setting keys and values:
 SmtpServer: The host name of the SMTP server used to send notification. By default, localhost is used.
 Server:  The iManage DMS server name.
 OptionsPath: The file path where options.xml file is stored. 
 -->
 <settings>
  <add key="SmtpServer" value=""/>
  <add key="server" value="dms"/>
  <add key="OptionsPath" value="data\options.xml"/>
 </settings>
</iManage.WorkSite>

Joe_Purdom

When I include that section of the Web.config, the application fails to compile.

I get an error, Unrecognized Config Section iManage.WorkSite.

dabird

Since this is your custom app (which I forgot about in my previous post), you need to specify that you are including a special config section and bind it to a .NET handler. This needs to go above the iManage.WorkSite config section.


<configSections>
 <sectionGroup name="iManage.WorkSite">
  <section name="settings" type="System.Configuration.NameValueSectionHandler"/>
 </sectionGroup>
</configSections>

Joe_Purdom

Thank you for your help.

My login script no longer throws any errors. However when the page is redirected to WorkSite/scripts/home.aspx the login credentials do not get passed on and I am always kicked back to WorkSite/default.aspx.

dabird

My login script no longer throws any errors. However when the page is redirected to WorkSite/scripts/home.aspx the login credentials do not get passed on and I am always kicked back to WorkSite/default.aspx.

I think the best approach is is to write a custom authentication module. This is how we recommend that you handle custom login routines in 8.1 and forward. Check out the webcast that explains what you need to do.

The other option is to contact DevSupport. I highly recommend that you provide a detailed explanation of what you are trying to accomplish by having a custom login on every page, along with pertinent screen shots so that the dev team can help you on this. Also provide the version of WSW that you are using.

Regards,
dabird

dabird

Please submit your ASPX page along with a description and screen shots to demonstrate how it worked in 8.0 to DevSupport. I think that you need to use a custom authentication module, but without looking at details, I can't say for certain.

Regards,
dabird

Joe_Purdom

We got it working, it turns out that the code we were given was written to run against 8.1, however we were still trying to use 8.01. Installing the right version fixed all our problems. Thank you.