Apache OpenOffice (AOO) Bugzilla – Issue 61724
Runtime Error while opening a document in a win98 network via Windows Explorer
Last modified: 2017-05-20 10:45:10 UTC
Hello, I have a WinXP machine with OOo 2.0.1 installed. The PC is connected to a win98 network. Problem: I open a document (doesn't matter, if word-doc or oo-doc) within the network via the windows explorer. The following error message is displayed and the doc is not opened: ------- Runtime Error! Program: "c:progr....soffice.bin" This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. ------- I can open the document via Windows Explorer, if it is stored locally. Neither connecting the network folder as a local drive nor a reinstallation does help. I can only open this document via the open-doc-dialog from OO, as it is working, but I think it is not satisfactorily. If you need further details do not hesitate to contact me! Best regards, Sascha Rankers ................................. Sascha Rankers .:mail sascha.rankers@gmail.com .:skype sascha.rankers .:icq 72946954 :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: German: WinXP Maschine mit Open Office Version 2.0.1 installiert. Windows Netzwerk mit 98 SE Rechnern. Wenn ich nun versuche über den Windows Eplorer eine oo-Datei zu öffnen bekomme ich nur eine Runtime FM: ------- Runtime Error! Program: "c:progr....soffice.bin" This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. ------- Wenn ich nun oo seperat öffne und über den Öffnen Dialog die Datei auswähle funktioniert es einwandfrei. Es funktioniert auch einwandfrei, wenn ich im Explorer eine oo-Datei lokal öffne (also auf einem lokalen Datenträger). Versuche ich den Netzordner als Laufwerk zu mappen bekomme ich den selben Fehler. Ich finde über Runtime Fehler einiges Google (und dieses Forum), aber nichts brauchbares. Eine Neuinstallation hat leider auch nichts gebracht. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Framework issue.
I can agree to the problem. The other way: opening a OOo-document with OOo installed on a Win98SE-machine by doubleklicking via windows-explorer on a network-resource XP-machine works as desired by mapped networkresource and by UNC-path.
probably duplicate to issue 60329
Plenty of other people getting this error, myself included. See http://www.oooforum.org/forum/viewtopic.phtml?p=127891#127891 . Contact me for additonal info if required. My set up is basically WinXp SP2 with new install of OOo 2.0.1 trying to launch network files (using double-click) hosted by Win98 machine.
*** Issue 61724 has been confirmed by votes. ***
*** Issue 62178 has been marked as a duplicate of this issue. ***
adding aswebdesign to CC.
*** Issue 60329 has been marked as a duplicate of this issue. ***
This problem was covered by issue 51026 (that is fixed (?) now). Hwoarang
*** Issue 59684 has been marked as a duplicate of this issue. ***
Workaround for this issue: Drag the file for opening from network folder (win 98 server) to an open firefox window. Confirm the opening window. File will be opened with OO2. Regards Dieter Bauckmeier
Issue 51026 was closed with the following comment by andreschnabel: "verified with OOo 2.0.1 final on win98 -> close" But I cannot confirm, that is fixed as I started this issue with the above mentioned system. The workaround from rainerbielefeld: "here is a workaround (at least for WIN networks) that solves the problem. I did several successful tests after I established a "Net drive assembly" ((?) from german: "Netzlaufwerk") on the WIN 98 PC, so we can reduce priority" does also not work for me as I mentioned in my issue description. The only workaround I found was the same defined in issue 59684 by hgnet. "Another work-around is to place a shortcut pointing to "C:\Programme\OpenOffice\program\soffice.exe -o" into the sendto folder!" I created by myself also a batchfile for the "SendTo" menu and start a document with this option.
Using OOo dialogs is another workaround. Hwoarang
TM-MAV: Please have a look, Thanks !
Hello, sorry, but I would like to know, if there are any news on this issue? Thanks a lot and best regards Ranki
Changing the target.
Can not reproduce the problem in our environment. I have tried to open documents placed on Win98 machine using double-klick in Windows Explorer from two different WinXP machines ( both are WinXP SP2, with the latest patches from MS ) and everything worked like a charm. So it should be an environment-dependent problem. In one of duplicate issues it was mentioned that the scenario works well on WinXP SP1 machine. So the problem might be caused by SP2, and might be solved by the latest patches. But it is only a guess. It would be nice if somebody who owns an affected WinXP SP2 machine installed all the latests patches and tried the scenario again.
MAV->HRO: The problem seems to happen before the SVMain is called ( the debug printing in this method seems not to be reached ). Could you please take a look.
Sorry. It looks like I have introduced incompatibility in one of the libraries. Taking the bug back for further investigation.
Hallo, I have some PC with OS Win NT/Win 2000 and OOo 2.0.3 installed, connected to a Win NT 4.0 server (the network file server). I can't open OOo-document using UNC path (in task manager I see soffice starting and then crashing without error messages) from another application. The same error double-clicking the file on Windows Explorer on a network resource. If I map the network resource on a drive, it works. Unfortunately I must use the UNC path, because of different environment configuration on the PCs connected to the file server. Error in OOo configuration or bug not resolved in 2.0.3 version? Thank you in advance
@mickey69 What you are talking about seems to be a seperate issue. Please see issue 19287.
according to release status meeting -> target 3.x
Reset the assignee to the default "issues@openoffice.apache.org".