Could not save document

I'm using GoLive CS2 v. 8.0.1
Mac OSX 10.6.7 on a Mac Pro w/ two Quad-core Xeon
I opened my site, made a small change, and when I tried to save the site, I received this error message:  Could not save document, OS Error (-36).
When I try to re-open the same site, I'm told the site cannot be read. When I open the backup site, the change I had made is visible but I cannot save this backup site either.
Opening previous copies of the site from another disk gives the same results; I can open the site, make changes, but can't successfully save the site without corrupting it.
I've been using the same version of GoLive successfully for several years, modifying the same site, and now it suddenly cannot save the site.
I updated to OSX 10.6 last December, and have used GoLive successfully since then.  I don't recall when the system did the update to 10.6.7 and am not sure if I used GoLive since that happened.
Does this sound like a corruption of the application software?  If so, is my best course of action just reloading the software?
Is there some compatibility problem between GoLive 8.0.1 and OSX 10.6.7?
What to do?
Don Wong
[email protected]

Thanks for the PPC tip. My PPC tower is long gone, but I've still got my 6 year old PowerBook. Not sure if it's up to the task, but I'll keep it around.
I'm a photographer, not a website writer, and only learned enough GoLive a few years back to write my site and maintain it.  I seem to remember that GoLive was replaced by Dreamweaver (Adobe gave me a copy of it along with GoLive) and my impression is that GoLive is no longer being updated and therefore more problems might crop up as operating systems and hardware evolve.  (I could be wrong, since I don't follow web software developments.)
Back to your original comment about wanting to stick with GoLive CS2. If for some reason I wanted to transition to another software in the future, is there a standout choice for me? Keeping in mind that I don't really use it that often, and would prefer spending the least amount of time relearning things.
What is the majority using these days?
Also, if I did switch software, would I have to re-write my site from scratch, or could the existing site be 'ported' over to the new software?

