Forums & Blog

A SmarterTools-sponsored community.
Welcome to Forums & Blog Sign in | Join | Help
in Search

[bug] impersonate user returns error

Last post 08-29-2008 7:24 PM by pod. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 08-27-2008 12:56 PM

    • sbwh
    • Top 150 Contributor
    • Joined on 05-01-2008
    • Posts 60

    [bug] impersonate user returns error

    Sincethe latest update (4.0.3159). This worked fine before the update

    trying to impersonate a user returns the following error:

     

    Server Error in '/' Application.

    Object reference not set to an instance of an object.

    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.NullReferenceException: Object reference not set to an instance of an object.

    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:

    [NullReferenceException: Object reference not set to an instance of an object.]
       SSWeb.Admin.Popups.frmImpersonateUser.btnOK_Click(Object sender, EventArgs e) +95
       SmarterTools.Web.Controls.ButtonBarIcon.RaisePostBackEvent(String eventArgument) +61
       System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11
       System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +177
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1746
    


    Version Information: Microsoft .NET Framework Version:2.0.50727.1434; ASP.NET Version:2.0.50727.1434

  • 08-29-2008 7:24 PM In reply to

    • pod
    • Top 75 Contributor
    • Joined on 02-19-2004
    • Posts 122

    Re: [bug] impersonate user returns error

    We are also getting this same error!

Page 1 of 1 (2 items)