Showing posts with label named. Show all posts

Monday, March 19, 2012

Connection issue with named instance

Hi all,
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instances
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
SylvainCan you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E1101E0-D5C1-4DBD-A398-FE485DFA439B.scuk
&
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
Regards
Surajit
"Sylvain" wrote:
> Hi all,
> Since the replacement of new client workstation I've trouble for connection
> of these new machines ot My different SQL Servers. On this configuration we
> only speak of client/server connected on the same LAN without any antivirus
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse network
> they can't see named instance (only default instance is displayed (port 1433)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instances
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instance
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
> Can you please follow below links and let us know if it was helpful for you.
> http://sqljunkies.com/How%20To/2E1101E0-D5C1-4DBD-A398-FE485DFA439B.scuk
> &
> http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
> > Hi all,
> >
> > Since the replacement of new client workstation I've trouble for connection
> > of these new machines ot My different SQL Servers. On this configuration we
> > only speak of client/server connected on the same LAN without any antivirus
> > enabled.
> > When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> > to my server via for example ODBC and in this case when they browse network
> > they can't see named instance (only default instance is displayed (port 1433)
> > !). Next to it if they force the name in the connection string they still
> > can't connect ot the server, because of the port resolution. My workaround
> > today is to force the port in the connection string of each client (quite
> > heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> > enable.
> > I've performed different test of connection (telnet 1433 work, PortQRY
> > return that 1433 and 1434 are working (but it didn't return all the instances
> > name), ping OK, tracert ok,...)
> >
> > Any help would be appreciated, thanks in advance
> > Sylvain

Connection issue with named instance

Hi all,
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instances
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
Sylvain
Can you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E110...85DFA439B.scuk
&
http://support.microsoft.com/default...b;en-us;287932
Regards
Surajit
"Sylvain" wrote:

> Hi all,
> Since the replacement of new client workstation I've trouble for connection
> of these new machines ot My different SQL Servers. On this configuration we
> only speak of client/server connected on the same LAN without any antivirus
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse network
> they can't see named instance (only default instance is displayed (port 1433)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instances
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain
|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instance
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
[vbcol=seagreen]
> Can you please follow below links and let us know if it was helpful for you.
> http://sqljunkies.com/How%20To/2E110...85DFA439B.scuk
> &
> http://support.microsoft.com/default...b;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:

Connection issue with named instance

Hi all,
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433
)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instance
s
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
SylvainCan you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E11...485DFA439B.scuk
&
http://support.microsoft.com/defaul...kb;en-us;287932
Regards
Surajit
"Sylvain" wrote:

> Hi all,
> Since the replacement of new client workstation I've trouble for connectio
n
> of these new machines ot My different SQL Servers. On this configuration w
e
> only speak of client/server connected on the same LAN without any antiviru
s
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse networ
k
> they can't see named instance (only default instance is displayed (port 14
33)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instan
ces
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instanc
e
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
[vbcol=seagreen]
> Can you please follow below links and let us know if it was helpful for yo
u.
> http://sqljunkies.com/How%20To/2E11...485DFA439B.scuk
> &
> http://support.microsoft.com/defaul...kb;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
>

Sunday, March 11, 2012

Connection from XP SP2 to Windows 2003 R2 with SQL Server 2005 failed

I cannot make named pipe connection with client by ODBC DSA.

Here is information. Refering to http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1.

[1] Client side:

1. What is the connection string in you app or DSN? (please specify) ODBC \\[SERVER_NAME]\pipe\sql\guery

