Frequently Asked Questions - Answers

• Go to Control Panel > Windows Firewall
• Click on the Exceptions Tab
• Click on " Add Port " button
• Enter the name and port number
• Click OK

• Inside the IE window, click on the Tools Menu > Internet Options > Security Tab
• Click on the Trusted Sites Icon then click the Sites Button
• Add the Chroniker address in here and click ok.
• Do the same thing for the Local Intranet and Internet Zones
• Also check the Restricted Sites Zone and see if the Chroniker Site is there. If so then remove it.
• Allow cookies from Chroniker:
  • Click on the Privacy Tab then the Sites Button
  • Enter the Chroniker address in the given field and click the Allow Button.
  • Click ok.

• 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>

• Make sure you can connect to the network drive you are copying from/to with the username and password you provided.
• Make sure to add a trailing \ at the end of your destination path. For example, c:\temp\

• 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.

1. 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.
2. 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
3. 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.

The default wait time is 10 seconds. It can be modified as follow: 

1. If you are using WaitForWindowAppear Action then you can modify the wait time option in the "Select Window" popup window.
2. If you are using WaitForBitmapAppear Action then you can modify the wait time option in the "Select Bitmap" popup window.
3. If you are using Wait Action then you can modify the wait time option in the "Wait" popup window.

• 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).

• 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 
  
  [Chroniker Install Folder]\ScenarioStation\bin\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
  
  WaitBitmapAppear (products,81,95,640,286,4,10,0,0,0,0)
  
  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.

• Go to start then run and type cmd then hit enter
• Register Chroniker: Go to your <Chroniker Install Folder>\webserv\bin\
• Type regsvr32 /u mscomctl.ocx then hit enter
• Now Type regsvr32 /u <Chroniker Install Folder>\Webserv\bin\mscomctl.ocx then hit enter
• To register Station: Go to your <Chroniker Install Folder>\appsloader\agent\
• Type regsvr32 /u mscomctl.ocx then hit enter
• Now Type regsvr32 /u <Chroniker Install Folder>\appsloader\agent\mscomctl.ocxthen hit enter
• To register Console: Go to your <Chroniker Install Folder>\appsloader\Console\
• Type regsvr32 /u mscomctl.ocx then hit enter
• Now Type regsvr32 /u <Chroniker Install Folder>\appsloader\Console\mscomctl.ocx then hit enter
• To register Session Initiator: Go to your <Chroniker Install Folder>\appsloader\Initiator\
• Type regsvr32 /u mscomctl.ocx then hit enter
• Now Type regsvr32 /u <Chroniker Install Folder>\appsloader\Initiator\mscomctl.ocx then hit enter
• If the above does not work do the following:
• Go to c:\windows\system32
• Type regsvr32 /u mscomctl.ocx then hit enter
• Now Type regsvr32 /u c:\windows\system32\mscomctl.ocx then hit enter

• 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

Check the following:

1. Make sure you have enough resources on that machine to run the number of users you're running.
2. Make sure windows Screensaver and Terminal Server timeout session are disabled for all users. You can disable them by going to gpedit.msc
3. Make sure you don't see any errors popping inside the RDP sessions.

• 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
  
  WaitBitmapAppear (products,81,95,640,286,4,10,0,0,0,0)
  
  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.

1. 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.
2. 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'
3. 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.
4. Ensure that WMI permissions have been set correctly.
5. 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.
6. 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
7. 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.
8. 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

For more information about troubleshooting WMI, please see the Microsoft WMI troubleshooting site

You might need to reset WMI counters, to do so use the following from command line:

winmgmt /clearadap 
winmgmt /resyncperf

if the counters are still empty, then try the command:

wmiadap

1. 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.
   • Add "Group Policy Object Editor" snap-in (File|Add/Remove Snap-in...|Add...|Group Policy)
   • 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 )
     • Edit Setting: "Windows Firewall: Allow Remote Administration Exception"
     • Set "Enabled".
     • 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" )
2. Enable RPC permissions on a single target machine:
   • Run Microsoft Management Console on the target machine (Start|Run|mmc)
   • Add "Group Policy Object Editor" snap-in (File|Add/Remove Snap-in...|Add...|Group Policy)
   • 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 )
     • Edit Setting: "Windows Firewall: Allow Remote Administration Exception"
     • Set "Enabled".
     • 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" )

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.

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.

For more information see the following Microsoft white paper, "Using Distributed COM with Firewalls": 
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndcom/html/msdn_dcomfirewall.asp

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:

1. In this example, use ports 5000 through 5100 inclusive, so the new registry key appears as follows: 
   Ports: REG_MULTI_SZ: 5000-5100 
   PortsInternetAvailable: REG_SZ: Y 
   UseInternetPorts: REG_SZ: Y

2. Restart the server. All applications that use RPC dynamic port allocation use ports 5000 through 5100, inclusive. In most environments, a minimum of 100 ports should be opened, because several system services rely on these RPC ports to communicate with each other. 
   You should open up a range of ports above port 5000. Port numbers below 5000 may already be in use by other applications and could cause conflicts with your DCOM application(s). Furthermore, previous experience shows that a minimum of 100 ports should be opened, because several system services rely on these RPC ports to communicate with each other.

Note*** The minimum number of ports may differ from computer to computer and depends on the configuration of the computer. For additional information, look up the following article numbers in the Microsoft Knowledge Base: 
167128 Network ports used by remote helpdesk functions 
179442 How to configure a firewall for domains and trusts 
263293 Windows 2000 NAT does not translate Netlogon traffic 
172227 Network Address Translators (NATs) can block Netlogon traffic