TM1 Forum

Hi All,

I had a call from a user having issue with a slice containing a custom roll up displaying Key Errors under teh Roll Up consolidation but the correct values under the children elements.

After a few tests,
turn up that the user was connected from 2 different computer / excel sessions.

Once disconnected from one of the instance, the sllice containing the roll up behave correctly again.

I suspect that it is related to objects from the user folder such as views or private subsets are somehow locked by the first instance opened.
Any idea how this behaviour could be explained technically ?

Thanks,

Kind Regards,

Olivier

Olivier wrote:Hi All,

I had a call from a user having issue with a slice containing a custom roll up displaying Key Errors under teh Roll Up consolidation but the correct values under the children elements.

After a few tests,
turn up that the user was connected from 2 different computer / excel sessions.

Once disconnected from one of the instance, the sllice containing the roll up behave correctly again.

I suspect that it is related to objects from the user folder such as views or private subsets are somehow locked by the first instance opened.

I doubt it. To the best of my knowledge the server doesn't re-read the .vue or .sub files (or indeed any other files) while it's running, though it does write to them.

I recall once trying to do a sneaky end run to get a process migrated from my dev to my production environment without having to reboot the prod server. I did that by creating the process as a raw shell in Production, closing it, then copying over the .pro file from development. Didn't work. When I reopened the process the raw shell was still there, which suggests that the server had it in memory and wasn't reading from the disk. I had to copy over the code tab by tab, then save it. I'd expect the same behaviour with views and subsets (indeed even moreso), otherwise the server would keep pounding the hard drive to read the .vue and .sub files every time someone opened a view.

Consequently my suspicion is that it has to do with the rollup not being registered in memory for the other session.

Olivier wrote:Any idea how this behaviour could be explained technically ?

The above is my best guess but I really don't think there's a need to explain it; having two sessions of Excel open is, IMHO, a big "thou shalt not" when you're using TM1. (Unless one of them is a local session and the other a Citrix session, and even then doing that with the same login is questionable.) There's always something that can and probably will go wrong when people do that, whether it's slices going into the wrong session or the client just getting generally confused and hanging itself. Users need to be trained accordingly, with a ruler across the knuckles if necessary.

Alan,

I haven't been precise enougth in my description of the issue.
The User was actually logged from 2 different physical machines.

And also to be precise, he created and use the roll up only from one machine.

So situation at the time was :
Machine 1, Log into Tm1 throught excel
Machine 2, Log into Tm1 using same logon , then create a view from this machine using a custom roll up then slice and getting partial Key Errors only below the roll up consolidation.

I know for exemple that if a user want to re use an excel slice containing a custom roll up he needs to store the private view containing the roll up to be able to refresh his DBRWs afterward...
So i was wondering how this is interracting between sessions...

but i take your point, does it really need to be explained...why would you log 20 times from 20 pcs...

thanks for your feedback !

Kind Regards,

Olivier

Olivier wrote: I haven't been precise enougth in my description of the issue.
The User was actually logged from 2 different physical machines.

And also to be precise, he created and use the roll up only from one machine.

So situation at the time was :
Machine 1, Log into Tm1 throught excel
Machine 2, Log into Tm1 using same logon , then create a view from this machine using a custom roll up then slice and getting partial Key Errors only below the roll up consolidation.

I know for exemple that if a user want to re use an excel slice containing a custom roll up he needs to store the private view containing the roll up to be able to refresh his DBRWs afterward...

I discourage people from doing that too; I really just don't trust roll-ups outside of the current session. I've seen them return whacky figures or no figures at all even in later sessions though they're theoretically OK, though whether that might vary from version to version I'm not sure. However if a user needs consolidations on a non-one-off basis I'd rather create a consolidation.

Olivier wrote:So i was wondering how this is interracting between sessions...

It could still be a memory registration issue; possibly the server getting confused between the session that has the roll-up defined and the one which doesn't. However even if that were correct it would be a bear to try to reproduce and prove as a bug, since it's likely to be only a "sometimes-thing".

Olivier wrote:but i take your point, does it really need to be explained...why would you log 20 times from 20 pcs...

You could set the Max Connections to 1 in the Client / Groups dialog I suppose... but I don't like doing that in case a session crashes out and the user can't get back in.

We have 3 authorised connections by user...But we never thougth they would 3 pcs too

Thanks for all your feebacks, appreciated as usual .)

Kind regards,

Olivier