Sentinel Hasp Driver Windows Server 2008

Sentinel Hasp Driver Windows Server 2008Sentinel Hasp Driver Windows Server 2008

I have a Windows Server 2008 R2 running under a VMWare vSphere 4.0. Recenty it has been slowly losing memory to the 'Proc' pool tag.

Namely, every time an application is started, 2656 bytes are lost forever to that pool tag. Checked by 'poolmon'. Eventually (like, once every 15-20 days) the server becomes starved for resources and can't do its job any more until it is restarted. At the same time I'm observing a steady increase in the number of process handles active. Checked by 'handles -s'. Bluetooth Suite Win7 Download there. Checking the long handles list mostly points to csrss.exe, MonitoringHost.exe (SCOM) and an instance of svchost hosting DcomLaunch, PlugPlay and Power as owning the most process handles.

The server has all the latest updates. The software installed is Veeam Backup & Replication along with SQL Server 2008 R2 and two monitoring agents - one for SCOM 2007 and one for Zabbix. Also Symantec Backup Exec System Recovery is present.

This error 'HASP not found (-10)' has been encountered when installing the License Manager on Windows Server 2008 R2 Standard. I installed the latest drivers posted on the Safenet website (Sentinel HASP/LDK Windows GUI Run-time Installer). Then installed the HASP LM 8.32. Sentiel customer.

I've already studied numerous KBs, most of which are either inapplicable or point to hotfixes already present on the server. The one about MonitoringHost.exe consuming massive amounts of CPU too.

The same problem was present on another server, but has been resolved by disabling diagnostic logging for SCOM and updating Sentinel HASP dirvers to the latest version. The same solution doesn't help in this case, though, partially because I don't have HASP drivers on this one (and I'm not sure installing them will be helpful). Multiple other 2008 R2 Servers under vSphere 4.0 work fine without leaking memory too. Could anyone point me in the right direction on this? How do I find the original source of problem and patch up the leak? Smith And Wesson 9mm Model 915 Owners Manual.

I have a Windows Server 2008 R2 running under a VMWare vSphere 4.0. Recenty it has been slowly losing memory to the 'Proc' pool tag. Namely, every time an application is started, 2656 bytes are lost forever to that pool tag. Checked by 'poolmon'. Eventually (like, once every 15-20 days) the server becomes starved for resources and can't do its job any more until it is restarted.

At the same time I'm observing a steady increase in the number of process handles active. Checked by 'handles -s'. Checking the long handles list mostly points to csrss.exe, MonitoringHost.exe (SCOM) and an instance of svchost hosting DcomLaunch, PlugPlay and Power as owning the most process handles.

This entry was posted on 11/1/2017.