Issue #19808 has been updated by Klavs Klavsen.
Puppet is run from the "Start command prompt with puppet" shell - that comes with the MSI. The same issue exists, when the daemon runs. I have not specified a path setting - I'd expect it to use the system path. puppet agent --configprint path - says: none ruby ..ALT_SEPERATOR says: \ running set in the cmdprompt where I run puppet from says the Path equals the system path - with puppet paths prepended (ie. c:\WINDOWS\system32 is included in there. ---------------------------------------- Bug #19808: Service provider for windows 2003 - does not work https://projects.puppetlabs.com/issues/19808#change-87883 * Author: Klavs Klavsen * Status: Needs More Information * Priority: Normal * Assignee: Klavs Klavsen * Category: * Target version: * Affected Puppet version: * Keywords: windows * Branch: ---------------------------------------- If I define: service { 'nscp': ensure => running, enable => true } puppet wants to use init provider. I then tried to force it to use windows provider - but it fails (according to --debug) with "file net.exe does not exist" windows service provider is not functional on this host. Yet: net nscp restart works just fine (ie. net works fine :) Anything I can do to help debug? I'm running puppet-3.1.1 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
