Issue 19287 - Network file access fails (MS Office docs resident on NT4 server)
Summary: Network file access fails (MS Office docs resident on NT4 server)
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 RC3
Hardware: Other Windows 98
: P3 Trivial with 8 votes (vote)
Target Milestone: AOO Later
Assignee: thorsten.martens
QA Contact: issues@ui
: 20299 26653 51342 (view as issue list)
Depends on: 51026
  Show dependency tree
Reported: 2003-09-08 22:26 UTC by dhitson
Modified: 2008-06-01 09:52 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description dhitson 2003-09-08 22:26:14 UTC
Will not open a Word Document or Excel Workbook resident on a server (NT4) via 
either 1) Previously defined Windows shortcut, or 2) Browsing the network and 
opening the file outside of the application (either by double-clicking or by 
right-clicking and selecting "Open"). However, the file will open if the OO 
application is first opened and using OO's File/Open function to browse to the 
Comment 1 stefan.baltzer 2003-09-10 20:20:32 UTC
SBA: Changed:
 - Prio from P1 to P3 because the Office keeps up and running and 
there is a workaround available.

 - Component from "UI" to "Framework"

 - Subcomponent from "UI" to "Code"

 - Reassigned to Thorsten
Comment 2 stefan.baltzer 2003-09-10 20:23:00 UTC
SBA: Changed Summary from "Network file access" to "Network file 
access fails (MS Office docs resident on NT4 server)" to summarize 
the findings.
Comment 3 thorsten.martens 2003-12-12 09:23:50 UTC
I will check this together with JSK. Target is set to OO later due to the fact
that OOo can open the files via it´s own file-open dialog. This looks like some
kind of system-integration problem with NT4 servers.
Comment 4 thorsten.martens 2003-12-12 12:51:12 UTC
*** Issue 20299 has been marked as a duplicate of this issue. ***
Comment 5 lohmaier 2004-05-02 12:41:53 UTC
*** Issue 26653 has been marked as a duplicate of this issue. ***
Comment 6 nrs298 2004-05-05 09:27:04 UTC

Have the same problem but on a Linux server (Redhat) accessed via Windows XP.
Can only open files from inside OO; double-clicking and right-click -> open
doesn't work.

Comment 7 thorsten.martens 2004-06-15 08:54:23 UTC
Please check problem with a more recent build like OOo 1.2RC3. There has been a
problem while trying to access files on non mapped devices (like opening files
via network neighbourhood). Otherwise map a device constantly with a drive
letter and open files from this device that should work. Problem has already
been fixed.
Comment 8 rftg 2005-06-29 09:37:05 UTC
Hi! I do have the same problem in my office. (I tried to migrate our whole
office, 35 WS, to OO but failed at this point)

This problem occurs in all OO Versions - up to 1.1.4 and even the new 2.0 beta.
Not only ms-docs are affectet - all documents are affectet.

Using double-click on document at mapped network-drive works fine.
Using double-click on document at \\unc\path doesnt work

Server is NT 4.0, on all Workstations XP, 2000, NT4WS the double click doesnt
work on unc.

For office-Users and migrating admins the problem is more than p3. I suggest an
update to p2.

Perhaps Issue 51346 have something relating to do with this problem, too?
Comment 9 Rainer Bielefeld 2005-07-10 13:51:10 UTC
related to issue 51026?
Comment 10 atdsm 2006-12-06 16:17:42 UTC
*** Issue 51342 has been marked as a duplicate of this issue. ***
Comment 11 atdsm 2006-12-06 16:25:02 UTC
For what it's worth, I'll repost my comment from 51342:

Functionality of double clicking on a file in \\unc\path works fine when the
server is a Samba server (3.0.20b). However, after some playing around, I later
copied the exact same file to another server on our network (which I believe is
a Windows NT server of some flavor) and experienced the problem described (OOo
fails to open).

Which is to say, it seems to be specifically related to Windows servers only;
Samba servers do not trigger this bug.
Comment 12 Mechtilde 2008-06-01 09:51:23 UTC
Comment 13 Mechtilde 2008-06-01 09:52:28 UTC