Long time reader, first time "asker"....
At my company we export data from SAS to excel, in XML file format. This exported file is saved to a UNC path and an ASP page on our intranet presents a link to this xml file. <a href="//unc/path/to/file.xml">
We are in the process to upgrade all our office installations to office365, and we have noticed that when office365 (streamed version of office2013) is installed on our computers we cannot open this XML file from the ASP page in excel any longer, it only
displays the xml file directly in IE. It did not do this when we had office 2010 installed, nor when we had local installations of office2013.
When installing office 365 the file association for .xml gets changed from "microsoft office XML viewer" (or something like it) to "Microsoft Application Virtualization Virtual Process Launcher" (wow.. thats a mouthful). and i think this is where the problem
lies. Microsoft AppV does not care about the header information in the xml file and thus reverts back to displaying directly in IE.
The file header of the exported file looks like such:
<Workbook
xmlns="urn:schemas-microsoft-com:office:spreadsheet"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:x="urn:schemas-microsoft-com:office:excel"
xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet"
xmlns:html="http://www.w3.org/TR/REC-html40">
<DocumentProperties xmlns="urn:schemas-microsoft-com:office:office">
...............................................
File associations for .xlsx and .xls and all the others are "Excel (Desktop)" according to "Control Panel\All Control Panel Items\Default Programs\Set Associations"
If i right click the file and save it locally to desktop or whatever (or go to the UNC path with Explorer), and then doubleclick it, the file opens in Excel as it should..
I have tried to set Excel as default program for .xml files but IE cares not about that
Oh i probaby should say we are running windows 7 PRO x64 on a VDI environment, IE 11 is installed.
What more information can i give at this moment?!?!..
dunno..
Anyhow.. Does anyone have an idea on how we can get this working again?!
a workaround would be to tell the users to go to the unc-path and doubleclick the file, but you know.. end users... change is not something they are comfortable with...