Ticket #3170 (closed: fixed)

Opened 9 years ago

Last modified 5 years ago

Error messages on startup

Reported by: Martyn Gigg Owned by: Martyn Gigg
Priority: major Milestone: Iteration 29
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Stuart Campbell

Description 

Welcome to Mantid - Manipulation and Analysis Toolkit for Instrument Data
Could not open library C:\MantidProject\builds\trunk\bin\Debug\\Lib.dll: failed with error 126: The specified module could not be found.


Error opening C:\MantidProject\builds\trunk\bin\Debug\Lib.
Could not open library C:\MantidProject\builds\trunk\bin\Debug\\Lib.dll: failed with error 126: The specified module could not be found.


Error opening C:\MantidProject\builds\trunk\bin\Debug\Lib.
Could not open library C:\MantidProject\builds\trunk\bin\Debug\\Lib.dll: failed with error 126: The specified module could not be found.


Error opening C:\MantidProject\builds\trunk\bin\Debug\Lib.

Since the python bundling on Windows, when you start Mantid with the plugins directory pointed at bin you get these messages.

Change History

comment:1 Changed 9 years ago by Martyn Gigg

  • Status changed from new to verify
  • Resolution set to fixed

(In [12502]) Kill the error messages from LibraryManager that appeared when Mantid started up with the plugins directory pointed at the bin directory. The real trouble was that Poco::Path().isDirectory does not actually examine the disk as to whether something is a directory, Poco::File().isdirectory() does this. Also cleared a compiler warning and a warning message on MantidPlot startup about a QWidget already having a layout. Fixes #3170.

comment:2 Changed 9 years ago by Martyn Gigg

(In [12503]) Fix the tests temporarily while I implement the proper fix. Re #3170

comment:3 Changed 9 years ago by Martyn Gigg

(In [12505]) Fixes #3170. Sops some of the tests failing when running in parallel and using Poco::File.

comment:4 Changed 9 years ago by Owen Arnold

  • Status changed from verify to verifying
  • Tester set to Owen Arnold

comment:5 Changed 9 years ago by Owen Arnold

  • Status changed from verifying to verify
  • Tester Owen Arnold deleted

comment:6 Changed 9 years ago by Stuart Campbell

  • Status changed from verify to verifying
  • Tester set to Stuart Campbell

comment:7 Changed 9 years ago by Stuart Campbell

I don't see the messages listed in the ticket, but I do see ... 

DllOpen-[Error] Could not open library C:\MantidBuild\bin\Debug\\QtDesignerd4.dl
l: failed with error 126: The specified module could not be found.
DllOpen-[Error]
DllOpen-[Error]
DllOpen-[Error] Could not open library C:\MantidBuild\bin\Debug\\QtDesignerd4.dl
l: failed with error 126: The specified module could not be found.
DllOpen-[Error]
DllOpen-[Error]
DllOpen-[Error] Could not open library C:\MantidBuild\bin\Debug\\QtDesignerd4.dl
l: failed with error 126: The specified module could not be found.
DllOpen-[Error]
DllOpen-[Error]
MantidPython-[Notice] Error: Importing module "LoadNISTSANS" failed". No module
named multiarray
MantidPython-[Notice] Error: Importing module "LoadNISTSANS" failed". No module
named multiarray

comment:8 Changed 9 years ago by Stuart Campbell

  • Status changed from verifying to closed

Since these are different messages, I have created a new ticket #3272 and assigned it to you Martyn - Feel free to pass it on.

comment:9 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​4017

Note: See TracTickets for help on using tickets.