Sparx Systems Forum

Enterprise Architect => Bugs and Issues => Topic started by: cbear42 on April 13, 2017, 04:29:42 am

Title: Missing DLL not fixed with re-install of Sparx 13
Post by: cbear42 on April 13, 2017, 04:29:42 am
I'm receiving a missing dll (WTHES432.dll) on installing to Windows 7 machine. Multiple complete uninstalls, reboots and re-installs are still giving the same error. Any ideas anyone?

Thanks,

CBear42
Title: Re: Missing DLL not fixed with re-install of Sparx 13
Post by: qwerty on April 13, 2017, 04:33:33 am
Google pointed me to http://www.wintertree-software.com/support/thesdb/patch41.zip (http://www.wintertree-software.com/support/thesdb/patch41.zip) and a couple of descriptive links.

q.
Title: Re: Missing DLL not fixed with re-install of Sparx 13
Post by: cbear42 on April 13, 2017, 05:08:40 am
Thanks for responding - but - unfortunately, no joy with that.

Copied the dll to the SysWOW64 directory and used the regsvr32 command on it and got an error that it could not find the DllRegisterServer entry point - and told me it was not a valid OCX/DLL file. (I am running on a 64-bit machine - which is the reason for running it from that directory in an elevated command window.)
Title: Re: Missing DLL not fixed with re-install of Sparx 13
Post by: Eve on April 18, 2017, 11:28:10 am
It's not COM, so registering it won't work. Just put it directly in the EA directory.

It should be installed there during install. I've seen problems when downgrading using an earlier msi. But either repairing or doing a fresh install always fixed issues for me. Not sure why it would fail to install correctly. Maybe Windows thinks that file is already installed for some reason.

It's probably worth running an install with logging turned to maximum (msiexec /i easetupfull.msi /l*vx eainstalllog.txt) and sending the log to us.
Title: Re: Missing DLL not fixed with re-install of Sparx 13
Post by: Glassboy on April 18, 2017, 12:53:59 pm
It's not COM, so registering it won't work. Just put it directly in the EA directory.

It should be installed there during install. I've seen problems when downgrading using an earlier msi. But either repairing or doing a fresh install always fixed issues for me. Not sure why it would fail to install correctly. Maybe Windows thinks that file is already installed for some reason.

It's probably worth running an install with logging turned to maximum (msiexec /i easetupfull.msi /l*vx eainstalllog.txt) and sending the log to us.

Windows caches MSIs.  Sometimes these can corrupt and cause issues.  A couple of times I've had to find the cached MSI and delete it before the repair will work properly.