locked
SQL Server Aborts Attempt to Drop SQL Login with Error 4502 RRS feed

  • Question

  • When attempting to drop a SQL Server login (with no database mappings or server role membership), has anyone ever gotten the following error and had the action aborted:

    Msg 4502, Level 16, State 1, Procedure sp_checkusernotloggedin, Line 14
    View or function 'sys.dm_exec_sessions' has more column names specified than columns defined.
    Msg 0, Level 20, State 0, Line 0
    A severe error occurred on the current command.  The results, if any, should be discarded.

    I'm running 64-bit SQL Server 2005 Standard Edition (9.00.1399.06). I'm executing the following statement:

    DROP LOGIN [Foo];
    

    Cheers,
    CA


    Adam
    Thursday, October 20, 2011 8:07 PM

Answers

  • 9.00.1399.06! That's SQL 2005 RTM! Download and install Service Pack 4. I don't know for a fact, but I would expect that to resolve the issue.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
    • Proposed as answer by Peja Tao Friday, October 21, 2011 1:57 AM
    • Marked as answer by Peja Tao Wednesday, October 26, 2011 7:59 AM
    Thursday, October 20, 2011 9:41 PM

All replies

  • 9.00.1399.06! That's SQL 2005 RTM! Download and install Service Pack 4. I don't know for a fact, but I would expect that to resolve the issue.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
    • Proposed as answer by Peja Tao Friday, October 21, 2011 1:57 AM
    • Marked as answer by Peja Tao Wednesday, October 26, 2011 7:59 AM
    Thursday, October 20, 2011 9:41 PM
  • Erland you're a wise man. I haven't tried the idea yet, but I've got wheels in motion to apply a service pack. I'll let you know how things work out.


    Adam
    Thursday, October 20, 2011 9:50 PM
  • Haven't forgotten to give an update whether this was the solution or not.

    The upgrade has been scheduled, but it won't take place for a few more days. I'll follow-up once I know if this resolved the problem (though I believe it will).


    Adam
    Wednesday, October 26, 2011 1:37 PM
  • Applying SQL Server Service Pack 4 corrected the issue. Thanks Erland!
    Adam
    Thursday, October 27, 2011 3:14 PM