Publisher 2.0: Sharing Violation When Running Network Version
Publisher 2.0: Sharing Violation When Running Network Version
Q109458
---------------------------------------------------------------------
The information in this article applies to:
- Microsoft Publisher for Windows, version 2.0
---------------------------------------------------------------------
SYMPTOMS
========
If you are running a shared (network) version of Publisher, you may
receive the following error when you try to run Publisher
Sharing violation reading drive x:
Could not open {filename}.
where drive x: is the shared Windows or Publisher drive. Sometimes
the error specifies a filename such as OLE2.DLL. Sometimes it does
not. The first user to run Publisher will not receive the error, but
the second and subsequent users will.
CAUSE
=====
The error occurs when some of the Publisher files, or Windows files
required by Publisher, are not marked read-only. This usually
happens on networks such as the Lantastic network, where file
protection is set file-by-file instead of directory-by-directory.
This error can also occur on a network that previously ran Publisher
successfully if a new workstation is set up.
RESOLUTION
==========
Ensure that all files in the shared Publisher AND the shared
Windows directory are marked read-only.
IMPORTANT: If you are setting up several workstations using the SETUP /N
command and you are running a shared (networked) copy of Windows, set up
all the workstations first and then set the read-only protection. This is
important because each time you run SETUP /N, Publisher writes new copies
of the essential Windows files (DLLs) to the shared Windows directory. On
some networks (for example, Lantastic) this resets the file protection to
Read-Write. If you later set up a new workstation to run Publisher, the
error may occur again for the same reason.
Additional query words: networked
