Report Server 2005: Keyset Does Not Exist

[fuzzyocelot]

Hi everyone!

I'm trying to configure a local instance of Report Server 2005 on my computer. I'm running Windows XP Professional (SP2) and have installed a local instance of SQL Server 2005 without any problems. I'm hoping somone can help me get Report Server to work. I am stumped as to what's wrong.

If I open IE and use the

http://localhost/ReportServer

URL, I get the following Reporting Services Error: "Keyset does not exist (Exception from HRESULT: 0x80090016) (rsRPCError)". If I use http://<myIPaddress>/ReportServer, I get "You are not authorized to view this page". If I use

http:///IT1234/ReportServer,

I get "The page cannot be displayed". The IT1234 is my computer name.

I have IIS 5.0 installed. The web site is "Default Web Site" and it has the ReportServer and Reports virtual directories. When I go to the properties for the web site, the IP address is unassigned and the TCP port is 80. On the Home Directory tab, I selected "A redirection to URL" and redirected to "/reports". I also selected "A directory below this one" under "The client will be sent to". I was trying to follow some documentation on configuring RS.

When I open Management Studio and connect to the Database Engine using my local SQL Server instance IT1234 (using Windows Authentication), I see the "ReportServer" and "ReportServerTempDB" databases. No problems there. If I try to connect to Reporting Services using my local instance IT1234 (using Windows Authentication), I get an error message that says "Cannot connect to IT1234. The remote name could not be resolved: 'it1234' (Microsoft.SqlServer.Management.UI.RSClient)". Huh?

Then I open the SQL Server 2005 Surface Area Configuration tool. I click on Surface Area Configuration for Features (localhost). Under "Select a component", I expand the tree down to Reporting Services. Under that is "Scheduled Events and Report Delivery", "Web Service and HTTP", and "Windows Integrated Security". When I click on "Windows Integrated Security", I get the following message: "The remote name could not be resolved: 'IT1234'(System)". The 'IT1234' is my computer name. I don't know why it's giving me this message. The checkboxes for "Scheduled Events and Report Delivery" and "Web Service and HTTP" are selected.

I checked and my SQL Server instance is running along with SQL Server Agent and Reporting Services. The only errors I found in the Event Viewer under System are as follows:

1. "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {BA126AD1-2166-11D1-B1D0-00805FC1270E} to the user IT1234\ASPNET SID (S-1-5-21-3364022493-2320958936-2409960447-1007). This security permission can be modified using the Component Services administrative tool." I don't know if it's related or not. The user is listed as "ASPNET".

2. "The SQL Server FullText Search (MSSQLSERVER) service depends on the following nonexistent service: NTLMSSP"

3. "The IPSEC Services service terminated with the following error: The authentication service is unknown"

4. "The following boot-start or system-start driver(s) failed to load: NHostNT1"

Here are my current configuration settings for Report Server:

Report Server Virtual Directory:
Name: Report Server
Website: Default Web Site

Report Manager Virtual Directory:
Name: Reports
Website: Default Web Site

Windows Service Identity:
Service Name: ReportServer
Service Account: NT Authority\LocalService
Built-in Account: Local Service

Web Service Identity:
ASP .NET Service Account: IT1234\ASPNET

Database Setup:
Server Name: IT1234
Database Name: ReportServer
Credentials Type: Service Credentials

I recently tried to uninstall and reinstall Reporting Services. I get the same problems.

I am stumped! I've searched the forums and newsgroups. I've Googled the heck out of this problem and can't find anything that helps. So any help would be greatly appreciated!! Thank you!!!!

 

[fuzzyocelot]

I probably should mention that this is the Beta version, which could explain the problems I've been having. I just might have to wait until we get the actual 2005 software and install that on my computer instead.