Hi,
We are using BO XI R3.1 version, and we never used the dash board here . Now when we are trying to access dashboard in Infoview its giving error as There is no AA Analytics Server available. Contact your Business administrator to verify status. AA2213
Even when we are trying to see settings Dashboard and Analytics setting same message appears.
We tried dashboard related server restart and also all server restart, but still problem exists.
Just had to reinstall my QA environment from scratch and am now getting that message. (Fully patched to FixPack 2.7)
I am in the process of verifying EVERY setting between my QA and Production environments (It’s working fine on production) and so far everything is identical. It’s the one thing that doesn’t seem to be working.
EDIT:
Ohh and I verified that the “AAAnalytics.exe*32” is running in Taskmanager, so it ‘seems’ to be running fine.
“I verified that the “AAAnalytics.exe*32” is running in Taskmanager, so it ‘seems’ to be running fine.”
But I am not getting where you checked “AAAnalytics.exe*32” because I am not getting in Task manager. Could you elobrate more on this.
Thanks in Advance
Vishal
[/quote]
I’m not sure what there is to elaborate… if I open Windows Taskmanager on the server, I can see that the PID created by the Business Objects Dashbaoard Analytic Server is linked to a Windows Processes called “AAAnalytics.exe”, in my case since I’m on a 64bit OS, it also denotes *32 indicating it’s a 32bit process.
Basically I’ve verified that the process that is supposed to be running is in fact running. I don’t know why Business objects is saying it’s not there.
I’ve had a ticket open with SAP and they’ve contacted me once already but after an hour or so on the phone and WebEx, they said everything is setup properly and they didn’t understand why it was happening. It was being ‘escalated’ but so far no response from SAP in about a day after that esclation.
PS: In case I didn’t mention it before, this is a Fresh installation of XIR3.1 SP2, Fixpack 2.7. I’m starting to think that perhaps something is messed up in the installation scripts that is causing the issue. My Production environment which was XIR3.1, SP1 then upgraded through Fixpack 2.7 does not have this issue.