Item 21 of 61 Previous | Next

2
Vote

Installation of SharePoint Foundation fails due to missing HKLM : InstalledLanguages key

description

Installation of SPF fails with an error message that a regkey InstalledLanguages cannot be found.
this is apparently not created during SPF Installation but is assumed to exist in the InstallLanguagePacks function

proposal for correction :
Function InstallLanguagePacks([xml]$xmlinput)
{
WriteLine
#Get installed languages from registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\InstalledLanguages)
# Offending line
#$InstalledOfficeServerLanguages = (Get-Item "HKLM:\Software\Microsoft\Office Server\14.0\InstalledLanguages").GetValueNames() | ? {$_ -ne ""}

# JJ.1 Updated to work with SP2010 Foundation that does not set language Keys on install
$KeyIL = Get-Item "HKLM:\Software\Microsoft\Office Server\14.0\InstalledLanguages" -EA 0
if ($KeyIL -ne $null ) {
$InstalledOfficeServerLanguages = $KeyIL.GetValueNames() | ? {$_ -ne "" }
} else {
$InstalledOfficeServerLanguages = $null
}

No files are attached

comments

tlyczko wrote Apr 26 at 12:31 PM

Jos, would you be willing/able to share your installer??
Thank you, Tom

JosVerlinde wrote Apr 26 at 6:41 AM

Hi Tom,

We have created our own branch of AutoSPInstallar thus far, that has a number of other changes for SPF and 100% hands-off unattended setup.

I'll contact Brian to see how the relevant bts of this can be brought back into codeplex

tlyczko wrote Apr 25 at 7:21 PM

Has any of this been put into the actual application itself??
Thank you, Tom

JosVerlinde wrote Feb 22 at 8:30 AM

Well as SharePoint contains SPF its not that surprsing. I have found that SPF stores the language info in another key and notation , and have built that into a new helper function as that language detection is called multiple times from various sections.

In addition I have made a number of other changes to several of the support functions and have a different version of the config.xml (config-spf.xml) as well .

the only remaining bug that i am aware of is an inforrect logic in the search provisioning if that is set to false in the input file that I have not yet resolved.

So 3 changes thus far.
please let me know how you would like me to share this.

brianlala wrote Feb 22 at 1:54 AM

Hmm this is interesting because I've made no efforts myself to make the script compatible with SharePoint Foundation at all :)
I presume you've made other customizations as well in order to support SPF? Are you having success with it? And how much did you have to deviate from the original script?

Thanks,
Brian