- The Language Of This Installation Package Is Not Supported By Your System While Uninstalling
- The Language Of This Installation Package Is Not Supported By Your System Office 2016
05-27-2010, 08:50 PM | #1 |
Guest | Language of this installation package is not supported by your sys I downloaded US English SharePoint Designer 2010 install from the Download Center (and again, from MSDN when I first started having issues). When I try to create a silent installation using the same method we used for Office 2007, I get the following error message: 'The language of this installation package is not supported by your system' If I just run setup, with the .msp in the updates folder it works fine (and installs silently), but the way we did it with 2007 was to run a cache-only setup first: C:sourcesetup.exe /config C:sourceSharePointDesigner.WWCacheOnly.xml .... and then run setup from the cache, as follows (obviously using the 2010 guid instead): 'C:MSOCacheAll Users{90140000-0017-0000-0000-0000000FF1CE}-Csetup.exe' /config c:sourceSharePointDesigner.WWconfig.xml The errror happens at this point (after a successful cache), when we try to run setup. Our systems have both US and Australian English as installed languages. I've installed Asian language support as this solved the problem for some users. I'm sure the files extracted correctly, too, as it wasn't in .iso format, but .exe and I used the /extract switch to grab the files. some people had reported this error when trying to run setup from incorrectly extracted .iso files. Any ideas? Here's the installation log: PERF: TickCount=1090234 Name=OBootStrapper::Run Description=Begin function Operating System version: 5.1.2600 Service Pack 3. Platform ID: 2 Running 32-bit setup on a 32-bit operating system. Command line: 'C:MSOCacheAll Users{90140000-0017-0000-0000-0000000FF1CE}-Csetup.exe' /config c:sourceSharePointDesigner.WWconfig.xml Parsing command line. Config XML file specified: c:sourceSharePointDesigner.WWconfig.xml Parsing config.xml at: c:sourceSharePointDesigner.WWconfig.xml Preferred product specified in config.xml to be: SHAREPOINTDESIGNER Logging type standard specified in config.xml. Log directory: C:Temp specified in config.xml Log file template: Microsoft Office SharePoint Designer Setup.log specified in config.xml Verify file signature in 'C:MSOCacheAll Users{90140000-0017-0000-0000-0000000FF1CE}-Csetup.exe' C:MSOCacheAll Users{90140000-0017-0000-0000-0000000FF1CE}-Csetup.exe is trusted. Verify file signature in 'C:MSOCacheAll Users{90140000-0017-0000-0000-0000000FF1CE}-COSETUP.DLL' C:MSOCacheAll Users{90140000-0017-0000-0000-0000000FF1CE}-COSETUP.DLL is trusted. Using setup controller dll at [C:MSOCacheAll Users{90140000-0017-0000-0000-0000000FF1CE}-COSETUP.DLL]. PERF: TickCount=1090500 Name=OBootStrapper::Run Description=Calling RunSetup PERF: TickCount=1090515 Name=RunSetup Description=Begin function Catalyst execution began: 05/27/2010 14:06:55. Parsing config.xml at: c:sourceSharePointDesigner.WWconfig.xml Preferred product specified in config.xml to be: SHAREPOINTDESIGNER Logging type standard specified in config.xml. Log directory: C:Temp specified in config.xml Log file template: Microsoft Office SharePoint Designer Setup.log specified in config.xml Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [disabled] for the [InstallExecutionMode] Searching for default versions of resource files under the folder [C:MSOCacheAll Users]. Found [1] resource files under the default folder. Running in [InstallExecutionMode]. Run from TEMP folder at [C:TempSetup0000078c]. Loaded resource file [C:TempSetup0000078cOSETUPUI.DLL] (CultureTag=en-US). Loaded Dll : C:MSOCacheAll Users{90140000-0017-0000-0000-0000000FF1CE}-COSETUP.DLL. Catalyst version is : 14.0.4755.1000 JobExecutionMode is InstallExecutionMode. Procedure SetProcessDPIAware is not found in USER32 Catalyst processor architecture check: The system is unknown Catalyst admin requirement check passed Catalyst setup running enviroment check: the current setup.exe is the only instance Catalyst Office 2003 Cache Integrity check. No corrupted cache found. System drive 'C:WINNT' has 28293 MB free space is more then required 100 MB Catalyst system drive free space check passed Check if Office is supported on Windows 5.1.2600 All OS requirement check passed Checking if CLSID_DOMDocument60 can be created. Checking the version of MSXML6. MSXML version check passed. Minimum required version is [6.10.1129], installed Version is [6.20.1103]. Parsing setup.xml file: C:MSOCacheAll Users{90120000-0010-0409-0000-0000000FF1CE}-Csetup.xml Xml Signature verification succeeded for C:MSOCacheAll Users{90120000-0010-0409-0000-0000000FF1CE}-Csetup.xml LIS: start parsing setup xml LIS: Package File Name = RosebudMUI.xml LIS: Package File Hash = 0287A5C5D3C001D1CAF924ACB57CAD9F LIS: Package File Size = 811 LIS: Package File Relative Cache Path = RosebudMUI.xml LIS: Package File Relative Source Path = RosebudMUI.xml LIS: Package File Name = RosebudMUI.msi LIS: Package File Hash = 3648D5B69F5E58A877E9771107A93F07 LIS: Package File Size = 49152 LIS: Package File Relative Cache Path = RosebudMUI.msi LIS: Package File Relative Source Path = RosebudMUI.msi LIS: Package File Name = RbudLR.cab LIS: Package File Hash = 190B04E9F2989F23D8137DD85AF06C1C LIS: Package File Size = 1581636 LIS: Package File Relative Cache Path = RbudLR.cab LIS: Package File Relative Source Path = RbudLR.cab LIS: Package File Name = Setup.xml LIS: Package File Hash = LIS: Package File Size = LIS: Package File Relative Cache Path = Setup.xml LIS: Package File Relative Source Path = Setup.xml LIS: finished parsing LIS package '{90120000-0010-0409-0000-0000000FF1CE}' Parsing setup.xml file: C:MSOCacheAll Users{90120000-0011-0000-0000-0000000FF1CE}-Csetup.xml Xml Signature verification succeeded for C:MSOCacheAll Users{90120000-0011-0000-0000-0000000FF1CE}-Csetup.xml LIS: start parsing setup xml LIS: Package File Name = Office64WW.xml LIS: Package File Hash = 3D97CD89EC26F6F3DF1844C442BED9BE LIS: Package File Size = 2310 LIS: Package File Relative Cache Path = Office64WW.xml LIS: Package File Relative Source Path = Office64WW.xml LIS: Package File Name = Office64WW.msi LIS: Package File Hash = 443BFBFD20C6200B2A3AA1A5578D789C LIS: Package File Size = 847872 LIS: Package File Relative Cache Path = Office64WW.msi LIS: Package File Relative Source Path = Office64WW.msi LIS: Package File Name = OWOW64WW.cab LIS: Package File Hash = D0D17FA309EE9EFC1B71AF61AE1255A3 LIS: Package File Size = 4151139 LIS: Package File Relative Cache Path = OWOW64WW.cab LIS: Package File Relative Source Path = OWOW64WW.cab LIS: Package File Name = ProPlusWW.xml LIS: Package File Hash = 6D4B39CECDFBD6D15B962ABABFB6D2DF LIS: Package File Size = 15813 LIS: Package File Relative Cache Path = ProPlusWW.xml LIS: Package File Relative Source Path = ProPlusWW.xml LIS: Package File Name = ProPlusWW.msi LIS: Package File Hash = E46C7F3F0A61B519DFFE94AC0019D5ED LIS: Package File Size = 15831552 LIS: Package File Relative Cache Path = ProPlusWW.msi LIS: Package File Relative Source Path = ProPlusWW.msi LIS: Package File Name = ProPlsWW.cab LIS: Package File Hash = 8A21415690A7108D85234A23563D86BF LIS: Package File Size = 236505785 LIS: Package File Relative Cache Path = ProPlsWW.cab LIS: Package File Relative Source Path = ProPlsWW.cab LIS: Package File Name = ID_00011.DPC LIS: Package File Hash = EA0C168D44E861D54E3A6840B166E8BE LIS: Package File Size = 1646 LIS: Package File Relative Cache Path = ID_00011.DPC LIS: Package File Relative Source Path = ID_00011.DPC LIS: Package File Name = setup.exe LIS: Package File Hash = 95B8A4245A6CD37D36E56FAE5A23E2B1 LIS: Package File Size = 463152 LIS: Package File Relative Cache Path = setup.exe LIS: Package File Relative Source Path = ..setup.exe LIS: Package File Name = osetup.dll LIS: Package File Hash = C0FEAA8B015DFA39963A2DC576EE4316 LIS: Package File Size = 6536992 LIS: Package File Relative Cache Path = osetup.dll LIS: Package File Relative Source Path = osetup.dll LIS: Package File Name = ose.exe LIS: Package File Hash = 5A432A042DAE460ABE7199B758E8606C LIS: Package File Size = 145184 LIS: Package File Relative Cache Path = ose.exe LIS: Package File Relative Source Path = ose.exe LIS: Package File Name = Setup.xml LIS: Package File Hash = LIS: Package File Size = LIS: Package File Relative Cache Path = Setup.xml LIS: Package File Relative Source Path = Setup.xml LIS: finished parsing LIS package '{90120000-0011-0000-0000-0000000FF1CE}' Error: Installation of this product requires operating system supplemental language support. Type: 54::NoSupportedCulture. Error: Installation of this product requires operating system supplemental language support. Type: 54::NoSupportedCulture. Error: Installation of this product requires operating system supplemental language support. Type: 54::NoSupportedCulture. Showing parent-less message Title: 'Setup Error', Message: 'The language of this installation package is not supported by your system. ' Message returned: 1 Catalyst execution finished: 05/27/2010 14:06:58. Return code: 30054. Exception caught: NoSupportedCulture. PERF: TickCount=1093671 Name=RunSetup Description=End function Sponsored Links |
The Language Of This Installation Package Is Not Supported By Your System While Uninstalling
- the language of this installation is not supported by your system If I just run the same command directly from same location (with a user having admin rights on local workstation) there is not a problem.
- If you install a language after you have imported Support Packages into your system, you may have overwritten new Support Package translations with obsolete translations. The language is then inconsistent. To correct the language data, you need to import the language part of the Support Package.
The Language Of This Installation Package Is Not Supported By Your System Office 2016
But when i unzip the setup file and try to install MOSS by using the command line '. Setup.exe /config config.xml' (for automating and customizing the installation), i get the following error: 'The language of this installation package is not supported by your system' The setup package downloaded and my server's locale is en-us.