I installed pgAdmin 4 as part of the postgres installer for MACOS. pgAdmin is now telling me there is a newer version.
However, there is no built in upgrade functionality in pgadmin 4.
Can someone help on this matter?
brew upgrade --cask pgadmin4
Works all the time.
You can reinstall a new pgadmin here:
https://www.pgadmin.org/download/pgadmin-4-macos/
I've installed pgadmin once via homebrew, and everytime I've done brew upgrade and there's been an update its installed it.
I go directly to the pgAdmin download page. Then I install it just like any other Mac program (dragging into the Applications folder).
Be sure to close all connections and shut down the server before installing.
Note: For me, this is in a folder within my Applications folder called "PostgreSQL 11" Not sure if this was by design or a mistake on my part.
I have an installer project setup from version, 1.0.0 ,1.0.1 and 1.0.2.Each having different changes I needed for my project.When I install them in order,they upgrade properly and get installed nicely.But I have a need where I need to go back from 1.0.2 to 1.0.1,but the setup project won't let me install it since it already has a newer version installed.And one of the ways I can get around it, is to manually uninstall it and run it.But I don't want the end user to do that and just run whatever setup he wants and it gets install removing previous versions. Can anyone suggest me a workaround for this or how to handle this situation?
Having deleted the Studio 3, which was working, and installing a new one, the first launch produced the message: "Failed to load the JNI Shared Library: 'C:...java.jdk1.8.0_05\bin..\jre\bin\server\jvm.dll'" Upon checking the indicated bin directory, the 'server' subdirectory was missing. I then installed both jre7 and jre8 as standalone jre's. Both hre7 and jre8 have the server subdirectory under bin. If I point JAVA_HOME towards one of the newer installs, I will lose ready access to the JDK. Is there any other way to tell Aptana Studio 3 which jvm to use?
This whole exercise was started in an attempt to get Aptana Studio 3 to use Ruby 2.0.0, rather than ruby 1.9.3 (both of which are installed). How might one do that? Both rubys are in the PATH, with ruby2.0.0 first. Also RUBY_HOME points to ruby2.0.0. Entering ruby -v at the command prompt yields 1.9.3.
In turn, I am doing this because I am getting a crash in 1.9.3 wich says: "You have encountered a bug in the ruby interpreter..."
You can configure which version of Java Aptana will use in AptanaStudio3.ini: simply add
-vm
C:/Program Files (x86)/Java/jdk1.7.0_21/bin/javaw.exe
(before --launcher.XXMaxPermSize) pointing to a 32bit Java version.
Make sure you have the 32-bit version of the JDK installed. This error occurs with the 64-bit version. Try and download the 32bit JDK, install and Aptana should run (at least that worked for me)
The latest Windows installer does not contain the JRE, contrary to what the page at http://www.aptana.com/products/studio3/success.html says:
The Windows installer includes a compatible version of Java.
I downloaded the 3.5 installer, installed to a different directory, and copied the JRE directory from there to the 3.6.x directory. This has resolved the issue for me.
(I suppose the installer could contain a 32-bit JRE, detect my system is a 64-bit system, and not install it, but the size difference between the two installers is enough to be accounted for by a missing JRE.)
I Was getting the same issue while loading aptana.
Fixed it with following steps.
Uninstalled available jdk7.1 (It was 64 bit)
Uninstalled aptana;
Downloaded and installed jdk7.1 32 bit.
The jvm.dll will be in the follwing path: "C:\Program Files (x86)\Java\jdk1.7.0_75\jre\bin\client"
Re installed aptana
Thanks
I have recently tried to install Python 3.4 as an alternative installation on my system in an attempt to familiarise myself before migrating code. My main Python installation is 2.7.6.
I tried the 64 bit installer for Windows, but it came up with an error message
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.
After this the install is rolled back (from the point shown below):
I have eventually found a solution to this posted below and decided to share in case anyone else was having the same issue.
After some looking online I found (here) that the issue was related to conflicting pip installs (I have a version already installed for Python 2.7 and apparently this is not compatible with the version that ships with Python 3.4.
To get around this issue I simply de-selected pip from the install options shown below and the install went ahead smoothly:
Run installer again and select PIP installation.
If the PIP fails to install with the same error, you may want to check environmental variables using a tool like http://eveditor.com/ which enables to check whether they are valid. If you had another version installed before, you most likely have wrong PYTHONHOME and PYTHONPATH variables. Fix them by setting them to relevant paths. e.g. PYTHONHOME=C:\python27 and PYTHONPATH=c:\python27\Lib
You will then be able to run and install PIP.
My issue was that I had a PYTHON_HOME or PYTHON_SOMETHING environment variable set. After removing the environment variable, the installation worked perfectly.
What worked for me, strangely enough, was the "Microsoft Program Install and Uninstall troubleshooter"
The "deselect pip" solution did not work for me.
My Python 3.4.1 install was failing with the same "A program run as part of the setup did not finish as expected" error. I tried both installing it on top of Python 3.4.0 and installing it in a new folder, but got the same error. I tried uninstalling Python 3.4.0 first, but got the error during the uninstall, as well.
I ran that Microsoft utility, which helped me uninstall 3.4.0, and was then able to install 3.4.1 cleanly. The utility has options for both problematic installs and uninstalls, so it may help even if you're doing a new install, not an upgrade.
I'm running 64-bit Windows 7, but was working with 32-bit Python versions.
I had similar issues with Python 3.4x on Windows 8.1. Even after a successful install, the uninstaller would fail in the same way. Ultimately, "Method 1" at the MS forum solved this for me when I ran Microsoft's (Un)installer Fix It.
I also had the problem that pip couldn't be installed like #ChrisPosser.
So I deselected pip and the installation went fine. afterwards I restarted the setup, chose "change python" and installed pip. now everything worked like expected.
If you have any problems with windows installers I recommend activating the verbose log like this:
msiexec /i python-2.7.10-1.609.2.msi /lv install-python.log
From the logs I could see that it was the pip install, which was not working.
Yes, I faced the same issue, and was working on this for the past one hour. Was trying to uninstall the Python 3.4.1 from the control panel -> uinstall program -> add/remove program, but was facing issues.
This trick worked for me:
Manually deleted the 3.4.1 folder, which was present in my C folders after I installed the 3.4.1
Then I followed these steps:
-> Went to Regedit.exe, checked in both HKEY_CURRENT_USER, HKEY_LOCAL SOFTWARE Folder, and deleted the Python folders there.
-> windows 8 -> Downloads -> 3.4.1 msi setup (Glad I never deleted it)
-> Right clicked on the msi setup and choose the repair option
-> The repair would re install the Python 3.4.1
-> After this, I un-installed the Python 3.4.1
-> Then I deleted the 3.4.1 msi setup.
Rebooted the system, and now, there is no instance of Python 3.4.1 in my system.
According to me when environment variables containing name 'Python' are created they somehow becomes related with python. I was unable to open idle (GUI PUTHON) and to uninstall it . Deleting a variable named 'PYTHON PATH' solved my all python related problems.
I had 3.7.4 and wanted to move to 2.7.13.
I uninstalled 3.7.4
Tried to install 2.7.13 but got the same error.
There was a 2.7.10 installer(not msi) also present, uninstalling which gave the same error.
So I downloaded 2.7.10 msi, installed it, and then just installed 2.7.13 from the downloaded msi and it worked fine. This overwriting worked because the major version i.e. 2.7 was same for both.
I don't know if this is helpful but after the hours I spent on this, I wanted to write out what worked for me.
Yup, I have already installed another version of python. I have uninstalled them using Program features. But still the same issue persisted because of the folder which was present in my C: drive. After deleting them manually, the installation got completed without errors
I faced this issue because of 2 conflicting versions of 7zip. Removing them both and installing just one fixed this issue.
I had python3.4 installed, then added 3.5, and deleted 3.4. That was a mistake. In trying to get a library to work, I had to go back to 3.4. I uninstalled 3.5, but couldn't uninstall 3.4 (folder deleted).
I ended up searching the registry in rededt32 for "python". There was a Guid folder with a number of entries that had c:\python34 and one more related to the same folder that I deleted. After this, the install worked correctly.
Windows 10.
Mine was linked to having installed an older version in the past, only for my own user account. I got around it by telling the installer to install Python for all users.
For me none of the suggested fixes worked for me. However checking the option "Install just for me" instead of "Install for all users" (Windows 10) worked for me. So this might be another option to try.
During my newbie phases I was not aware that Max OSX had appache2 installed by default.
I manually installed it and now I have two versions running and it's extremely confusing, because at times I don't know to which version my developments point to. As of now, I have two version in the following locations:
/etc/apache2/ (I believe is the default installation)
/opt/local/apache2 (I believe this is the one I manually installed)
How do I uninstall version 2 (the one I manually installed)?
Thanks!
Being that it's in /opt, the directory MacPorts uses, have you tried port uninstall apache2?