First, make sure you have a maintenance contract. A maintenance contract includes: free updates/upgrades and unlimited support. During the first year after purchase, maintenance is free. Your license certificate states when maintenance expires.
To upgrade, do the following:
When you install Network Monitor in the same directory as the previous Network Monitor version, the configuration is automatically converted. Otherwise, you need to import the previous configuration.
To (re)install the manager application on remote PC(s), you must (re)create the share in the Remote Manager tab of the 'Remote Management' dialog (Tools menu).
Most probably, you don't have administrator rights on the machine where you install the product. Local administrator rights are required to install ActiveXperts Network Monitor on the computer.
Use the following steps to uninstall Network Monitor manually:
(-) Stop the Network Monitor service by using the Services applet, or by typing NET STOP AXSNMSVC from the command prompt;
ActiveXperts uses the InstallShield product for its installations. Only on rare occasions, InstallShield doesn't update its registry key after uninstall, so it will ask you to uninstall the next time you start the installation. You can use this workaround:
Now, InstallShield won't ask to uninstall anymore.
You are right: you cannot install the product in an existing directory.
Upon un-installation, the original directory (default: C:\Program Files\ActiveXperts\Network Monitor) is NOT deleted in case there are files created/modified after the previous installation. You must delete these files/directories manually.
Once the directory (C:\Program Files\ActiveXperts\Network Monitor) is deleted, you can re-install it in that directory.
In previous versions of the product, it was possible to install in an existing directory, but this often lead to interference with previous installations.
No agents will be installed on the monitred servers. You only need to install the ActiveXperts Network Monitor service on 1 server in your LAN.
The installation program will prompt for it when a reboot is required. But in most situations, a reboot is not necessary.
No, it's a full functioning product; its functionality will be reduced after 30 days (all monitoring functions will be disabled then, except HTTP and ICMP functions). Open the About dialog to see how many days are still remaining.
If you want to monitor member servers or domain controllers in your domain, it's strongly recommended to enter Domain Administrator credentials. For many tasks (like disk space checking, event log monitoring, and so on), Local Administrator rights are required on the monitored computers. By default, Domain/Enterprise Administrators are Local Administrators on domain member servers. If you don't enter a Domain- or Enterprise Administrator account during installation, you must configure an Administrator account for each check that requires it in the ActiveXperts Network Monitor software.
Yes. Assign the right permissions to the share is the best way to deny people from using the ActiveXperts Network Monitor. Be sure that the ActiveXperts Network Monitor service has Change permissions on the share.
See KB Q6500005
Please check the Event Log for more details. Look for 'AxsNmSvc' Event Source. Most probably, you have passed the wrong credentials to the ActiveXperts Network Monitor service. Use the services control applet to change these credentials. Be sure that this account had local administrator rights on the server where the Network Monitor service is be running.
Please do the following:
These are the steps to accomplish the migration to a new sever:
No, it won't. ActiveXperts Network Monitor doesn't install/replace any Windows systems DLL's. The only shared components that may be replaced are MFC42.DLL or MSVCRT.DLL, but only if these files were installed before 1999. ActiveXperts uses Windows API to monitor servers and devices. The following API's are used:
The application is unable to access its configuration files. The configuration files are accessed through the shared ActiveXperts Network Monitor directory. Check out registry key 'HKEY_LOCAL_MACHINE\Software\ActiveXperts\Network Monitor Manager'. It should contain two values:
Be sure that the remote Manager application can Read/Write to the share, i.e. it must have Read/Write permissions on share level and on NTFS level.
Yes it is. All configuration data is stored in one file: CONFIG.MDB, located in the CONFIGURATION folder. Assign read-only permission to this file for(groups of) people who are not allowed to make changes to the configuration. The Manager application detects this read-only flag and disable some program menu's. The Manager program does not allow configuration changes for the HelpDesk employees. You can also set Read-only permissions on share level, but this is not recommended, because then the Manager won't be able to send control information to the ActiveXperts Network Monitor service, like 'monitor now' and so on.
Assign appropriate permission on the share (default sharename: 'networkmonitor'). By default, the share permission on 'networkmonitor' is 'Full Control'.
You must take the following steps:
You can change the name of the computer where the Manager application is running. This will not affect the ActiveXperts Network Monitor Manager installation.
There can be two reasons for that:
WMI is required on both monitoring server and monitored server. Check the Services applet on the monitoring server and monitored server to verify that the WMI services are indeed running. Windows operating systems ship with the WMIC command line utility ('Windows Management Instrumentation Command-line'). Use this utility to check if WMI is working fine and to check credentials. Try to query the CPU counter on the monitoring machine first:
wmic /node:localhost path Win32_Processor where DeviceID='CPU0' get LoadPercentage
Then, use the same command from a console window on the monitored server:
wmic /node:localhost path Win32_Processor where DeviceID='CPU0' get LoadPercentage
and finally, run the command from the monitoring server to check CPU usage on the monitored server:
wmic /node:remote-computer /user:user /password:password path Win32_Processor where DeviceID='CPU0' get LoadPercentage
This is a WMI issue and is described in Microsoft's KB: WMI may return a value of 98 percent every time that you query the LoadPercentage property in Windows 2000.
This article also includes a link to a hotfix to resolve this problem.
Check out our online Database Monitoring Guidelines to read more about how to setup an MS SQL / ADO database check.
ActiveXperts Network Monitor uses the OLE DB libraries to access SQL servers (and other ADO compliant databases). The OLE DB libraries are installed by most Operating System Service Packs and by many applications. But if it is not installed yet, you can download it from the Microsoft website and install it. You can download the latest MDAC package from the Microsoft download site for free.
First check your System DSN settings, and test them from the Control Panel. Be sure you are using the right DSN with Network Monitor. Or use ADO as an alternative; ADO works similar as ODBC but doesn't require DSN configuration.
To monitor Oracle with ActiveXperts Network Monitor, it's recommended to install the ActiveXperts Network Monitor software on a working Oracle client. If you install it the other way around, you may run into problems, not getting Oracle monitoring to work.
There's no fixed connection string syntax for Oracle; the format of the connection string depends on the Oracle version, the authentication method and the type of security used. Please check the following web site for more information about Oracle connection strings: www.connectionstrings.com.
There's native support for MS SQL and Oracle. Besides that, any ODBC and ADO compliant database is supported. To read more about ODBC, click here; to read more about ADO, click here.
Verify that WMI is working well as described here. Then, check if you can access the Disk Drive class using the following command line commands: wmic /node:localhost path Win32_DiskDrive where Index='1' get Status wmic /node:remote-computer /user:user /password:password path Win32_DiskDrive where Index='1' get Status
Yes, that is exactly what the 'Disk Drive' check does. When a disk becomes 'not healthy' or unavailable, Network Monitor will let you know.
There can be many reasons. Most probably, the problem is not related to ActiveXperts Network Monitor at all. A few reasons for not being able to monitor the disk:
The operating system has access to RAID set as it were one physical drive. So, it is not a simple matter of checking a disk. A failure of a disk in a RAID can only be determined by the manufacturer's hardware driver or management software. So there are basically two options to check such a failure:
On LINUX and UNIX, simply use an SSH check. There are scripts included with ActiveXperts to monitor disk usage and disk free space.
Yes, you can, but only through SNMP. The vast majority of NetApp drives support the SNMP v2c protocol. This allows you to monitor any performance counter of your NetApp volume, including drive space.
You can monitor the following MS Dynamics suites:
Yes, there's a list of Performance Counters here: www.activexperts.com/admin/dynamics/.
If you have ActiveXperts Network Monitor running on a Windows 2003 (R2) server, you can monitor ONLY standard Application/System/Security logs on remote computers. Besides that you can NOT query any windows computers.
The reason for this is the fact that the Windows API on this Windows operating system does not support extended event logs (.evtx).
If you have Network Monitor running on Windows 7/Vista or higher, or Windows 2008 or higher, you can monitor any Windows event log, not only the standard Application/System/Security logs, but also the extended .evtx logs. You can query any windows computers except Windows XP, Windows 2000 and Windows 2003.
In the standard built-in Event Log check, you can only do basic Event Log checking. To do more advanced Event Log monitoring, you should use our VBScript- or PowerShell script that ships with the product, and customize it to meet your requirements.
Event Log monitoring consumes a lot of network bandwidth, and can really decrease the performance of your network, especially with large Event Logs. Unfortunately, there's nothing we can do about it. Just try any WMI script that scans event logs over the network and you'll see. In general, do not allow large event logs, i.e. only log events from the last two days, and (important!) import your event log data in some kind of database (SQL for instance). Also, do not query event logs frequently, not scanning every 2 minutes or so, but for instance every 15 minutes.
Yes, it is possible. First of all, you must make use of the VBScript equivalent of the Event Log check. This VBScript check monitors Event Logs in the same way as the built-in check. With a small modification to the script, you can include event details in your notifications.
The following document describes how to modify the script to include event details in your notifications: www.activexperts.com/support/network-monitor/online/eventlog.
Most probably, it is uncertain because there's an error in the script as a result of a 'null' object. This happens when the remote machine cannot be accessed. Please try to temporarily remove the 'On Error Resume Next' statements in the script. Network Monitor will then show the line where the script error occurs. Most probably, it is due to a WMI security problem. To read more about that, click here.
This problem occurs because Windows Management Instrumentation (WMI) uses AutoDiscovery/AutoPurge (ADAP) to build its internal performance counter table. If the particular Exchange service on the monitored computer was not started when the WMI ADAP process is started, the performance counters are not transferred to WMI.
Please run the following command from the command line on the monitored computer:
wmiadap /f
and then restart the wmi-service.
Most probably, this web site contains a redirection to other pages, or it includes frames. Network Monitor does NOT redirect to a linked page, it only checks the actual page.
The easiest way to find this out, is by using HTTP Client Diagnostic Utility (Diagnostic Utilities are available from the 'Tools' menu).
You will see the contents as it is retrieved by the ActiveXperts Network Monitor service, and you'll be able to find out the reason. Most probably, you should match your pattern against one of the include pages of the main page.
ActiveXperts Network Monitor relies on the Microsoft's WinHTTP libraries. By default, we use the WinHTTP5.DLL for all web checks. However, there may be an incompatibility due to late service packs. Please try the following:
The Network Monitor will now use another WinHTTP library, and you're problem will most probably be solved.
It depends: on LINUX and UNIX, the URL's may be case sensitive, so must enter URL's with the right lower/uppercase characters. The HTTP contents check is NOT case sensitive.
Most LINUX flavors use case-sensitive URL's, and Windows doesn't. Please check if this is the problem.
This is a known problem on Windows 2003 and Windows 2003 SP1 machines. It is an issue in WMI, that has fixed in Windows 2003 SP2. So if you are monitoring Windows 2003 machines without SP2 installed, please install SP2 in order to monitor 'available memory' properly.
This problem occurs because Windows Management Instrumentation (WMI) uses AutoDiscovery/AutoPurge (ADAP) to build its internal performance counter table. If the particular MSMQ service on the monitored computer was not started when the WMI ADAP process is started, the performance counters are not transferred to WMI.
Please run the following command from the command line on the monitored computer:
wmiadap /f
and then restart the wmi-service.
You should create a new 'Performance Counter' check. Select the 'Network Interface' performance object, and choose the relevant NIC card as the instance. Then, select your performance item(s), e.g. 'Bytes Received/sec, 'Bytes Sent/sec', 'Bytes Total/sec', 'Current Bandwidth', 'Packets Received/sec', etc.
You must allow Powershell scripting on the machine that has ActiveXperts Network Monitor running. Read more on allowing Powershell scripting here:
www.activexperts.com/support/network-monitor/online/powershell/
Pleasae note that allowing Powershell is different in 32-bits operating systems than in 64-bit operating systems.
You can turn on PowerShell logging for the Network Monitor Engine. To do so, enter a valid file name in the following registry entries (there's a registry entry for each PowerShell thread/subprocess):
HKLM\Software\ActiveXperts\Network Monitor\Server\Trace\ThreadPowerShell000 HKLM\Software\ActiveXperts\Network Monitor\Server\Trace\ThreadPowerShell001
For instance:
c:\powershell00.log c:\powershell01.log
After that, restart the service. Then, all PowerShell operations will be written to the log file(s).
ActiveXperts Network Monitor uses WMI to monitor printers. The WMI module is part of the Operating System. For troubleshooting purposes, you can run www.activexperts.com/support/network-monitor/wmi/printer.vbs to get detailed information about the status of the printer. If you want to customize the printer check, you can create a new VBScript based check and define a new printer check. You can fully customize this printer check and adjust it to your needs.
Verify that WMI is working well as described in the here.
Then, check if you can access the Process class using the following command line commands:
wmic /node:localhost path Win32_Process where Name='explorer.exe' get ProcessID
wmic /node:remote-computer /user:user /password:password path Win32_Process where Name='explorer.exe' get ProcessID
Yes it is. However, the standard built-in Process check can't handle it. There's a function called 'CheckNumProcesses' in 'Process.vbs'. With this script, you can monitor instances of a process.
There can be several reasons for it; it can be caused by the built-in Windows Firewall (blocking WMI calls to it). It can also be a security issue, where the ActiveXperts Network Monitor Service Account has no privileges to monitor the remote computer. Ensure that the credentials used for the ActiveXperts Network Monitor service are sufficient.
The best would be to troubleshoot with a simple VBScript program that runs independent from ActiveXperts Network Monitor:
Most problably, you won't be able to monitor the remote machine, just like with ActiveXperts Network Monitor.
Then, use the built-in WMIC command (only available for Windows 2003 and Windows XP) to monitor the remote machine:
wmic /node:COMPUTERNAME path Win32_Processor where DeviceID='CPU0' get LoadPercentage
WMIC will provide more advanced error information, to help you troubleshooting the problem.
On Windows 2003, you need to configure the SNMP service before you can actually use it. You can configure the service in the following way:
No, it is NOT required. ActiveXperts Network Monitor uses the SNMP Agent (i.e. the normal SNMP Service) to send out SNMP Traps.
Network Component requires an SNMP Agent running (remote) computer. By default, SNMP is not installed on a Windows platform. This applies to all major Windows platforms, i.e. Windows NT4, Windows XP, Windows 2000 and Windows 2003.
To install the SNMP agent on a Windows XP/2000/2003 platform, you must do the following:
On Windows XP SP2 and Windows 2003 stations, you must configure the SNMP Agent service after installation of the SNMP Agent service.
For more information on SNMP Monitoring, click the Online SNMP Monitoring Guidelines.
This can happen when the command started is a background process which keeps current stdout or stderr open. The solution is to redirect stdout and stderr. Click here for more information.
The other possibility is that you are running a version of OpenSSH which is older than 4.9. These versions contain a bug which causes it to never close sessions for root users. More information in the release notes for version 4.9 under (bz#926).
Yes, you can. The NTI device has an SNMP interface, like most environmental monitors. Simply look up the SNMP OID identifiers in the NTI manual, and use the ActiveXperts' SNMP check to monitor temperature, humidity or wetness.
The Sensatronics EM1 support SNMP. SNMP is enabled by default. You just need to enter a new SNMP check in Network Monitor and enter the appropriate SNMP OID's. Check the Sensatronics EM1 manual to get a list of supported OID's.
For a list of supported Sensatronics models, click here.
To configure the unit:
For a list of Sensatronics EM1 OID's, click here.
ActiveXperts Network Monitor uses WMI to monitor temperature. If IBM ships a WMI driver to check its temperature, the answer is: yes. Otherwise, it is not possible to check temperatures on IBM servers.
Most probably, RSH is not configured properly on the remote UNIX machine. Be sure to setup your .rhosts file correctly on your UNIX server.
The .rhosts file typically permits network access on UNIX/LINUX systems. The .rhosts file lists computer names and associated logon names that have access to remote computers. When you run rcp, rexec, or rsh commands remotely with a proper .rhosts file, you do not need to provide logon and password information for the remote computer. The .rhosts file is a text file in which each line is an entry. An entry consists of the local computer name, the local user name, and any comments about the entry. Each entry is separated by a tab or space, and comments begin with a pound sign (#). For example:
host7 #This computer is in room 31A
The .rhosts file must be in the user's home directory on the remote computer. For more information about the specific implementation of the .rhosts file on a remote computer, see the remote system documentation.
When troubleshooiting RSH, try the Windows built-in RSH client command utility to test if the RSH configuration is working fine.
Problems regarding RSH are usually due to the configuration of the RSH daemon on the remote server (.rhosts file), so check the RSH configuration on the Unix machine first.
Then, isolate the problem by using the standard Windows built-in RSH tool. Let's assume that the remote UNIX machine called PLUTO, you can issue the following command from the command line:
RSH PLUTO ls
Click here for instruction about how to setup the RSH daemon on LINUX.
There's an online ActiveXperts VBScript Guidelines page available here. It tells you how to write new VBScript checks, how to test these scripts and how to use the ActiveXperts VBScript debugger.
ActiveXperts Network Monitor service uses the VBScript engine of the operating system. You must have version 5.5 or higher of the script engine. This version is included in IE55SP2 or higher, and in the latest service packs of the operating systems.
WScript.Echo only works for a script that is called by a command line interpreter (i.e. CSCRIPT or WSCRIPT). You should avoid all console-related functions.
The online Network Monitor VBScript Guidelines explain how to write VBScript checks for ActiveXperts Network Monitor, and provides information about troubleshooting.
To pass a regular string parameter to your VBScript function, you should use double-quotes , e.g.:
"\\myserver\c$"
If you want to have a double-quote as part of the string passed to the function, you should escape the double-quote character by a double-quote, e.g.:
"ActiveXperts Software, ""Innovators in Communications""."
Make sure you have not disabled the Windows Firewall. If Windows Firewall is turned on, Network Monitor cannot query the machine from another server in the network. To disable the Windows Firewall:
Make sure the DCom is enabled on the monitoring server. To do so:
Make sure that UAC (User Account Control) is not causing you problems. UAC is enabled by default. Try to switch it off and see if the problem still persists.To disable UAC:
If you have created a local Administrator account on a monitored Windows 2008 server, and you use this account as alternate credentials without turning off UAC, it will definitely not work! Only the built-in local Administrator has sufficient rights. If you want to make use of another local Administrator, make sure UAC is turned off.
This generally happens on computers with the Windows Firewall enabled which blocks WMI calls to it. By default, Windows 2003 SP1 and Windows XP Professional SP2 have the Firewall module enabled. To have WMI calls allowed on a Windows 2003 Service Pack 1 computer with firewall enabled, the following script has to be run:
Set objFirewall = CreateObject("HNetCfg.FwMgr")
Set objPolicy = objFirewall.LocalPolicy.CurrentProfile
Set objAdminSettings = objPolicy.RemoteAdminSettings
objAdminSettings.Enabled = TRUE
This script will enable WMI administration.
The problems can also be a security issue, where the ActiveXperts Network Monitor Service Account has no privileges to monitor the remote XP PC's. Ensure that the credentials used for the ActiveXperts Network Monitor service are sufficient.
You can check this out with a simple VBScript program:
Most probably, you won't be able to monitor the remote machine, just like with ActiveXperts Network Monitor.
Then, use the built-in WMIC command (only available for Windows 2003 and Windows XP) to monitor the remote machine:
wmic /node:COMPUTERNAME path Win32_Processor where DeviceID='CPU0' get LoadPercentage
WMIC will provide more advanced error information, to help you troubleshooting the problem.
WMIC is only support on Windows 2003 servers and Windows XP stations. WMIC is not available for Windows 2000 machines.
See also FAQ Item 7300005
WMI (Windows Management Interface) is not included in the default setup of NT4. However, it is available as a separate product without extra costs. Click here to download WMI for NT4 from the Microsoft website now.
WMI monitoring uses the Microsoft VBScript engine. Do the following to find out the reason of the problem:
Most probably, the script will produce an error related to VBScript Engine, OS or security. It's possible that an upgrade of this VBScript engine is required (depending on the type of error). You can upgrade the VBScript engine either through an upgrade of IE, an upgrade of IIS, or an upgrade of the Windows Scripting Host (available from the MS web site).
Yes you can. You must download and install it first.
WMI for NT4: http://download.microsoft.com/download/platformsdk/wmint4/1.5/NT4/EN-US/wmint4.EXE;
WMI for 95/98: http://www.microsoft.com/downloads/details.aspx?FamilyID=afe41f46-e213-4cbf-9c5b-fbf236e0e875&DisplayLang=en.
This problem occurs because Windows Management Instrumentation (WMI) uses AutoDiscovery/AutoPurge (ADAP) to build its internal performance counter table. If a particular service on the monitored computer was not started when the WMI ADAP process is started, the performance counters are not transferred to WMI.
Please run the following command from the command line on the monitored computer:
wmiadap /f
and then restart the wmi-service.
Yes, IPv6 is supported for all checks.
The ports used when monitoring a server using ActiveXperts Network Monitor depend on the type of monitor function that is being done. For example, monitoring a web site usually requires one port – port 80, monitoring an SMTP server requires port 25, monitoring DNS requires port 53(udp).
WMI (or more correctly RPC/DCOM) uses TCP ports 135 and 445 as well
as dynamically-assigned ports above 1024. WMI is used for many Windows-based checks.
When checking which ports must be opened on the firewall, one should also take into consideration the ports required to perform the action if the monitoring check fails.
The best practice is to use a packet sniffer like the Microsoft Network Monitor (installed only with the Windows 2000/2003 server) to see which ports are required.
Communication between Network Monitor Manager (the graphical application) and the ActiveXperts Network Monitor service (the Engine) is based on a Windows share. You must allow Windows Sharing through the firewall.
Windows Sharing (or more correctly RPC/DCOM) uses TCP ports 135 and 445 as well as dynamically-assigned ports above 1024.
The best practice is to use a packet sniffer like the Microsoft Network Monitor (installed only with the Windows 2000/2003 server) to see which ports are required.
No; the ActiveXperts Network Monitor service automatically detects changes to the configuration and reads the new configuration in memory.
Use VBScript to write your own monitoring checks.
Simply create a new monitoring check, choose 'VBScript' as the check-type, and add a new VBScript function.
Use RSH shell scripting to write custom UNIX and LINUX functions.
WMI means: Windows Management Interface, and is part of the Windows 2000 operating system and higher. It can be installed separately on Windows NT 4 machines. WMI is an interface to all hardware and software configuration items. ActiveXperts Network Monitor supports WMI. You can use WMI inside your VBScript monitor checks.
ADSI means: Active Directory Service Interfaces, and is part of the Windows 2000 operating system and higher. It can be installed separate on Windows NT 4 machines. ActiveXperts Network Monitor supports ADSI. You can use ADSI inside your VBScript checks.
ADSI is not included in the default setup of NT4. However, it is available as a separate product without extra costs. Click here to read all about ADSI on NT4.
First of all, Network Monitor uses the DNS API of the Operating System. This DNS API is only provided on Windows 2000 operating systems and higher. So, if you are using NT4, the DNS function will not work.
Second, you need to provide a proper DNS server in the DNS Setup dialog of the Network Monitor application; The DNS function does NOT use the DNS server specified by the TCP/IP properties of the OS. This would be useless, since the DNS function is often used in environments with redundant DNS servers; operators want to monitor all of the DNS servers in the network.
Last but not least: if you have problems with the DNS monitor function, please try NSLOOKUP on the monitoring server to find the reason of the problem. Click here for more information about how to use NSLOOKUP; to read more about DNS, click here.
Just configure the 'Maintenance Hours' from the Tools menu. Select 'day of week' and choose 'Saturday'. Also enter time and duration.
All errors during this period won't be considered as a failure.
The ActiveXperts Network Monitor Manager application can be used to configure the ActiveXperts Network Monitor service and to view results and logfiles. The ActiveXperts Network Monitor Manager application can be installed on multiple desktop PCs. Usually, all system operators will have the ActiveXperts Network Monitor Manager application installed on their PC.
Most probably, the reason for failure is: Security. The ActiveXperts Network Monitor service requires Local Administrator rights on the server that is monitored. To verify this, interactively log on to the Network Monitor server using the same credentials, open a command prompt and type: 'NET USE \\<serverx>\IPC$' , where 'serverx' is the server you are monitoring. If this fails, then the problem is: security, and you have to make sure that the ActiveXperts Network Monitor service account has Local Administrator rights on 'serverx'.
You can use either the short name (as it appears in the registry, in 'HKLM\System\CurrentControlSet\Services') or its display name (as it appears in the control panel). Make sure that the Network Monitor service has sufficient permissions to check the service on the remote machine. Local Admin permissions on the server you are monitoring is recommended.
Yes they are.
Most probably, one or a few checks are pulling the performance down. It is always hard to say which one it is. Assuming that AxNmSvc.exe is consuming all CPU, do the following:
Perhaps one or two checks are consuming all CPU. You should consider monitoring these checks less frequent. What will help as well, is adding a second processor to the system. Since the monitoring service is multithreaded (>10 threads), the processes of the services will be divided over the processors by the OS. This will definitely increase performance.
Communication between the Manager Application and Service requires all NetBIOS and RPC ports. Monitoring requires ports that depends on the type of monitor function it uses; for instance, monitoring a web site usually requires one port, monitoring an SMTP server requires port 25, monitoring DSN requires port 53 (UDP), Best practice is to use the Network Monitor of Windows to see which ports are required.
The log directory only logs system state changes. For instance, when a server has been up all the time, then there will be only one entry in the log directory saying that the server is up.
The logging you see in the ActiveXperts Network Monitor Manager is different: it shows the activity of the ActiveXperts Network Monitor service.
Yes it is possible. A UPS usually reports problems in the Windows Event Log. By monitoring the Windows Event Log for specific UPS events, you can receive notifications from Network Monitor when there's a problem with your UPS.
Most probably, one particular check is responsible for crashing the service. There are a few known scenario's where this can happen
Disable all notification types from the Tools->Notifications menu. and restart the service. If the problem still persists, use a 'divide and conquer' approach to find out which check is causing the problem, like this:
This 'divide and conquer' approach is the easiest way to find out what makes the service crash. Once you've found the particular check, report this to the ActiveXperts Help Desk.
No, ActiveXperts Network Monitor can use any SMTP-compliant server. No Internet Information Server is needed.
SMTP is the acronym for "Simple Mail Transfer Protocol", which is the standard that defines how email is sent (RFCs 821 & 822). ActiveXperts Network Monitor is RFC 821 and RFC 822 compliant. For more information about RFC 821 and 822, please check the website of the Internet Engineering Task Force. They have all RFC pages available.
You can turn on e-mail logging for the Network Monitor Engine. To do so, you must enter a valid file name in the following registry entry:
HKLM\Software\ActiveXperts\Network Monitor\Server\Trace\NotifyEmail
For instance:
c:\notfyemail.log
After that, restart the service. After that, all e-mail operations will be written to the log file.
Exchange is configured in such a way that it prevents relay of SMTP messages from inside to outside. Enable relay from inside to outside and it'll work.
This is a known issues for users using McAfee VirusScan Enterprise. By default, it would not allow AxsNmSvc.exe (the network monitor service) to send SMTP traffic.
Open the VirusScan Console by Right-clicking the VirusScan icon in the system tray, select VirusScan Console, double-click Access Protection,
select Prevent mass mailing worms from sending mail, click the edit
button, and type AxsNmSvc.exe in the excluded processes field.
You should try Outlook Express on the server where the ActiveXperts Network Monitor service is running, configure an e-mail account and try to send an e-mail. Most probably, this will also fail, due to wrong login/password on Exchange or a wrong Exchange configuration.
You must select a different character set in the ActiveXperts Network Monitor Manager. Open the 'Notification Settings' dialog from the 'Tools' menu. Select the 'SMTP/Email' tab and click on 'Format Message Body'. There you can select the 'big5' character set in order to support the Chinese e-mail notifications. There's also support for the Japanese e-mail notifications: the iso-2202-jp character set.
A mailbox on the SMTP server is required. Try Outlook Express first using same configuration.
From the 'Tools' menu, click 'Notification Settings' and select the 'E-mail' tab (selected by default). Click on the 'Format Message' button. You can now modify the standard e-mail message.
Insert the 'Notes' variable by clicking on the 'Insert system variable' link and select the 'Notes' variable.
ActiveXperts supports any modem that is compliant with both ETSI GSM 07.05 and ETSI GSM 07.07 standards.
Please note this doesn't necessarily mean that a modem that is compliant to these standards is automatically a good modem. There are many cheap modems around, with different firmware versions etc. For a list of recommended modems, please click here.
For more information on recommended modems for ActiveXperts Network Monitor, click here.
You can set the service center address with AT+CSCA in two ways:
The syntax for the AT+CSCA command: <-p>
AT+CSCA="
Yes, you need a GSM modem.
A GSM modem is a serial- or USB device. It has a slot for a SIM card. You can use a regular SIM card, i.e. the same one as used for mobile phones. You must connect it to the machine where the ActiveXperts Network Monitor service is running.
ActiveXperts recommends the 'SAMBA 75 GSM/GPRS Modem'. It is reliable and has a good price/quality ratio.
ActiveXperts offers a special SAMBA/Network Monitor bundle (artcile# AX007-0250). For more details, click here.
All Hayes compatible modems are supported.
You can turn on modem logging for the Network Monitor Engine. To do so, you must enter a valid file name in the following registry entry:
HKLM\Software\ActiveXperts\Network Monitor\Server\Trace\NotifySms
For instance:
c:\notfysms.log
After that, restart the service. After that, all SMS operations will be written to the log file.
It depends on how you send out SMS messages. Network Monitor supports SMSC service providers, GSM modems and GSM phones. Click here to learn which format you should use.
A: It is very important to use the right format for the recipient ID. Some providers require a country code, some don't. A provider very often accepts any recipient ID, processes it and reports that there's no problem, but actually doesn't send it out because of a bad format. For instance, when you are located in the UK (+44), you should try the following formats:
Go to the command prompt and type: echo AT > COM1 . The modem should flash lights.
Yes, it does, as long as these devices can be referred through a COM port. Most USB modem drivers install a COM port interface on Windows.
First, check out our SMSC list on our web site to see if a provider for your country is listed. If not, please ask your local Telecom company for a list of SMSC dial-in providers.
This means that the COM port does not exist. You only get this error if you use a COM port (like COM1) rather than a Windows Telephony device (like 'Standard 9600 bps Modem'). Error 30102 does NOT mean that the port is already in use. If the port would already be in use, you would get another error: 30103.
This means that the port you are attempting to open is already in use by another application. You only get this error if you use a COM port (like COM1) rather than a Windows Telephony device (like 'Standard 9600 bps Modem').
Check if there's another application that is already using the COM port. In some situations, you may want to benefit from a thing called 'port sharing', where one port can be shared by multiple applications. To benefit from 'port sharing', you must use Windows Telephony devices (like 'Standard 9600 bps Modem').
This means that the Windows Telephony Device you are using, is NOT defined on the computer. You may have made a typing mistake. Error 11201 does NOT mean that the port is already in use (you would get error 11202).
You will never get this error when using direct COM ports (like 'COM1'), but only when using Windows Telephony devices.
This error only occurs when using Windows Telephony devices (like 'Standard 9600 bps Modem'). The error implies that the Windows Telephony device is valid, but that the associated COM port is either already in use, or does not exist. The error does NOT imply that the Windows Telephony device is invalid (that would give error 30201); it neither implies that the Windows Telephony device is already used (that would give error 30204).
This error only occurs when using Windows Telephony devices (like 'Standard 9600 bps Modem'). The Windows Telephony device name is valid,. There can be two reasons for this error:
Most probably, the baud rate causes the problem: COM port and modem are not sending/receiving at the same speed. We strongly recommend to use 9600bps. Two things you need to do:
Network Messaging requires that the Windows 'Messenger' service is running on both sending and receiving computers. By default, the Messenger service is not started automatically.
So, make sure that the Messenger service is running on the machine where ActiveXperts Network Monitor service is running.
Also try to send network messages from the command line, like this:
net send your message recipient
and see if you get an error message.
Make sure you have the SNMP Service installed, configured and running.
For information about installing/configuring the SNMP Service, click here.
For more information about SNMP Traps and Network Monitor, click here.
Yes you can. SNMP v1 and SNMP v2c traps are supported. To read more about SNMP traps, click here.
Yes it is; configure the 'Advanced' tab of the particular monitoring check; here you find "Notification Frequency". When you configure "...notify every 10 minutes…", you will be notified 6 times an hour.
This will be included in a future release, but is not available yet.
Paging through dialup/DTMF was available until version 7.1. It later versions, it has been replaced by SMS notifications. However, it is still possible to make use of Paging/DTMF, but only by the use of a custom action script.
To define Pager notifications for a specific check, please do the following:
After that, Pager notifications work as they used to in earlier versions of Network Monitor.
Yes you can, but the .NET Framework needs to be installed on the server where ActiveXperts Network Monitor is running. The .NET Framework is part of Windows 2003. If the Network Monitor engine runs on a Windows 2000 or Windows NT4 platform, you can download the Framework from the Microsoft download site. For further information on the .NET Framework, click here.
To restart a service, you should either enter its internal service name, or its long service displayname (as it appears in the Windows' services applet).
For instance, to restart the Windows Time Service, you can either provide w32time (short name) or Windows Time (long displayname) in the network monitor configuration.
Yes you can. To restart multiple services, simply separate each service with a ';' character. For instance, to restart the alerter service and the messenger service, enter this string in the 'Restart service(s) after failure' box: alerter;messenger
It is pretty easy: just write a small VBScript program and launch it when the check fails. You can use the following script as a base for your own script:
strRemoteComputer = "server05"
strService = "alerter"
For each Service in GetObject("winmgmts:{impersonationLevel=impersonate}!//" & strRemoteComputer)_
.ExecQuery("select * from Win32_Service where Name='" & strService & "'")
Service.StartService
Next
Yes you can. To restart multiple services, simply separate each service with a ';' character. For instance, to restart the alerter service and the messenger service, enter this string in the 'Restart service(s) after failure' box: alerter;messenger
Click here for more information about restarting services.
Try the SHUTDOWN utility (Windows NT4 and Windows 2000 Resource Kit) to reboot that machine, using the same credentials as the Network Monitor service. Check the error. Most probably, the service account has no administrative privileges on the remote computer.
The best way is to use folders, and let them depend on certain checks. This way your depency configuration is dynamic, i.e. when you add new checks to the folder, they will become dependent automatically. For further information, check the online Dependency Guidelines.
Dependencies are transitive. As a result, you do not need to make check C dependent on check A.
Yes there is. Click on 'Properties' of the particular check, and select the 'Advanced Properties' tab. Click on the 'Dependencies' button; it will show the dependees.
Yes, it does. It is explained in our Network Monitor Logging Guidelines.
The ActiveXperts Network Monitor service provides tracing for various tasks, including logging. To enable tracing for ADO logging, you must do the following:
The Trace file will tell you exactly what's going wrong. Don't forget to reset the entry to the emtpy string after you have finished troubleshooting.
Yes, it is possible. You must migrate the Temperatures.mdb file to MS SQL. This is explained in our Environmental Data Logging Guidelines.
This means the the Network Monitor service cannot write the log requests to the log database, or database writes are too slow and log requests are congested. Please check the Logging settings:
Please note that the maximum number of outstanding requests is indicated by the following registry entry:
HKLM\Software\ActiveXperts\Network Monitor\Server\Queue\MaxPendingLogRequests
You can modify this value; you need to restart the service for the changes to take effect.
No you can't. The layout of the HTML reports are static; if you want to change the layout of your reports, you should use XML Reports instead.
When you print the report, the graph bars on the document indicating the up/downtimes of the checks may not appear on the printed paper. This is because 'Backgroud Printing' is disbaled in an internet Browser by default.
To enable background Printing in Internet Explorer, choose 'Internet Options' from the 'Tools' menu, and enable 'Print background colors and images' from the 'Advanced' tab.
To enable background printing in Mozilla Firefox, choose 'Page Setup' from the 'File' menu and enable 'Print Background (colours & images)'.
See also: ActiveXperts Network Monitor Report Printing.
Yes that is possible. You must use the command-line utility 'AxRgCmd.exe' to create reports without user intervention. You can use this 'AxRgCmd.exe' from the Windows Task Scheduler to create reports automatically and send the reports to a group of e-mail recipients.
The 'AxRgCmd.exe' utility requires a few parameters. There are a few batch jobs (.cmd) included with the product. Each batch jobs use the 'AxRgCmd.exe' with the required parameters and can be used directly in the Windows Task Scheduler. The batch jobs are located in the '<INSTALL-DIR>\Reports\Batchjobs\' directory and perfectly demonstrate how to schedule a report.
You should create a new XSL stylesheet. This style sheet is the layout for your new reports. Please visit the online Custom XML Reports page for details. The page describes how to create a new XML Report.
It is strongly recommended to migrate the report database to MS SQL Server (or MS SQL Server Express Edition). This is because Network Monitor uses complex queries to generate reports. With MS Access and a small configuration (less than 100 checks), generating reports can take minutes already after a few weeks, whereas with MS SQL it will take one a few seconds or even less.
Yes, MS SQL Express Edition is supported.
Migration to MS SQL Server Express Edition can be done in the same way as migrating to MS SQL Server, with only one difference: you MUST specify the instance ID of the SQL Server Express Edition database in the 'Host' field.
For example, if the name of the database server is named 'DbServer01', and the instance id of the database is named 'SQLExpress', then specify 'DbServer01\SQLExpress'.
There's no performance difference between MS SQL Server and MS SQL Server Express. See also FAQ #7780120.
No, there's no performance difference between MS SQL Server and MS SQL Server Express Edition. It is strongly recommended to migrate your reporting database to either MS SQL Server or MS SQL Server Express Edition to boost the performance of the reporting tools.
Yes, that is possible. There's a registry key for that, depending on the type of Report Databse you are using (MS Access or MS SQL Server):
HKLM\Software\ActiveXperts\Network Monitor\Reports\ThesholdMsAccess
or
HKLM\Software\ActiveXperts\Network Monitor\Reports\ThesholdMsSql
The value indicates the number of events in the Report Database before a warning is given.
Note that you can completely surpress this warning, regardless of the treshold. See also FAQ #7780160.
Yes, that is possible. There's a registry key for that:
HKLM\Software\ActiveXperts\Network Monitor\Reports\ShowWarning
By setting this value to 0, no warnings will be given after that.
This means the the Network Monitor service cannot write the report requests to the statistical database, or database writes are too slow and report requests are congested. Please check the Reports and Graphs settings:
Please note that the maximum number of outstanding requests is indicated by the following registry entry:
HKLM\Software\ActiveXperts\Network Monitor\Server\Queue\MaxPendingReportRequests
You can modify this value; you need to restart the service for the changes to take effect.
This means the the Network Monitor service cannot write the graph requests to the statistical database, or database writes are too slow and report requests are congested. Please check the Reports and Graphs settings:
Please note that the maximum number of outstanding requests is indicated by the following registry entry:
HKLM\Software\ActiveXperts\Network Monitor\Server\Queue\MaxPendingGraphRequests
You can modify this value; you need to restart the service for the changes to take effect.
Please read our online Web Interface Guidelines. The process is explained step-by-step.
A very good source for XML and XSL is the W3Schools Online Web Tutorials. At W3Schools you will find all the Web-building tutorials you need, from basic HTML and XHTML to advanced XML, XSL, Multimedia and WAP.
ActiveXperts Network Monitor needs the so called 'IIS6 Metabase' interface to automatically create the virtual directory for you. On IIS 6, this interface is installed by default. On IIS 7, this interface is included but not installed by default.
Please see check the following document: How to install the IIS 6 Metabase Compatibility Component on IIS 7.
If you don't want to install the 'IIS 6 Metabase Compatibility components', you can create the virtual directory manually. See also FAQ#Q7820110.
To publish the ActiveXperts Network Monitor web interface through an IIS Virtual Directory, you can use the ActiveXperts Web Interface Configurator program, or configure the virtual directory manually.
To configure the virtual directory manually:
You can now use http://<iisservername>/networkmonitor/
The module that crashes is the Network Monitor Engine ('AxsNmSvc.exe').
Somehow, the NTDLL API (NTDLL.DLL) got corrupted. The most common reasons are:
ActiveXperts Network Monitor may not be the only software on your server that is suffering from this; also other applications and services may have undesirable results.
A very good source for XML and XSL is the W3Schools Online Web Tutorials. At W3Schools you will find all the Web-building tutorials you need, from basic HTML and XHTML to advanced XML, XSL, Multimedia and WAP.
To learn about the different license options for ActiveXperts Network Monitor, click here.
Licensing is based on the number of monitored servers in ONE organization, no matter how many subnets you have. You need only one Enterprise License.
You need a Small Business License.
With a Small Business License, you are allowed to define as many checks as you want, as long you are not exceeding 10 different IP-devices/workstations/servers. See also: www.activexperts.com/sales#licax007
If you need to monitor more than 10 IP-devices/workstations/servers in your organization, you need the Enterprise License.
Licensing is based on the number of devices (computers, servers, routers, etc.) you are monitoring in your organization. So, in your situation, you only need 1 Enterprise License.
External hosts on the public internet do NOT count as server. With a Small Business License you can monitor up to 10 different IP-devices/workstations/servers in your organization, as well as an unlimited number of hosts on the internet. See also: www.activexperts.com/sales#licax007
No, you don't. An ActiveXperts Network Monitor license covers an SMS and MMS Toolkit license, an ActiveXperts Email Component license, an Network Component license and an ActiveXperts Scripting Component license. You can even use these components inside your scripts.
ActiveXperts' Maintenance Agreement entitles customers to use ActiveXperts' technical support services, and to receive all product upgrades, free of charge, during a specified Agreement duration. The Maintenance Agreement applies to all ActiveXperts products.
After purchase, you get 1 year Maintenance for free
After this free Maintenance period, Licensee may purchase Maintenance. The price for the Maintenance Agreement is 15% of the price that was paid for the product.
Read our Maintenance Agreement in PDF format.
After 30 days of evaluation, functionality will be reduced. All monitoring functions will be disabled, except HTTP and ICMP functions. Open the About dialog to see how many days are still remaining.
For detailed sales information, check the Sales webpage.
It's very simple: just launch the ActiveXperts Network Monitor Manager application, go to the Tools menu and select the Registration menu item. Here, you can enter the registration code. That's all you got to do, no further activation is required.
Your security settings do not allow to store the license key. Please do the following:
Once you've completed the above steps, the key is stored on the system.
No you don't. ActiveXperts Network Monitor indeed uses the ActiveXperts Email Component and SMS and MMS Toolkit products for notification purposes, but you do you not need to purchase additional licenses for these products.
During the first (1) year after purchase, Maintenance is free. After this free Maintenance year, Licensee may purchase Maintenance. The price for the Maintenance Agreement is approx. 15% of the price that was paid for the product.
Customers choose between one-, two- and three years Maintenance Agreement renewal. Please read the Maintenance Agreement document for more details.
Renewals that come in after the maintenance has expired will be backdated to start from the old expiry date. Also, you are only able to get Technical Support and Software Maintenance when your support contract is valid.
No, we do not ship or sell the sourcecode of our products.
The only sourcecode that is included with our products, are the code samples shipped with toolkits or API’s.
| Error codes |
|---|
| Click here to view the full list of error codes |