August 2nd, 2007

Team System Web Access: Workaround for installation problem on a non-English Windows OS

Buck Hodges
Director of Engineering

[UPDATE 8/8/07]  There is now a KB article on this issue.

Hakan posted the following on Brian Harry’s blog in response to a customer report about encountering the following issue when installing the new Team System Web Access release on German, French, Italian or Spanish Windows.  We plan to add this to the FAQ page.

Symptom:

You receive the following error while trying to install Team System Web Access.

System.Security.Principal.IdentityNotMappedException: Some or all identity references could not be translated.

(Spanish) System.Security.Principal.IdentityNotMappedException: No se pudieron convertir algunas o todas las referencias de identidad.

(French) System.Security.Principal.IdentityNotMappedException: Impossible de traduire certaines ou toutes les références d’identité.

Cause:

During the installation, we grant permissions to Network Service account for the Cache folder. On some non-English operating systems, the installer cannot locate the Network Service account because the account name is localized.

Affected Operating Systems:

This problem only happens when TSWA is installed on a German, French, Italian or Spanish Windows. Other Windows languages are not affected by this issue.

Workaround:

If you’re installing Web Access on a Windows with any of the following languages: German, French, Italian, or Spanish; before running the installer, please follow the steps below:

1. Create a new local user group with the name “Network Service”

2. Add the localized network service account to the recently created “Network Service” group. Here’s a mapping:

    German – NT-AUTORITÄT\NETZWERKDIENST

    French – AUTORITE NT\SERVICE RÉSEAU

    Italian – NT AUTHORITY\SERVIZIO DI RETE

    Spanish – NT AUTHORITY\SERVICIO DE RED

3. Run the TSWA setup.

We’re tracking this issue on our support forum:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1954637&SiteID=1

Author

Buck Hodges
Director of Engineering

Director of Engineering, Azure DevOps

0 comments