• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 10233 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCSv6: Could not write metadata for '/RemoteSystemsTempFiles'.

stevenh
Guru 20045 points


Hello,

I am got the following error when I exited CCS.

Could not write metadata for '/RemoteSystemsTempFiles'.
.....\.metadata\.plugins\org.eclipse.core.resources\.projects\RemoteSystemsTempFiles\.markers (The system cannot find the path specified)

RemoteSystemsTempFiles does not exist in the .project folder.

What could be causing this issue.

Stephen

  • 0
    Guru 20045 points
    The .projects folder contains ones folder having the name of my project and that folder contains other file, one of which is the .markers file.
  • 0 in reply to stevenh
    Guru 20045 points
    Also, a dialog box appears while CCS is running. The dialog box shows:

    'Periodic workspace save.' has encountered a problem.
    Could not write metadata for '/RemoteSystemsTempFiles'.
  • 0 in reply to stevenh
    TI__Guru**** 173310 points

    This page provides some solutions, some of which are to manually create the folder it is trying to write to, or clean the workspace/open a new workspace.
    Hope one of the suggestions there helps your situation.

  • 0 in reply to AartiG
    Guru 20045 points
    Hello AartiG,

    Thanks for the info.

    This issue started when I moved both my workspace and my project to a network drive. Before that time, I have never had this problem.

    Also, I am using tortoisehg versioning for both the workspace and project. Other's have mentioned that it is not a good idea to manage mercurial repos directly on a network drive.

    However. I have had good luck with working with cloned network repos on my local drive.

    Just recently, I decided to work directly off the network drive, which probably wasn't a good idea. I created both a workspace and a project in that workspace. After getting some code to work, I commited everything to the mercurial repo. I think the issue started happening sometime after I did that. I also remember testing my repo out by deleting its contents and then doing a hg update. That may have caused the issue if not everything got committed to the repo.

    I might try one or more of the suggestions that were at the link you sent. If none work out, I'll just create everything on my local drive, put it on the network drive and then clone the repo back to my harddrive and work from there. In the end I probably end up working from a cloned network repo. That sounds like the best way to do it.

    Thanks,
    Stephen