Executable installed by Windows installer crashes on startup.

[Mathieu Doucet]

Tried installing the latest nightly build (16/08/10) on a Windows 7 machine (64-bit Intel). Python 2.5 was properly installed. Running either the Mantid.msi or Mantid64.msi installers, the installed executable crashes on startup with the following message:

The application was unable to start correctly (0xc00007b).

For reference, Release 1.0.4875 runs just fine.

[Nick Draper]

look into this please, Owen Arnolds PC is Windows 7

[Michael Whitty]

Same result on Win7 64b for release 5818. Going to back track to try and find break point.

[Michael Whitty]

5671 (16/08 09:28): unable to start 5660 (13/08 20:56): unable to start 5654 (13/08 17:22): unable to start 5648 (13/08 09:13): unable to start 5643 (12/08 19:49): unable to start 5642 (12/08 18:41): unable to start 5641 (12/08 17:50): unable to start 5641 (12/08 17:28): unable to start

5636 (12/08 16:38): not recognising Python at install point 5636 (12/08 16:15): not recognising Python at install point 5617 (11/08 11:17): not recognising Python at install point

So, on this PC for some reason none of them work, but there's a difference in reactin between 5636 and 5641 (which are adjacent for Win64), that would suggest something in the installer is different for these.

[Michael Whitty]

32 bit has more consistent builds...

last nights build: starts 5691 (17/08 09:15): starts 5639 (12/08 17:05): starts

Problem doesn't seem to affect Win32.

[Michael Whitty]

(In [5837]) re #1487 - problem is due to wrong python libraries being used. Installer updated to dis-allow 32bit python dlls being considered acceptable for 64bit installer.

[Nick Draper]

fill in missing resolution

[Mathieu Doucet]

Works. Also checked that the installer verifies the python version (32bit vs 64bit)

[Stuart Campbell]

This ticket has been transferred to github issue ​2334