April 3, 2014 at 10:32 am
They get Error loading resource library. (0x8007007E).
deleted rsclientprint*.* from windows/system and windows/
reinstalled to c:\windows\downloaded program files\
Still the same error. Even local admin so not rights to c:\windows\downloaded program files\
tried manually registering rsclientprint.dll
Its SQL 2008, not R2.
Any ideas?
This seems to be only on users using ie 10 but not 100% on that.
April 4, 2014 at 4:19 am
What Windows version is the user running? Here's a large discussion on the issue to look at
April 4, 2014 at 7:01 am
The machine I looked at was a windows 7. I think most users are on windows 7 there may be a few xp stragglers. IE 10, this happened in the upgrade to 10 I think.
I saw the article you post.
I tried the fix for the report viewer even though they are not using report viewer, running righ out of
/reports or /reportserver
The final interesting 12 steps or so, not all are relevant to ie 10 I think.
I will try those again anyway and let you know
April 4, 2014 at 7:13 am
Did you see this articel at at StackOverflow?
April 4, 2014 at 7:16 am
Yes, that's were I found the idea to delete out rsclientprint*.* from system32 and windows and make sure in downloaded program files.
April 4, 2014 at 8:18 am
April 4, 2014 at 8:30 am
When you reinstalled it, how did you do it? depending on the source sometimes I've been caught but the "blocked Application" in the file Properties. That's usually when I've downloaded something and try to run it for the first time.
April 4, 2014 at 9:53 am
Yes we are doing that work around currently, but it's not a fix
April 4, 2014 at 9:54 am
I did both manual and let ie prompt and do
April 4, 2014 at 10:02 am
The main problem IMO is ActiveX which is the technology MS used to create its RSClientPrint. ActiveX does not work all the time in web scenarios and in other browsers other than IE. We have a code here that modify ReportViewer in an ASP.NET page to make a printing cross browser. It talks about RDLC local reports but the same can be applied to RDL server reports. It requires an external utility to be installed at the client AND the developing of a custom web page to display the reports i.e. you cannot get it working in Report Manager portal if this is what you are using.
April 4, 2014 at 10:11 am
What's your patch level? I know it's not the error you're getting but there was a patch to fix the "error loading print control" error for 2008. The fix for that and the fix for your error(at least the ones I found googling) seem very similar.
When you reinstalled where did you get the files?
April 6, 2014 at 6:21 pm
Its R2 SP2 SQL (thought it wasn't R2 but it is).
SSRS is on a different server:
and its 10.50.250
SP2 is 10.50.400
I'm going to look into applying sp2 to the report server.
April 6, 2014 at 6:51 pm
I'm going to have some users test but I think getting sp2 on the report server may have fixed this.
Its not in the bug fix but maybe having R2 and sp2 on the sql box but not the report server caused the issue. I'll let you know how it goes on the workstation tests tomorrow but we may be fixed here.
April 7, 2014 at 12:26 pm
What SQL Server 2008 service pack are you on?
I had a print problem due to the printer cab files were outdated in Service Pack 2 for SQL Server 2008.
I found the newer print cabs and put them in the correct directory on my report server.
The next time a user tried to print, they would pick up the new cab files and they would be able
to print again.
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply