Page 1 of 1

Upgrade from 9.5.2 to 10.2.2 FP7: Architect menu options greyed out

Posted: Mon May 01, 2017 5:10 pm
by skriptmeister
Hi,

having performed an upgrade from TM1 9.5.2 to 10.2.2 FP7, we are encountering a problem with Architect: After successful connection to one of the databases, some of the context men options, particularly the security menu items "users" and "groups", are greyed out and cannot be clicked.

IMHO, this problem is not linked to the well-known tm1p8.lic file issue, because it only appears with one of the databases. A login to one of the other DBs will show the full set of menu options as expected, and we made sure the lic file is available on the client search path.

I appreciate any hint or idea to resolve this issue.

Cheers,
Florian

Re: Upgrade from 9.5.2 to 10.2.2 FP7: Architect menu options greyed out

Posted: Mon May 01, 2017 6:05 pm
by tomok
Perhaps you logged into one of these TM1 servers with an ID that does not have administrator privileges.......?

Re: Upgrade from 9.5.2 to 10.2.2 FP7: Architect menu options greyed out

Posted: Mon May 01, 2017 7:13 pm
by skriptmeister
No, I logged in as admin to all of them (to be precise, by the name of the built-in administrator, "admin").

Re: Upgrade from 9.5.2 to 10.2.2 FP7: Architect menu options greyed out

Posted: Mon May 01, 2017 8:16 pm
by tomok
You upgraded both server AND client (Perspectives and Architect) to version 10.2.2?

Re: Upgrade from 9.5.2 to 10.2.2 FP7: Architect menu options greyed out

Posted: Mon May 01, 2017 10:22 pm
by skriptmeister
Yes, we did. And again: the issue appears only with one of the databases, though we are accessing all of them using the very same Architect instance on the same client machine, same admin server, same DB server. I supposed there was a problem with the migration of the DB from 9.5.2 to 10.2.2 FP7, but another DB that has also been migrated is just fine.

Re: Upgrade from 9.5.2 to 10.2.2 FP7: Architect menu options greyed out

Posted: Tue May 02, 2017 9:41 am
by skriptmeister
Last night, during a scheduled server restart, the problem went away mysteriously, it's all up and running now. Just the old "have-you-tried-turning-it-off-and-on-again" story. Sorry for having bothered you and thank you for your support.

Cheers, Florian