0

Troubleshooting Version Control and Shared Workspaces

  • updated 1 mth ago

When you set up and use shared workspaces, the LogicNets Designer makes multiple API calls and checks permissions, so you may experience short delays. If an API call receives an error, the system displays an error message. The table below lists the types of errors, specific messages, and recommended next steps you should take.

Note that Shared Workspaces do require appropriate permissions to be set, and it is important to communicate to the users who the Shared Workspace Administrator(s) are for the installation.

On-Screen Warning Messages

Error Message Suggested Action(s)
403 Forbidden You have not been assigned permission to access this information. Contact your Administrator for assistance. Check your permissions for the Shared Workspace.

If set to read-only you will not be able to check out the project or make changes to it.

You CAN unlink the project and work with a non-version-controlled copy.
403 Forbidden You do not have permission to unlock this project
403 Forbidden You do not have permission to check-in this project
403 Forbidden You do not have permission to edit the status
403 Forbidden You do not have permission to get the project
403 Forbidden You have not been assigned permission to access this information. Contact your Administrator for assistance.
403 Forbidden The workspace does not exist or you do not have permission to access this workspace
404  Not Found Failed: no such revision or project exists Check with the project owner regarding the project status.
404  Not Found Failed: the source of this linked project is deleted
404  Not Found Failed: getting the project revision status
404  Not Found Failed: the project data is not found
404  Not Found Failed to query workspace info from admin database
409 Conflict Failed: reading lock status Check your permissions for the Shared Workspace. If they are set to read-only you will not be able to check out the project or make changes to it.

You CAN unlink the project and work with a non-version-controlled copy.
409 Conflict Failed: creating lock
409 Conflict Failed: to get the project history
409 Conflict Failed: to get the project information from the history table
409 Conflict Failed: to get the project information from the project table
409 Conflict Failed: already locked by Request that the other user check in or release the project.
500 Server error Failed to create temporary workspace Try the process again and verify with your colleagues.

Report the issue to your LogicNets Administrator.
500 Server error Publishing failed Try the process again and verify with your colleagues.

Report the issue to your LogicNets Administrator.
Reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
Like Follow
  • 5 mths agoLast active
  • 21Views
  • 2 Following

Home