Showing posts with label w2k3. Show all posts
Showing posts with label w2k3. Show all posts

Monday, March 19, 2012

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 from our developer

Hi,
SQL 2005 EE is installed on W2k3 box and firewall is off in this server.
From my client machine, my window account and that developer window account
all can login into this server with ODBC, sql client, telent to 1433 or VS
connection. But, this developer can't login to SQL server from him machine
with any appliction. He is in the same domain as server and my machine. I
don't know what's the reason to cause this issue now.
Please advise. Thank you.
Lynn
Best Regards,
Lynn
What is the exact error message and error number he gets
when he tries to log into SQL Server?
-Sue
On Thu, 22 Mar 2007 10:33:45 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>Hi,
>SQL 2005 EE is installed on W2k3 box and firewall is off in this server.
>From my client machine, my window account and that developer window account
>all can login into this server with ODBC, sql client, telent to 1433 or VS
>connection. But, this developer can't login to SQL server from him machine
>with any appliction. He is in the same domain as server and my machine. I
>don't know what's the reason to cause this issue now.
>Please advise. Thank you.
>Lynn
|||We only enable Shared Memory and TCP/IP protocal in server side. And, those
are the error they are getting.
osql -- SQL server doesn't exist or access denied
Query Analyzer -- General network error. Check your network documentation
VS 2005 -- (without specifing TCP protocal in connection) A connection was
succssfully established with the server, but then an error occured during the
pre-login handshake. When connecting ....(provider: Named Pipes provider,
error: 0 - No process is on the ther end of the pipe)
VS 2005 -- (specify TCP protocal in connection) An error has occurred while
establishing a connection to the server. When connecting to SQL server 2005,
this failure may be caused by the fact that under the default settings ...
(provider: TCP provider: 0 -- A connection attempt failed because the
connected party didn't not properly respond after a period of tiem, or
established connection failed because connected host has failed to respond.)
Again, this developer is able to login by using my machine with his WIN
account.
After I enable Named Pipes in server. This developer is able to connect to
server on his machine by using Named Pipe.
Firewall is off in the server, so I can't think of the issue for TCP
connection on developer's machine.
Please advise. Thank you.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> What is the exact error message and error number he gets
> when he tries to log into SQL Server?
> -Sue
> On Thu, 22 Mar 2007 10:33:45 -0700, Lynn
> <Lynn@.discussions.microsoft.com> wrote:
>
>
|||Check the following article in Books Online:
http://msdn2.microsoft.com/en-us/library/ms175496.aspx
-Sue
On Fri, 23 Mar 2007 09:15:08 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>We only enable Shared Memory and TCP/IP protocal in server side. And, those
>are the error they are getting.
>osql -- SQL server doesn't exist or access denied
>Query Analyzer -- General network error. Check your network documentation
>VS 2005 -- (without specifing TCP protocal in connection) A connection was
>succssfully established with the server, but then an error occured during the
>pre-login handshake. When connecting ....(provider: Named Pipes provider,
>error: 0 - No process is on the ther end of the pipe)
>VS 2005 -- (specify TCP protocal in connection) An error has occurred while
>establishing a connection to the server. When connecting to SQL server 2005,
>this failure may be caused by the fact that under the default settings ...
>(provider: TCP provider: 0 -- A connection attempt failed because the
>connected party didn't not properly respond after a period of tiem, or
>established connection failed because connected host has failed to respond.)
>Again, this developer is able to login by using my machine with his WIN
>account.
>After I enable Named Pipes in server. This developer is able to connect to
>server on his machine by using Named Pipe.
>Firewall is off in the server, so I can't think of the issue for TCP
>connection on developer's machine.
>Please advise. Thank you.
|||Sue,
The developer's client protocol order is TCP and NP. We didn't enable Named
Pipe in server at the beginning, that's why the first message is NP message
due to client will try to connect in the protocol order in the client. As I
menetioned, after I turn on Named Pipes in server, user's machine is able to
connect to server. But, the issue our developers had is that they couldn't
connect with TCP protocol from their machine. (I can connect by TCP protocol
from my machine. The developer login to my machine and his win account can
connect to the server as well). His machine is able to connect to our SQL
2000 with TCP protocol, but just can't connect to 2005 with TCP protocol. I
was thinging is firewall in server to caused this issue, but firewall didn't
enable in the server at all. So, I don't know what cause the issue.
Please advise.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> Check the following article in Books Online:
> http://msdn2.microsoft.com/en-us/library/ms175496.aspx
> -Sue
> On Fri, 23 Mar 2007 09:15:08 -0700, Lynn
> <Lynn@.discussions.microsoft.com> wrote:
>
>
|||When you get symptoms like this where it only affects the
user on a particular PC then you need to look at that PC.
You'd probably start by testing basic connectivity to the
server from the PC: Can the user ping the server by name,
can the user ping the server by IP, what network related
issues are found in the Event logs on the PC, can the user
connect to the server using sqlcmd, etc. Also, have you
tried logging in from that users PC?
If you find that the issue is comes up only with Management
Studio, have the user increase the connect timeout in SSMS:
When logging on, click on the options button in the Connect
to Server window and increase the connection timeout to
something greater than the 15 second default.
It would also be worth checking the users MDAC installation
using the component checker. You can download this from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
You may also want to look at applying the latest SQL Server
service pack to the client on that PC having problems.
-Sue
On Thu, 29 Mar 2007 15:38:05 -0700, Lynn
<Lynn@.discussions.microsoft.com> wrote:

