AQTime can profile 64-bit applications, as well as COM, ASP.NET, IIS and service applications on 64-bit versions of the Windows operating systems (for information on supported versions, see System Requirements). Profiling of 64-bit applications has some specifics that are described further in this topic.
All AQTime profilers support 64-bit application profiling.
AQTime projects can contain either 32-bit or 64-bit modules, but not modules of both types. In other words, a project can contain modules having the same “bitness” . This is caused by the Windows operation system limitation: 32-bit modules can be loaded only into 32-bit processes and 64-bit modules -- only into 64-bit processes (a 32-bit module may not be loaded into a 64-bit process).
So, if the first module that you added to your AQTime project was 64-bit, you can continue adding only 64-bit modules. Similarly, if the first module was a 32-bit one, you can add only 32-bit modules later.
To change the “bitness” of your AQTime project, remove all modules from the project and then add modules of the desired “bitness”.
To profile 64-bit applications under Windows Server 2003 x64 edition, you should log into the session 0 (console session). To do this, you can run the Remote Console via the following command line:
In order for AQTime to be able to function on Windows Server 2008 R2, the WoW64 component of this operating system must be installed. The Server Core installation option for Windows Server 2008 R2 does not install WoW64 by default, so, you should install it yourself. Install the WoW64 component even if you are going to profile 32-bit modules on a 64-bit operating system.