This project has moved. For the latest updates, please go here.

Script fails on localized versions of SharePoint


Grant-SPObjectSecurity uses literal string for Rights parameter, with not correct for Russian version of SharePoint (my case)

Two service apps affected: Managed Metadata Service App and User Profile Service App


gandjustas wrote Nov 13, 2012 at 9:56 PM

Another bug: locating lists by title fails in localized versions.

brianlala wrote Nov 15, 2012 at 1:33 AM

I agree that the original issue might be viewed as a bug. Have a look at related discussions here:

But re: your most recent comment, AutoSPInstaller doesn't do anything with lists, so not sure why that would be seen as a bug.


bschlotthauer wrote Nov 21, 2012 at 10:08 PM

Hi Brain,

we have improved the Workaround which is described in about the “granting rights” error of the managed metadata service when a german language pack is installed.

Our approach was to question the unusual behavior of the powershell to “change to German language” during the script runtime. “Grant-SPObjectSecurity : Das Argument 'Rights' ist ungültig.” This should not happen.
As described in the above thread, following additional web application (with type “Others”) where all created incorrect with german rights designations in user policy. An additional problem was that the superusers in this Web Applications had no rights given in the user policy. As a consequence, the "granting rights" error creating the Managed Metadata Service appears.

We found out that stopping and starting the SPAutoInstaller script one time after the creation of the “Portal”, “MySite” and first “Other” Web Application, prevents “changing to german language”.
In the new script session the additional Web Applications are created correct (english rights in user policy) and the error creating the Managed Metadata Service will although no longer appear.

Unfortunately we can’t explain why the powershell environment “changes to german” after creating the three Web Applications in the function “CreateWebApplications”. It seems to be no script error.

To be able to stop the script for the workaround we inserted a pause command in the loop of the “CreateWebApplications” function.

Kind regards


wrote Feb 22, 2013 at 12:53 AM