There are a number of requirements when profiling scripts. If you get empty results when profiling scripts or if you cannot start profiling, most likely your computer or actions do not meet these requirements. Below are some tips that may help you solve the problem:

Check the profiler you use. Script profiling is only supported by the Performance, Coverage, Light Coverage and Function Trace profilers (currently, the Function Trace profiler does not collect information on values of script routines’ parameters).
Check if you are running multiple instances of AQTime. Only the first instance of AQTime can profile scripts and obtain results.
Check whether the tested application uses the Microsoft Scripting Engine, since AQTime can only profile those scripts that are executed by this engine.
If you profile scripts in Internet Explorer version 8 and later --
- Make sure that you close all Internet Explorer windows before you start profiling and that you do not open any irrelevant pages and windows until the profiling session is over.
- Make sure that the script code you want to profile is written in JScript. Starting from version 8, Internet Explorer does not support VBScript code profiling.
- Check other specifics of the Internet Explorer 8 mode described in the Profiling Scripts in Internet Explorer 8 and Later topic.
If you profile scripts in Internet Explorer version 7 and earlier, make sure that the Microsoft Script Debugger is installed on your computer. Note that there are several versions of the debugger and AQTime may not support some of them. For instance, there is a known problem with the script debugger installed by Microsoft Visual Studio 2008 and Microsoft Visual Studio 2010. Currently, AQTime cannot use this one for script profiling since the Visual Studio installation program replaces some debugger modules and AQTime stops working with the debugger properly. To avoid the problem, re-install Microsoft Script Debugger after installing Visual Studio 2008 or 2010.

To be sure you have the correct version of the debugger, follow these steps:
- Download and install all the updates available for the operating system.
  
  There is one exception: While updating, you may be suggested to install the most recent version of Internet Explorer. This update is not required, and you may skip it if you want to use another version of the browser.
- Download and install Microsoft Script Debugger from this site: http://www.microsoft.com/downloads/details.aspx?FamilyId=2F465BE0-94FD-4569-B3C4-DFFDF19CCD99&displaylang=en
- Download the PDM.dll from this page: http://www.dll-files.com/dllindex/dll-files.shtml?pdm. This DLL implements some debugger’s functionality.
- Replace the PDM.dll file in the <Windows>\System32 folder with the downloaded module.
- Open the Command Prompt window.
  
  Note that on Windows Vista and later operating systems, you need to launch Command Prompt with administrator privileges. You can do this in the following manner:
  - Open the Start menu.
  - Type cmd.exe in the Search box and press Enter.
  - Right-click cmd.exe in the search results and select Run as administrator from the context menu.
- Register the downloaded module with the following command typed in the Command Prompt window:
  
  regsvr32.exe C:\Windows\System32\pdm.dll
- Restart your computer, if the changes do not immediately take effect.
If you use a host application, it may not associate executed scripts with script modules added to the project. In this case, try checking the Entire Script Code area in the Code to Profile pane of the Setup panel.
If you profile with the “Attach-to-Process” feature, change the approach and try launching the host application from AQTime (you can specify the host application for your script units in the Run Parameters dialog).
If you profile scripts of ASP pages, make sure that the script is running on the client side. AQTime cannot profile server-side scripts of ASP pages.
Check whether the host application that executes the script code you want to profile is 32-bit. AQTime cannot profile scripts executed in 64-bit processes (except for the 64-bit version of Internet Explorer) because there are no script debugging libraries that can be used in these processes.
If you profile your scripts with the Coverage or Light Coverage profiler, the Report panel may sometimes contain duplicated results for some script routines (this problem is caused by some specifics of the script engine's and the profilers' functioning). In this case, you can use one of the following two approaches to resolve the problem:
- Remove all script files from the Modules pane of the Setup panel.
- Check the Entire Script Code area in the Code to Profile pane of the Setup panel.
-- or --
- Create a new including area in the Code to Profile pane of the Setup panel.
- Add all script routines from the Modules pane of the Setup panel to that area.
- Check the area with the script routines.
- Uncheck the Entire Script Code area.
If these tips do not help, send a message to SmartBear Support Team.

Profiling Scripts - Troubleshooting

See Also