Is there a way to "forcibly" dump a client's MSOLAP cache? (using PTSLite
for connections)

I am using a 3rd party OLAP browser (and don't tell me to whine to them.
It's a dead end) in a .NET app that works fine *UNTIL* any dimension/cube is
reprocessed by *ANYONE*. At that point, the control will not work, even if
it is destroyed and recreated. It returns the following error:

"The object invoked has disconnected from its clients."

Which I believe (in this particular context) means that some internal cache
is out of sync with the OLAP database (Analysis Services). I've gotten this
error from "raw" ADOMD as well. Closing and reopening (or opening a new)
connection does not reset it, either. The only way to get beyond the error
is to exit the whole application and reenter, at which point everything
works fine. That is, until something gets reprocessed....

It would seem that PTS maintains some kind of client cache that persists
unless the entire process exits. What I would like is some way of achieving
that without exiting the app. At the very least, if I can prove that PTS
isn't the culprit, I'll have a better position when dealing with the 3rd
party support....

GW

You can prove it very easily by demonstrating it with MDX Sample. If you do
full process of the cube while you are connected with MDX Sample, all it
takes to see new cube is to change database or reconnect. If the 3rd party
insists its a problem with PTS - ask them to contact us.

--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================

"Greg Walker" <Gregory.Walker (AT) Turner (DOT) c.o.m> wrote