Unable to open View / pick element from subset in CubeViewer

[Lukas Meyer]

Hello,

Server & Client 9.1 SP3, Perspectives with Excel 2003 SP2, language in sync

Unfortunately I lost the screenshot of how the CubeViewer responds when opening a View directly from Server Explorer.
What happens is, that the view pops up for a split second, then closes and is replaced by "Error retrieving View Handle" (where the error message might not be accurate since I can't remember it. But If you had this error you will know what I am referring to, right?)
User was in the Admin group, no private elements. An other user - admin too - had private elements which he couldn't open either.

One cube was completely inaccessible, the other had two views which would not open due to above described error.

Restart solved the problem - for now.

I know it is not much to work with and usually I am better describing/documenting the error, but the server had to work ASAP so no time for debugging. (The copy of the tab is useless too - after restart everything works fine)

Since this is rather unusual, anyone who had this error might remember it and maybe knows why it happened?

What I tried in my desperation to reproduce it:
Created some views with only unnamed subsets
Added named subsets, dynamic & static
Deleted elements from dimension
Created private view using public subsets
Created private view using private subsets
Created private view using private & public subsets
Deleted some elements, added some
Messed a bit with security via rules & TI, without performing Securityrefresh (yeah, admin - but why not try?)
Executed the statement in my signature to really kill the stupid server, repeated all above steps.

No luck - I could always open the views...


edit:
Oh, I forgot my second problem I think might be similar, although it occurred at another server.

Server & Client 9.1 SP3, Perspectives with Excel 2003 SP2, language in sync

Have a look at the attached error-message.
This occurred when a user (in admin group) opened a view an tried to select an other element in a title dimension. The subset should be dynamic, but changing it to an other one didn't help. Restart solved the problem.
Since both servers are rather similar (security-distribution in process & rules) the errors could somehow be related...

[kangkc]

You may have a corrupted or missing subset somewhere.

[Lukas Meyer]

That was my first thought too - but a restart should not auto-repair subsets, eh? And if TM1 manged to have corrupt subsets in memory, everything is lost anyways, so that solution is not an option

[par3]

I remember getting that error if you got timed out. Or it can happen, like most times with me, is our wireless connection fails and you lose your IP. Subsequently you lose your connection to the Tm1 server as well.

[Lukas Meyer]

Thanks, that could come in handy for problems in the future, in this case it won't apply tough.
The first described problem occurred on the machine (via mstsc) itself, the second one was limited to that very subset, some other could still be accessed and altered.

A college of mine deleted the views blb-files prior to start of the server. Since my plain restart resolved the problem aswell, I don't suspect the blb-files to be corrupt or bad.
On the other hand the rules blb-files are really weird, inserting stupid newlines...

[David Usherwood]

Quite a few of our clients finish up with lots of extra lines in heavily edited rules. Most of them are on 90SP3U7 or U9.