DOCX File Open via ie9 fails only in VMWare View 4.6 VDI
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?
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?
ASKER
Thanks, UAC is already set to lowest level: Do Not Notify.
ASKER
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.EX
Faulting module path: unknown
Report Id: 291457aa-6ea4-11e1-b487-00
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</Event
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2012-03-15T13:
<EventRecordID>5350</Event
<Channel>Application</Chan
<Computer>ComputerName</Co
<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</Da
<Data>C:\Program Files\Microsoft Office\Office14\WINWORD.EX
<Data>unknown</Data>
<Data>291457aa-6ea4-11e1-b
</EventData>
</Event>
Any ideas?
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.EX
Faulting module path: unknown
Report Id: 291457aa-6ea4-11e1-b487-00
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</Event
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2012-03-15T13:
<EventRecordID>5350</Event
<Channel>Application</Chan
<Computer>ComputerName</Co
<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</Da
<Data>C:\Program Files\Microsoft Office\Office14\WINWORD.EX
<Data>unknown</Data>
<Data>291457aa-6ea4-11e1-b
</EventData>
</Event>
Any ideas?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok
ASKER
Not a solution but a compromise. but that is all that is available.
Has before some issues with those settings combined with word.