VERIFIED SOLUTION i

Resolve EngageOne Vault ERROR 50389: unable to process resource pack

Issue

Files fail to load into EngageOne Vault with the following error:
 
20:31:26 processing resource packs for guids [46663BD9F9C14E6981DF4EC145EF87A3] 
20:31:35 ERROR 50389: unable to process resource pack [error: internal error, problem guids: (null)] 
20:31:35 RmfUtil version is 5.04.0744
20:31:35 ERROR 10114: document build failed for file [work\09262013202914_somedocumentafp.drp]

Cause

This error can occur for more than one reason:

1) The most common reason this error will happen is because the Print stream was creating with a different version of the HIP than Vault has. 

2) Doc1 has been upgraded.  If Doc1 has been upgraded to a newer version without also upgrading Vault, the new HIP/HIM files may not be compatible with that version of Vault, resulting in this error.

3) In rare instances there may be read only files or files with the wrong permissions in the vault/server/distrib/default directory.

4) If the HIP or RPK was transferred off the host platform with end of line conversion and not in binary mode,

Resolution

UPDATED: March 28, 2017
The most likely resolution to these issues are below:

1) Whenever the HIP file, RPK file, or HIM file changes the new HIP/HIM/RPK must also be loaded to Vault.  When Vault ingests the file it checks to see if it has the matching version of the HIP/HIM/RPK, and if it doesn't have it, Vault will fail with this error.

2) Upgrade Vault to the same version or later than the Designer version that created the HIP, or apply a patch containing the RMFutil.dll files that will make the current version of Vault compatible with the new HIP files.  On Windows based Vault systems, the patch needs to be applied to the vault_install_path/server/ and vault_install_path/server/tools directory, after backing up the older versions of the files.

3) In rare instances there might be read only files or files with the wrong permissions in the vault_install_path/server/distrib/default directory.  Check for hidden system file "thumbs.db".  If such a file is in vault_install_path/server/distrib/default/ it can cause RMFutil to not be able to copy these files during the ingestion process, which can also cause this error message.

4) Even more rare, if the HIP or RPK was transferred off the host platform with end of line conversion and not in binary mode, RMFutil will think the resource pack is corrupt and fail.  The most likely cause is the end of lines having incorrect line terminators:
 
0D 0A <-> 0D 0D 0A
 
Environment Details