Cannot Access Cube -- Need Assistance

[Guest]

Before noon today, PWA was working fine. The business users were entering
resources and working in portfolio analyzer. Then, one user got what she
described as a "fatal error" and then was unable to view any resources or
projects. The symptoms are identical to KB 832588 (projects redirects to
home page and resources gives error msg "An error occurred while trying to
access the resources stored on the database. Either there are too many
resources, or the project server may not have the correct DSN configuration.
Contact the server administrator"), however, I have done the following
things

1. Used EditSite to test for connectivity -- all passed fine
2. Used PSCOM+ to reset OLAP administrator -- solved nothing
3. Verified that MSADC namespace was an excluded path in WSS.
4. Verified passwords for msprojectserveruser and msprojectuser.
5. In Analysis Manager, verified the connection of the DataSource and
manually reprocessed the cube.

Can anyone offer any suggestions. I have to have this up for a demo on Wed.

Thanks.

John Willard
Sr. IT Architect
VA Dept of Transportation

 

[Gary L. Chefetz [MVP]]

John:

Are you seeing errors in the application event log?

--


Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

For Project Server FAQs visit
http://www.projectserverexperts.com

For Project FAQs visit
http://www.mvps.org/project

 

[Guest]

Thanks, Gary

It was a permissions error after all. And the demo got postponed, so I could
stop the panic attack and think through things the right way.

Thanks for all your help, all the time. Your past postings have helped
without my having to post questions.

John

 

[KJW]

I was hoping John might come back and more specifically identify the security
setting he had to adjust to fix the issue. I have checked everything from
the WSS Managed paths exclusion to the MSADC directory configuration to the
local user's ActiveX permissions in IE and I can't seem to shake an isolated
issue that, like John, was very similar to the issue in KB832588 but not
resolved by MS's fixes.

And the Application event log shows nothing related to IE.