This has nothing to do with translations. It's about the user configuration (their permissions) being screwed up. See: IdentityNotMappedException Class and IdentityNotMappedException.
Windows 8 & German Locale
vboveyI have a German customer that is having problems installing an update on Windows 8 that was built with version 2.6.18.4. The Show Details button on the Update Failed dialog says:
Some or all Identity references could not be translated
Any ideas what this means?
The update does work properly for him on Windows 7 computers.
Nothing tricky is being done by the update. The update contained a single .exe to replace an existing one in the program folder.
vboveyThanks for the fast reply Sam. Yes - it's not a locale issue. Our customer support guys have gotten it to fail here in the US on our Windows 8 computers.
Can you add some clarity to your response please....
Is this something that needs to be fixed/changed in the wyUpdate program? I built this from code that I downloaded maybe 2-3 years ago and customized it in appearance only. I downloaded the latest version and it appears that there are a number of changed to the source code that happened in the interim period.
OR
Are you saying that this is related to how the user setup their login for Windows 8 (i.e. this is a Windows system administration problem).
Again, thanks for the help. This program has always worked great for us.
Are you saying that this is related to how the user setup their login for Windows 8 (i.e. this is a Windows system administration problem).
Yes, that. Here's the best answer from the second link I posted:
IdentityNotMappedException is returned when a SecurityIdentifier can not be mapped, e.g. when a SID can not be translated to an NT user. This is usually caused by deleted users or no access to the domain controller who performs the translation. If it only happens once, then it is probably caused by intermittent domain controller connection failures or some sort of lag.
vboveyWe couldn't determine what could possibly be wrong with the Windows login that was causing the problem. Certainly we are not experts in system administration for Windows 8 so it could be the case that we are missing some nuance in setting up user accounts. If that's the case, then our customers will have the same problem since most are small companies without a dedicated IT function. So as an experiment....
We got the latest source code for the client wyUpdate.exe and built the solution (VS 2010, release configuration for x86). That solved this problem. It worked just fine doing the update on Windows 8. We're not interested in doing a deep-dive into the source code changes to see what was changed that caused this to magically work on Windows 8. Just happy and relieved to have a solution.