locked
The project cannot be checked out because the server is in read-only mode. RRS feed

  • Question

  • Receiving the message "The project cannot be checked out because the server is in read-only mode." when a project manager is trying to access a project. He is a backup PM, and I'm wondering if that's why he is getting the message (since he is not the Owner or Status Manager of the project he is trying to access). We are using SharePoint permissions in Project Server 2013.
    Monday, January 12, 2015 4:47 PM

Answers

  • We switched to Project Permissions mode to leverage the Delegate feature. Also, learned that using Project Permissions feature in ribbon allows you to add other PMs to your project with flexible permission options (view, edit)
    • Marked as answer by TonyPM Tuesday, July 21, 2015 4:12 PM
    Tuesday, July 21, 2015 4:12 PM

All replies

  • I would check with your SQL Server DBA. It sounds like the DBA have either put your project databases in read-only mode or your database is having an issue and it has forced read-only on the databases.

    Or I would check with your SharePoint Central Administrator and see if they have put the databases into ready only mode.

    Cheers!


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Tuesday, January 13, 2015 4:50 AM
  • Hi,

    I have a solution that might work for you, please follow steps below:

    1) Go to your project schedule, make a small modification to any task on schedule and 'Publish' the project.

    2) While your project is being published and saved, open another window 

    Server Settings -> Manage Queue Jobs

    3) Here you can view the progress of your current Project Publishing update, check if all goes smooth and your project is published successfully without indicating any errors :
     ( to view any error look at the last column of table on Manage Queue Job page)

    4) Also in your Project window see if the project is published and not saved as Draft.

    Basically this will give you a fair idea of your project being published or not.

    Regards

    Tuesday, January 13, 2015 10:08 AM
  • Hi,

    Are you getting the error when opening the project in PWA or Project Professional? In either case I would ask someone else with proper access to re-publish the project and after checking back in the project, check if the user is able to access the project.

    Hope this helps

    Paul

    Tuesday, January 13, 2015 10:52 PM
  • Thank you all. The project is checked-in and published. The Project Manager can access just fine, but when another Project Manager tries to access the project, the Edit icon is greyed out in PWA, and he can only open in Read-Only status in Project Pro. Seems like a permission issue, but I'd like to confirm if more than one PM can edit the same project. Is that possible?
    Thursday, January 15, 2015 5:18 PM
  • Then its a cache issue.  Clean the cache for the user having the problem.  If they are using VPN, then delete the cache folder.

    Cheers!


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Friday, January 16, 2015 11:17 PM
  • We switched to Project Permissions mode to leverage the Delegate feature. Also, learned that using Project Permissions feature in ribbon allows you to add other PMs to your project with flexible permission options (view, edit)
    • Marked as answer by TonyPM Tuesday, July 21, 2015 4:12 PM
    Tuesday, July 21, 2015 4:12 PM
  • We have the same error message here. The project manager of a project gets this error message when he tries to checkout his project in Project Pro 2013. The MS Project Administrator as his backup has no problems to checkout the project. We operate with Project Permissions. We have cleaned the cache for the user having the problem. All other Project Managers in our company don't have problems to checkout their projects.
    Tuesday, August 11, 2015 8:53 AM
  • We have fixed the problem. Now the project manager of the project is also the owner of the project plan. Our project system administrator is no longer the owner of the project plan. We do not understand why this action did solve the problem. For all other of our projects the following rules are valid: The project managers are the administrators of the project plan but they not the owners of the project plan. Our project system administrator is the owner of all other project plans. This combination works fine for all other projects.
    • Proposed as answer by ribalm Thursday, August 13, 2015 9:28 AM
    Thursday, August 13, 2015 9:28 AM
  • Check your client version
    • Proposed as answer by rpuLLIa Thursday, October 5, 2017 11:26 AM
    Thursday, October 5, 2017 11:26 AM
  • If changing the Project Owner fixed the problem.  Then problem is with your security groups and permission settings. Out of the box setup of PWA< is that only the project owner (Project Manager) can edit the project schedule.  Administrators can also edit schedules because the "My Organization" category allows them to access all projects and the permission on this category allows them to edit, save and publish all projects.


    Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
    Website http://www.WhartonComputer.com
    Blog http://MyProjectExpert.com contains my field notes and SQL queries

    Sunday, October 8, 2017 10:42 AM
  • I found a simple solution to this- Adding the user to Resource Manager group. Hope it helps others!
    Tuesday, February 20, 2018 11:08 AM