Hi, don't know if it helps you too, but this post https://groups.google.com/forum/#!topic/puppet-users/Ll1VIWSbmO8 helped me when i got that error.
I just replaced the forward-slashes in the source attribute by double backslashes and i could install the msi. Regards, Michael Am Donnerstag, 18. Juli 2013 05:49:40 UTC+2 schrieb Josh Cooper: > > > > > On Wed, Jul 17, 2013 at 1:29 PM, Josh D <[email protected]<javascript:> > > wrote: > >> On Wednesday, July 17, 2013 1:56:42 PM UTC-6, Josh Cooper wrote: >> >>> >>> Another user had to modify the NTFS and Share permissions for 'Domain >>> Computers' to access the share (map the drive)[2]. This is because >>> LocalSystem doesn't have any credentials with which to access the network. >>> >>> Josh >>> >>> [1] https://groups.google.com/**d/msg/puppet-users/** >>> 86dBOxvirK0/I6CtTH_BGEgJ<https://groups.google.com/d/msg/puppet-users/86dBOxvirK0/I6CtTH_BGEgJ> >>> [2] https://groups.google.com/**d/topic/puppet-users/** >>> xoJpt6ARe0Y/discussion<https://groups.google.com/d/topic/puppet-users/xoJpt6ARe0Y/discussion> >>> >> >> I think that's the issue: >> G:\Tools\Puppet\win64\Python>psexec -i -s msiexec.exe /qn /norestart /i >> \\<server>\<share>\Puppet\win64\Python\python-2.7.5.amd64.msi >> TARGETDIR=C:\Python27 ALLUSERS=1 >> >> PsExec v1.98 - Execute processes remotely >> Copyright (C) 2001-2010 Mark Russinovich >> Sysinternals - www.sysinternals.com >> >> >> msiexec.exe exited on SSCLD134G82G with error code 1619. >> > > This exit code means "This installation package could not be opened. > Verify that the package exists and that you can access it."[1] > > Side note, I think the error code (1619) isn't getting picked up by Puppet >> correctly. >> > > Yes, ruby truncates windows exit codes to a single byte[2] > > C:\work\puppet>ruby --version > ruby 1.9.3p374 (2013-01-15) [i386-mingw32] > C:\work\puppet>ruby -e "%x{cmd.exe /c exit 1619}; puts $?.exitstatus > 83 > > where 1619 = 0x653 and 83 = 0x53 > > A fellow puppet user has tried to work around this in the dism module[3]. > I would hate to see this proliferate across modules, surely ruby will fix > this, though I can't understand why the ticket is marked as a feature. > > So I'm trying to weigh my options. I'm a lowly developer and can't muck >> with domain users, nor can I change the security permissions on any of the >> CIFS network shares. Running puppet agent manually, works on my test >> machine because I'm local admin, but won't work for other users who aren't. >> I think I've tried copying installers using a File resource and then >> requiring and installing from said file in a package, but I recall that >> causing issues. >> >> In the windows world, you'll either need to modify the network shares > (which you can't do), configure the puppet agent service to run as a domain > user that does have permission (not sure if that's an option for you), or > serve the packages through some other means, e.g. puppet master file > server[4], apache, etc. > > Josh > > [1] http://support.microsoft.com/kb/290158 > [2] https://bugs.ruby-lang.org/issues/8083 > [3] https://github.com/puppetlabs/puppetlabs-dism/pull/14 > [4] http://docs.puppetlabs.com/guides/file_serving.html > > -- > Josh Cooper > Developer, Puppet Labs > > *Join us at PuppetConf 2013, August 22-23 in San Francisco - * > http://bit.ly/pupconf13* > **Register now and take advantage of the Final Countdown discount - save > 15%!* > -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users. For more options, visit https://groups.google.com/groups/opt_out.
