Wednesday, July 18, 2012

Unable to load client print control

Firstly! No happy ending to this story.
Error is shown when users use print control in an external hosted application.
Still works to print, when first pushing abort and then running anyways.
Hosted application use a Microsoft SQL Server Report Viewer Control.
Users connect from Remote Desktop Server running Server 2008 R2 using Internet Explorer 9.
UAC is disabled, due to other 3rd party application that requires this.
Addin is loaded in Internet Explorer. Probable cause is rights issue.
Only reason it works anyways is because I logged in as administrator and ran the installation above. Problem is that this control tries to download every time user access the site, just in case there is a new version.
Registered rsclientprint.dll manually on adminlogin, and in user environment. No effect.
Removed files from Windows\Downloaded Program Files > Went back to not working at all. Copied back to allow users to print despite error message.
Registered rsclientprintx64.dll > No effect. Browser is probably running in x32 mode so the right components should be installing.
Tried to run website from Iexplore in 64bits mode > Site didn’t even work.
Set up GPO to allow server-users to autoinstall activex components > No effect.
Tried adding the user to Power Users to do the install > No effect.
Resolution: to be added….
Most of information on Internet points to the server hosting the webapplication needing to install Microsoft Report Viewer SP1 - and Report Viewer Redistributable 2008 Service Pack 1 GDIPLUS.DLL Security Update
But since I don’t have control of the server and the company hosting the application isn’t very forthcoming I wanna solve on the clientside. This doesn’t seem to work though. So severals hours of trying to solve it has led me to take a timeout and await the company helpdesk. Annoying.

Update 1.
After calling to the supplier with my grief it turned out that they indeed had recently updated their plattform and were experiencing some issues... Well at least I could turn over my hours of research into the problem to them, hoping this would speed up their own troubleshooting.
Another great link I found :
This points toward the issue only happening in environements were the user isn't administrator.

No comments: