Results 1 to 7 of 7
  1. #1
    Join Date
    Jun 2004
    Location
    Philly
    Posts
    51

    Unanswered: reinstalling reporting services

    so i uninstalled reporting services and rebooted

    now when i run setup it doesnt even ask me for any options to fill out, it just runs for a minute and says done, but it doesn't really install anything (IIS sites, DB, etc...)

    i deleted the DBs, the IIS sites, and the files left over. i did everything except delete stuff in the registry

    what do i have to do to get it to reinstall from scratch?

    i tried using the .ini file and using the command line utility with no luck

  2. #2
    Join Date
    Nov 2004
    Location
    on the wrong server
    Posts
    8,835
    Provided Answers: 6
    welcome to the hell that Reporting Services 2000. read chapter 7 of this...

    http://www.awprofessional.com/articl...&seqNum=1&rl=1

    and then read the whole thing.

    SQL 2005 reporting Services is a lot more agreeable.
    “If one brings so much courage to this world the world has to kill them or break them, so of course it kills them. The world breaks every one and afterward many are strong at the broken places. But those that will not break it kills. It kills the very good and the very gentle and the very brave impartially. If you are none of these you can be sure it will kill you too but there will be no special hurry.” Earnest Hemingway, A Farewell To Arms.

  3. #3
    Join Date
    Nov 2005
    Location
    San Francisco, CA
    Posts
    506
    Quote Originally Posted by xarfox
    so i uninstalled reporting services and rebooted

    now when i run setup it doesnt even ask me for any options to fill out, it just runs for a minute and says done, but it doesn't really install anything (IIS sites, DB, etc...)

    i deleted the DBs, the IIS sites, and the files left over. i did everything except delete stuff in the registry

    what do i have to do to get it to reinstall from scratch?

    i tried using the .ini file and using the command line utility with no luck
    Check your Sql server Service pack as well as Windows server service pack.It happened to me also.Reboot and Install it again...
    Success is the ability to go from one failure to another with no loss of enthusiasm.
    - Sir Winston Churchill
    Joydeep

  4. #4
    Join Date
    Jun 2004
    Location
    Philly
    Posts
    51
    Quote Originally Posted by rudra
    Check your Sql server Service pack as well as Windows server service pack.It happened to me also.Reboot and Install it again...
    using all of the latest service packs, and i rebooted twice with the same results

  5. #5
    Join Date
    Jun 2004
    Location
    Philly
    Posts
    51
    Quote Originally Posted by Thrasymachus
    welcome to the hell that Reporting Services 2000. read chapter 7 of this...

    http://www.awprofessional.com/articl...&seqNum=1&rl=1

    and then read the whole thing.

    SQL 2005 reporting Services is a lot more agreeable.
    i did read this chapter, and looked over the whole thing

    i also read the entire sql reporting services book from the people at www.sqlreportingservices.net

    none of their solutions helped

    i think i am going to try an unattended installation to try to force it to use my ini file, after that i'm out of ideas

  6. #6
    Join Date
    Nov 2005
    Location
    San Francisco, CA
    Posts
    506
    Some info for your help...


    Renaming a computer causes a corresponding name change for the Web server and SQL Server instance (if it is on the same computer).


    In some cases, Reporting Services is not functional after a computer name change. If you are running a Windows 2000 server and the ReportServer Windows service runs as Local System, the ReportServer Windows service no longer starts automatically when you restart the computer. If you are running Windows Server 2003, the service will start, but you cannot connect to the report server database. To restore service after a computer name change, follow these steps:

    Run rsconfig at the command line to update the encrypted connection information in the report server database. Use this syntax when running rsconfig (your values may be different).

    rsconfig -s<NewServerName> -dreportserver -aSQL -uSA -p<SAPassword>

    Reset IIS. To do this at the command line, type iisreset.

    In the RSWebApplication.config file, modify the ReportServerURL setting to reflect the new server name.

    In the RSReportServer.config file, modify the URLRoot setting to reflect the new server name.

    Update the URL property of the program item used to access Report Manager from the Start menu. To do this, point to Start, point to Program Files, point to Microsoft SQL Server, point to Reporting Services, right-click on Report Manager. On the Web Document page, update the URL to the new server name.
    Open Report Manager and update any shared data sources or report-specific data sources that contain references to the old computer name.
    If you are running Windows 2000 server, perform these additional steps:

    Manually start the ReportServer Windows service.

    Run rsactivate at the command line. Use this syntax when running rsactivate (note that your actual values may be different if you did not install to the default path).

    rsactivate -c"%installdir%\Reporting

    Services\ReportServer\RSReportServer.config"

    Reset IIS. To do this at the command line, type iisreset.

    For a period of time, the report server and Report Manager may continue to be available under the previous name if you are using Windows Internet Naming Service (WINS) on your corporate network. WINS maps an IP address to each computer it services. Once WINS refreshes the IP address for the renamed computer, the old computer name can no longer be used to access a report server or Report Manager.
    Success is the ability to go from one failure to another with no loss of enthusiasm.
    - Sir Winston Churchill
    Joydeep

  7. #7
    Join Date
    Jun 2004
    Location
    Philly
    Posts
    51
    i did this as well, the problem is that RSCONFIG does not support Named Instances as per Microsoft's website. plus the config files are envrypted - i dont think you can see server names listed in the config files, i remember checking before i did anything

    it has to be reinstalled through the GUI which does support named instances

    i solved the problem to my issue once again:

    asp.net 2.0 was installed on this machine as well, which caused the registry key RootVer to be set to ASP 2.0. This is why the install package was saying that 1.1 was not installed (even though it was). YOu have to temporarily change the RootVer key to 1.1, install, and then set it back. This allows you to reinstall report server etc...

    [\\HKLM\SOFTWARE\Microsoft\ASP.NET\RootVer] = "1.1.4322.573"

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •