My colleague has been testing extensively with winxp, win2k3, win7, win2k8, win8, win2k12 and reports the following problem.
What happens is that eventually, an installed winexesvc service on a target system becomes unstartable. The error message is:
Service cannot start, status=0x00000001
ERROR: Failed to install service winexesvc - NT_STATUS_UNSUCCESSFUL
Removing the service on the target system with "sc delete winexesvc" and then running winexe again seems to work, but within a few hours the service becomes unstartable again.
Could you provide some steps neccesary to reproduce this bug.
I have asked my colleague to provide more information.
My colleague never encountered the problem again because, since then, he has not used winexe so intensively. The problem arose with intensive use.
I just used winexe to run thousands of dir commands in a tight loop on a Windows 7 system and saw no probs.
Not reproducible
I realise this is closed, but I can add a bit more info...
This seems to be a timing related issue. I use winexe in scripts a lot, and often see this unless I add -d1 (or greater) to the command. This gives me a lot of extra debug info....and avoids the error ever appearing.
My best guess is that printing the debug info slows down....something, just enough to avoid whatever the fault condition is
Still cannot reproduce. By the way, do you use --reinstall/--uninstall options?
Oh well - I can't reliably reproduce it either, other than it occurs
sometimes. However, since adding the debug flags reliably works around it
it isn't a big deal.
I have never used the --reinstall/--uninstall options
Are they housekeeping calls for removing the service on machines?
Happy NY btw
On Tue, Dec 30, 2014 at 10:06 PM, ahajda ahajda@users.sf.net wrote:
Related
Bugs:
#29