Unable to access PDI

suganyar1
Giga Contributor

I am unable to access the PDI instance, it shows attached error. Please guide me further. 

 

 

 

1 ACCEPTED SOLUTION

GlideFather
Tera Patron

Hi @suganyar1 

 

GlideFather_0-1755500245929.png

 

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */


View solution in original post

9 REPLIES 9

Nikhil Bajaj9
Tera Sage

Hi @suganyar1 ,

 

Navigate to developer.servicenow.com and login. Click on arrow next to your name on top right. You will get few options - Click on Change role and change your role to Admin and check again.

 

https://www.servicenow.com/community/eam-forum/when-i-tried-to-log-into-my-developer-instance-it-say...

https://www.servicenow.com/community/sysadmin-forum/unable-to-start-app-engine-studio/m-p/3346736

 

if my answer helped you, please mark it- solution accepted. 

 

Regards,

Nikhil Bajaj

Please appreciate my efforts, help and support extended to you by clicking on – “Accept as Solution”; button under my answer. It will motivate me to help others as well.
Regards,
Nikhil Bajaj

Viraj Hudlikar
Giga Sage

Hello @suganyar1 

Do check my response over this thread:
Re: Instance Issue - ServiceNow Community

If my response has helped you hit helpful button and if your concern is solved do mark my response as correct.

 

Thanks & Regards
Viraj Hudlikar.

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @suganyar1 

 

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.

 

 

 

 

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

GlideFather
Tera Patron

Hi @suganyar1 

 

GlideFather_0-1755500245929.png

 

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */