Hello there
I have two servers on diffrent computer
Both of them are registered together
One of them declared as a publisher and the otherone as subscripter
When i add the subscript it gave me an error of connecting between them and
the synchronize is not active
where the problem can be?
Normally when you get the subscription is not active it means that your
publication is not activated.
in your publication database do this
sp_changepublication 'publicationname','status','active'
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Oded Kovach" <roygoldh@.hotmail.com> wrote in message
news:O8FBVRMlEHA.712@.TK2MSFTNGP09.phx.gbl...
> Hello there
> I have two servers on diffrent computer
> Both of them are registered together
> One of them declared as a publisher and the otherone as subscripter
> When i add the subscript it gave me an error of connecting between them
and
> the synchronize is not active
> where the problem can be?
>
Showing posts with label servers. Show all posts
Showing posts with label servers. Show all posts
Tuesday, March 27, 2012
Connection problem
I have 2 sql servers running on different machines. I want to manage both
servers from one machine. When I try to add the other server in the
enterprise manager it gives me the error "sql server does not exist or access
denied". I am using a valid log on user name that is set up on the server, I
have even tried using a windows username. I know that the problem has to lie
in authentication because I know the server exist. Anyone know of anything I
may be doing wrong?"Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> I have 2 sql servers running on different machines. I want to manage both
> servers from one machine. When I try to add the other server in the
> enterprise manager it gives me the error "sql server does not exist or
access
> denied". I am using a valid log on user name that is set up on the
server, I
> have even tried using a windows username. I know that the problem has to
lie
> in authentication because I know the server exist. Anyone know of
anything I
> may be doing wrong?
To rule out the server permissions issue, in other words your account has
permissions on the server itself -- try using an account that has
administrative rights on the target server and sysadmin permissions on SQL
Server.
Steve|||Ok here is what I tried. I went to the remote sql server and created a
windows user that is part of the admin group. I then went to the enterprise
manager on the remote sql server and created a user which I browsed for and
got from the windows users list. I gave that login SA rights on the sql
server. I then went back to the other server and tried to register the
remote sql server using sql authentication. I used the username and password
that I had created and I still get the same error message. Any ideas?
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Another thing I forgot to mention. I also tried to register the other server
on the remote server (the reverse of what I have been trying). When I go to
register the server I see seven or so other servers that we have here at
work; however when I have been doing it on the other computer I only see one
server (that being the remote sql server). I am wondering what may cause
this and if it might have something to do with the login issue.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Other things I have tried:
Pinging the remote sql server - works fine
telnet to port 1433 on the remote server - does NOT work
there is not a firewall between the two machines.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Problem Solved: I was really simple actually, all I had to do was go to the
properties of the remote sql server and configure the network configuration
to enable tcp/ip using port 1433
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>sqlsql
servers from one machine. When I try to add the other server in the
enterprise manager it gives me the error "sql server does not exist or access
denied". I am using a valid log on user name that is set up on the server, I
have even tried using a windows username. I know that the problem has to lie
in authentication because I know the server exist. Anyone know of anything I
may be doing wrong?"Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> I have 2 sql servers running on different machines. I want to manage both
> servers from one machine. When I try to add the other server in the
> enterprise manager it gives me the error "sql server does not exist or
access
> denied". I am using a valid log on user name that is set up on the
server, I
> have even tried using a windows username. I know that the problem has to
lie
> in authentication because I know the server exist. Anyone know of
anything I
> may be doing wrong?
To rule out the server permissions issue, in other words your account has
permissions on the server itself -- try using an account that has
administrative rights on the target server and sysadmin permissions on SQL
Server.
Steve|||Ok here is what I tried. I went to the remote sql server and created a
windows user that is part of the admin group. I then went to the enterprise
manager on the remote sql server and created a user which I browsed for and
got from the windows users list. I gave that login SA rights on the sql
server. I then went back to the other server and tried to register the
remote sql server using sql authentication. I used the username and password
that I had created and I still get the same error message. Any ideas?
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Another thing I forgot to mention. I also tried to register the other server
on the remote server (the reverse of what I have been trying). When I go to
register the server I see seven or so other servers that we have here at
work; however when I have been doing it on the other computer I only see one
server (that being the remote sql server). I am wondering what may cause
this and if it might have something to do with the login issue.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Other things I have tried:
Pinging the remote sql server - works fine
telnet to port 1433 on the remote server - does NOT work
there is not a firewall between the two machines.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Problem Solved: I was really simple actually, all I had to do was go to the
properties of the remote sql server and configure the network configuration
to enable tcp/ip using port 1433
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>sqlsql
Sunday, March 25, 2012
Connection problem
Strange database problem.
I have 2 servers one running as webserver and the other as Database server running MSSQL 2000 SP3.
They are connected i 2 ways. Through a public net using static IP and through a direct cable using another IP.
My problem is that I cannot connect to or from the database through the crossed cable (I run a DTS which imports a zipped access file from an FTP account on the webserver).
Running through the public net works fine but not through the crossed/direct cable.
All other connecting (ping, filesharing, FTP not through DTS, etc) works fine through that cable but ODBC connections from the webserver don't and neither does DTS access from the database server.
Does anyone have a clue.I assume there is a different IP associated with the crossed-cable connection. Configure your ODBC to use that IP address instead of the server name.|||That's what I couldn't do. However everything worked out after restarting the webbserver. Seems like it was just a glitch.sqlsql
I have 2 servers one running as webserver and the other as Database server running MSSQL 2000 SP3.
They are connected i 2 ways. Through a public net using static IP and through a direct cable using another IP.
My problem is that I cannot connect to or from the database through the crossed cable (I run a DTS which imports a zipped access file from an FTP account on the webserver).
Running through the public net works fine but not through the crossed/direct cable.
All other connecting (ping, filesharing, FTP not through DTS, etc) works fine through that cable but ODBC connections from the webserver don't and neither does DTS access from the database server.
Does anyone have a clue.I assume there is a different IP associated with the crossed-cable connection. Configure your ODBC to use that IP address instead of the server name.|||That's what I couldn't do. However everything worked out after restarting the webbserver. Seems like it was just a glitch.sqlsql
Connection problem
I have 2 sql servers running on different machines. I want to manage both
servers from one machine. When I try to add the other server in the
enterprise manager it gives me the error "sql server does not exist or access
denied". I am using a valid log on user name that is set up on the server, I
have even tried using a windows username. I know that the problem has to lie
in authentication because I know the server exist. Anyone know of anything I
may be doing wrong?
"Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> I have 2 sql servers running on different machines. I want to manage both
> servers from one machine. When I try to add the other server in the
> enterprise manager it gives me the error "sql server does not exist or
access
> denied". I am using a valid log on user name that is set up on the
server, I
> have even tried using a windows username. I know that the problem has to
lie
> in authentication because I know the server exist. Anyone know of
anything I
> may be doing wrong?
To rule out the server permissions issue, in other words your account has
permissions on the server itself -- try using an account that has
administrative rights on the target server and sysadmin permissions on SQL
Server.
Steve
|||Ok here is what I tried. I went to the remote sql server and created a
windows user that is part of the admin group. I then went to the enterprise
manager on the remote sql server and created a user which I browsed for and
got from the windows users list. I gave that login SA rights on the sql
server. I then went back to the other server and tried to register the
remote sql server using sql authentication. I used the username and password
that I had created and I still get the same error message. Any ideas?
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Another thing I forgot to mention. I also tried to register the other server
on the remote server (the reverse of what I have been trying). When I go to
register the server I see seven or so other servers that we have here at
work; however when I have been doing it on the other computer I only see one
server (that being the remote sql server). I am wondering what may cause
this and if it might have something to do with the login issue.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Other things I have tried:
Pinging the remote sql server - works fine
telnet to port 1433 on the remote server - does NOT work
there is not a firewall between the two machines.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Problem Solved: I was really simple actually, all I had to do was go to the
properties of the remote sql server and configure the network configuration
to enable tcp/ip using port 1433
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
sqlsql
servers from one machine. When I try to add the other server in the
enterprise manager it gives me the error "sql server does not exist or access
denied". I am using a valid log on user name that is set up on the server, I
have even tried using a windows username. I know that the problem has to lie
in authentication because I know the server exist. Anyone know of anything I
may be doing wrong?
"Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> I have 2 sql servers running on different machines. I want to manage both
> servers from one machine. When I try to add the other server in the
> enterprise manager it gives me the error "sql server does not exist or
access
> denied". I am using a valid log on user name that is set up on the
server, I
> have even tried using a windows username. I know that the problem has to
lie
> in authentication because I know the server exist. Anyone know of
anything I
> may be doing wrong?
To rule out the server permissions issue, in other words your account has
permissions on the server itself -- try using an account that has
administrative rights on the target server and sysadmin permissions on SQL
Server.
Steve
|||Ok here is what I tried. I went to the remote sql server and created a
windows user that is part of the admin group. I then went to the enterprise
manager on the remote sql server and created a user which I browsed for and
got from the windows users list. I gave that login SA rights on the sql
server. I then went back to the other server and tried to register the
remote sql server using sql authentication. I used the username and password
that I had created and I still get the same error message. Any ideas?
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Another thing I forgot to mention. I also tried to register the other server
on the remote server (the reverse of what I have been trying). When I go to
register the server I see seven or so other servers that we have here at
work; however when I have been doing it on the other computer I only see one
server (that being the remote sql server). I am wondering what may cause
this and if it might have something to do with the login issue.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Other things I have tried:
Pinging the remote sql server - works fine
telnet to port 1433 on the remote server - does NOT work
there is not a firewall between the two machines.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Problem Solved: I was really simple actually, all I had to do was go to the
properties of the remote sql server and configure the network configuration
to enable tcp/ip using port 1433
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
sqlsql
Tuesday, March 20, 2012
Connection options from *nix to SQL Server 2000
Hi All,
There is a possibility that we may need to move our existing W2K servers and
our custom application over to *nix.
I am interested to know what are the options available to us if we stick
with SQL Server 2000 Enterprise as the database on a W2K or W2003 OS.
Is JDBC the way to go? Is there a better option? Likewise we currently use
ATL to access SQL from our application, would an alternative solution offer
the same level of performance and stability?
Any help would be very much appreciated.
Thanks in advance.
Phil
Phil:
I think you have to basic options for a Java app on UNIX to SQL Server
2000 -- stick w/ JDBC or use a ODBC driver for UNIX, like the one Data
Direct sells.
-shelby
Shelby Goerlitz
Microsoft SQL Server
"philwhite3" <philwhite3@.supanet.com> wrote in message
news:eFNVmSchEHA.3320@.TK2MSFTNGP11.phx.gbl...
> Hi All,
> There is a possibility that we may need to move our existing W2K servers
and
> our custom application over to *nix.
> I am interested to know what are the options available to us if we stick
> with SQL Server 2000 Enterprise as the database on a W2K or W2003 OS.
> Is JDBC the way to go? Is there a better option? Likewise we currently use
> ATL to access SQL from our application, would an alternative solution
offer
> the same level of performance and stability?
> Any help would be very much appreciated.
> Thanks in advance.
> Phil
>
There is a possibility that we may need to move our existing W2K servers and
our custom application over to *nix.
I am interested to know what are the options available to us if we stick
with SQL Server 2000 Enterprise as the database on a W2K or W2003 OS.
Is JDBC the way to go? Is there a better option? Likewise we currently use
ATL to access SQL from our application, would an alternative solution offer
the same level of performance and stability?
Any help would be very much appreciated.
Thanks in advance.
Phil
Phil:
I think you have to basic options for a Java app on UNIX to SQL Server
2000 -- stick w/ JDBC or use a ODBC driver for UNIX, like the one Data
Direct sells.
-shelby
Shelby Goerlitz
Microsoft SQL Server
"philwhite3" <philwhite3@.supanet.com> wrote in message
news:eFNVmSchEHA.3320@.TK2MSFTNGP11.phx.gbl...
> Hi All,
> There is a possibility that we may need to move our existing W2K servers
and
> our custom application over to *nix.
> I am interested to know what are the options available to us if we stick
> with SQL Server 2000 Enterprise as the database on a W2K or W2003 OS.
> Is JDBC the way to go? Is there a better option? Likewise we currently use
> ATL to access SQL from our application, would an alternative solution
offer
> the same level of performance and stability?
> Any help would be very much appreciated.
> Thanks in advance.
> Phil
>
Connection Open (Create File()) /SQL server registration
Hello,
i have SQL 7.0 servers A, B, C, D
when tryin to register server (mmC) A on B,C,D i get the errormessage
"Client unable to establish connection Connection Open (Create File())"
This worked 2 weeks ago.. and we didn't change anything..
Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
have this problem
THX a lot
PIrmincheck connection with QA
try TCP and NP connection
"Pirmin" wrote:
> Hello,
> i have SQL 7.0 servers A, B, C, D
> when tryin to register server (mmC) A on B,C,D i get the errormessage
> "Client unable to establish connection Connection Open (Create File())"
> This worked 2 weeks ago.. and we didn't change anything..
> Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> have this problem
> THX a lot
> PIrmin|||Hi,
sorry.. your answer was litl short 4 me..
wht do you mean with "check connection with QA"
Where do i set the connection frm TCP to NamedPipes on the
ServerRegistration..
Thx
Pirmin
"Aleksandar Grbic" wrote:
> check connection with QA
> try TCP and NP connection
> "Pirmin" wrote:
> > Hello,
> >
> > i have SQL 7.0 servers A, B, C, D
> > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > "Client unable to establish connection Connection Open (Create File())"
> >
> > This worked 2 weeks ago.. and we didn't change anything..
> > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > have this problem
> >
> > THX a lot
> > PIrmin|||you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
check connectivity with sql server
use tcp:<server> to connect with tcp
or
use np:<server> to connect with Named Pipes
later, configure Client Network utility to use one of these protocol and try
connect from mmc
"Pirmin" wrote:
> Hi,
> sorry.. your answer was litl short 4 me..
> wht do you mean with "check connection with QA"
> Where do i set the connection frm TCP to NamedPipes on the
> ServerRegistration..
> Thx
> Pirmin
> "Aleksandar Grbic" wrote:
> > check connection with QA
> > try TCP and NP connection
> >
> > "Pirmin" wrote:
> >
> > > Hello,
> > >
> > > i have SQL 7.0 servers A, B, C, D
> > > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > > "Client unable to establish connection Connection Open (Create File())"
> > >
> > > This worked 2 weeks ago.. and we didn't change anything..
> > > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > > have this problem
> > >
> > > THX a lot
> > > PIrmin|||THX,
well i can't connect via NP nor TCP..
(Pinging works..)
Also checked
"SQL server network config"
TCP and NP are configured..
Anyother idea?
THX
Pirmin
"Aleksandar Grbic" wrote:
> you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> check connectivity with sql server
> use tcp:<server> to connect with tcp
> or
> use np:<server> to connect with Named Pipes
> later, configure Client Network utility to use one of these protocol and try
> connect from mmc
>
> "Pirmin" wrote:
> > Hi,
> >
> > sorry.. your answer was litl short 4 me..
> > wht do you mean with "check connection with QA"
> > Where do i set the connection frm TCP to NamedPipes on the
> > ServerRegistration..
> >
> > Thx
> >
> > Pirmin
> >
> > "Aleksandar Grbic" wrote:
> >
> > > check connection with QA
> > > try TCP and NP connection
> > >
> > > "Pirmin" wrote:
> > >
> > > > Hello,
> > > >
> > > > i have SQL 7.0 servers A, B, C, D
> > > > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > > > "Client unable to establish connection Connection Open (Create File())"
> > > >
> > > > This worked 2 weeks ago.. and we didn't change anything..
> > > > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > > > have this problem
> > > >
> > > > THX a lot
> > > > PIrmin|||firewall?
consult your network admin?
can you connect from server A?
server A listen on 1433?
"Pirmin" wrote:
> THX,
> well i can't connect via NP nor TCP..
> (Pinging works..)
> Also checked
> "SQL server network config"
> TCP and NP are configured..
> Anyother idea?
> THX
> Pirmin
> "Aleksandar Grbic" wrote:
> > you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> > check connectivity with sql server
> >
> > use tcp:<server> to connect with tcp
> > or
> > use np:<server> to connect with Named Pipes
> >
> > later, configure Client Network utility to use one of these protocol and try
> > connect from mmc
> >
> >
> > "Pirmin" wrote:
> >
> > > Hi,
> > >
> > > sorry.. your answer was litl short 4 me..
> > > wht do you mean with "check connection with QA"
> > > Where do i set the connection frm TCP to NamedPipes on the
> > > ServerRegistration..
> > >
> > > Thx
> > >
> > > Pirmin
> > >
> > > "Aleksandar Grbic" wrote:
> > >
> > > > check connection with QA
> > > > try TCP and NP connection
> > > >
> > > > "Pirmin" wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > i have SQL 7.0 servers A, B, C, D
> > > > > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > > > > "Client unable to establish connection Connection Open (Create File())"
> > > > >
> > > > > This worked 2 weeks ago.. and we didn't change anything..
> > > > > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > > > > have this problem
> > > > >
> > > > > THX a lot
> > > > > PIrmin
i have SQL 7.0 servers A, B, C, D
when tryin to register server (mmC) A on B,C,D i get the errormessage
"Client unable to establish connection Connection Open (Create File())"
This worked 2 weeks ago.. and we didn't change anything..
Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
have this problem
THX a lot
PIrmincheck connection with QA
try TCP and NP connection
"Pirmin" wrote:
> Hello,
> i have SQL 7.0 servers A, B, C, D
> when tryin to register server (mmC) A on B,C,D i get the errormessage
> "Client unable to establish connection Connection Open (Create File())"
> This worked 2 weeks ago.. and we didn't change anything..
> Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> have this problem
> THX a lot
> PIrmin|||Hi,
sorry.. your answer was litl short 4 me..
wht do you mean with "check connection with QA"
Where do i set the connection frm TCP to NamedPipes on the
ServerRegistration..
Thx
Pirmin
"Aleksandar Grbic" wrote:
> check connection with QA
> try TCP and NP connection
> "Pirmin" wrote:
> > Hello,
> >
> > i have SQL 7.0 servers A, B, C, D
> > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > "Client unable to establish connection Connection Open (Create File())"
> >
> > This worked 2 weeks ago.. and we didn't change anything..
> > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > have this problem
> >
> > THX a lot
> > PIrmin|||you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
check connectivity with sql server
use tcp:<server> to connect with tcp
or
use np:<server> to connect with Named Pipes
later, configure Client Network utility to use one of these protocol and try
connect from mmc
"Pirmin" wrote:
> Hi,
> sorry.. your answer was litl short 4 me..
> wht do you mean with "check connection with QA"
> Where do i set the connection frm TCP to NamedPipes on the
> ServerRegistration..
> Thx
> Pirmin
> "Aleksandar Grbic" wrote:
> > check connection with QA
> > try TCP and NP connection
> >
> > "Pirmin" wrote:
> >
> > > Hello,
> > >
> > > i have SQL 7.0 servers A, B, C, D
> > > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > > "Client unable to establish connection Connection Open (Create File())"
> > >
> > > This worked 2 weeks ago.. and we didn't change anything..
> > > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > > have this problem
> > >
> > > THX a lot
> > > PIrmin|||THX,
well i can't connect via NP nor TCP..
(Pinging works..)
Also checked
"SQL server network config"
TCP and NP are configured..
Anyother idea?
THX
Pirmin
"Aleksandar Grbic" wrote:
> you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> check connectivity with sql server
> use tcp:<server> to connect with tcp
> or
> use np:<server> to connect with Named Pipes
> later, configure Client Network utility to use one of these protocol and try
> connect from mmc
>
> "Pirmin" wrote:
> > Hi,
> >
> > sorry.. your answer was litl short 4 me..
> > wht do you mean with "check connection with QA"
> > Where do i set the connection frm TCP to NamedPipes on the
> > ServerRegistration..
> >
> > Thx
> >
> > Pirmin
> >
> > "Aleksandar Grbic" wrote:
> >
> > > check connection with QA
> > > try TCP and NP connection
> > >
> > > "Pirmin" wrote:
> > >
> > > > Hello,
> > > >
> > > > i have SQL 7.0 servers A, B, C, D
> > > > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > > > "Client unable to establish connection Connection Open (Create File())"
> > > >
> > > > This worked 2 weeks ago.. and we didn't change anything..
> > > > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > > > have this problem
> > > >
> > > > THX a lot
> > > > PIrmin|||firewall?
consult your network admin?
can you connect from server A?
server A listen on 1433?
"Pirmin" wrote:
> THX,
> well i can't connect via NP nor TCP..
> (Pinging works..)
> Also checked
> "SQL server network config"
> TCP and NP are configured..
> Anyother idea?
> THX
> Pirmin
> "Aleksandar Grbic" wrote:
> > you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> > check connectivity with sql server
> >
> > use tcp:<server> to connect with tcp
> > or
> > use np:<server> to connect with Named Pipes
> >
> > later, configure Client Network utility to use one of these protocol and try
> > connect from mmc
> >
> >
> > "Pirmin" wrote:
> >
> > > Hi,
> > >
> > > sorry.. your answer was litl short 4 me..
> > > wht do you mean with "check connection with QA"
> > > Where do i set the connection frm TCP to NamedPipes on the
> > > ServerRegistration..
> > >
> > > Thx
> > >
> > > Pirmin
> > >
> > > "Aleksandar Grbic" wrote:
> > >
> > > > check connection with QA
> > > > try TCP and NP connection
> > > >
> > > > "Pirmin" wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > i have SQL 7.0 servers A, B, C, D
> > > > > when tryin to register server (mmC) A on B,C,D i get the errormessage
> > > > > "Client unable to establish connection Connection Open (Create File())"
> > > > >
> > > > > This worked 2 weeks ago.. and we didn't change anything..
> > > > > Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> > > > > have this problem
> > > > >
> > > > > THX a lot
> > > > > PIrmin
Connection Open (Create File()) /SQL server registration
Hello,
i have SQL 7.0 servers A, B, C, D
when tryin to register server (mmC) A on B,C,D i get the errormessage
"Client unable to establish connection Connection Open (Create File())"
This worked 2 weeks ago.. and we didn't change anything..
Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
have this problem
THX a lot
PIrmin
check connection with QA
try TCP and NP connection
"Pirmin" wrote:
> Hello,
> i have SQL 7.0 servers A, B, C, D
> when tryin to register server (mmC) A on B,C,D i get the errormessage
> "Client unable to establish connection Connection Open (Create File())"
> This worked 2 weeks ago.. and we didn't change anything..
> Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> have this problem
> THX a lot
> PIrmin
|||Hi,
sorry.. your answer was litl short 4 me..
wht do you mean with "check connection with QA"
Where do i set the connection frm TCP to NamedPipes on the
ServerRegistration..
Thx
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> check connection with QA
> try TCP and NP connection
> "Pirmin" wrote:
|||you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
check connectivity with sql server
use tcp:<server> to connect with tcp
or
use np:<server> to connect with Named Pipes
later, configure Client Network utility to use one of these protocol and try
connect from mmc
"Pirmin" wrote:
[vbcol=seagreen]
> Hi,
> sorry.. your answer was litl short 4 me..
> wht do you mean with "check connection with QA"
> Where do i set the connection frm TCP to NamedPipes on the
> ServerRegistration..
> Thx
> Pirmin
> "Aleksandar Grbic" wrote:
|||THX,
well i can't connect via NP nor TCP..
(Pinging works..)
Also checked
"SQL server network config"
TCP and NP are configured..
Anyother idea?
THX
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> check connectivity with sql server
> use tcp:<server> to connect with tcp
> or
> use np:<server> to connect with Named Pipes
> later, configure Client Network utility to use one of these protocol and try
> connect from mmc
>
> "Pirmin" wrote:
|||firewall?
consult your network admin?
can you connect from server A?
server A listen on 1433?
"Pirmin" wrote:
[vbcol=seagreen]
> THX,
> well i can't connect via NP nor TCP..
> (Pinging works..)
> Also checked
> "SQL server network config"
> TCP and NP are configured..
> Anyother idea?
> THX
> Pirmin
> "Aleksandar Grbic" wrote:
i have SQL 7.0 servers A, B, C, D
when tryin to register server (mmC) A on B,C,D i get the errormessage
"Client unable to establish connection Connection Open (Create File())"
This worked 2 weeks ago.. and we didn't change anything..
Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
have this problem
THX a lot
PIrmin
check connection with QA
try TCP and NP connection
"Pirmin" wrote:
> Hello,
> i have SQL 7.0 servers A, B, C, D
> when tryin to register server (mmC) A on B,C,D i get the errormessage
> "Client unable to establish connection Connection Open (Create File())"
> This worked 2 weeks ago.. and we didn't change anything..
> Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> have this problem
> THX a lot
> PIrmin
|||Hi,
sorry.. your answer was litl short 4 me..
wht do you mean with "check connection with QA"
Where do i set the connection frm TCP to NamedPipes on the
ServerRegistration..
Thx
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> check connection with QA
> try TCP and NP connection
> "Pirmin" wrote:
|||you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
check connectivity with sql server
use tcp:<server> to connect with tcp
or
use np:<server> to connect with Named Pipes
later, configure Client Network utility to use one of these protocol and try
connect from mmc
"Pirmin" wrote:
[vbcol=seagreen]
> Hi,
> sorry.. your answer was litl short 4 me..
> wht do you mean with "check connection with QA"
> Where do i set the connection frm TCP to NamedPipes on the
> ServerRegistration..
> Thx
> Pirmin
> "Aleksandar Grbic" wrote:
|||THX,
well i can't connect via NP nor TCP..
(Pinging works..)
Also checked
"SQL server network config"
TCP and NP are configured..
Anyother idea?
THX
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> check connectivity with sql server
> use tcp:<server> to connect with tcp
> or
> use np:<server> to connect with Named Pipes
> later, configure Client Network utility to use one of these protocol and try
> connect from mmc
>
> "Pirmin" wrote:
|||firewall?
consult your network admin?
can you connect from server A?
server A listen on 1433?
"Pirmin" wrote:
[vbcol=seagreen]
> THX,
> well i can't connect via NP nor TCP..
> (Pinging works..)
> Also checked
> "SQL server network config"
> TCP and NP are configured..
> Anyother idea?
> THX
> Pirmin
> "Aleksandar Grbic" wrote:
Connection Open (Create File()) /SQL server registration
Hello,
i have SQL 7.0 servers A, B, C, D
when tryin to register server (mmC) A on B,C,D i get the errormessage
"Client unable to establish connection Connection Open (Create File())"
This worked 2 weeks ago.. and we didn't change anything..
Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
have this problem
THX a lot
PIrmincheck connection with QA
try TCP and NP connection
"Pirmin" wrote:
> Hello,
> i have SQL 7.0 servers A, B, C, D
> when tryin to register server (mmC) A on B,C,D i get the errormessage
> "Client unable to establish connection Connection Open (Create File())"
> This worked 2 weeks ago.. and we didn't change anything..
> Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> have this problem
> THX a lot
> PIrmin|||Hi,
sorry.. your answer was litl short 4 me..
wht do you mean with "check connection with QA"
Where do i set the connection frm TCP to NamedPipes on the
ServerRegistration..
Thx
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> check connection with QA
> try TCP and NP connection
> "Pirmin" wrote:
>|||you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
check connectivity with sql server
use tcp:<server> to connect with tcp
or
use np:<server> to connect with Named Pipes
later, configure Client Network utility to use one of these protocol and try
connect from mmc
"Pirmin" wrote:
[vbcol=seagreen]
> Hi,
> sorry.. your answer was litl short 4 me..
> wht do you mean with "check connection with QA"
> Where do i set the connection frm TCP to NamedPipes on the
> ServerRegistration..
> Thx
> Pirmin
> "Aleksandar Grbic" wrote:
>|||THX,
well i can't connect via NP nor TCP..
(Pinging works..)
Also checked
"SQL server network config"
TCP and NP are configured..
Anyother idea?
THX
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> check connectivity with sql server
> use tcp:<server> to connect with tcp
> or
> use np:<server> to connect with Named Pipes
> later, configure Client Network utility to use one of these protocol and t
ry
> connect from mmc
>
> "Pirmin" wrote:
>|||firewall?
consult your network admin?
can you connect from server A?
server A listen on 1433?
"Pirmin" wrote:
[vbcol=seagreen]
> THX,
> well i can't connect via NP nor TCP..
> (Pinging works..)
> Also checked
> "SQL server network config"
> TCP and NP are configured..
> Anyother idea?
> THX
> Pirmin
> "Aleksandar Grbic" wrote:
>sqlsql
i have SQL 7.0 servers A, B, C, D
when tryin to register server (mmC) A on B,C,D i get the errormessage
"Client unable to establish connection Connection Open (Create File())"
This worked 2 weeks ago.. and we didn't change anything..
Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
have this problem
THX a lot
PIrmincheck connection with QA
try TCP and NP connection
"Pirmin" wrote:
> Hello,
> i have SQL 7.0 servers A, B, C, D
> when tryin to register server (mmC) A on B,C,D i get the errormessage
> "Client unable to establish connection Connection Open (Create File())"
> This worked 2 weeks ago.. and we didn't change anything..
> Network wise B,C,D "see" A (ping, net-share..) only "sql-server" wise we
> have this problem
> THX a lot
> PIrmin|||Hi,
sorry.. your answer was litl short 4 me..
wht do you mean with "check connection with QA"
Where do i set the connection frm TCP to NamedPipes on the
ServerRegistration..
Thx
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> check connection with QA
> try TCP and NP connection
> "Pirmin" wrote:
>|||you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
check connectivity with sql server
use tcp:<server> to connect with tcp
or
use np:<server> to connect with Named Pipes
later, configure Client Network utility to use one of these protocol and try
connect from mmc
"Pirmin" wrote:
[vbcol=seagreen]
> Hi,
> sorry.. your answer was litl short 4 me..
> wht do you mean with "check connection with QA"
> Where do i set the connection frm TCP to NamedPipes on the
> ServerRegistration..
> Thx
> Pirmin
> "Aleksandar Grbic" wrote:
>|||THX,
well i can't connect via NP nor TCP..
(Pinging works..)
Also checked
"SQL server network config"
TCP and NP are configured..
Anyother idea?
THX
Pirmin
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> you can use Query Analyzer (QA - SQL graphical query tool) - isqlw.exe to
> check connectivity with sql server
> use tcp:<server> to connect with tcp
> or
> use np:<server> to connect with Named Pipes
> later, configure Client Network utility to use one of these protocol and t
ry
> connect from mmc
>
> "Pirmin" wrote:
>|||firewall?
consult your network admin?
can you connect from server A?
server A listen on 1433?
"Pirmin" wrote:
[vbcol=seagreen]
> THX,
> well i can't connect via NP nor TCP..
> (Pinging works..)
> Also checked
> "SQL server network config"
> TCP and NP are configured..
> Anyother idea?
> THX
> Pirmin
> "Aleksandar Grbic" wrote:
>sqlsql
Monday, March 19, 2012
Connection Manager - No available servers
Hi
Windows XP Pro, SQL Server 2005 (Developer) & Visual Studio 2005 (Pro)
New SSIS project (Visual Studio)
New OLE DB/SQL Native client connection.
There's no servers available in the drop down box.
All the services that need to be running are running.
Guess I've missed the obvious here
Cheers
Dave
Hi,
did you try to enter the nae manually ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Yes I did. Will re-try and then post the error.|||Just tried entering the name manually and it worked...
Any ideas why I can't browse to the instance/server?
|||Do you use another port than the default one 1433 ? If so, you will have to make sure that SQL Server browser is started. What for ? See the link here for more information about the SQL Browser.http://msdn2.microsoft.com/en-us/library/ms181087.aspx
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
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
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:
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:
>
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 dts to MySql
Two of our servers have a "MYSql OleDB Provider" Datasource. I have no idea
where they came from but I would like to add this Datasource to my own PC. Is
this something someone likely purchased? Does Microsoft provide it?
Thanks
Hi
Look at the MySQL web site. MS does not provide it.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Snake" wrote:
> Two of our servers have a "MYSql OleDB Provider" Datasource. I have no idea
> where they came from but I would like to add this Datasource to my own PC. Is
> this something someone likely purchased? Does Microsoft provide it?
> Thanks
where they came from but I would like to add this Datasource to my own PC. Is
this something someone likely purchased? Does Microsoft provide it?
Thanks
Hi
Look at the MySQL web site. MS does not provide it.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Snake" wrote:
> Two of our servers have a "MYSql OleDB Provider" Datasource. I have no idea
> where they came from but I would like to add this Datasource to my own PC. Is
> this something someone likely purchased? Does Microsoft provide it?
> Thanks
Connection from dts to MySql
Two of our servers have a "MYSql OleDB Provider" Datasource. I have no idea
where they came from but I would like to add this Datasource to my own PC. I
s
this something someone likely purchased? Does Microsoft provide it?
ThanksHi
Look at the mysql web site. MS does not provide it.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Snake" wrote:
> Two of our servers have a "MYSql OleDB Provider" Datasource. I have no ide
a
> where they came from but I would like to add this Datasource to my own PC.
Is
> this something someone likely purchased? Does Microsoft provide it?
> Thanks
where they came from but I would like to add this Datasource to my own PC. I
s
this something someone likely purchased? Does Microsoft provide it?
ThanksHi
Look at the mysql web site. MS does not provide it.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Snake" wrote:
> Two of our servers have a "MYSql OleDB Provider" Datasource. I have no ide
a
> where they came from but I would like to add this Datasource to my own PC.
Is
> this something someone likely purchased? Does Microsoft provide it?
> Thanks
Connection from ASP page to SQL Server Express
Hi!
Try using "Provider", rather than "Driver".
I have two servers, the web (with IIS - win2003) and the test data
server (winXPpro with SQL Express)
I'm trying to connect to the db but with no success...
here is the connection string I'm using:
sConn = "Driver=SQLNCLI;
Server=marco-server\SQLEXPRESS;
Database=grimp;
Uid=grimpuser;
Pwd=somePassword;"
I get this:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified
I've tried also with Driver={SQL Native Client} but I get the same
error.
do I have to install something on the web server?(ma.giorgi@.gmail.com) writes:
Quote:
Originally Posted by
I have two servers, the web (with IIS - win2003) and the test data
server (winXPpro with SQL Express)
I'm trying to connect to the db but with no success...
here is the connection string I'm using:
sConn = "Driver=SQLNCLI;
Server=marco-server\SQLEXPRESS;
Database=grimp;
Uid=grimpuser;
Pwd=somePassword;"
>
I get this:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Driver Manager] Data source name not found and no
default driver specified
>
I've tried also with Driver={SQL Native Client} but I get the same
error.
Try using "Provider", rather than "Driver".
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
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.
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.
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.
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.
Saturday, February 25, 2012
connection error
Hello,
We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
All 3 servers are in same location.
SQL-1 and SQL-2 are in same domain, i.e. domain-a.
SQL-3 is another domain, i.e. domain-b.
SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
(We did not add SQL-1 and SQL-2 on 'Client Network Utility')
But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and port
1433.
Then we have the message 'SQL Server does not exist or access denied
connection open (Connect[])' during add SQL-3 from 'New SQL Server
Registration'.
SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
using RPC' is checked.
Thanks
Hi
This could be a firewall issue or you may be using dynamic ports (if this is
a named instance for example). Have you checked which port SQL3 is listening
on? Can you telnet on the given port to SQL3 from the other servers? Have you
tried using IP addresses instead of DNS Names?
You may want to check out SQLPing at
http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx
Also check the client protocols being used your service pack would indicate
TCP/IP should be first.
John
"Newbie" wrote:
> Hello,
> We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
> We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
> All 3 servers are in same location.
> SQL-1 and SQL-2 are in same domain, i.e. domain-a.
> SQL-3 is another domain, i.e. domain-b.
> SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
> (We did not add SQL-1 and SQL-2 on 'Client Network Utility')
> But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
> We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and port
> 1433.
> Then we have the message 'SQL Server does not exist or access denied
> connection open (Connect[])' during add SQL-3 from 'New SQL Server
> Registration'.
> SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
> using RPC' is checked.
> Thanks
We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
All 3 servers are in same location.
SQL-1 and SQL-2 are in same domain, i.e. domain-a.
SQL-3 is another domain, i.e. domain-b.
SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
(We did not add SQL-1 and SQL-2 on 'Client Network Utility')
But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and port
1433.
Then we have the message 'SQL Server does not exist or access denied
connection open (Connect[])' during add SQL-3 from 'New SQL Server
Registration'.
SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
using RPC' is checked.
Thanks
Hi
This could be a firewall issue or you may be using dynamic ports (if this is
a named instance for example). Have you checked which port SQL3 is listening
on? Can you telnet on the given port to SQL3 from the other servers? Have you
tried using IP addresses instead of DNS Names?
You may want to check out SQLPing at
http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx
Also check the client protocols being used your service pack would indicate
TCP/IP should be first.
John
"Newbie" wrote:
> Hello,
> We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
> We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
> All 3 servers are in same location.
> SQL-1 and SQL-2 are in same domain, i.e. domain-a.
> SQL-3 is another domain, i.e. domain-b.
> SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
> (We did not add SQL-1 and SQL-2 on 'Client Network Utility')
> But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
> We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and port
> 1433.
> Then we have the message 'SQL Server does not exist or access denied
> connection open (Connect[])' during add SQL-3 from 'New SQL Server
> Registration'.
> SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
> using RPC' is checked.
> Thanks
connection error
Hello,
We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
All 3 servers are in same location.
SQL-1 and SQL-2 are in same domain, i.e. domain-a.
SQL-3 is another domain, i.e. domain-b.
SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
(We did not add SQL-1 and SQL-2 on 'Client Network Utility')
But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and port
1433.
Then we have the message 'SQL Server does not exist or access denied
connection open (Connect[])' during add SQL-3 from 'New SQL Server
Registration'.
SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
using RPC' is checked.
ThanksHi
This could be a firewall issue or you may be using dynamic ports (if this is
a named instance for example). Have you checked which port SQL3 is listening
on? Can you telnet on the given port to SQL3 from the other servers? Have yo
u
tried using IP addresses instead of DNS Names?
You may want to check out SQLPing at
http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
Also check the client protocols being used your service pack would indicate
TCP/IP should be first.
John
"Newbie" wrote:
> Hello,
> We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
> We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
> All 3 servers are in same location.
> SQL-1 and SQL-2 are in same domain, i.e. domain-a.
> SQL-3 is another domain, i.e. domain-b.
> SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
> (We did not add SQL-1 and SQL-2 on 'Client Network Utility')
> But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
> We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and po
rt
> 1433.
> Then we have the message 'SQL Server does not exist or access denied
> connection open (Connect[])' during add SQL-3 from 'New SQL Server
> Registration'.
> SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
> using RPC' is checked.
> Thanks
We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
All 3 servers are in same location.
SQL-1 and SQL-2 are in same domain, i.e. domain-a.
SQL-3 is another domain, i.e. domain-b.
SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
(We did not add SQL-1 and SQL-2 on 'Client Network Utility')
But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and port
1433.
Then we have the message 'SQL Server does not exist or access denied
connection open (Connect[])' during add SQL-3 from 'New SQL Server
Registration'.
SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
using RPC' is checked.
ThanksHi
This could be a firewall issue or you may be using dynamic ports (if this is
a named instance for example). Have you checked which port SQL3 is listening
on? Can you telnet on the given port to SQL3 from the other servers? Have yo
u
tried using IP addresses instead of DNS Names?
You may want to check out SQLPing at
http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
Also check the client protocols being used your service pack would indicate
TCP/IP should be first.
John
"Newbie" wrote:
> Hello,
> We just add a new SQL2000 server (SQL-3, 192.168.100.3) w/SP4 installed.
> We have old SQL-1(192.168.100.1) and SQL-2(192.168.100.2) servers.
> All 3 servers are in same location.
> SQL-1 and SQL-2 are in same domain, i.e. domain-a.
> SQL-3 is another domain, i.e. domain-b.
> SQL-3 can add SQL-1 and SQL-2 from 'New SQL Server Registration'.
> (We did not add SQL-1 and SQL-2 on 'Client Network Utility')
> But SQL-1 or SQL-2 can not add SQL-3 from 'New SQL Server Registration'.
> We use 'Client Network Utility' add alias with TCP/IP 192.168.100.3 and po
rt
> 1433.
> Then we have the message 'SQL Server does not exist or access denied
> connection open (Connect[])' during add SQL-3 from 'New SQL Server
> Registration'.
> SQL-3's 'Allow other SQL Server to connect remotelly to this SQL Server
> using RPC' is checked.
> Thanks
Subscribe to:
Posts (Atom)