Re: User unable to open Word Document on Network
From: Happy Heart (Happy.Heart@verizon.net)
Date: 09/26/02
- Next message: Mike Klick: "3rd Party VPN Router and Windows 2000 VPN."
- Previous message: Joe Cave: "failure audit - directory service acces - event id 565"
- In reply to: Jeff: "Re: User unable to open Word Document on Network"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Happy Heart <Happy.Heart@verizon.net> Date: Thu, 26 Sep 2002 01:10:10 GMT
Are there any groups that are "deny access" on this folder?
If there are, and this user is a member of that group, he/she will be
denied access, regardless of any other explicit permissions you may
assign them.
Is this share on a server, or workstation? Workstations have a limit
of 10 consecutive connections. Servers have a limit of however many
client access licenses you tell them you own. We've had some pretty
bazar behaviour when we reinstalled a server and forgot to enter the
licenses into license manager. It reached the 5 (or whatever we
initially entered) and stopped accepting connections. Of course it
issued strange messages that had nothing to do with the actual
problem.
What operating system is the user working on? I've also experienced
problems if the document has a character in the name that the
Microsoft world considers illegal. For instance, if the documents are
created from a Macintosh, and the user encountering problems is
working on a Win9x machine. A windows NT machine will show the name,
but show a " |" symbol at the problem character. The message you are
getting sounds like the machine can not follow the path to the file,
or can not read the file name correctly.
Another thing I would try, if none of the above apply, is to force all
NTFS permissions to be reapplied to the folder. Sometimes the
permissions just get messed up and the only way to fix them is to
manually reapply them. Also make sure you apply them from the
machine. We have a mix of Win2k servers and Win NT4 servers. The
permissions are not fully compatible across the two platforms! I've
had to remotely mount drives onto the NT4 domain controller, and apply
the permissions from the 4.0 machine in order to make everything work
correctly.
Hope something here helps!
On Fri, 20 Sep 2002 06:15:28 -0700, "Jeff"
<pvtpilotjeff@earthlink.net> wrote:
>That's not the case here since the other users with the
>same permissions to this folder can open the Word
>Documents okay....thx though. I'm at a loss. I've even
>created a group and just added the one user that I'm
>having problems with and then added the group to the
>folder with the same permissions as the rest of the 4
>users. This still didn't work.
>>-----Original Message-----
>>
>>"Jeff" <pvtpilotjeff@earthlink.net> wrote in message
>>news:254a01c25f49$6cafff40$35ef2ecf@TKMSFTNGXA11...
>>> I'm at a loss. 5 users have the same
>rights/permissions
>>> to a network folder where MS Word files reside. All
>but
>>> one can open the files. I've double-checked all the
>>> permissions and they're identical. I've even gone as
>far
>>> as uninstalling Word and reinstalling it. Also, I've
>>> deleted and added the user to the network all over
>>> again. I thought maybe it's a workstation issue, but
>if
>>> the user logs in as one of the other 4, she gets in
>>> fine. I've triple checked permissions. This folder
>>> isn't shared, but I thought maybe if I shared it it
>might
>>> work, but I had the same problem. Please, can tell me
>>> what might be wrong or what I overlooked? When the
>user
>>> opens Word and clicks on File...Open and selects the
>>> network drive and folder, she gets the following msg
>and
>>> trying to open any of the Word documents.....
>>> "Word cannot open the document. Try one or more of the
>>> following: On the file menue, click Open to open the
>>> document. Make sure the document has a .DOC
>extention."
>>> I've already verified all of these. I've also had the
>>> user try logging onto another pc and she gets the same
>>> problem, but the other 4 users don't.
>>
>>
>>This is a shot in the dark, but i'd try putting the
>folder options on all
>>the computers to not hide extensions of known file
>types. That may or may
>>not be why you get that error message.
>>
>>
>>.
>>
- Next message: Mike Klick: "3rd Party VPN Router and Windows 2000 VPN."
- Previous message: Joe Cave: "failure audit - directory service acces - event id 565"
- In reply to: Jeff: "Re: User unable to open Word Document on Network"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|