I’ve seen this a couple of times.  As IFS is a click-once application and the 2.0 folder seems to contain a cache of the downloaded IFS forms etc, you can get corruption/mismatches between the online app and the 2.0 folder.

It’s certainly the easiest way to solve the problem.

We get this from someone in our Apps10 environment at least weekly.  It looks like a file corruption in one or more of the client files which get downloaded into that folder, and when you delete that content IFS then re-downloads the client files the next time it runs.

There is also a Command Prompt command that can be run which deletes the IFS cache, but there is nothing wrong with what you are doing.  Here’s the command, which I think is case sensitive:

rundll32 dfshim CleanOnlineAppCache

HTH,

Nick

IFS IEE utilizes a Microsoft technology called ClickOnce. ClickOnce allows non-admin users to “install” applications into their %localappdata%\Apps\2.0 folder without admin credentials. This ClickOnce folder can become corrupt when updating files there or when running the same application from another environment (such as DEV, QA, and Production).

This problem is not specific to IFS but is seen in all ClickOnce products around the world. With enough technical and debugging skills, you could potentially track down the inconsistent file(s) / versions and manually fix them. However, this is potentially a significant task and not to be taken lightly. While inconvenient, clearing the folder is by far the simplest and fastest resolution.

Thank you to all for your feedback.

Clearing the 2.0 folder it is! 

This is a continual issue for many of our users! Is there a better solution?