All Files Read Only in All Document Libraries

I had a few users complain that their files are all set to Read Only.
I checked into it further and it seems that every file in every
document library is now Read Only.

If I create a new document, and upload that to the server and then try
and edit it, it is Read Only. I cannot replace a file when I save it
or I get the "This file is Read Only" message. I can save it as a
different name, and then try to edit that new file and now that file is
Read Only as well.

I have searched around and haven't found any solutions but a few people
with similar problems and no answers. A point in the right direction
or any ideas would be greatly appreciated!

Thanks in Advance!

Matt

Matthew
Fri Oct 28 20:22:30 CDT 2005

I think this happens because you have content approval turned on.
Click modify columns and settings on the document library, then turn
off content approval.

Cheers,

--
Matthew Cosier
http://workspaces.gotdotnet.com/SAST
http://workspaces.gotdotnet.com/ReGhost

Shane
Sat Oct 29 15:28:12 CDT 2005

Have you tried, checking out the document, then clicking on the document
drop down box and choosing "edit in Microsoft word"?

--
Shane Young - Now with MVP power
SharePoint911 - "SharePoint Help...Now!"
http://www.SharePoint911.com


"The_Captain" <mattrouse@gmail.com> wrote in message
news:1130540788.922175.276110@g14g2000cwa.googlegroups.com...
>I had a few users complain that their files are all set to Read Only.
> I checked into it further and it seems that every file in every
> document library is now Read Only.
>
> If I create a new document, and upload that to the server and then try
> and edit it, it is Read Only. I cannot replace a file when I save it
> or I get the "This file is Read Only" message. I can save it as a
> different name, and then try to edit that new file and now that file is
> Read Only as well.
>
> I have searched around and haven't found any solutions but a few people
> with similar problems and no answers. A point in the right direction
> or any ideas would be greatly appreciated!
>
> Thanks in Advance!
>
> Matt
>

The_Captain
Mon Oct 31 12:09:44 CST 2005

I had already tried this and I checked into the content approval
settings and they had no effect and were already turned off in most
libraries except where needed.

My problem is that every document in ALL LIBRARIES are now read only.

My server has roughly 850 users on my Sharepoint Portal, more then 50
areas containing about 100 libraries. It is running on an up to date
IBM eServer, Windows 2003. It is on a domain, internal only (no
outside world access except for updates to anti-virus and winodws
updates), the SQL server and backups are on a drive that is a simulated
hard drive using fiber-card to an IBM San.

The_Captain
Mon Nov 07 14:33:59 CST 2005

I've been working with MS Pay-per-incident support. Looks like we have
narrowed this down to corruption in the SITE SQL Database. They have
my DBs now and are looking through those and the SQL traces to track
down the corruption. I'll let you know when I find out what it was.

Christine
Thu Nov 10 11:25:06 CST 2005

Hi-- just fyi-- we have had the same "read only" situation since we installed
and started using Sharepoint-- we just live with it-- it isn't that big of a
hassle and stops a lot of people from accidently changing files...

"The_Captain" wrote:

> I had a few users complain that their files are all set to Read Only.
> I checked into it further and it seems that every file in every
> document library is now Read Only.
>
> If I create a new document, and upload that to the server and then try
> and edit it, it is Read Only. I cannot replace a file when I save it
> or I get the "This file is Read Only" message. I can save it as a
> different name, and then try to edit that new file and now that file is
> Read Only as well.
>
> I have searched around and haven't found any solutions but a few people
> with similar problems and no answers. A point in the right direction
> or any ideas would be greatly appreciated!
>
> Thanks in Advance!
>
> Matt
>
>

TheCaptain
Fri Dec 09 15:02:02 CST 2005

I found the solution myself even after many hours on the phone with
Microsoft. I reinstalled everything, restored and had the same problem, but
it dissappeared when I re-instealled SP2 for WSS. Hopefully this will help
the few souls out there who, like I was, were frustrated with a re-producable
problem but no solutions to be found anywhere.

--
I just slack here.


"The_Captain" wrote:

