HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- SIM 5.2 and ISEE : high CPU usage of Wscript.exe
Server Management - Systems Insight Manager
1833566
Members
3275
Online
110061
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
- Report Inappropriate Content
03-12-2008 11:11 PM
03-12-2008 11:11 PM
SIM 5.2 and ISEE : high CPU usage of Wscript.exe
Hello.
Since the installation of SIM 5.2, I noticed that the ISEE_SWM_CommandQueue service was not starting. I found the Srvany.exe file was missing in C:\PROGRA~1\HEWLET~1\SWMAgent\SWM\CLI\srvany.exe. I copied it from a different place and the service started successfully.
Since then, the cpu is all the time above 90%, mostly used bu a Wscript.exe process. And Wscript is a parameter passed to the Srvany.exe in the registry.
If I stop the two ISEE services, the CPU usage is normal. I changed the start mode of these services to manual and something (mxdomainmgr ?) changed the start mode of ISEE_CMS_SwmAgent to automatic and started it.
Can someone explain me what is hapenning ? I suppose I must reinstall ISEE.
Is this issue has something to see with my other post about the tempoutputxxx.entitlement_* files filling the temp folder ?
Thank you.
Since the installation of SIM 5.2, I noticed that the ISEE_SWM_CommandQueue service was not starting. I found the Srvany.exe file was missing in C:\PROGRA~1\HEWLET~1\SWMAgent\SWM\CLI\srvany.exe. I copied it from a different place and the service started successfully.
Since then, the cpu is all the time above 90%, mostly used bu a Wscript.exe process. And Wscript is a parameter passed to the Srvany.exe in the registry.
If I stop the two ISEE services, the CPU usage is normal. I changed the start mode of these services to manual and something (mxdomainmgr ?) changed the start mode of ISEE_CMS_SwmAgent to automatic and started it.
Can someone explain me what is hapenning ? I suppose I must reinstall ISEE.
Is this issue has something to see with my other post about the tempoutputxxx.entitlement_* files filling the temp folder ?
Thank you.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2008 01:47 PM
06-10-2008 01:47 PM
Re: SIM 5.2 and ISEE : high CPU usage of Wscript.exe
Your message helped me identify what is wrong with my SIM 5.1 Remote Support Software Manager (RSSM) so I thought I'd drop you this note to possibly help you ID what you are looking at.
ISEE_CMS_SwmAgent by default is set to Automatic and ISEE_SWM_CommandQueue by default is set to Manual (it will be started when you run RSSM and is set to stop after 3 minutes of inactivity).
In my case the ISEE_SWM_CommandQueue service was also set to use a SrvAny.exe file in the ...\CLI path and when I checked it was non-existent. I found that I had already downloaded that file from the HP web site and after copying it to the ...\CLI path my RRSM started working properly.
Here is one of the HP web site resources that I looked over while trying to figure out my issue:
Understanding the Remote Support Software Manager
http://docs.hp.com/en/418812-004/ch07s01.html?jumpid=reg_R1002_USEN
There are other documents as well but I'll leave it up to you to search for them now that you have a better idea of what you need to look for.
ISEE_CMS_SwmAgent by default is set to Automatic and ISEE_SWM_CommandQueue by default is set to Manual (it will be started when you run RSSM and is set to stop after 3 minutes of inactivity).
In my case the ISEE_SWM_CommandQueue service was also set to use a SrvAny.exe file in the ...\CLI path and when I checked it was non-existent. I found that I had already downloaded that file from the HP web site and after copying it to the ...\CLI path my RRSM started working properly.
Here is one of the HP web site resources that I looked over while trying to figure out my issue:
Understanding the Remote Support Software Manager
http://docs.hp.com/en/418812-004/ch07s01.html?jumpid=reg_R1002_USEN
There are other documents as well but I'll leave it up to you to search for them now that you have a better idea of what you need to look for.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP