MSO2057.acl error

[NewBoy]

Has anyone come across this error before,

 

Every time one of the children log onto a laptop it opens showing the following error;

 

'Your Autocorrect file, MSO2057.acl, could not be saved. The file may be read-only, or you may not have permission to modify the file.'

 

I have tried repairing the installation and that had no effect, un-installed and re-installed and still no joy. I have scanned for a virus with Sophos and Avast and then used 3 different anti-spyware solutions and all comes up clean so really not sure what's causing the problem and I really don't want to have to re-image them all :-(.

 

But if you log on as a member of staff then everything is fine, it's only started happening since returning after xmas so cant see it being a policy issue as nothing has changed on that side of things.

 

Any advice would be greatly appreciated.

Edited January 21, 2016 by NewBoy

[NokiX]

I experienced the same issue however I found it was caused due to the appdata not being available to the user when they were away from the network. This also seems to only affect 64 bit machines for me however I managed to resolve the issue on affected devices (mainly new laptops) by setting the users appdata to be part of the offline files policy which fixed the problem when they were not able to access their appdata on the network.

 

I expect it will be related to the pupils permissions & appdata so it may be worth checking your wsus server to see if any office updates were applied and roll them back but if nothing was applied then I'm not sure what else to suggest since I found little to no information about the problem other than it can be caused by corrupted installations which It can't be in your case.

 

One question however, which version of office are you using?

[NewBoy]

Thanks for the reply it's office 2013 pro been searching for ages but none of the so called solutions are working, they dont have a WSUS server and updates have been turned off so not to sure whats causing the problem.

[NokiX]

I experienced the issue with office 2013 as well so it could be related to the version being used. Sorry I can't be of any more help however hopefully the details of my own situation may provide some insight although I would suggest trying both 64 bit and 32 bit versions and if possible see if office 2010 will work as a temporary fix.