David Jensen
Guest
|
 Posted:
Wed Jan 12, 2005 5:08 am Post subject:
Getting a "read only" message when I shouldn't be |
|
|
In setting up a new server, I populated it with our data by restoring a
backup from another server onto this new server using V2i protector. I
assume that it was becuase of this method of loading data onto the new
drives that every file and folder was showing up as "read only". I have
unchecked the "read only" attribute on the root of the drive and told it to
propogate down to all files and folders. I thought that would solve the
problme. However, I'm having the following behavior:
When ever I try to open an Access mdb file from the server console, it now
opens fine. When I try to do do with the same administrative logon from a
client PC accessing the same file off of the server it continues to tell me
that the file is "read only" and will not allow me to modify records in the
db. Oddly, when I tried accessing the server via Terminal Services with the
same administrative logon, it wouldn't let me. When I tried TS using a
different user that doesn't have administrative access, they can open the
mdb file without it being read only. Strange. I can open Word and Excel and
text documents without any problem. The only problem seems to be in Access.
I am running windows 2003 server and XP on the client. I have not yet
installed the Windows or TS CALS. Don't know if that makes difference here.
For some reason all the folders still show up as a grayed (but not ghosted)
"read only" still, even though the files in the folders do not.
The cross posting is because I don't know if this is a server problem,
Access problem, or a Terminal Services problem. If you could show me how to
stop getting this read only message, I would be forever grateful. I don't
know what else to try on my own.
David Jensen
--
David Jensen
Replace the xx in my E-mail address with "Team" for my real E-mail address |
|
Tom Wickerath
Guest
|
| Posted:
Wed Jan 12, 2005 6:27 am Post subject:
Re: Getting a "read only" message when I shouldn't be |
|
|
David,
| Quote: | For some reason all the folders still show up as a grayed (but not
ghosted) "read only" still, even though the files in the folders do not.
|
Each user must have RWCD privleges for the folder, in order for the locking database file (*.LDB)
to be created & managed properly.
Suggest you read the following KB article:
Introduction to .ldb files
http://support.microsoft.com/?id=299373
Tom
__________________________________
"David Jensen" <djnews1@xxhealthcare.com> wrote in message
news:W%YEd.4029$KJ2.2319@newsread3.news.atl.earthlink.net...
In setting up a new server, I populated it with our data by restoring a
backup from another server onto this new server using V2i protector. I
assume that it was becuase of this method of loading data onto the new
drives that every file and folder was showing up as "read only". I have
unchecked the "read only" attribute on the root of the drive and told it to
propogate down to all files and folders. I thought that would solve the
problme. However, I'm having the following behavior:
When ever I try to open an Access mdb file from the server console, it now
opens fine. When I try to do do with the same administrative logon from a
client PC accessing the same file off of the server it continues to tell me
that the file is "read only" and will not allow me to modify records in the
db. Oddly, when I tried accessing the server via Terminal Services with the
same administrative logon, it wouldn't let me. When I tried TS using a
different user that doesn't have administrative access, they can open the
mdb file without it being read only. Strange. I can open Word and Excel and
text documents without any problem. The only problem seems to be in Access.
I am running windows 2003 server and XP on the client. I have not yet
installed the Windows or TS CALS. Don't know if that makes difference here.
For some reason all the folders still show up as a grayed (but not ghosted)
"read only" still, even though the files in the folders do not.
The cross posting is because I don't know if this is a server problem,
Access problem, or a Terminal Services problem. If you could show me how to
stop getting this read only message, I would be forever grateful. I don't
know what else to try on my own.
David Jensen
--
David Jensen
Replace the xx in my E-mail address with "Team" for my real E-mail address |
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in