>Sue,
>The developer's client protocol order is TCP and NP. We didn't enable Named
>Pipe in server at the beginning, that's why the first message is NP message
>due to client will try to connect in the protocol order in the client. As I
>menetioned, after I turn on Named Pipes in server, user's machine is able to
>connect to server. But, the issue our developers had is that they couldn't
>connect with TCP protocol from their machine. (I can connect by TCP protocol
>from my machine. The developer login to my machine and his win account can
>connect to the server as well). His machine is able to connect to our SQL
>2000 with TCP protocol, but just can't connect to 2005 with TCP protocol. I
>was thinging is firewall in server to caused this issue, but firewall didn't
>enable in the server at all. So, I don't know what cause the issue.
>Please advise.
|||Sue,
Thank you again. Definitely, we already checked the network connect from
those developers machine. The connection issue happens to all related
developers. The developers were able to ping the server by name and IP from
their machine. But, the issue only happened on connecting to SQL 2005 with
TCP protocol. We tested through ODBC (with TCP/IP), osql, telnet to 1433
port, VS, but all connection were failed.
One developer already reinstall SQL 2005 client, but the problem is still
resisted. Will ask them to update to sp2 and go from there.
Best Regards,
Lynn
"Sue Hoegemeier" wrote:

> When you get symptoms like this where it only affects the
> user on a particular PC then you need to look at that PC.
> You'd probably start by testing basic connectivity to the
> server from the PC: Can the user ping the server by name,
> can the user ping the server by IP, what network related
> issues are found in the Event logs on the PC, can the user
> connect to the server using sqlcmd, etc. Also, have you
> tried logging in from that users PC?
> If you find that the issue is comes up only with Management
> Studio, have the user increase the connect timeout in SSMS:
> When logging on, click on the options button in the Connect
> to Server window and increase the connection timeout to
> something greater than the 15 second default.
> It would also be worth checking the users MDAC installation
> using the component checker. You can download this from:
> http://msdn2.microsoft.com/en-us/data/aa937730.aspx
> You may also want to look at applying the latest SQL Server
> service pack to the client on that PC having problems.
> -Sue

Thursday, March 8, 2012

connection failed port 25

I have two w2k3 SP1 server setup with smtp for relay. Both servers are
pretty much a mirror of each other. Locally, I can telnet from one server
but not the other. When I tried to telnet locally from the servers with its
own local IP to port 25, I get connection failed to port 25. There is no
differences between the two servers except their IP.
There must be a differnece between them, did you try to portscan these
servers to see wheter the port is activated and listens. What dies
Netstat -a say ? Once we had an issue about port 25, becasue a virus scanner
was installed which blocked the port 25 to forbid open relays, perhaps this
could be a point.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"manoa" <manoa@.discussions.microsoft.com> schrieb im Newsbeitrag
news:F8B1E423-3882-4A79-9077-113018F558D1@.microsoft.com...
>I have two w2k3 SP1 server setup with smtp for relay. Both servers are
> pretty much a mirror of each other. Locally, I can telnet from one server
> but not the other. When I tried to telnet locally from the servers with
> its
> own local IP to port 25, I get connection failed to port 25. There is no
> differences between the two servers except their IP.

connection failed port 25

I have two w2k3 SP1 server setup with smtp for relay. Both servers are
pretty much a mirror of each other. Locally, I can telnet from one server
but not the other. When I tried to telnet locally from the servers with its
own local IP to port 25, I get connection failed to port 25. There is no
differences between the two servers except their IP.There must be a differnece between them, did you try to portscan these
servers to see wheter the port is activated and listens. What dies
Netstat -a say ? Once we had an issue about port 25, becasue a virus scanner
was installed which blocked the port 25 to forbid open relays, perhaps this
could be a point.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"manoa" <manoa@.discussions.microsoft.com> schrieb im Newsbeitrag
news:F8B1E423-3882-4A79-9077-113018F558D1@.microsoft.com...
>I have two w2k3 SP1 server setup with smtp for relay. Both servers are
> pretty much a mirror of each other. Locally, I can telnet from one server
> but not the other. When I tried to telnet locally from the servers with
> its
> own local IP to port 25, I get connection failed to port 25. There is no
> differences between the two servers except their IP.

