Apache OpenOffice (AOO) Bugzilla – Issue 5149
Cannot open files with UNC
Last modified: 2005-10-31 10:14:28 UTC
Hi There, I have noticed that if you try to open a file using the UNC convention (\\servername\ressource) it does not work. That can be a problem when for example the MY DOCUMENTS is re-routed to a server share. Thanks, and keep up the good work, OpenOffice is the best Product i've seen so far... ;) Christian Francoeur Network Administrator - Doubletex
DL->SBA: Would you please check this in your team?
Component changed to Framework. Reassigned to Thorsten.
TM->FT: Due to the fact, that our own file.open dialog can`t handle UNC-filenames but the systems dialog can, this feature should be implemented as soon as possible.
Hi Have just started using OpenOffice.org and very impressed, but this problem is a show-stopper for many corporates using Windows networking as lots of users tend to 'browse the network' to the file to open rather than open it via a mapped drive letter. Cheers Peter
This is *definitely* a showstopper in a networked Windows environment, and should be given a high priority!
In Windows 2000, I experienced a problem not with loading a document (a spreadsheet, it was) from a UNC path, but with saving it back. I'm going to research the issue a bit more though, since I have the impression it does work at home where it didn't at work.
I cannot confirm this. Using the following enviroment: Windows 2000 Server (server) Windows 2000 Professional, SP 2 (workstation) with a simple 'user', no admin-rights on the server. Opening and saving a openoffice.org writer documents via UNC \\servername\directory\file.sxw. I tested this with 1.0.0 and 1.0.1 (rc build). Can you add more details about your enviroment? What about your access rights on the server?
Windows 2000 Pro desktop, NT4 file server, NT domain, regular user. Accessing the user's home directory via My Computer going to a mapped drive letter (H:) the user is able to double-click to open files and may save files without problems in the app dialogs. Going via My Network Places (a.k.a. Network Neighborhood) to the same location (e.g. \\server\users_home\) and double-clicking on the document saved via the mapped drive letter opens an empty OO window (the app starts, but apparently cannot open the document). No error message is displayed. Opening the file via the mapped drive letter and choosing Save As..., then navigating via Network Neighborhood to the same location results in an error dialog: Error saving the document whatevername.doc Wrong Parameter The operation was started under an invalid parameter
*** Issue 5696 has been marked as a duplicate of this issue. ***
*** Issue 6271 has been marked as a duplicate of this issue. ***
*** Issue 6377 has been marked as a duplicate of this issue. ***
*** Issue 5557 has been marked as a duplicate of this issue. ***
*** Issue 5803 has been marked as a duplicate of this issue. ***
*** Issue 5853 has been marked as a duplicate of this issue. ***
*** Issue 5169 has been marked as a duplicate of this issue. ***
*** Issue 6144 has been marked as a duplicate of this issue. ***
*** Issue 6063 has been marked as a duplicate of this issue. ***
Hello all. I've marked a bunch of issues as duplicate of this issue. I've read the other issues and here's the general pattern that has been noted by the users. If the drive is first mapped as a drive letter in Windows, opening and saving files to the shared drive is successful. If the drive is accessed using an UNC path ( \\server name\path ), opening and saving files to the shared drive is unsuccessful.
*** Issue 6481 has been marked as a duplicate of this issue. ***
Update from one of the users. Hi, version 1.0.1 solved problems with UNC names in the format \\server\folder\text.doc, but i still have problems with the format \\svr_name\folder\text.doc caused by the undeline caracter in the computer name. Other Office applications run OK under same conditions, even StarOffice 5.2. Thanks a lot, Amilcar
I have installed 1.0.1, and still have the problem, with or without underscores in the UNC name. Cheers, Peter
*** Issue 4945 has been marked as a duplicate of this issue. ***
*** Issue 7898 has been marked as a duplicate of this issue. ***
Updated QA Contact from issues@l10n.openoffice.org to issues@framework.openoffice.org
We have 1.0.1 deployed since September 2002, and I believe we have a related issue with OOo hanging, and stopping Windows 2000 users from logging out. The only way to fix is to kill the process with Task Manager. As others have suggested, UNC support is important for us corporates - is there a possibility of targeting 1.1 beta with this?
Hi Stefan, from what I see this issues has been solved in the meantime. Can you please verify this? Thx
ES->TM: please check this.
I also cannot open a document in version 1.0.2 when there are spaces in the computer name, for example: \\dell server\VOL1\document.doc I can open documents if the network is mounted to a drive letter or there is no space in the network name.
Problem has been fixed by accepting several special characters in the servers name of an UNC path (like _). A space in the servers name isn´t accepted as a valid character further on (referring to Microsoft NetBIOS Computer Naming Conventions where a blank in a servers name is an invalid character too. See -> http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q188997&
Verified in OOo 1.1 Beta2.
closed ...
*** Issue 13828 has been marked as a duplicate of this issue. ***
*** Issue 9910 has been marked as a duplicate of this issue. ***
I get a general I/O-error when trying to open any file on any network share in OpenOffice 2.0rc3 on MacOS X 10.4.2, fileserver is a local Linux 2.6.12-box with Samba 3.0.20b. Should I open a new bug or can you reopen this one?