Mailing List ArchivesAuthenticated access |
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}
|
Mailing List ArchivesAuthenticated access |
|
|
Just as an FYI John, I had a similar error when installing from the msi file for version 8.8.12 but only when installing into c:\program files\condor. It worked OK if I installed into c:\condor I could then uninstall it, reinstall it into c:\program files\condor, copy the condor_config file from the c:\condor install (the uninstall does not remove this) into c:\program files\condor and change the item: RELEASE_DIR = C:\Condor to RELEASE_DIR = C:\Program Files\Condor and everything seemed to work OK. I hadn’t tried this for a while, but it was pleasing to see that HTCondor is now happy to handle the space in C:\Program Files\Condor Cheers Greg From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx>
On Behalf Of John M Knoeller Hi Fabrice. From an Administrator command prompt can you run the installer with logging enabled ? msiexec /log inst905.1.log /i condor-9.0.5-Windows-x64.msi Once installation is complete (or failed) can you then query the ACLs on the files in the install directory? icacls c:\condor and icacls c:\condor\* and send me the output? I have tried a fresh install and I think I'm seeing the same thing that you did. It looks like the recent Windows update has disabled the ability of installers to run _vbscript_, which is what
we use to take the questions the installer asks and use the answers to customize the condor config files. The good news is that Condor is actually installed, and once you fix the ACLs on condor_config and condor_config.local and edit the config as needed, Condor will work. The bad news is that the questions that the installer asked aren't doing any good. condor_config will not have any of those customizations, and it will also not be readable by ordinary users. You can fix the ACL's of the condor_config files by running this command from an administrator command prompt
icacls condor_config* /grant BUILTIN\Users:RX After that you have will have to configure condor by editing the condor config files by hand. It is probably still less work to do this than to use the tarball installer. I have added this as a bug ticket to our ticket tracking system. -tj From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Fabrice Bouye <FabriceB@xxxxxxx> Hi, I am starting preliminary tests to see how condor 9.0.x behave before attempting further upgrades to our 8.8.x flock. As part of the tests I am setting up HTCondor anew on a test Linux CM and a couple of selected Windows/Linux/macOS
submit/execute machine to form a new mini test flock. However I have issues with the provided MSI installer which fails to install properly on Windows 10. Note: I have searched the issue before and some had it occurring in previous versions when attempting to install HTCondor in directories containing space in their name. Here I am just installing into c:\condor\ Installation was done with an account that has administrative permissions on the computer. Also the HTCondor 8.8.12 MSI installer just installs fine without any error on the same Windows 10 machine. The HTCondor 9.0.5 MSI installer proceeds OK through the license, pool, behavior, accounting domain, email settings, Java settings, permissions settings, universe settings, destination folder and ready to install screens.
It then asked for elevated access and proceeds with installation, but, near the end of the installation, it fails and issues the following error: > There is a problem with this Windows Install package. A script required for this install to complete could not be run. Contact your support personnel or package vendor. The install wizard then lands on the following screen:
> condor-9.0.5 Setup Wizard ended prematurely > > condor-9.0.5 Setup Wizard ended prematurely because of an error. Your system has not been modified. To install this program at a later time, run Setup Wizard again. Click the Finish button to exit the Setup Wizard. However at this stage, modifications have been made to the system: * the c:\condor\ has been created and filled * The condor service has been registered * the condor uninstallation has been registered (and working) * some files, such as condor_config and condor_config.local seem to have incoherent access permissions (ie: they are not accessible by the account who performed the installation). I will have a look into deploying the ZIP archive as an alternative even tough it’s not what the manual recommends and the instructions at
https://htcondor.readthedocs.io/en/latest/admin-manual/windows-installer.html#manual-installation-of-htcondor-on-windows are a bit lacking… ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– As part of our emissions reduction strategy, please only print this email if necessary |
