Jump to content
CRNNTG

Excel 2016 being blocked after MBAE 1.13.2.125 update

Recommended Posts

I am getting reports from several users that MBAE is blocking there Excel files from opening after the MBAE 1.13.2.125 update last night. Any one else seeing this? Any way to verify it is a real issue or false positive?

Any help would be appreciated.

 

Thanks,

Chris R

Share this post


Link to post
Share on other sites

Suchita,

Thanks for the quick response.

I have attached the compressed log files from one of the machines.

The users are opening an Excel file that they have been working on for some time and it is giving them the MBAE Block notification.

All users are Windows 10 Pro 1803, Office 2016 Standard OVL.

 

mbae-protector.zip

Share this post


Link to post
Share on other sites

Suchita,

     Another item I am noticing in the logs is that the clients seem to have updated to 1.13.2.117 then it shows errors with MS Office apps. In the same time frame the client updated to 1.13.2.125.

    There are quit a few threads on errors with 1.13.2.117 in the forum.

     Additionally, we have closed all office apps and re-opened and it the error appears to have stopped.

 

Thanks,

Chris R

Share this post


Link to post
Share on other sites

Hi Chris,

Thanks for posting the logs. Does this block occur after you updated the machines to the latest version 1.13.2.125 and re-open MS Office Apps?

1.13.2.125 is the latest release. 

 

Share this post


Link to post
Share on other sites

Hi Chris,

We are looking further into this issue. Let me know if you face further issues. Kindly update your machines to the latest version 1.13.2.125 and restart MS Office Applications.

Thanks again for your prompt responses. 

Share this post


Link to post
Share on other sites

Suchita,

    We have verified all systems are up to 1.13.2.125 and restarted all MS Office apps and it appears to be working properly now.

    I would appear that the update to 117 was the issue. 125 corrects the issue.

 

Thank you,

Chris R

Share this post


Link to post
Share on other sites

Hi Chris, 

Thanks for letting us know that the new update to 125 fixed the issue. Let us know if you run into any further issues.

Thanks :)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.