Forums | Admin

Discussion Forums: open-discussion

Start New Thread Start New Thread

 

By: Clifford Caoile
RE: Gem win32-eventlog v0.5.2 on Ruby 1.9.1-1.9.2 [ reply ]  
2011-02-02 23:08
Hello,

I had the same String encoding error when using win32-dir. I proposed the following solution:

http://rubyforge.org/forum/forum.php?thread_id=49201&forum_id=319

which was to force the reset of the Encoding of the data received from the Windows API to the Default External Encoding. In my case that made the String's Encoding turn into Shift JIS.

For your case, try modifying win32/eventlog.rb in the same way as above.

By: Jason Bourne
Gem win32-eventlog v0.5.2 on Ruby 1.9.1-1.9.2 [ reply ]  
2011-02-02 18:42
1.Requirement: Read the latest lines of the Windows Application Event
Viewer to verify deployment status executions.
2. Environment: Ruby 1.9.1 On Windows
win32-eventlog (0.5.2)
windows-api (0.4.0)
windows-pr (1.1.3)
3. Problem: On Ruby 1.8.7 my scripts using win32 evenlog api works fine
but on ruby 1.9.1 they don't. I know the String management has changed
on Ruby 1.9.1 and above.

4. Exception Details.
C:/Ruby191/lib/ruby/gems/1.9.1/gems/win32-eventlog-0.5.2/lib/win32/eventlog.rb:14:in
`[]': invalid byte sequence in US-ASCII (ArgumentError)
from
C:/Ruby191/lib/ruby/gems/1.9.1/gems/win32-eventlog-0.5.2/lib/win32/eventlog.rb:14:in
`nstrip'
from
C:/Ruby191/lib/ruby/gems/1.9.1/gems/win32-eventlog-0.5.2/lib/win32/eventlog.rb:613:in
`read'
from bw_logutil.rb:49:in `read_event_log'
from bw_logutil.rb:97:in `block in <main>'
from bw_logutil.rb:96:in `each'
from bw_logutil.rb:96:in `<main>'
5. Source of Information :
http://raa.ruby-lang.org/project/win32-eventlog/
6. Tried Solutions. Tried to use WMI but there is no way to filter the
latest results.

Could someone help me with this.