SQL 2008 R2 SSRS and Excel 2013

We recently upgraded Office 2007 Pro Plus to Office 2013 Pro Plus and have encountered an issue with the reporting piece in one of our applications.  The third-party application runs on a server with Windows 2008 R2 Standard and SQL 2008 R2 Standard.  

From within the application, users are given a variety of ways to view/export reports, one of them being to Excel.  Since upgrading to Excel 2013, we now receive an error message when exporting certain types of reports (i.e. ones where multiple reports/spreadsheets are merged into one).

In working with the application vendor's support department, I was told that the version of SSRS is incompatible with Office 2013 applications.  I'm not necessarily looking for a solution to the error from this forum, so much as I'm just trying to get some validation for this explanation.  I haven't been able to find anything on the web that answers this specific question and I feel that this may be just one way for them to sweep this issue under the rug.

So, whereas there may not be a simple answer, the simple question is:  Is SQL 2008 R2 SSRS compatible with Excel 2013?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

At first glance I'd not really expect it to be - after all, Office 2013 was 3 years in the the future when 2008R2 was released.

I believe that 2008R2 is noted by MS as being compatible with the .xlsx file format (unlike 2008, which only output to .xls files).

However, your app vendor may be doing something with SSRS that works fine when working with Office 2010 (exploiting what they maybe didn't realise was a bug) and now doesn't work with 2013 (bug fixed by MS). Of course, it could also been the other way around!

I'd suggest trying out going back to Excel 2010 on the machine that renders the reports and seeing how you get on.



Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
apexcapAuthor Commented:
I haven't had a chance to try it with Excel 2010 yet, but am running into other macro-related issues with Excel 2013 so I may have to go back to a previous version regardless.  And you're probably right about the vendor doing something with SSRS that's conflicting with 2013, so we'll probably just have to wait until they release an update.  In any case, thanks for the response.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.