App Engine Studio is not working in PDIs Yokohama and Zurich

[Joatan Fontoura]

Here are the details of the issue:

- In PDIs running Yokohama Patch 4, Patch 5 and Patch 6, as well as in Zurich release, it is not possible to open App Engine Studio.
- The following error message is displayed: “You need a valid App Engine Studio license to continue working.”
- This issue does not occur in PDIs running Xanadu, Washington DC, or in Yokohama up to Patch 3. I have a Yokohama PDI in Patch 3 and AES is working fine! So, the issue started in Patch 4. 
- I have requested and tested several PDIs across these versions, and the behavior is consistent.

I have also checked  and there are multiple threads reporting the same problem here in ServiceNow Community. Some responses suggest going to the Developer Site, selecting “Change User Role”, switching the role to App Engine Studio Creator, and then back to Admin. Unfortunately, this workaround has never solved the problem in any of my tests.

I believe that ServiceNow needs to do something about this issue. This is not an isolated case! We don't have nothing to do!

[Joatan Fontoura]

Hi @Dr Atul G- LNG!

Thank you!

I've tried it but after the upgrade, AES starts to show the license issue. 😥

[Dr Atul G- LNG]

Oops… then I think there’s no other way, mate.
Generally, changing the role should work — give it a try, it might do the trick.

[Nikhil Bajaj9]

Hi @Joatan Fontoura ,

Yes there is no fix so you may raise it with Servicenow as a Bug (As there is no support provided for PDI). Whom to reaach for which purpose info can be found here:- https://learning.servicenow.com/lxp/en/get-started-with-servicenow-university-resources?id=kb_articl...

[Joatan Fontoura]

Hi @Nikhil Bajaj9!

Thank you!

Although I didn't find anything helpful in KB0010311. They talk about a feedback button on Developer Site but I didn't find it.

[Nikhil Bajaj9]

Hi @Joatan Fontoura ,

https://learning.servicenow.com/lxp/en/get-started-with-servicenow-university-resources?id=kb_articl...

this is the link where all contact infoirmation is mentioend- please check again. Although no fix yet for this issue but still if you want, check with Servicenow.