[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] update with zip vs msi package




We also have had this problem in some machines but didn't figure out how to fix it. The only way to make it work at that moment was to install using the MSI installer (first time) and then update as we needed. We followed the procedure described in "3.2.5.5 Manual Installation Condor on Windows" that Todd refered in his message, but when we tried to start the service an error message has been shown telling that there were some depencencies not installed (perhaps the mentioned .dll file).
I will investigate on that machines if .NET was updated to v3.5.

Please share any additional information that could be helpful.

Cheers,

Klaus



<Greg.Hitchen@xxxxxxxx>
Sent by: condor-users-bounces@xxxxxxxxxxx

12/01/2010 23:36

Please respond to
Condor-Users Mail List <condor-users@xxxxxxxxxxx>

To
<condor-users@xxxxxxxxxxx>
cc
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
kixstart install script. Manually looking in the \Windows\WinSxS directory and
look for the *VC90.CRT* folder to see if it's there will tell you. Our script actually
checks the registry to see if .NET 3.5 is installed.
 
Cheers
 
Greg
 


From: condor-users-bounces@xxxxxxxxxxx [mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of carl langlois
Sent:
Wednesday, 13 January 2010 4:54 AM
To:
Condor-Users Mail List
Subject:
Re: [Condor-users] update with zip vs msi package


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.


Thanks

Carl

On Tue, Jan 12, 2010 at 12:50 PM, Todd Tannenbaum <tannenba@xxxxxxxxxxx> wrote:
carl langlois wrote:
Hi,


In 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 ?.....


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:

http://www.cs.wisc.edu/condor/manual/v7.2/3_2Installation.html#SECTION00425500000000000000

Some 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.

Hope this helps,
Todd

_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to
condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at:

https://lists.cs.wisc.edu/archive/condor-users/
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/condor-users/



This message is intended solely for the use of its addressee and may contain privileged or confidential information. All information contained herein shall be treated as confidential and shall not be disclosed to any third party without Embraer’s prior written approval. If you are not the addressee you should not distribute, copy or file this message. In this case, please notify the sender and destroy its contents immediately.
Esta mensagem é para uso exclusivo de seu destinatário e pode conter informações privilegiadas e confidenciais. Todas as informações aqui contidas devem ser tratadas como confidenciais e não devem ser divulgadas a terceiros sem o prévio consentimento por escrito da Embraer. Se você não é o destinatário não deve distribuir, copiar ou arquivar a mensagem. Neste caso, por favor, notifique o remetente da mesma e destrua imediatamente a mensagem.