We build a thinapp of Adobe Reader 10.1. The thinapp worked well. After a week we had the first error. A Appcrash withe the message: Adobe Reader X doesn't work anymore. He crashes with every pdf-file. Temorary solution is to delete the temp folder of the thinapp. Then it will go well for another 1 or 2 weeks. After Adobe Reader 10.1, we had tryed 9.4 and Foxit Reader. But also those 2 apps give the same error after a few times of usage.
We have no idea what causes the error. Just like I said, it doesn't care with pdf-file you use. Does someone can help us?
Thanks!
We use a clean W7 VM and Thinapp 4.6
Please try following the steps here: http://communities.vmware.com/docs/DOC-15718
Also try using the latest ThinApp version 4.6.2
Ok thank you for the help. We will give it a try!
I've tried that method exactly for every version of Adobe Reader X but each version results in a SideBySide error in Event Viewer as soon as Adobe Reader X is closed.
I have no problems at all with Adobe Reader 9.
Any suggestions please?
Maybe for the SxS errors they can be ignored if the thinapp is working correctly. The reason you do not find a solution for al the SxS errors is there is no real one.. These events are irritating but are not indicating a true error. There is a workaround. On you physical client add the following folders C:\Program Files\Name of the application (path where the errors complaining about).
I did end up with creating policy preferences for creating these folders for the users at logon. Now we don't see any SxS errors in de events logs.
this is the error:
Activation context generation failed for "C:\Users\MICHAEL\AppData\Roaming\Thinstall\Adobe Reader X (10.1.1)\SKEL\5672-4.manifest". Dependent Assembly Adobe.Reader.Dependencies,processorArchitecture="x86",publicKeyToken="0000000000000000",type="win32",version="10.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis.
The path mentioned exists. I also created the Program Files path for Adobe Reader X but that didn't help either.
In event viewer it is shown as a critical error so i doubt it should be ignored.
cheers
Hi heywheels,
Like I posted for most of our thinapps creating the directory resolved the SxS errors in the event logs. The others also generate some SxS errors just like yours. But the Thinapps run normal without any issues. I'm ignoring them because everything works witout any issues. Let me know if you found a solutions.
Cheers
Fair enough. It seems to work fine just filling Event Viewer with errors. I haven't fond a soluton yet but I'll keep looking. It would be nice to know what causes the SideBySide problems with thinapps.
Hi heywheels,
When a ThinApp application has dependencies on SxS DLLs, it checks the host file system for SxS security updates. This generates events in the Windows event log. Read this KB:
Thanks for that link. It's strange that the SxS errors only occur with some programs and then only some versions of those programs, not all.
I am currently out of the office. I have limited email access and will get back to you as soon as possible.
Regards,
Stephen Ziegenfus
Stephen Ziegenfus, Systems Administrator, Balch & Bingham LLP
1901 Sixth Avenue North • Suite 1500 • Birmingham, AL 35203-4642
t: (205) 488-5401 f: (205) 488-5834 e: sziegenfus@balch.com