none
.net and sql performance RRS feed

  • Question

  • We are experiecing serious performance issues with one of our applications.  It seems to cause high cpu utilization on the sql server but I'm not sure that is where the problem lies.  I think we have an issue with .net or the IIS config.  Below is the error that users get frequently while working in the application.  We are running with .net 1.1.4322.2443 and IIS 6 on a windows 2003 server.  It is connecting to a seperate sql server that has 48gb of ram and 2 6 core processors.   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.Web.HttpException: Server Too Busy

    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:

    [HttpException (0x80004005): Server Too Busy]
      System.Web.HttpRuntime.RejectRequestInternal(HttpWorkerRequest wr) +148
    


    Version Information: Microsoft .NET Framework Version:1.1.4322.2443; ASP.NET Version:1.1.4322.2470

    Any suggestions on this would be great!  If this is not the correct forum please let me know.

    Thanks,

     

    Server Error in '/' Application.

    Server Too Busy

     

    • Moved by Bob Beauchemin Friday, February 18, 2011 9:42 PM Moving to more relevent forum. Even better if you repost to ASP.NET forums (From:.NET Framework inside SQL Server)
    Friday, February 18, 2011 7:59 PM

Answers

  • Check http://forums.asp.net/t/391549.aspx

    This is an asp.net error, not an ADO.Net one. I suggest you to visit forums.asp.net if you need further assistance on the question.



    The following is signature, not part of post
    Please mark the post answered your question as the answer, and mark other helpful posts as helpful, so they will appear differently to other users who are visiting your thread for the same problem.
    Visual C++ MVP
    Friday, February 18, 2011 11:09 PM
  • SQL Server performance problems can often be the cause of IIS issues. Applications calling into SQL Server wait for results. If these take too long, IIS times out and can cause the application to fail. I suspect this is indeed a SQL Server problem.

    There are a myriad of issues that can cause SQL Server performance issues:

    • Missing or incorrect indexes
    • Challenged query design as when fetching too many rows
    • Hardware contention as when there is not enough RAM to cache the data
    • Other competing services
    • Lock contention
    • (and much more)

     


    __________________________________________________________________
    William Vaughn
    Mentor, Consultant, Trainer, MVP
    http://betav.com
    http://betav.com/blog/billva
    http://www.hitchhikerguides.net

    “Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)”

    Please click the Mark as Answer button if a post solves your problem!

    Monday, February 21, 2011 6:34 AM
    Moderator

All replies

  • Check http://forums.asp.net/t/391549.aspx

    This is an asp.net error, not an ADO.Net one. I suggest you to visit forums.asp.net if you need further assistance on the question.



    The following is signature, not part of post
    Please mark the post answered your question as the answer, and mark other helpful posts as helpful, so they will appear differently to other users who are visiting your thread for the same problem.
    Visual C++ MVP
    Friday, February 18, 2011 11:09 PM
  • SQL Server performance problems can often be the cause of IIS issues. Applications calling into SQL Server wait for results. If these take too long, IIS times out and can cause the application to fail. I suspect this is indeed a SQL Server problem.

    There are a myriad of issues that can cause SQL Server performance issues:

    • Missing or incorrect indexes
    • Challenged query design as when fetching too many rows
    • Hardware contention as when there is not enough RAM to cache the data
    • Other competing services
    • Lock contention
    • (and much more)

     


    __________________________________________________________________
    William Vaughn
    Mentor, Consultant, Trainer, MVP
    http://betav.com
    http://betav.com/blog/billva
    http://www.hitchhikerguides.net

    “Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)”

    Please click the Mark as Answer button if a post solves your problem!

    Monday, February 21, 2011 6:34 AM
    Moderator