Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Still breaking puppetlabs/registry #7

Open
sandinak opened this issue Dec 18, 2013 · 17 comments
Open

Still breaking puppetlabs/registry #7

sandinak opened this issue Dec 18, 2013 · 17 comments

Comments

@sandinak
Copy link

Error: Failed to apply catalog: Parameter path failed on Registry_value[HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnections]: Munging failed for value "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnections"
Wrapped exception:
Munging failed for value "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnections" in class path: uninitialized constant PuppetX::Puppetlabs::Registry::KEY_WOW64_64KEY

uninstall and things start working again.

@liamjbennett
Copy link
Owner

What system are you running on?

@sandinak
Copy link
Author

Windows XP SP2 and SP3

On Dec 18, 2013, at 10:59 AM, Liam Bennett [email protected] wrote:

What system are you running on?


Reply to this email directly or view it on GitHub:
#7 (comment)

@liamjbennett
Copy link
Owner

What fact are you seeing this error? Do you have puppetlabs/registry installed?

@sandinak
Copy link
Author

Yea .. i have registry installed .. and it seems to happen if both are installed ( I saw the notes on previous tickets ) but I can't see a conflict.

On Dec 18, 2013, at 12:25 PM, Liam Bennett [email protected] wrote:

What fact are you seeing this error? Do you have puppetlabs/registry installed?


Reply to this email directly or view it on GitHub:
#7 (comment)

@liamjbennett
Copy link
Owner

Ok, apologies, yes I can see the bug now in the windows_sid fact. I will get this fixed shortly.

If your interested it's this line:
18 access = Win32::Registry::KEY_READ | KEY_WOW64_64KEY

@sandinak
Copy link
Author

Danke ;) I am starting to write several windows based puppet modules myself .. cygwin most specifically ;)

On Dec 18, 2013, at 12:40 PM, Liam Bennett [email protected] wrote:

Ok, apologies, yes I can see the bug now in the windows_sid fact. I will get this fixed shortly.


Reply to this email directly or view it on GitHub:
#7 (comment)

@liamjbennett
Copy link
Owner

That's great to hear. If you need any help, advice or guidance in doing that then I'm happy to help. You can always contact me on twitter @liamjbennett

@liamjbennett
Copy link
Owner

Also accepting feature requests as well as bugs ;)

@sandinak
Copy link
Author

k .. you can find me as @sandinak ;)

On Dec 18, 2013, at 12:44 PM, Liam Bennett [email protected] wrote:

That's great to hear. If you need any help, advice or guidance in doing that then I'm happy to help. You can always contact me on twitter @liamjbennett


Reply to this email directly or view it on GitHub:
#7 (comment)

@sandinak
Copy link
Author

Are you aware of any repo managers for windows + puppet? I've taken to creating /module/foo/install and putting installers in there and setting up shared mount .. etc. I am considering writing a tool to manage populating the install directories if people put source's in the module/manifests/init.pp .. kicking it around ;)

On Dec 18, 2013, at 12:44 PM, Liam Bennett [email protected] wrote:

That's great to hear. If you need any help, advice or guidance in doing that then I'm happy to help. You can always contact me on twitter @liamjbennett


Reply to this email directly or view it on GitHub:
#7 (comment)

@liamjbennett
Copy link
Owner

http://chocolatey.org/ and https://github.com/chocolatey/puppet-chocolatey is probably the nearest thing your after.

I am in the process of writing a couple of providers to cover the network and http sources for when you don't have or don't want to have a chocolatey infrastructure.

What your are doing now is still unfortunately a very common pattern.

@halberom
Copy link

Hello,
Have just started using this module and promptly ran into this bug, will you be doing a release shortly to resolve it?
Thanks

@delwaterman
Copy link

Bump on this issue as well

@AutomationD
Copy link

Still seeing an issue, Windows Server 2008 R2 (64 bit). Any clue how to mitigate it?
Thanks!

@JasonCrease
Copy link

Bump, getting it here too.

@dylanratcliffe1
Copy link

I was getting this error and found a fix that had nothing to do with win_facts. I was using the puppetlabs/registry module to change values without prefixing them with "32:" e.g. "32:HKLM\Softw..." Don't ask me WHY this fixed it (there is an answer but it goes completeley over my head) but it might be worth a try.

@gibbsoft
Copy link

+1 for dylanratcliffe1's answer... that solved my issue. Thanks.

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

No branches or pull requests

8 participants