2. If client fails to connect, what is the client error messages? (please specify) Connection failed: SQLState: ’01000’ SQL ServerError: 1326 [Microsoft][ODBC SQL Server Driver][Named Pipes]connectionOpen (Connect()) Connection failed: SQLState: ’08001’ SQL Server Error: 17 [Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.

3. Is the client remote or local to the SQL server machine? [Remote | Local]

4. Can you ping your server? [YES | NO ]

In cmd.exe console, type “ping -a <server_name>”.

5. Can you telnet to your SQL Server? [YES | NO, please specify the error message ]

In cmd.exe console, type “telnet <server name> port, where port can be 135, 445 or sql_server_tcp_port. If your cmd.exe console turns into a complete black screen with a cursor flushing on top left corner, you are connected. Type ctrl+’[‘ to bring up telnet prompt and type “quit” <enter>.

7. Is your client computer in the same domain as the Server computer? (Same domain | Different domains | WorkGroup)

8. What protocol the client enabled? [Shared Memory | TCPIP | Named Pipes].

9. Do you have aliases configured that match the server name portion of your connection string? If so, please check if it is correct. You can use cliconfg.exe (SS 2000) or SQL Server Configuration Manager (SS 2005) to configure the alias. [NO]

10. Do you select force encryption on server and/or client? [NO]

I was able to connect with TCP/IP settings.

[2] Server side:

1. What is the MS SQL version? [SQL Server 2005]

2. What is the SKU of MS SQL? [Enterprise | Standard | Workgroup | Express (or MSDE) | other (please specify)].

3. What is the SQL Server Protocol enabled? [Shared Memory | TCPIP | Named Pipes ]. Use SQL Server Configuration Manager to configure it and check ERRORLOG or event log to confirm.

4. Does the server start successfully? [YES | NO] If not what is the error messages in the SQL server ERRORLOG?

5. If SQL Server is a named instance, is the SQL browser enabled? [YES | NO]

6. What is the account that the SQL Server is running under?[Local System | Network Service | Domain Account]

7. Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider? [YES | NO | not applicable | not enabled]

8. Do you make firewall exception for SQL Browser UDP port 1434? In SQL2000, you still need to make firewall exception for UDP port 1434 in order to support named instance.[YES | NO | not applicable | not enabled]

I could connect locally with named pipes.

Do I have to make some file shares manually?

[2a] Tool Used to Connect

What tool or Application are you using to connect to SQL Server (eg: Visual Studio, SQL Server Management Studio, SQLCmd.exe, OSQL, etc) and especially the version of SQL Server (Express, Workgroup, Standard, Enterprise, Developer)

[3] Platform:

1. What is the OS version? [Windows XPSP2 | Windows 2003 | Windows 2000 | Windows 98 | others (please specify ) ].

1. Server [Windows Server 2003 R2]

2. Client [Windows XP SP2]

2. Do you have third party antivirus, anti-spareware software installed? [Symantec | Norton | other (please specify) ? NO].

[4] Misc:

1. If you have certificate configuration issue: Please use “certutil.exe –v –store my” to dump certificate specific info and post it in your question. [NO]

What happens if you execute
net use \\[server_name]\ipc$
from the client?

connection from virtual ip address to firewall?

Hi,
We try to connect from a same named instance to a linked sql server in the
DMZ. The firewall has been set up to allow connections from the virtual ip
address of the instance to pass through and the linked server has been set
up correctly to connect through TCP/IP and the correct port. However, we
cannot connect and we see on the firewall that the requests are coming from
the active cluster node, not from the virtual ip address (even if we open a
Remote Desktop connection to the virtual server name). How can we solve
this?
Hans
This is how clustering works. Make sure you have the Node's IP defined for
access through the firewall.
Cheers,
Rod
"HVE" <eylenh@.hotmail.com> wrote in message
news:1e3yhnhwapvac.q9iklq79zipt$.dlg@.40tude.net...
> Hi,
> We try to connect from a same named instance to a linked sql server in the
> DMZ. The firewall has been set up to allow connections from the virtual ip
> address of the instance to pass through and the linked server has been set
> up correctly to connect through TCP/IP and the correct port. However, we
> cannot connect and we see on the firewall that the requests are coming
from
> the active cluster node, not from the virtual ip address (even if we open
a
> Remote Desktop connection to the virtual server name). How can we solve
> this?
> Hans

Saturday, February 25, 2012

Connection Error from ASP.Net under IIS: provider: Named Pipes Provider, error: 40

We experience the 40 error when our Asp.net code runs under IIS and uses named pipes to a sql server 2005 named instance.

We've tried all suggestions found on blogs and KB articles such as making sure the named pipes protocol is enabled, making sure the Browser service is started, making sure Allow Remote Connections is enabled, making sure we're not using Asp.Net 2.0 membership providers, and the list goes on and on.

We boiled it down to a simple test scenario. We open a SqlConnection to the sql 2005 box in the code with the intention of binding a datareader to a gridview, but it never gets that far because the connection.Open() fails.

If we run this test application as a virtual directory in IIS and Asp.Net 2.0, the connection.Open() fails.

If we run this test application from Visual Studio .Net using Cassini (PWS), the connection.Open() succeeds and binds to the gridview.

What could be causing the connection to fail under IIS but succeed under Cassini? We've tried setting IIS to run as a domain user and with digest authentication enabled. That made no difference.

Any help or insight is appreciated!

Could you try to answer the following questions though some of them may be already implied by your post?

(1) Is this remote connection or local connection?

(2) Is the account that runing your visual studio.net the the same as your IIS. Do you impersonate client connection in IIS?

(3) Can you make direct connection to your backend sqlserver from your virtual studio or sql server management studio?

(4) Can you try connecting using TCP instead? If not, what is the error code?

|||

(1) Is this remote connection or local connection?

-Remote connection

(2) Is the account that runing your visual studio.net the the same as your IIS. Do you impersonate client connection in IIS?

-Same account, windows authentication. No impersonation

(3) Can you make direct connection to your backend sqlserver from your virtual studio or sql server management studio?

-Management Studio works, Cassini works.. IIS does not

(4) Can you try connecting using TCP instead? If not, what is the error code?

TCP gives "server actively refused connection" error

|||

Does your connection string like "servername\instancename" or something else?

The TCP failure indicates either the server TCP listener is not up or client uses different TCP port to connect. So please check whether the TCP is enabled or not. Restart the server after the configuration change. Then check if the connection string has instancename specified. Once you find out which port the server is listening on, you can also use "tcpervername,port" to connection to the server.

Connection error : SQL Server does not exist or access denied

hello , i'm very new to sql server.

i'm using sql server 200 & winXP. I have a local server called "JO" and a dsn named "LocalServer".

Authentication is sql server authentication & window with username of "cying" and password "admin"

i can ping my server "JO" but cannot telnet it's sql_server_tcp_port.

this is the error code i obtained when try to open the connection:

Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

my connection string is as below :

set objcon = server.CreateObject("ADODB.Connection")

strConnection = "Provider=MSDASQL;Driver={SQL Server};Server=local;Data Source=LocalServer;User ID=cying;Password=admin;Persist Security Info=False"

objcon.open, strConnection

is there anything wrong with my connection string or setting?

pls help, thanks in advance

ok, i can now connect to sql server but another error occurs:

Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'Provider=MSDASQL'.

my connection string is as below :

strConnection = "Provider=MSDASQL;Driver={SQL Server};Server=(local);User ID=cying;Password=admin;Persist Security Info=False;"

do i need to put in data source? i created the user id under enterprise manager, (local) > serucity > logins. server access is set to permit. i even try log in with sa account but still comes out the same error.

pls help, thank u

|||

Hi,

It looks like you're running into a known problem described in the BOL (http://msdn2.microsoft.com/en-us/library/ms190204.aspx):

Note:

To enhance security, SQL Server 2005 disables TCP/IP connectivity to SQL Server 2005 for new installations of the Developer, Evaluation, and SQL Server Express editions. OLEDB applications connecting with MDAC 2.8 cannot connect to the default instance on local server using ".", "(local)", or (<blank>) as the server name. To resolve this, supply the server name, or enable TCP/IP on the server. Connections to local named instances are not affected, and connections using SQL Native Client are not affected. Installations where a previous installation of SQL Server is present might not be affected.

Try changing "(local)" to the name of the server.

Il-Sung.

|||

i manage to connect to db finally after changing the code, here's my new connection string

strConn = "Provider=MSDASQL;Driver={SQL Server};server=(local);uid=cying;pwd=admin;database=cying"

II-Sung, i'm using sql server 2000 and hav TCP/IP enabled

i think the cause of problem is uid & pwd, previously i used user name & password and failed to establish a connection

thanks for ur help though =)

Friday, February 24, 2012

Connection denied. Please help

Hello, everyone. I'm new in Reporting Services 2005. I encountered a confused connection problem. I'm running a named instance (called 'sql05') of SQL Server 2005 Standard Edition(a SQL Server 2000 instance as my default) on my Windows XP Professional machine. I log in Windows XP as a member of Administrators group. When I came into SQL Server Management Studio and connect to my local reporting server using Windows Authentication, the report server denied my connection request 'actively'. The service is running but it denied my connection. But when I use the same method to connect to my database engine and Analysis Services in Management Studio, no problem has happened. Does anyone have similar experiences? I appreciate for any help. Thank you!Ha, I found the solution. I mistakely altered the settings in Reporting Services Configuation Manager. On the 'Database Setup' page, I mistakely changed the 'Credential Type' from 'Service Credentials' to 'Windows Credentials' and input my WindowsXP username and password. This seems error-prone. When I changes back to 'Service Credentials' and apply it, the problem above solved. Can you help me distinguish between these Credential Types? Which type is suitable?

Connection confusion

When I try to run my application on our server I cannot connect to the SQL Server that's on the same machine (a named instance). I get the SqlException:Login failed for ("null") user. Not a trusted SQL Server connection. I CAN however, connect to this database from the IDE on my laptop--the app works just fine.

I have reconfigured the IIS, the default site and the directory for the app: I turned off anonymous access, turned it on, changed users, changed passwords, etc. I have done the same for the database, added users, changed permissions, added permissions, etc., you get the picture...none of it worked. (I changed the connection string to those users/pwds)

I saw on an MS site that this error can occur under heavy loads...but that's not the case here.

Please help! Thanks!!

You have what is called orphan user, it happened to me recently I had to delete some files in the master but there are other solutions. You may have moved the database from another server or recreated it, the login you are trying to use only exist in the Master but is not available. Try the links below for solutions. If you are still having the problem, I would restore from backup using the device option in the backup wizard. Hope this helps.

http://vyaskn.tripod.com/troubleshooting_orphan_users.htm
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=12615

|||

Sorry to be so long responding, got pulled to another issue...

I'm not sure that an orphan user isn't the problem, but I ran sp_helplogins and the results show user ASPNET mapped toservername/ASPNET.I think that means that ASPNET is recognized as a validated user. This would explain why I can connect from my laptop IDE (Visual Studio.NET) with no problems, wouldn't it?

Is there something within the .NET framework installed on the server that needs to be changed or upgraded?

Thanks again for your help!

Sunday, February 19, 2012

Connection and Logon Code Problem

Hi...

I am having problem with my Crystal Report XI Connection and Logon Code. I am using VB.NET 2003

1. I made a non-embedded report document named AccountReport.rpt and save it in "D:\Report\AccountReport.rpt"

2. AccountReport.rpt connection properties

a. I used an odbc(RDO) connection string

Provider=MSDataShape;Driver={Microsoft Access Driver (*.mdb)};Dbq=D:\Account.mdb;Uid=admin;Pwd=userxxx;

3. In My VB.NET code:

a. VB.NET Code:

Dim AccountRPT As New ReportDocument
'Instantiate my report document

AccountRPT.Load(Path.GetFullPath(".") & "D:\Report\AccountReport.rpt")
'Load the report

AccountRPT.DataSourceConnections(0).SetConnection("Account", "F:\Business\Grocerry\Account.mdb", "admin", "userxxx")
'You can see here that I change my database location from "D:\Account.mdb" to "F:\Business\Grocerry\Account.mdb".

AccountRPT.SetParameterValue("BALANCE", 2000)
'Passed a value into a parameter list

frmGraph.crvReport.ReportSource = AccountRPT
'Set my report document as a report source for viewing

4. The Problem.

a. The connection of my Report Document "AccountRPT" does not change from "D:\Account.mdb" to "F:\Business\Grocerry\Account.mdb".

If anybody can help please do...

Sincerely...Check with this link :

http://support.businessobjects.com/library/kbase/articles/c2010371.asp

It may help you to solve your problem.

Thanks,
Vidu.

Friday, February 17, 2012

Connecting without SQL Browser

I'm unable to connect to my named instance of SQL Server 2005 when the
Browser service isn't running on the server.
I do specify the port that the SQL Server instance is listening to in the
connection string, as in SERVER:PORT
Is it impossible to connect to an instance of SQL Server when the browser
isn't running? I have verified that the server will accept remote
connections, and I can connect as soon as I start the browser.Hello,
You may want to check the SQL 2005 process ID in task manager, and then run
the following command to see if the PID is listening on the proper port
netstat -aon
If it is OK, please try to telnet the port from client:
telnet <server name> <port number>
If not, it seems there is firewall blocking the port. Please check
Windows/third party firewall on the server to test
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Connecting without SQL Browser
>thread-index: AcZCiOBLNVbTQlN8TSihYXkvAvuyTQ==>X-WBNR-Posting-Host: 84.147.139.248
>From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
>Subject: Connecting without SQL Browser
>Date: Wed, 8 Mar 2006 00:18:27 -0800
>Lines: 7
>Message-ID: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423714
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>I'm unable to connect to my named instance of SQL Server 2005 when the
>Browser service isn't running on the server.
>I do specify the port that the SQL Server instance is listening to in the
>connection string, as in SERVER:PORT
>Is it impossible to connect to an instance of SQL Server when the browser
>isn't running? I have verified that the server will accept remote
>connections, and I can connect as soon as I start the browser.
>|||From the SQL Server log:
Server process ID is 1552
Server is listening on [ 'any' <ipv4> 1743].
Server local connection provider is ready to accept connection on [
\\.\pipe\SQLLocal\S5 ].
Server local connection provider is ready to accept connection on [
\\.\pipe\MSSQL$S5\sql\query ].
Server is listening on [ 127.0.0.1 <ipv4> 1744].
Dedicated admin connection support was established for listening locally on
port 1744.
SQL Server is now ready for client connections. This is an informational
message; no user action is required.
From netstat -aon
TCP 0.0.0.0:1743 0.0.0.0:0 LISTENING 1552
TCP 127.0.0.1:1744 0.0.0.0:0 LISTENING 1552
Connecting with Telnet from the client gives "Connect failed", also when the
Browser is started.
"Peter Yang [MSFT]" wrote:
> Hello,
> You may want to check the SQL 2005 process ID in task manager, and then run
> the following command to see if the PID is listening on the proper port
> netstat -aon
> If it is OK, please try to telnet the port from client:
> telnet <server name> <port number>
> If not, it seems there is firewall blocking the port. Please check
> Windows/third party firewall on the server to test
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --
> >Thread-Topic: Connecting without SQL Browser
> >thread-index: AcZCiOBLNVbTQlN8TSihYXkvAvuyTQ==> >X-WBNR-Posting-Host: 84.147.139.248
> >From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
> >Subject: Connecting without SQL Browser
> >Date: Wed, 8 Mar 2006 00:18:27 -0800
> >Lines: 7
> >Message-ID: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
> >Newsgroups: microsoft.public.sqlserver.server
> >Path: TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423714
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >X-Tomcat-NG: microsoft.public.sqlserver.server
> >
> >I'm unable to connect to my named instance of SQL Server 2005 when the
> >Browser service isn't running on the server.
> >I do specify the port that the SQL Server instance is listening to in the
> >connection string, as in SERVER:PORT
> >Is it impossible to connect to an instance of SQL Server when the browser
> >isn't running? I have verified that the server will accept remote
> >connections, and I can connect as soon as I start the browser.
> >
>|||Hello,
Apparently you have firewall on the server blocks port 1552. Please
temporarily disable firewalls to test the situation. If it works, you could
open port on firwall to solve the problem.
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Connecting without SQL Browser
>thread-index: AcZCp+TVAS+gwqT9QQy7/KMJ33jN/g==>X-WBNR-Posting-Host: 84.147.139.248
>From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
>References: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
<ODsJWLqQGHA.5448@.TK2MSFTNGXA03.phx.gbl>
>Subject: RE: Connecting without SQL Browser
>Date: Wed, 8 Mar 2006 04:00:29 -0800
>Lines: 87
>Message-ID: <7F0CD604-75BE-4858-9745-BC6E621A7D15@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423729
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>From the SQL Server log:
>Server process ID is 1552
>Server is listening on [ 'any' <ipv4> 1743].
>Server local connection provider is ready to accept connection on [
>\\.\pipe\SQLLocal\S5 ].
>Server local connection provider is ready to accept connection on [
>\\.\pipe\MSSQL$S5\sql\query ].
>Server is listening on [ 127.0.0.1 <ipv4> 1744].
>Dedicated admin connection support was established for listening locally
on
>port 1744.
>SQL Server is now ready for client connections. This is an informational
>message; no user action is required.
>From netstat -aon
>TCP 0.0.0.0:1743 0.0.0.0:0 LISTENING 1552
>TCP 127.0.0.1:1744 0.0.0.0:0 LISTENING 1552
>Connecting with Telnet from the client gives "Connect failed", also when
the
>Browser is started.
>
>"Peter Yang [MSFT]" wrote:
>> Hello,
>> You may want to check the SQL 2005 process ID in task manager, and then
run
>> the following command to see if the PID is listening on the proper port
>> netstat -aon
>> If it is OK, please try to telnet the port from client:
>> telnet <server name> <port number>
>> If not, it seems there is firewall blocking the port. Please check
>> Windows/third party firewall on the server to test
>> Best Regards,
>> Peter Yang
>> MCSE2000/2003, MCSA, MCDBA
>> Microsoft Online Partner Support
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> =====================================================>>
>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>>
>> --
>> >Thread-Topic: Connecting without SQL Browser
>> >thread-index: AcZCiOBLNVbTQlN8TSihYXkvAvuyTQ==>> >X-WBNR-Posting-Host: 84.147.139.248
>> >From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
>> >Subject: Connecting without SQL Browser
>> >Date: Wed, 8 Mar 2006 00:18:27 -0800
>> >Lines: 7
>> >Message-ID: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>> >Newsgroups: microsoft.public.sqlserver.server
>> >Path: TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423714
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >X-Tomcat-NG: microsoft.public.sqlserver.server
>> >
>> >I'm unable to connect to my named instance of SQL Server 2005 when the
>> >Browser service isn't running on the server.
>> >I do specify the port that the SQL Server instance is listening to in
the
>> >connection string, as in SERVER:PORT
>> >Is it impossible to connect to an instance of SQL Server when the
browser
>> >isn't running? I have verified that the server will accept remote
>> >connections, and I can connect as soon as I start the browser.
>> >
>>
>|||1552 is the process id of sql server in the example.
"Peter Yang [MSFT]" wrote:
> Hello,
> Apparently you have firewall on the server blocks port 1552. Please
> temporarily disable firewalls to test the situation. If it works, you could
> open port on firwall to solve the problem.
> Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --
> >Thread-Topic: Connecting without SQL Browser
> >thread-index: AcZCp+TVAS+gwqT9QQy7/KMJ33jN/g==> >X-WBNR-Posting-Host: 84.147.139.248
> >From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
> >References: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
> <ODsJWLqQGHA.5448@.TK2MSFTNGXA03.phx.gbl>
> >Subject: RE: Connecting without SQL Browser
> >Date: Wed, 8 Mar 2006 04:00:29 -0800
> >Lines: 87
> >Message-ID: <7F0CD604-75BE-4858-9745-BC6E621A7D15@.microsoft.com>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
> >Newsgroups: microsoft.public.sqlserver.server
> >Path: TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423729
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >X-Tomcat-NG: microsoft.public.sqlserver.server
> >
> >From the SQL Server log:
> >Server process ID is 1552
> >Server is listening on [ 'any' <ipv4> 1743].
> >Server local connection provider is ready to accept connection on [
> >\\.\pipe\SQLLocal\S5 ].
> >Server local connection provider is ready to accept connection on [
> >\\.\pipe\MSSQL$S5\sql\query ].
> >Server is listening on [ 127.0.0.1 <ipv4> 1744].
> >Dedicated admin connection support was established for listening locally
> on
> >port 1744.
> >SQL Server is now ready for client connections. This is an informational
> >message; no user action is required.
> >
> >From netstat -aon
> >TCP 0.0.0.0:1743 0.0.0.0:0 LISTENING 1552
> >TCP 127.0.0.1:1744 0.0.0.0:0 LISTENING 1552
> >
> >Connecting with Telnet from the client gives "Connect failed", also when
> the
> >Browser is started.
> >
> >
> >
> >"Peter Yang [MSFT]" wrote:
> >
> >> Hello,
> >>
> >> You may want to check the SQL 2005 process ID in task manager, and then
> run
> >> the following command to see if the PID is listening on the proper port
> >>
> >> netstat -aon
> >>
> >> If it is OK, please try to telnet the port from client:
> >>
> >> telnet <server name> <port number>
> >>
> >> If not, it seems there is firewall blocking the port. Please check
> >> Windows/third party firewall on the server to test
> >>
> >> Best Regards,
> >>
> >> Peter Yang
> >> MCSE2000/2003, MCSA, MCDBA
> >> Microsoft Online Partner Support
> >>
> >> When responding to posts, please "Reply to Group" via your newsreader so
> >> that others may learn and benefit from your issue.
> >>
> >> =====================================================> >>
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >>
> >>
> >> --
> >> >Thread-Topic: Connecting without SQL Browser
> >> >thread-index: AcZCiOBLNVbTQlN8TSihYXkvAvuyTQ==> >> >X-WBNR-Posting-Host: 84.147.139.248
> >> >From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
> >> >Subject: Connecting without SQL Browser
> >> >Date: Wed, 8 Mar 2006 00:18:27 -0800
> >> >Lines: 7
> >> >Message-ID: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
> >> >MIME-Version: 1.0
> >> >Content-Type: text/plain;
> >> > charset="Utf-8"
> >> >Content-Transfer-Encoding: 7bit
> >> >X-Newsreader: Microsoft CDO for Windows 2000
> >> >Content-Class: urn:content-classes:message
> >> >Importance: normal
> >> >Priority: normal
> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
> >> >Newsgroups: microsoft.public.sqlserver.server
> >> >Path: TK2MSFTNGXA03.phx.gbl
> >> >Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423714
> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >> >X-Tomcat-NG: microsoft.public.sqlserver.server
> >> >
> >> >I'm unable to connect to my named instance of SQL Server 2005 when the
> >> >Browser service isn't running on the server.
> >> >I do specify the port that the SQL Server instance is listening to in
> the
> >> >connection string, as in SERVER:PORT
> >> >Is it impossible to connect to an instance of SQL Server when the
> browser
> >> >isn't running? I have verified that the server will accept remote
> >> >connections, and I can connect as soon as I start the browser.
> >> >
> >>
> >>
> >
>|||Hello Pat,
Sorry. My typo. Server port 1743 shall be opened by firewall. Also, client
network shall be configured to 1743 as well.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
>Thread-Topic: Connecting without SQL Browser
>thread-index: AcZMNgMtU2vKHeRwTEqMU7ZbMxx2xA==>X-WBNR-Posting-Host: 84.147.154.98
>From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
>References: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
<ODsJWLqQGHA.5448@.TK2MSFTNGXA03.phx.gbl>
<7F0CD604-75BE-4858-9745-BC6E621A7D15@.microsoft.com>
<PBj2TK1QGHA.6216@.TK2MSFTNGXA03.phx.gbl>
>Subject: RE: Connecting without SQL Browser
>Date: Mon, 20 Mar 2006 07:50:29 -0800
>Lines: 146
>Message-ID: <B93CC259-A26F-444C-93C7-1155FDC5310C@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.server
>Path: TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:424932
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>X-Tomcat-NG: microsoft.public.sqlserver.server
>1552 is the process id of sql server in the example.
>"Peter Yang [MSFT]" wrote:
>> Hello,
>> Apparently you have firewall on the server blocks port 1552. Please
>> temporarily disable firewalls to test the situation. If it works, you
could
>> open port on firwall to solve the problem.
>> Regards,
>> Peter Yang
>> MCSE2000/2003, MCSA, MCDBA
>> Microsoft Online Partner Support
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> =====================================================>> This posting is provided "AS IS" with no warranties, and confers no
rights.
>>
>> --
>> >Thread-Topic: Connecting without SQL Browser
>> >thread-index: AcZCp+TVAS+gwqT9QQy7/KMJ33jN/g==>> >X-WBNR-Posting-Host: 84.147.139.248
>> >From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
>> >References: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
>> <ODsJWLqQGHA.5448@.TK2MSFTNGXA03.phx.gbl>
>> >Subject: RE: Connecting without SQL Browser
>> >Date: Wed, 8 Mar 2006 04:00:29 -0800
>> >Lines: 87
>> >Message-ID: <7F0CD604-75BE-4858-9745-BC6E621A7D15@.microsoft.com>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>> >Newsgroups: microsoft.public.sqlserver.server
>> >Path: TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423729
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >X-Tomcat-NG: microsoft.public.sqlserver.server
>> >
>> >From the SQL Server log:
>> >Server process ID is 1552
>> >Server is listening on [ 'any' <ipv4> 1743].
>> >Server local connection provider is ready to accept connection on [
>> >\\.\pipe\SQLLocal\S5 ].
>> >Server local connection provider is ready to accept connection on [
>> >\\.\pipe\MSSQL$S5\sql\query ].
>> >Server is listening on [ 127.0.0.1 <ipv4> 1744].
>> >Dedicated admin connection support was established for listening
locally
>> on
>> >port 1744.
>> >SQL Server is now ready for client connections. This is an
informational
>> >message; no user action is required.
>> >
>> >From netstat -aon
>> >TCP 0.0.0.0:1743 0.0.0.0:0 LISTENING 1552
>> >TCP 127.0.0.1:1744 0.0.0.0:0 LISTENING 1552
>> >
>> >Connecting with Telnet from the client gives "Connect failed", also
when
>> the
>> >Browser is started.
>> >
>> >
>> >
>> >"Peter Yang [MSFT]" wrote:
>> >
>> >> Hello,
>> >>
>> >> You may want to check the SQL 2005 process ID in task manager, and
then
>> run
>> >> the following command to see if the PID is listening on the proper
port
>> >>
>> >> netstat -aon
>> >>
>> >> If it is OK, please try to telnet the port from client:
>> >>
>> >> telnet <server name> <port number>
>> >>
>> >> If not, it seems there is firewall blocking the port. Please check
>> >> Windows/third party firewall on the server to test
>> >>
>> >> Best Regards,
>> >>
>> >> Peter Yang
>> >> MCSE2000/2003, MCSA, MCDBA
>> >> Microsoft Online Partner Support
>> >>
>> >> When responding to posts, please "Reply to Group" via your newsreader
so
>> >> that others may learn and benefit from your issue.
>> >>
>> >> =====================================================>> >>
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> >>
>> >>
>> >> --
>> >> >Thread-Topic: Connecting without SQL Browser
>> >> >thread-index: AcZCiOBLNVbTQlN8TSihYXkvAvuyTQ==>> >> >X-WBNR-Posting-Host: 84.147.139.248
>> >> >From: =?Utf-8?B?UGF0?= <pat@.online.nospam>
>> >> >Subject: Connecting without SQL Browser
>> >> >Date: Wed, 8 Mar 2006 00:18:27 -0800
>> >> >Lines: 7
>> >> >Message-ID: <87FE193F-FB5E-4CF3-ACA0-6AAA087B9E47@.microsoft.com>
>> >> >MIME-Version: 1.0
>> >> >Content-Type: text/plain;
>> >> > charset="Utf-8"
>> >> >Content-Transfer-Encoding: 7bit
>> >> >X-Newsreader: Microsoft CDO for Windows 2000
>> >> >Content-Class: urn:content-classes:message
>> >> >Importance: normal
>> >> >Priority: normal
>> >> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>> >> >Newsgroups: microsoft.public.sqlserver.server
>> >> >Path: TK2MSFTNGXA03.phx.gbl
>> >> >Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.sqlserver.server:423714
>> >> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >> >X-Tomcat-NG: microsoft.public.sqlserver.server
>> >> >
>> >> >I'm unable to connect to my named instance of SQL Server 2005 when
the
>> >> >Browser service isn't running on the server.
>> >> >I do specify the port that the SQL Server instance is listening to
in
>> the
>> >> >connection string, as in SERVER:PORT
>> >> >Is it impossible to connect to an instance of SQL Server when the
>> browser
>> >> >isn't running? I have verified that the server will accept remote
>> >> >connections, and I can connect as soon as I start the browser.
>> >> >
>> >>
>> >>
>> >
>>
>

Connecting without SQL Browser

Tuesday, February 14, 2012

Connecting to wrong SQL Server

I have a machine where I have installed Visual Studio 2005 including SQLExpr
ess. I have also installed MSDE2000. They are both named instances:
MyMachine\SQLExpress and MyMachine\S3MSDE.
Locally everything works fine. But when I connect to MyMachine from an other
machine with the connectstring containing '...Data
Source=MyMachine\S3MSDE,1234;...' I always end up beeing connected to the SQ
LExpress instance of SQL Server.
WHY?
ToschIt looks like you are always connecting to the default port. Try starting
the SQL Server Browser Service on MyMachine. It is the browser service that
resolves the name to the correct port.
--
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Tosch" <tosch_nospam@.swissonline.ch> wrote in message
news:o50292l98e45ugu0j7cej427gm5qeaj5ju@.
4ax.com...
>I have a machine where I have installed Visual Studio 2005 including
>SQLExpress. I have also installed MSDE2000. They are both named instances:
> MyMachine\SQLExpress and MyMachine\S3MSDE.
> Locally everything works fine. But when I connect to MyMachine from an
> other machine with the connectstring containing '...Data
> Source=MyMachine\S3MSDE,1234;...' I always end up beeing connected to the
> SQLExpress instance of SQL Server.
> WHY?
> Tosch
>|||It looks like you are always connecting to the default port. Try starting
the SQL Server Browser Service on MyMachine. It is the browser service that
resolves the name to the correct port.
--
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Tosch" <tosch_nospam@.swissonline.ch> wrote in message
news:o50292l98e45ugu0j7cej427gm5qeaj5ju@.
4ax.com...
>I have a machine where I have installed Visual Studio 2005 including
>SQLExpress. I have also installed MSDE2000. They are both named instances:
> MyMachine\SQLExpress and MyMachine\S3MSDE.
> Locally everything works fine. But when I connect to MyMachine from an
> other machine with the connectstring containing '...Data
> Source=MyMachine\S3MSDE,1234;...' I always end up beeing connected to the
> SQLExpress instance of SQL Server.
> WHY?
> Tosch
>|||ok, since I changed the port number to the port number msde2000 uses everyth
ing works fine. Apparently if you add the port number the name of the
sqlserver/instance doesn't seem to matter.
Tosch
On Thu, 15 Jun 2006 08:05:26 -0700, "Rick Byham [MS]" <rickbyh@.online.mi
crosoft.com> wrote:

>It looks like you are always connecting to the default port. Try starting
>the SQL Server Browser Service on MyMachine. It is the browser service that
>resolves the name to the correct port.|||ok, since I changed the port number to the port number msde2000 uses everyth
ing works fine. Apparently if you add the port number the name of the
sqlserver/instance doesn't seem to matter.
Tosch
On Thu, 15 Jun 2006 08:05:26 -0700, "Rick Byham [MS]" <rickbyh@.online.mi
crosoft.com> wrote:

>It looks like you are always connecting to the default port. Try starting
>the SQL Server Browser Service on MyMachine. It is the browser service that
>resolves the name to the correct port.

Connecting to SSIS in Management Studio.

Hi:

I have 4 named instances of SQL 2005 running on one of our sales server (dont ask me why I have 4 instances.Its a beefy box btw). All the instances have SSIS Packages (around 6-7 in each instance) saved to the SQL server and not to the file system. The issue is every time i need to look at the packages or export the packages from SSMS I have to edit the MsDtsSrvr.ini.xml and type in the named instance name within the <ServerName></ServerName> tag . I then have to restart my SSIS. I dont see an easier approach to this method.

This is causing me a lot of unnecessary time waste. is there anyway this can be automated where in i can pass the instance name dynamically to the ini file or even more best, can I have all the instance names in the ini file and some how look at the packages in each Instance. I am not sure how having all the instance names in the ini file woud resolve the issue though.

I know I can use BIDS which is much more flexible and a recommended approach but need a solution for looking at SSIS packages through SSMS in all of the 4 instances. I look forward to recommendations from anyone who have better ideas and suggestions.

Thank you

you could create a console app that edits the xml file and re-starts ssis.|||

Thanks Duane. Do you happen to have an example code sample on how to do that?. I can build looking from that.

Thanks again

|||

Ankith wrote:

Thanks Duane. Do you happen to have an example code sample on how to do that?. I can build looking from that.
Thanks again
AK

unfortunately, i don't have a code example to share with you. however, writing such an application should be fairly straightforward (provided that you know .NET). the .NET system.xml namespace provides a number of classes to manipulate xml data. also, the system.serviceprocess namespace provides classes to manipulate windows services.

i hope this helps.

|||

Hi Duane:

I got this working. I am posting the code snippet for the benefit of others. I have created a SQL Agent job that changes the server name in the XML ini file and restarts SSIS. Restarting I do it through the Job step. Works great.

if (File.Exists(xmlFile))
{
XmlDocument doc = new XmlDocument();
doc.Load(xmlFile);

XmlNode node = doc.SelectSingleNode(@."//*[local-name()='ServerName']");

if (node == null)
{
Console.Write("Node does not exist");
}
else
{
node.InnerText = value;
}

node = null;

doc.Save(xmlFile);

Thanks again for your help.

|||Instead of switching between the servers, you can simply add them all to the SSIS service config file! Simply copy the <FOLDER> tag (till the end - </FOLDER>) as many times as you have SQL instances, give each one unique <NAME>, save config file and restart the SSIS service:

...
<TopLevelFolders>
<Folder xsi:type="SqlServerFolder">
<Name>Sql1</Name>
<ServerName>.\Instance1</ServerName>
</Folder>
<Folder xsi:type="SqlServerFolder">
<Name>Sql2</Name>
<ServerName>.\Instance2</ServerName>
</Folder>
<Folder xsi:type="SqlServerFolder">
<Name>Sql3</Name>
<ServerName>.\Instance3</ServerName>
</Folder>
</TopLevelFolders>
...|||

WOW!!!. Thats cool. Thanks Michael.I used your solution and it works great and I dont need my code anymore. DBAs who dont have much experience with C# will find your method really helpful.

Thanks for posting it.

Best Regards

Connecting to SSIS in Management Studio.

Hi:

Thank you

you could create a console app that edits the xml file and re-starts ssis.|||

Thanks Duane. Do you happen to have an example code sample on how to do that?. I can build looking from that.

Thanks again

|||

Ankith wrote:

Thanks Duane. Do you happen to have an example code sample on how to do that?. I can build looking from that.
Thanks again
AK

i hope this helps.

|||

Hi Duane:

if (File.Exists(xmlFile))
{
XmlDocument doc = new XmlDocument();
doc.Load(xmlFile);

XmlNode node = doc.SelectSingleNode(@."//*[local-name()='ServerName']");

if (node == null)
{
Console.Write("Node does not exist");
}
else
{
node.InnerText = value;
}

node = null;

doc.Save(xmlFile);

Thanks again for your help.

WOW!!!. Thats cool. Thanks Michael.I used your solution and it works great and I dont need my code anymore. DBAs who dont have much experience with C# will find your method really helpful.

Thanks for posting it.

Best Regards

Connecting to SQL2000 using DNS Alias/Named Pipes

Hi,
I have a very confusing issue.
I am attempting to connect to a SQL2000 server using Named Pipes and a
DNS Alias without success. I get the sql server does not exist or
access is denied error. I can successfully connect using TCPIP
sockets however.
If I connect to the server using it's own servername I can connect
using Named Pipes or TCPIP sockets.
Any ideas?
Named pipes does not use DNS so a DNS alias will not work with named pipes.
Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
connection works.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<xEV$7$j0EHA.3152@.cpmsftngxa10.phx.gbl>...
> Named pipes does not use DNS so a DNS alias will not work with named pipes.
> Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
> connection works.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
Rand
I now have this working after using the DisableStrictNameChecking fix.
I can now use the DNA Alias for the SQL server ver named pipes.

Connecting to SQL2000 using DNS Alias/Named Pipes

Hi,
I have a very confusing issue.
I am attempting to connect to a SQL2000 server using Named Pipes and a
DNS Alias without success. I get the sql server does not exist or
access is denied error. I can successfully connect using TCPIP
sockets however.
If I connect to the server using it's own servername I can connect
using Named Pipes or TCPIP sockets.
Any ideas'Named pipes does not use DNS so a DNS alias will not work with named pipes.
Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
connection works.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<xEV$7$j0EHA.3152@.cpmsftngxa10.phx.gbl>...
> Named pipes does not use DNS so a DNS alias will not work with named pipes.
> Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
> connection works.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
Rand
I now have this working after using the DisableStrictNameChecking fix.
I can now use the DNA Alias for the SQL server ver named pipes.

Connecting to SQL2000 using DNS Alias/Named Pipes

Hi,
I have a very confusing issue.
I am attempting to connect to a SQL2000 server using Named Pipes and a
DNS Alias without success. I get the sql server does not exist or
access is denied error. I can successfully connect using TCPIP
sockets however.
If I connect to the server using it's own servername I can connect
using Named Pipes or TCPIP sockets.
Any ideas'Named pipes does not use DNS so a DNS alias will not work with named pipes.
Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS the
connection works.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<xEV$7$j0EHA.3152@.cpm
sftngxa10.phx.gbl>...
> Named pipes does not use DNS so a DNS alias will not work with named pipes
.
> Named pipes uses a broadcast of the NetBios name. Since TCP/IP uses DNS th
e
> connection works.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
Rand
I now have this working after using the DisableStrictNameChecking fix.
I can now use the DNA Alias for the SQL server ver named pipes.

Sunday, February 12, 2012

Connecting to SQL Server over the LAN

Hello,
I have SQL Server installed on a machine named SQLHOST with an IP
address 192.168.1.4, and the SQL server is installed with the instance
named 'CLIENTDB'. Now on another machine, I have a client software
written using .NET which connects using the following string:
Server=SQLHOST\CLIENTDB;Initial Catalog=clients;User
ID=clientdb;Password=xyz;Trusted_connect
ion=false; Persist Security
Info=false;Pooling=false;
This works fine. But when I replace "SQLHOST" with "192.168.1.4" it
does not connect. Why is this? Is there no way one can connect with an
IP Address? As this is going to be deployed across the LAN, I would
rather rely on the IP address than the computer name... Does this make
sense?
Looking forward to your reply,
Thanks in advance,
JimHello Jim,
The instance name is significant in connecting to SQL Server. Try using 192.
168.1.4\CLIENTDB.

> I would
> rather rely on the IP address than the computer name... Does this make
> sense?
Yes, but not the way you are doing it. You'd be better off to get DNS setup
and going first so you can easily change the dotted-quad for SQLHOST without
having redeploy your app...
Thanks!
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/|||Hello Kent,
Thank you for the quick reply.
I tried using 192.168.1.4\CLIENTDB but I get an error saying SQL
Server or instance name not found. The only way it has worked is by
supplying the computer name...
I can not set up a DNS system right now as we are very low on time.
Thanks again,
Regards,
Jim
On Mar 21, 4:15 pm, Kent Tegels <kteg...@.develop.com> wrote:
> Hello Jim,
> The instance name is significant in connecting to SQL Server. Try using 19
2.168.1.4\CLIENTDB.
>
> Yes, but not the way you are doing it. You'd be better off to get DNS setu
p
> and going first so you can easily change the dotted-quad for SQLHOST witho
ut
> having redeploy your app...
> Thanks!
> Kent Tegels
> DevelopMentorhttp://staff.develop.com/ktegels/

Monday, March 19, 2012

Connection issue with named instance

Connection issue with named instance

Connection issue with named instance

Sunday, March 11, 2012

Connection from XP SP2 to Windows 2003 R2 with SQL Server 2005 failed

Do I have to make some file shares manually?

connection from virtual ip address to firewall?

Saturday, February 25, 2012

Connection Error from ASP.Net under IIS: provider: Named Pipes Provider, error: 40

Connection error : SQL Server does not exist or access denied

Friday, February 24, 2012

Connection denied. Please help

Connection confusion

Sunday, February 19, 2012

Connection and Logon Code Problem

Friday, February 17, 2012

Connecting without SQL Browser

Connecting without SQL Browser

Connecting without SQL Browser

Tuesday, February 14, 2012

Connecting to wrong SQL Server

Connecting to SSIS in Management Studio.

Connecting to SSIS in Management Studio.

Connecting to SQL2000 using DNS Alias/Named Pipes

Connecting to SQL2000 using DNS Alias/Named Pipes

Connecting to SQL2000 using DNS Alias/Named Pipes

Sunday, February 12, 2012

Connecting to SQL Server over the LAN

asp sql server

Blog Archive

About Me