none
Upgraded to 2.9.7205.27375 from 2.9.6842.37624 and now Outlook won't work RRS feed

  • Question

  • We recently Upgraded to 2.9.7205.27375 from 2.9.6842.37624 and now Outlook won't work.  We get an error saying Outlook can't load.  I've tried repairing Outlook but that didn't help.  We are using Microsoft UPD with FSLogix Office Container. The older version was working fine initially but then it started to crash the server.  So we tried upgrading to the latest version but now Outlook won't load.  Any ideas?  I have a ticket open but so far they have not provided a solution. 
    Sunday, October 27, 2019 7:25 AM

All replies

  • I'm having the same issue here. Did you managed to find a way around it ?

    Thursday, November 21, 2019 7:49 AM
  • We recently Upgraded to 2.9.7205.27375 from 2.9.6842.37624 and now Outlook won't work.  We get an error saying Outlook can't load.  I've tried repairing Outlook but that didn't help.  We are using Microsoft UPD with FSLogix Office Container. The older version was working fine initially but then it started to crash the server.  So we tried upgrading to the latest version but now Outlook won't load.  Any ideas?  I have a ticket open but so far they have not provided a solution. 
    2.9.7205.27375 did have a regression in it that was causing deadlocks.  would you be willing to update to 2.9.7237.48865 and try with that build?  If you are still seeing issues with that new build we can rule out the filesystem lock up, and avoid having you run into that one, and move forward from there.  Just in case you run into the issue on the new build as well can you help me understand your config a little better.  Are you including or excluding any extra locations from the UPD config?
    Tuesday, November 26, 2019 1:36 AM
  • We're having a similar issue. What's the full error message you're seeing?

    Error we get is: "Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. The information stored could not be opened".

    Re-creating the Outlook profile and deleting the contents of "%AppData%\Microsoft\Outlook" and "%LocalAppData%\Microsoft\Outlook" has no effect. To fix it, we have to delete the user VHDX and have them log in again. The problem returns a couple days later.


    • Edited by DanRobb Tuesday, November 26, 2019 11:20 AM
    Tuesday, November 26, 2019 11:19 AM
  • We've experienced this issue and we've ended up rolling back to 2.9.6964.52690.  I upgraded the client to FSLogix_Apps_2.9.7237.48865 and got the exact same message as above.  Even when removing the mapi profile it gave a slightly different error and wouldn't automatically detect.  Re-installed 2.9.6964.52690 and functionality returned.

    We are using VL version of office 2016.  The last time we upgraded for another client, I ended up repairing office then running DISM /online /Cleanup-Image /RestoreHealth & sfc /scannow.  Then eventually it worked without the above error. 

    I'm reluctant to upgrade as I am sure others are if this is going to cause more issues.  We're certainly not going to start deleting ODFC VHDX just get outlook to work.

    Thanks

    Mark


    Thursday, December 5, 2019 11:03 AM
  • We're going to try the upgrade again, however I'll fully remove the client before updating to the latest version.
    Thursday, December 5, 2019 12:33 PM
  • what was the result of this?
    Friday, December 6, 2019 9:29 AM
  • I attempted an upgrade to by removing 2.9.6964.52690, rebooting and installing 2.9.7237.48865.  Whilst the profile loaded, it was in metered mode.  I attempted a repair of office as per microsoft article, however it remained the same.  Removing 2.9.7237.48865, rebooting and installing the first Microsoft FSLogix release gave the cannot open outlook error.  The only difference with this particular setup, is that it's a MSI version of Office 2016 and not 365.

    Restoring 2.9.6964.52690 and outlook functions fine again, with search and indexing working OK.

     
    Monday, December 9, 2019 9:31 AM