Some Applications Fail to Sequence with Error Code 53256 / Unsupported UTF format

I recently worked on an issue sequencing an application with the Softgrid 4.1 SP1 and 4.2 Sequencer. After selecting a location to download the virtual environment (after the install was completed) an error would appear “SystemGuard download failed (error code 53256)”.

The sft-seq-log.txt would show the following:
[08/01/2007 16:51:38 VRB VFSX] SxS: Starting SxS public-to-private assembly conversion.
[08/01/2007 16:51:38 ERR VFSX] SxSPrivateAssembly::LoadConfigFile : Load failed.
[08/01/2007 16:51:38 ERR VFSX] SxSPrivateAssembly::LoadConfigFile : Load failed.
[08/01/2007 16:51:40 WRN VFSX] SxSPE::parseUTF : Unsupported UTF format for file Q:\MyApp\MyFile.dll (format # 3).
[08/01/2007 16:51:40 VRB RTSK] Failed to convert public SxS assemblies.
[08/01/2007 16:51:40 ERR RTSK] SystemGuard download failed (error code 53256).
[08/01/2007 16:51:40 ERR RTSK] SystemGuard download failed (error code 53256).

I found that the root cause of this specific problem (unique to the “Unsupported UTF format” error) is that we attempt to read the manifest in MyFile.dll and the manifest in that file is corrupt. A corrupt manifest in a file will only result in this error if the application you are installing contains SxS binaries. 

You can view or edit the manifest of any file with a PE editor.  I was able to workaround the issue by deleting the corrupt manifest from MyFile.dll after the application had installed but before I selected “Stop Monitoring”.  Obviously we don’t recommend modifying files of applications without contacting the manufacturer of the application for their guidance.

Comments (2)

  1. Admin_NS says:


    Are there any chance that you could instruct in how to find the corrupted manifest and how to remove it?


  2. Russ Slaten says:

    The sft-seq-log.txt contains the location of the file with the corrupt manifest.  To view a files manifest you must use a PE Editor (there are many available for download, just search for it).  It depends on the editor you choose, but the jist is that you open the file, find the manifest (it’s usually in the same area as the Icon information, but will be organized differently depending on the program you use), then either replace the corrupt information (non text characters) with valid xml information *or* delete the entire manifest.  Keep in mind that blanking out the manifest itself will not work.  You must either replace the bad data with good data or delete the *entire* manifest itself.