Forum Discussion
Users are not able to open Projects from O365 in Chrome to MS Project on the desktop
The Win 7 and IE 11 issue was resolved over the weekend with a fix rolled out to the Project Online service. There are still similar symptoms related to Chrome and also some Protocol Handler version problmes that may look similar - but the IE 11 and Win 7 should be resolved now.
MicrosoftGlad you resolved this Steve - and thanks for sharing the link too - I should have mentioned the semi-annual channel in my first response. And apologies for calling you 'Owen' rather than 'Steve' - twice - I can't blame lack of coffee...
Best regards,
Brian.
Hello Brian,
Thank you for the replies on this post, we are facing the same issue using Project Server 2016, is there a known fix for this?
Using the latest version of Chrome on Win7, Win8 and Win10 and facing same issue
any update or workaround that can get project schedules to open through Chrome is highly appreciated
EDIT: i found this link that proposes a solution, will give it a try and see if it works, if you also have any other solutions, would greatly appreciate it
Hi Brian,
I'm running Chrome 80.0.3987.116 (Official Build) (64-bit) and still not able to open MPP in Share Point.
Cheers.
- Brian-Smith
khaledh - which update do you have applied to your Project Server 2016? We fixed this for Chrome some time ago. Update to a recent Public Update and the problem should go away.
Best regards,
Brian.
Brian-Smith we are still facing the same issue here, i have SP 2016 on prem, my client machines are Win 7 enterprise, some users have Project 2016 and others have 2013, all on latest version of Chrome, same issue happening
Hey Brian-Smith , thanks for the quick response. Though this is an older post, it is still related to this issue. What do we see ? Last week we released some security updates to our client machines. Since then, we cannot open project plans anymore in project professional 2013. We are connecting to an on-premise installation, and teached our project managers to open their project plans starting from PWA, the icon in the grid. But this approach no longer works for now.
Following your advice I tested project plans without a space. Works perfectly. Tested with project plans with spaces in their names, but this gives the same issues.
We are working on Windows 7 desktops, and checked the dependency on KB4489878. I can confirm that this security update is causing the problems we face. Uninstalling that specific update makes it all working again.. Working with IE 11, intranet zone and compatibility mode and protected mode on (or off, same result). So, what should we do ? Hope this helps you analyse as well our issue ?
- Brian-Smith
Guy Anthuenis what is the exact symptom? This is an old thread so you may be seeing a different issue. A recent update did break opening projects with spaces in their names - see https://techcommunity.microsoft.com/t5/Project-Support-Blog/Projects-with-spaces-in-their-names-A-recent-Windows-Security/ba-p/382867
Best regards,
Brian
Hello Brian-Smith , seems like this issue also appears when using Project desktop 2013 in combination with Project Server 2013 on-premise on windows 7 machines running IE 11 after applying KB4489873). The fix you mentioned is also coming to Project Server 2013 and older desktop clients ?
- Brian-Smith
This relies on both Project and Office Khaledh, and it could be that they need patching - so best to get both up to date. We have occasionally seen browser changes break things - but you should be able to work out what changed. If it never worked for this user then updating is probably best. If it stopped working then some other change impacted things.
Best regards,
Brian
Hello Brian and much appreciated for the response! This is happening at a client site, might it be that they are running an old version of Project Professional 2016?
Regards,
Khaled
- Brian-Smith
This is quite an old thread Khaledh, and I wasn't aware that this issue had returned. I just tested on the very latest Chrome build and it works perfectly for me on Window 10. I'm not sure why it isn't working for you but you could open a support case with Microsoft so we can help investigate.
Best regards,
Brian.
