January 10, 2005 at 2:11 pm
The local NT Service is not activated
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.
January 13, 2005 at 8:00 am
This was removed by the editor as SPAM
January 14, 2005 at 4:36 pm
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
January 18, 2005 at 1:21 pm
Thanks Terry. That fixed it.
January 20, 2005 at 9:12 am
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?
January 20, 2005 at 9:56 am
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
April 12, 2005 at 11:32 am
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
April 12, 2005 at 12:07 pm
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
April 12, 2005 at 5:06 pm
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.
October 19, 2005 at 4:30 pm
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