Fatal Exception in deplayer-only
Fatal Exception in deplayer-only
Hi. Not DE-savvy, so please forgive me. We recently migrated, thanks to one of DE's brilliant associates, over to LE9 from from LE 6.53. One niggle that we can't seem to fathom: when running certain procedures in deplayer, we get a Fatal Exception: Access Violation, and we are kicked out. I believe this is to do with memory? The strange thing is, when running the same procedures through Developer, they work perfectly. Stranger still - a single colleague of mine, running the same version of Windows, is able to run said procedures through deplayer.... Any ideas why these would work through Developer and not player, and why they do seem to work through player for a single user? Thanks in advance.
Re:Fatal Exception in deplayer-only
Are you running the DEPLAYER that is shipped with Developer.
We have seen sometimes that doesn't work when Developer does and the full player works. The Player shipped with Developer is more a test version (even though eventually it will be a full part of the package) to test application on how they will work in player when you develop.
The problem is sharing of files and settings between Developer and Player.
Which version are you using?
Re:Re:Fatal Exception in deplayer-only
Hello. Thank you for your response. I believe we are running the most up-to-date version of each - 9.0.0.6835. We have only very recently downloaded and installed them. What I can't seem to work out is why these procedures work through player on one particular machine, but crash on all others. We have 7 users, all running the same version of player. 6 out of 7 crash - but one seems to work perfectly. The machine it is working on is running the same version of Windows (11). There's nothing obviously different about it. Most peculiar!
Re:Re:Re:Fatal Exception in deplayer-only
Does the procedures that crash by any chance use any CDF's or something like that?
Re:Re:Re:Fatal Exception in deplayer-only
Do you run the player that is shipped with Developer or do you use the dedicated Player install?
Re:Re:Re:Re:Fatal Exception in deplayer-only
Hello! Apologies for the late response. Your question regarding running Player that shipped with Developer vs. standalone Player is an interesting one! On 5 machines I installed Developer first, then the player that shipped with it. These are the machines are the ones experiencing crashes. On machine 6, I installed standalone player-only. This is the machine where all functions appear to be working!
So, the simple fix would be to install standalone player on all other machines.
However, I've encountered a problem with that, too.
I should note that at this point, I haven't uninstalled anything.
On my machine, I downloaded and installed standalone player. I entered our licence key, all worked perfectly. I went to the next user, repeated the process on their machine, but when I entered the licence key, I got an error message to say "Licence Invalid". I'm not quite sure why? Do I need to uninstall everything from these other machines, and then redownload?
Thank you in advance.
Installing DEPLAYER on Server share and running it from there.
No. You don't have to de-install anything ;-)
The problem is most likely that you get a space to much in front of the License key when you copy paste ;-)
You can even install (copy) the Player to a share on your server and run it from there. If you take your licence key and put it in either the Program Catalogue on the share or directly in your app then you don't have to enter it on each device.
DataEase licensing is designed so you in principle can license an application only but that is another story and something we offer vertical companies etc.
Then you just create a shortcut that point at the share with the necessary arguments and copy that out to each computer after.
The best thing with this solution is that when you upgrade your LE9 you only have to do it in one location rather than on each device.