• Twitter
  • LinkedIn
  • RSS Feed
  • Subscribe via Email

Today’s Fixed App-V Apps!

Written by Dan Gough. Posted in App-V v5.x

If you didn’t know, I spend most of my days sequencing and packaging applications, and fixing broken packages. This is just a quick post to detail two App-V 5 apps I’ve fixed today, perhaps the information may be of use if you encounter similar issues on the front line!

Access 2007

This customer had Office 2007 on the base and Access 2007 deployed via App-V so that they could control who had ‘access’ to it (badoom-tish). All worked fine until you tried to export some data to Excel, where Excel would refuse to load with an ‘out of memory’ error. It turns out that Excel just flat out refused to open inside the virtual environment of this package. I suspected that it was because this Access package had been sequenced on a clean machine, making various Office folders and registry keys set to override. Resequencing with Office 2007 already on the base resolved the issue.

In-house App

This in-house line of business application was located on a network share, and the App-V package was simply used to create a shortcut pointing to the exe on the network share. For some reason, it refused to connect to its database when run inside the virtual environment. Since the App-V package contained no files or registry entries, I decided to start my troubleshooting by disabling these virtual subsystems in the package config files. I started with the registry:

<Registry Enabled=”false“>

Hey presto, that worked, but I’m not going to pretend to know the reason why! But sometimes you just have to accept you’ve fixed it and move on, there’s plenty more broken apps needing my attention!

Beware When Sequencing Access Runtime!

Written by Dan Gough. Posted in App-V v5.x

Just a quick post to warn of something I encountered today. I had an application that required an older Access 2007 Runtime (Access 2013 was installed locally). The sequencer picked up Access 2007 as an application along with all of its filetype associations, which I duly deleted in the last tab of the sequencer before saving the package.

However these filetype associations still exist, and after publishing the application, Office 2013 triggers a time consuming self-repair when the user double-clicks on an mdb file.

The solution is to disable these FTA’s from within the configuration files; I could do this quickly by disabling the entire subsystem as my application did not register any. But if your application has some, you will need to comment out all of the Access related ones, which is no simple task as there are so many!

I applied this change to both DeploymentConfig and UserConfig xml files (as I did not know how the app was going to be published):

<FileTypeAssociations Enabled=”false“>

Whilst I was digging around in this file I also noticed an app path was registered. Trying to run msaccess.exe via Explorer’s run box tried to launch the virtual Access 2007 runtime rather than my local Access 2013. It would be possible to disable this entire subsystem also:

<AppPaths Enabled=”false“>

However my application had an app path I wished to keep so I just commented out the ones I did not require:

<!–Extension Category=”AppV.AppPath”>
<PATHEnvironmentVariablePrefix>[{ProgramFilesX86}]\Microsoft Office\Office12\</PATHEnvironmentVariablePrefix>
<ApplicationId>[{ProgramFilesX86}]\Microsoft Office\Office12\MSACCESS.EXE</ApplicationId>
<Extension Category=”AppV.AppPath”>

Remember these config files are not used by default when either publishing from the App-V Mangement Server or installing from the MSI so they will need to be specified. If you are using the MSI packages I have a solution to import the config files over here.


Fix for Mouse Freezes in App-V Apps (.NET 4.5.2 and WISPTIS.exe)

Written by Dan Gough. Posted in App-V v4.x, App-V v5.x

You may have seen Nicke Källén’s blog post about this issue recently along with some workarounds provided by the App-V community:


Microsoft have now however provided an official fix in the form of an update rollup to the .NET Framework, I recommend anyone using App-V apply this as soon as possible!


Obligatory “I am now an App-V MVP” Blog Post!

Written by Dan Gough. Posted in Miscellaneous

Well, I have been for 6 weeks now – I meant to post this a while back, but better late than never!

I am honoured to have received the Most Valuable Professional (MVP) for App-V from Microsoft. If you’ve never heard of the MVP program, you can find out more here. But in a nutshell, it’s a way for Microsoft to reward those who make top contributions to technical communities via conferences, forums and websites like this (among other ways). As a result, I now get to participate in regular product group interaction sessions with the App-V team where we get to give our feedback and hear about what’s coming in the future, and also get invited to the annual MVP Summit in Redmond. There are plenty of other benefits too, including free subscriptions to MSDN and Office365, and many vendors offer free licenses of their software to MVPs also!

Big thanks those that helped make this happen, including Nicke Källén, Rory Monaghan and Tim Mangan among others. Also to Colin Bragg, who not only first got me involved with App-V and also inspired me to start this site!

If you’re interested to know who the other App-V MVPs are around the world, click here.

Want to be an MVP? Here’s what it takes:

  • Start a blog site and post original content that helps others – not steal content from other people’s blogs like some have done to me and others!
  • Present at conferences and user groups, or organise your own!
  • Contribute to forums such as Technet and AppVirtGuru.
  • Produce (or assist in producing) additional written content such as books and whitepapers on your technical subject of expertise.
  • Engage with other MVPs and users through social media like Twitter and LinkedIn (not Facebook – that’s for sharing dumb clickbait articles and drunken photos!)