VERIFIED SOLUTION i
X

error | resource pack for guid could not be found

Issue

Customer obtained the message error | resource pack for guid could not be found when trying to add an old file back into vault that had been previously removed via the .REMOVE process.

Customer performed the following steps to obtain the error:

REMOVING FILE
20120324061324-vltfact-17363-bch194-fa0-ps-c0f50a0275aa11e18ddbba64cb5b0000.jrn
The extension "jrn" is changed to "remove" and the file is placed in d:\data\process
The file has been removed

Re-loading  the file to eVault.
Place the “jrn” in d:\data\work
Place the “drp” in d:\data\process

LOG:
13:35:46 <connection1> notice.cacheflush request
13:35:46 <connection1> notice.cacheflush returned, elapsed [0]
13:40:06 building [D:\Data\work\20120324061324-vltfact-17363-bch194-fa0-ps-c0f50a0275aa11e18ddbba64cb5b0000.drd] profile [BSCSIXINV_Pfile] document build engine [xmljournal]
         0    10   20   30   40   50   60   70   80   90   100
         |    |    |    |    |    |    |    |    |    |    |
         XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
13:40:07 [D:\Data\work\20120324061324-vltfact-17363-bch194-fa0-ps-c0f50a0275aa11e18ddbba64cb5b0000.drd] has been successfully built, [439] documents, [1741] pages
13:40:07 processing resource packs for guids [7EAED27E92524418B610FE7546E5E7A3]
13:40:07 ERROR 50384: unable to process resource pack [error: resource pack for guid could not be found, problem guids: 7EAED27E92524418B610FE7546E5E7A3]
13:40:07 RmfUtil version is 6.0.687.0
13:40:07 document build suspended for file [D:\Data\work\20120324061324-vltfact-17363-bch194-fa0-ps-c0f50a0275aa11e18ddbba64cb5b0000.drp]
 

Cause

The error:

13:40:07 ERROR 50384: unable to process resource pack [error: resource pack for guid could not be found, problem guids: 7EAED27E92524418B610FE7546E5E7A3]

is typically caused because the HIP file that was used to create the job is missing from the vault/server/resource directory.  That was the case here, but what was surprising was that the resource process needed the HIP file at all once the DRP was already created as it was in this example.

Resolution

UPDATED: September 26, 2017


If the customer uses the .REMOVE / .REINSTATE process instead of the process they outlined above, then the HIP file is not necessary and the job .REISTATES successfully.

Root cause is the missing HIP file.  If they can provide the missing HIP file, then either method of adding the file back will work.

Environment Details

Product Feature: Loader

Operating System: Windows 2008 64bit

Database: Not stated

Configuration: Not stated
 

Downloads

  • No Downloads