Good Afternoon,
Recently in my company the Planning Analytics server was migrated to a new location, after the migration i went in to test planning and wasn't able to connect to anything. After working with the IT team i was able to log in to architect but still can access PAW. I tried in different browser and i get the same result "This page isn't working". I've checked the docker and is working, i ran the commands and not errors but still cannot connect to PAW. I'm almost at the point of giving up. Can anyone help me, please.
Thanks
Cannot connect to PAW
-
hankler
- Posts: 4
- Joined: Fri Sep 13, 2019 5:44 pm
- OLAP Product: Planning Analytics
- Version: 2.0
- Excel Version: 365
Cannot connect to PAW
- Attachments
-
- 2020-05-29_15-49-02.jpg (165.82 KiB) Viewed 2545 times
-
Ajay
- Regular Participant
- Posts: 183
- Joined: Wed May 14, 2008 8:27 am
- OLAP Product: TM1
- Version: 10.2.0, PA 2.0.9
- Excel Version: 2016
- Location: London
Re: Cannot connect to PAW
Have you checked all your settings in the Config\paw.ps1 ?
From memory I seem to remember a setting for PA Workspace authentication needing the TM1LoginServerURL
From memory I seem to remember a setting for PA Workspace authentication needing the TM1LoginServerURL
-
hankler
- Posts: 4
- Joined: Fri Sep 13, 2019 5:44 pm
- OLAP Product: Planning Analytics
- Version: 2.0
- Excel Version: 365
Re: Cannot connect to PAW
Hello Ajay,
Pardon my ignorance but how do you check those settings?
Regards
Pardon my ignorance but how do you check those settings?
Regards
-
declanr
- MVP
- Posts: 1828
- Joined: Mon Dec 05, 2011 11:51 am
- OLAP Product: Cognos TM1
- Version: PA2.0 and most of the old ones
- Excel Version: All of em
- Location: Manchester, United Kingdom
- Contact:
Re: Cannot connect to PAW
Can you connect from the same machine that PAW is running on?
Or try and do an ipconfig on the PAW server and then see if you can connect with the IP address rather than the server name.
In power shell on the paw server run ./scripts/admintool.ps1 in the admin tool window that opens up; go to Status; press refresh and check that everything is in a “running” state - “initialization” should say complete instead of running.
It sounds like your admin server has been moved (since architect needed to be repointed also) and they possibly have not set the new URIs in workspace; which can be done in the admintool or through paw.ps1 script as Ajay mentioned (the script is found in the install directory for PAW and you just right-click and edit) - if you make changes via the admintool it will update the ps1 file for you automatically. And the admintool lets you run a validation to make sure it connects ok.
Or try and do an ipconfig on the PAW server and then see if you can connect with the IP address rather than the server name.
In power shell on the paw server run ./scripts/admintool.ps1 in the admin tool window that opens up; go to Status; press refresh and check that everything is in a “running” state - “initialization” should say complete instead of running.
It sounds like your admin server has been moved (since architect needed to be repointed also) and they possibly have not set the new URIs in workspace; which can be done in the admintool or through paw.ps1 script as Ajay mentioned (the script is found in the install directory for PAW and you just right-click and edit) - if you make changes via the admintool it will update the ps1 file for you automatically. And the admintool lets you run a validation to make sure it connects ok.
Declan Rodger