11-09-04 07:48 AM
I have seen this response posting in many places before, but it generally
does not answer the question that is being asked. It does not answer the
question about getting back to dynamically updating live data on the web
site. Front page sites can publish a Top 10 list and other usage related
summaries directly into web pages that are visible on the site in question.
A command line instruction is not useful for such automatic updates to a web
site.
I have confirmed that logs are being generated properly but the question I
am asking is how to restore the functionality that was available with FP2002
extensions on IIS5 servers to a W2003 server installation (IIS6). It seems
that this is a very pervasive question in many of the search results that I
have read, so I know that there are MANY of us struggling with the really
apparent loss of functionality with IIS6 and Front Page 2002 extensions..
I have several sites that have used this functionality to automatically
provide updated information to visitors to the sites. It is still a feature
in the FP2003 software and I am trying to learn if there is a different
Microsoft solution (like WSS...) that is needed to restore these lost
features.
I do not want to mess up the server by trying to force old STS extensions
since this is a dead technology and may or may not work. Hopefully, someone
that understands the Microsoft Web Server path can help with this posting.
Thanks,
Jeff W.
"Harikumar H [MSFT]" <harikumh@online.microsoft.com> wrote in message
news:iakjIjbxEHA.1884@cpmsftngxa10.phx.gbl...
> Hi Jeff,
>
> On a Windows 2000 server, in the FPSE admin web page to configure a site
> there is
> a section called usage analysis. This section is not there on the windows
> 2003
> machine. This is due to the following reasons.
>
>
> 1) Version 5012 of FrontPage Server Extensions that ships with Windows
2003
> is
> optimized for IIS 6.0.
>
> 2) Usage Analysis is not available on this version. Usage analysis uses
> OWSTimer
> which has been yanked out of Windows 2003. In other words Usage analysis
> will only
> work through the command prompt and not through the admin pages.
>
> the command to run usage is:
>
> owsadm.exe -o usage -p lm/w3svc/# where # is the instance number you wish
> to run
> usage against.
> This command can be scheduled using the windows task scheduler if you want
> to run
> it on a regular basis.
>
> Hope this helps
>
>
> regards
>
> Hari
> MSFT
>
> This posting is provided "as is" with no warranties and confers no rights
> --------------------
> |
> | What are the necessary steps to get back to the functionality that was
> | available running FP2002 extensions on W2000 server (IIS5) now that the
> | server is W2003? Some of the items that are no longer functional on the
> web
> | sites (that used to work) are the Top 10 lists, the usage analysis
> functions
> | and the email notifications that used to advise the webmaster that the
log
> | files were being updated. I have seen numerous posts about the ows
timer
> | service not being resident in the FP2002 extensions that come with W2003
> | Server and I'm wondering if this is the problem? The sites are all
> | functioning fine except for the items that I have mentioned. Do I need
to
> | load WSS on this server? Any suggestions would be appreciated.
> |
> | Thank you,
> | Jeff W.
> |
> |
> |
>
>
[ Post a follow-up to this message ]
| 
