I’ve seemed to have befuddled Epicor Support with this error. Has anyone encountered this and if so how did you fix it?
This occurs on all reports when trying to run on 10.1.600
: RunTask: Client found response content type of ‘application/octet-stream’, but expected ‘text/xml’. The request failed with an empty response.
Thanks for your help,
Jonathan
gold star for “befuddled”–it’s a perfectly cromulent word 
This error is almost always a time out.
Is this a new environment or one that had an earlier version of Epicor where this wasn’t a problem and was upgraded?
How long does it take to generate this error? Seconds, minutes, hours?
This even occurs with the Book listing report?
Hey Nathan,
The VM is new. It was built right to .600. We encountered the error on the first load. We noticed the VM was a bit slow and had some other issues so we blew it away and started from scratch. We reloaded .600 and connected it to the SQL DB and the error persisted. We did a migration from 9 to 10.600. We already have one that’s migrated to .500 and it works fine.
We tried it on various reports, Sales order, AR Invoice, Shop Load and I just ran a Book Listing and got the same error.
I think this is a really interesting issue. I thought it would be awesome to share with the group in case this ever happens to anyone else. We have Epicor involved, experts Joe and Nathan. They both love a Vexatious puzzle. It may be one we get our Consulting firm involved with if we can get a hold of them. Tricky bunch of people.
DISCLAIMER:
IF YOU WANT TO KNOW HOW TO READ THIS, IMAGINE A LARGE MAN WHO DRANK A LOT… AND I MEAN A LOT OF COFFEE AND DOWNED IT WITH A MOUNTAIN DEW… YEAH, THAT!
Anyway, so what we know so far.
** Microsoft SQL Server Management Studio 13.0.16106.4_**
** Microsoft Analysis Services Client Tools 13.0.1700.441**
** Microsoft Data Access Components (MDAC) 6.3.9600.17415**
** Microsoft MSXML 3.0 6.0 **
** Microsoft Internet Explorer 9.11.9600.18666**
** Microsoft .NET Framework 4.0.30319.42000**
** Operating System 6.3.9600**
The App Server changed from Epicor 10.1.500.14 to 10.1.600.5. A new version.NET, 4.6.2, was updated.
The upgrade was successful. We had no issues upgrading and the data is sound. Backups were taken and no animals were injured during this Major Release upgrade.
The problem is we can’t print reports. When we print any report at all we get this little botheration:
Program Ice.Services.Lib.RunTask raised an unexpected exception with the following message: RunTask: Client found response content type of ‘application/octet-stream’, but expected ‘text/xml’. The request failed with an empty response.
I can see the report server, “HTTP://EpiMagicDB/Reports” and HTTP://EpicMagicDB/ReportServer both work. Yes, I can interact with the reports using either Visual Studios or Report Builder.
We checked the web.config file and didn’t see any anomalies there because Nathan thought it may be a time out issue. Still an angle we’re perusing, so we may have more on that.
We checked and changed the RSSRVPolicy.Config for the report server. Basically I grabbed a backup of the policy and made it live. Nadda, didn’t work.
Joe thought it could be a hard disk space issue… HAHAHAHA, NOPE! Needless to say, I’m very proud of the size of my… Database. And so was Joe. Again, 90% or more space free on all drives.
One of the things I’m considering is that since the App server is using .NET 4.6.2 should the SQL database be as well. Kind of tricky when you upgrade a .NET version of a database and some of the consequences, I know. BUT! We have the magic of Hyper-V! And my company loves spend money on me, so pfffft. I’ll get started on that today. And it’s SATURDAY! Yeah, my wife either loves me or she stays for the kids.
If you’d like to chime in feel free. Don’t worry, we have plenty of Starbucks for everyone. Although we’re running low on Dew… Just sayin’.
[quote=“Jonathan_Lang, post:4, topic:38973, full:true”]
I think this is a really interesting issue. I thought it would be awesome to share with the group in case this ever happens to anyone else. We have Epicor involved, experts Joe and Nathan. They both love a Vexatious puzzle. It may be one we get our Consulting firm involved with if we can get a hold of them. Tricky bunch of people.
DISCLAIMER:
IF YOU WANT TO KNOW HOW TO READ THIS, IMAGINE A LARGE MAN WHO DRANK A LOT… AND I MEAN A LOT OF COFFEE AND DOWNED IT WITH A MOUNTAIN DEW… YEAH, THAT!
Anyway, so what we know so far.
** Microsoft SQL Server Management Studio 13.0.16106.4_**
** Microsoft Analysis Services Client Tools 13.0.1700.441**
** Microsoft Data Access Components (MDAC) 6.3.9600.17415**
** Microsoft MSXML 3.0 6.0 **
** Microsoft Internet Explorer 9.11.9600.18666**
** Microsoft .NET Framework 4.0.30319.42000**
** Operating System 6.3.9600**
The App Server changed from Epicor 10.1.500.14 to 10.1.600.5. A new version.NET, 4.6.2, was updated.
The upgrade was successful. We had no issues upgrading and the data is sound. Backups were taken and no animals were injured during this Major Release upgrade.
The problem is we can’t print reports. When we print any report at all we get this little botheration:
Program Ice.Services.Lib.RunTask raised an unexpected exception with the following message: RunTask: Client found response content type of ‘application/octet-stream’, but expected ‘text/xml’. The request failed with an empty response.
I can see the report server, “HTTP://EpiMagicDB/Reports” and HTTP://EpicMagicDB/ReportServer both work. Yes, I can interact with the reports using either Visual Studios or Report Builder.
We checked the web.config file and didn’t see any anomalies there because Nathan thought it may be a time out issue. Still an angle we’re perusing, so we may have more on that.
We checked and changed the RSSRVPolicy.Config for the report server. Basically I grabbed a backup of the policy and made it live. Nadda, didn’t work.
Joe thought it could be a hard disk space issue… HAHAHAHA, NOPE! Needless to say, I’m very proud of the size of my… Database. And so was Joe. Again, 90% or more space free on all drives.
One of the things I’m considering is that since the App server is using .NET 4.6.2 should the SQL database be as well. Kind of tricky when you upgrade a .NET version of a database and some of the consequences, I know. BUT! We have the magic of Hyper-V! And my company loves spend money on me, so pfffft. I’ll get started on that today. And it’s SATURDAY! Yeah, my wife either loves me or she stays for the kids.
If you’d like to chime in feel free. Don’t worry, we have plenty of Starbucks for everyone. Although we’re running low on Dew… Just sayin’.
SOLUTION
Unfortunately we weren’t able to answer the three questions:
What happened?
Why did it happen?
and How do we fix it?
What happened? We have to look at what changed. The only thing that changed was upgrading the App server and database to Epicor 10.1.600.x from 10.1.500.x.
That leads us to why did it happen? That’s the mystery. We don’t know, but we’re going to keep following up with Epicor Support. We won’t close this case until that is answered and when they do we’ll post the answer here.
How do we fix it? The link below is from Microsoft on how to uninstall reporting services.
I’d like to thank everyone that commented and tried to answer this valorous visitation of a by-gone vexation.
Jonathan
Nothing in the Windows Event logs???
Next, not sure if this is failing in populating the report from e10 db to ssrs temp db or from ssrs against the temp db. I am not sure I understand where the error is coming from. From that, you can diagnose either via SSRS or e10 tracing…
Hey Bart!
No errors except the usual Extension and Perflib stuff.
I’m actually focused on the Datasource right now. I’m waiting for Epicor to finish with the Conversion Workbench so I can get in test. It looks like all of the permissions were wiped from the SharedDataSource. The problem is I don’t know when that happened. I reset the securities on the DataSource, but I’m skeptical.
It has to be something with the Report Services. It’s something simple and Epicor and I are missing it. Absolutely nerve racking. OMG, COME ON CONVERSION WORKBENCH!! COULD YOU BE ANY SLOWER! 
I might have missed this in the thread but what additional nuggets do you have in your report server logs?
For Example: E:\Program Files\Microsoft SQL Server\MSRS11.MSSQL\Reporting Services\LogFiles
Good afternoon Dan,
I tried running a Sales Report. Here’s what I got. ReportServerService__06_24_2017_11_49_02.txt (99.2 KB)
Could you post your reportserver.config file?
Here is the trace from Epicor 10. The error is:
The report server encountered an unhandled exception in HttpApplication.(rsUnhandledHttpApplicationError)
EpicorTrace.txt (34.4 KB)
SSRS tries to instantiate Oracle and|or Terradata drivers and fails. Why would it do that?
Another question - what binding TaskAgent uses?
UsernameWindowsChannel is the end point binding I have set.
I don’t have Oracle or Terradata drivers loaded so I can see why it would fail. Report Services is a default configuration and is only connected to one database.
Typically, the Oracle and Terradata errors are indicators of other problems such as account permissions, report server database access, etc. The puzzling part of this is that the browser access is working fine.
Have you unchecked SSRS from the admin console, removed all associated report folders, etc from SSRS, and then re-deployed? I would also make sure to drop the reporting database you referenced in the Epicor SSRS configuration. Just to get a fresh start.
That’s what we’re doing this morning. I was hoping to avoid having to remove Report Services, but that seems to be the consensus. My hope was that we could answer What, Why and How:
What happened?
Why did it happen?
and How do we fix it?
The nuclear button is always the easiest to push.
Thank you Dan for your help on this issue. You earned a Heart! WHOO HOO!! LOL.
Hi Everyone,
We had this same error with all our reports processing to error as a result of the web config file however the issue turned out to be the .net service on the server that had stopped and required restart.