locked
Help 3 windows XP issue RRS feed

  • Question

  • Hello,

    We have created help 3 documentation and get stuck with the following issue:

    When we install help 3 on windows 7 everything works as expected, but when we run the same command on Windows XP SP2 we have a crash during installation.

    Here is the event log regarding the crash:

    "An error occurred while updating local content: Microsoft.Help.CacheLib.CacheLibCabSignatureException: The digital signature on file C:\Documents and Settings\All Users\Application Data\Microsoft\HelpLibrary\content\MyCompany\incoming\c9168d7b-2aa6-4d6a-bd63-d72d47228fd3\mycontent.cab could not be verified."

    "mycontent.cab" is signed with a valid certificate which hasn't expired yet.

    We are using the following command to install our help "C:\Program Files\Microsoft Help Viewer\v1.0\HelpLibManager.exe" /product VS /version 100 /locale en-us /content "C:\Documents and Settings\All Users\Application Data\Microsoft\HelpLibrary" /sourceMedia "C:\Program Files\MyCompany\MyProduct \Documentation\myhelp.msha" Manifest file refers on the mycontent.cab mentioned before.

    Does anyone face with the same issue. What can you suggest?

    Vitaliy Korney

    Wednesday, June 15, 2011 4:00 AM

Answers

  • Both VS 10 SP1 (Help Viewer 1.1)?

    Tried using helpcontentsetup.msha file name instead of myHelp.msha?

    Make sure that the .mshc, .mshi and .cab files all have the same base file name otherwise the compile will fail.

    And this kind of certificate has been used previously on the test machine? ie. The machine understands this certificate?

    While you are replying I'll ask Paul O'Rear [MSFT] can comment.

    http://social.msdn.microsoft.com/Forums/en-US/devdocs/thread/adb79316-3358-45d6-84a7-f1f8047240a3

    Please also post how you are signing the file (command line) and anything else you think is relevant.

    Rob


    Rob Chandler Help MVP http://Helpware.net/ http://mshcmigrate.helpmvp.com/
    Wednesday, June 15, 2011 5:42 AM
    Moderator

All replies

  • Both VS 10 SP1 (Help Viewer 1.1)?

    Tried using helpcontentsetup.msha file name instead of myHelp.msha?

    Make sure that the .mshc, .mshi and .cab files all have the same base file name otherwise the compile will fail.

    And this kind of certificate has been used previously on the test machine? ie. The machine understands this certificate?

    While you are replying I'll ask Paul O'Rear [MSFT] can comment.

    http://social.msdn.microsoft.com/Forums/en-US/devdocs/thread/adb79316-3358-45d6-84a7-f1f8047240a3

    Please also post how you are signing the file (command line) and anything else you think is relevant.

    Rob


    Rob Chandler Help MVP http://Helpware.net/ http://mshcmigrate.helpmvp.com/
    Wednesday, June 15, 2011 5:42 AM
    Moderator
  • Hello Rob,

    Thank you for quick reply!

    >Both VS 10 SP1 (Help Viewer 1.1)?

    I've tried only on VS10 Help Viewer 1.0. And on my Windows 7 PC I didn't get this issue, even without SP1.

    I haven't tried with SP1, because I had some troubles with service pack after installing it. For example, if you install SP1 and then try to install Silverlight tools you won't be able to do that because installer don't detect Visual Studio with SP1. So, I've decided to avoid intalling SP1 until I need it.

    >Tried using helpcontentsetup.msha file name instead of myHelp.msha?

    Yes, it is really called "helpcontentsetup.msha".

    >Make sure that the .mshc, .mshi and .cab files all have the same base file name otherwise the compile will fail.

    I have "ps_docs.cab" with "ps_docs.mshc" inside.

    >And this kind of certificate has been used previously on the test machine? ie. The machine understands this certificate?

    We have bought our certificate from the next web-site "http://www.verisign.com/code-signing/index.html?tid=a_box" and actively using it.  In the properties of my signed cab I have found the following info:

    "Certificate status is ok", but on the first tabpage I see "Windows doesn't have enough information to verify this certificate".

    Our certificate "Issued by: VerySign Class 3 Code Signing 2010 CA".

    It seems that problems come from certificate, but I can't get why as we are using this certificate for our installation package signing and we had no problems with our certificate before.

    >Please also post how you are signing the file (command line) and anything else you think is relevant.

    Here is the command script we are using for signing:

    "C:\Program Files\Microsoft SDKs\Windows\v6.0\Bin\signtool.exe" sign /a /f "C:\Projects\Sign\<our_company>_private_key.pfx" /p <password> /t "http://timestamp.verisign.com/scripts/timstamp.dll" /v %1

    "C:\Program Files\Microsoft SDKs\Windows\v6.0\Bin\signtool.exe" verify /pa /v %1

    Many thanks,

    Vitaliy Korney

    Wednesday, June 15, 2011 8:08 AM
  • Hello Rob,

    Many thanks for your tip regarding certificate, we have found what was the cause of the problem:

    As soon as we configured or test machine to go to the internet certificate was verified successfully and we didn't get any crashes during the installation.

    Many thanks,

    Vitaliy Korney

    Wednesday, June 15, 2011 9:16 AM