Anyone else come across this? Everything else seems to be working OK. This is accessing GO_New_Stores, so should be fairly standard.
Error accessing set editor from PAx
-
- Community Contributor
- Posts: 306
- Joined: Mon May 12, 2008 8:11 am
- OLAP Product: TM1
- Version: TM1 11 and up
- Excel Version: Too many to count
- Steve Rowe
- Site Admin
- Posts: 2423
- Joined: Wed May 14, 2008 4:25 pm
- OLAP Product: TM1
- Version: TM1 v6,v7,v8,v9,v10,v11+PAW
- Excel Version: Nearly all of them
Re: Error accessing set editor from PAx
The pre-requisite that is often missed is that IE11 is required on pax machines, this looks like that error.
Technical Director
www.infocat.co.uk
www.infocat.co.uk
-
- Community Contributor
- Posts: 306
- Joined: Mon May 12, 2008 8:11 am
- OLAP Product: TM1
- Version: TM1 11 and up
- Excel Version: Too many to count
Re: Error accessing set editor from PAx
It doesn't look like that's it - IE11 is installed, and I've even made it default now. I still get the same result.
Thanks
Thanks
Paul
- Steve Rowe
- Site Admin
- Posts: 2423
- Joined: Wed May 14, 2008 4:25 pm
- OLAP Product: TM1
- Version: TM1 v6,v7,v8,v9,v10,v11+PAW
- Excel Version: Nearly all of them
Re: Error accessing set editor from PAx
Did you point PAx at PAW, rather than the TM1 Service? That is the other area that generates an error when getting into the common objects. I don't think that is it since I think that is a simple 404 error.
Technical Director
www.infocat.co.uk
www.infocat.co.uk
-
- Community Contributor
- Posts: 306
- Joined: Mon May 12, 2008 8:11 am
- OLAP Product: TM1
- Version: TM1 11 and up
- Excel Version: Too many to count
Re: Error accessing set editor from PAx
I did (I'm pretty sure). I get the PAW-like logon screen, which works and lets me in.
Paul
-
- Community Contributor
- Posts: 306
- Joined: Mon May 12, 2008 8:11 am
- OLAP Product: TM1
- Version: TM1 11 and up
- Excel Version: Too many to count
Re: Error accessing set editor from PAx
Well, I've fixed it, but not cured it. I had the http port set to 8080 on the PAW start.bat rather than 80 as there was something else on 80. I've got rid of the something else and rebuilt PAW using port 80 and it now works. Thanks for the help though, Steve.
Paul