G
Gary
Hello,
For those of you that have encountered issues with adding hit counters to
your FP server extended sites, I am submitting a resolution to this issue.
After lots of frustration I submitted a case with Microsoft and did get a
resolution.
Please note, my sites are hosted on a Windows Server 2003 with IIS 6
running. In summary, URLScan is locked down pretty tight on the default
installation of IIS 6 and will usually require modification of the .ini
file.
**************************************************************************************************
Cause:
=====
1. The URL scan is installed in the web server. The URL scan was not
configured to enable the hit counter.
Resolution:
=====
Applied the following steps and it resolved the issue.
1. Right-click the Start menu, click Explore, and then locate the
following folder (where %windir% is your Windows folder, such as C:\Windows
or C:\Winnt):
%windir% \system32\inetsrv\urlscan
2. Right-click the Urlscan.ini file, and then click Copy.
3. Right-click the folder, and then click Paste.
4. A copy of the file is created and named Copy of Urlscan.ini.
5. Double-click the Urlscan.ini file (the file opens in Notepad).
6. Make sure, you have the following entries in the [AllowVerbs]
section.
GET ; allow GET (most Web requests)
HEAD ; allow HEAD requests
OPTIONS ; allow OPTIONS (Web Folders need this)
POST ; allow POST (FPSE and HTML forms need this)
7. In the [DenyExtensions] section, remove the ".exe" extension to
enable hitcounter
8. Also use the following KB
article(http://support.microsoft.com/default.aspx?scid=kb;en-us;825538)to
configure enable editing of your site using FrontPage 2003.
For those of you that have encountered issues with adding hit counters to
your FP server extended sites, I am submitting a resolution to this issue.
After lots of frustration I submitted a case with Microsoft and did get a
resolution.
Please note, my sites are hosted on a Windows Server 2003 with IIS 6
running. In summary, URLScan is locked down pretty tight on the default
installation of IIS 6 and will usually require modification of the .ini
file.
**************************************************************************************************
Cause:
=====
1. The URL scan is installed in the web server. The URL scan was not
configured to enable the hit counter.
Resolution:
=====
Applied the following steps and it resolved the issue.
1. Right-click the Start menu, click Explore, and then locate the
following folder (where %windir% is your Windows folder, such as C:\Windows
or C:\Winnt):
%windir% \system32\inetsrv\urlscan
2. Right-click the Urlscan.ini file, and then click Copy.
3. Right-click the folder, and then click Paste.
4. A copy of the file is created and named Copy of Urlscan.ini.
5. Double-click the Urlscan.ini file (the file opens in Notepad).
6. Make sure, you have the following entries in the [AllowVerbs]
section.
GET ; allow GET (most Web requests)
HEAD ; allow HEAD requests
OPTIONS ; allow OPTIONS (Web Folders need this)
POST ; allow POST (FPSE and HTML forms need this)
7. In the [DenyExtensions] section, remove the ".exe" extension to
enable hitcounter
8. Also use the following KB
article(http://support.microsoft.com/default.aspx?scid=kb;en-us;825538)to
configure enable editing of your site using FrontPage 2003.