- Community Home
- >
- Servers and Operating Systems
- >
- ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: Windows Management Instrumentation has stopped...
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-09-2017 06:17 AM
01-09-2017 06:17 AM
Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning value
does anybody now how to resolve this warning from WMI (Proliant DL 360e G8/Windows Server 2012 R2) . It is connected to WBEM providers and I dont want to see it in event log. I doubled the number handles per host but it happened again Error is :
Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning value. Quota: HandleCount Value: 4097 Maximum value: 4096 WMIPRVSE PID: 2852 Providers hosted in this process: C:\Program Files\HPWBEM\Server\dll\HPWmiCpuTEvt.dll, C:\Program Files\HPWBEM\Server\dll\HPWmiTestEvt.dll, C:\Program Files\HPWBEM\Server\dll\HPWmiDiskTEvt.dll, C:\Program Files\HPWBEM\Server\dll\HPWmiSensorEvt.dll, C:\Program Files\HPWBEM\Storage\dll\HPWMIFCA.dll, C:\Program Files\HPWBEM\Storage\dll\HPWMISA.dll
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-03-2017 06:45 AM
03-03-2017 06:45 AM
Re: Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning va
We are also seeing this on muliple servers, not just on one or two (ML310 Gen 8 v2, ProLiant DL380 Gen9, ProLiant ML150 Gen9, ProLiant DL380p Gen8)
we have the latest WBEM providers from HP installed, still having issues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-03-2017 10:47 AM
04-03-2017 10:47 AM
Re: Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning va
I am getting the same issue on a pair of Windows 2012R2 Clusters running on Proliant DL360p Gen 8 servers with Fibre channel cards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-16-2018 03:20 AM
03-16-2018 03:20 AM
Re: Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning va
Hello,
I see this post as - a pretty old one - without a solution.
I've the same issue on a fresh 2016 server
anyone?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-13-2018 01:56 AM
11-13-2018 01:56 AM
Re: Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning va
This is what I did on our servers, and that solved it.
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP