TM ART 0 functions - Many possible causes of getting 0 functions in TM ART Monitor Workbench for web applications.

Version 11
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    BMC Transaction Management Application Response Time - Infrastructure Edition


    BMC Transaction Management Application Response Time Monitor WorkBench


    BMC Transaction Management Application Response Time TM ART



    Workbench will not record. Shows Functions: 0. Zero functions get recorded. I am trying to record a script, but no functions get recorded in the TM ART Workbench recorder. Functions count not increasing






    Legacy ID:KA286577


    1. New Signing Code requirement in Windows 7 and Windows 2008 R2 and later

    AppInit_DLLs on Windows 7 and Windows Server 2008 R2 and later has a new code-signing requirement.


    This can result in 0 functions being recorded by the recorder.




    To work around this issue, the Registry key ‘RequireSignedAppInit_DLLs’ must be set to 0.




    Expand the registry Key HKEY_LOCAL_MACHINE | SOFTWARE | Wow6432Node | Microsoft | Windows NT | CurrentVersion | Windows | RequireSignedAppInit_DLLs


    •         Right Click RequireSignedAppInit_DLLs
    •         Select Modify
    •         Check that the value is 0




    2. TM ART 4.2 does not support IE11 for direct, hooking type of recording. The Technical Bulletin for Service Pack 4 for TM ART 4.2 is here:

    Page 2 has a section called
    Internet Explorer 11
    and it shows how to record using the proxy method.

    (In the Proxy Server settings of IE make sure you specify localhost for address. If you leave it empty you will get 0 functions.)

    3.  Must run Setup.exe as an Administrator when running application on a UAC System (Windows 7 and Windows 2008 R2 and later)




    When installing WorkBench on a UAC system, you must right click on the setup.exe and choose the option to "Run as Administrator".




    4. Make sure you clear the browser cache before you begin the recording. If you have visited that web site before then the browser may use the cache and thus generate no web traffic and thus there is nothing to record.




    5. Existing browser instance
    TM ART Monitor Workbench may not record browser traffic if an existing instance of the browser is open before the recorder is launched. Before recording, shut down existing instances of the browser.


    6. Application profile specifies the 64bit version of Internet Explorer
    TM ART Monitor Workbench is unable to record the 64bit version of Internet Explorer and the 32bit version should be specified at "SETTINGS | SYSTEM | RECORDER | APPLICATION PROFILE".
    If you are using a 64bit operating system the correct path to the 32bit version of Internet Explorer is usually "C:\Program Files (x86)\Internet Explorer\iexplore.exe".


    7. Internet Explorer 10 on a 64bit version of Windows 7 or Windows 8
    There is a known issue where the 64bit version of Internet Explorer 10 is launched even though the 32bit version is specified.
    This occurs because the "TabProcGrowth" registry entry is set to 0, meaning tabs are set to run in the same process as the manager process (64-bit), rather than opening a new process for each tab (32-bit). You can fix this by changing the registry entry here:


    HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\TabProcGrowth


    Set it to something greater than 0, restart IE, and you should see normal behavior resume.
    To check whether the 32bit or 64bit version of Internet Explorer is running, open task manager when Internet Explorer is running.
    The Internet Explorer processes are listed as either:
    iexplore.exe - this is the 64bit version
    iexplore.exe *32 - this is the 32bit version


    8. Incorrect setting of the registry key AppInit_DLLs
    NOTE Since BM TM ART 2.9 the recorder will check that this registry entry is correct and if not it will change the value to allow successful recording. Once recording is complete and the recorder is closed it will change this value back to the original. However, this will require that you are logged in with admin rights. If not you will continue to get the error. To correct this you will need to get someone with admin rights to log on and fix the registry key as detailed below and then ensure that the user without admin rights restarts the recorder again. If you are using a version earlier than 7.3 then you can either upgrade to that version or if you'd prefer to use your current version then continue reading the information for section 1.

    The Workbench Recorder uses the registry key AppInit_DLLs. If the entry for this key is incorrect the Recorder may not function correctly. To verify its setting

    ·         From the Start button select Run

    ·         Enter regedit and click OK

    ·         Expand the registry Key HKEY_LOCAL_MACHINE | SOFTWARE | Microsoft | Windows NT | CurrentVersion | Windows | AppInit_DLLs

    ·         Right Click AppInit_DLLs

    ·         Select Modify

    ·         Check that the value is exactly "qaphooks.dll"

    ·         Make sure that there are no trailing characters e.g. "," or " " (spaces)

    ·         Although this should resolve the issue, you may need to check step 2 below as the qaphooks.dll registry setting can change some default Workbench settings.


    For a 64 bit Operating Systems, the AppInit_DLLs registry key may be required in the registry location:[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows]

    If AppInit_DLLs is not already in that registry location with its value set to exactly "qaphooks.dll" you must create it.



    9. Incorrect application profile or proxies set up

    To verify the setup of your application profile


    ·         Select the Application Profile for the browser you are using

    ·         Click Edit

    ·         The Application Path should point to the browser executable.

    ·         The application type should be the type of the browser

    ·         In the PROTOCOL SELECTION area of this dialog, ensure that 'Web' checkbox is checked. The 'Web Settings...' button will then become active;

    ·         Select Winsock and the ws2_32.dll

    * NOTE  if the Winsock and the ws2_32.dll option is disabled (greyed out), please delete and recreate the PERFHK_NAME7x system variable. (START | SETTINGS | CONTROL PANEL | SYSTEM | ADVANCED | ENVIRONMENT VARIABLES | SYSTEM VARIABLES)


    To verify the setup of your proxies


    ·         Highlight SOCKS and click Edit

    ·         Protocol should be Socks

    ·         Listen port should be 19180 by default

    ·         Remote host should be "Any"


    ·         Highlight HTTP and click Edit

    ·         Protocol should be HTTP

    ·         Listen port should be 8080

    ·         Remote host should be "Any"




    10. Incorrect browser Settings

    For example, for Internet Explorer

    ·         Click TOOLS | INTERNET OPTIONS | CONNECTIONS Tab | LAN Settings

    ·         Automatically Detect Settings should be checked.

    ·         Verify that the settings for Use automatic configuration script and Use proxy server are correct for your environment



    11. Conflict with other Software

    Typically the software which causes conflicts with the Workbench recorder either hooks into the application that is to be recorded or hooks into the Operating System at a low level. If both applications are trying to use the same system or application resource then it is understandable how the conflict arises.


    To resolve this problem you may need to take different approaches depending on the software installed. This can entail stopping the service, editing a registry setting or uninstalling the conflicting software.  You may need to uninstall both TM ART Monitor Workbench and the conflicting software and then re-install TM ART Monitor Workbench. 

    The following are the applications that are known to conflict with BMC TM ART Workbench:

    • Google Toolbar Browser Addon
    • Aventail remote control software (similar to PC Anywhere)
    • Netinstaller Installer program
    • Net Medic (Hooks Browser to provide performance data)
    • NVDesk32 Video driver
    • Penicillin AntiVirus software
    • Zoftech
    • Babylon Translation software
    • Cisco Security Version
    •  Avecto Privilege Guard

    If you do not have any of the above installed on your machine then please use a tool such as Process Explorer to identify which dll's are loaded when your browser loads. This may help identify other software that causes such conflicts.
    For more information and to download Process Explorer see: SysInternal's Process Explorer

    You may wish to look at the other suggestions below before using Process Explorer as software conflict is not always the reason for the problem.





    12. Entries in the Extend.ini file

    Open file EXTEND.INI using notepad. This is normally found in
    C:\Program Files\BMC Software\BMC TM ART Monitor Workbench x.x

    The file should contain only the information outlined below.

    // BEGIN extend.ini header
    // (do not delete these header lines)
    // END extend.ini header




    13. Checking if another application is using the same listener port as the Workbench Recorder

    To find what ports are being used on your system

    ·         Open Workbench and start the recorder

    ·         Press Ctrl & Z (This will expand the recorder's GUI)

    ·         Click on the Log tab.

    ·         Press Ctrl & D (This will clear the log and show the current status of the recorder's listener port).

    ·         If you see an error similar to the following then another application is using the same port as the recorder.

    Error(#0, Bind: Could not start listening on port 8080, maybe there is another application listening on the same port)


    In order to change the listener port in Workbench

                                            ·         Click SYSTEM SETTINGS | RECORDER | PROXIES Tab

    ·         Select the SOCKS or HTTP proxy as appropriate and click Edit

    ·         Change the Listener port to something higher such as 19123





    14. Incorrect setting of the registry key BrowseNewProcess

    The registry key BrowseNewProcess specifies whether a new process is created for each instance of Internet Explorer. If the entry for this key is not "yes" all instances of Internet Explorer and Windows Explorer that you start are run in the same process. As a result, the Recorder may not be able to hook IE correctly.

    This registry key was changed by selecting Launch browser windows in a separate process option in the Tools | Internet Options | Advanced tab of versions of Internet Explorer before IE 5.01 and will probably only effect such versions.

    In order to verify that this registry key is set correctly:

    ·         From the Start button select Run

    ·         Enter regedit and click OK

    ·         Expand the registry Key HKEY_CURRENT_USER | Software | Microsoft | Windows | CurrentVersion | Explorer | BrowseNewProcess

    ·         Right BrowseNewProcess

    ·         Select Modify

    ·         Check that the value is exactly "yes"

    ·         Repeat this process for the registry Key HKEY_LOCAL_MACHINE | Software | Microsoft | Windows | CurrentVersion | Explorer | BrowseNewProcess

    See the Microsoft knowledge base for additional information on this setting.





    If necessary remove any other information and save the file.

     15. Wrong version of perfShkXX.dll.install


    In the C:\Windows\System32 folder there is a file called perfShkXX.dll.install where the XX is the version of TM ART being used. This file is responsible for hooking into the process to be recorded (i.e. initializing the recording functionality).


    Note: this file may also appear in the C:\Documents and Settings\\Local Settings\Temp\BMC TMART XX\program files\Borland\BMC TMART XX - depending on where the %TEMP% variable is set to.


    You should try deleting this file from the folder using the instructions below and rebooting the machine. Normally, this file can cause problems when there have been patches or hotfixes applied to the system which included this file and a wrong version of it is located in the system32, or relevant, directory.


    Note: there may be multiple files if multiple versions of TM ART Monitor Workbench are installed on the machine. All files should be removed in this case. Deleting this file will not have any negative impact on the system.


    Process to Delete


    Close the application to be recorded and the Recorder before deleting the file. This file is just a temporary file used for initializing the recording functionality. It will be generated again when the Recorder is started and the DLL is used for recording.




     The source/original file of this DLL is located in the TM ART installation directory. This file should not be deleted because it is used to copy into the system32, or relevant, directory.






    16. Sometimes starting the Internet Explorer starts explorer.exe instead of iexplore.exe.  See KA286578

    Bonus 1: See also this YouTube video entitled "Verifying Silk Performer DLL injection": 

    Bonus 2: TM ART 4.2 does not support Windows 2012 R2. 

    Bonus 3. If all else fails you could try the proxy technique of recording. 

    Bonus 4: If using Chrome or Firefox, try the 32 bit version instead of the 64 bit version. 

    We would recommmend you to move to TMART 4.2 SP7 as this is the latest. 


    Related Products:  
    1. BMC Transaction Management Application Response Time - Infrastructure Edition


    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles