ITA 9.1.3 PUE Dashboard - The page doesn't exist

[tjlaw]

Hi All, 

We have upgraded ITA 9.1.2 to 9.1.3 recently. I found that the PUE Dashboard launched form the webpage show error of "The page doesn't exist" as shown below:

However, when I launch the PUE dashboard from the ITA Client, is shows a proper PUE value. 

Is this a new bug? 

BR, 

TJ

[Jef]

Hi TJ,

I have a test server upgraded from 9.1.2 to 9.1.3, it displays the PUE dashboard without any problem:

and if I click on the 'Open in new window' (in top right), I get the following page https://<ITA server IP>/pue-dashboard/?locale=en (displaying the PUE as well):

So it doesn't seem to be a bug.
I guess (only guessing):
it might be browser related (browser cache or something)
or perhaps something with the PUE configuration, specially if the possible sensor data (from DCE) is not being reported properly.

Kind regards,

Jef

[tjlaw]

Hi Jef, 

When i click "open in new window" it leads to a page with the address "https://<ita_Ip_address>/web/null>. Which displays "The page doesn't exist". It doesn't launch to https://<ITA server IP>/pue-dashboard/?locale=en where I could launch it from the desktop client. 

Additional info, I get the below message from the browser developer tools when loading the PUE dashboard. I also checked that my user login is administrator level. 

/web/api/webclient/v8.1/users/current?include=customers&include=permissions&include=preferences&include=user_groups:1 Failed to load resource: the server responded with a status of 401 (Unauthorized)

BR, 

TJ

[Jef · Accepted solution]

Hi TJ,

I have been running some tests and for the time being it seems I can reproduce it by trying to log in with a user with limited access to the setup, however providing the full permission doesn't help either. It is also reproduceable using a newly created user with full permission.

So, you are right - that seems to be a bug, I will capture this in our backlogs.

Many thanks!

Kind regards,

Jef 

[Jef · Accepted solution]

Hi TJ.  

You've been informed via our direct messages - however sharing the update & workaround  with the forum as well: 
Issue seems to be caused by user locale not be properly set in the database - it will be fixed in a near future release version.
For the time being here is a simple workaround:
in web-client go to your Account > Language change the language to something else such as Deutsch, and then change it back to your own (for example English). 

Kind regards,
Jef