Changing wireless internet connection stops TM1 service

[Wim Gielis]

Hello all

Just a question about what pisses me off very often...

I have my own TM1 model locally on my laptop. It is a rather small model with some personal finance stuff and some generic TM1 stuff (zero out code, MDX, ...)
The model (ca. 70 MB RAM) runs under a service. I am Administrator on the laptop.

Now, everytime I change the wireless internet connection, the model is gone and I need to restart the service!
Let's say, a local wireless internet connection at home, after a different connection at the customers side or in our offices at work, always the same behavior.
Is this something you encountered too? What is the link? If I just put the laptop in sleep mode or hibernation and wake up an hour later with other internet connection: dang!
The service needs to be stopped (not only starting again, also first stopping the service)

Thanks for writing down your comments and tips.

Have an interesting week!

Wim

[David Usherwood]

I've suffered from this for years. I believe that the service itself keeps running, but the Admin service gets its unmentionables in a twist when the IP address changes (which happens when you change wifi connection). Then both the server and the admin server need bouncing.
I did try setting up a 'loopback' network adapter but I can't recall whether that provided a consistently reliable fix.
9.5 persistent feeders are rather a godsend here.

[Andy Key]

Something has got worse more recently. I'm not sure whether to blame IBM or Microsoft though.

I used to be able to hibernate my machine with a TM1 server running, then as long as I resumed the machine with the same network connections the TM1 server remained contactable. This was useful for large demos where you could take your machine off of the office network, restart the TM1 server, then hibernate it, go to the meeting, resume and hey presto, one TM1 server ready to demo.

Whether it was the change from 9.5.1 to 9.5.2 or from WinXP to Win2007 I don't know, they both happened on my laptop at the same time, but now hibernating breaks the TM1 server as well.

[Alan Kirk]

Something has got worse more recently. I'm not sure whether to blame IBM or Microsoft though.

I used to be able to hibernate my machine with a TM1 server running, then as long as I resumed the machine with the same network connections the TM1 server remained contactable. This was useful for large demos where you could take your machine off of the office network, restart the TM1 server, then hibernate it, go to the meeting, resume and hey presto, one TM1 server ready to demo.

Whether it was the change from 9.5.1 to 9.5.2 or from WinXP to Win2007 I don't know, they both happened on my laptop at the same time, but now hibernating breaks the TM1 server as well.

I've been finding the same thing since Vista on that P.O.S. Dell that I had before my current one. I don't recall it being an issue on my earlier XP notebook, though hibernation is something that changed quite dramatically between the two. (No more scrolling black and white bar.) Unfortunately I can't be sure of the TM1 versions involved either. However it's not consistent. Sometimes I'll have to kick the admin host over, most times, admittedly, it'll just be there and running.

[Wim Gielis]

Thank you for your comments.

[jim wood]

Have you tried uninstalling and and re-installing with your laptop disconnected from any network? I don't know if this will work but it's got to be worth a try?

[Alan Kirk]

Have you tried uninstalling and and re-installing with your laptop disconnected from any network? I don't know if this will work but it's got to be worth a try?

I completely uninstall / reinstall on a regular basis for various reasons, since the notebook is mostly a testbed. And it's almost always while it's off line. Makes no difference; you'll still get this occasionally because it's the nature of the beast. I doubt that there will be much support forthcoming from IBM since, understandably, servers weren't designed to hibernate or to hot-switch networks.

[jim wood]

Alan do you mean in terms of going in to standby or the WIFI issue? The reason I suggested it is that if you logon to your machine without a network it uses a local profile instead of the network profile for your user and therefore the installation may inherit the offline properties and also the admin host may not try to resolve the DNS / IP address of the host as this didn't exist either as part of the original install. I think the stand by issue is similar but not the same. I'm probably wrong mind but thought I would stick my neck out for a change. (Firmly with tin hat in place!!)

[Alan Kirk]

Alan do you mean in terms of going in to standby or the WIFI issue?

Both. My notebook also jumps between three different networks (both wired and wireless) as well as between IP addresses within any given network as well as hibernating regularly. Periodically I'll do either one and... bang, just like Wim described. The service is still running, it's still using memory, but even after kicking over Excel I just can't see the thing until I bounce the servers and the Admin Server. Doesn't happen all the time, doesn't seem to happen to me as often as it does to Wim, but I've noticed that the bigger the database I'm running, the more likely it is to happen.

[stephen waters]

I run my TM1 servers as applications (since I am not sophisticated enough to run them as a service) but I get similar results. If I change networks, and presumably IP address, I have to bounce the server before i can connect again. This normally happens if I disconnect from the office and connect to wifi at home, though will also happen if I eg use my wifi dongle.

I don't think this is a recent problem, I have noticed it for years.

[tomok]

This has been my experience as well. What I have been able to determine is that the TM1 Server requires an accessible Admin Server in order to stay up. If the Admin Server becomes unreachable, for any reason, the TM1 Server will freeze. If the Admin Server is brought back on line within a few seconds then the two can reconnect but if the two can't communicate for more than 30 seconds or so, you are toast.

[Andy Key]

I've been finding the same thing since Vista ...

Happy to say I never had the 'pleasure' if Vista!

Think I installed it on a VM when it came out, decided it wasn't really a business OS and stuck with XP until late last year.

[IanB]

Here's my hot tip for running a local edition of tm1 without suffering when network configuration changes
1) Disconnect from wired and switch off wireless
This ensures that your machine's IP address is now the loopback 127.0.0.1
2) Stop any TM1 services - if running in foreground, close the admin server (look in the notification area) and the database server

3) Start up your services or foreground process
A foreground server will automatically launch an admin server in the taskbar notification area if an admin service is not found
These processes are now locked in to communicating on address 127.0.0.1

You now have a portable solution - TM1 will keep running and clients stay connected no matter what you do to the network configuration - wired, wireless, vpn, even hibernate the machine - it just goes on working
Thanks to sysinternals tcpview for making everything so very clear!

IanB

[Kyro]

I use a Macbook Pro with a Windows 7 VM. If I set the network connection to NAT on the Virtual Machine Settings (Which just means "use whatever internet the Physical Machine has") the connection is always present even if the physical machine has no internet connection at all. This means local TM1 Servers will never break connection with the adminhost service.

[lotsaram]

I use a Macbook Pro with a Windows 7 VM. If I set the network connection to NAT on the Virtual Machine Settings (Which just means "use whatever internet the Physical Machine has") the connection is always present even if the physical machine has no internet connection at all. This means local TM1 Servers will never break connection with the adminhost service.

I used to use more or less the same setup but with VM Win 2003 x64 Server running on a Win7 x64 laptop. Suspend the VM, hibernate the laptop and start again with everything exactly as it was. IMO best set up for demos as you can have everything preprepared (nothing worse than being in a demo "oh let's just wait 10 minutes while the server loads"). The only thing to be mindful of is to plan enough time for the VM to load and suspend.

[jim wood]

Here's my hot tip for running a local edition of tm1 without suffering when network configuration changes
1) Disconnect from wired and switch off wireless
This ensures that your machine's IP address is now the loopback 127.0.0.1
2) Stop any TM1 services - if running in foreground, close the admin server (look in the notification area) and the database server

3) Start up your services or foreground process
A foreground server will automatically launch an admin server in the taskbar notification area if an admin service is not found
These processes are now locked in to communicating on address 127.0.0.1

You now have a portable solution - TM1 will keep running and clients stay connected no matter what you do to the network configuration - wired, wireless, vpn, even hibernate the machine - it just goes on working
Thanks to sysinternals tcpview for making everything so very clear!

IanB

That's kind of what I was angling towards with the instal above.