Solved

DOCX File Open via ie9 fails only in VMWare View 4.6 VDI

Posted on 2012-03-14
6
446 Views
Last Modified: 2012-06-21
We are experiencing an unusual failure of MS Word 2010 failing to open docx file from ie9.
Example:
Google JaneDow.DOCX, click on the link to open the file (or just any docx file on the internet).

Here is what happens in VDI (VMWare View 4.6, with Persistent drive):
Windows/ie prompt asks:  "What would you like to do with the ...docx file?"
Click on OPEN
Microsoft Word windows pops with scrawling messages and moving bar from left to right:
first: "Microsoft Word has stopped working.  Windows checking for solution..."
then: "Trying to recover your information"
then: window closes and nothing happens.
However, if one opens WORD at this point, the document recovers and is shown.

If word was already opened, the same sequence happens, only it ends with:
"Microsoft Word has stopped working", [Close Program] button only option to click, and Word closes. Then, if opened, the docx appears.

The same site from a normal workstation, Word simply opens the docx same if already Word is opened or not.

Setup:
VMWare View 4.6
VDI with persistent drive (user folder is redirected to drive P:)
VDI also configured for separate drive for windows/vmware temporary files. that is, this drive gets purged on reboot.
Windows 7 Thin PC
IE version 9.0.4


Any ideas?
0
Comment
Question by:InWoods
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
6 Comments
 
LVL 2

Expert Comment

by:EvertG
ID: 37720836
already tried to change the User Account Control Settings ?
Has before some issues with those settings combined with word.
0
 

Author Comment

by:InWoods
ID: 37720983
Thanks, UAC is already set to lowest level:  Do Not Notify.
0
 

Author Comment

by:InWoods
ID: 37724902
Update:
Had a thought and launched the Base PC for the View Pool, the template if you will.  This (virtual) workstation has nothing to do with VIEW and, besides being a VM, not match to do with VMWare.  I proved later by running the same test on regular laptop loaded with ThinPC.

When Word is called from IE to open a DOC file (NOT DOCX), it needs to translate it to DOCX.
DOC to DOCX translation fails when called from IE on ThinPC’s.  Regardless of on or off domain.
Example:  google “jonedoe.docx” – this is actually NOT a docx! But a DOC file, and it fails.

When Word is called from IE to open a DOCX, not translation occurs and it opens it up fine.
Example: go to – http://plone.scottsdalecc.edu/career/sample-ws-jane-doe-resume.docx/view and open the sample file.
This is an actual DOCX file.  Works fine!

So at this point I narrowed it down to ThinPC/Office 2010 installation.

Furthermore:  for every attempt to open such file form internet or intranet, you get this application event viewer error:

Log Name:      Application
Source:        Application Error
Date:          3/15/2012 8:38:35 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     ComputerName
Description:
Faulting application name: WINWORD.EXE, version: 14.0.6024.1000, time stamp: 0x4d83e310
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0xc1c
Faulting application start time: 0x01cd02b0e8b14f3a
Faulting application path: C:\Program Files\Microsoft Office\Office14\WINWORD.EXE
Faulting module path: unknown
Report Id: 291457aa-6ea4-11e1-b487-00505687001a
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2012-03-15T13:38:35.000000000Z" />
    <EventRecordID>5350</EventRecordID>
    <Channel>Application</Channel>
    <Computer>ComputerName</Computer>
    <Security />
  </System>
  <EventData>
    <Data>WINWORD.EXE</Data>
    <Data>14.0.6024.1000</Data>
    <Data>4d83e310</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>00000000</Data>
    <Data>c1c</Data>
    <Data>01cd02b0e8b14f3a</Data>
    <Data>C:\Program Files\Microsoft Office\Office14\WINWORD.EXE</Data>
    <Data>unknown</Data>
    <Data>291457aa-6ea4-11e1-b487-00505687001a</Data>
  </EventData>
</Event>


Any ideas?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Accepted Solution

by:
InWoods earned 0 total points
ID: 37778109
Got an answer from MS:  ThinPC was not ment to be used with Office.  Haaa, but it works!  only for that one flow....

here is the tread for the case:

http://social.technet.microsoft.com/Forums/en-US/word/thread/03af13be-caf3-4f77-8ade-8d2aa0337d4e/

Guess our solution is to convert all of our intranet documents to DOCX.  it is the conversion from DOC that fails.

So be it.
0
 

Author Comment

by:InWoods
ID: 37778127
ok
0
 

Author Closing Comment

by:InWoods
ID: 37795147
Not a solution but a compromise. but that is all that is available.
0

Featured Post

SharePoint Admin?

Enable Your Employees To Focus On The Core With Intuitive Onscreen Guidance That is With You At The Moment of Need.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I will show you HOW TO: Install VMware Tools for Windows on a VMware Windows virtual machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, using the VMware Host Client. The virtual machine has Windows Server 2016 instal…
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question