Skip to content
This repository has been archived by the owner on Feb 19, 2019. It is now read-only.

Second path fragment must not be a drive or UNC name. #613

Open
lmayorga1980 opened this issue Nov 17, 2014 · 7 comments
Open

Second path fragment must not be a drive or UNC name. #613

lmayorga1980 opened this issue Nov 17, 2014 · 7 comments

Comments

@lmayorga1980
Copy link

I am trying to install a package with custom arguments but it seems that i have some issues with chocolatey.

vagrant_log

https://gist.github.com/lmayorga1980/70bd7d8740372a984030

puppet_code

class siteminder ($version = '12.51') {

  $pkg = "siteminder-${version}-win64"

  file { 'config' :
    ensure  => present,
    path    => "C:\\Temp\\${pkg}.properties",
    content => template('siteminder/siteminder-win64.properties.erb'),
  } ->

  package { $pkg :
    name            => 'siteminder',
    ensure          => $version,
    provider        => 'chocolatey',
    install_options => ['-ia',"-f C:\\Temp\\siteminder-${version}-win64.properties"],
  }

  reboot {'siteminder reboot':
    subscribe => Package[$pkg],
  }
}

chocolatey package code

try {
  Install-ChocolateyPackage 'siteminder' 'exe' '-i silent' 'http://myserver/nuget/siteminder-12.51-win64.exe'

  Write-ChocolateySuccess 'siteminder'
} catch {
  Write-ChocolateyFailure 'siteminder' $($_.Exception.Message)
  throw
}
@ferventcoder
Copy link
Contributor

That's an interesting issue. This looks like it might be something with https://github.com/chocolatey/puppet-chocolatey though. Thoughts?

@ferventcoder
Copy link
Contributor

Can you run that with --debug --verbose --trace and post the output?

@lmayorga1980
Copy link
Author

@ferventcoder
Copy link
Contributor

==> default: Wrapped exception:
==> default: Execution of 'C:\ProgramData\chocolatey\chocolateyInstall\chocolatey.cmd install siteminder -version 12.51 -ia "-f C:\Temp\siteminder-12.51-win64.properties" -source http://myserver/nuget' returned 1: Chocolatey (v0.9.8.28) is installing 'siteminder' and dependencies. By installing you accept the license for 'siteminder' and each dependency you are installing.
==> default:  
==> default: siteminder v12.51
==> default: Installing siteminder...
==> default: siteminder has been installed.
==> default: siteminder has finished successfully! The chocolatey gods have answered your request!
==> default: siteminder has finished successfully! The chocolatey gods have answered your request!
==> default: Finished installing 'siteminder' and dependencies - if errors not shown in console, none detected. Check log for errors if unsure.
==> default: Chocolatey (v0.9.8.28) is installing 'C:\Temp\siteminder-12.51-win64.properties' and dependencies. By installing you accept the license for 'C:\Temp\siteminder-12.51-win64.properties' and each dependency you are installing.
==> default: Second path fragment must not be a drive or UNC name.
==> default: Parameter name: path2
==> default: Command 'install' failed (sometimes this indicates a partial failure). Additional info/packages: C:\Temp\siteminder-12.51-win64.properties
==> default: 

What happens when you run just
C:\ProgramData\chocolatey\chocolateyInstall\chocolatey.cmd install siteminder -version 12.51 -ia "-f C:\Temp\siteminder-12.51-win64.properties" -source http://myserver/nuget

Maybe it's an issue with the siteminder installer?

@ferventcoder
Copy link
Contributor

Lots of search results, particularly this one about using c:\ - http://gayotfow.wordpress.com/2014/04/27/second-path-fragment-must-not-be-a-drive-or-unc-name/

I think it has to do with your install args from the looks of things. Thoughts?

@lmayorga1980
Copy link
Author

@ferventcoder It seems that it worked from the command line without any issues but also it seems that the both parameters were send correctly to the siteminder installer

Command Line Args:
0:  -i
1:  silent
2:  -f
3:  C:\Temp\siteminder-12.51-win64.properties

I think that it might be an issue with puppet-chocolatey puppet module.

@rismoney could probably help us with this issue.

@ferventcoder
Copy link
Contributor

@lmayorga1980 I think this might be fixed in the new choco, but the puppet provider would need to be updated first...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants