locked
Error 17827: Failure while attempting to encrypt a password RRS feed

  • Question

  • Getting this error every few days:

    <local machine="">Sep 11 2012 2:49PM|Error: 17827, Severity: 20, State: 1. Sep 11 2012 2:49PM|There was a failure while attempting to encrypt a password. The connection has been closed.</local>

    This is SQL Server 2005 SP3 Enterprise x64 running on Windows 2003 x64.

    Not much info on this via Google, other than resource constraints. Perfmon trace shows normal readings at time of error. Any ideas on fixing it would be welcome.


    Karl Maher


    • Edited by Karl Maher Thursday, September 13, 2012 5:40 PM
    • Moved by Tom Phillips Thursday, September 13, 2012 8:55 PM Possibly better answer from security forum (From:SQL Server Database Engine)
    Thursday, September 13, 2012 5:23 PM

All replies

  • But at what point the error happens?

    Roberson Ferreira - Database Developer
    Acesse: www.robersonferreira.com.br
    Email: contato@robersonferreira.com.br

    Se esta sugestão for útil, por favor, classifique-a como útil.
    Se ela lhe ajudar a resolver o problema, por favor, marque-a como Resposta.

    Thursday, September 13, 2012 10:58 PM
  • Karl, see: http://www.sqlservercentral.com/Forums/Topic888252-391-1.aspx

    Roberson Ferreira - Database Developer
    Acesse: www.robersonferreira.com.br
    Email: contato@robersonferreira.com.br

    Se esta sugestão for útil, por favor, classifique-a como útil.
    Se ela lhe ajudar a resolver o problema, por favor, marque-a como Resposta.

    Thursday, September 13, 2012 11:05 PM
  • Roberson, thanks for responding. I saw that post, which is why I ran a perfmon trace. This is a very busy server -- CPU was at 100% for about six hours during the 24-hour trace. However, the error occurred when the server wasn't maxed out. 

    Karl Maher

    Friday, September 14, 2012 3:55 PM
  • Hi Karl Maher,

    How many connections are being made to your SQL Server 2005 instance? Although there is no hard limit to connections, there are resource limits on memory and once those are used up, you will have problems. Because the error:17827 I see in TechNet in SQL Server 2000 means: “The maximum number of '%1!ld!' remote connections is currently in use”.

    Can you check how many user connections during this error is generated and also find out what kind of processes are running?

    Based on that many people have met this error:17827 about SQL Server 2005 and wait for the resolution, so if it still cannot fix this error, I would recommend to submit it to the Microsoft Connect: https://connect.microsoft.com/SQLServer/Feedback. This connect site will serve as a connecting point between you and Microsoft, and ultimately the large community for you and Microsoft to interact with. Your feedback enables Microsoft to offer the best software and deliver superior services, meanwhile you can learn more about and contribute to the exciting projects on Microsoft Connect.

    Regards,
    Amy Peng


    Amy Peng

    TechNet Community Support

    Tuesday, September 18, 2012 2:38 AM
  • Hi Amy. Thanks for your input. SQL Server connections were at 570 when the error was generated, with about 650 batch requests/sec.

    Here's the process list:


    Image Name                     PID Session Name        Session#    Mem Usage
    ========================= ======== ================ =========== ============
    System Idle Process              0 Console                    0         24 K
    System                           4 Console                    0        256 K
    smss.exe                       864 Console                    0        732 K
    csrss.exe                      532 Console                    0      5,376 K
    winlogon.exe                   624 Console                    0     17,564 K
    services.exe                   728 Console                    0     60,708 K
    lsass.exe                      740 Console                    0     50,816 K
    svchost.exe                   1044 Console                    0      4,636 K
    svchost.exe                   1312 Console                    0      7,260 K
    svchost.exe                   1368 Console                    0      8,152 K
    svchost.exe                   1512 Console                    0      5,584 K
    EmcPowSrv.exe                 1552 Console                    0      9,092 K
    svchost.exe                   1564 Console                    0     29,820 K
    spoolsv.exe                   2028 Console                    0      7,792 K
    racsvc.exe                     256 Console                    0      2,920 K
    msdtc.exe                      340 Console                    0      7,284 K
    3dnslsnr.exe                   588 Console                    0      4,792 K
    AeXNSAgent.exe                 668 Console                    0      8,216 K
    dsm_sa_eventmgr32.exe          896 Console                    0      5,688 K
    dsm_sa_datamgr32.exe           744 Console                    0     16,116 K
    dmexplorer.exe                1004 Console                    0     17,340 K
    svchost.exe                   1148 Console                    0      3,796 K
    mr2kserv.exe                  1180 Console                    0      3,172 K
    MsDtsSrvr.exe                 1244 Console                    0     33,512 K
    msftesql.exe                  1776 Console                    0     11,084 K
    sqlservr.exe                  1836 Console                    0  3,225,024 K
    sqlservr.exe                  1924 Console                    0 25,406,680 K
    nimbus.exe                     480 Console                    0      3,328 K
    NTRtScan.exe                   604 Console                    0      8,196 K
    controller.exe                1052 Console                    0      8,124 K
    dsm_om_shrsvc32.exe           1700 Console                    0      6,024 K
    portmap.exe                   1728 Console                    0      2,776 K
    svchost.exe                    452 Console                    0      8,768 K
    dsm_om_connsvc32.exe          2080 Console                    0     36,548 K
    SnareCore.exe                 2104 Console                    0     11,084 K
    sqlbrowser.exe                2160 Console                    0     10,052 K
    TmListen.exe                  2364 Console                    0      7,368 K
    lhm.exe                       2660 Console                    0     29,120 K
    spooler.exe                   1080 Console                    0      6,144 K
    hdb.exe                       3200 Console                    0      5,496 K
    ntevl.exe                     3348 Console                    0     31,888 K
    ntservices.exe                3604 Console                    0      4,312 K
    processes.exe                 3692 Console                    0      6,068 K
    sqlserver_monitor.exe         3820 Console                    0      9,488 K
    cdm.exe                       3948 Console                    0      8,664 K
    vxsicld.exe                   3952 Console                    0     20,876 K
    WideIPLsnr.exe                3416 Console                    0      4,660 K
    msftesql.exe                  3484 Console                    0      6,176 K
    qlremote.exe                  3500 Console                    0     10,480 K
    SQLAGENT90.EXE                3528 Console                    0     13,924 K
    wmiprvse.exe                  3880 Console                    0     23,096 K
    svchost.exe                   4276 Console                    0      7,424 K
    halrun.exe                    4488 Console                    0     40,968 K
    halrun.exe                    4804 Console                    0     34,116 K
    wmiprvse.exe                  4888 Console                    0      7,972 K
    CNTAoSMgr.exe                 1280 Console                    0      4,088 K
    AeXNSAgentHostSurrogate32     4876 Console                    0     19,808 K
    logon.scr                     4592 Console                    0      2,880 K
    SQLAGENT90.EXE                6100 Console                    0      7,028 K
    bpinetd.exe                   5660 Console                    0      9,908 K
    pbx_exchange.exe              2548 Console                    0      6,816 K
    bpjava-msvc.exe               7072 Console                    0      7,572 K
    wscript.exe                   6032 Console                    0     10,464 K
    snmp.exe                      7152 Console                    0      9,164 K
    snmp.exe                      3332 Console                    0      9,352 K
    dbbackex.exe                  6392 Console                    0     27,712 K
    dbbackex.exe                  6204 Console                    0     23,164 K
    bpcd.exe                      6644 Console                    0      8,596 K
    csrss.exe                     1920 RDP-Tcp#29                 1      4,752 K
    winlogon.exe                  5524 RDP-Tcp#29                 1      3,536 K
    rdpclip.exe                   5144 RDP-Tcp#29                 1      4,936 K
    explorer.exe                  5984 RDP-Tcp#29                 1     13,324 K
    BacsTray.exe                  4636 RDP-Tcp#29                 1      3,088 K
    EmcPowMon.exe                 3860 RDP-Tcp#29                 1      3,032 K
    PccNTMon.exe                  6504 RDP-Tcp#29                 1      2,484 K
    AeXAgentUIHost.exe            3344 RDP-Tcp#29                 1      7,764 K
    cmd.exe                       5840 RDP-Tcp#29                 1      2,456 K
    tasklist.exe                  5560 RDP-Tcp#29                 1      5,316 K


    Karl Maher

    Tuesday, September 18, 2012 2:53 PM
  • Are you runing two sql instances on one server?

    sqlservr.exe                  1836 Console                    0  3,225,024 K
    sqlservr.exe                  1924 Console                    0 25,406,680 K

    Share the user connection on both instances. Along with min & max memory setting on both instances. Out of 2 which instacnes in consuming high CPU.

    Also share the total memory avilable on server.


    Regards,
    Rohit Garg
    (My Blog)
    This posting is provided with no warranties and confers no rights.
    Please remember to click Mark as Answerand Vote as Helpfulon posts that help you. This can be beneficial to other community members reading the thread.


    • Edited by RohitGarg Tuesday, September 18, 2012 6:56 PM
    Tuesday, September 18, 2012 6:56 PM
  • Hmmm. So you're saying go back to default memory settings on both instances? (BTW, the server with 25gb of memory uses most cpu and got the error).

    Karl Maher

    Tuesday, September 18, 2012 7:40 PM
  • No on default settings. Its recomemded to configure min & max memory settings. share current min & max memory setting on both instances.

    Regards,
    Rohit Garg
    (My Blog)
    This posting is provided with no warranties and confers no rights.
    Please remember to click Mark as Answerand Vote as Helpfulon posts that help you. This can be beneficial to other community members reading the thread.


    • Edited by RohitGarg Tuesday, September 18, 2012 7:47 PM
    Tuesday, September 18, 2012 7:46 PM
  • OK, misunderstood.

    Instance A
    Max: 24000
    Min: 0
    User connections: 780

    Instance B
    Max: 3000
    Min: 0
    User connections: 65

    Also, Available memory steady at 2.5gb.


    Karl Maher


    • Edited by Karl Maher Tuesday, September 18, 2012 7:59 PM
    Tuesday, September 18, 2012 7:58 PM
  • Your error shows an some how issue related to resoruces. Although that is not directly your error, it may be a hint as to the
    underlying problem.

    As mention by Amy, you can can submit your issue & feebback.

    If you are continously getting this error, Then call Microsoft product support team for support. Also suggest to apply SP4 before raising a case with MS PSS team.


    Regards,
    Rohit Garg
    (My Blog)
    This posting is provided with no warranties and confers no rights.
    Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.

    Tuesday, September 18, 2012 8:39 PM