Link to home
Start Free TrialLog in
Avatar of QPR
QPRFlag for New Zealand

asked on

Web Analytics reports cannot be displayed

Web Analytics reports cannot be displayed because the Web Analytics Service Application is not provisioned. Contact the farm administrator to request that the Web Analytics Service Application be provisioned.

Googled this and it spoke of services and web apps needing to be turned on - as far as  can tell there are.
Where exactly should I be looking to get this working.
It seemed to work fine on the Dev server OOTB but not the production server.
Only difference being that the Dev server is a clean 2010 install where as the production server is an in place upgrade from 2007 MOSS to SP 2010
Avatar of Justin Smith
Justin Smith
Flag of United States of America image

In central admin, if you go to app management - manage service applications.  Do you see a Web Analytics Service App?
Avatar of QPR

ASKER

I have one called WSS_UsageApplication with a description of "Usage and Health Data Collection Proxy" which is apparently started.
Is that the one?
ASKER CERTIFIED SOLUTION
Avatar of Justin Smith
Justin Smith
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of QPR

ASKER

Can't see any drop downs other than the site actions one and I'm farm/collection admin/owner
Have included a screenshot of what I can see
CentralAdmin.gif
Avatar of QPR

ASKER

cancel that... I thought I was!
My other account has the "new" button... maybe because my usual domain account does not have local admin on the SP server but this other one does maybe?
Is it because you have a proxy highlighted?  
Yeah, you need to be a local admin for some reason for some functions to work in 2010.
Avatar of QPR

ASKER

ok so I clicked new and selected web analytics app and am wondering if I should use an existing app pool or create a new? I know what app pools are but am not sure of the ramifications (SP) of using an existing - what is best practise?
Built in user (e.g. networkservice)? predefined one or new?
For most people, all service apps can run under the same app pool, which uses a domain account.  The only exceptions would be Search.

I always suggest domain accounts for everything, though it may not be critical with the Web Analytics app.
Avatar of QPR

ASKER

ok thanks, I used an existing one called SharedServices1_V14
Or should I will when I get past the last two questions it needs to know.
Staging database name? Report Server name?
Is it asking me to invent names or to use existing DBs?
We have a SQL RS instance on the database server and the DB is just called ReportServer

Or does it just want something like
WA_Staging and WA_Reports so it can create them?
Avatar of QPR

ASKER

ok I took a guess and just made up a couple of names - so far so good... just have to do this now

The following Web Analytics Service Application has been successfully created: Web Analytics Service Application 1

To complete setup, confirm that:

1. The Web Analytics Data Processing Service and the Web Analytics Web Service have been started. (Click "System Settings" on the Central Administration home page, and then click "Manage Services on Server")

2. The Events to Log check boxes are selected for the required data points you want to log. (Click "Monitoring" on the Central Administration home page, and then click "Configure usage and health data collection")

3. The State Service Application is provisioned.
Avatar of QPR

ASKER

looks like I'm good to go!
I go to the reports page now and now see all the traffic stats (which of course are all zero as we haven't been logging)

Thanks for the pointer