Forum Discussion
Schedule Opens in Read-Only Mode from Conference Room Computer
In Project Server, a Project Manager opens his schedule on a conference room computer, but it opens Read Only mode and the PM is not able to check it out and edit/publish the project. We made sure it was not already checked out, and the PM is able to open, edit and publish this schedule from his work station. As far as we can tell, this problem only occurs when opening this one schedule from the conference room computer.
We have cleared the cache as described in this handy article: https://www.dalehowardmvp.com/force-check-in-stuck-projects/ but this didn’t solve the issue.
I have seen another article https://www.dalehowardmvp.com/how-to-fix-corrupted-files/ about using Save for Sharing to correct possibly corrupted schedules. My question is: would doing this cause any issues since we are accessing the schedule from a conference room? We do not want to adversely affect the way the PM opens this project from their work station.
Does anyone have an experience with schedules opening from the PM’s work station but opening Read-Only when accessing PWA from a conference room computer? Would Save for Sharing help in this instance?
Thank you
2 Replies
Wow, totally weird. I have NEVER run into this behavior before. There is obviously something different between the user's own computer and the computer in the conference room, but I have no idea what the difference actually is. The best I can recommend is that the user avoid using the computer in the conference room. Sorry I cannot be of more help. :(
Hi Brett, you may want to check who the licensed user that computer user is. When you go into Project Pro, on the top right you'll see a name - this is who is licensed to use the app and access the data behind it. There's a chance this user isn't in the Resource pool or doesn't have proper security to check out a project. You can 'switch user' to whomever the actual user with access is, and see if that works? Sometimes O365 apps esp Project have conflicts when the user on the PC isn't the same one as the app you are logging into on the back end (Pserver).
Hope this helps.
