Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
EMU does not open
#1
I just installed EMU earlier and it was running fine.  I did an update to the fixture library and then closed out of EMU and now the app won’t open.  I tried restarting computer as well.  I am using windows with a brand new laptop.
Reply
#2
Something similar here; I did the update to the new v21.9.3.1 and I have to run the software twice to make it run, because the first time it shows the annoy splash and then it close, and the next one it does opens.
Reply
#3
(04-09-2021, 03:14 AM)Mike7300 Wrote: I just installed EMU earlier and it was running fine.  I did an update to the fixture library and then closed out of EMU and now the app won’t open.  I tried restarting computer as well.  I am using windows with a brand new laptop.

Anyone else having this issue? I find it hard to believe I would be the only one.
Reply
#4
(06-09-2021, 02:52 PM)Mike7300 Wrote:
(04-09-2021, 03:14 AM)Mike7300 Wrote: I just installed EMU earlier and it was running fine.  I did an update to the fixture library and then closed out of EMU and now the app won’t open.  I tried restarting computer as well.  I am using windows with a brand new laptop.

Anyone else having this issue? I find it hard to believe I would be the only one.

I am also having the same issue. I assumed it was an issue with my older laptop so installed it on my new one but had exactly the same experience. Frustratingly even completely uninstalling the program and reinstalling from the original download file (i.e. pre update) does not make any difference. No attempts at rebooting, reopening etc are having any impact so at the moment it is unusable Sad
Reply
#5
Had the same problem after an update of the software. I guess its a bug.
Try to go to "C:\Users\Public\Documents\EMU" and delete the "emu_db.tmp" file if there is one.
This fixed my problem.
Reply
#6
Thanks for reporting guys! If possible would you be able to ping across your <C:\Users\Public\Documents\EMU> database files, either directly or to our support teams directly referencing this thread if you'd rather not share your logs on the forum.

It seems certain windows builds are causing EMU to throw issues (oddly not on all versions of Windows) - our test machines seem to be running without a hitch. If you are able to send over the suspect logs we'll be sure to dive in and try and pinpoint what's going on here.
Reply
#7
(11-09-2021, 04:54 AM)JamesW_ENTTEC Wrote: Thanks for reporting guys! If possible would you be able to ping across your <C:\Users\Public\Documents\EMU> database files, either directly or to our support teams directly referencing this thread if you'd rather not share your logs on the forum.

It seems certain windows builds are causing EMU to throw issues (oddly not on all versions of Windows) - our test machines seem to be running without a hitch. If you are able to send over the suspect logs we'll be sure to dive in and try and pinpoint what's going on here.

deleting the .tmp file mentioned by another user also worked for me.

Happy to share my database file but you'll have to hold my hand and give me precise instructions as to how I do this (who I need to email etc).

The database file is large and it didnt seem to want to let me add it on here.

However I can help please let me know Smile
Reply
#8
(10-09-2021, 08:12 PM)Godelsberg Wrote: Had the same problem after an update of the software. I guess its a bug.
Try to go to "C:\Users\Public\Documents\EMU" and delete the "emu_db.tmp" file if there is one.
This fixed my problem.

This worked for me too, thank you for the tip Smile
Reply
#9
(10-09-2021, 08:12 PM)Godelsberg Wrote: Had the same problem after an update of the software. I guess its a bug.
Try to go to "C:\Users\Public\Documents\EMU" and delete the "emu_db.tmp" file if there is one.
This fixed my problem.

This fixed it for me also, thanks!
Reply
#10
(10-09-2021, 08:12 PM)Godelsberg Wrote: Had the same problem after an update of the software. I guess its a bug.
Try to go to "C:\Users\Public\Documents\EMU" and delete the "emu_db.tmp" file if there is one.
This fixed my problem.

After a bit of playing around here is what I deduced:

Deleting the emu_db.tmp file does indeed enable the program to re-open, but it means that the fixture library is stuck at the previous version (i.e. the downloaded update hasn't been successfully applied. It appears that the .tmp file is actually the new fixture library, so I did the following:

Renamed emu.db file to emuold.db

Renamed the .tmp file to emu.db

Restarted the program.

At this point it successfully opened and my fixture library is now running on the latest version (21.09.4507 at the time of writing)

Obviously a bug in the system somewhere but this has at least given me a work around for now.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)