Recently, I upgraded to PostgreSQL 10 and pgAdmin 4 on Windows 10. When I started pgAdmin 4 from the All apps list in the Start menu, pgAdmin did not start as expected and a message was displayed that the PostgreSQL server could not be contacted!
How to fix that? Fortunately, it turned out to be easy. I inspected the AppData\Roaming\pgAdmin folder within my Windows user account home folder and realized that it contained various files and folders. After moving all of them into the Recycle Bin, I was able to restart pgAdmin successfully.
Maybe, data stored and dumped while working with a prior pgAdmin version interfere with version 4. Then, to avoid pgAdmin4 start-up errors has a simple one-step fix (the way it worked for me as described above):
Remove all files and folders from your AppData\Roaming\pgAdmin folder. This folder has the path
C:\Users\YourUserName\AppData\Roaming\pgAdmin
with YourUserName being—well—your user name. If you still want to switch back to an older pgAdmin version previously installed and run on your computer, you should keep the removed files in storage—just in case..
How to fix that? Fortunately, it turned out to be easy. I inspected the AppData\Roaming\pgAdmin folder within my Windows user account home folder and realized that it contained various files and folders. After moving all of them into the Recycle Bin, I was able to restart pgAdmin successfully.
Maybe, data stored and dumped while working with a prior pgAdmin version interfere with version 4. Then, to avoid pgAdmin4 start-up errors has a simple one-step fix (the way it worked for me as described above):
Remove all files and folders from your AppData\Roaming\pgAdmin folder. This folder has the path
C:\Users\YourUserName\AppData\Roaming\pgAdmin
with YourUserName being—well—your user name. If you still want to switch back to an older pgAdmin version previously installed and run on your computer, you should keep the removed files in storage—just in case..
No comments:
Post a Comment