Open GoogleCodeExporter opened 9 years ago
Hmmm. Thanks for picking this up and for the workaround. I'm going to have to
think around this a bit but I'll almost certainly end up with a variation of
your code.
Original comment by tjgolden@gmail.com
on 27 Jul 2011 at 3:18
Yes, I figured you'd need to think about it from the perspective of the larger
design. Options I considered, without trying to understand the larger design,
included reading the registry lazily so it only fails if you try to use those
values, stuffing the reg_err_53.strerror into a defaultdict for the chunk of
code below my hack that reads attributes, and saving the error to check later
in dumped(). Having no idea where else these attributes are used if anywhere,
I offer these ideas, some obviously bad, hoping they'll help you think through
the right design.
Original comment by stu...@gmail.com
on 27 Jul 2011 at 3:39
Thanks for the ideas. I've just tested the scenario you describe and... I get
an access denied error, which is what I'd expect. At the risk of insulting your
intelligence, could you confirm that you definitely are using a target machine
name which is visible as such from your source? My test case is simply a
non-domain virtual server to which my own user has no particular access. A call
to registry.registry (r'\\server\HKLM') returns x_access_denied as does
event_logs.event_log (r"\\server\Application") at the RegConnectRegistry call.
Original comment by tjgolden@gmail.com
on 28 Jul 2011 at 7:29
I can confirm because after adding my workaround I'm able to read the event
log on the remote machine with no problem, it's just accessing the registry
remotely that fails. Access denied is not, if I recall, error 53, so maybe
something else is going on.
Original comment by stu...@gmail.com
on 29 Jul 2011 at 3:44
Thanks for the input. I'll look harder...
Original comment by tjgolden@gmail.com
on 29 Jul 2011 at 9:05
Original issue reported on code.google.com by
stu...@gmail.com
on 27 Jul 2011 at 3:57