[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] update with zip vs msi package
- Date: Wed, 13 Jan 2010 09:34:24 +0800
- From: <Greg.Hitchen@xxxxxxxx>
- Subject: Re: [Condor-users] update with zip vs msi package
We also found this
Carl and now check for and install .NET 3.5 as part of our
script. Manually looking in the \Windows\WinSxS directory
look for the
*VC90.CRT* folder to see if it's there will tell you. Our script
see if .NET 3.5 is installed.
After updating .Net framework to 3.5 it started to work. It as
something to do with msvcr90.dll. It was in condor bin dir but not in the
windows directory. That was the difference from the working machine and
the non-working one.
On Tue, Jan 12, 2010 at 12:50 PM, Todd Tannenbaum <tannenba@xxxxxxxxxxx>
The steps taken
by the automated install that you will need to do (if you are installing for
the first time from the zip file) are documented here:
carl langlois wrote:
the process of updating my condor pool to 7.2.5 i have encounter a issue on
some of the windows machine with condor_master failing to start. But if i
use the msi package it work fine.
After a digging a bit more a found in
some thread that i'm not the only one that had this problem. It has a
something to do with dll file in provide by windows.
The way i work
for updating my pool is repackaging the zip file with internal tool and
install that. My question is what the msi condor package do so that
condor_master is working but not working with the zip file?.
Is there any
dll registration, regkey ?.....
of these steps include registering the condor_master with the Windows Service
Control manager, having either a system environment variable or a registry key
pointing to the config file, etc.
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
archives can be found at: