We're running into this issue on every windows 7 workstation.
According to http://www.symantec.com/business/support/index?page=content&id=TECH76597 setting the locals the same should fix this, it does not. Or I am missing a locale, and then hope to get information what locales need to be adjusted where.
Adding users to the powerusers group, and assigning that permissions to the msmapi folders ..\1033 and 1043, is obviously not a good solution. Is there ANY OTHER way to be able to get Virtual Vault working, without needing to fiddle with permissions or other nono's.
I was thinking of (perhaps) a loginscript that copies mapisvc.inf from the 1033 to the 1043 folder. (although everything is in English, mapisvc.inf is installed in the 1043 (dutch) folder.). We're using the english client. Should we perhaps go for the dutch one?
Has anyone resolved this issue by another workaround? Less intrusive and easier to implement in a large environment?
I'm in the US, so I haven't had to do anything with the locale setting, but I have seen this error occur a lot recently on Windows XP (don't recall any running Windows 7). The solution I used can be found at http://www.symantec.com/business/support/index?page=content&id=TECH126007.
If that fixes the problem I'm not sure what the best solution would be to script the fix so it will run on all of the affected workstations.