Unable to start app engine studio

[PrasadGJoshi]

Dear All,

Unable to open the App engine studio from PDI and facing below error.

"You need a valid App Engine Studio license to continue working."

Can someone please help?

[KrushnakumaT · Accepted solution]

Hi @PrasadGJoshi ,
Kindly check below solutions from community.
https://www.servicenow.com/community/product-launch-forum/you-need-a-valid-app-engine-studio-license...
https://www.servicenow.com/community/app-engine-forum/app-engine-engine-issue-you-need-a-valid-app-e...
https://www.servicenow.com/community/app-engine-forum/unable-to-access-app-engine-studio-license-req...

If this response helped, please mark it as the correct answer so it can help others as well.
Thank you!!

[Dr Atul G- LNG · Accepted solution]

Hi @PrasadGJoshi 

No need to worry — this is a known issue with PDIs these days. Please follow the steps below:

1. Log in to developer.servicenow.com.

2. Go to your Profile.

3. Select Change User Role.

4. Change the role from AES to Admin.

5. Save your changes.

6. Log out, then log back in to your PDI instance.

If the issue still persists, you can release the instance and provision a new one.

This is a fairly common issue with PDIs recently. Also, please note that since there’s no official support for PDIs, it might take a few attempts — but keep trying.

Workaround:

If it's still not working, try this workaround:

• Assign the admin role

• Log out and log back in

• Then assign the AES role

• After that, reassign the admin role

This sequence has worked in some cases.

[mayankkumar · Accepted solution]

Hi @PrasadGJoshi,
Try the following steps-:

1. Go to the homepage of your ServiceNow Developer Instance.

2. Click on your profile icon (top-right corner).

3. Select "Change User Role."

4. Choose the "admin" role from the list and save.

If your still not resolves try getting a new PDI with a lower version
----------------------------------------------------------------------------------------------------------------------------------------
Please mark my response as helpful and accept as solution
Thanks & Regards
Mayank

[SD_Chandan · Accepted solution]

Hi @PrasadGJoshi ,

Just change user role will work for your instance 

[KrushnakumaT · Accepted solution]

Hi @PrasadGJoshi ,
Kindly check below solutions from community.
https://www.servicenow.com/community/product-launch-forum/you-need-a-valid-app-engine-studio-license...
https://www.servicenow.com/community/app-engine-forum/app-engine-engine-issue-you-need-a-valid-app-e...
https://www.servicenow.com/community/app-engine-forum/unable-to-access-app-engine-studio-license-req...

If this response helped, please mark it as the correct answer so it can help others as well.
Thank you!!

[Dr Atul G- LNG · Accepted solution]

Hi @PrasadGJoshi 

No need to worry — this is a known issue with PDIs these days. Please follow the steps below:

1. Log in to developer.servicenow.com.

2. Go to your Profile.

3. Select Change User Role.

4. Change the role from AES to Admin.

5. Save your changes.

6. Log out, then log back in to your PDI instance.

If the issue still persists, you can release the instance and provision a new one.

This is a fairly common issue with PDIs recently. Also, please note that since there’s no official support for PDIs, it might take a few attempts — but keep trying.

Workaround:

If it's still not working, try this workaround:

• Assign the admin role

• Log out and log back in

• Then assign the AES role

• After that, reassign the admin role

This sequence has worked in some cases.

[mayankkumar · Accepted solution]

Hi @PrasadGJoshi,
Try the following steps-:

1. Go to the homepage of your ServiceNow Developer Instance.

2. Click on your profile icon (top-right corner).

3. Select "Change User Role."

4. Choose the "admin" role from the list and save.

If your still not resolves try getting a new PDI with a lower version
----------------------------------------------------------------------------------------------------------------------------------------
Please mark my response as helpful and accept as solution
Thanks & Regards
Mayank

[SD_Chandan · Accepted solution]

Hi @PrasadGJoshi ,

Just change user role will work for your instance