Google matched several DLL websites, but number 3 on the list of results was a link to an update from Microsoft. Not sure what to make of this just yet, I tried the most desperate (or smartest if you will) thing and searched Google for one of the filenames. If I searched the current machine, similar files were available. The missing files all appeared to be related. So i opened up the file C:\Program Files (x86)\Microsoft Office\Office16\VVIEWER.DLL in Dependency Walker, and indeed, there were some missing dependencies. So if a DLL or EXE files has several dependencies, Dependency Walker will show this. This is a tool which analyses dependency linkage between executable files. I opened up the Visio dll file in Dependency Walker.
But since Visio Viewer was a control Internet Explorer loaded, maybe where is some dependency it needed, but what? Maybe there is a crash or something in the Event Viewer? Nope. Maybe it was Internet Explorer security settings? Change everything to the lowest secure settings. So i delete the registry keys for Visio from HKEY_LOCAL_MACHINE\SOFTWAR E\Microsof t\Internet Explorer\ActiveX Compatibility. If I check the 32bit registry node, there is also an Alternate CLSID. Hey, is listed in HKEY_LOCAL_MACHINE\SOFTWAR E\Microsof t\Internet Explorer\ActiveX Compatibility! And there was even a suggestion that if the specific registry which blocks Visio Viewer was removed, Visio would launch. Visio files appear to be associated correctly.īut plugin does not load in Internet ExplorerĪt first, I thought this might have something to do with ActiveX Killbits, because when I tried to research the error, it appears the Visio Viewer Active X control was blocked. It is in fact where I first encountered the error This was tested on Windows 7, but it applies to Windows Server 2008 R2 as well.
0 kommentar(er)
