none
Http test request failed, error code is 8

    Question

  • Hi,

    I am facing the issue of "Call to HttpSendRequestSync failed for port 80 with an error code, Http test request failed, error code is 8" on SCCM 2007 primary server and because of this getting error in wsus i.e "System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full" and unable to open WSUS console.

    But this is getting resolved after restarting the server.

    So please help me to understand root cause of this. Below is error snap.



    • Edited by Parag_M Friday, June 27, 2014 8:22 AM
    Friday, June 27, 2014 8:20 AM

All replies

  • Hello !

    This error is due to a lack of memory.

    You have to verify the used RAM level and increase it if possible.

    Hope this helps.


    Note: This posting is provided 'AS IS' with no warranties or guarantees, and confers no rights. Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions.

    Friday, June 27, 2014 9:06 AM
  • How much RAM it is required?

    Currently having 12GB.

    This issue is happening recently, earlier it was proper on same RAM.

    So how can we say this is only because of RAM issue.

    Friday, June 27, 2014 10:12 AM
  • Where is SQL install? Have you cap the ram that SQL will consume?

    Have you looked at the perf counter?

    How many pcs are you managing?



    • Edited by Garth JonesMVP Friday, June 27, 2014 11:45 AM sig messed up.
    Friday, June 27, 2014 10:51 AM
  • SQL is installed locally.

    How to cap the RAM?

    What I have to monitor in perf counter?

    Managing around 5000 machines.

    Friday, June 27, 2014 11:27 AM
  • 12 GB is a bit lite for 5000 PCs, 16 GB would be better.

    Capping SQL

    http://www.bauer-power.net/2011/01/how-to-set-memory-cap-for-microsoft-sql.html#.U61Zlo0U-po

    There standard three counters would tell you a lot about your server. CPU, RAM and IO.


    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Friday, June 27, 2014 11:49 AM
  • 12 GB is a bit lite for 5000 PCs, 16 GB would be better.

    Capping SQL

    http://www.bauer-power.net/2011/01/how-to-set-memory-cap-for-microsoft-sql.html#.U61Zlo0U-po

    There standard three counters would tell you a lot about your server. CPU, RAM and IO.


    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    32 would be even better. :-)

    I'm running 24Gb for 1000 computers.


    John Marcum | Microsoft MVP - Enterprise Client Management
    My blog: System Center Admin | Twitter: @SCCM_Marcum | Linkedin: John Marcum

    Friday, June 27, 2014 12:46 PM
    Moderator
  • Dear Experts,

    Are you sure that it is only issue of RAM? Since we are also having 30 secondary servers where WSUS is installed and there RAM is 4/8 GB but there is no such type of issue expect one site.

    Apart from this WSUS from CAS site is also working fine but is having 16 GB of RAM.

    My point is if this issue is only of RAM then why we are facing this issue now only, earlier it was working on same RAM. We have installed SCCM 2/3 years back.

    Please suggest.

    Friday, June 27, 2014 5:43 PM
  • It can be a lot so things, did you cap SQL RAM?

    Did you look at Perfmon yet? What did it say??


    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ


    • Edited by Garth JonesMVP Friday, June 27, 2014 7:06 PM Remove extra CM12 stuff. :-)
    Friday, June 27, 2014 6:19 PM
  • You run are Running a CAS for 5000 Device?? You do know that a CAS is indented for 100,000 PCs.

    It can be a lot so things, did you cap SQL RAM?

    Did you look at Perfmon yet? What did it say??


    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ


     "....on SCCM 2007 primary server and because of this getting error in.."

    John Marcum | Microsoft MVP - Enterprise Client Management
    My blog: System Center Admin | Twitter: @SCCM_Marcum | Linkedin: John Marcum


    Friday, June 27, 2014 6:48 PM
    Moderator
  •  "....on SCCM 2007 primary server and because of this getting error in.."


    oops.. go CM12 on the brain. Remove the bit about CM12.

    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Friday, June 27, 2014 7:07 PM
  • No I haven't cap SQL RAM.

    I am yet to check perfmon logs, I will check the same and get back.

    As all of you saying its a RAM issue then if I want to increase the RAM then what will be recommended RAM?

    Currently it is having 12 GB RAM for around 5000 clients. Server OS is Windows Server 2008.

    Please suggest.

    Sunday, June 29, 2014 5:16 AM
  • No I haven't cap SQL RAM.

    I am yet to check perfmon logs, I will check the same and get back.

    As all of you saying its a RAM issue then if I want to increase the RAM then what will be recommended RAM?

    Currently it is having 12 GB RAM for around 5000 clients. Server OS is Windows Server 2008.

    Please suggest.


    Why don't you start with the two easy items that I have already suggested and then move on from there.

    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Sunday, June 29, 2014 10:12 AM
  • That means your suggested to CAP the SQL memory as per above link and increase the RAM to 16 GB?
    Monday, June 30, 2014 12:59 PM
  • That means your suggested to CAP the SQL memory as per above link and increase the RAM to 16 GB?

    Let put it this way, If you can increase the RAM to 2TB of RAM and if you don't CAP the RAM for SQL, SQL will grab it all the RAM and starve the Site Server of RAM. And the problem will still exist.

    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Monday, June 30, 2014 1:10 PM
  • Sorry for late reply, but actually I was in 3 days continuous travelling and after that I felt ill.

    As I checked on SQL server memory, its has set to 4096 MB (maximum).

    But still issue is there.

    Is there any other checkpoint?

    Friday, July 04, 2014 11:57 AM
  • For 12 Gb of RAM SQL should be cap at 8GB, leaving 4 GB for the system and CM12.

    Have you look at Perfmon yet? What does it say?


    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Friday, July 04, 2014 11:59 AM
  • I set the 8 GB cap but it didn't help. Still issue the there.

    Not understanding what to check in perfmon. Please help. Issue is happening in some night time.

    Monday, July 07, 2014 6:12 AM
  • I set the 8 GB cap but it didn't help. Still issue the there.

    Not understanding what to check in perfmon. Please help. Issue is happening in some night time.

    Start with the basics, CPU, ram, page file, NIC. Once you get an idea as to what is causing the problem to can move on from there.

    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Monday, July 07, 2014 10:00 AM
  • Is there any tool which can continuously monitor CPU , RAM utilization and gives its diagnostic or report?

     
    Monday, July 07, 2014 5:10 PM
  • Is there any tool which can continuously monitor CPU , RAM utilization and gives its diagnostic or report?

     

    Yes, IMO, SCOM is the best tool to manage any Windows environment.

    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Monday, July 07, 2014 6:48 PM
  • I am facing the same issue on primary server and one of the secondary server. It has been observed that LSASS.EXE (local security authority process) process utilizing quit high memory and its Handles are getting continuously increasing. Reaches around 90000.

    Will this affect the site server?

    If yes then how to control this. Please suggest.

    Sunday, July 13, 2014 3:55 PM