See link for processname. http://wsustot.ndsdrift.no/DAK/ScrShots ... thDots.jpg
See link for testproperties in HM. http://wsustot.ndsdrift.no/DAK/ScrShots ... erties.jpg
Processtest fails if processname contains dots. Tests without dots (example lsass.exe) works fine.
Because of Firewall restrictions, I can not perform test directly from HM server (for testing error only in agent).
I beleave this must be a bug in HM.
Possible to get a fix?
PS!
I've tried with "process.name.exe" and 'process.name', same result.
Process test fail if name contains dot (process.name.1.exe)
-
KS-Soft Europe
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Process test fail if name contains dot (process.name.1.exe)
In some cases Windows truncates process names that exceed 15 characters.
You may check process name on system, where process is started, using Windows Task Manager.
E.g. on Windows XP SP3, process name, started from network drive, will be truncated to 15 characters.
So, file Infodoc.ServiceHost.WindowsService.exe will be truncated to Infodoc.Service
You may use Test properties dialog to retrieve list of processes with actual (truncated) names.
You may check process name on system, where process is started, using Windows Task Manager.
E.g. on Windows XP SP3, process name, started from network drive, will be truncated to 15 characters.
So, file Infodoc.ServiceHost.WindowsService.exe will be truncated to Infodoc.Service
You may use Test properties dialog to retrieve list of processes with actual (truncated) names.
When you report some problem, please always tell us what exactly software do you use.
- Windows?
- Service Pack?
- HostMonitor version?
For example we just tested HostMonitor version 8.86 using processes like Infodoc.ServiceHost.WindowsService and other with similar names on Windows XP SP3, Windows 7x64 and we cannot reproduce the problem. HostMonitor works fine.
(unless you start process from network drive on Windows XP, but its not HostMonitor fault. Windows cuts name but you see the same truncated name when you select process to monitor using Test Properties dialog or Windows Task Manager)
Regards
Alex
- Windows?
- Service Pack?
- HostMonitor version?
For example we just tested HostMonitor version 8.86 using processes like Infodoc.ServiceHost.WindowsService and other with similar names on Windows XP SP3, Windows 7x64 and we cannot reproduce the problem. HostMonitor works fine.
(unless you start process from network drive on Windows XP, but its not HostMonitor fault. Windows cuts name but you see the same truncated name when you select process to monitor using Test Properties dialog or Windows Task Manager)
Regards
Alex
I am quite embarrassed right now. I've messed up the ip addresses and the test has been performed on a server witch the service do not reside (and of course it fails).KS-Soft wrote:When you report some problem, please always tell us what exactly software do you use.
- Windows?
- Service Pack?
- HostMonitor version?
For example we just tested HostMonitor version 8.86 using processes like Infodoc.ServiceHost.WindowsService and other with similar names on Windows XP SP3, Windows 7x64 and we cannot reproduce the problem. HostMonitor works fine.
(unless you start process from network drive on Windows XP, but its not HostMonitor fault. Windows cuts name but you see the same truncated name when you select process to monitor using Test Properties dialog or Windows Task Manager)
Regards
Alex
After changing to correct ip address, the test runs fine. Sorry for bothering you with false alarm..
If you're still interested I have a drawing of my environment: http://wsustot.ndsdrift.no/DAK/ScrShots ... ucture.jpg
