Profile 25 - Machine is not local error profiling web app

Brian Donahue

• Date: 7 Sep 2005
• Versions Affected: 2.0-2.5

When you are profiling a web application on the local computer, and the local computer is a server class with many websites differentiated by host headers, you may get an error from ANTS Profiler stating that it can only profile web applications on the local machine if you do change the server name in the address pull-down.

ANTS Profiler tries to resolve the host name of the address that you specify for profiling to the local computer. This means that the name of the server that you specify in the address pull-down must resolve back to the local computer, either in the DNS or in the hosts file. If you need to specify a host name other than your local computer name in order for your web application to work properly, you can do this by adding an alias into your hosts file. This file is shipped with Windows operating systems and exists in %SYSTEMROOT%\system32\drivers\etc. You may open this file using notepad.exe and add an alias using the example below.

This hosts file modification allows the profiling of a website called OnlineApps on a computer called BRIAN. Normally this would not be possible because of the error mentioned above.

# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost
#[My local IP (get this from ipconfig)]{TAB}[machine name]{TAB}[alias]
10.1.1.87 BRIAN OnlineApps