Post reply

Error: Max. No. of DBPROCESSes already allocated

  • September 13, 2011 at 7:38 am

    #256998

    Dear Fellows,

    I have a 3rd party application that runs daily, inserting data from a flat CSV file into SQL Server 2005 EE. Overnight this application began to output the error: "General SQL error. Maximum number of DBPROCESSes already allocated."

    sys.sp_configure N'user connections' outputs:

    0 minimum

    32767 maximum (same as @@MAX_CONNECTIONS)

    0 config_value

    0 run_value

    I don't know what is causing this error. I will be setting a perfmon collector set for tonight, initially to gauge logins, logouts, connections, transactions and batch requests per second. I'm perplexed by this error

    :w00t:

  • September 14, 2011 at 8:24 am

    #1381327

    For the record: the problem was with the 3rd party application. I restarted it and the problem is gone. But it's curious that SQL Server throws such error on these circumstances.

  • September 14, 2011 at 8:51 am

    #1381357

    That's not a SQL Server error. Hence it must have been coming from the app for some reason or other.

    SELECT * FROM sys.messages AS m WHERE text LIKE 'General SQL error%'

    0 row(s) returned

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply