TM1 Forum

Hi all, I am trying to connect TM1 10.2.2 Perspectives on a client (with MS Excel 2010 - 32 bit / Windows 7 - 64 bit) to one of 3 models on our production server. The client can connect to the other 2 models without a problem, but when I double-click on the 3rd model to try to log on, the client just idles for about 15 seconds then stops trying. Even if I have selected the 3rd model in server explorer and then move the mouse over the Server menu option, the client just idles for 15 seconds then does nothing. No such problem on the development server; the client connects as normal to all 3 models.

I'm sure it is just a config setting, but I fear that I have been looking for too long, and now cannot see the forrest for the trees.

Any assistance would be greatly appreciated.
Thanks,
Rob.

Still looking for a response... anyone?

xRobChandler wrote:I'm sure it is just a config setting, but I fear that I have been looking for too long, and now cannot see the forrest for the trees.

Post the tm1s.cfg file... did you check it against the ones that work?

Which security mode(s) are you using?

Are all three TM1 services configured to use different IP ports?

tomok wrote:Are all three TM1 services configured to use different IP ports?

I think Tom is on da money. I've seen exactly the behaviour described by the OP and the reason was that multiple TM1 servers on the same admin host had been assigned the same port number.

Hi all,
thanks for the suggestions. Am using TM1 authentication. Have checked the config file ports on each model and no conflicts there...

What about the UseSSL setting? That used to cause funny connection issues in the past depending on the set-up.

UseSSL = T in all models, so I don't think that is the cause. But thanks anyway.

Do you have something different in your set-up between development and production whereby the admin host to which the model is registered is different from the host box actually running the TM1 instance? This might mean you need different admin host settings in Perspectives to connect to development vs production instances... if you post your tm1s.cfg as I suggested earlier it might be a bit easier to spot something - but people do appreciate you may have sensitive data etc in there. Just saying...

Thanks Robin, yes, I'd rather not post the whole file contents. But, I have reset a value against the 'ipversion' parameter - from dual back to ipv4. Unfortunately, I cannot restart the service until this evening. So will let you know in the morning if the issue is still occurring.

Thank you all, the problem is resolved. It was the ipversion parameter causing the issue. Much obliged.

Rob, just a bit curious why you chose to set the parameter to 'dual'? Is your organisation looking to move to ipv6? I'd imagine most corporates would do a 'big-bang' kind of migration and not try and run ipv4 and ipv6 on their internal networks simultaneously... but I am somewhat out of my depth in that field...

Hi Robin, no, we only use ipv4. We had an external consultant develop the new model and also configured the initial setup; my fault, I should have attended to the setup and config myself... but didn't.