after upgrading from 6.1.1 to 6.1.3 we had major issues and decided to reinstall the complete Pulse-Environment.
Than all worked okay until we deleted one TM1-Instance from the configuration. This instance didn’t disappear in the list of instances in Pulse until I reload the TM1-Server in the Environment-Tab o the Administration in Pulse.
But since than most of the running instances are shown as loading or they are not connected. User credentials are okay, Ports are all open and REST is available.
I would give it a try deleting the whole environment and creating it again.
Is this installation on the same server as the instances? If not, I would check the connection to and from the monitor, maybe you can use telnet for that aim.
Regards,
Gerardo.
thx for the suggestion. I tried this with no success. And also I just configured another server with nearly the same amount of instances (~20) and there I have the same issue without reload etc.
Do you have the backups from the old pulse version, probably located still on the migration folder…? If so, you can try this.
Stop Pulse services
Housekeep or rename the folder (Do Not Delete, just in case) D:\Program Files\Pulse for TM1\vcs\git\SERVERNAME\InstanceName
Copy the content of D:\Program Files\Pulse for TM1\migrate\SERVERNAME\vcs\git\InstanceName (or from your backup) into D:\Program Files\Pulse for TM1\vcs\git\SERVERNAME\InstanceName
I have no backup but made a new setup. The Server I setup new after the first Issue is now fine.
But the server the issue started with has still the issue. I now realised that only Instances with CAM-Authentication are not connection. Instances with Native Authentication are connecting.
Saving the Instance-Settings are working. So User-Credentials are okay.
