Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Stephen Gornick

My feedback

  1. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Stephen Gornick commented  · 

    This issue persists, using the most current ODBC driver v17 (v17.4.2). Same thing happens whether 32 bit or 64 bit Office 365 (and thus, corresponding (32 bit or 64 bit) version of ODBC driver).

    An error occurred while saving the comment
    Stephen Gornick commented  · 

    I had first posted this as a question on the Technet Forum, but was encouraged to file a bug report on it here.

    Technet forum post:

    - https://social.technet.microsoft.com/Forums/en-US/bf17349d-9021-4523-98d9-a269db874c61

    Stephen Gornick shared this idea  · 
  2. 12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Virtual Machines » Windows  ·  Flag idea as inappropriate…  ·  Admin →
    Stephen Gornick supported this idea  · 
  3. 18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Virtual Machines  ·  Flag idea as inappropriate…  ·  Admin →
    Stephen Gornick supported this idea  · 
  4. 32 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Virtual Machines  ·  Flag idea as inappropriate…  ·  Admin →
    Stephen Gornick supported this idea  · 
  5. 45 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Virtual Machines  ·  Flag idea as inappropriate…  ·  Admin →
    Stephen Gornick supported this idea  · 
  6. 45 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Virtual Machines  ·  Flag idea as inappropriate…  ·  Admin →
    Stephen Gornick supported this idea  · 
  7. 18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Virtual Machines » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature

    An error occurred while saving the comment
    Stephen Gornick commented  · 

    Same issue here with Windows Server 2016 using other Azure VM sizes as well.

    DS1_v2 (3.5 GB Ram), Windows Update would stop with an error, and Event Viewer shows in the Windows System Log:

    Event 2004, Resource-Exhaustion-Detector

    And the Application log Microsoft-Windows-WindowsUpdateClient/Operational
    would have:

    Event 25, WindowsUpdateClient
    "Windows Update failed to check for updates with error 0x8024000E."

    After setting Virtual Memory to a "Custom size" of 4GB, Windows Updates installed without getting the Resource-Exhaustion-Detector events anymore.

    Also, I could instead STOP (deallocate) the VM, change the VM size to DS2_v2 (7 GB), and the issue went away without having to adjust the Virtual Memory configuration.

    Stephen Gornick supported this idea  · 

Feedback and Knowledge Base