Usage Analyst for Frontpage

[WTC]

Hello,

I am running IIS with FPSE 2002 installed on Windows Server 2003. I have
many client that are using FrontPage as their web page editor. Some clients
have complain that the usage analyst is not working for them.

I have the usage analyst turned on in the Front Page Server Administration
pages for all the site that have FPSE enabled and all log files for all
sites are enabled. The usage analyst is running on daily basis. In order to
get the usage analyst to work, I had to set up a scheduled tasks to run the
usage analyst for the clients on a daily basis with the following command.

owsadm.exe -o usage

Also the owstimer.exe is running as a process. I do not know why the FP
Server Admin is not doing this automatically. If I remove the schedule task,
the daily usage analyst will not run. If anyone could shed some light on
this, it would be most helpful.

 

[Tom [Pepper] Willett]

The usage analysis is enabled for root webs only, correct?
Your clients that are complaining are actually trying to view the usage
reports by opening them on the server, correct?

--
===
Tom [Pepper] Willett
Microsoft MVP - FrontPage
---
FrontPage Support:
http://www.frontpagemvps.com/

About FrontPage 2003:
http://office.microsoft.com/home/office.aspx?assetid=FX01085802
===
| Hello,
|
| I am running IIS with FPSE 2002 installed on Windows Server 2003. I have
| many client that are using FrontPage as their web page editor. Some
clients
| have complain that the usage analyst is not working for them.
|
| I have the usage analyst turned on in the Front Page Server Administration
| pages for all the site that have FPSE enabled and all log files for all
| sites are enabled. The usage analyst is running on daily basis. In order
to
| get the usage analyst to work, I had to set up a scheduled tasks to run
the
| usage analyst for the clients on a daily basis with the following command.
|
| owsadm.exe -o usage
|
| Also the owstimer.exe is running as a process. I do not know why the FP
| Server Admin is not doing this automatically. If I remove the schedule
task,
| the daily usage analyst will not run. If anyone could shed some light on
| this, it would be most helpful.
|
| --
| William
|
|
|

 

[WTC]

Hi Tom,

The usage analyst is enabled for the root webs, there is no sub-webs within
the root webs.

The clients are viewing the Usage reports by using the FrontPage Editor in
the report section when connected to the server.

To add more to this, I believe this may be a permission issue. The
SharePoint Timer services is starting through the "NETWORK SERVICE" account.
When I view the permissions for the log files in
"%windir%/system32/LogFiles/W3SVC*/*.log". The only permissions assigned to
this account are "SYSTEM" and "ADMINISTRATORS".

I know Windows XP Pro is different than 2003 Server, but the SharePoint
Timer Service is started by the "SYSTEM" account on the XP Pro system. Note:
I do not use Windows XP as a web server, this is my personal machine and I
did install the FPSE 2002 on it for testing.

When I view the permissions on the files located in the following directory:

C:\Program Files\common files\Microsoft Shared\Web Server Extensions\60\bin

The is no permissions listed for the account "NETWORK SERVICE". So am I
concluding if I change the Account to "SYSTEM" for the SharePoint Timer
Service, then the OWSTIMER.EXE process will process the usage stats for
these webs.

 

[WTC]

Just to update this thread,

I did change the SharePoint Service Timer start up account to the SYSTEM
account, and all seems to be functioning correctly.

--
William

Hi Tom,

The usage analyst is enabled for the root webs, there is no sub-webs
within the root webs.

The clients are viewing the Usage reports by using the FrontPage Editor in
the report section when connected to the server.

To add more to this, I believe this may be a permission issue. The
SharePoint Timer services is starting through the "NETWORK SERVICE"
account. When I view the permissions for the log files in
"%windir%/system32/LogFiles/W3SVC*/*.log". The only permissions assigned
to this account are "SYSTEM" and "ADMINISTRATORS".

I know Windows XP Pro is different than 2003 Server, but the SharePoint
Timer Service is started by the "SYSTEM" account on the XP Pro system.
Note: I do not use Windows XP as a web server, this is my personal machine
and I did install the FPSE 2002 on it for testing.

When I view the permissions on the files located in the following
directory:

C:\Program Files\common files\Microsoft Shared\Web Server
Extensions\60\bin

The is no permissions listed for the account "NETWORK SERVICE". So am I
concluding if I change the Account to "SYSTEM" for the SharePoint Timer
Service, then the OWSTIMER.EXE process will process the usage stats for
these webs.

--
William

The usage analysis is enabled for root webs only, correct?
Your clients that are complaining are actually trying to view the usage
reports by opening them on the server, correct?

--
===
Tom [Pepper] Willett
Microsoft MVP - FrontPage
---
FrontPage Support:
http://www.frontpagemvps.com/

About FrontPage 2003:
http://office.microsoft.com/home/office.aspx?assetid=FX01085802
===
| Hello,
|
| I am running IIS with FPSE 2002 installed on Windows Server 2003. I
have
| many client that are using FrontPage as their web page editor. Some
clients
| have complain that the usage analyst is not working for them.
|
| I have the usage analyst turned on in the Front Page Server
Administration
| pages for all the site that have FPSE enabled and all log files for all
| sites are enabled. The usage analyst is running on daily basis. In
order
to
| get the usage analyst to work, I had to set up a scheduled tasks to run
the
| usage analyst for the clients on a daily basis with the following
command.
|
| owsadm.exe -o usage
|
| Also the owstimer.exe is running as a process. I do not know why the FP
| Server Admin is not doing this automatically. If I remove the schedule
task,
| the daily usage analyst will not run. If anyone could shed some light
on
| this, it would be most helpful.
|
| --
| William
|
|
|