OLAP Problem - Urgent help

[Alvarez@discussions.microsoft.com Rene Alvarez]

I have installed a small farm (one application server and one database serve)
Project Server 2007 environment (Project Server 2007, SQL Server 2005,
Windows Server 2003). The cubes are being built correctly using a SQL Server
repository.
From the server I can create OLAP views and access them. However, from any
client machine, the views always show the error:
"An error has occured in the transport layer."
"The peer prematurely closed the connection."

Now, I installed all SQL client components (OLEDB and so) in 3 different
laptops, one with Vista, one with Windows 7 and a clean Windows XP with the
same error.

If I try to access the cubes from Excel, it works fine and I can see all the
information I need, but from PWA it simply won't work.

Please advise

[Uttkarsh Kalia]

Hi Rene,

To diagnose the OLAP error, I need you to check event manager>> Applications
and check whenever you try to access OLAP views from user computer does it
record any error's in Event Manager>>Application Log.

If it does, pls share the error. I am sure we will find solution for the same.

Cheers!
--
Uttkarsh Kalia

EPM Solution Specalist

[Barbara - Austria]

Hi Rene,

as far as I can remember I saw that once in an environment, where clients
hadn't been member of the same AD as Project Server. There I could solve it
by adding Project Server in Control Panel - User Accounts - Manage your
network passwords.

Not sure if that fits to your situation?
Regards
Barbara

"Rene Alvarez" <Rene Alv...@discussions.microsoft.com> wrote in message
news:6D9C6E64-3C34-4200...@microsoft.com...

[Rene Alvarez]

No errors that I can relate with it. The only two errors in Application Log
are:

"The resource file 'msmdsrv.rll' for locale '1034' could not be loaded.
Switching to US English (1033) if available.

and

"Sqlib error: Database WSS_Content_PWA of SQL Server instance is stored on
multiple volumes, only some of which are being shadowed".

The last one is from SQL but not Analysis Services, only the first one.
However, once again, the cubes are working perfectly from the server side.

I ran a SQL Profiler trace and founded that everytime a client tries to
connect, Analysis Services receives an "ANONYMOUS" login information. I think
this is it but still don't know how to correct it, and to determine if the
problem lies in the server or in the client.

[Rene Alvarez]

Barbara, thanks a lot.

I tried your suggestion but got the same result.