ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Solved SQL Express problem with SSRS when using an expression based connection string

    IT Discussion
    sql server reporting services ssrs microsoft sql
    3
    7
    2.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JaredBuschJ
      JaredBusch
      last edited by JaredBusch

      Situation: I have a fully working system running on Server 2008 with SQL Server 2008 that I am migrating to Server 2012 R2 VM with SQL Server Express with Advanced Services (in order to get the Reporting Services component).

      Problem: Here is the Microsoft error message

      An error has occurred during report processing. (rsProcessingAborted)
      Cannot create a connection to data source 'Dynamic'. (rsErrorOpeningConnection)
      The feature: "The edition of Reporting Services that you are using requires that you use local SQL Server relational databases for report data sources and the report server database." is not supported in this edition of Reporting Services. (rsOperationNotSupported)

      Pretty straight forward, but to be 100% clear, is this telling me that I cannot use an expression based data source? Instead, I am required to use a local data source?

      1 Reply Last reply Reply Quote 1
      • dafyreD
        dafyre
        last edited by

        Are you coming from a Licensed SQL Server and switching to Express?

        JaredBuschJ 1 Reply Last reply Reply Quote 1
        • JaredBuschJ
          JaredBusch @dafyre
          last edited by

          @dafyre said:

          Are you coming from a Licensed SQL Server and switching to Express?

          I was hoping to, yes. The application is extremely light and the fact that Express can now handle a DB up to 10GB is more than enough.

          The problem seems to be that Express only allows you to communicate with itself or a localdb file. While the expression string is still only connecting to the SQLEXPRESS instance, you could in theory tell it to connect to anything there so MS seems to simply have disabled the entire feature there instead of do something else to ensure the connections stay local.

          1 Reply Last reply Reply Quote 0
          • dafyreD
            dafyre
            last edited by

            That is what I was thinking. SQL Server 2008 should install just fine on Server 2012 IIRC.

            JaredBuschJ 1 Reply Last reply Reply Quote 0
            • JaredBuschJ
              JaredBusch @dafyre
              last edited by

              @dafyre said:

              That is what I was thinking. SQL Server 2008 should install just fine on Server 2012 IIRC.

              That is not what I am trying to do. We want 2014. We will purchase it if required, but that is $3000-$6000 that could be saved if not needed.

              dafyreD 1 Reply Last reply Reply Quote 0
              • dafyreD
                dafyre @JaredBusch
                last edited by

                @JaredBusch Ah, cool. Then it looks like you may have to pay it. 😞

                1 Reply Last reply Reply Quote 0
                • drewlanderD
                  drewlander
                  last edited by

                  To the best of my knowledge, the Express Editions do not have an Agent. You might also encounter another issue if you rely on report subscriptions.

                  1 Reply Last reply Reply Quote 1
                  • 1 / 1
                  • First post
                    Last post