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

    SQL Reporting Services will not start

    IT Discussion
    microsoft sql
    3
    6
    1.4k
    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.
    • IRJI
      IRJ
      last edited by

      I am running Server 2008 R2 with a SQL 2008 R2 install. Yesterday I tried to add reporting services. Unfortunately a vendor was VPNed into our system and running windows installer at the sametime. So I received several error messages and one stating that the installation would have to be canceled. I hit cancel, however, SQL acted like it completed successfully.

      Now the Vendor is telling me SQL reporting services wont start. I launched the SQL install again this morning and its telling me that Reporting Services are already installed. Does anyone know a way to uninstall them without affecting SQL itself? I would like to uninstall then reinstall.

      NetworkNerdN 1 Reply Last reply Reply Quote 3
      • IRJI
        IRJ
        last edited by

        This has been resolved.

        1 Reply Last reply Reply Quote 0
        • NetworkNerdN
          NetworkNerd @IRJ
          last edited by

          @IRJ
          Sorry for the delay in response here, but can you verify the SQL Server Reporting Services service startup type is set to Automatic and not disabled for any reason?

          Also, from the Windows Start menu, do you see the Reporting Services Configuration Manager? You should be able to search for it or drill into Microsoft SQL Server 2008 -> Configuration Tools and see it.

          1 Reply Last reply Reply Quote 0
          • IRJI
            IRJ
            last edited by

            I think this was a case of bad vendor communication with us.

            NetworkNerdN 1 Reply Last reply Reply Quote 0
            • NetworkNerdN
              NetworkNerd @IRJ
              last edited by

              @IRJ said:

              I think this was a case of bad vendor communication with us.

              Well, I am happy you were able to get it resolved.

              scottalanmillerS 1 Reply Last reply Reply Quote 0
              • scottalanmillerS
                scottalanmiller @NetworkNerd
                last edited by

                @NetworkNerd Yeah!

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