Connection Issues To Report Services

Hello all,

I just installed the SQL 2k5 standard suite of services on a w2k3 enterprise edition server. All went well except for the connection to the reporting server. I get the error below.

"No connection could be made because the target machine actively refused it"

I can't seem to find any information on this error and have no clue where to even start. I've done 10+ installations of this software on various machines and have not encountered this error on any of them.

I have uninstalled, then reinstalled the reporting services and still no solution. All connection attempts are being made on the actual server, not from a desktop. sp1 for sql 2k5 is also installed, if that helps.

Windows Firewall is off.

What web searches I've done have turned up nothing useful. I'm pretty good at figuring this stuff out but this error provides very little of any use.

Anyone out there have any ideas?

Thanks in advance,

Greg

Have you seen this page: http://www.sqljunkies.com/WebLog/edwardm/ ?|||

First, thanks for the link. I'll make note of the ports used by SSAS and some of the other information in there.

I did figure this out, though. Not a very scientific approach so I'll have to run into this problem again to verify but, at a minimum, backing up the encryption key from within Reporting Services Configuration seemed to do the trick. I had a few other things out of whack, too.

At one point, the Backup option was disabled, but disabling "Web Server and HTTP Access" via SQL Server Surface Area Configuration -> Surface Area Configuration for Feature -> Reporting Services enabled the Backup button (kind of a round-about way of making that happen).

After backing up the encryption key, I enabled that option and could connect after that. Problem Solved!

This was further complicated by the fact that the reporting services install didn't conform to some "default" system configuration and performed only a "files-only" install. I really didn't pay that much attention during the install and the difference never really registered in my mind. So, I had to manually configure the reporting server (web directories, db connections, dbs and all).

So, chalk this up to experience and I'll know the next time I run into this.

Other things I addressed, but I'm not sure were relevant were:

the state of the IIS Admin and WWW publishing services (these were stopped and in manual mode during the install - I would think the install would start these if needed)

The execution permissions and application protection modes of the reporting server virtual directories (these were different on the problem installation than a "default" installation - an install on another machine that did work fine)

I don't think I needed to do the reporting services re-install.

When creating the databases manually, I ended up having to do that with scripts. For some reason, the database creation was timing out. The creation of the two databases was ok, but the reporting server temp db did not have any objects in it (no tables, views, etc).

There are a myriad of other things, but I'm almost certain these weren't relevant. All-in-all, a hassle.

Greg

|||Greg: Thanks for your post. I have a problem getting SSRS to work on one of my servers, too. I posted on Sunday:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1215786&SiteID=1
but no one answered. In my case, the local SSRS does not even appear in the list of servers to initialize, within the RS Config Manager. When I installed SSRS, I got the message "Reporting Services was installed, but not configured". This was on a reinstall of SQL05 needed to place the files on a drive other than C:

I will see if backing up the key fixes my problem, next time I'm at that site.|||I'm back at the server with the problem. When I run RS Config Mgr, the button to back up the encryption key is disabled. The only enabled buttons on that page are the 'Restore' button, and the 'Delete' (delete encrypted content) button.

I tried disabling HTTP and Web Access using the Surface Area tool, but the 'Backup' button is still disabled.

Any ideas on how to diagnose and fix this?|||

