SSRS 2008 to 2014 Migration Excel Export error












0















We are working on migrating our SSRS from SQL Server 2008 to SQL Server 2014. After brining the reports over I have a set of reports that will execute just fine but when I try to perform a standard export to excel from the 2014 Server I get a message box saying:




We found a problem with some content in ACM Consolidated
Invoie_2014.xlsx. Do you want us to recover as much as we can?
If you trust the source of this workbook, click yes.




However, I do not receive the same message when exporting to Excel from the 2008 server. I believe the problem is related to some Numeric fields that are coming back with a value of 0.0000000000000000000. Has something changed with the excel export function between these two versions?










share|improve this question














bumped to the homepage by Community 16 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    0















    We are working on migrating our SSRS from SQL Server 2008 to SQL Server 2014. After brining the reports over I have a set of reports that will execute just fine but when I try to perform a standard export to excel from the 2014 Server I get a message box saying:




    We found a problem with some content in ACM Consolidated
    Invoie_2014.xlsx. Do you want us to recover as much as we can?
    If you trust the source of this workbook, click yes.




    However, I do not receive the same message when exporting to Excel from the 2008 server. I believe the problem is related to some Numeric fields that are coming back with a value of 0.0000000000000000000. Has something changed with the excel export function between these two versions?










    share|improve this question














    bumped to the homepage by Community 16 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0








      We are working on migrating our SSRS from SQL Server 2008 to SQL Server 2014. After brining the reports over I have a set of reports that will execute just fine but when I try to perform a standard export to excel from the 2014 Server I get a message box saying:




      We found a problem with some content in ACM Consolidated
      Invoie_2014.xlsx. Do you want us to recover as much as we can?
      If you trust the source of this workbook, click yes.




      However, I do not receive the same message when exporting to Excel from the 2008 server. I believe the problem is related to some Numeric fields that are coming back with a value of 0.0000000000000000000. Has something changed with the excel export function between these two versions?










      share|improve this question














      We are working on migrating our SSRS from SQL Server 2008 to SQL Server 2014. After brining the reports over I have a set of reports that will execute just fine but when I try to perform a standard export to excel from the 2014 Server I get a message box saying:




      We found a problem with some content in ACM Consolidated
      Invoie_2014.xlsx. Do you want us to recover as much as we can?
      If you trust the source of this workbook, click yes.




      However, I do not receive the same message when exporting to Excel from the 2008 server. I believe the problem is related to some Numeric fields that are coming back with a value of 0.0000000000000000000. Has something changed with the excel export function between these two versions?







      migration ssrs-2008 ssrs-2014






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Sep 26 '16 at 14:17









      LumpyLumpy

      1,12461935




      1,12461935





      bumped to the homepage by Community 16 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 16 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          This appears to be related to some implicit conversions that are occurring in the background when exporting the report to xlsx. Numeric columns are being sent to excel as if they are text columns. One report responded to a change to the query using an Explicit cast to Numeric (Cast as opposed to convert to remove any commas or other formatting that might confuse the conversion). Several other reports did not respond to the Cast but returned correctly after using an expression conversion of VAL(). I still have several reports that are not responding to either. If anyone out there has a good explanation for this I'd love to hear it.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "182"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f150659%2fssrs-2008-to-2014-migration-excel-export-error%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            This appears to be related to some implicit conversions that are occurring in the background when exporting the report to xlsx. Numeric columns are being sent to excel as if they are text columns. One report responded to a change to the query using an Explicit cast to Numeric (Cast as opposed to convert to remove any commas or other formatting that might confuse the conversion). Several other reports did not respond to the Cast but returned correctly after using an expression conversion of VAL(). I still have several reports that are not responding to either. If anyone out there has a good explanation for this I'd love to hear it.






            share|improve this answer




























              0














              This appears to be related to some implicit conversions that are occurring in the background when exporting the report to xlsx. Numeric columns are being sent to excel as if they are text columns. One report responded to a change to the query using an Explicit cast to Numeric (Cast as opposed to convert to remove any commas or other formatting that might confuse the conversion). Several other reports did not respond to the Cast but returned correctly after using an expression conversion of VAL(). I still have several reports that are not responding to either. If anyone out there has a good explanation for this I'd love to hear it.






              share|improve this answer


























                0












                0








                0







                This appears to be related to some implicit conversions that are occurring in the background when exporting the report to xlsx. Numeric columns are being sent to excel as if they are text columns. One report responded to a change to the query using an Explicit cast to Numeric (Cast as opposed to convert to remove any commas or other formatting that might confuse the conversion). Several other reports did not respond to the Cast but returned correctly after using an expression conversion of VAL(). I still have several reports that are not responding to either. If anyone out there has a good explanation for this I'd love to hear it.






                share|improve this answer













                This appears to be related to some implicit conversions that are occurring in the background when exporting the report to xlsx. Numeric columns are being sent to excel as if they are text columns. One report responded to a change to the query using an Explicit cast to Numeric (Cast as opposed to convert to remove any commas or other formatting that might confuse the conversion). Several other reports did not respond to the Cast but returned correctly after using an expression conversion of VAL(). I still have several reports that are not responding to either. If anyone out there has a good explanation for this I'd love to hear it.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Oct 26 '16 at 17:46









                LumpyLumpy

                1,12461935




                1,12461935






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Database Administrators Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f150659%2fssrs-2008-to-2014-migration-excel-export-error%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    SQL Server 17 - Attemping to backup to remote NAS but Access is denied

                    Always On Availability groups resolving state after failover - Remote harden of transaction...

                    Restoring from pg_dump with foreign key constraints