You are here

LibreOffice 3.6.1 on Vista Home Premium fails due to Data Execution Protection

10 posts / 0 new
Last post
lvirden
Offline
Last seen: 11 years 6 months ago
Joined: 2011-07-18 12:59
LibreOffice 3.6.1 on Vista Home Premium fails due to Data Execution Protection

32 bit Vista Home
Fresh Java installed this morning
Last night I used the PortableApps start program to verify that I have the lastest apps. It updated LibreOffice to 3.6.1.

Now when I attempt to run LibreOffice Portable or Base, I get an error saying that Vista closed it because of Data Execution Protection.

John T. Haller
John T. Haller's picture
Offline
Last seen: 8 hours 9 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
How Far?

Do you know how far the process gets? I know I have DEP on in Windows 7 x64 on my machine and it works just fine. And I believe it's the same code in Vista and 7 (and 8 as well). My only Vista install is 32-bit (which doesn't have DEP as a result) and it works fine there. Could you try running soffice.exe directly? It's in LibreOfficePortable\App\libreoffice\program. This is equivalent to running the regular version, so it will create a profile in APPDATA for it, but it will help with troubleshooting.

Sometimes, the impossible can become possible, if you're awesome!

lvirden
Offline
Last seen: 11 years 6 months ago
Joined: 2011-07-18 12:59
How to determine progress?

I see a splash page and the progress bar appears to go about 40 percent across the screen. Is there a way to determine more details?

This is 32 bit Vista that I am using as well.

Running soffice.exe directly results in the same problem.

Is there some way to get a log file of what is happening?

John T. Haller
John T. Haller's picture
Offline
Last seen: 8 hours 9 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Ah, Vista DEP

Ah, I think I know. You turned on DEP for all programs in Vista, correct? (The default is just for Windows programs) If so, this setting can impact other things. For instance, the LibreOffice (regular local) installer fails to run with DEP on.

I did test it out on mine which supports DEP at the hardware layer and LibreOffice Portable 3.6.1 worked just fine.

Sometimes, the impossible can become possible, if you're awesome!

lvirden
Offline
Last seen: 11 years 6 months ago
Joined: 2011-07-18 12:59
Vista DEP

Actually, it is still on the "essential windows programs and services only setting.

And my machine also is listed as supporting DEP at the hardware layer.

John T. Haller
John T. Haller's picture
Offline
Last seen: 8 hours 9 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Path?

What is the full path to LibreOffice Portable?

Sometimes, the impossible can become possible, if you're awesome!

lvirden
Offline
Last seen: 11 years 6 months ago
Joined: 2011-07-18 12:59
path to the libreoffice portable app folder

C:\Users\Owner\Software\PortableApps\PortableApps\LibreOfficePortable.

The path after Owner/Software was generated by default by the portable apps installer. Is it a problem?

John T. Haller
John T. Haller's picture
Offline
Last seen: 8 hours 9 min ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Not Sure

Not sure, just wondering if it was a system special folder. I can't figure out any reason your system should be doing this as I can't get my test Vista 32 system to recreate your issue.

Would you be averse to installing a local copy of LibreOffice temporarily to see if that has the same issue?

Sometimes, the impossible can become possible, if you're awesome!

lvirden
Offline
Last seen: 11 years 6 months ago
Joined: 2011-07-18 12:59
Installing local

I don't have a problem - it used to be installed locally, but I was trying to set up the portable environment.

lvirden
Offline
Last seen: 11 years 6 months ago
Joined: 2011-07-18 12:59
LO 3.6.1 local install works

Okay, I am back. Fell asleep while running the install.... sorry.
Anyways, with it installed regularly, it runs. Slowly, but it runs.
Also, the splash page displays a running commentary of what is starting wiht it installed this way - the portable one didn't do that, if I recall correctly. Appears to be something unusual about the portable 3.6.1 in my environment.

Log in or register to post comments