{"id":188,"date":"2014-05-22T12:29:46","date_gmt":"2014-05-22T12:29:46","guid":{"rendered":"http:\/\/www.johntimney.com\/?p=188"},"modified":"2014-05-22T12:29:46","modified_gmt":"2014-05-22T12:29:46","slug":"access-apps-and-language-packs","status":"publish","type":"post","link":"http:\/\/www.johntimney.com\/?p=188","title":{"rendered":"Access Apps and Language Packs"},"content":{"rendered":"<p>install SharePoint2013 Server 2013 in your native language &#8211; in my case English.<\/p>\n<p>Configure SharePoint for building Access Apps (http:\/\/social.technet.microsoft.com\/wiki\/contents\/articles\/12514.sharepoint-2013-access-services.aspx)<\/p>\n<p>Create a new Access App, test it as working<\/p>\n<p>Install a language pack (you should have done this first by the way &#8211; not after you had started using SharePoint but we do occasionally consume\/partner with other companies and face this stuff).<\/p>\n<p>Created a second Access App and you will find it fails to initiate correctly even although the first app works fine still.<\/p>\n<p>So, SharePoint initially creates a web for the\u00a0Access-App with the initial locale of your native install whihc in this case is &#8220;en-US&#8221;.\u00a0 Thats now not valid as you have installed a language pack &#8211; Access web is confused which means you now need to update the language of the app web as the language of the site is stored at SP Web level.<\/p>\n<p>It is stored in database in the AllWebs table and the only wy to fix this appears to be by applying a small hack to the contentdb &#8220;dbo.AllWebs&#8221;using a SQL query.<\/p>\n<p>&nbsp;<\/p>\n<p>Ideally, you need You need to modify two specific attributes so look for &#8220;language&#8221; and &#8220;locale&#8221;\u00a0 in the contentDB and change the values from the install value (so 1033 (en-US)) to the locale for your language pack. Dutch for example is 1043.<\/p>\n<p>To change the language in database you need to fire following Query:<\/p>\n<p>For changing the language of all sites in to \u2018Dutch\u2019 language:<br \/>\nUPDATE dbo.AllWebs SET Language = 1043<\/p>\n<p>Changing the language of one site collection: (Dutch language)<br \/>\nUPDATE dbo.AllWebs SET Language = 1043 WHERE SiteId = [[SiteCollectionId]]<\/p>\n<p>Changing the language of a single web or subsite: (Dutch language)<br \/>\nUPDATE dbo.AllWebs SET Language = 1043 WHERE Id = [[WebId]]<\/p>\n<p>I&#8217;d suggest you take a backup of the DB first, as this isn&#8217;t supported by Microsoft.\u00a0 If you happen to be an organization who uses the Microsoft RAP service then you&#8217;ll get found out and it may invalidate your support contract.<\/p>\n<p>However, while this isn&#8217;t supported &#8211; powershell manipulation of the locale and language now is.\u00a0 So you would be better off following this example and using the information above to help debug your specific problem:<\/p>\n<p>http:\/\/www.parallelfun.com\/2013\/11\/sharepoint-set-locale-region-on-all-web.html<\/p>\n","protected":false},"excerpt":{"rendered":"<p>install SharePoint2013 Server 2013 in your native language &#8211; in my case English. Configure SharePoint for building Access Apps (http:\/\/social.technet.microsoft.com\/wiki\/contents\/articles\/12514.sharepoint-2013-access-services.aspx) Create a new Access App, test it as working Install a language pack (you should have done this first by the way &#8211; not after you had started using SharePoint but we do occasionally consume\/partner [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1,2],"tags":[],"_links":{"self":[{"href":"http:\/\/www.johntimney.com\/index.php?rest_route=\/wp\/v2\/posts\/188"}],"collection":[{"href":"http:\/\/www.johntimney.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.johntimney.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.johntimney.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.johntimney.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=188"}],"version-history":[{"count":1,"href":"http:\/\/www.johntimney.com\/index.php?rest_route=\/wp\/v2\/posts\/188\/revisions"}],"predecessor-version":[{"id":189,"href":"http:\/\/www.johntimney.com\/index.php?rest_route=\/wp\/v2\/posts\/188\/revisions\/189"}],"wp:attachment":[{"href":"http:\/\/www.johntimney.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=188"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.johntimney.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=188"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.johntimney.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=188"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}