Issue #19808 has been updated by Klavs Klavsen.

I have never heard of setting PATH in puppet.conf.

Could you point me to some docu. on this? I can't find anything about it here: 
http://docs.puppetlabs.com/guides/configuring.html

These are standard installed windows 2003 and 2008 servers - I haven't messed 
with the PATH. the path is also fine - when ruby looks - the which command you 
gave me, could find c:\windows\system32\net without a problem.

If I look at Environment variables - the first entry in Path is: 
%SystemRoot%\system32 (which when you save the field is shown as 
c:\windows\system32 - so I can't figure how you conclude it to be a system path 
problem ?

----------------------------------------
Bug #19808: Service provider for windows 2003 - does not work
https://projects.puppetlabs.com/issues/19808#change-87581

* Author: Klavs Klavsen
* Status: Needs More Information
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* Affected Puppet version: 
* Keywords: 
* 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.


Reply via email to