Just for "archival purposes" I figured this out. The psexec tool when first run
displays a "accept license" dialog. I knew this and ran it and accepted the
license. However, I later realized that ccnet (which calls nant) runs under our
build domain account not my personal account. So, I had to login as the build
user, run psexec, accept the licese, then restart the ccnet service (to pick up
the path change). After I did that all was well.
From: Bob Archer [mailto:bob.arc...@amsi.com]
Sent: Wednesday, November 17, 2010 1:11 PM
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] Exec task not releasing exe
Our build server crashed so I had to build a new one. It was Windows 2003 not
on Windows 2008R2 64-bit. Our build script seems to have an issue... one of the
build tools that is run with an exec task doesn't exit when run via nant.
However, if I run it at the command line it exits fine.
If I end the process the build continues to run from that point.
Any ideas why this might be happening and what I could do about it?
I'm using nant .86.3317.0
(I have turned UAC off to see if maybe that affected it, but it doesn't seem to
matter).
BOb
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
