Unable to connect to TM1 server after VM migration

[Dev1975]

Hello everyone,

A Customer had some migration work done over this Easter weekend and had his Cognos VM's moved over to a new VMWare vCenter server. Since the move, however, any attempt to connect to the TM1 server through Architect or TM1Web results in a "Cannot connect to server" message being returned.

I've re-created the cryptographic keys and restarted the services but to no avail. I've asked them to confirm if the new vCenter server is in the same domain and doesn't have any firewalls/proxy servers sitting in front of it that would cause this. Is there anything else to watch out for in this situation? I'm waiting for the TM1 server config files to come through but if anyone knows of any "gotcha"'s that I should look out for, that would be appreciated.

Cheers,
Dev

[MFGF]

Hello everyone,

A Customer had some migration work done over this Easter weekend and had his Cognos VM's moved over to a new VMWare vCenter server. Since the move, however, any attempt to connect to the TM1 server through Architect or TM1Web results in a "Cannot connect to server" message being returned.

I've re-created the cryptographic keys and restarted the services but to no avail. I've asked them to confirm if the new vCenter server is in the same domain and doesn't have any firewalls/proxy servers sitting in front of it that would cause this. Is there anything else to watch out for in this situation? I'm waiting for the TM1 server config files to come through but if anyone knows of any "gotcha"'s that I should look out for, that would be appreciated.

Cheers,
Dev

Has the hostname changed? Is it possible the config was set up using IP address instead of hostname? These are the two things that spring to mind, Dev...

Cheers!

MF.

[Dev1975]

Hi MFGF,

I thought the same after I got the TM1S.cfg file from the Customer. The hostname is still the same, as are the IP Addresses specified. In the previous VM environment they couldn't get TM1 working until they added the IP Address parameters, which made it work. They've simply migrated over to vCenter 6 from vCenter 5 and now it's not working.

The TM1 Web server can ping the Admin server successfully on all IP addresses except one, which was assigned to a backup network card. Removing this IP and the backup card did not solve the issue. They've also tried moving it back but it doesn't work.

So the only change is that the VM's have been moved from one vCenter to another and it's been enough of a change to make everything break. The VM's were shutdown and removed from the inventory of vCenter 5.1 and added back into the inventory of the vCenter 6.0 server. The datastore stayed the same and the same VM files were used. I assume this is standard procedure for migrating VM's from one server to another...?

Ugh!