The description for Event ID ( 487 ) in Source ( Zend Optimizer ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Unable to view file mapping, Attempt to access invalid address.
A:
This means Optimizer can't set up the shared memory. you need to clean your windows temp dir, ensure that everybody has access to it, and remove ZendOptimizer files from there,
then restart the webserver. Alternatively, you can just ignore it - shared memory is used only for limited-user scripts, so if you don't run those, Optimizer is OK without it.
If you are using Logs, you will need Logs Agent in the servers containing the log files you want to monitor. With the exception of Logs, all other Chroniker monitors are agent-less.
Chroniker monitors multiple operating systems including Red Hat Linux versions 7.2, 7.3, 8.0 and 9.0 amongst others. However, the install host server for the application is Windows only.
Linux and Unix install versions will be available soon.
Right now you can monitor Unix, but must have one Windows box to run Chroniker. A Linux version will be available shortly. (you can convert at no cost)
This probably occurred because you used the browser navigation (Back and Forward) buttons. You should only use the buttons within the Chroniker program to navigate
in Chroniker. To get your page back, use the normal Chroniker navigation and try again. If the problem persists, please restart the Chroniker
Service by right clicking on the Chroniker icon in the system tray and click Stop Chroniker Server, and then when the icon turns red, right click again and click Start Chroniker Server.
It might be a Windows Firewall issue. You need to open the port number that the Chroniker listens to in your windows firewall. The default Chroniker port is 8888. To do so:
Starting version 3.5, Chroniker gives you the option to use a secure web interface. During the installation, check the box to use secure web interface otherwise Chroniker will use a regular web interface.
Chroniker uses self-signed certificates which are valid for server name "localhost". To avoid this pop-up, you need to generate your own certificate and key or obtain them from Certificate Authorities like Verisign. Once you have your certificate, refer to the "How can I use my own SSL certificate" question below for the steps on how to make your certificate work with Chroniker.
Copy your certificate to the "<chroniker install folder>\webserv\conf\ssl" folder.
If the certificate and key names are different than the ones already present in the above folder, then you will need to edit the webserver config file:
Open httpd.conf found in the "<chroniker install folder>\webserv\conf" folder.
Change the following values to point to your own certificate and key:
SSLCertificateFile conf/ssl/localhost.cert
SSLCertificateKeyFile conf/ssl/localhost.key
If you want to change the server-name to reflect the name contained in your server-certificate then edit the following key:
ServerName <your-server-name>:<Chroniker listener port>
Every module includes Service Level Agreement (SLA) reports, Daily/Monthly/Yearly and Top (N) reports for the most and least of a data set. If you would like additional reports using Chroniker, contact us about custom programming.
Yes. Reports are even color coded for ease of use. Daily, weekly and monthly reports are created, with the ability to set any time frame you would like.
We can develop custom reports that fit your specific needs. All you need to do is send us a request with a description of the needed report. Click
here to learn more or contact sales@nrgglobal.com
Nodes monitors any node or networking device as long as it is TCP/IP based. Meaning it must have an associated IP address. Click here to read a full list.
Systems monitors the response time for changes in file size, average disk queue length, CPU usage, application processes, physical and virtal memory and window services.
Applications monitors Applications like Citrix, Oracle, SAP, PeopleSoft, Sieble, etc... from the End users perspective. Click here to read a full list.
Yes. You can achieve this functionality by using the 4 type of alerts and the duration. In this example, you would have a warning sent to person A if value is greater than X for a duration of 5 mins then you can have an error alert sent to person B if value is still greater than X after 20 mins.
With Applications, each ScenarioStation comes with unlimited number of scenarios. The cost depends on how many ScenarioStations you need. Please contact sales@nrgglobal.com for current pricing.
The pricing depends on your monitoring requirements. Email sales@nrgglobal.com with a description of the number of servers and nodes you will be monitoring so you can get the current pricing of the package that fits your needs.
Nagios is good openware that can be made to do a lot of things, but Chroniker will help with the overall picture and essential health reports. Chroniker is simple and shows results right away. When a manager needs a report, it is provided instantly. Chroniker provides a centralized, web based graphical user interface (GUI) to see everything at once. Plus Chroniker's monitors contain tests unavailable elsewhere.
You can setup Chroniker to send SNMP traps that will forward the Chroniker alerts message to your other monitoring software. To do so:
Go to SNMP trap reaction page
Click on the reactions button in Chroniker top menu
Click on "Add New Reaction"
Once the menu is displayed, click "SNMP Trap Reaction"
Follow the instructions on the page on how to download TrapGen program
Fill out the form as follow:
Enter the host serverwhen your other software is running
The port is optional (it defaults to 162)
In the message field have the alert message variable only, %ms.
Whatever variables you want to include in the alert message, you can set them at the event level as follow:
Go to the events page (click on the events button in the top Chroniker menu bar)
Edit or create an event
Under the Alert Message field, type in your message and use the drop down list in the right of the field to include the necessary variables
Note: This message alert in the event is the one that will be sent in the trap.
The password is changed by clicking on “Setup" in the top menu of any module, then click on Change Password. We recommend you change your password from the default the first time you use Chroniker.
Click on the icon located on the Start Menu-> Program files ->Chroniker to create a new shortcut. Or to manually open the program in a web browser; the URL is http://(your_hostname):(port)/. Replace (your_hosname) with the name of the computer that Chroniker is installed on, Replace (port) with the TCP port you selected for Chroniker Web server. The default port is 8888.
You can use WaitForWindowAppear Action on the left pane of your Scenario Station to wait for window to load successfully, you can set the time of wait in the "Select Window" popup window.
You can use WaitForBitmapAppear Action on the left pane of your Scenario Station to wait for bitmap in that window to load successfully, you can set the time of wait in the "Select Bitmap" popup window
You can use Wait Action on the left pane of your Scenario Station and set wait time in seconds.
Note: Make sure the total time of your scenario including wait times does not exceed the "Playback error after" time specified in File->Scenario Properties in your Scenario Station.
You can use Transaction action on the left pane of your Scenario Station to divide your Scenario into meaningful sections. Each Transaction is a section of the scenario (consisting of a sequence of actions) marked for the purpose of measuring the performance (response time) of that section within the scenario. Transactions let you know the exact point where the failure or slowness occurs when playing back the scenario against your target application.
Click on the scenario name to see the graph and summary statistics.
Click on the point on the graph where the scenario failed in the past (value will be zero).
The actual screenshot of the failed scenario will pop up.
Note: the center of the magnifying glass must be exactly over the point to retrieve the screen shot.
My Scenario keeps failing at a certain bitmap image:
Check to see that your bitmap does not change color or style on mouse over. When using Bitmap actions on the left pane to capture bitmaps,
make sure the bitmap image and the captured image are the same.
If the bitmap on the screen needs time to appear, then use WaitForBitmapAppear action instead of FindBitmap. You can also specify the wait time for the bitmap
to appear in the WaitForBitmapAppear window. If you enter 5 as below, for example, this means the scenario will look for the image for 5 seconds before it
decides a fail or success.
If you captured the bitmap on one machine and then moved your scenarios to a different machine, then make sure the two machines have same color depth and the
captured image matches the original.
Another way of capturing the bitmap is without using waitForBitmapAppear action:
You can take the bitmap yourself using snapshot or pint screen on your keyboard (make sure you don't edit the image or change the format). You can capture the image itself and save it as bitmap using "paint" program. Make sure you save the bitmap same color depth as the machine you are running the scenario on. For example, If the machine depth is 16bits then you should save the bitmap as 16 bits.
Save the image in your scenario scripts [scenario]_files folder
and give it a meaningful name, in our example we will use products.bmp
Open your scenario file in Text Editor "notepad", for example, and add the following line where appropriate
products is the name of the image we saved 81 is the width of the saved image 95 is the threshold of the image we saved 640 is the x position on the screen where you captured the bitmap 286 is the y position on the screen where you captured the bitmap 4 This is cursor position (center) 10 is the time wait for the bitmap to appear 0 Search Region (x) top from (top, left) 0 Search Region (y) left from (top, left) 0 Search Region (x) from (bottom, right) 0 Search Region (y) from (bottom, right)
My Scenario fails before it's complete and I get "Playback failed to complete within specified duration of [number of seconds] :
You can set the scenario time by going to File then Scenario Properties from your Station and set the "Playback Error After" time. The duration time of your
actual scenario plus ( Event Enterval * number of lines in your scenario ) should be equal or less than "Playback Error After" time. The Event Enterval means
to wait for the specified time in milliseconds before it executes each line in your scenario. It can also be specified by going to File then Scenario
Properties from your Station
My scenario fails and I have many applications open. How can close all those open applications?
In your Station, go to File then choose Scenario Properties: Input the command to execute on scenario failure. The command you enter will be
executed at the specific station where the scenario fails.
You can enter more than one command, for example,
taskkill /im iexplore.exe /im wfica32.exe /f
The above command will kill all "Internet Explorer" running and "Citrix ICA Client Engine" running.
note: This command is a windows command. You can enter any windows command that is installed on your windows OS in this option box.
My scenario would not start from Chroniker. I can run the scnenario fine from Scenario Station but not from Chroniker, why?
The machine where you have Scenario Station installed must be logged on all the time and never goes into sleep mode. Make sure to disable screen savers. However, the machine can be locked for security.
If you are monitoring the station through an RDP session to the machine where Scenario Station is installed, make sure that it is a console session. The script will run on the Console not inside the RDP.
Note: when you open a console RDP session, the actula console will be logged off, so once you are done from the Console RDP, log it off and make sure that the console is logged back on.
When installing Scenario Station, the web default port of scenario station is 8000 unless it is changed. You can test the connectivity between the station and Chroniker by openning a web
browser on Chroniker machine and type the following URL in the address bar http://[IP of Scenario Station machine]:8000
You should see a Remote Locations page. If you don't see the page, then:
check any firewall connections between Chroniker Base machine and Scenario Station machine if each is installed on its own machine.
And check that you have registered Scenario Station with the correct port by going to tools-> Scenario Stations page, then edit the station.
Yes. The saved scenario file can be found under your \My Documents\AppLoader Station\script\ folder. You can open the scenario file in notepad or any text editor to modify it.
Go to your AppLoader Station and click on Tools then Options. Check the host and the port. The host should be the host of the machine where Console is installed, and the port is the Station listening port, the default port is 11003 or the port you specified when installing the Station. If this information is blank or incorrect then the Station is not able to read the registry or the registry information is incorrect.
To resolve this issue:
Make sure to close the Console, Session Initiator, and Log off current users on Terminal Server. (To Log off current users, log in to the Terminal Server as an administrator and go to Task Manager then go to Users Tab and right click on the users to log them off.
Go to start then run. Type regedit then hit enter
HKEY_LOCAL_MACHINE -> SOFTWARE -> CHRONIKER -> AppLoader (click on AppLoader)
On the left pane you will see the keys, make sure they are correct
Make sure your users have full access to the registry. To give permissions: right click on AppLoader (located in HKEY_LOCAL_MACHINE -> SOFTWARE -> CHRONIKER -> AppLoader) and click on Permissions.
Go to start -> run and type services.msc then hit enter. Restart Chroniker Agent Service.
Launch AppLoader Console, the Session Initiator and test your connection
Make sure the bitmap you selected matches the image. For example, some images change on mouseover. Also make sure that the image has the same color depth as the machine running the scenario.
My Scenario keeps failing at a certain bitmap image:
Check to see that your bitmap does not change color or style on mouse over. When using Bitmap actions on the left pane to capture bitmaps,
make sure the bitmap image and the captured image are the same.
If the bitmap on the screen needs time to appear, then use WaitForBitmapAppear action instead of FindBitmap. You can also specify the wait time for the bitmap
to appear in the WaitForBitmapAppear window. If you enter 5 as below, for example, this means the scenario will look for the image for 5 seconds before it
decides a fail or success.
If you captured the bitmap on one machine and then moved your scenarios to a different machine, then make sure the two machines have same color depth and the
captured image matches the original.
Another way of capturing the bitmap is without using waitForBitmapAppear action:
You can take the bitmap yourself using snapshot or pint screen on your keyboard (make sure you don't edit the image or change the format). You can capture the image itself and save it as bitmap using "paint" program. Make sure you save the bitmap same color depth as the machine you are running the scenario on. For example, If the machine depth is 16bits then you should save the bitmap as 16 bits.
Save the image in your scenario scripts [scenario]_files folder
My Documents\AppLoader Station\script\[scenario]_files folder
and give it a meaningful name, in our example we will use products.bmp
Open your scenario file in Text Editor "notepad", for example, and add the following line where appropriate
products is the name of the image we saved 81 is the width of the saved image 95 is the threshold of the image we saved 640 is the x position on the screen where you captured the bitmap 286 is the y position on the screen where you captured the bitmap 4 This is cursor position (center) 10 is the time wait for the bitmap to appear 0 Search Region (x) top from (top, left) 0 Search Region (y) left from (top, left) 0 Search Region (x) from (bottom, right) 0 Search Region (y) from (bottom, right)
My Scenario fails before it's complete and I get "Playback failed to complete within specified duration of [number of seconds] :
You can set the scenario time by going to File then Scenario Properties from your Station and set the "Playback Error After" time. The duration time of your
actual scenario plus ( Event Enterval * number of lines in your scenario ) should be equal or less than "Playback Error After" time. The Event Enterval means
to wait for the specified time in milliseconds before it executes each line in your scenario. It can also be specified by going to File then Scenario
Properties from your Station
My scenario fails and I have many applications open. How can close all those open applications?
In your Station, go to File then choose Scenario Properties: Input the command to execute on scenario failure. The command you enter will be
executed at the specific station where the scenario fails.
You can enter more than one command, for example,
taskkill /im iexplore.exe /im wfica32.exe /f
The above command will kill all "Internet Explorer" running and "Citrix ICA Client Engine" running.
note: This command is a windows command. You can enter any windows command that is installed on your windows OS in this option box.
If you get the message "Access Denied" or "The remote machine does not exist or is unavailable":
Check that you have local Administrator rights on the target machine. WMI will not function unless the account you are using has local Administrator rights on the machine you wish to monitor.
Check that DCOM is enabled on both the host and the target PC. Check the following registry value on both computers:
Key: HKLM\Software\Microsoft\OLE, value: EnableDCOM, should be set to 'Y'
Check that WMI is installed. WMI is present by default in all flavors of Windows 2000 and later operating systems, but must be installed manually on NT4 systems.
To check for the presence of WMI, type "wbemtest" into the Run box (Start Menu). If the WMI Tester application starts up, then WMI is present, if not, it must be installed.
Ensure that WMI permissions have been set correctly.
On a Windows XP Pro computer, make sure that remote logons are not being coerced to the GUEST account (aka "ForceGuest", which is enabled by default computers that are not attached to a domain). To do this, open the Local Security Policy editor (e.g. by typing 'secpol.msc' into the Run box, without quotes). Expand the "Local Policies" node and select "Security Options". Now scroll down to the setting titled "Network access: Sharing and security model for local accounts". If this is set to "Guest only", change it to "Classic" and restart your computer.
Also on an XP computer running SP2, configure the firewall to allow remote administration. To do this, open a command prompt and type: netsh firewall set service RemoteAdmin
If you have other internal firewalls on your network, you may have to configure them to allow WMI messages.
Even if you are not knowingly running any firewall software, bear in mind that big-name antivirus solutions such as those produced by McAfee and Symantec often contain their own firewall functionality. If such software is not properly configured to allow WMI traffic, then this may be the cause of the problem.
Make sure that no remote access or WMI-related services have been disabled. On an XP machine, the following services should be running (or at least allowed to start on demand):
COM+ Event System
Remote Access Auto Connection Manager
Remote Access Connection Manager
Remote Procedure Call (RPC)
Remote Procedure Call (RPC) Locator
Remote Registry
Server
Windows Management Instrumentation
Windows Management Instrumentation Driver Extensions
WMI Performance Adapter
Workstation
There are two ways you can fix this -
Enable RPC permissions in the Domain Group Policy
-OR-
Enable RPC permissions on a single target machine
Enable RPC permissions in the Domain Group Policy:
Run Microsoft Management Console on a Windows XP machine (Start|Run|mmc). Note: The Group Policy Object Editor for Windows 2000 does not have the required template to edit Windows XP Firewall settings, thus it must be run under Windows XP.
Select the Group Policy Object for which you want to enable RPC ( Normally this will be the "Default Domain Policy", but if you already have other Group Policy Objects enabled for your networks, select the appropriate one )
Navigate to: [Group Policy Object]|Computer Configuration|Administrative Templates|Network|Network Connections|Windows Firewall|Domain Profile ( for a Domain administered network - Standard Profile for a Workgroup network )
Set "Allow unsolicited incoming messages from:" to "localsubnet" (without the quotes)
Apply settings
These settings will not generally take effect immediately. You can use Microsoft's Group Policy Update Utility to force immediate updates ( see Microsoft's article: "A Description of the Group Policy Update Utility" )
Enable RPC permissions on a single target machine:
Run Microsoft Management Console on the target machine (Start|Run|mmc)
Select the "Local Computer" Group Policy Object for which you want to enable RPC
Navigate to: [Group Policy Object]|Computer Configuration|Administrative Templates|Network|Network Connections|Windows Firewall|Domain Profile ( for a Domain administered network - Standard Profile for a Workgroup network )
Set "Allow unsolicited incoming messages from:" to "localsubnet" (without the quotes)
Apply settings
These settings will not generally take effect immediately. You can use Microsoft's Group Policy Update Utility to force immediate updates ( see Microsoft's article: "A Description of the Group Policy Update Utility" )
In order to access WMI on a remote machine, you'll need to alter the WMI security on the remote computer and restart the WMI service. This can all be accomplished through the Computer Management Console in the control panel shown in Figure 2. Right clicking on the WMI Control of the Services and Application section allows you to access the WMI Properties.
Computer Management Console in the System Administration Tools of the Control Panel
This will bring up the WMI Control Properties dialog shown in Figure 3. This dialog will allow you to change the security on the particular WMI node you are trying to access. In this case we want to change the security on the CIMV2 node to enable remoting.
WMI Control Properties Dialog (Security Tab)
Clicking the security button opens a dialog that allows us to change security on the computer to enable remoting as shown in figure 4. We will give remote access to everyone in this case.
Allow Everyone Remote Access to WMI
Now we simply restart the WMI service in the computer management console as shown in figure 5.
Remote Procedure Call (RPC) dynamic port allocation is used by remote administration applications such as Dynamic Host Configuration Protocol (DHCP) Manager, Windows Internet Name Service (WINS) Manager, and so on. RPC dynamic port allocation will instruct the RPC program to use a particular random port above 1024.
Customers using firewalls may want to control which ports RPC is using so that their firewall router can be configured to forward only these Transmission Control Protocol (TCP) ports.
The following registry entries apply to Windows NT 4.0 and above. They do not apply to previous versions of Windows NT. Even though you can configure the port used by the client to communicate with the server, the client must be able to reach the server by its actual IP address. You cannot use DCOM through firewalls that do address translation (e.g. where a client connects to virtual address 198.252.145.1, which the firewall maps transparently to the server's actual address of, say, 192.100.81.101). This is because DCOM stores raw IP addresses in the interface marshaling packets and if the client cannot connect to the address specified in the packet, it will not work.
MORE INFORMATION
The values (and Internet key) discussed below do not appear in the registry; they must be added manually using the Registry Editor. Also, note that you must use Regedt32.exe instead of Regedit.exe to add the REG_MULTI_SZ value.
Warning*** If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. We cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
With Registry Editor, you can modify the following parameters for RPC. The RPC Port key values discussed below are all located in the following key in the registry: HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Internet\ Key Data Type
Ports REG_MULTI_SZ
Specifies a set of IP port ranges consisting of either all the ports available from the Internet or all the ports not available from the Internet. Each string represents a single port or an inclusive set of ports (for example, "5984" or "5000-5100" ). If any entries are outside the range of 0 to 65535, or if any string cannot be interpreted, the RPC runtime treats the entire configuration as invalid.
PortsInternetAvailable REG_SZ - Y or N (not case-sensitive)
If Y, the ports listed in the Ports key are all the Internet-available ports on that computer. If N, the ports listed in the Ports key are all those ports that are not Internet-available.
UseInternetPorts REG_SZ - Y or N (not case-sensitive)
Specifies the system default policy.
If Y, the processes using the default will be assigned ports from the set of Internet-available ports, as defined previously.
If N, the processes using the default will be assigned ports from the set of intranet-only ports.
Example:
