SQL Server 2008 Reporting Services Add-In for MOSS 2007 installation failure..

I’m trying to get SQL Server 2008 Reporting Services Add-in for MOSS 2007 working and have everything set up, from the SQL Server side of things, to get this running.

But, while i’m trying to run the installer i’m told that the installation has been interrupted – so the installer doesn’t seem to be working.

I looked at the logs on the SQL Server to see what was happening and for some reason it’s trying to connect to the server as NT Authority/Anonymous – which isn’t working. That was the first step and “thought” i’d located a fix for that.

What i tried was to run the following command, which only installs the files:

rsSharePoint.msi SKIPCA=1

and then move to the “Temp” folder and run:

rsCustomAction.exe /i

that threw a different error:

User: xxxxxxx
Installing Report Server feature.
Calling copyappbincontents command.

Access denied.

Install error: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensi
ons\12\bin\stsadm.exe return error code: -2147024891
Error details: System.Exception: C:\Program Files\Common Files\Microsoft Shared\
Web Server Extensions\12\bin\stsadm.exe return error code: -2147024891
   at RSCustomAction.BaseProcessLaunch.LaunchCommand(String fileName, String arg
uments, Boolean ignoreExitCode)
   at RSCustomAction.StsadmCommands.CopyAppBinContents()
   at RSCustomAction.RSFeatureSetup.Install(Boolean repair, Int32 addRetries)
Uninstalling Report Server feature.
Uninstalling Report Server feature.
Report Server feature was uninstalled.
Stopping W3SVC service.
SSRSCustomActionError: Cannot open W3SVC service on computer ‘.’.

Has anybody had this error before? my account is part of the local administrators group on the server and searching for that error code seems to reveal nothing either.

