Deploy task hangs

Dec 23, 2010 at 10:26 AM

Finally got Team Deploy working here. Great! :)

However, I'm experiencing two strange problems.
1) If Remote Desktop is disabled on the target computer (tested on Windows 7 64-bit), I receive a System.IO.IOException as shown below.
2) Deploy task hangs. See log below.

 

#1 (Remote Desktop disabled on client):
       Task "Deploy"
         Stopping service psexesvc on testW7...
         Stopping service psexesvc on testXP...
         Stopping service psexesvc on testXP returned code:0
         Process psexesvc on testXP returned code:-1
         Process psexesvc on testXP had been terminated.
         Deleting service psexesvc on testXP...
         Deleting service psexesvc on testXP returned code:0
         In Uninstall.Execute()
         Stopping service psexesvc on testW7 returned code:0
         Process psexesvc on testW7 returned code:-1
         Process psexesvc on testW7 had been terminated.
         Deleting service psexesvc on testW7...
         Deleting service psexesvc on testW7 returned code:0
     1>C:\BuildType\TFSBuild.proj(237,5): error : Error executing CleanupPsExec: TargetMachine=testW7 KillPathFilename=c:\Program Files\PSTools\pskill2.exe:::System.IO.IOException: The network path was not found.
C:\BuildType\TFSBuild.proj(237,5): error :
C:\BuildType\TFSBuild.proj(237,5): error :    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
C:\BuildType\TFSBuild.proj(237,5): error :    at System.IO.File.Delete(String path)
C:\BuildType\TFSBuild.proj(237,5): error :    at TeamDeploy.Tasks.CleanupPsExec.Execute()

#2 (Deploy task hangs?):
     1>Target "DeployMSITargetVirtuals" in file "C:\BuildType\TFSBuild.proj" from project "C:\BuildType\TFSBuild.proj":
       Using "Deploy" task from assembly "C:\Program Files\MSBuild\TeamDeploy\TeamDeploy.Tasks.dll".
       Task "Deploy"
         Stopping service psexesvc on testXP...
         Stopping service psexesvc on testW7...
         Stopping service psexesvc on testXP returned code:0
         Stopping service psexesvc on testW7 returned code:0
         Process psexesvc on testW7 returned code:-1
         Process psexesvc on testW7 had been terminated.
         Deleting service psexesvc on testW7...
         Deleting service psexesvc on testW7 returned code:0
         Process psexesvc on testXP returned code:-1
         Process psexesvc on testXP had been terminated.
         Deleting service psexesvc on testXP...
         Deleting service psexesvc on testXP returned code:0
         Process A.exe on testW7 returned code:-1
         Process A.exe on testW7 had been terminated.
         Process B.exe on testW7 returned code:-1
         Process B.exe on testW7 had been terminated.
         Process A.exe on testXP returned code:-1
         Process A.exe on testXP had been terminated.
         Process C.exe on testW7 returned code:-1
         Process C.exe on testW7 had been terminated.
         Process B.exe on testXP returned code:-1
         Process B.exe on testXP had been terminated.
         Process D.exe on testW7 returned code:-1
         Process D.exe on testW7 had been terminated.
         Process E.exe on testW7 returned code:-1
         Process E.exe on testW7 had been terminated.
         In Uninstall.Execute()
         Process C.exe on testXP returned code:-1
         Process C.exe on testXP had been terminated.
         Process D.exe on testXP returned code:-1
         Process D.exe on testXP had been terminated.
         Uninstalling {11111111-2222-3333-4444-555555555555} on testW7 returned code:1605
         Uninstalling {11111111-2222-3333-4444-555555555555} on testW7 completed successfully.
         Process E.exe on testXP returned code:-1
         Process E.exe on testXP had been terminated.
         In Uninstall.Execute()
         Uninstalling {11111111-2222-3333-4444-555555555555} on testXP returned code:1605
         Uninstalling {11111111-2222-3333-4444-555555555555} on testXP completed successfully.
         This was the last item being logged. Waited 25 minutes and then terminated the build...

 

The only thing I can conclude from that is that the killing of process E.exe was not executed on testW7. I would expect the following entries:
         Process E.exe on testW7 returned code:-1
         Process E.exe on testW7 had been terminated.


Any ideas? Greatly appreciate your help!

Coordinator
Dec 23, 2010 at 12:59 PM

Hi,

I'm glad to hear you have Team Deploy working.  As for disabling RDP, I did some research and it changes some firewall settings behind the scenes.  You might try temporarily disabling the firewall to see if there was something set to block it.  Also, you might check the network settings and make sure the option that this computer can be seen by other computers is still enabled.   With a local administrator account, can you manually get to \\testW7\admin$?

As for the hanging, I'm not sure why you are seeing the -1.  I would try running PSKill manually to see if there is any more information.  Also, if you log into the machine, sometimes there is a dialog box being displayed that causes it to hang.

I hope this helps,

Mike