GLADIATOR@MSFT

Adventures in Desktop, Application, and User State Virtualization

Browse by Tags

Related Posts
  • Blog Post: App-V 5: Application Troubleshooting: “Fly-by-Night” Error Messages

    To continue the discussion of application troubleshooting, I wanted to provide some clarification on a certain type of application failure. In a blog post a while back ( http://blogs.technet.com/b/gladiatormsft/archive/2013/05/15/app-v-process-exit-codes-and-why-they-matter-when-troubleshooting-virtual...
  • Blog Post: App-V 5: On Sequencing Using Tokenized Paths, PVAD’s, VFS, and VFS Write Mode

    When sequencing applications, you often never know how the application was written with regards to what paths are actually referenced via hard-coded paths or through tokenized, or well-known paths or KNOWNFOLDERIDS. In previous versions of App-V and Softgrid, these paths were referenced using %CSIDL...
  • Blog Post: App-V 5: Application Troubleshooting: On the Origins of an Error Message

    Have you ever been testing a virtualized application and it fails with a bizarre application error that is either extremely vague (unknown error) or coupled with some random hex code? Your first reaction usually is “Where’d that error come from?” That is a good reaction to have as it...
  • Blog Post: On the Art of Troubleshooting App-V Applications

    Lately I have been dealing with the big challenge of teaching something that I have become to know as more of an art than a science. That is, the troubleshooting of virtual applications not functioning correctly in App-V. I have seen many articles that walk through how someone was able to figure out...
  • Blog Post: App-V 5.0: On these 0xc0000142 errors and where they are coming from.

    "Where are these 0xc0000142 errors coming from in App-V 5.0?" There has been some chatter revolving around this generic application error that is happening with many LOB (Line of Business applications) running virtualized with App-V 5.0. You will also note that for a lot of these applications, this...
  • Blog Post: App-V: Process Exit Codes and why they matter when troubleshooting virtual applications

    In a previous blog post ( http://blogs.technet.com/b/gladiatormsft/archive/2013/04/27/on-the-art-of-troubleshooting-app-v-applications.aspx ) I discussed the “art” of troubleshooting virtual applications and mentioned the fact that there are a lot of custom recipe’s out on the Internet...
  • Blog Post: The Case of the Three Second Delay (a.k.a What is SFTDDE?)

    A while back I encountered an issue that forced me to become introduced to the DDE Launcher used by App-V (SFTDDE.)  A customer was encountering an issue where, no matter how much they tuned their terminal servers, even with pre-cached virtual applications; Office applications appeared to always have...
  • Blog Post: App-V 5: Useful Stuff for the App-V Professional (I hope!)

    So I’ve been receiving a lot of feedback on ways to enhance App-V toolkits for customers and their in-house troubleshooting. I’ve received usually two kinds of feedback on previous articles such as http://blogs.technet.com/b/gladiatormsft/archive/2013/11/13/app-v-on-operational-troubleshooting...
  • Blog Post: App-V 4.6: Why is SFTLP.EXE crashing and why can’t I troubleshoot it?

    I have encountered an interesting issue where a series of applications that have been virtualized with App-V 4.6 will fail due to an operational error. Ironically it has nothing to do with any kind of limits within App-V or is even related to the virtualization model of App-V. It happens because a key...
  • Blog Post: App-V: More on that Failed Office Add-in

    Continuing from my previous post a few days ago, let’s talk more about application errors when Office add-ins are virtualized. It is pretty easy to resolve most add-in issues with the right methodology. One of the first steps in my methodology is to first determine if the issue is related to the...