(tye)Re: Remote Win32::TieRegistry

End with ".../Parameters/Session/" instead of leaving off that final "/". This tells TieRegistry that you want the key "Session" and not the value "Session". Yes, it should work either way, but I suspect you've found a bug in regard to that.

Please let me know if that works.

- tye (but my friends call me "Tye")

Comment on (tye)Re: Remote Win32::TieRegistry

Replies are listed 'Best First'.
Re: (tye)Re: Remote Win32::TieRegistry by Anonymous Monk on Jul 03, 2002 at 21:36 UTC
Good idea but still no go. It know this is strange, but I can manipulate this key remotely with both regedit & regedt32 w/out any problems. I would assume they are using the same file (winreg.h) that Win32API::Registry is. I just wish I could get a more illluminating error message from M$.	[reply]
(tye)Re2: Remote Win32::TieRegistry by tye (Sage) on Jul 03, 2002 at 23:30 UTC
Another common problem is that TieRegistry, by default, requests quite a bit of access to the keys that it opens. This is most commonly a problem when someone wants read-only access to a key. This problem should produce a different error reason than the one you reported, but perhaps not in this case for some reason. So try specifying that you want less access to the key and see if that helps: `$remote_key = $Registry->Open( "$machine/$root_key", { Access => "KEY_READ" } ) or die "Can't read $root_key: ", regLastError(), "\n";` [download] For more sophisticated control over the level of access, you'll need to import some symbols: `use Win32::TieRegistry qw( :KEY_ ); # ... $remote_key = $Registry->Open( "$machine/$root_key", { Access => KEY_READ()\|KEY_SET_VALUE() } ) or die "Can't read $root_key: ", regLastError(), "\n";` [download] - tye (but my friends call me "Tye")	[reply] [d/l] [select]