connection failed port 25

I have two w2k3 SP1 server setup with smtp for relay. Both servers are
pretty much a mirror of each other. Locally, I can telnet from one server
but not the other. When I tried to telnet locally from the servers with its
own local IP to port 25, I get connection failed to port 25. There is no
differences between the two servers except their IP.There must be a differnece between them, did you try to portscan these
servers to see wheter the port is activated and listens. What dies
Netstat -a say ? Once we had an issue about port 25, becasue a virus scanner
was installed which blocked the port 25 to forbid open relays, perhaps this
could be a point.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"manoa" <manoa@.discussions.microsoft.com> schrieb im Newsbeitrag
news:F8B1E423-3882-4A79-9077-113018F558D1@.microsoft.com...
>I have two w2k3 SP1 server setup with smtp for relay. Both servers are
> pretty much a mirror of each other. Locally, I can telnet from one server
> but not the other. When I tried to telnet locally from the servers with
> its
> own local IP to port 25, I get connection failed to port 25. There is no
> differences between the two servers except their IP.

Tuesday, February 14, 2012

Connecting to SSAS on workgroup W2K3 server using SQL Server Management Studio...how?

Hi All,

I'm trying to connect to SSAS on a workgroup (i.e. non-AD) Windows 2003SP1 server from my XPSP2 PC, using SQL Server Management Studio and/or Visual Studio, with no luck.

I have set up SSAS to accept anonymous connections, firewall is off, no anti-virus software, etc. I have added 'Everyone', 'NT Authority\ANONYMOUS LOGON' to the SSAS 'server' role (I don't care about security at this stage).

I can connect to SSAS from my PC via code, though I have found out by trial-and-error that I need to specify a connection string that includes a User ID and Password; e.g.:

"Data Source=sandbox; Provider=msolap; Initial Catalog=Analysis Services Tutorial;User ID=some_user;password=password;"

When I try to connect to the server using Management Studio, there is no option to change the authentication user name or password - it is always set to the local pc\local user combination - so the attempt fails with the 'An existing connection was forcibly closed by the remote host (System)' error message.

A profiler trace review shows that the PC is connecting to the server, but it is failing authentication - most likely because it is trying local pc\local user credentials.

Unfortunately my organisation doesn't use AD - we use Novell NDS (aaarghh!) - hence the need to persist with standalone servers. I need to be able to maintain/deploy to standalone servers.

Does anyone have any ideas on how I can use Management Studio on a PC to connect to SSAS on a workgroup/standalone server?

Thanks in advance,

Tim Pedersen.

First I am sure that SSAS only accepts windows authentication.

Next, a simple way, but not secure, is to add your windows account to the administrators account on the stand alone server.

Last. You will have to run the tool, called surface area detection(or something near) configuration tool, in order for SSAS to accept external connections.

Kind regards

Thomas Ivarsson

|||

Thanks,

I've given up trying to connect via Management Studio. I just have to wait until our organisation rolls out AD fully sometime late this year. In the meantime I just have to use the backup-restore database, etc. options, and use remote desktop...

|||

Another thing to try is: Try setting RequireClientAuthentication sever property to 0.

This allows any user to connect to your server.

Here is a whitepaper about server configuration properties: http://download.microsoft.com/download/4/f/8/4f8f2dc9-a9a7-4b68-98cb-163482c95e0b/SSASProperties.doc

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi,

Thanks for the link to the white paper, the information in it is quite useful.

However, I have managed to solve the problem via another route. It looks as though the RequireClientAuthentication property is ignored in a workgroup network situation.

I did a network trace on the TCP conversation between the PC and the server and found that there was a SSPI handshake taking place which looked like it was failing...so this indicated that maybe I needed to ensure that there was some form of shared credentials, even though RequireClientAuthentication is set to false. So I created a user on the server with the same user id as on the PC, with identical password...and hey presto I can connect!

I am doing some more testing - it looks as though the server user still needs to be added to SSAS security for everything to work correctly.

I think that in the absence of AD/Kerebos SSAS falls back to NTLM/workgroup security with matching user name/passwords on all the computers, regardless of the setting of RequireClientAuthentication. Perhaps RequireClientAuthentication only has meaning in an AD-based network...?

Cheers,

Tim Pedersen