Similar Messages

  • Xformbuilder error ... Could not save document Name/Name-Schema.xml

    Hello everyone,
    We're using 7.00 SP14 and I have a problem with the xml forms builder on one of our systems. We're having a 3 system landscape - all three are on the same patch level etc.
    I was able to create a new xml form on one machine, unfortunately it doesn't work on our P-system. I tried to create a new form as well as copied an existing one - with the same error result.
    While saving a project the following errors appear:
    The following error occured when saving the schema: Could not save document Name/Name-Schema.xml. Reason: Operation is not supported
    The project could not be saved on the server. Do you want to save a local copy?
    Oct 13, 2008 2:45:43 PM - (ERROR)com.sapportals.wcm.app.xfbuilder.server.ServerManager :Could not serialize document: Operation not supported
    Does anyone know what the problem is? I'd appreciate your help, thanks.
    Sincerely,
    Susanne
    Okay I just found out that it's not possible to create a new folder in KM under xmlforms. That's working on the other 2 systems quite well. I have all the admin roles but somehow somewhere somewho must have restricted that. We found out that ice, etc, runtim, entry points and maybe even a few more aren't setup to create new folders in there. Does anyone know where/how to change that? It doesn't work with Details - permissions etc.
    Edited by: Susanne Zahn on Oct 13, 2008 3:40 PM

    For anyone who's interested in the solution.. there you go.
    14.10.2008 - 17:53:00 CET - Antwort von SAP     
    Dear customer,
    Can you please check whether the repository /etc is in read-only
    mode?
    Please navigate to -
    System Administration -> System Configuration -> Knowledge Management
    -> Content Management -> Repository Managers -> File System Repository
    There you can see the checkbox for "read-only".
    Please insure that this is not ticked. If it is, please uncheck it
    and building/saving the project again.

  • Could not save the document to the repository for the following reason

    Hi,
    Some of the Scheduled reports are getting failed because of the following Error.
    Could not save the document to the repository for the following reason: [repo_proxy 30] InfoStore::ObjectExport::commit - (Helpers::InfoStore::ObjectExport::commit) File Repository Server error : Failed to put the file to file server: frs://Output/a_242/027/084/5512178/aduu8vtfkntmvyv8lsnntas.wid already exists.(hr=#0x80042a4a)(Error #-2147210678 (WIS 30567)
    i have searched about this but no use no information on the same.
    So Pls let me know why this problem will occur and how to resolve this,I am new to this forum if any this is wrong pls let me know
    Thanks in advance,

    HiShwetabh Suman
    Thanks a lot for immediate response,
    Please go through the following
    From the logs I see a difference in the execution steps as below:
    [2014-03-31 10:24:15,364] [TID:13] [INFO ] [child.RunStatusTimerTask.run():17]: calling checkRunStatus
    [2014-03-31 10:24:31,887] [TID:3168] [INFO ] [child.ChildImpl.request():23]: request: [GetLoad]
    [2014-03-31 10:24:31,888] [TID:3168] [INFO ] [child.ChildImpl.request():25]: response: [1]
    [2014-03-31 10:24:37,879] [TID:3153] [ERROR] [webi.PublishingSubsystem.run():93]: Throwable exception caught:
    com.businessobjects.rebean.wi.ServerException: Could not save the document to the repository for the following reason: [repo_proxy 30] InfoStore::ObjectExport::commit
    - (Helpers::InfoStore::ObjectExport::commit) File Repository Server error : Failed to put the file to file server:
    frs://Output/a_165/024/084/5511333/aqew_jeqdcjcrukoadjdtk0.wid already exists.(hr=#0x80042a4a)(Error #-2147210678 (WIS 30567)
    Can you please help us understand the reason why the child.runstatustimertask.run() is called in the case where we get the failure. Because upon noticing the difference in the steps of execution I see that this method is called and after that the failure is occuring.
    Also, few other findings are that :
    1. The error occurs from both the nodes adaptive job servers randomly.
    2. The IFRS and OFRS of one of the node is not being used at all for any file transfers (though the configurations are exactly same).
    Please advise and help us get rid of the said error.
    Can u give any permanent solution for us

  • Error message 'Could not save to path /Users/yogasail/Documents/' appeared and cannot save files?

    I have an iMac 21.5 running OS X 10.9.4:Processor  2.7 GHz Intel Core i5:Memory  8 GB 1600 MHz DDR3. I have suddenly got this message every time I try to save a file -'Could not save to path /Users/yogasail/Documents/Emma/xxxx.rtf. Choose a different path.' Unable to save anything now?? Can anybody help?

    Back up all data before proceeding.
    This procedure will unlock all your user files (not system files) and reset their ownership, permissions, and access controls to the default. If you've intentionally set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it, but you do need to follow the instructions below.
    Step 1
    If you have more than one user, and the one in question is not an administrator, then go to Step 2.
    Triple-click anywhere in the following line on this page to select it:
    sudo find ~ $TMPDIR.. -exec chflags -h nouchg,nouappnd,noschg,nosappnd {} + -exec chown -h $UID {} + -exec chmod +rw {} + -exec chmod -h -N {} + -type d -exec chmod -h +x {} + 2>&-
    Copy the selected text to the Clipboard by pressing the key combination command-C.
    Launch the built-in Terminal 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 Terminal in the icon grid.
    Paste into the Terminal window by pressing command-V. I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting.
    You'll be prompted for your login password, which won't be displayed when you type it. Type carefully and then press return. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
    The command may take several minutes to run, depending on how many files you have. Wait for a new line ending in a dollar sign ($) to appear, then quit Terminal.
    Step 2 (optional)
    Take this step only if you have trouble with Step 1, if you prefer not to take it, or if it doesn't solve the problem.
    Start up in Recovery mode. When the OS X Utilities screen appears, select
              Utilities ▹ Terminal
    from the menu bar. A Terminal window will open. In that window, type this:
    res
    Press the tab key. The partial command you typed will automatically be completed to this:
    resetpassword
    Press return. A Reset Password window will open. You’re not going to reset a password.
    Select your startup volume ("Macintosh HD," unless you gave it a different name) if not already selected.
    Select your username from the menu labeled Select the user account if not already selected.
    Under Reset Home Directory Permissions and ACLs, click the Reset button.
    Select
               ▹ Restart
    from the menu bar.

  • "could not save as ***.psd because the document is bigger than 2 gb

    "could not save as ***.psd because the document is bigger than 2 gb

    Yes, that's the maximum for PSD. Save as PSB instead.

  • Could not save the document to the repository for the following reason: [repo_proxy 30] DocumentFacade::uploadBlob - Query execute has failed : Error occurred while attempting to reconnect to CMS : Not a valid logon token. (FWB 00003) (hr=#0x80042a70) (WI

    Hi, getting Could not save the document to the repository for the following reason: [repo_proxy 30] DocumentFacade::uploadBlob - Query execute has failed : Error occurred while attempting to reconnect to CMS : Not a valid logon token. (FWB 00003) (hr=#0x80042a70) (WIS 30567) amongst lots of other errors when scheduling.
    I was logged in as administrator and attempting to schedule a webi document to my self using the email option.
    thanks in advance

    Hi Trinath,
    Could you please confirm if you could save a new report as well or not; or is it specific to scheduling.
    If you are unable to save a report also then I think this is due to the path of the Input File Repository Server or its temporary directory are not pointing to the same path, and their locations are set to 2 different hard drives
    BOXI3.1 Server must use the same hard drive (local or network share) for the Input File Repository Server and its temporary directory.
    - Shahnawaz

  • Could not save because file is locked

    I have Photoshop CS6 and I have never had a problem with this before -
    All of a sudden I am getting an error message when saving : " Could not save…because the file is locked, you do not have necessary access permissions, or another program is using the file. Use the ‘Get Info’ command in the Finder to ensure the file is unlocked and you have permission to access the file. If the problem persists, save the document to a different file or duplicate it in the Finder."
    No other program is even open… I have quit every process I could in the Activity Monitor.
    I have tried saving as a different file name and format, I have changed permissions for the Staff option on all of file folders.
    I have even completely restarted my computer, but literally nothing has worked.
    Help!

    No anti-virus software (they cause far more problems than they solve, at least on a semi-secure network), I don't leave Bridge running. iTunes is running, so is InerTrak (time tracking software)... so it has to be Spotlight or Time Machine unless Activity Monitor will lock files. Or it could be Quicksilver, which creates indices like Spotlight.
    First thing I'm doing is adding all my hard drives to "Prevent Spotlight from searching these locations" and we'll see if this comes up again.
    Could it be the Finder? Does the Finder lock the file while reading the thumbnail?
    I'm surprised that there's no way to tell what process has locked the file.
    OK, last bit: Why doesn't Photoshop lock the file when it's open so that other programs won't open it?

  • I have PS 6 and just purchased an iMac and am running OS 10.10.1 (Yosemite).  When i try to Save or Save As a file I get the following message:  Could not save as "Whatever.psd" because this file is locked, you do not have necessary access permissions, or

    I have PS 6 and just purchased an iMac and am running OS 10.10.1 (Yosemite).  When i try to Save or Save As a file I get the following message:  Could not save as "Whatever.psd" because this file is locked, you do not have necessary access permissions, or another program is using the file.  Use the Get Info command in the Finder to ensure the file is unlocked and you have permission to access the file.  If the problem persists, save the document to a different file or duplicate it in the Finder.  Any suggestions?  Thanks.

    Photoshop: Basic Troubleshooting steps to fix most issues
    Look under Troubleshoot User Permissions.
    Gene

  • When I close Photoshop CS6, the following message appears: "Could not save Preferences because the file is locked, you do not have necessary access permissions, or another program is using the file.

    When I quit Photoshop CS6, the following message appears:
    " Could not save Preferences because the file is locked, you do not have necessary access permissions, or another program is using the file. Use the ‘Get Info’ command in the Finder to ensure the file is unlocked and you have permission to access the file. If the problem persists, save the document to a different file or duplicate it in the Finder."
    If I try to change the Workspace in PS6 from Essentials to any other Workspace, the following messsage appears:
    "Could not apply the workspace because the file is locked, you do not have necessary access permissions, or another program is using the file. Use the ‘Get Info’ command in the Finder to ensure the file is unlocked and you have permission to access the file. If the problem persists, save the document to a different file or duplicate it in the Finder."
    I have checked the Sharing and Permissions section of the "Get Info" panel accessed from the Finder and I have set Read and Write Privileges for my user account for Photoshop CS6. System and Admin are also set to Read and Write.
    I have a MacBook Pro with OS X Version 10.9.5 and have all available updates for Photoshop CS6, Lightroom 5 and Bridge CS6.
    I tried uninstalling the program and downloading it again and reinstalling, but nothing changed.
    Can you help?
    Thanks,
    cjpnm

    You may get better help in Photoshop General Discussion
    The Cloud forum is not about using individual programs
    The Cloud forum is about the Cloud as a delivery & install process
    If you will start at the Forums Index https://forums.adobe.com/welcome
    You will be able to select a forum for the specific Adobe product(s) you use
    Click the "down arrow" symbol on the right (where it says All communities) to open the drop down list and scroll
    If FINDER means Mac, read below (and try to give more information when asking a question)
    Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
    Enable Mac Root User https://forums.adobe.com/thread/1156604
    -more Root User http://forums.adobe.com/thread/879931
    -and more root user http://forums.adobe.com/thread/940869?tstart=0

  • Photoshop CS3 error saving files - Could not save ... because the fileis already in use or was left

    I have a problem with Adobe Photoshop CS3 that only started happening last night. Heres a description of the problem.
    When I try and save a Photoshop file, I get the following error message:-
    Could not save (filename). because the file is already in use or was left open
    I have rebooted my computer, rebooted our server, un-installed & reinstalled Photoshop and also done a system restore, and I still have the problem. (The system restore actually caused huge problems I got the error message The licensing subsystem has failed catastrophically. You must reinstall or call customer support, except I wasnt able to reinstall or uninstall the product. The computer just would not run the installer. I had to undo the system restore.)
    I can do Save For Web with no trouble and I can save files to the same location with every other Adobe product installed in the Web bundle, just not Photoshop.
    We have 2 machines here with an identical set up (hardware and software) and the problem is only on one machine.
    Even though Photoshop says it cant save the file, its actually saving the file in the following format:-
    ~psX.tmp where X is a random variable, either characters or numbers.
    I have to manually open My Documents and rename the file to filename.psd so I can access it again.
    Short of reformatting my computer (which Im not keen on doing because it will mean several wasted work hours and I will have to pay our IT people to come in and hook me back up to our network), how can this problem be fixed?
    I have also Googled the problem and the only help I found was a suggestion to search for a psicon.dll file and rename it. This file does not appear anywhere on my system, so I'm at a loss.
    I have contacted support about this issue, but thought it was also worth while to ask here at the same time.

    I'm having similar problems with not being able to save files after editing them (and giving them a new file-name, obviously) in Photoshop Elements 4.0. I get an error message saying (for instance): "Could not save as (whatever I'm trying to name the file) because the file is already in use or was left open". Then I see a .tmp file (that I can't open)
    I did a search and found that the file was being saved twice, once within Photoshop (where I'm working with it) and also in..
    "C:\Documents and Settings\Owner\My Documents\My Pictures\Temporary"
    I'm assuming this is the problem, but if you have any clue as to why is this happening and what I can do about it, I'd welcome any input. I've been using PSE-4.0 for years, and this problem just started cropping up. The only (cumbersome) way around this problem has been to just make my edits (in PSE-4.0) and do a "save" under the original file name, then go into explorer and rename the file. So, in short, I cannot do what I've been doing for years, editing a picture and saving it (renamed) in the sane folder (or a different one).
    I can "see" the .tmp files in PSE-4.0, but they won't open.. but they will in JASC.. odd..
    Thanks-
    Bob

  • Could not save as - The file may be read-only or is already open in another application

    Can anyone think of a reason why if I'm working locally on a CS3 Flash .fla on my C: drive that I would get the error:
    Could not save as: C:\Users\John\Desktop\Project_File\ANNUAL REPORT RELEASE\01-19-11\report_stragegy.fla
    The file may be read-only or is already open in another application. Save using a different name, or close the document and try again.
    I'm running Windows 7 Home Premium 64-bit.
    It happens sporadically. I haven't been able to find a reason why this error pops up when saving some of my .fla files!!
    The files are not set to "read only" when I right click on them and choose 'Properties' in the Windows 7.
    I found some somewhat similar situations with saving errors:
    http://board.flashkit.com/board/showthread.php?t=796857
    http://forums.adobe.com/message/2980090?tstart=0
    http://www.actionscript.org/forums/showthread.php3?t=153738
    Thanks

    Sometimes I can save with a different file name. But sometimes I can't and start a new blank document and cut and paste from the one that won't save to the new untitled document.

  • Could not save *.* because file is in use or was left open...

    OK, I mentioned this when it happened with .eps files, and rather than get a single useful tip(Except for 'choose a new file name'), I got a series of responses from people telling me how I should be saving in .tiff and 'eps files aren't any good anyway, etc., etc... IN other words, no help, just a bunch of opinions on what I was doing wrong in the first place.
    Well, now I have had it happen with a .tiff file. I opened the file, did some work, and went to re-save it, and I got the error that it could not save the file because it was in use, or had been left open.
    Anybody got any suggestions on why this is happening?
    Mac OS 10.4.1
    Dual 2.66 GHz Dual core Intel Processors
    2 Gb RAM
    Photoshop CS3

    OOPs I forgot to paste the Adobe help message so here it is;
    understand that you receive an error when you try to edit Lightroom
    images in Photoshop® CS3.
    If you have not already done so, update to Photoshop Lightroom 1.3. In
    Photoshop Lightroom, choose Help > Check For Updates. You can also
    download the update from the Product Updates page on the Adobe website.
    Try specify Photoshop CS3 as the Additional External Editor in your
    Lightroom preferences:
    - Click the Lightroom menu and choose Preferences.
    - Click the External Editing tab.
    - Click the Choose button under the Additional External Editor
    section.
    - Browse to the Photoshop CS3 application file and click Choose. If
    Lightroom gives you a warning, select Use Anyway.
    - Select an image in the Lightroom Library module, click the Photo
    menu and choose the second option for Edit In Adobe Photoshop CS3.
    If this does not resolve your issue, it is possible that files from
    Photoshop CS2 are interfering with your workflow. To completely remove
    Photoshop CS2 files from your computer, follow the instructions in the
    following document on our website:
    http://kb.adobe.com/selfservice/viewContent.do?externalId=331404
    <(>&<)>sliceId=2
    If this does not resolve your issue, it is possible that your Lightroom
    catalog is damaged. To test the integrity of your catalog:
    - Launch Lightroom while holding the Ctrl key on your keyboard.
    - Check Test integrity of this catalog
    - Click the Select button.
    If you have a large number of photos in the catalog, Lightroom may take
    some time to complete the testing process and finish launching.
    If that does not resolve the issue, quit Lightroom, launch it the same
    way and create a new catalog in the Select Catalog window.
    If you continue to experience the issue, try the steps in this general
    troubleshooting guide on our website:
    http://kb.adobe.com/selfservice/viewContent.do?externalId=333653
    <(>&<)>sliceId=1

  • Could not save preferences because the file could not be found (Windows) then Error 1 on PS,AE,PR,ID

    I was trying out Photoshop, everything was running fine then one day when I close it I get an error:
    "Could not save preferences because the file could not be found..."
    Now when I boot it I get the Configuration Error 1.
    After Effects still boots, but it reset all my preferences there. For example the workplace layout was reset, all my saved Output presets were removed and my memory-cache and performance settings were reset again.
    Premiere and InDesign get the error too and won't boot.
    This is the second time it has happened, I'll try wiping every Adobe program and reinstalling all over again, but it had run fine before for a while and it randomly happened.
    Any idea how to fix this?

    Nope I havent touched the Documents folder.
    Forgot to mention that I'm on Windows 7

  • InD blocking Ps to save a file / Could not save * because the file is already in use error

    Many users have reported a  Photoshop Could not save * because the file is already in use error in many different circumstances.
    I place raw jpgs in InDesign document, then open them in Photoshop via Edit original order to adjust them. On random occasions Ps gives me that annoying error. So i found a little trick to avoid saving that image under a different name and relinking it plus reloading Ps since the error repeats on other pictures to.
    All you have to do is: when Ps gives error, (Cmd-Tab) switch to InD, directly select the worked jpg in image frame (one that you try to save in Ps)  and simply move it left-right (or move it and Undo). Now you can save it without problem.

    JPEG is a "lossy" compression format. Every time you save as jpeg you recompress and throw away a little more information. In addition, jpeg does not support transparency or layers, both very useful features for woring with images. For example, you can add an adjustment layer in Photoshop to do your adjustments non-destructively for may of the things that you can do using Image > Adjustments... which will change your pixel data permanently. Throw away an adjustment layer and you image data is untouched. Also, ID allows you to place a layered image and control layer visibility from within ID, making it possible to multi-purpose a single file by showing or hiding various layers.

  • "Could not save a copy because the file is already in use..."

    I have read previous discussions of this issue, but nobody suggested a solution. Sometimes when I use the Save As command to save an open file with the same name as an existing Photoshop file that is not currently open, I get the dreaded message: "Could not save a copy because the file is already in use or was left open."
    When this happens, I have to save my open file using a different filename, then change the name in the Finder after manually deleting the original file with that name. This happened occasionally in Photoshop CS3, and is now happening more frequently in CS4. If no one can offer a solution, can someone please tell me if there is a way to officially submit a bug report? The simple truth is that Photoshop costs way too much for a well-known problem like this one to be hanging around version after version. Adobe really needs to fix this and I'd like to tell them so. Thanks!

    alansky1 wrote:
    Adobe really needs to fix this and I'd like to tell them so.
    I've run into this and I'm convinced it's not Adobe. Whenever I've gotten around the problem it's often something from Apple that got in the way.
    I use a simple workaround when Finder/QuickLook isn't letting go of the file. First use a free utility like TinkerTool or Onyx to turn on the Quit command in the Finder. Whenever the Finder gives you trouble, if closing the Finder window in question doesn't solve it, just do the ol' Command-Q. It's a little faster (and maybe safer?) than force-relaunching the Finder. This usually releases files for me when all else fails; it also often cures the annoying "can't eject the volume because it's in use" messages when you've already quit every program you can find.
    There's the question of why Photoshop and not others; I'm not an engineer but I think the sheer size of Photoshop files is a factor. In one instance I noticed that quicklookd was using a lot of RAM, and QuickLook has been implicated by an earlier post in this thread. It isn't unusual for a Photoshop file to be very large compared to other types of documents. It's possible that when QuickLook hits a large Photoshop file, and it does its normal thing of generating a big preview for it, it could get tied up reading that huge image long enough to block another program. Sometimes it seems like QuickLook just hangs on them. When it happens, you can try looking at Activity Monitor to see if something like QuickLook, Spotlight, or some other program is using an unusual amount of CPU or RAM.
    Apple Mail (at least in 10.5) is another major offender by the way. If you attach a file to Apple Mail it will hang on to it as "open" even after you remove the attachment. Other programs will not be able to write to the file that was attached or formerly attached. Nothing short of quitting Apple Mail will make it let go of the file. You'll notice it when you delete a JPEG, PDF, Word doc (definitely not just Photoshop) attachment because you realize you need to make a change and attach it again. Attempting to export an updated one over the old one is blocked until Apple Mail is quit.
    In my experience I think what Chris says is true.

Maybe you are looking for