Community Forums
Page 2 of 2 FirstFirst 12
Results 6 to 7 of 7

Thread: Patching limit

  1. #6
    Join Date
    Aug 2005
    Posts
    518
    Quote Originally Posted by gwesterfield View Post
    I am experiencing the same exact error, even when I don't add any new files. If all I do is change the version between the msi's I get the error. Also, the patch log has a ton of "INFO File Key: _(GUID) is newly added" logs which is what I think is accounting for the patch hitting the limit as you can see below. What I don't understand is all the files are 100% identitical and the only changes I have made to the ism is the version. Any idea what could be causing these new file keys to be added when there are no new files?

    INFO File Key: _54EA9BFC14E7710A5F19837CADA1E8CA is newly added
    PERF INFO: File Info Lookup Time: 0 ms
    INFO File Key: _DC3ECD300D578635A09A69FFE4D8B3DC is newly added
    PERF INFO: File Info Lookup Time: 0 ms
    INFO File Key: _E77E3757AA11E347958F54916D847290 is newly added
    PERF INFO: File Info Lookup Time: 0 ms
    INFO File Key: _2DED20C450A5C40DAE0B11D9DB43B19F is newly added
    PERF INFO: File Info Lookup Time: 0 ms
    INFO File Key: _2A5B77D2B5631605ABEEE34C34B6F7E1 is newly added
    PERF INFO: File Info Lookup Time: 0 ms
    INFO File Key: _1FD7C352264C433D907DEE909493A7B9 is newly added
    PERF INFO: File Info Lookup Time: 0 ms
    PERF INFO: V:\t\911\Prev1\AirWatch.msi 47216 ms
    PERF INFO: V:\t\Console FP1\9.1.1.3\Latest1\AirWatch.msi 47299 ms
    SCHEMA: Table: Patch has mismatched schema (or missing column) for: Header
    ERROR: Failed to execute view: 'File'
    ERROR: The Last Error Received is: 0x65b (1627)
    ERROR: The Last Error Received is: 1: 2210 2: \\?\C:\Users\GWESTE~1.VMW\AppData\Local\Temp\3\ISPE6B8.tmp\Prev1.MSI 3: 0
    This sounds like you may want to look into 2 things:

    1. "Best Practice" dynamic file links. (The default when created newly in any recent IS version--not the default if you're maintaining a project created a long time ago)
    2. The "Previous Package" setting in the release configuration. This tries to synchronize primary keys to avoid errors like you're mentioning.

    What's likely at play is that the legacy style dynamic file links are generating new primary keys every time you build. This isn't likely your only issue if you're generating patches:

    • files left behind on uninstall
    • when folders are removed, no files updated by the patch
    • patch file size is weirdly large
    Cary R.
    Configuration Engineer

  2. #7
    Join Date
    Jun 2017
    Posts
    2
    Quote Originally Posted by Cary R View Post
    This sounds like you may want to look into 2 things:

    1. "Best Practice" dynamic file links. (The default when created newly in any recent IS version--not the default if you're maintaining a project created a long time ago)
    2. The "Previous Package" setting in the release configuration. This tries to synchronize primary keys to avoid errors like you're mentioning.

    What's likely at play is that the legacy style dynamic file links are generating new primary keys every time you build. This isn't likely your only issue if you're generating patches:

    • files left behind on uninstall
    • when folders are removed, no files updated by the patch
    • patch file size is weirdly large
    Setting the "Previous Package" fixed the issue. I also went ahead and set all of my dynamically linked directories to the new "Best Practice" setting. Thanks for the help!!

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •