Page 1 of 1

Local Installation Crashes

Posted: Wed Jul 31, 2019 8:42 pm
by Thurston Howell III
Hi All,

My company has offices in a few cities across America. Myself and my team have no issue using our local installation wherever we are, but the people in our other office always experience a crash whenever slicing or snapshotting from a cube view on their local installations. They can, however, use a Citrix image off the server, which is located in their city.

Has anyone else experienced anything like this? What might be different about a local installation in a different geographical location?

Re: Local Installation Crashes

Posted: Thu Aug 01, 2019 7:31 am
by Steve Rowe
Hi, Can you be explicit about the "crash" behaviour? Do you mean user gets bored waiting and kills Excel or an actual crash?

Re: Local Installation Crashes

Posted: Thu Aug 01, 2019 11:40 am
by tomok
So you have people in remote cities (meaning not the same place where the TM1 server is housed) and they are using Perspectives to access TM1? I'm surprised you were even able to make this work. This is a known issue with TM1, that Architect/Perspectives clients need to be on the same network as as the TM1 server in order to perform acceptably. This issue is resolved under PAX but if you still need to use Perspectives then the answer is to use Citrix or VDI or some other tool like that, where that server is located right next to the TM1 server.

Re: Local Installation Crashes

Posted: Thu Aug 01, 2019 6:08 pm
by gtonkin
Have had mixed luck with Perspectives over a network-some perform better than others.
In my experience, corporate WANs using MPLS networks (my packet lost at the switch) seem to perform the worst whereas clients who use 3G/4G and VPN to the LAN perform better.

This apparently is down to MTU settings. With TM1 being chatty (small bits of data but frequent) networks with high MTU settings like typical network may have size like 1492 or 1500 i.e. you need to fill a bucket with 1500 bytes before it is sent. This can create lag and choppy reposnses with packets dropped. This is how it was explained to me at any rate - don't hold me to this as gospel.

In any event, you could try some client side debugging to see if your crashes/disconnects are due to networking or something else.
Have a look at this article on Client Logging. Be aware that it can get quite verbose and create some big files to trawl through depending on your configuration.