Hi,
I've been fighting WebDeploy 3.0 for a few days because Web Deploy Service (MsDepSvc.exe) randomly crashes. I've managed to recreate this behavior by executing the following run command 10-15 times on a row:
msdeploy.exe -verb:sync -source:runCommand="ipconfig" -dest:auto,computerName="remoteServer",userName="domain\user",password="password"
By duplicating this command in a .bat file about 20 times, I've managed to consistently replicate this crash. In addition we've seen this behaviour very frequently in our continuous deployment process, where this issue was originally discovered, but at different intervals and times.
Note: By adding back Web Deploy 2.0 on the servers, the problem goes away.
On the server running MsDepSvc the follwing relevant entries are found in the event log:
1) Entry from WebDeploy:
System.ArgumentException: Invalid token for impersonation - it cannot be duplicated.
at System.Security.Principal.WindowsIdentity.CreateFromToken(IntPtr userToken)
at System.Security.Principal.WindowsIdentity..ctor(IntPtr userToken, String authType, Int32 isAuthenticated)
at System.Security.SecurityContext.CreateCopy()
at System.Threading.ExecutionContext.CreateCopy()
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
2) Entry from .NET runtime:
Application: MsDepSvc.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException
Stack:
at System.Security.Principal.WindowsIdentity.CreateFromToken(IntPtr)
at System.Security.Principal.WindowsIdentity..ctor(IntPtr, System.String, Int32)
at System.Security.SecurityContext.CreateCopy()
at System.Threading.ExecutionContext.CreateCopy()
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
Note: We use WebDeploy 3.0 from the source/client. The command works perfectly with WebDeploy 2.0 on the server, so for now we've been forced to use 2.0 until this problem is solved in 3.0.
Would be very interested to hear if others are able to replicate this, cause we have these errors on 10s of servers in 2 different environments/domains.
Thanks,
Jon Arild Tørresdal