Microsoft KB Archive/181662

= Hit Counter doesn't advance past 1 on IIS =

Article ID: 181662

Article Last Modified on 8/15/2006

-

APPLIES TO


 * Microsoft FrontPage 98 Standard Edition
 * Microsoft FrontPage 2000 Standard Edition

-



This article was previously published under Q181662



SYMPTOMS
When you preview a page that contains a Hit Counter, the Hit Counter does not advance past the number one. This problem occurs if you host the page that contains the Hit Counter on a Microsoft Internet Information Server (IIS) for Microsoft Windows NT Server.



CAUSE
This behavior occurs if the IUSR_ account does not have sufficient permissions to read and write to the .htm.cnt file, where is the name of the Windows NT server and  is the name of the page that contains the Hit Counter.

Note The .htm.cnt file stores a log of how many times the page was accessed, thus incrementing the Hit Counter.

This problem can also occur if the content has been copied or FTPd rather than published to the Web. You can recalculate hyperlinks to fix this situation.



RESOLUTION
Change the permissions on the .htm.cnt file to read and write for the IUSR_ account on the Windows NT server. To do this, follow these steps:  On the Windows Start menu, point to Programs, and then click Windows NT Explorer. Expand the following folder:

C:\Inetpub\wwwroot\_private\

 Right-click the Default.htm.cnt file, and then click Properties on the menu that appears. Click the Security tab.</li> Click Permissions. The IUSR_ should be listed. Double-click it to edit permissions. Select the following options:

Read (R)

Write (W)

NOTE: If the IUSR_ account is not listed, you must add it. To do this, click Add, click the IUSR_  account, and then click OK.</li> Click OK.</li></ol>

Note You must verify that the correct permissions are set for each page that contains a Hit Counter. By default the <Pagename>.htm.cnt files are located in the _Private folders in each Web.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

<div class="moreinformation_section">

MORE INFORMATION
When you enable Anonymous access, the IUSR_ account is used to authenticate. If the virtual directory is local to the computer, the Windows NT File System (NTFS) checks directory and file permissions. If this account does not have correct permissions on the directory, the Hit Counter does not increase. This is because Everyone has Full Control by default. Because the IUSR_ is a local account, it is included in Everyone.

If the virtual directory is on a remote server, then the computer uses the "Connect As..." information to retrieve the requested pages. The FrontPage Server Extensions are implemented as CGI applications. The computer starts these applications in a separate process with the context of the user who is logged on, in this case IUSR_. Then the Hit Counter application, FPCount.exe, tries to get the _private/<Pagename>.htm.cnt file on the remote server. The request fails with the error "ACCESS DENIED" because the IUSR_ account does not exist on the remote computer. The system retries until it times out. As a result, the page takes a long time to be displayed. Even if the share has assigned Everyone Full Control, the request fails because the user is unknown. When you enable the Guest account, the request does not work for the same reason.

If you disable Anonymous access and map the virtual directory to a Microsoft Site Server Membership Instance, then the computer uses the Windows NT Impersonation account. By default, this is the MemProxyUser1 account. To verify that this account exists, look in the Properties page of the Microsoft Site Server MMC Personalization and Membership Instance under Windows NT impersonation account. As with the other two accounts, this account must have access to either the local NTFS directory or be able to connect to the remote computer. To facilitate this you can configure a domain account.

<div class="references_section">