> I've been working with MS Pay-per-incident support. Looks like we have
> narrowed this down to corruption in the SITE SQL Database. They have
> my DBs now and are looking through those and the SQL traces to track
> down the corruption. I'll let you know when I find out what it was.
>
>

Swippe
Tue Dec 27 06:41:02 CST 2005

I have a customer who has upgraded its WSS to SP2, after that they lost the
choice to create a new document from a template. If I reinstall this SP2,
could this maybe solve this problem!?

"The_Captain" wrote:

> I found the solution myself even after many hours on the phone with
> Microsoft. I reinstalled everything, restored and had the same problem, but
> it dissappeared when I re-instealled SP2 for WSS. Hopefully this will help
> the few souls out there who, like I was, were frustrated with a re-producable
> problem but no solutions to be found anywhere.
>
> --
> I just slack here.
>
>
> "The_Captain" wrote:
>
> > I've been working with MS Pay-per-incident support. Looks like we have
> > narrowed this down to corruption in the SITE SQL Database. They have
> > my DBs now and are looking through those and the SQL traces to track
> > down the corruption. I'll let you know when I find out what it was.
> >
> >

Shane
Tue Dec 27 11:35:26 CST 2005

Try this http://msmvps.com/blogs/shane/archive/2005/11/02/74038.aspx

--
Shane Young - SPS MVP
SharePoint911 - http://www.SharePoint911.com
Blog - http://msmvps.com/shane/



"Swippe" <Swippe@discussions.microsoft.com> wrote in message
news:38C9A449-4686-4BDA-964D-AAD45CE7FC1B@microsoft.com...
>I have a customer who has upgraded its WSS to SP2, after that they lost the
> choice to create a new document from a template. If I reinstall this SP2,
> could this maybe solve this problem!?
>
> "The_Captain" wrote:
>
>> I found the solution myself even after many hours on the phone with
>> Microsoft. I reinstalled everything, restored and had the same problem,
>> but
>> it dissappeared when I re-instealled SP2 for WSS. Hopefully this will
>> help
>> the few souls out there who, like I was, were frustrated with a
>> re-producable
>> problem but no solutions to be found anywhere.
>>
>> --
>> I just slack here.
>>
>>
>> "The_Captain" wrote:
>>
>> > I've been working with MS Pay-per-incident support. Looks like we have
>> > narrowed this down to corruption in the SITE SQL Database. They have
>> > my DBs now and are looking through those and the SQL traces to track
>> > down the corruption. I'll let you know when I find out what it was.
>> >
>> >

Swippe
Wed Dec 28 00:58:01 CST 2005

Thankyou, hopefully this will solve my problem. I will give a full report
when I solved the problem! :o)


"Shane Young [SPS MVP]" wrote:

> Try this http://msmvps.com/blogs/shane/archive/2005/11/02/74038.aspx
>
> --
> Shane Young - SPS MVP
> SharePoint911 - http://www.SharePoint911.com
> Blog - http://msmvps.com/shane/
>
>
>
> "Swippe" <Swippe@discussions.microsoft.com> wrote in message
> news:38C9A449-4686-4BDA-964D-AAD45CE7FC1B@microsoft.com...
> >I have a customer who has upgraded its WSS to SP2, after that they lost the
> > choice to create a new document from a template. If I reinstall this SP2,
> > could this maybe solve this problem!?
> >
> > "The_Captain" wrote:
> >
> >> I found the solution myself even after many hours on the phone with
> >> Microsoft. I reinstalled everything, restored and had the same problem,
> >> but
> >> it dissappeared when I re-instealled SP2 for WSS. Hopefully this will
> >> help
> >> the few souls out there who, like I was, were frustrated with a
> >> re-producable
> >> problem but no solutions to be found anywhere.
> >>
> >> --
> >> I just slack here.
> >>
> >>
> >> "The_Captain" wrote:
> >>
> >> > I've been working with MS Pay-per-incident support. Looks like we have
> >> > narrowed this down to corruption in the SITE SQL Database. They have
> >> > my DBs now and are looking through those and the SQL traces to track
> >> > down the corruption. I'll let you know when I find out what it was.
> >> >
> >> >
>
>
>