Site Usage Analysis is not working in PRoject Web Access.

W

waqas sarwar

Hi Project server / WSS gurus

I am wondering about the problem how can i set the Usage Analysis . I set
the Usage Anaylsis and then wait for the 24 hours but when i go the PWA sites
then go under the "Site Settings" click the "Site usage report " under the
heading "Site Administration". but its show this error:

"A usage report is not available for this site. Usage processing may be
disabled on this server or the usage data for this site has not been
processed yet. "

Even i already set it.

Kindly help me in this regard. I shall be much obliged for it
thanks
waqas
 
A

Aj

Waqas,

It could be the reason that you have not set the site usages
configuration properly in WSS Central admin area. Check whether you
have admin access to the central admin area (not the project server
settings). If you have,set the usage analysis report configuration as
I have explained in the last section of my reply. But before that, I
thought to explain the usage analysis process (I hope this should be
helpful for u). The tracking of usage data takes up a lot of disk
space on the Web front-end server and the server where the content
database is located. If you want to conserve disk space, you can stick
to the default option and leave usage analysis processing disabled. In
this scenario, you could use third-party tools to analyze the IIS
logs. However, if you want to use the site administration pages to
view usage data, you need to enable the processing of the usage logs.

By default, the log files are set to be processed every day at 1:00
A.M. During this process, the content of the Windows SharePoint
Services logs is aggregated, summarized, and written to the content
database. You can schedule the usage log to be processed at a more
convenient downtime for your websites or for your SQL Backup schedule.
You can specify an interval, by specifying the start time and end time
of the interval, during which the usage processing job starts. The job
is guaranteed to start at some time within the interval, but you
cannot control when the job ends. If your websites are primarily used
by internal employees, for example, you might schedule the log to be
processed at night, when demand on the sites is lower than during
working hours.

If your websites are primarily used by internal employees, for
example, you might schedule the log to be processed at night, when
demand on the sites is lower than during working hours. Because usage
analysis processing runs only once a day, when you enable usage
analysis processing, you will not see any data until the next day. Log
processing is done only for a single day’s worth of data. If you turn
off the log processing for a week but leave the data logging turned
on, the next time you turn on processing, it will process only the
previous day’s log files. The log files for all the days before that
will remain unprocessed.

The tracking of usage data takes up a lot of disk space on the Web
front-end server and the server where the content database is located.
If you want to conserve disk space, you can stick to the default
option and leave usage analysis processing disabled. In this scenario,
you could use third-party tools to analyze the IIS logs. However, if
you want to use the site administration pages to view usage data, you
need to enable the processing of the usage logs. By default, the log
files are set to be processed every day at 1:00 A.M. During this
process, the content of the Windows SharePoint Services logs is
aggregated, summarized, and written to the content database. You can
schedule the usage log to be processed at a more convenient downtime
for your websites or for your SQL Backup schedule. You can specify an
interval, by specifying the start time and end time of the interval,
during which the usage processing job starts. The job is guaranteed to
start at some time within the interval, but you cannot control when
the job ends. If your websites are primarily used by internal
employees, for example, you might schedule the log to be processed at
night, when demand on the sites is lower than during working hours.
Because usage analysis processing runs only once a day, when you
enable usage analysis processing, you will not see any data until the
next day. Log processing is done only for a single day’s worth of
data. If you turn off the log processing for a week but leave the data
logging turned on, the next time you turn on processing, it will
process only the previous day’s log files. The log files for all the
days before that will remain unprocessed. When you configure usage
analysis processing for a server, it takes effect for any existing
virtual servers. If you later add a virtual server, you must configure
usage analysis processing again to enable usage analysis for the new
virtual server.

To configure usage analysis processing for a server, perform the
following steps:
1. Click Start, point to All Programs, point to Administrative Tools,
and then click SharePoint Central Administration or Windows SharePoint
Services Central Administration. The configuration takes effect for
any existing virtual server, so it does not matter which of these
pages you use.
2. Under Component Configuration, click Configure usage analysis
processing.
3. In the Logging Settings section, select the Enable logging check
box.
4. In the Log file location box, type the location to store the log
file.
5. In the Number of log files to create box, type a number between 1
and 30.
6. In the Processing Settings section, select the Enable usage
analysis processing check box.
7. Under Run processing between these times daily, specify the range
of times to start the usage analysis log processing. In the Start box,
select the earliest time of day to begin running log processing. In
the End box, select the latest time to end running log processing.
8. Click OK.

You can also configure usage analysis processing at the command prompt
by using the Stsadm.exe tool. This tool can be used to schedule the
timed job responsible for starting the processing of log files.

Hope this helps.

Ajit
www.epmguru.com
 
W

waqas sarwar

Hello AJ,

Thanks for reply. Its a excellent reply. I got alot of stuff from it. But
their is little issue stil left. Like i configure the site "Usage analysis
processing" as per your instructions. But after 24 hours when I visited the
site page i found 2 things.

1) when i visited the WSS Sites its showed the data for the both "Site
Collection Usage Summary" under the Site Collection Administration and "Site
Usage Report " under the Site Administration. Succesful.

2) But when i visited the PWA sites its shows the Data only for the "Site
Collection Usage Summary" under the Site Collection Administration but fo the
"Site Usage Report " under the Site Administration it shows the same error
message which i mentioned in my 1st email that is
"A usage report is not available for this site. Usage processing may be
disabled on this server or the usage data for this site has not been
processed yet."

I am wondering why its not work for the Project Web Access site? Please
guide under your experince.

Thanks
Waqas
 
A

Aj

Hi Waqas,

Really sad to hear that you still have the same problem.

I can now understand where the problem lies.

Your WSS central admin is keeping a track of the all the sub sites
(including PWA sites usage records). This log file is a master log.
You can verify this by visiting the log file root. The default path
for (if you have not changed the path for wss logs) log files are in
%windir%\system32\LogFiles\STS.

By default, the log files are in %WinDir%system32\LogFiles\STS. You
can specify any other location you prefer for this root log folder.

If you choose a different log file location, you must be sure to give
the STS_WPG user group Read, Write, and Update permissions to the
directory. Without these permissions, the usage log files cannot be
created or updated by Windows SharePoint Services. Inside this folder
is a folder for every virtual server named using the Windows
SharePoint Services virtual server globally unique identifier (GUID),
and under those folders, a different folder for each day will be
generated. The path of these folders cannot be modified.

Check there whether you have the logs for PWA within Project Server
Folder.

If not increase the number of log files to maximum (30) in the Number
of log files to create box (you have to go back to the usage log
setting area in SharePoint central admin).

This should work. If you get the PWA site (collection) reports from
the WSS central admin (site usage) log, then your problem is solved:)

Coming back to the PWA issue, the default log file path for PWA is
stored inside Microsoft shared folder. I think from your statement "By
the way i store the Log Files in the Folder where i have put my
Backup", the path is creating the problem.

Please let me know if this helps.

Ajit
www.epmguru.com
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top