3 Replies Latest reply on Jul 30, 2009 12:31 AM by AchimBock

    coult repair corrup filepackage

    B.Marxer Expert
      Hallo

      Ich habe ein Problem. Bei der Ausführung eines Softwaresets erhalte ich bei zwei Komponenten diese Meldung. Zuvor habe ich diese beiden Komponenten geändert. Revision angelegt etc. Sie sind auch distributiert etc.

      Das NISRV32-LOG meint dazu:

      11:22:45.390 2      FPS.dll: File 'CAM_MAN\MAN32_II\Local_Standard\APPLIC.MB' is corrupted. File is missing or the file size or date is wrong.
      11:22:45.390 2      FPS.dll: On disk  : Date = 24.07.2009 - 09:15:33, Size = 192512
      11:22:45.390 2      FPS.dll: Should be: Date = 16.07.2009 - 14:40:12, Size = 192512

      resp.

      11:22:44.109 2      FPS.dll: File 'Script.inc' is corrupted. File is missing or the file size or date is wrong.
      11:22:44.125 2      FPS.dll: On disk  : Date = 24.07.2009 - 09:15:32, Size = 472
      11:22:44.125 2      FPS.dll: Should be: Date = 16.07.2009 - 12:33:21, Size = 472

      Im Paket sind aber die korrekte File vom 16.07.2009 gepackt.

      Das File scheint immer das Datum an dem das Paket verteilt wird zu erhalten.

      Kann mir da jemand weiterhelfen ich sollte dieses Paket dringend verteilen!!!

      Danke!
        • 1. Re: coult repair corrup filepackage
          B.Marxer Expert
          Hat hier wirklich niemand eine Idee?

          Aus irgend einem Grund erhält dieses File immer ein aktuelles Datum. Wenn ich allerdings dieses File von Hand in den Repository-Cache kopiere wird das Paket korrekt ausgeführt. Es scheint also dass beim Cachen des Paketes etwas schief läuft.

          Hier nochmals ein Auszug aus dem LOG:


          14:27:01.482 2     Checking Prerequisites of Job JOB:POLICYINSTANCE.98973...
          14:27:01.685 2      Passed PrerequisitesCheck for Job JOB:POLICYINSTANCE.98973 ...
          14:27:01.701 2     Preparing Run of Job JOB:POLICYINSTANCE.98973...
          14:27:01.701 1      SWMSRT: Checking if policies should run for the trigger 'Start of script'.
          14:27:01.717 2      SwmsTpExtenderScript: Making Components available for Package ESCRIPTPACKAGE.39156:
          14:27:01.732 2      SwmsTpExtenderScript: Making Components available for {16D1595C-1F6A-4138-9486-419B70ED3ACA}
          14:27:01.748 2       SWMSClntLib: Making file package available
          14:27:01.764 1        SWMSClntLib: Package must be installed from cache.
          14:27:01.779 1        FPSClnt.dll: Effective revision to make available is 'R1'.
          14:27:01.795 1      FPS.dll: --------------- FpsOpenFilePackage interface called ---------------
          14:27:01.826 2      FPS.dll: File package is opened.
          14:27:01.842 1      FPS.dll: --------------- FpsOpenFilePackage finished ---------------
          14:27:01.842 1      FPSClnt.dll: --------------- FpsClientInvalidateCorruptedPackage interface called ---------------
          14:27:01.858 1      FPS.dll: --------------- FpsCheckPackageConsistency interface called ---------------
          14:27:02.296 2      FPS.dll: File 'CAM_MAN\MAN32_II\Local_Standard\APPLIC.MB' is corrupted. File is missing or the file size or date is wrong.
          14:27:02.311 2      FPS.dll: On disk  : Date = 27.07.2009 - 12:24:28, Size = 192512
          14:27:02.343 2      FPS.dll: Should be: Date = 16.07.2009 - 14:40:12, Size = 192512
          14:27:02.390 2      FPS.dll: File package files aren't consistent with FPI. Missing files: 0, corrupted files: 1
          14:27:02.405 1      FPS.dll: --------------- FpsCheckPackageConsistency finished ---------------
          14:27:02.421 1      FPSClnt.dll: --------------- FpsClientInvalidatePackage interface called ---------------
          14:27:02.484 1      FPSClnt.dll: --------------- FpsClientInvalidatePackage finished ---------------
          14:27:02.499 1      FPSClnt.dll: --------------- FpsClientInvalidateCorruptedPackage finished ---------------
          14:27:02.515 2      FPS.dll: Closing the file package '\\?\C:\Program Files\Common Files\enteo\RepositoryCache\8260\rev\5\'.
          14:27:02.530 E      Warning (Module:SWMSRT, Severity:0x03): FilePackage of Job JOB:POLICYINSTANCE.98973 is corrupt
          14:27:02.577 1       SWMSRT: Trying to make FilePackage available for Job JOB:POLICYINSTANCE.98973 now
          14:27:02.609 0        FPSClnt.dll: Failed to resolve depot root directory.
          There is no offline installation media registered.
          14:27:02.624 0        FPSClnt.dll: Failed to resolve depot with ID 2 or repository with ID 65956.
          There is no offline installation media registered.
          14:27:02.671 2        SWMSClntLib: Making file package available
          14:27:02.687 1         SWMSClntLib: Package must be installed from cache.
          14:27:02.703 1         FPSClnt.dll: Effective revision to make available is 'R5'.
          14:27:03.673 2       SwmsTpExtenderScript: Making Components available for Package ESCRIPTPACKAGE.39156:
          14:27:03.704 2       SwmsTpExtenderScript: Making Components available for {16D1595C-1F6A-4138-9486-419B70ED3ACA}
          14:27:03.735 2        SWMSClntLib: Making file package available
          14:27:03.751 1         SWMSClntLib: Package must be installed from cache.
          14:27:03.767 1         FPSClnt.dll: Effective revision to make available is 'R1'.
          14:27:03.798 1       FPS.dll: --------------- FpsOpenFilePackage interface called ---------------
          14:27:03.829 2       FPS.dll: File package is opened.
          14:27:03.829 1       FPS.dll: --------------- FpsOpenFilePackage finished ---------------
          14:27:03.845 1       FPSClnt.dll: --------------- FpsClientInvalidateCorruptedPackage interface called ---------------
          14:27:03.861 1       FPS.dll: --------------- FpsCheckPackageConsistency interface called ---------------
          14:27:03.876 2       FPS.dll: File 'CAM_MAN\MAN32_II\Local_Standard\APPLIC.MB' is corrupted. File is missing or the file size or date is wrong.
          14:27:03.892 2       FPS.dll: On disk  : Date = 27.07.2009 - 12:27:03, Size = 192512
          14:27:03.892 2       FPS.dll: Should be: Date = 16.07.2009 - 14:40:12, Size = 192512
          14:27:03.907 2       FPS.dll: File package files aren't consistent with FPI. Missing files: 0, corrupted files: 1
          14:27:03.923 1       FPS.dll: --------------- FpsCheckPackageConsistency finished ---------------
          14:27:03.939 1       FPSClnt.dll: --------------- FpsClientInvalidatePackage interface called ---------------
          14:27:03.986 1       FPSClnt.dll: --------------- FpsClientInvalidatePackage finished ---------------
          14:27:04.001 1       FPSClnt.dll: --------------- FpsClientInvalidateCorruptedPackage finished ---------------
          14:27:04.017 2       FPS.dll: Closing the file package '\\?\C:\Program Files\Common Files\enteo\RepositoryCache\8260\rev\5\'.
          14:27:04.033 E       Warning (Module:SWMSRT, Severity:0x03): FilePackage of Job JOB:POLICYINSTANCE.98973 is corrupt
          14:27:04.158 E      Warning (Module:Main, Severity:0x03): Preparing Run of Job JOB:POLICYINSTANCE.98973 failed

          14:27:04.205 E     Warning (Module:SwmsTpExtenderCMP, Severity:0x03): Run of at least one Component failed
          14:27:04.236 1    SwmsTpExtenderCMP: Checking State of SwSet
          14:27:04.424 E     Warning (Module:SwmsTpExtenderCMP, Severity:0x03): Mandatory Component-PolicyInstance POLICYINSTANCE.98969 has State Failed
          14:27:04.455 E     Warning (Module:SwmsTpExtenderCMP, Severity:0x03): Mandatory Component-PolicyInstance POLICYINSTANCE.98973 has State Failed
          14:27:04.486 E    Warning (Module:SwmsTpExtenderCMP, Severity:0x03): A mandatory Component-PolicyInstance has State failed
          14:27:04.502 E    Warning (Module:SWMSRT, Severity:0x03): Installation or Uninstallation of Package ESCRIPTSOFTWARESET.39255 (Benz CAM Management - CAM Manager) via PolicyInstance POLICYINSTANCE.98974 failed!
          14:27:04.627 E    Warning (Module:Main, Severity:0x03): Run of Job JOB:POLICYINSTANCE.98974 failed
          14:27:04.659 2   Cleaning up Run of Job JOB:POLICYINSTANCE.98974...
          14:27:04.674 1    SWMSRT: Checking if policies should run for the trigger 'Terminated script'.
          14:27:04.690 E     Warning (Module:SWMSClntLib, Severity:0x03): Failed to read package id.
          14:27:04.706 2     SWMSClntLib: Failed to read package respository id.
          14:27:04.721 E     Warning (Module:SWMSClntLib, Severity:0x03): Failed to retrieve ICDB id for repository.
          The requested container could not be found.

          14:27:04.752 E     Warning (Module:SWMSClntLib, Severity:0x03): Could not read package properties to make files available
          14:27:04.768 1    SWMSRT: Could not clean up Files of Job JOB:POLICYINSTANCE.98974
          14:27:04.784 2    SWMSRT: Handling Reboot
          14:27:04.799 2      SWMSRT: Reboot not allowed: Job failed or undone
          14:27:04.799 1      System reboot flag cleared
          14:27:04.815 1      System reboot flag cleared
          14:27:04.831 2    Cleaned up Run of Job JOB:POLICYINSTANCE.98974 successfully

          • 2. Re: coult repair corrup filepackage
            B.Marxer Expert
            Hallo

            Ich kenne den Grund für dieses Problem nicht aber es ist für mich im Moment erledigt.
            Ich habe die Petroffenen Pakete nun komplett neu erstellt und nun funkionieren sie "wieder".
            • 3. Re: coult repair corrup filepackage
              AchimBock Apprentice
              Hallo Brian,

              falls das Problem nochmals auftritt, mach bitte einen Call auf. Aus der Entwicklung habe ich folgenden Kommentar bekommen:

              "Hi Achim, Das Problem kenne ich noch nicht. Was seltsam ist, dass einmal Revision 1 und dann wieder Revision 5 in den Logs auftaucht. Auch seltsam ist, dass der Timestamp der Datei im Cache sich ändert. Um mehr zu sagen, müsste man das komplette Paket vom Depot (install) und den RepositoryCache haben. Auch interessant wäre, was jetzt wirklich zugewiesen ist. Vermutlich Revision 5. Am besten einen Call aufmachen. Sorry."

              Es gibt noch die Vermutung, daß das Problem evtl. dann auftritt, wenn auf dem Computer das Paket schon mal als "Pilotinstallation" (also nicht freigegeben) zugewiesen war und dann später nochmals geändert und upgedatet wurde.

              Viele Grüße,

              Achim Bock
              frontrange solutions