slamit
asked on
Windows Photo Viewer can not run on WinSvr 2008 x64 / XenApp Server
Hi folks,
We have a customer with 3 XenApp Servers on WinSvr 2008 x64 R2. Desktop Experience is installed as they use the Windows Photo Viewer app.
When attempting to open images (associations are to Photo Viewer) an error shows up saying "Windows cannot find image.jpg. Make sure you typed the name correctly, and then try again".
Testing shows it's not the image file that can't be found, it's Photo Viewer just not loading.
It's working fine on 2 of their Servers still (it used to work fine on this one - no updates or changes applied to break it). Have even been able to copy the appropriate files from the known good Server, to no avail.
We've uninstalled the Desktop Experience feature, reinstalled it rebooted, re-registered DLLs, changed associations back and forth but so far, no dice.
Unfortunately it's one of those situations where we need to get it working.
Any thoughts?
Thanks in advance!
We have a customer with 3 XenApp Servers on WinSvr 2008 x64 R2. Desktop Experience is installed as they use the Windows Photo Viewer app.
When attempting to open images (associations are to Photo Viewer) an error shows up saying "Windows cannot find image.jpg. Make sure you typed the name correctly, and then try again".
Testing shows it's not the image file that can't be found, it's Photo Viewer just not loading.
It's working fine on 2 of their Servers still (it used to work fine on this one - no updates or changes applied to break it). Have even been able to copy the appropriate files from the known good Server, to no avail.
We've uninstalled the Desktop Experience feature, reinstalled it rebooted, re-registered DLLs, changed associations back and forth but so far, no dice.
Unfortunately it's one of those situations where we need to get it working.
Any thoughts?
Thanks in advance!
Check this hotfix: http://support.microsoft.com/kb/980393/en-us
ASKER
Thanks for the tip - but the DLL is already a newer version than this. :(
OK, try the following:
Browse to the following path in the registry:
HKEY_CLASSES_ROOT\AppID\{7 6D0CB12-76 04-4048-B8 3C-1005C7D DC503}
Locate the RunAs registry entry, and delete it.
Also try doing a microsoft update on the server.
Browse to the following path in the registry:
HKEY_CLASSES_ROOT\AppID\{7
Locate the RunAs registry entry, and delete it.
Also try doing a microsoft update on the server.
ASKER
Thanks - unfortunately the RunAs entry doesn't exist, and the Server is fully up to date with patching.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks.
That has lead me on the path to find that the COM+ System Application service won't start. After running sfc, it looks as if dllhost.exe is corrupt and sfc can't repair it.
Looks like that's the source of our woes... Any tips on that one?
Thanks for your help!
That has lead me on the path to find that the COM+ System Application service won't start. After running sfc, it looks as if dllhost.exe is corrupt and sfc can't repair it.
Looks like that's the source of our woes... Any tips on that one?
Thanks for your help!
ASKER
I found exactly what I'll need to do:
http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/107c8ab2-3057-4034-acf9-0179804b5aab/
... unfortunately we can't rename, delete or even take ownership of dllhost.exe - we can view properties, but on trying to take ownership we get "file can not be found".
dllhost.exe has definitely been changed...
http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/107c8ab2-3057-4034-acf9-0179804b5aab/
... unfortunately we can't rename, delete or even take ownership of dllhost.exe - we can view properties, but on trying to take ownership we get "file can not be found".
dllhost.exe has definitely been changed...
Why don't you try to repair the Windows installation instead of trying to take ownership and replacing the file. After running the repair, run windows update.
Hope this helps.
Hope this helps.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Glad that your issue got resolved.
ASKER
Mutawadi put me on to the right track - and managed to sort out the solution with my notes above.