Hmm. That's what I did. One other thing you might try is deleting the encrypted content. At some point in my troubleshooting process, I pressed that button. I would assume that if encrypted content did exist, and you didn't have the proper encryption key to restore from, the encrypted content would be un-accessible (that's rather obvious). I was comfortable deleting encrypted content because the installation was new and there was nothing to lose.

After doing that, you could then go throught the HTTP and Web Access routine again.

|||No luck for me. Could not get the 'Backup' button enabled on the Encryption Key page. I found in the event log I'm getting EventID 7000 from the RS Service saying "...cannot connect to the report server database". I tried scripting out the DB creation and running that separately. The script ran without errors, but I still get the connection failure event.

I tried running "rsconfig.exe -t -c -d SSRS -a windows -s mssqlserver", where SSRS is my RS db name and mssqlserver is the SQL Server instance name (the default instance), and it came back with "The command completed successfully"

Now since running rsconfig, in the GUI version, RS Configuration Mgr, I'm getting error popups saying it can't connect to SQL Server at all. The popups say it was trying to connect using named pipes. I went to the Surface Area tool and enabled named pipes on remote connections, but RS Config Mgr still can't connect.

It seems like my installation is hosed. I thought Crystal Enterprise was hard to use, but this SSRS is worse! I'm open to suggestions. Does anyone know a reliable way to configure the db connection for Reporting Services?|||I uninstalled and reinstalled the Reporting Services components. This at least allowed RS Config Mgr to connect to SQL Server. However, when I attempt to create a new database for RS, each step succeeds except the last one. For the "Setting Connection Info for the Reporting Server" task, there

was a yellow '!', with the explanation, "Although saving the database

connection succeeded, the report server cannot access internal

information about this deployment to determine if the current

configuration is valid for this edition. ..." The RS Service is still logging errors in the event log saying it cannot connect. I give up.

Connection Issue

I am a novice and have SQL 2k5 installed on my server running windows SBS 2003. I am able to connect to the database from my workstation and I am able to view all the fields of the database but I am not able to view any of the records contained in the database. Can someone please guide me. I need to be able to view add and delete records using Access as a front end program to SQL. Thank you.

How are you connecting to the server? What 'client tool' are you using? (Visual Studio, SSMS, QA, etc.)

|||I am connecting to the server via an intranet enviroment and I am logged on with administrator properties.|||

The most important thing to note is how you are connecting, like windows Authentication or with a SQL username and password.

If you can connect to the SQL Server and see some of the fields, and schema, then depending on the way you are connecting it could be that the user does not have access to SELECT from the tables.

If you are using Access to connect, you should be able to do what you want to do if you are using the appropriate permissions inside SQL for your tables.

Ben Miller

|||

Thank you!

I reset all the ODBC connections and I was able to view the data. Your response was very helpful. Thank you once more.

Connecting to SQL Server 2k5 Dev Edition

I recently removed my June CTP version of SS2k5 and installed the release developer version on a 2 proc server with Win Server 2003 SP1 (I'll call this machine Server), and suddenly I cannot connect to this box over our network. I have SS2k5 Dev Edition installed on my local machine (WinXP, and I'll call this machine Local), and was able to connect to the CTP version on the server with no problems. Now, not only can I not connect (or see the server through the network browse) to the Server from Local, nor can I connect or see my Local from the Server. I used the Surface Area Configuration tool to allow TCP/IP and Named Pipe connections (Local was set to local only connections, but was working fine to and from the CTP version of the Server), but to no avail.

Are there any other settings that I should look at? I'm working a bit in the dark here.

Thank you,

NoelHi Noel,

So I understand the problem you're experiencing, let me restate the problem. :)

On SERVER, which is Windows Server 2003 SP1, you have SQL 2005 Dev RTM.
On LOCAL, which is Windows XP SP2, you also have SQL 2005 Dev RTM.

When you say you "cannot see" SERVER from LOCAL or LOCAL from SERVER, what do you mean? Can you PING LOCAL from SERVER and vice versa by name? by IP?

Did you run the Surface Area Configurator on both machines and ensure Local + Remote access was enabled? After enabling TCP\IP and Named Pipes on LOCAL, did you stop and restart the service (this has to be done for the service to start listening on those protocols)?

jeff.|||Also, if your instance name is a named instance you'll need to start the SQL Browser service. If the Windows Firewall is enabled you'll need to add exceptions for sqlservr.exe and sqlbrowser.exe. To find the path to the correct SQL Server executable check out the "Path to executable" in the Windows Service Control Manager for the SQL Server service.

This blog for SQL Server Express is also relevant for Dev edition: http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

Dan