in reply to Re^3: How to access Windows Vista/Server 2008 eventlogs(.evtx vs. .evt)
in thread How to access Windows Vista/Server 2008 eventlogs(.evtx vs. .evt)

Did you ever figure this out? I have been given an executable that has this call in it (which works just fine when run on an XP machine (backing up another remote xp machine): Win32::EventLog::OpenBackup ($EVTFILE,$SOURCE) where $EVTFILE = sprintf("%s\\%s_%s.evt",$BACKUP_LOG_DIR,$machine, $log_name); and $SOURCE = sprintf('\\\\%s',$MACHINE); and $MACHINE = shift || Win32::NodeName; But I get the same error when running this executable on a Server 2008 machine, trying to backup the event logs on a remote XP machine. I don't have the ability to change the code that the executable was compiled from. but perhaps I might be able to update the local DLLs or something else?
  • Comment on Re^4: How to access Windows Vista/Server 2008 eventlogs(.evtx vs. .evt)

Replies are listed 'Best First'.
Re^5: How to access Windows Vista/Server 2008 eventlogs(.evtx vs. .evt)
by BrowserUk (Patriarch) on Jun 11, 2010 at 15:03 UTC
    Did you ever figure this out?

    Yes. It works fine on Vista locally. Therefore I suggest you have a permissions problem.

    I don't have the ability to change the code that the executable was compiled from.

    "Compiled"? This is a Perl forum. If you really mean "packaged" (as in Par or similar), then extracting the source code from the packaging is (apparently) quite trivial.

    Quite frankly, expecting a script packaged under XP to continue to work under Vista is optimism of the highest (and most naive) order. Vista has a ream of changes in the way it works that simply didn't exist under XP.

    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom