InDesign CS5 - preventing "Read Only" files?

Hi all,
We've always worked on a file server; and InDesign CS4 (and below) would lock any open files so only one person could access the document at a time. Now CS5 appears to let other other people view the INDDs as a read only file while others are working on it.
This allows people to open a live file, make changes and do a Save As. This is really bad for our workflow since we can't risk multiple people accessing a file at one time.
Is there anyway to disable this?
Thanks.

Thanks, Stix.
Updating the app fixed it. I tried searching for this answer on the forum first (as is protocol), but couldn't find the answer.
A co-worker found a similar thread/answer as well. I guess I need to fine tune my search skills.

Similar Messages

  • My Time machine has stopped backing up saying there are some read only files.

    My Time machine has stopped backing up and says that ther are some read only files preventing this. What steps do I need to take to fix it?

    If you have more than one user account, these instructions must be carried out as an administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.
    Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Post the messages timestamped from then until the end of the backup, or the end of the log if that's not clear.
    Post the log text, please, not a screenshot. If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into a message.
    Some personal information, such as the names of your files, may be included — edit that out, too, but don’t remove the context.

  • Solaris 10  - After installation read only file system

    Dear All,
    I have installed the Solaris 10 on my x86 system with out any problem. The installation was completed successfully. I have followed the installation instructions that are mentioned in the following link.
    http://docs.sun.com/app/docs/doc/817-0544/6mgbagb19?a=view
    I am facing a different problem. I am not able to create even a single file / sub-directory on any of the existing directories. It always says READ ONLY file system can not create firl / directory.
    Please help me how to resolve this issue.
    Thanks in advance.
    Regards,
    Srinivas G

    What do you get for 'svcs -xv' output?
    Darren

  • How to delete a READ ONLY file from Directory

    Hi Friends,
    how to delete a READ ONLY file from Directory , file is in my system only.
    Please help me .
    note: its read only file.
    Thank you.
    Karthik.

    hI,
    try with this statement.
    delete dataset <datasetname>.
    this will definitely work.
    Regards,
    Nagaraj

  • Read-only file access from network volume

    I get an read-only file access from network volume problem while sharing a drive from Snow Leopard to a Tiger install. Most of files were opening well, but *.fp7 (FileMaker) and *.xls (Excel) files won't open dealing with a read-only error.
    As descibed in the last post of http://discussions.apple.com/thread.jspa?threadID=1406977 the client have the same share name of the server. Renomming it resolved the error!
    Thanks!

    right then, as it looks like I'm talking to myself....
    I have just wiped clean the Macbook Pro.
    I installed Leopard from scratch, then installed Office 2008.
    Logged back onto the network share, and the read-only error came up again, ONLY in Excel.
    bugger.
    Did the same thing with my Macbook and all is fine.
    Copy the file to the local hard drive, opens ok.
    I then copied the file to another Mac on the network.
    mmmm, opens fine.
    what's the difference....
    mmmm, the machine it opens fine from is running 10.4
    the machine which hosts all the data is running 10.3.9
    could this be the problem.
    Just done a software update check on the 10.3 machine and there are some security updates that need doing.
    Going to run that now and see what happens, otherwise I think the iMac running 10.3.9 is going to need to come up to 10.4 and fingers crossed this will solve it.

  • Crashes and read-only file systems

    Notice: I apolgize for the long post, I've tried to be as thorough as possible.  I have searched everywhere for possible solutions, but things I've found end up being temporary workarounds or don't apply to my situation.  Any help, even as simple as, "have you checked out XYZ log, it's hidden here", would be greatly appreciated.  Thanks
    I'm not sure what exactly caused the issues below, but they did start to happen within a day of running pacman -Syu.  I hadn't run that since I first installed Arch on December 2nd of this year.
    Setup:
    Thinkpad 2436CTO
    UEFI/GPT
    SSD drive
    Partitions: UEFISYS, Boot, LVM
    The LVM is encrypted and is broken up as: /root, /var, /usr, /tmp, /home
    All LVM file systems are EXT4 (used to have /var and /tmp as ReiserFS)
    The first sign that something was wrong was gnome freezing.  Gnome would then crash and I'd get booted back to the shell with all filesystems mounted as read-only.  I started having the same issues as this OP:
    https://bbs.archlinux.org/viewtopic.php?id=150704
    At the time, I had /var and /tmp as ReiserFS, and would also get reiserfs_read_locked_inode errors.
    When shutting down (even during non-crashed sessions) I would notice this during shutdown:
    Failed unmounting /var
    Failed unmounting /usr
    Followed by a ton of these:
    device-mapper: remove ioctl on <my LVM group> failed: Device or resource busy
    Nother of these errors had ever appeared before.
    After hours of looking for solutions (and not finding any that worked) I was convinced (without any proof) that my Reiser file systems were corrupt and so I reformatted my entire SSD and started anew - not the Arch way, I know   I set all logical volumes as EXT4.
    After started anew, I noticed
    device-mapper: remove ioctl on LVM_SysGroup failed: Device or resource busy
    was still showing up, even with just a stock Arch setup (maybe even when powering off via Arch install ISO, don't remember).  After a lot of searching, I found that most people judged it a harmless error, so I ignored it and continued setting up Arch.
    I set up Gnome and a basic LAMP server, and everything seemed to work for a couple of hours.  Soon after, I got the same old issues back.  The System-journald issue came back and per the workaround on https://bbs.archlinux.org/viewtopic.php?id=150704 and a couple other places, I rotated the journals and stopped journald from saving to storage.  That seemed to stop THOSE errors from at least overwhelming the shell, but I would still get screen freezes, crashes, and read-only file systems.
    I had to force the laptop to power off, since poweroff/reboot/halt commands weren't working (would get errors regarding the filesystems mounted as read-only).
    I utilized all disk checking functions possible.  From running the tests (SMART test included) that came as part of my laptop's BIOS to full blown fsck.  All tests showed the drive was working fine, and Fsck would show everything was either clean, or
    Clearing orphaned inode ## (uid=89, gid=89, mode=0100600, size=###
    Free blocks count wrong (###, counted=###)
    Which I would opt to fix.  Nothing serious, though.
    I could safely boot back into Arch and use the system fine until the system decides to freeze/crash and do the above all over again.
    The sure way of recreating this for me is to run a cron job on a local site I'm developing. After a brief screen freeze (mouse still moveable but everything is otherwise unreponsive) I'll systemctl status mysqld.service and notice that mysqld went down.
    It seems that it's at this point my file systems are mounted as read only, as trying to do virtually anything results in:
    unable to open /var/db/sudo/...: Read-only file system
    After some time, X/Gnome crashes and I get sent back to shell with
    ERROR: file_stream_metrics.cc(37)
    RecordFileError() err = 30 source = 1 record = 0
    Server terminated successfully (0)
    Closing log file.or_delegate.h(30)] sqlite erro1, errno 0: SQL logic error or missing database[1157:1179
    rm: cannot remove '/tmp/serverauth.teuroEBhtl': Read-only file system
    Before all this happened, I was using Arch just fine for a few weeks.  I wiped the drives and started anew, and this still happens with just the minimal number of packages installed.
    I've searched for solutions to each individual problem, but come across a hack that doesn't solve anything (like turning off storing logs for journal), or the solution doesn't apply to my case.
    At this point, I'm so overwhelmed I'm not even sure where exactly to pick up figuring this issue out.
    Thanks in advance for any help

    Did this occur when you booted from the live/install media?
    What is your current set up? That is, partitions, filesystems etc. I take it you have not yet reinstalled X but are in the default CLI following installation?
    If turning off log storage didn't help, reenable it so that you may at least stand a chance of finding something useful.
    What services, if any, are you running? What non-default daemons etc.?
    Does it happen if you keep the machine off line?
    Have you done pacman -Syu since installation and dealt with any *.pacnew files?
    Last edited by cfr (2012-12-26 22:17:57)

  • How can I protect a PDF file to where when I am editing the file and another user opens the file, it is only a read-only file?

    I work for an auditing firm and we have recently gone paperless with our audit documentation. We have our files saved on a server and multiple people can access the same file at one time. We noticed that Acrobat does not give an message notifying a user that someone else is in that file, nor does Acrobat make that PDF file a read only file when someone else is in it editing the document. Is there a way to notify someone that another user is in the same PDF file? Or is there a way to make a PDF read only when someone else is working with the document?

    Hi ashleyr1936858
    You can restrict editing of a pdf by setting the password, such that anyone who wants to edit the pdf would need to input that password. This would make the pdf a read-only file.
    Here's a Link for more information : Acrobat Help | Securing PDFs with passwords
    Regards,
    Rahul

  • Java Does Not Throw Exception When Writing To Read-Only Files

    I have noticed that when I try to write to a read-only file in a window environment, Java does not throw an IOExcpetion, it just dosn't write to the file.
    I am writing an FTP server and here is the code:
         public static long copyStream(InputStream in, OutputStream out)throws IOException
              IOException exception = null;
              long copied = 0;
              try
                   byte buffer[] = new byte[1024];
                   int read;
                   while((read = in.read(buffer)) != -1)
                        out.write(buffer, 0, read);
                        copied += read;
              catch(IOException e)
                   //ensures that the streams are closed.
                   exception = e;
              try
                   in.close();//ensures output stream gets closed, even if there is an
                   //excption here.
              catch(IOException e){exception = e;}
              out.close();//try to close output.
              if(exception != null)
                   //exception is not null, an exception has occured.
                   //rethrow exception.
                   throw exception;
              return copied;//all ok, return bytes copied.
         }Is this a bug in JAVA VM? Is so, how should I report it?

    I have noticed that when I try to write to a read-only file in a window environment,
    Java does not throw an IOExcpetion, it just dosn't write to the file.C:\source\java\Markov>attrib readonly.out
    A R C:\source\java\Markov\readonly.out
    �C:\source\java\Markov>java b
    java.io.FileNotFoundException: readonly.out (Access is denied)
    at java.io.FileOutputStream.open(Native Method)
    at java.io.FileOutputStream.<init>(Unknown Source)
    at java.io.FileOutputStream.<init>(Unknown Source)
    at b.main(b.java:5)
    import java.io.*;
    public class b {
        public static void main(String[] args) {
         try     {
              OutputStream os = new FileOutputStream ( "readonly.out");
         catch (Exception e) {
              e.printStackTrace();
    }

  • (Read-only file system) ,EXT3-fs error (device sda6) in start_transaction, FOR MY MCS7825I3-K9-CMC1

    I got this problem for my cucm version System version: 7.0.2.20000-5
    Product Part Number: MCS7825I3-K9-CMC1
    java.io.FileNotFoundException: /var/log/active/platform/log/cli.bin (Read-only file system)
    log4j:ERROR No output stream or file set for the appender named [CLI_LOG].
    EXT3-fs error (device sda6) in start_transaction: Journal has aborted   SeverityMatch - Critical kernel: EXT3-fs error (device sda6) in start_transaction: Journal has aborted   SeverityMatch - Critical kernel: EXT3-fs error (device sda6) in
    Any Advice to solve this issue ?
    Kind Regards
    Mohammed khamis
    java.io.FileNotFoundException: /var/log/active/platform/log/cli.bin (Read-only file system)
            at java.io.RandomAccessFile.open(Native Method)
            at java.io.RandomAccessFile.<init>(RandomAccessFile.java:212)
            at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.restoreIndex(c                                                                            iscoRollingFileAppender.java:100)
            at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.setFile(ciscoR                                                                            ollingFileAppender.java:43)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.                                                                            java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces                                                                            sorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:585)
            at org.apache.log4j.config.PropertySetter.setProperty(PropertySetter.jav                                                                            a:196)
            at org.apache.log4j.config.PropertySetter.setProperty(PropertySetter.jav                                                                            a:155)
            at org.apache.log4j.xml.DOMConfigurator.setParameter(DOMConfigurator.jav                                                                            a:530)
            at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.ja                                                                            va:182)
            at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurat                                                                            or.java:140)
            at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfi                                                                            gurator.java:153)
            at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOM                                                                            Configurator.java:415)
            at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:3                                                                            84)
            at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:783)
            at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java                                                                            :666)
            at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java                                                                            :616)
            at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java                                                                            :584)
            at org.apache.log4j.xml.DOMConfigurator.configure(DOMConfigurator.java:6                                                                            87)
            at sdMain.main(sdMain.java:511)
    java.lang.NullPointerException
            at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.updateIndex(ci                                                                            scoRollingFileAppender.java:117)
            at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.nextFileName(c                                                                            iscoRollingFileAppender.java:92)
            at com.cisco.iptplatform.fappend.ciscoRollingFileAppender.append(ciscoRo                                                                            llingFileAppender.java:74)
            at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)
            at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders                                                                            (AppenderAttachableImpl.java:57)
            at org.apache.log4j.Category.callAppenders(Category.java:187)
            at org.apache.log4j.Category.forcedLog(Category.java:372)
            at org.apache.log4j.Category.info(Category.java:674)
            at sdMain.main(sdMain.java:525)
    log4j:ERROR No output stream or file set for the appender named [CLI_LOG].
       Welcome to the Platform Command Line Interface
    admin:java.io.FileNotFoundException: /var/log/active/platform/log/cli.bin (Read-only f                                                                            ile system):java.io.FileNotFoundException: /var/log/active/platform/log/cli.bin (Read-only f                                                                            ile system)

    Hello
    Thanks Manish .
    I found many articles in cisco which says that this error is related to the bug which need firmware upgrade , but I don't have support from cisco because EOS.
    https://supportforums.cisco.com/document/49511/updated-16-february-2011-ibm-7816-i4-782x-i4-filesystem-errors
    Solution
    The file-system going read-only issue which has recently been affecting server models MCS-7816-I4, MCS-7825-I4, and MCS-7828-I4 (or their IBM equivilants) in the field is addressed by CSCti52867 - "IBM 7816-I4 and 782x-I4 READONLY file system".
    The fix for CSCti52867 is now available and requires the application of two patch files.  Install both of these patch files in the order listed below.
    1. First install ciscocm.ibm-diskex-1.0.cop.sgn 
         The Readme file ciscocm.ibm-diskex-1.0.cop.sgn includes installation instructions for this .cop.sgn.
         Make sure to only install this utility when show hardware CLI output indicates the array is in a healthy state.
         If your server has never had the filesystem go readonly then this step is optional. 
    2. Next install Cisco-HDD-FWUpdate-3.0.1-I.ISO .
         The Readme file Cisco-HDD-FWUpdate-3.0.1-I.Readme.pdf includes installation instructions for this ISO.
         This installer is completely independant of the OS installed on the server.
    Note:  Installing the FWUpdate v3.0(1) or later will get you firmware with the fix for this defect.  It is always recommended that you apply the latest FWUCD available for your server.
    Refer to the Release Note of CSCti52867 and the Readme file for each of the above mentioned patch files for more details.
    Symptoms
    The file system goes READONLY, then CUCM services may go down, the server may become "unresponsive" meaning that it is not possible to ssh into the server, login to the console, or web into the server although it may still respond to pings.
    Traces from all services stop writing (including syslog)
    You see the following error on the server console
    EXT3-fs error (device sda6) in start_transaction: Jornal has aborted

  • How do I upgrade CS5 to read RAW files from my upgraded camera Canon 70D. It reads my 550D

    How do I upgrade Photoshop CS5 to read RAW files from my upgraded camera Canon 70D. It reads my 550D with no problem

    Photoshop CS6 will run ACR 8.7.
    Use the DNG converter: Adobe - Adobe Camera Raw and DNG Converter : For Windows : Adobe DNG Converter 8.7
    Adobe - Adobe Camera Raw and DNG Converter : For Macintosh : Adobe DNG Converter 8.7
    Benjamin

  • Can't write to pacman.conf -- Read only file

    Hello everybody,
    I'm a complete noob when it comes to installing (arch) linux. I just installed (a part of) arch linux to my old computer, but I'm stuck now.
    I used the Arch Linux beginners guide and now I'm at the part where I need to configure pacman.
    But once I'm trying to adjust something in pacman.conf the computer tells me it's a read only file.
    I also can't udate the system when I use pacman -Syu I get: error: failed to update core/extra/community (unable to lock database)
    Btw I installed syslinux and I'm logged in as root.
    I hope you can help me with this and that i'm not asking a really dumb question.
    Thanks in advance!

    Pimmmo wrote:
    I can only take pictures, because my arch linux is on an other computer.
    here is my fstab (btw it's read only as well)
    And here is my mount output
    That's not even the full /etc/fstab. It's horrible.
    Add a tmpfs like in the fstab wiki entry. It's probably because you used one ">" when using genfstab (my bad, sorry).
    https://wiki.archlinux.org/index.php/Fstab
    PS: Which bootloader do you use? Syslinux? Don't remove "ro" then. Keep it, just like in the examples.
    Last edited by DSpider (2012-09-18 13:22:25)

  • Cannot apply keywords/metadata to old pics - says "read only" files

    Hi, I'm new to Apple World. Got a new Intel iMac, latest version Leopard, Photoshop Elements 6 that came with Bridge. No problem working with new photos. But it will not let me apply new keywords or metadata to old pictures imported from disk because it says they are "read only." These old photos were copied to my Mac hard drive from DVDs that were incremental backups from my Photoshop Elements 4.0 catalog on my old Windows XP PC. They were all copied into folders that I named to correspond with the backup disks. Some of the keywords ("tags" on PC program) imported, but many didn't. So I'm going through the arduous task of manually inputting the data again. Tried it with a template first -- did let me add keywords. Then bringing up each picture individually it gives me the "can't apply metadata to read only files" message. I have hundreds of old photos in over 100 different categories (previously topical tags) to go through here. What is the solution? Please help! Thanks. Judy

    Judy
    can you be more specific about the 'Old Files'. Are they jpeg or tiff or something else. Do they have the proper extension jpeg: .jpg tiff: .tif etc..
    And I don't know what copy from Elements catalog means, do you have the actual original files copied or just previews or other files that were set there by elements in the catalog?
    Have you already checked if the files are not locked itself? select one in the finder, choose info and see if it is locked by itself ( there can also be a lock symbol in the bridge thumbnail that can be changed using Bridge menu.
    Last, not many visitors of this forum use Elements, have you already tried this question in the Elements forum itself??

  • Help with a fcpx library that is locked "could not be opened. Read-only file system"

    Hi all,
    I recently moved all my fcpx projects/events to a new Harddrive - I thought I did this correctly by copying/duplicating all projects/events from within FCPX.
    When I last used FCPX all the projects/events were there - no issues.  Also, when I look at package contents - everything is still there in terms of events and file sizes.  
    All the library files are on an external hard drive, on an encrypted disk image.  Now a week later I have tried to open FCPX and I get the following error
    "The document “MND_Z_FCPX” could not be opened. Read-only file system" and nothing will open.
    Have checked permissions - these all seem in order.  OSX is10.9.5 
    Any suggestions as to what might be the issue? 
    Thanks in advance.
    R

    the permissions themselves look ok - they have my two computer profiles as read/write.   I also note that on some occasions the library has opened in my other Computer profile, but not in the one that I want it to open.
    So I think you're right, there is something with permissions happening here.  I keep a work and personal computer profile.
    Don't know how it happened - but the volume is definitely Read Only - even though I've created a Read/Write permissions for it

  • Lightroom v1.0 Install Leaves Read-Only Files in Temp Directory

    I just installed v1.0 (fresh install, no previous betas, WinXP). There seem to be quite a few (20 to be exact) read-only files left in the folder:
    C:\Documents and Settings\**User**\Local Settings\Temp\
    These all appear to be related to Sonic Solutions (CD/DVD burning in LR?)
    i.e.
    pxhelp20.sys
    pxwave.dll
    pxmas.dll
    px.dll
    etc.
    Do these files serve any function after Lightroom is installed? Can they be safely deleted?

    you naming convention is confussing. you should follows Java naming convention..you have a getXXX but decalred the return type as "void"...get usully means to return something...
    your code is doing too much..and hard to follows..
    1. get the selected files
    for each selected file
    process the file and return the result
    write out the result.
    /** close the precious resource */
    public void closeResource(Reader in){
        if (in != null){
            try{ in.close(); }
            catch (Exception e){}
    /** get the total number of line in a file */
    public int getLineCount(File file) throws IOException{
        BufferedReader in = null;
        int lineCount = 0;
        try{
            in = new BufferedReader(new FileReader(file));
            while ((in.readLine() != null)
                lineCount++;
            return lineCount;
        finally{ closeResource (in);  }
    /** read the file */
    public void processFile(File inFile, File outFile) throws IOException{
        BufferedReader in = null;
        StringBuffer result = new StringBuffer();
        try{
            in = new BufferedReader(new FileReader(inFile));
            String line = null;
            while ((in.readLine() != null){
                .. do something with the line
                result.append(....);
            writeToFile(outFile, result.toString());
        finally{ closeResource (in);  }
    public void writeToFile(File outFile, String result) throws IOException{
        PrintWriter out = null;
        try{
            out = new PrintWriter(new FileWriter(outFile, true));  // true for appending to the end of the file
            out.println(result);
        finally{  if (out != null){ try{ out.close(); } catch (Exception e){} }  }
    }

  • [SOLVED] /bin/tar: Cannot utime: Read-only file system

    While doing a tar backup on my servers, I get this error:
    /bin/tar: /usr/local/bin/sendEmail: Cannot utime: Read-only file system
    The error happens on all files in /usr that I'm trying to backup. I know why the error is happening -- I deliberately mount /usr as read-only.
    I'd like to know why tar is trying to "utime" my files and how I can stop that behaviour if possible?
    This is my tar command:
    tar cjf /mnt/backup/backup.tar.bz2 --label='backup_090116' --atime-preserve --no-wildcards-match-slash --files-from=/root/backup.include --exclude-from=/root/backup.exclude
    TIA
    Last edited by fukawi2 (2009-01-17 07:53:02)

    Isn't it quite pointless to preserve timestamps on files from a filesystem on which timestamps aren't modified? Maybe tar tries to update the timestaps prior to archiving the file and is that giving troubles.

Maybe you are looking for