[1.1.0-Beta1] Windows XP, 7, 8: problems with native library WinUtil.dll when using a 32-Bit Java - SikuliX not useable --- fixed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SikuliX |
Fix Released
|
Critical
|
RaiMan |
Bug Description
---- possible workarounds:
-- on 64-Bit Windows use a 64-Bit Java version
-- use the WinUtil.dll from version 1.0.1
-------
Have already successfully loaded and used Sikuli 1.0.rc3 for over a year and then switched over to Sikuli 1.0.1 in the last few weeks. (Uninstalled Sikuli 1.0rc3, then installed Sikuli 1.0.1 in c:\SikuliX. All was fine. Today, renamed SikliX to SikuliX1.01. Created a new directory c:\Automation\
…. more ….
[debug (5/5/14 1:35:50 PM)] RunSetup: trying to set up the environment
[debug (5/5/14 1:35:50 PM)] ResourceLoader: check: we are running on arch: x86
[debug (5/5/14 1:35:50 PM)] ResourceLoader: check: using Java at: C:/Program Files/Java/jre6/
[error (5/5/14 1:35:50 PM)] ResourceLoader: check: No valid libs path available until now!
[action (5/5/14 1:35:50 PM)] ResourceLoader: check: Please wait! Trying to extract libs to jar parent folder: C:/Automation/
[debug (5/5/14 1:35:50 PM)] ResourceLoader: extractLibs: from: file:/C:
[debug (5/5/14 1:35:51 PM)] ResourceLoader: extractLibs: Found 20 Files in META-INF/
[debug (5/5/14 1:35:53 PM)] ResourceLoader: checkLibsDir: trying: C:\Automation\
[debug (5/5/14 1:35:53 PM)] ResourceLoader: checkLibsDir: Running on Windows - checking system path!
[debug (5/5/14 1:35:55 PM)] ResourceLoader: checkLibsDir: Added libs dir to path: C:\Automation\
[debug (5/5/14 1:35:55 PM)] ResourceLoader: checkLibsDir: ... n25;c:\support tools;C:
[error (5/5/14 1:35:55 PM)] ResourceLoader: loadLib: Fatal Error 110: loading: WinUtil.dll
[error (5/5/14 1:35:55 PM)] ResourceLoader: loadLib: Since native library was found, it might be a problem with needed dependent libraries
C:\Automation\
[error (5/5/14 1:35:55 PM)] ResourceLoader: loadLib: Check, wether a valid Sikuli libs folder is in system path at runtime!
[error (5/5/14 1:35:55 PM)] ResourceLoader: loadLib: Running Setup: ignoring this error for now
[debug (5/5/14 1:35:55 PM)] ResourceLoader: checkLibsDir: Using libs at: C:\Automation\
[debug (5/5/14 1:35:55 PM)] ResourceLoader: check: recreated ClassLoader.
[debug (5/5/14 1:35:58 PM)] RunSetup: Trying to run functional test: running script statements via SikuliScript
…. more ….
[debug (5/5/14 1:36:10 PM)] ResourceLoader: loadLib: Now loaded: VisionProxy from: C:\Automation\
[error (5/5/14 1:36:10 PM)] RunSetup: null
[error (5/5/14 1:36:10 PM)] RunSetup: Something serious happened! Sikuli not useable!
Check the error log at C:\Automation\
[error (5/5/14 1:38:21 PM)] RunSetup: Functional test Jython did not work
[error (5/5/14 1:38:21 PM)] RunSetup: ... terminated abnormally :-(
[error (5/5/14 1:38:21 PM)] RunSetup: Something serious happened! Sikuli not useable!
Check the error log at C:\Automation\
Even though it did not install correctly, I still tried to run Sikuli via the command line. I got this error:
[error] ResourceLoader: loadLib: Fatal Error 110: loading: WinUtil.dll
[error] ResourceLoader: loadLib: Since native library was found, it might be a problem with needed dependent libraries
C:\Automation\
[error] ResourceLoader: loadIb: Check, wether a valid Sikuli libs folder is in system path at runtime!
[error] RunSetup: Problem with SikuliX libs folder - see error log
summary: |
[1.1.0-Beta1] Windows XP, 7, 8: problems with native library WinUtil.dll - when using a 32-Bit Java - SikuliX not useable + when using a 32-Bit Java - SikuliX not useable --- fixed |
Changed in sikuli: | |
status: | New → Fix Released |
importance: | Undecided → Critical |
assignee: | nobody → RaiMan (raimund-hocke) |
milestone: | none → 1.1.0 |
under evaluation