Hello,
I have been successfully building out a TM1 model with contributor. When I go to log into TM1 Contributor I receive the msg below;
"Could not logon to any available servers with the provided credentials."
I think problem relates to changing server name in TM1s.cfg file. With this change I can log into TM1 without concern. What else do I need to update so Contributor acknowledges and works.
Thanks
Can No Longer Log Into Contributor
- Martin Ryan
- Site Admin
- Posts: 1989
- Joined: Sat May 10, 2008 9:08 am
- OLAP Product: TM1
- Version: 10.1
- Excel Version: 2010
- Location: Wellington, New Zealand
- Contact:
Re: Can No Longer Log Into Contributor
If you've changed your server name you'll have to redeploy (and probably rebuild) your contributor application.
Martin
Martin
Please do not send technical questions via private message or email. Post them in the forum where you'll probably get a faster reply, and everyone can benefit from the answers.
Jodi Ryan Family Lawyer
Jodi Ryan Family Lawyer
-
- MVP
- Posts: 352
- Joined: Wed May 14, 2008 1:37 pm
- OLAP Product: TM1
- Version: 2.5 to PA
- Excel Version: Lots
- Location: Sydney
- Contact:
Re: Can No Longer Log Into Contributor
If your users haven't started using the system yet, I would suggest following Martin's advice. It would be advisable to run the process called something like }tp_admin_delete_all to get rid of the existing Application specific Contributor objects as you are just about to replace them with a different Application. I haven't got a machine with Contributor on with me so the process might have a slightly different name.
If they are already using it, and you want to retain the current status of the submissions, you can hack the pmpsvc_config.xml file, along with the {<Application_ID>}.model and {<Application_ID>}.security files, where <Application_ID> is the value in the }tp_Applications dimension - assuming you only have one application on this TM1 Server. These files will be in different places depending on whether you are using the default TomCat instance or whether you have deployed using the same TomCat instance that comes with BI.
Or the simplest option is to rename your TM1 server back to what it was originally called...
If they are already using it, and you want to retain the current status of the submissions, you can hack the pmpsvc_config.xml file, along with the {<Application_ID>}.model and {<Application_ID>}.security files, where <Application_ID> is the value in the }tp_Applications dimension - assuming you only have one application on this TM1 Server. These files will be in different places depending on whether you are using the default TomCat instance or whether you have deployed using the same TomCat instance that comes with BI.
Or the simplest option is to rename your TM1 server back to what it was originally called...
Andy Key