Ticket #1487 (closed: fixed)

Opened 10 years ago

Last modified 5 years ago

Executable installed by Windows installer crashes on startup.

Reported by: Mathieu Doucet Owned by: Michael Whitty
Priority: major Milestone: Iteration 24
Component: Keywords:
Cc: Blocked By:
Blocking: Tester: Mathieu Doucet

Description

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.

Change History

comment:1 Changed 10 years ago by Nick Draper

  • Status changed from new to assigned
  • Owner set to Michael Whitty

look into this please, Owen Arnolds PC is Windows 7

comment:2 Changed 10 years ago by Michael Whitty

  • Status changed from assigned to accepted

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

comment:3 Changed 10 years ago by 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.

comment:4 Changed 10 years ago by 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.

comment:5 Changed 10 years ago by 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.

comment:6 Changed 10 years ago by Michael Whitty

  • Status changed from accepted to verify

comment:7 Changed 10 years ago by Nick Draper

  • Resolution set to fixed

fill in missing resolution

comment:8 Changed 10 years ago by Mathieu Doucet

  • Status changed from verify to verifying
  • Tester set to Mathieu Doucet

comment:9 Changed 10 years ago by Mathieu Doucet

  • Status changed from verifying to closed

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

comment:10 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 2334

Note: See TracTickets for help on using tickets.