Any ideas?

  16 comments for “SQL Server 2008 Reporting Services Add-In for MOSS 2007 installation failure..

  1. Marcelo Silva
    September 17, 2008 at 09:26

    Yeah I am having the same problem

  2. SAV
    October 7, 2008 at 09:01

    It may be possible impersonation does not work when portal is deployed as a farm. Web Front End connects to SQL as anonymous user.

  3. October 7, 2008 at 09:27

    I’m not running this on the WFE but on the main MOSS server..

    however i’ve seen some other solutions mentioned Kerberus authentication to allow that “propagation” of the autthentication tokens..

    Still working on a solution for this and as soon as i get it running i’ll be posting the solution up here.

    am currently battling with another problem on Team Foundation Server (again, a reporting server problem)…as soon as i get back to this i’ll post more….

    Thanks for the idea tho – will check it out for sure.

  4. Ryan Pugh
    October 31, 2008 at 13:15

    If you are running on Windows 2008 Server and you are certain that the credentails have Local Admin rights, go to the Control Panel > User Accounts and TURN OFF Account Control.
    This solved my ACCESS DENIED problem on installs and command line utils

  5. Marc Purkiss
    December 16, 2008 at 03:11

    Hi. I am having the same problem. Has anyone found a way around this yet? Turning off account control made no difference for me!

  6. BrianMadsen
    December 16, 2008 at 15:51

    Hey Marc,

    i finally got it working – but i had to elevate the priviledges on the console first.

    open up a console (cmd) and type the following in:

    runas /profile /user:domain\administrator_user cmd

    (use a user that’s both a local admin as well as a farm admin on sharepoint)

    you’re then prompted for password – enter it and voila you got yourself a console running as the administrator.

    i then ran the commands and this time i didn’t get an “Access Denied” error.

    navigate to the folder where rsSharePoint.msi is located and run:

    rsSharePoint.msi SKIPCA=1

    then navigate to the folder where rsCustomAction.exe is located (c:\users\currentusername\appdata\local\temp)

    run the following command:

    rsCustomAction /i

    should mention that i’d turned off UAC temporarily as well – the installer went through successfully after that.

    try that again and let me know if it works..

  7. Vince
    December 28, 2008 at 09:36


    I tried your remedy above, the first command eneded successfully, but I got a different error than above when running rsCustomAction /i

    Starting W3SVC
    SSRSCustomActionError: Cannot open database “WSS_Content_dxxxxx” requested by the login. The login failed

    the login failed for user SPS\MOSSinstall

    Note, I turned UAC off and ran the command above runsas….

  8. BrianMadsen
    December 28, 2008 at 17:40

    might be a silly question here – but is SPS\MOSSinstall a farm admnistrator?

    WSS_Content_dxxxxx is the content database for sharepoint – check to see if you have access to that as well (could be that something’s gone wrong with permissions somewhere).

  9. Vince
    December 29, 2008 at 08:57


    First off thanks for responding to my post, and making this resource avilable

    Yes, MOSSinstall is a farm administrator, I added this account to WSS_content databases, and got past the login error and then got an error about not having permission to execute certain stored procedures which I then also corrected, my lastest error is

    Exception from HRESULT: 0x80004004 (E_ABORT

    I am about to give up…

    As you suggested the problems I am experiencing seem to be security related, and I thought using the account that I had orignailly used for the SP install which was also a farm admin would work for the add-in install, but apparently not. This add-in install seems to be particularly challenging (at least to me), tried repeatedly to use the GUI and moved on to above. Any security guidelines you’re aware of that I may of overlooked? The log file has references in it about site collections

    Activating Report Server feature to root level site collections.
    Activating feature in web app ‘My Site’
    Activating feature to root site collection: http://srv1:300

    Wondering what relevance this might have to the install? Thought I saw something about site collection admin…

  10. BrianMadsen
    December 29, 2008 at 19:33

    Hey Vince,

    yeah – the install seems to be particularly tricky – i had tons of problems with it at first but did manage to get past it by following the steps above.

    However, i also run a few other apps, such as Team Foundation Server, which also utilises this particular instance of MOSS and had to jump through a couple of hoops to get reporting working after i’d installed it.

    If you haven’t gotten far in the setup and configuration (and of course assuming this isn’t a production server) i’d almost suggest re-installing. Something could have gone wrong somewhere.

    Anyways, before you go any further, check that your sharepoint log isn’t full. that’s one of the errors you can get from that.

    Also, do you have any front end servers? you need to run rsSharePoint.msi SKIPCA=1 on those first before running rsCustomAction on the main server(s).

    lastly, i’d go through your setup and check all permissions are good to go. The service account i used was not the same as the one i installed with – it has far higher permissions than the installation service account did/does.

    Also, read through this carefully:

    that’s the HowTo on how to install and uninstall the 2008 SSRS add-in.

    also, let us have a look at your log – could easily be that there’s a problem in there that you’ve overlooked.

  11. Marc Purkiss
    January 13, 2009 at 04:56

    Hello All

    First of all thanks for all the comments in this post as they have saved my sanity and enabled me to successfully install the Reporting Services addin.
    I did however come across one problem that is not mentioned here. After successfully installing the addin on 2 WFE servers I found that the Central Administration application on my application server stop working with a runtime error. The only way I found to get around this was to install the addin on this server too. Has anyone else had this problem?

  12. BrianMadsen
    January 13, 2009 at 17:24

    Hey Marc,

    thanks for the feedback – haven’t had the problem you’re facing but am currently having issues with some DLLs not being found 🙂

    so, a re-install on another system is my next option here..

  13. Mike Donnellan
    January 27, 2009 at 13:10

    Hi Brian,

    Many thanks sir! The procedure worked and RS and SharePoint are happy together!

    Only been working on this, on and off, for 2 days… finicky install for sure.


  14. BrianMadsen
    January 27, 2009 at 15:33

    Hey Mike,

    Glad to hear we could be of help – enjoy SSRS and MOSS 🙂

  15. Carla
    March 4, 2009 at 20:21

    Thanks for all the posts here guys, turning off UAC did the trick for me 🙂


  16. Joy Muehlenbein
    June 9, 2009 at 13:26

    The solution you posted on 12/16/08 solved my pesky installation issue (Setup was interrupted before SQL Server 2008 Reporting Service Add-in for SharePoint could be completely installed). Thanks much for sharing!

Comments are closed.