Can not see models list in TM1 Architect

[andreykadysh]

Hi everyone!

After updating TM1 version to 2.0.9.19 cannot see models list in TM1 Architect.
Update was performed without deleting previous version. I've stopped services, backup config files and run installation in the same folder.

Models are running and list of models is visible and accesible from TM1 Architect on another Server, in Cubewise Arc, in PAW.
Admin server ports are OK.

Any help would be appreciated!

PA version: 2.0.9.19
OS: Windows Server 2019 Standard

[ascheevel]

Did you populate anything for Admin Host in File->Options within Architect?

[burnstripe]

Is the install set up to use the IBM certs or self certified certs? If it uses self certified the issue it may be the certificates are missing... Here's a link on it...

https://www.ibm.com/support/pages/how-c ... 20-and-201

I'm wondering if the tm1api.config may have been removed by the update

[andreykadysh]

Did you populate anything for Admin Host in File->Options within Architect?

No, all fields are empty. So, I expect to see a list of models from the localhost.

[andreykadysh]

Is the install set up to use the IBM certs or self certified certs? If it uses self certified the issue it may be the certificates are missing... Here's a link on it...

https://www.ibm.com/support/pages/how-c ... 20-and-201

I'm wondering if the tm1api.config may have been removed by the update

Yes, we use custom certs. But before updating architect was working without extra tweaking.
I compared to other servers, and there is no tm1api.config files there...

I've tried to follow this technote.
My tm1api.config file now looks like this. Thes same paths as in adminserver config:

Code: Select all

[tm1api]
keystorefile=C:\ibm\cognos\tm1_64\bin64\ssl\custom.kdb
keystashfile=C:\ibm\cognos\tm1_64\bin64\ssl\custom.sth

But architect still doesn't show models list...

[burnstripe]

There could be several reasons for the instances not showing, some of which are..

- Firewall (unlikely since other clients could connect)
- Incompatible client (architect version differs pa server version possible but do not suspect as it sounds like the other architect versions hadn't been updated)
- Trust issue with certificates (most likely)
- Account that did the install didn't have sufficient privileges... Have you tried to run architect using "run as administrator", can see this by right clicking on the architect icon/app, do the instances display then

Fiddler could be helpful for diagnosing...
https://www.telerik.com/download/fiddler

I would also look in event viewer for any warnings/alerts

Also my be worth trying to add an admin host with the ip address of the server as a trial

[andreykadysh]

Thank you all for your answers and suggestions!
I'll try to figure it out and give here feedback. Most likely this is a cert issue.

[andreykadysh]

Finally, it started work properly after I added tm1api.config to C:\ibm\cognos\tm1_64\bin
Before it was only in C:\ibm\cognos\tm1_64\bin64 folder.
It looks quite strange because this is x64 server and installation pack was 64...

And if I open windows Start menu => IBM Cognos TM1 - 64 => Architect "open file location" button. It leads me to C:\ibm\cognos\tm1_64\bin

[hshah]

Hello everyone.
In my company we are using 5-6 Tm1 server instances and I have task to create new one.
For that steps I followed.
1. Copied main folder with data and logs as a subfolders
2. pasted it in place where all the other server instances folders were there
3. created new resource instance in Tm1 configuration and also changed configuration file with required CAM URI and Server URI
4. Started server at that time - I faced error "Server is starting or stopping" - I ignored it and it looks green (started)
BUT I can not see my new created server in the TM1 architect.
All the other previous ones are there.

Also if I try to stop this new server it again turns into green
What could be the reason for it? why I can not see it in architect?

Any Help will be really appreciated.

Thank you very much!

[ascheevel]

Post your question in a new thread instead of attaching to this one.