The Netscape servers listed in the "Symptoms" section of this article
intermittently change the query string that is constructed by the hit
counter and passed to the hit counter executable file (Fpcount.exe).
The following are examples of query strings that are constructed by the hit
counter
and then passed to Fpcount.exe, and how the Netscape server determines the
location of the file that contains the hit counter information.
For Hit Counters on Pages in the Root Web
If the hit counter is on a page in the Root Web, the hit counter constructs
the
following query string and passes this string to Fpcount.exe:
_vti_bin/fpcount.exe/?Page=hitcounttest.htm|Image=4
In this example, the Netscape Enterprise server correctly determines the
location of the file that contains the hit counter information and
constructs
the path like this:
C:/Netscape/Server/docs/_private/hitcounttest.htm.cnt
For Hit Counters on Pages in a Sub web
If the hit counter is on a page in a subweb, the hit counter constructs the
following query string and passes this string to FPcount.exe:
_vti_bin/fpcount.exe/myweb/?Page=hitcounttest.htm|Image=4
In this example, the query string is structured in such a way that the
subweb is
not included. As a result, the Netscape Enterprise server incorrectly
determines the location of the file that contains the hit counter
information
and constructs the path like this:
C:/Netscape/Server/docs/myweb_private/hitcounttest.htm.cnt
Because this path refers to a file that does not exist in the content root,
the
hit counter will not work in a subweb on a Netscape Enterprise NT.
In this example, the correct location for the file that contains the hit
counter
information should be:
C:/Netscape/Server/docs/myweb/_private/hitcounttest.htm.cnt
The third-party products discussed here are manufactured by vendors
independent of Microsoft; we make no warranty, implied or otherwise,
regarding these products' performance or reliability.