xxxxxx-xxxxxxxx-20000193
Since application virtualization is my current field of expertise, I might as well blog about it, right? OK!

The above noted gem of an error usually occurs in messy environments (Yes, I’m pointing a finger at you!) when someone tries to save sequencing or deployment time by editing or replacing OSD information in a live system. You end up with multiple SFT files with the same GUID and DC information that references to obsolete paths. In short, human error. Add to that a load distribution/balancing system that someone wrote in the spur of the moment and you end up with a number of very confusing problems to swim through.

Resolution

The best way I found to fix this was to test the sequence in an environment I trusted to be stable. Once it was confirmed that the sequence was fine, I removed the offending package (including clones and test versions) and applications from the SoftGrid Console. Verified the rights on the content source path, verified path information in the project (sprj) and OSD files and added the applications back to the system using the Import Applications function.

Mind you, if you choose to walk this path, make sure you test with a clean (enough) system. Clear any reference to the old package from the registry, unload and remove applications, clear the OSD cache (manually) and restart the SoftGrid Virtual Service Agent on the workstation before launching to test.