Word docs open as Read-Only from Vista clients

[John]

Hi
I have a windows server 2003 standard edition with some Vista Ultimate
clients. From those clients we open and edit documents placed in the server
2003. When I double click a Word document sometimes opens as “read-onlyâ€.
This means that I have always to save the document with a different name in
order to make changes. I notice that if I close the read only doc and double
click on it again, opens with not the read only property. As I mention above
all this happens sometimes. Perhaps a documents which opens normally today,
tomorrow open as read only. Those docs were created with Word 2003 in XP
clients. Now we also use Word 2003 but in Vista Ultimate clients. Any help?

Thanks a lot!

 

[Alias says BAAAAAAAAAA]

Hi
I have a windows server 2003 standard edition with some Vista Ultimate
clients. From those clients we open and edit documents placed in the
server
2003. When I double click a Word document sometimes opens as "read-only".
This means that I have always to save the document with a different name
in
order to make changes. I notice that if I close the read only doc and
double
click on it again, opens with not the read only property. As I mention
above
all this happens sometimes. Perhaps a documents which opens normally
today,
tomorrow open as read only. Those docs were created with Word 2003 in XP
clients. Now we also use Word 2003 but in Vista Ultimate clients. Any
help?

Thanks a lot!

Open the file (hopefully as read only) and then open Computer Management -
connect to your server. Go to System Tools - Shared Folders - Open Files.
Look for your User ID and the file. Does it show it as being locked?

 

[Terry R.]

The date and time was 9/24/2008 4:40 AM, and on a whim, John pounded out

Hi
I have a windows server 2003 standard edition with some Vista Ultimate
clients. From those clients we open and edit documents placed in the server
2003. When I double click a Word document sometimes opens as “read-onlyâ€.
This means that I have always to save the document with a different name in
order to make changes. I notice that if I close the read only doc and double
click on it again, opens with not the read only property. As I mention above
all this happens sometimes. Perhaps a documents which opens normally today,
tomorrow open as read only. Those docs were created with Word 2003 in XP
clients. Now we also use Word 2003 but in Vista Ultimate clients. Any help?

Thanks a lot!

Hi John,

Are these shared folders on the network? Could by chance someone have
the same document open at the same time?

If they are private folders, do the users have full permissions in them?

If the documents are on the workstation locally, does it ever happen?
--
Terry R.

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.

 

[John]

The date and time was 9/24/2008 4:40 AM, and on a whim, John pounded out


Hi John,

Are these shared folders on the network? Could by chance someone have
the same document open at the same time?

If they are private folders, do the users have full permissions in them?

If the documents are on the workstation locally, does it ever happen?
--
Terry R.

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.

Hi
Here are the answers

Are these shared folders on the network?

Their physical location is on drive D of server.

Could by chance someone have the same document open at the same time?

No! We have checked this case!

If they are private folders, do the users have full permissions in them?

The problem regards documents placed in folders which are not private. In
those folders have access a lot of employees and we have set full access
permissions for all of them. With the previous PCs (windows xp) we didn’t
face this problem.

If the documents are on the workstation locally, does it ever happen?

We don’t notice something wrong. But I am not 100% sure because this problem
happens randomly!

At the end, to mention again that when I re-open a document with the read
only property opens without this property.

Thanks!

 

[Terry R.]

The date and time was 9/25/2008 4:16 AM, and on a whim, John pounded out

Hi
Here are the answers
Their physical location is on drive D of server.

Drive D? Is this a domain or just a workgroup?

No! We have checked this case!

The problem regards documents placed in folders which are not private. In
those folders have access a lot of employees and we have set full access
permissions for all of them. With the previous PCs (windows xp) we didn’t
face this problem.

So the only difference is the OS, correct? Everyone is using MSO2003.

We don’t notice something wrong. But I am not 100% sure because this problem
happens randomly!

It would be nice to test this. Work locally with a known problematic
file and find out if it's strictly related to the server.

At the end, to mention again that when I re-open a document with the read
only property opens without this property.

Thanks!

Does this happen only to files that are existing and have been edited
over and over, or does it happen to newly created files also?

--
Terry R.

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.

 

[John]

Hi

Drive D? Is this a domain or just a workgroup?

On server we have created a domain (Active Directory). Vista clients are
members of this domain.

So the only difference is the OS, correct? Everyone is using MSO2003.

Yes! the only difference is the OS, everyone use MSO2003

It would be nice to test this. Work locally with a known problematic file and find out if it's strictly related to the server.

I believe this problem is related to the server. We don’t notice something
wrong when we work locally. Its little difficult to test this because the
problem happens randomly. There are not docs which have this problem all the
time.

Does this happen only to files that are existing and have been edited over and over, or does it happen to newly created files also?

Yes this happen only to files that are existing and have been edited over
and over. We don’t notice any problem with newly crated files.

Thanks a lot!

 

[Terry R.]

The date and time was 9/26/2008 2:56 AM, and on a whim, John pounded out

Hi

On server we have created a domain (Active Directory). Vista clients are
members of this domain.

Yes! the only difference is the OS, everyone use MSO2003

I believe this problem is related to the server. We don’t notice something
wrong when we work locally. Its little difficult to test this because the
problem happens randomly. There are not docs which have this problem all the
time.

Yes this happen only to files that are existing and have been edited over
and over. We don’t notice any problem with newly crated files.

Thanks a lot!

Then it sounds like there might be some header info in the file that
might be causing it. Try copying the info in a problematic file and
pasting it into a new file and saving. Test open the new file
repeatedly. Report back.

--
Terry R.

***Reply Note***
Anti-spam measures are included in my email address.
Delete NOSPAM from the email address after clicking Reply.

 

[Charlie Tame]

The date and time was 9/26/2008 2:56 AM, and on a whim, John pounded out


Then it sounds like there might be some header info in the file that
might be causing it. Try copying the info in a problematic file and
pasting it into a new file and saving. Test open the new file
repeatedly. Report back.

Just a thought at random, could this be something to do with the
timestamp on the files, for example are the machines' clocks running in
sync? I seem to recall reading somewhere that Vista is pretty sensitive
to time settings.