April 3, 2013 at 11:26 am
We've been replacing or upgrading users' machines from Windows XP to Windows 7. After doing that one of the users tried running an ASP.NET Intranet app we have, which has some SSRS 2005 reports in it. It failed with the error, "Unable to load client print control" error message. In doing searches it appeared as though the issue was a .CAB file which needed to be installed, but we couldn't find any way of getting that done. And honestly all of the search results that Google gave us were for Windows Me or Windows XP; pretty old stuff. But finally we found one that talked about the files in the .CAB being exported to a C:\Windows\Downloaded Program Files area, and that there would be a RSClientPrint.dll file in that folder, which could be registered with RegSvr32. We couldn't find it on the user's machine, so we went to another machine where the SSRS reports were working fine, found that folder and copied all of the contents from that working machine, to the user's machine where they weren't working. I then brought up the command prompt, running as an Administrator, and registered RSClientPrint.dll. At that point I thought our problems were solved, but just to double check I brought up IE and ran it again. I was wrong. We got rid of the, "Unable to load client print control" error, but now we have a new error. Looking at the event viewer on the user's machine, the new error says (in part):
Log Name: Application
Source: Application Error
Date: 4/3/2013 11:02:27 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: the.users.machine.com
Description:
Faulting application name: iexplore.exe, version: 9.0.8112.16470, time stamp: 0x510c8801
Faulting module name: RSClientPrint.dll, version: 2005.90.4053.0, time stamp: 0x4a1c6386
Exception code: 0xc0000005
Fault offset: 0x000173ee
Faulting process id: 0xd88
Faulting application start time: 0x01ce308cf44947b9
Faulting application path: C:\Program Files (x86)\Internet Explorer\iexplore.exe
Faulting module path: C:\Windows\Downloaded Program Files\RSClientPrint.dll
Report Id: 42b8bf45-9c80-11e2-b598-a41f72532ecd
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-04-03T17:02:27.000000000Z" />
<EventRecordID>2822</EventRecordID>
<Channel>Application</Channel>
<Computer>the.users.machine.com</Computer>
<Security />
</System>
<EventData>
<Data>iexplore.exe</Data>
<Data>9.0.8112.16470</Data>
<Data>510c8801</Data>
<Data>RSClientPrint.dll</Data>
<Data>2005.90.4053.0</Data>
<Data>4a1c6386</Data>
<Data>c0000005</Data>
<Data>000173ee</Data>
<Data>d88</Data>
<Data>01ce308cf44947b9</Data>
<Data>C:\Program Files (x86)\Internet Explorer\iexplore.exe</Data>
<Data>C:\Windows\Downloaded Program Files\RSClientPrint.dll</Data>
<Data>42b8bf45-9c80-11e2-b598-a41f72532ecd</Data>
</EventData>
</Event>
So, it looks as though what we did didn't solve anything, and honestly at this point I unregistered the RSClientPrint.dll, just so the user's browser would stop crashing. Bottom line, how do we resolve this issue so the user can run the reports from our Intranet?
Kindest Regards, Rod Connect with me on LinkedIn.
April 4, 2013 at 8:22 am
Thank you, Steven, I will definitely look over the article you referred to. But one thing I didn't make clear yesterday when I posted the question, is the reports aren't run from the server the SQL Server is on. i.e.: they're not run from Report Manager. Instead the reports are .RDLC files within the ASP.NET application, so technically they're running "locally", within the ASP.NET app. I don't know if that will make any difference or not.
Kindest Regards, Rod Connect with me on LinkedIn.
April 4, 2013 at 8:39 am
I should that the part that helped me was the location of the cab file on the server that houses reporting services and where to put the RDL and DLL files that were in the cab.
April 4, 2013 at 2:18 pm
I've got a follow-up question. So, now it works fine, I've registered the RSClientPrint.dll that I extracted from the RSClientPrint.CAB file (along with all of those .rll files). But something else I've noticed is that it only works, if I'm running the 32-bit version of IE (either IE9 or IE10). We've getting newer machines and all of them are 64-bit versions of Windows. If someone runs the 64-bit version of IE they get the, "Unable to load client print control" error message. In-house we can easily fix that, but for customers off-site running similar reports, I'm concerned. Most of our external customers tend to lag behind, technologically, so I think we'll be OK for a while, but eventually they'll start getting 64-bit versions of Windows and they'll probably have this problem. I'd like to know if newer versions of SQL Server Reporting Services have RSClientPrint.CAB files for both 32-bit and 64-bit versions? (We're still at SQL Server 2005, but I'm hoping we'll be able to upgrade to SQL Server 2012 this year.)
Kindest Regards, Rod Connect with me on LinkedIn.
April 4, 2013 at 2:28 pm
I believe there's a x32 and x64 version of the CAB as well. I'm not sure if the files are named the same or not or what to do if they are. I'll have to dig around and have a look.
April 4, 2013 at 2:32 pm
the files are named differently so you could probably try the process with those files and see if it works. There wasn't anything in the article about 64bit.
July 13, 2016 at 9:01 am
same kind of probelm with me too
July 14, 2016 at 7:53 am
Here’s the mail I got recently
• What is the version of internet explorer you are using?
• Any recent changes done on the computer?
A runtime error is a software or hardware problem that prevents a program from working correctly. Runtime errors might cause you to lose information in the file you're working on, cause errors in the file (corrupt the file) so you can't work with it, or prevent you from using a feature. Unlike stop errors, runtime errors don't typically cause Windows or a program to stop working.
What is a runtime error?
I would suggest that you run the Fix it tool available in the below Microsoft kb article and check if it works.
Fix Runtime Errors in Internet Explorer
If the above step fails then I would suggest that you check if any add on is causing the error in the internet explorer I would suggest you to try opening Internet explorer in the no add-ons mode.
Click the Start button, click All Programs, click Accessories, click System Tools, and then click Internet Explorer (No Add-ons)
Refer the link below for more information.
http://www.deskdecode.com/internet-explorer-has-stopped-working/
Hope this helps!
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply