[will not fix] - Compilation error LGHT0311

Discussion in 'Submit: Bug Reports' started by yoavain, March 8, 2012.

    • Premium Supporter

    yoavain MP Donator

    System Specs
    Hi,

    I'm trying to run the MSBUILD_Rebuild_Release_Setup.bat and I receive the following errors:

    Code (text):
    C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\Client\ClientFeatures.wxs(2711): error LGHT0311: A string was provided with characters that are not available in the specified database code page '1252'. Either change these characters to ones that exist in the database's code page, or update the database's code page by modifying one of the following attributes: Product/@Codepage, Module/@Codepage, Patch/@Codepage, PatchCreation/@Codepage, or WixLocalization/@Codepage. [C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\MP2-Setup.wixproj]
    C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\Client\ClientFeatures.wxs(3044): error LGHT0311: A string was provided with characters that are not available in the specified database code page '1252'. Either change these characters to ones that exist in the database's code page, or update the database's code page by modifying one of the following attributes: Product/@Codepage, Module/@Codepage, Patch/@Codepage, PatchCreation/@Codepage, or WixLocalization/@Codepage. [C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\MP2-Setup.wixproj]
    C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\Client\ClientFeatures.wxs(3431): error LGHT0311: A string was provided with characters that are not available in the specified database code page '1252'. Either change these characters to ones that exist in the database's code page, or update the database's code page by modifying one of the following attributes: Product/@Codepage, Module/@Codepage, Patch/@Codepage, PatchCreation/@Codepage, or WixLocalization/@Codepage. [C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\MP2-Setup.wixproj]
    C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\Client\ClientFeatures.wxs(3557): error LGHT0311: A string was provided with characters that are not available in the specified database code page '1252'. Either change these characters to ones that exist in the database's code page, or update the database's code page by modifying one of the following attributes: Product/@Codepage, Module/@Codepage, Patch/@Codepage, PatchCreation/@Codepage, or WixLocalization/@Codepage. [C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\MP2-Setup.wixproj]
    C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\Client\ClientFeatures.wxs(3665): error LGHT0311: A string was provided with characters that are not available in the specified database code page '1252'. Either change these characters to ones that exist in the database's code page, or update the database's code page by modifying one of the following attributes: Product/@Codepage, Module/@Codepage, Patch/@Codepage, PatchCreation/@Codepage, or WixLocalization/@Codepage. [C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\MP2-Setup.wixproj]
    C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\Client\ClientFeatures.wxs(3677): error LGHT0311: A string was provided with characters that are not available in the specified database code page '1252'. Either change these characters to ones that exist in the database's code page, or update the database's code page by modifying one of the following attributes: Product/@Codepage, Module/@Codepage, Patch/@Codepage, PatchCreation/@Codepage, or WixLocalization/@Codepage. [C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\MP2-Setup.wixproj]
    C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\Client\ClientFeatures.wxs(3680): error LGHT0311: A string was provided with characters that are not available in the specified database code page '1252'. Either change these characters to ones that exist in the database's code page, or update the database's code page by modifying one of the following attributes: Product/@Codepage, Module/@Codepage, Patch/@Codepage, PatchCreation/@Codepage, or WixLocalization/@Codepage. [C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\MP2-Setup.wixproj]
    Done Building Project "C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\MP2-Setup.wixproj" (Rebuild target(s)) -- FAILED.
    Done Building Project "C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup\MP2-Setup.wixproj.metaproj" (Rebuild target(s)) -- FAILED.
    Done Building Project "C:\Dev\MediaPortal-2\MediaPortal\Setup\MP2-Setup.sln" (Rebuild target(s)) -- FAILED.
     
    Build FAILED.
     
    Googling it suggests it has something to do with MSI limitation because of the encoding of the file ClientFeatures.wxs. I guess my windows localization (Hebrew, 1252) is the reason it does not work for me, but works for you guys.

    Do you know of any workaround? (maybe something in command-line or maybe you could change the naming of these files)

    Thanks,
    Yoav
    yoavain, March 8, 2012
    Share #1
    • Team MediaPortal

    Smeulf Test Group

    System Specs
    You have downloaded MP2 sources in a zip file from GitHub right ?

    We have some filename transcoding problems with Git when a zip is grabbed. The problematic files are some german TV logos provided by SlimTV plugin containing non english chars.

    The best workaround is to pull git directly with a dedicated tool. Please take a look at our WIKI page about git.

    The building of the installer itself is not the cause.

    Cheers.
    Smeulf, March 8, 2012
    Share #2
    • Premium Supporter

    yoavain Thread Starter MP Donator

    System Specs
    Thanks for your quick reply. However, I am using msysgit and TortoiseGit. I've pulled the code using 'git pull'
    yoavain, March 8, 2012
    Share #3
    • Team MediaPortal

    Smeulf Test Group

    System Specs
    Arg, that's not the answer I was waiting for! :confused:

    Anyway, building the installer is only needed if you want to try some changes in the MSI. And if you can do such changes, maybe you could be able to provide a patch ? ;)

    Also, you should be able to use a fresh build of MP2 with the binaries in the "bin" folder. Ths installer is not needed to use MP2.

    Not sure it totally answers your question, but at the moment I don't have any idea how to make the setup build process work on your computer, and I can't test it...

    I'm curious to see how the files referenced at lines 2711, 3044, .... of ClientFeatures.wxs looks like. Can you show us ?

    Cheers.
    Smeulf, March 8, 2012
    Share #4
    • Premium Supporter

    yoavain Thread Starter MP Donator

    System Specs
    This is how I see it in a text editor:
    Code (text):
    2711: <File Id="filF97663018B31D7236644A63214AD1075" KeyPath="yes" Source="$(var.SourceClientPlugins)\SlimTvClient\Skin\default\images\channellogos\Bayerisches FS Sd.png" />
    3044: <File Id="fil692BF4C0E85FC8976D1C9F6E35747272" KeyPath="yes" Source="$(var.SourceClientPlugins)\SlimTvClient\Skin\default\images\channellogos\MDR THRINGEN.png" />
    3431: <File Id="fil559F017F6DB873757123170E003B2F75" KeyPath="yes" Source="$(var.SourceClientPlugins)\SlimTvClient\Skin\default\images\channellogos\sky fuball bundesliga.png" />
    3557: <File Id="filB61E61D76FAF10BF8D0886588A80931B" KeyPath="yes" Source="$(var.SourceClientPlugins)\SlimTvClient\Skin\default\images\channellogos\TeleZri.png" />
    3665: <File Id="filD7E892B34FA101E4AECDA9C92C8943E6" KeyPath="yes" Source="$(var.SourceClientPlugins)\SlimTvClient\Skin\default\images\channellogos\WDR Dsseldorf.png" />
    3677: <File Id="fil5D896884441B3E8A112CD1B59971F923" KeyPath="yes" Source="$(var.SourceClientPlugins)\SlimTvClient\Skin\default\images\channellogos\WDR Kצln.png" />
    3680: <File Id="filE99DA18165BCE5B1B11C79E8EBCE39D9" KeyPath="yes" Source="$(var.SourceClientPlugins)\SlimTvClient\Skin\default\images\channellogos\WDR Mnster.png" />
    The file in hex view starts with EF BB BF (UTF-8).
    yoavain, March 8, 2012
    Share #5
    • Like Like x 1
    • Premium Supporter

    yoavain Thread Starter MP Donator

    System Specs
    I just wanted to see if I can build the installer by myself. The Client/Server compiles correctly.
    Anyway, wanted to report this so if there's a solution or workaround, others can benefit from it...
    Thanks anyway.
    yoavain, March 8, 2012
    Share #6
    • Team MediaPortal

    Smeulf Test Group

    System Specs
    Smeulf, March 9, 2012
    Share #7
    • Like Like x 1
    • Team MediaPortal

    Albert MP2 Developer

    IIRC the setup build program builds a setup from the contents in the Bin/..../Release/.../MP2-Client and MP2-Server.
    If there are problems with the SlimTV plugin, you can just remove the plugin directory from the MP2-Client/Plugins folder to exclude it from the installer.
    Albert, March 9, 2012
    Share #8
    • Like Like x 1
    • Team MediaPortal

    Smeulf Test Group

    System Specs
    Also SlimTVClient is not a part of the "basic" MP2 distribution. It will be shipped as a separate plugin. Maybe we should exclude it from the standard setup building once for all (no offence Morpheus ;)) and have a specific setup for this plugin ?

    Cheers.
    Smeulf, March 9, 2012
    Share #9
    • Team MediaPortal

    Albert MP2 Developer

    Well, unfortunately (or fortunately?), the build script builds whatever is currently located in the Release folder, so it's always a manual step to build the Release version of MP2 before the setup can be created. The good thing is that if you want to build a custom version, you can just build the Release version and then modify it before building the setup.
    I think yoavain just had the SlimTVClient compiled in the Release folder before he built the setup.
    Albert, March 10, 2012
    Share #10

Share This Page

Users Viewing Thread (Users: 0, Guests: 0)

Running the latest version?

V1.3.0 FINAL - released March 2013
Releasenews | Download
Changelog | Requirements
MediaPortal Media Center

Features | Screenshots
Documentation
MediaPortal Bugtracker
MediaPortal RSS Feeds

windows media center News & Blogs
htpc P&S: New
htpc Documentation
htpc Forum
htpc P&S: Updated
htpc Bugtracker
HTPC
Team-MediaPortal
 
About
Contact |  Press
Partners