ASP.NET Login control bug or SQL 2005 bug?

Discussion in 'ASP .Net' started by RedEye, Dec 12, 2005.

  1. RedEye

    RedEye Guest

    Hello,

    I have been working on an ASP.NET application for the past 2 weeks and
    everything has been going fine. I am using the ASP.NET login controls to
    handle user logins and I'm using SQL 2005 Workgroup Edition for the backend.

    The problem I am have is for some reason the login control will no longer
    authenticate. I am using the same password as before and now it's not
    working.

    I have reset the password and still nothing. Nothing has changed in the
    application code or SQL since the last time I worked on the app. The only
    thing that has changed is I have restarted my system.

    I had this problem before in Beta 2 but this is the first time i've seen in
    the final version.

    Does anyone know what could cause this issue?

    Thanks,
    Red
    RedEye, Dec 12, 2005
    #1
    1. Advertising

  2. RedEye

    Jason Kester Guest

    How about option 3: "Your Bug".

    Chances are roughly zero that you've found a but in a major Microsoft
    product while using one of the most popular components in the intended
    manner. Step through your code and watch what happens when it goes
    wrong. Isolate that section into a small test page that so that you
    can demonstrate the problem is repeatable. Then post that code along
    with annotations to this group and maybe you'll get a helpful response.

    But in the future, try to avoid using the word "bug" in your subject
    line. Most of us don't even bother reading posts with subject lines
    like yours.

    Jason Kester
    Expat Software Consulting Services
    http://www.expatsoftware.com/
    Jason Kester, Dec 13, 2005
    #2
    1. Advertising

  3. RedEye

    Jason Kester Guest

    How about option 3: "Your Bug".

    Chances are roughly zero that you've found a bug in a major Microsoft
    product while using one of the most popular components in the intended
    manner. Step through your code and watch what happens when it goes
    wrong. Isolate that section into a small test page that so that you
    can demonstrate the problem is repeatable. Then post that code along
    with annotations to this group and maybe you'll get a helpful response.

    But in the future, try to avoid using the word "bug" in your subject
    line. Most of us don't even bother reading posts with subject lines
    like yours.

    Jason Kester
    Expat Software Consulting Services
    http://www.expatsoftware.com/
    Jason Kester, Dec 13, 2005
    #3
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Juan T. Llibre
    Replies:
    0
    Views:
    454
    Juan T. Llibre
    Jun 7, 2005
  2. Sql Agentman
    Replies:
    0
    Views:
    652
    Sql Agentman
    Jan 19, 2006
  3. =?Utf-8?B?c2NvdHRybQ==?=

    sql session state for .net v1.1/.net v2.0 and sql server 2005

    =?Utf-8?B?c2NvdHRybQ==?=, Feb 13, 2006, in forum: ASP .Net
    Replies:
    3
    Views:
    2,789
    Steven Cheng[MSFT]
    Feb 16, 2006
  4. XJ
    Replies:
    8
    Views:
    1,753
  5. Garry
    Replies:
    1
    Views:
    157
    MikeS
    Mar 28, 2006
Loading...

Share This Page