We have a package which was recently deployed in SCCM. This package requires dot net 4.8 as a pre requisite and installs dot net 4.8 before installing the application. It is expected for the machine to restart after installing dot net 4.8 . But, in case of this package, even after restarting once post dot net 4.8 installation, it restarts the machine once again after starting the application install and this time without even a warning or 1.5 hours of countdown. Even after restarting the machine twice, the application is not successfully installed.
When clicked on more information on "Failed" status in SCCM, the error code is 0x40010004(1073807364). Please see below image for reference.
So, I wanted to know if this is an issue with SCCM or if this is an issue with the application msi files and .cmd script?
I installed pgAdmin 4 as part of the postgres installer for Windows. pgAdmin is now telling me there is a newer version (4.8, > 4.5 which I have). However, there is no built in upgrade functionality that I can see, and when I went to download and run the pgAdmin 4 installer to upgrade, it installed itself in the wrong place, leading to problems.
At first I tried installing it to the default location (C:\Program Files (x86)\pgAdmin 4\v4), which was incorrect, because the previous installation (from the postgres installer) went to a different location (C:\Program Files\PostgreSQL\11\pgAdmin 4).
The second time, I pointed it to my existing install of postgres (C:\Program Files\PostgreSQL\11\pgAdmin 4), but it installed itself to a subdirectory there instead (C:\Program Files\PostgreSQL\11\pgAdmin 4\v4), rather than upgrading the existing installation, once again yielding to duplicated installations and problems arising from that. I assume if I go download the postgres installer, it will just reinstall version 4.5 of pgAdmin, though I have not tested this.
What is the correct method for upgrading a pgAdmin instance originally installed by the postgres Windows installer?
I think the best option is to go to Program and files -> Select PostgreSQL and "Uninstall".
Uninstaller will ask you if you want to uninstall the whole application or only individual components. Select individual components and then select pgAdmin.
This will uninstall pgAdmin from PostgreSQL directory.
From now, install the latest version pgAdmin only from official website which will install it into: C:\Program Files (x86)\pgAdmin 4\v4
If you Download the installer from here https://www.postgresql.org/ftp/pgadmin/pgadmin4/v4.8/windows/
It should automatically install the 4.8 version in (C:\Program Files (x86)\pgAdmin 4\v4)
overwriting any existing 4.x version but keeping your server connections and setting.
In your case, the previous install was in a different place, therefore, you ended up having 2 versions.
What I suggest to you is go to control panel and uninstall from there all the versions you have. After that go to the above link, download and install the v4.8 in the default location. Every time there is a new version available just install it and let the installer install it on the default location.
Please note that your pgadmin server connections can be found in %appdata%\pgAdmin.
Note that I have personally just upgraded from v4.5 to v4.8 using this method (installing it in the default location) and it worked like a charm.
Not sure the best approach here.
If you update directly pgadmin from: https://www.postgresql.org/ftp/pgadmin/pgadmin4/v4.10/windows/ the installation goes into
"C:\Program Files (x86)\pgAdmin 4\v4\runtime\pgAdmin4.exe"
Wheras the installation of the whole EnterpriseDB Installer from:
https://www.enterprisedb.com/downloads/postgres-postgresql-downloads is installed here:
"C:\Program Files\PostgreSQL\11\pgAdmin 4\bin\pgAdmin4.exe"
This looks like a wholly undesirable conflict? And leads to the problem identified by #Anomaly ?
To anyone finding this post (like me), before uninstalling your current pgAdmin 4, be aware that there may be limits on compatible versions based on your version of PostgreSQL. Following the instructions by Claudio Corchez, I removed my existing pgAdmin 4 and downloaded the latest 6.15. When I attempted to install it, the installer informed me that this version was not compatible with my version of PostgreSQL 10.3. So, I headed back and downloaded 4.30, which is now running. Unfortunately, it warns me each time I run it that a newer version is available. I just need to upgrade my entire PostgreSQL installation.
I had the same issue previously, and had to manually select the path.
Apparently now (v. 4.25) it auto-detects the path and updates correctly.
I had to download from the website, there was no update button embedded in pgAdmin itself
I just installed Apache Casandra 1.2.1 on Windows Server 2012 (It's a VM). I double clicked cassandra.bat and it worked without an error.
How can I run Cassandra.bat as a Windows Service, so I can sign out from cumputer?
cassandra.bat file also helps you to run Cassandra as a Windows Service. You just need Commons Daemon Service Runner Windows binaries.
You will need to create a folder named daemon under the bin directory and extract the correct version (32/64 bit) of prunsrv.exe to this directory (bin\daemon).
Run command prompt and change directory to the bin. Type;
cassandra.bat install
Then run services.msc command to see cassandra(yes, lowercased) as a Windows Service.
You can also download
Datastax Community Edition
or
Cassandrows
which easily install, configure and run Apache Cassandra as a Windows Service.
I followed several tutorials-which all appeared to say the same thing-on how to create deployable flat-packages (.pkg) using the OS X system provided pkgbuild tool. The packages was always generated just fine. They did, however, not want to be installed.
Running the graphical Apple Installer or the command line interface installer aborted the installation early on giving an generic “Unknown error” after prompting for higher permissions.
Hours later after closer investigation I discovered that I could not install other packages either. Not even updates and new installations from the OS X App Store. Why could I not install my own nor any other packages? What was going on?
The installer daemon service itself is unresponsive. Force quit the installed program from from the Activity Monitor, or from the command line with sudo killall installd.
Can somebody let me know the best way to installation clear case application on a AIX server.
Clearcase version 7.1.2
If we have the method for uninstallation , it will be highly appreciated.
This should follow the general rules for ClearCase installation on Unix.
I have detailed one in "How do you install ClearCase 7.1 on a Unix-based server with no GUI and no internet?".
There are only a few of feature issues with AIX.
The silent uninstall procedure for ClearCase is covered in "ClearCase 7.1 Silent Uninstall by example on UNIX or Linux".
CD to the directory /var/ibm/InstallationManager/uninstall on the installed system.
Download the appropriate operating system response file from the following technote:
Sample uninstall response files for IBM Rational ClearCase
Run the following command in the above directory:
Example:
uninstall --launcher.ini silent-uninstall.ini -input /root/clearcase_uninstall_response_sol_x86.xml
In the previous example the response file is
/root/clearcase_uninstall_response_sol_x86.xml
This will uninstall ClearCase from the system.
The following will uninstall Install Manager from the above said directory:
uninstall --launcher.ini silent-uninstall.ini