MS Word XP Document Becomes Read Only While Open

[chemikalguy]

I have a user (User A) reporting that after he opens a file and edits it, periodically saving it, that it becomes 'read only' and will no longer take the changes without him saving it with a different file name.

The file is on a network and is shared by multiple users. Apparently, User B opens the file while user A has it open and received the message that "User A has the file opened - do you wish to open a read only copy". User B does, but the file becomes 'read only' for User A as well. I'm not sure if the file becomes 'read only' at the moment that User B opens it, but I thought I'd mention it.

Any thoughts?

Thanks!

 

[xlhelp]

Your network connection may be getting dropped after a period of inactivity.

Please look at article 297684 at microsoft.com

Member- AAAA Association Against Acronym Abusers

 

[chemikalguy]

I thought this might be the issue, but I checked the event log and found the error "TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts". Could this be part of the issue? I worked on the document at the user's desk myself, and saw the exact same thing happen while I worked on it. Something else that's happening now is that it won't even let the user save it as a different name, it tells him that it's unable to save because the document is 'read only'.

 

[xlhelp]

If you are getting that error, there should be a link alos that points you somewhere. You are probably conflicting with another app like Bit Torrent or such.

Look at

http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2net...

under "Limited number of simultaneous incomplete
outbound TCP connection attempts" section



Member- AAAA Association Against Acronym Abusers

 

[chemikalguy]

I read about the issues with P2P software a while back because another user was having trouble with a different program. We run a pretty tight ship, and users can't install software on their workstations, so I know that P2P isn't to blame. I'll have to do some more digging to get to the bottom of it.