RsActivate keeps failing

  • Hello:
    I been trying to rsActivate my RS server using the RsActivate utility but keeps getting this error:
     
    Failure starting the web service:

    The local NT Service is not activated

     
    I'm also getting this error from the Log:
    aspnet_wp!crypto!97c!1/10/2005-14:47:52:: i INFO: Initializing crypto as user: NTw2k\ASPNET

    aspnet_wp!crypto!97c!1/10/2005-14:47:52:: i INFO: Exporting public key

    aspnet_wp!crypto!97c!1/10/2005-14:47:52:: w WARN: Web Service not activated

    aspnet_wp!crypto!97c!1/10/2005-14:47:52:: i INFO: Client is not a local admin.  Not attempting activation.

     
    Everything works fine if RS install creating the 2 new databases.  But when the I want to use the existing databases I get the errors above.
     
    Another issue I also encounter is if I applied RS SP2 then I can't point the new install to it.  It complains the database are different version.
     
    But my main issue is how to resolve the rsActivate and have multiple system pointing to the same SQL server.  Any help would be appreciated.   Thanks in advance.
  • This was removed by the editor as SPAM

  • scorpvo:

    Sounds like your encryption keys are messed up.  Try this:

    BOLD - your entry

    Italics - response

    Overall:  Run IISRESET early and often during the process.

     

    C:\>rskeymgmt -d

    All data will be lost.  Are you sure you want to delete all encrypted data from the report server database (Y/N)? y

     

    Restarting the Report Server Windows service...

    Restarting IIS...

    The command completed successfully

     

    C:\>iisreset

     

    To reconfigure the keys:

     

    Run rsconfig:

     

    C:\>rsconfig -c -s<servername> -d reportserver -a windows

    (or -a SQL if you're using SQL authentication)

    The command completed successfully

     

    Then run report server from the web browser:  <A href="http:///reports">http://<servername>/reports

     

    For each data source, reconfigure as follows:

     

    Connection type:  Microsoft SQL Server

    Connection string:

    data source=<servername>; (use appropriate server name here)

    initial catalog=AdventureWorks2000; (use initial database name here)

    Integrated Security=SSPI; (insert this string if using Integrated Windows Security)

     

    The full connection string in the Connection String box is:

    data source=DHSCDICSQL02; initial catalog=AdventureWorks2000; Integrated Security=SSPI;

    (No parentheses, no quotation marks, just the text above.  I didn’t check to see if the final semi-colon is required, but it works with it.)

     

    Connect Using:  Click the Radio Button for the appropriate authentication type.

    That was the last step in solving my problems after I removed and reinstalled Reporting Services.

    Good luck to you.

    Terry

  • Thanks Terry.  That fixed it.

  • These steps helped me as well, however when I try to connect to my datasources to update them I get the following error:

    The underlying connection was closed: Could not establish trust relationship with remote server.

    Anybody else seen that?

  • Nick-

    Looks like you're using SSL on the connection between the servers.  I'm in a secure environment and don't have SSL enabled.

    You might try searching for "SSL" in RSBOL and see if that points you in the right direction.

    Terry

  • Our issue is similar to this thread.

    We deleted the encrypted keys via the rsconfig command.

    When we create the new key, SQL shows it as a NULL key.  Does this mean we're not logging in with the correct permissions?  We log on with Local Admin perms.

    Here's what we see via SQL:

    InstanceID          Client       Public Key       SymmetricKey

    0000(all zeros)        -1             NULL             NULL

    7F97 (etc)              0           0x0602(etc)       NULL

    7F97(same one as above)   Public Key same as above

                         client = 1          SymmetricKey 0x01(etc)

    We think the last key has to do with the NT Report Service so we shouldn't delete it, right?

    We don't see any ODBC data sources to configure.

    Any other clues we can follow?

    Thanks so much,

    Connie

  • Having decided we have no fear, we deleted all the keys and started again....results were the same.

    Starting the NT service creates the 1st key - client=1 and a symmetrickey.

    Browsing over to the localhost report services, the second key gets auto generated but with Client=0 and a NULL symmetrickey .... shouldn't there be a symmetric key generated at this point?

     

    Thanks,

    Connie

  • Not sure if this helps, but our keys aren't quite the same, we don't have the same/identical sym key for the two client records.

    I suppose you've already checked either the RS logs or the event log to see if anything is thrown that could point towards how to fix it?

    Steve.

  • This is a great post, it worked wonders for me.  Terry your posting skills are awesome, so incredibly easy to read.  I loved it.

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply