Hi
I am trying to merge a set of tables from 5 separate databases (4 on
separate servers and 2 on the same server) into one 'master' database.
The tables being replicated all have unique ID ranges
How to I organise the replication so that the subscriber database can allow
inserts which fit into the ID ranges for the related Publishers database.
ie All inserts with a Lab_ID = 'L' should ONLY be replicated back to the
associated publisher.
I am not familiar with the automatic identity range handling .. can anyone
point me to an article about how this works ?
any help would be appreciated
cheers
mike
Mike,
as you've got multiple publishers, just ordinary filters will work to
restrict the flow of data to each publisher. For identity range handling,
you'll need to design each publisher's range yourself. The subscriber table
can be created during the first initialization, and all others are nosync
ones. So, the subscriber's identity range is defined after the first
initialization, and subsequent publications need to be sure not to overlap
with this range. Make the ranges large, because assignment of another range
might cause an overlap, so if the range is so big there will never be any
need to reset then this is best.
Alternatively, all subscriptions can be nosync ones.
These might help:
http://www.replicationanswers.com/No...alizations.asp
http://www.replicationanswers.com/ManualIdentities.asp
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Showing posts with label via. Show all posts
Showing posts with label via. Show all posts
Thursday, March 29, 2012
Sunday, March 25, 2012
Connfig Replication via Internet
I want to replicate data via Internet using FTP Server, i have SQL 2K with SP3. i set up client network as
- Server alias: my local server's name
- Server Name: ip address on internet
- Network libraries: TCP/IP
- Port : 1433
But i connect using Enterprise Manage to SQL Server then it errors:
A Connection could not be established to Dis-server ( Dis-server is my servername)
Reason: SQL Server does not exist or accessed denied
ConnectionOpen(Connect())..
please help me..tks
Regards
NBtri
from the subscriber can you ping your publisher?
On your publisher and subscriber you have to configure the subsciber and
publisher using client network utility.
Make sure that the publsiher and subscriber are listed in the hosts file
(thanks Paul Ibison for this tidbit of tidbitosity)
Then on your Publisher go to Tools - replication - Configure Publishers,
subscribers, distributors, click on the subscribers tab, and click on the
check box to the right of your subscriber server name. Ensure you are using
a SQL Server account, and enter the subscriber sa (or an account in the
system administrator role) onthe subscriber and its password.
Then on your subscriber, set up a pull subscription.
"NBTri" <anonymous@.discussions.microsoft.com> wrote in message
news:8ABF42AE-6921-4A63-8479-CD7910909F89@.microsoft.com...
> I want to replicate data via Internet using FTP Server, i have SQL 2K with
SP3. i set up client network as
> - Server alias: my local server's name
> - Server Name: ip address on internet
> - Network libraries: TCP/IP
> - Port : 1433
> But i connect using Enterprise Manage to SQL Server then it errors:
> A Connection could not be established to Dis-server ( Dis-server is my
servername)
> Reason: SQL Server does not exist or accessed denied
> ConnectionOpen(Connect())..
>
> please help me..tks
> Regards
> NBtri
>
- Server alias: my local server's name
- Server Name: ip address on internet
- Network libraries: TCP/IP
- Port : 1433
But i connect using Enterprise Manage to SQL Server then it errors:
A Connection could not be established to Dis-server ( Dis-server is my servername)
Reason: SQL Server does not exist or accessed denied
ConnectionOpen(Connect())..
please help me..tks
Regards
NBtri
from the subscriber can you ping your publisher?
On your publisher and subscriber you have to configure the subsciber and
publisher using client network utility.
Make sure that the publsiher and subscriber are listed in the hosts file
(thanks Paul Ibison for this tidbit of tidbitosity)
Then on your Publisher go to Tools - replication - Configure Publishers,
subscribers, distributors, click on the subscribers tab, and click on the
check box to the right of your subscriber server name. Ensure you are using
a SQL Server account, and enter the subscriber sa (or an account in the
system administrator role) onthe subscriber and its password.
Then on your subscriber, set up a pull subscription.
"NBTri" <anonymous@.discussions.microsoft.com> wrote in message
news:8ABF42AE-6921-4A63-8479-CD7910909F89@.microsoft.com...
> I want to replicate data via Internet using FTP Server, i have SQL 2K with
SP3. i set up client network as
> - Server alias: my local server's name
> - Server Name: ip address on internet
> - Network libraries: TCP/IP
> - Port : 1433
> But i connect using Enterprise Manage to SQL Server then it errors:
> A Connection could not be established to Dis-server ( Dis-server is my
servername)
> Reason: SQL Server does not exist or accessed denied
> ConnectionOpen(Connect())..
>
> please help me..tks
> Regards
> NBtri
>
Connet to SQL using VB6 forms via Internet
We have one system that is developed using Visual Basic 6. The system connects to MS SQL database using ODBC configuration. We have another branch that has to access the same database. We've got an Internet connection with a speed of 2MB, as we tried to connect using Virtual Private Network (VPN), but the problem we faced that the system became very slow over the Internet, its taking half an hour to open one form. Is there any way to connect to the database and via the Internet using VB6 Forms? Or its not useful as its not a web based tool.
Hi,it′s hard for us to tell where the bottleneck in your application design is. But as of your description the application is not designed for slow connections to the database. To find out exactly what your problem is, you will either have to through the code to see which data is requested from the server, or let the profiler runn to see where the latency is based on.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
Connecto to remote SQL Server
Hi, community
I want to connect a program (like query analyzer) in home, to the sql server in office via internet, but i can't log in to the remote server. Someone know how to establish the connection?
Thanks to all of you!!!You will need to get permission from you network group to VPN into the network.|||thank you, but can you be a little more detailed?|||You need to talk to your network group and have them give you VPN access and tell you how to use it.|||I've tryed lot of things but cant connect!!!!, i try to establish a VPN in win 2k3 server as Server and winXP Prof as client, but it is impossible to get connected!!!
I finally get the VPN connection, i've missing directives, but now i cant connect to SQL Server!
I want to connect a program (like query analyzer) in home, to the sql server in office via internet, but i can't log in to the remote server. Someone know how to establish the connection?
Thanks to all of you!!!You will need to get permission from you network group to VPN into the network.|||thank you, but can you be a little more detailed?|||You need to talk to your network group and have them give you VPN access and tell you how to use it.|||I've tryed lot of things but cant connect!!!!, i try to establish a VPN in win 2k3 server as Server and winXP Prof as client, but it is impossible to get connected!!!
I finally get the VPN connection, i've missing directives, but now i cant connect to SQL Server!
Sunday, March 11, 2012
Connection to SQLserver
We have a server running SQL2000 which I am trying to get access to via the
internet. I have used the port forwarding setup on our router/firewall to
transfer all traffic on port 1433 to the server 192.168.0.99. I cannot get a
connection as it states the server was not found or it was denied access.
I have a similar method of access to a couple of Personal Addition setups
off site and I can get a connection.
What is slightly unusual is that I have two connections to the internet one
leased line where I can't get access to the firewall and a broadband where I
do. Both are running NAT. Is this an area to check
Thanks for a pointers you can give me
Ian
"Ian Rudge" <Ian.Rudge@.shaw.co.uk> wrote in message
news:Opx2sOvmEHA.556@.tk2msftngp13.phx.gbl...
> We have a server running SQL2000 which I am trying to get access to via
the
> internet. I have used the port forwarding setup on our router/firewall to
> transfer all traffic on port 1433 to the server 192.168.0.99. I cannot get
a
> connection as it states the server was not found or it was denied access.
> I have a similar method of access to a couple of Personal Addition setups
> off site and I can get a connection.
> What is slightly unusual is that I have two connections to the internet
one
> leased line where I can't get access to the firewall and a broadband where
I
> do. Both are running NAT. Is this an area to check
Maybe. There are a lot of variables in getting this to work properly. Check
this article along with links for troubleshooting this setup
http://support.microsoft.com/default...b;en-us;287932
BTW, I hope that was only a fictitious external IP address for your
server...
Steve
|||Thank you for pointers and I will start my search from that.
The IP address is fictional but as it is internal in the 192.168... range I
thought you couldn't get to it or should I panic?
Thx
Ian
"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:OGpa1X0mEHA.3876@.TK2MSFTNGP15.phx.gbl...
> "Ian Rudge" <Ian.Rudge@.shaw.co.uk> wrote in message
> news:Opx2sOvmEHA.556@.tk2msftngp13.phx.gbl...
> the
> a
> one
> I
> Maybe. There are a lot of variables in getting this to work properly.
> Check
> this article along with links for troubleshooting this setup
> http://support.microsoft.com/default...b;en-us;287932
> BTW, I hope that was only a fictitious external IP address for your
> server...
> Steve
>
|||You're right, I should have recognized that range ;) No need to panic, it
goes without saying that you need a good firewall and isolation from the
"outside".
Steve
"Ian Rudge" <Ian.Rudge@.shaw.co.uk> wrote in message
news:%23rcxs97mEHA.3628@.TK2MSFTNGP09.phx.gbl...
> Thank you for pointers and I will start my search from that.
> The IP address is fictional but as it is internal in the 192.168... range
I[vbcol=seagreen]
> thought you couldn't get to it or should I panic?
> Thx
> Ian
> "Steve Thompson" <stevethompson@.nomail.please> wrote in message
> news:OGpa1X0mEHA.3876@.TK2MSFTNGP15.phx.gbl...
to[vbcol=seagreen]
access.[vbcol=seagreen]
setups
>
|||I think I have found my answer. If I want to connect from outside, the
gateway for the SQLServer machine must point to the Broadband router not the
leased line one
Thx
for the help
"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:OEGQIECnEHA.1236@.TK2MSFTNGP09.phx.gbl...
> You're right, I should have recognized that range ;) No need to panic, it
> goes without saying that you need a good firewall and isolation from the
> "outside".
> Steve
> "Ian Rudge" <Ian.Rudge@.shaw.co.uk> wrote in message
> news:%23rcxs97mEHA.3628@.TK2MSFTNGP09.phx.gbl...
> I
> to
> access.
> setups
>
internet. I have used the port forwarding setup on our router/firewall to
transfer all traffic on port 1433 to the server 192.168.0.99. I cannot get a
connection as it states the server was not found or it was denied access.
I have a similar method of access to a couple of Personal Addition setups
off site and I can get a connection.
What is slightly unusual is that I have two connections to the internet one
leased line where I can't get access to the firewall and a broadband where I
do. Both are running NAT. Is this an area to check
Thanks for a pointers you can give me
Ian
"Ian Rudge" <Ian.Rudge@.shaw.co.uk> wrote in message
news:Opx2sOvmEHA.556@.tk2msftngp13.phx.gbl...
> We have a server running SQL2000 which I am trying to get access to via
the
> internet. I have used the port forwarding setup on our router/firewall to
> transfer all traffic on port 1433 to the server 192.168.0.99. I cannot get
a
> connection as it states the server was not found or it was denied access.
> I have a similar method of access to a couple of Personal Addition setups
> off site and I can get a connection.
> What is slightly unusual is that I have two connections to the internet
one
> leased line where I can't get access to the firewall and a broadband where
I
> do. Both are running NAT. Is this an area to check
Maybe. There are a lot of variables in getting this to work properly. Check
this article along with links for troubleshooting this setup
http://support.microsoft.com/default...b;en-us;287932
BTW, I hope that was only a fictitious external IP address for your
server...
Steve
|||Thank you for pointers and I will start my search from that.
The IP address is fictional but as it is internal in the 192.168... range I
thought you couldn't get to it or should I panic?
Thx
Ian
"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:OGpa1X0mEHA.3876@.TK2MSFTNGP15.phx.gbl...
> "Ian Rudge" <Ian.Rudge@.shaw.co.uk> wrote in message
> news:Opx2sOvmEHA.556@.tk2msftngp13.phx.gbl...
> the
> a
> one
> I
> Maybe. There are a lot of variables in getting this to work properly.
> Check
> this article along with links for troubleshooting this setup
> http://support.microsoft.com/default...b;en-us;287932
> BTW, I hope that was only a fictitious external IP address for your
> server...
> Steve
>
|||You're right, I should have recognized that range ;) No need to panic, it
goes without saying that you need a good firewall and isolation from the
"outside".
Steve
"Ian Rudge" <Ian.Rudge@.shaw.co.uk> wrote in message
news:%23rcxs97mEHA.3628@.TK2MSFTNGP09.phx.gbl...
> Thank you for pointers and I will start my search from that.
> The IP address is fictional but as it is internal in the 192.168... range
I[vbcol=seagreen]
> thought you couldn't get to it or should I panic?
> Thx
> Ian
> "Steve Thompson" <stevethompson@.nomail.please> wrote in message
> news:OGpa1X0mEHA.3876@.TK2MSFTNGP15.phx.gbl...
to[vbcol=seagreen]
access.[vbcol=seagreen]
setups
>
|||I think I have found my answer. If I want to connect from outside, the
gateway for the SQLServer machine must point to the Broadband router not the
leased line one
Thx
for the help
"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:OEGQIECnEHA.1236@.TK2MSFTNGP09.phx.gbl...
> You're right, I should have recognized that range ;) No need to panic, it
> goes without saying that you need a good firewall and isolation from the
> "outside".
> Steve
> "Ian Rudge" <Ian.Rudge@.shaw.co.uk> wrote in message
> news:%23rcxs97mEHA.3628@.TK2MSFTNGP09.phx.gbl...
> I
> to
> access.
> setups
>
Connection to SQL Server 2005 lost
We have developed a VB6 client program accsessing SQL Sever 7.0 via ADO
(Provider=sqloledb) and MDAC 2.8. This program has worked flawlessly for
years, but after upgrading to SQL Server 2005, the database connection is
sometimes lost during larger operation involving open/close of several
recordsets. The general error message says:
“[DBNETLIB][ConnectionOpen,Connect()).]SQL Server does not exsist or access
denied". "Simpler" parts of the program involving just a recordset or two
always work fine. Any idea of what is going on here?
Have you tried using the SQL Native Client (SNAC) instead to see if that
makes a difference?
http://msdn2.microsoft.com/en-us/data/aa937733.aspx
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Handeland" <Glenn Handeland@.discussions.microsoft.com> wrote in
message news:9A2E8820-DEFC-4209-B019-8A0996CF7FDF@.microsoft.com...
> We have developed a VB6 client program accsessing SQL Sever 7.0 via ADO
> (Provider=sqloledb) and MDAC 2.8. This program has worked flawlessly for
> years, but after upgrading to SQL Server 2005, the database connection is
> sometimes lost during larger operation involving open/close of several
> recordsets. The general error message says:
> “[DBNETLIB][ConnectionOpen,Connect()).]SQL Server does not exsist or
> access
> denied". "Simpler" parts of the program involving just a recordset or two
> always work fine. Any idea of what is going on here?
|||Thank you for the suggestion.
We have not tried the native client, because the FAQ says:
Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
server?
A. Applications deployed before SQL Server 2005 was released can and should
continue to use MDAC.
Most likely it is a server configuration problem. Our program is used by
many clients, accessing the datebase from different computers/configurations,
and all of them experience this error message when conneting to a given SQL
Server 2005 Server. Some of our clients from other firms also have their own
SQL Server 2005 running, and they have successfully managed to connect to
their database using MDAC and never experience this error message.
"Andrew J. Kelly" wrote:
> Have you tried using the SQL Native Client (SNAC) instead to see if that
> makes a difference?
> http://msdn2.microsoft.com/en-us/data/aa937733.aspx
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Glenn Handeland" <Glenn Handeland@.discussions.microsoft.com> wrote in
> message news:9A2E8820-DEFC-4209-B019-8A0996CF7FDF@.microsoft.com...
>
|||Sorry I don't have another answer for you. I have not heard of or seen this
particular issue before.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@.microsoft.com...[vbcol=seagreen]
> Thank you for the suggestion.
> We have not tried the native client, because the FAQ says:
> Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
> server?
> A. Applications deployed before SQL Server 2005 was released can and
> should
> continue to use MDAC.
> Most likely it is a server configuration problem. Our program is used by
> many clients, accessing the datebase from different
> computers/configurations,
> and all of them experience this error message when conneting to a given
> SQL
> Server 2005 Server. Some of our clients from other firms also have their
> own
> SQL Server 2005 running, and they have successfully managed to connect to
> their database using MDAC and never experience this error message.
>
> "Andrew J. Kelly" wrote:
|||Ah, I would STILL upgrade to SNAC. I agree that if the application is
working and deployed it should not be disturbed, but yours is not working
and SNAC solves any number of issues like this.
__________________________________________________ ________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
__________________________________________________ __________________________________________
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@.microsoft.com...[vbcol=seagreen]
> Thank you for the suggestion.
> We have not tried the native client, because the FAQ says:
> Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
> server?
> A. Applications deployed before SQL Server 2005 was released can and
> should
> continue to use MDAC.
> Most likely it is a server configuration problem. Our program is used by
> many clients, accessing the datebase from different
> computers/configurations,
> and all of them experience this error message when conneting to a given
> SQL
> Server 2005 Server. Some of our clients from other firms also have their
> own
> SQL Server 2005 running, and they have successfully managed to connect to
> their database using MDAC and never experience this error message.
>
> "Andrew J. Kelly" wrote:
|||We upgraded to SNAC, but still experience the very same error. The text of
the error message reported is a little bit different, thought. It now says
"Named Pipes Provider: No process is on the other end of the pipe." We did
get rid of the error message when we changed the recordsets cursor from
server-side to client-side (CursorLocation = adUseClient).
"William Vaughn" wrote:
> Ah, I would STILL upgrade to SNAC. I agree that if the application is
> working and deployed it should not be disturbed, but yours is not working
> and SNAC solves any number of issues like this.
> --
> __________________________________________________ ________________________
> William R. Vaughn
> President and Founder Beta V Corporation
> Author, Mentor, Dad, Grandpa
> Microsoft MVP
> (425) 556-9205 (Pacific time)
> Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
> __________________________________________________ __________________________________________
> "Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
> message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@.microsoft.com...
>
|||You are putting less work on the SQL Server by doing that and is generally a
good idea anyway. But you should also think about changing to TCP instead of
using named pipes.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:530FDB75-0B6B-46E3-A9CA-FFD3E2B3F75F@.microsoft.com...[vbcol=seagreen]
> We upgraded to SNAC, but still experience the very same error. The text of
> the error message reported is a little bit different, thought. It now says
> "Named Pipes Provider: No process is on the other end of the pipe." We did
> get rid of the error message when we changed the recordsets cursor from
> server-side to client-side (CursorLocation = adUseClient).
>
> "William Vaughn" wrote:
|||It sounds like the server is rejecting the Open. Make sure that the server
configuration is not limiting the total number of connections in any way.
These might have been configured to comply with license or other artifical
constraints.
__________________________________________________ ________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
__________________________________________________ __________________________________________
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:530FDB75-0B6B-46E3-A9CA-FFD3E2B3F75F@.microsoft.com...[vbcol=seagreen]
> We upgraded to SNAC, but still experience the very same error. The text of
> the error message reported is a little bit different, thought. It now says
> "Named Pipes Provider: No process is on the other end of the pipe." We did
> get rid of the error message when we changed the recordsets cursor from
> server-side to client-side (CursorLocation = adUseClient).
>
> "William Vaughn" wrote:
(Provider=sqloledb) and MDAC 2.8. This program has worked flawlessly for
years, but after upgrading to SQL Server 2005, the database connection is
sometimes lost during larger operation involving open/close of several
recordsets. The general error message says:
“[DBNETLIB][ConnectionOpen,Connect()).]SQL Server does not exsist or access
denied". "Simpler" parts of the program involving just a recordset or two
always work fine. Any idea of what is going on here?
Have you tried using the SQL Native Client (SNAC) instead to see if that
makes a difference?
http://msdn2.microsoft.com/en-us/data/aa937733.aspx
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Handeland" <Glenn Handeland@.discussions.microsoft.com> wrote in
message news:9A2E8820-DEFC-4209-B019-8A0996CF7FDF@.microsoft.com...
> We have developed a VB6 client program accsessing SQL Sever 7.0 via ADO
> (Provider=sqloledb) and MDAC 2.8. This program has worked flawlessly for
> years, but after upgrading to SQL Server 2005, the database connection is
> sometimes lost during larger operation involving open/close of several
> recordsets. The general error message says:
> “[DBNETLIB][ConnectionOpen,Connect()).]SQL Server does not exsist or
> access
> denied". "Simpler" parts of the program involving just a recordset or two
> always work fine. Any idea of what is going on here?
|||Thank you for the suggestion.
We have not tried the native client, because the FAQ says:
Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
server?
A. Applications deployed before SQL Server 2005 was released can and should
continue to use MDAC.
Most likely it is a server configuration problem. Our program is used by
many clients, accessing the datebase from different computers/configurations,
and all of them experience this error message when conneting to a given SQL
Server 2005 Server. Some of our clients from other firms also have their own
SQL Server 2005 running, and they have successfully managed to connect to
their database using MDAC and never experience this error message.
"Andrew J. Kelly" wrote:
> Have you tried using the SQL Native Client (SNAC) instead to see if that
> makes a difference?
> http://msdn2.microsoft.com/en-us/data/aa937733.aspx
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Glenn Handeland" <Glenn Handeland@.discussions.microsoft.com> wrote in
> message news:9A2E8820-DEFC-4209-B019-8A0996CF7FDF@.microsoft.com...
>
|||Sorry I don't have another answer for you. I have not heard of or seen this
particular issue before.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@.microsoft.com...[vbcol=seagreen]
> Thank you for the suggestion.
> We have not tried the native client, because the FAQ says:
> Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
> server?
> A. Applications deployed before SQL Server 2005 was released can and
> should
> continue to use MDAC.
> Most likely it is a server configuration problem. Our program is used by
> many clients, accessing the datebase from different
> computers/configurations,
> and all of them experience this error message when conneting to a given
> SQL
> Server 2005 Server. Some of our clients from other firms also have their
> own
> SQL Server 2005 running, and they have successfully managed to connect to
> their database using MDAC and never experience this error message.
>
> "Andrew J. Kelly" wrote:
|||Ah, I would STILL upgrade to SNAC. I agree that if the application is
working and deployed it should not be disturbed, but yours is not working
and SNAC solves any number of issues like this.
__________________________________________________ ________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
__________________________________________________ __________________________________________
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@.microsoft.com...[vbcol=seagreen]
> Thank you for the suggestion.
> We have not tried the native client, because the FAQ says:
> Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
> server?
> A. Applications deployed before SQL Server 2005 was released can and
> should
> continue to use MDAC.
> Most likely it is a server configuration problem. Our program is used by
> many clients, accessing the datebase from different
> computers/configurations,
> and all of them experience this error message when conneting to a given
> SQL
> Server 2005 Server. Some of our clients from other firms also have their
> own
> SQL Server 2005 running, and they have successfully managed to connect to
> their database using MDAC and never experience this error message.
>
> "Andrew J. Kelly" wrote:
|||We upgraded to SNAC, but still experience the very same error. The text of
the error message reported is a little bit different, thought. It now says
"Named Pipes Provider: No process is on the other end of the pipe." We did
get rid of the error message when we changed the recordsets cursor from
server-side to client-side (CursorLocation = adUseClient).
"William Vaughn" wrote:
> Ah, I would STILL upgrade to SNAC. I agree that if the application is
> working and deployed it should not be disturbed, but yours is not working
> and SNAC solves any number of issues like this.
> --
> __________________________________________________ ________________________
> William R. Vaughn
> President and Founder Beta V Corporation
> Author, Mentor, Dad, Grandpa
> Microsoft MVP
> (425) 556-9205 (Pacific time)
> Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
> __________________________________________________ __________________________________________
> "Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
> message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@.microsoft.com...
>
|||You are putting less work on the SQL Server by doing that and is generally a
good idea anyway. But you should also think about changing to TCP instead of
using named pipes.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:530FDB75-0B6B-46E3-A9CA-FFD3E2B3F75F@.microsoft.com...[vbcol=seagreen]
> We upgraded to SNAC, but still experience the very same error. The text of
> the error message reported is a little bit different, thought. It now says
> "Named Pipes Provider: No process is on the other end of the pipe." We did
> get rid of the error message when we changed the recordsets cursor from
> server-side to client-side (CursorLocation = adUseClient).
>
> "William Vaughn" wrote:
|||It sounds like the server is rejecting the Open. Make sure that the server
configuration is not limiting the total number of connections in any way.
These might have been configured to comply with license or other artifical
constraints.
__________________________________________________ ________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
__________________________________________________ __________________________________________
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:530FDB75-0B6B-46E3-A9CA-FFD3E2B3F75F@.microsoft.com...[vbcol=seagreen]
> We upgraded to SNAC, but still experience the very same error. The text of
> the error message reported is a little bit different, thought. It now says
> "Named Pipes Provider: No process is on the other end of the pipe." We did
> get rid of the error message when we changed the recordsets cursor from
> server-side to client-side (CursorLocation = adUseClient).
>
> "William Vaughn" wrote:
Connection to SQL Server 2005 lost
We have developed a VB6 client program accsessing SQL Sever 7.0 via ADO
(Provider=sqloledb) and MDAC 2.8. This program has worked flawlessly for
years, but after upgrading to SQL Server 2005, the database connection is
sometimes lost during larger operation involving open/close of several
recordsets. The general error message says:
“[DBNETLIB][ConnectionOpen,Connect()).]SQL Server does not exsist
or access
denied". "Simpler" parts of the program involving just a recordset or two
always work fine. Any idea of what is going on here?Have you tried using the SQL Native Client (SNAC) instead to see if that
makes a difference?
http://msdn2.microsoft.com/en-us/data/aa937733.aspx
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Handeland" <Glenn Handeland@.discussions.microsoft.com> wrote in
message news:9A2E8820-DEFC-4209-B019-8A0996CF7FDF@.microsoft.com...
> We have developed a VB6 client program accsessing SQL Sever 7.0 via ADO
> (Provider=sqloledb) and MDAC 2.8. This program has worked flawlessly for
> years, but after upgrading to SQL Server 2005, the database connection is
> sometimes lost during larger operation involving open/close of several
> recordsets. The general error message says:
> “[DBNETLIB][ConnectionOpen,Connect()).]SQL Server does not exsis
t or
> access
> denied". "Simpler" parts of the program involving just a recordset or two
> always work fine. Any idea of what is going on here?|||Thank you for the suggestion.
We have not tried the native client, because the FAQ says:
Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
server?
A. Applications deployed before SQL Server 2005 was released can and should
continue to use MDAC.
Most likely it is a server configuration problem. Our program is used by
many clients, accessing the datebase from different computers/configurations
,
and all of them experience this error message when conneting to a given SQL
Server 2005 Server. Some of our clients from other firms also have their own
SQL Server 2005 running, and they have successfully managed to connect to
their database using MDAC and never experience this error message.
"Andrew J. Kelly" wrote:
> Have you tried using the SQL Native Client (SNAC) instead to see if that
> makes a difference?
> http://msdn2.microsoft.com/en-us/data/aa937733.aspx
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Glenn Handeland" <Glenn Handeland@.discussions.microsoft.com> wrote in
> message news:9A2E8820-DEFC-4209-B019-8A0996CF7FDF@.microsoft.com...
>|||Sorry I don't have another answer for you. I have not heard of or seen this
particular issue before.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@.microsoft.com...[vbcol=seagreen]
> Thank you for the suggestion.
> We have not tried the native client, because the FAQ says:
> Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
> server?
> A. Applications deployed before SQL Server 2005 was released can and
> should
> continue to use MDAC.
> Most likely it is a server configuration problem. Our program is used by
> many clients, accessing the datebase from different
> computers/configurations,
> and all of them experience this error message when conneting to a given
> SQL
> Server 2005 Server. Some of our clients from other firms also have their
> own
> SQL Server 2005 running, and they have successfully managed to connect to
> their database using MDAC and never experience this error message.
>
> "Andrew J. Kelly" wrote:
>|||Ah, I would STILL upgrade to SNAC. I agree that if the application is
working and deployed it should not be disturbed, but yours is not working
and SNAC solves any number of issues like this.
________________________________________
__________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
________________________________________
____________________________________
________________
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@.microsoft.com...[vbcol=seagreen]
> Thank you for the suggestion.
> We have not tried the native client, because the FAQ says:
> Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
> server?
> A. Applications deployed before SQL Server 2005 was released can and
> should
> continue to use MDAC.
> Most likely it is a server configuration problem. Our program is used by
> many clients, accessing the datebase from different
> computers/configurations,
> and all of them experience this error message when conneting to a given
> SQL
> Server 2005 Server. Some of our clients from other firms also have their
> own
> SQL Server 2005 running, and they have successfully managed to connect to
> their database using MDAC and never experience this error message.
>
> "Andrew J. Kelly" wrote:
>
(Provider=sqloledb) and MDAC 2.8. This program has worked flawlessly for
years, but after upgrading to SQL Server 2005, the database connection is
sometimes lost during larger operation involving open/close of several
recordsets. The general error message says:
“[DBNETLIB][ConnectionOpen,Connect()).]SQL Server does not exsist
or access
denied". "Simpler" parts of the program involving just a recordset or two
always work fine. Any idea of what is going on here?Have you tried using the SQL Native Client (SNAC) instead to see if that
makes a difference?
http://msdn2.microsoft.com/en-us/data/aa937733.aspx
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Handeland" <Glenn Handeland@.discussions.microsoft.com> wrote in
message news:9A2E8820-DEFC-4209-B019-8A0996CF7FDF@.microsoft.com...
> We have developed a VB6 client program accsessing SQL Sever 7.0 via ADO
> (Provider=sqloledb) and MDAC 2.8. This program has worked flawlessly for
> years, but after upgrading to SQL Server 2005, the database connection is
> sometimes lost during larger operation involving open/close of several
> recordsets. The general error message says:
> “[DBNETLIB][ConnectionOpen,Connect()).]SQL Server does not exsis
t or
> access
> denied". "Simpler" parts of the program involving just a recordset or two
> always work fine. Any idea of what is going on here?|||Thank you for the suggestion.
We have not tried the native client, because the FAQ says:
Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
server?
A. Applications deployed before SQL Server 2005 was released can and should
continue to use MDAC.
Most likely it is a server configuration problem. Our program is used by
many clients, accessing the datebase from different computers/configurations
,
and all of them experience this error message when conneting to a given SQL
Server 2005 Server. Some of our clients from other firms also have their own
SQL Server 2005 running, and they have successfully managed to connect to
their database using MDAC and never experience this error message.
"Andrew J. Kelly" wrote:
> Have you tried using the SQL Native Client (SNAC) instead to see if that
> makes a difference?
> http://msdn2.microsoft.com/en-us/data/aa937733.aspx
>
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Glenn Handeland" <Glenn Handeland@.discussions.microsoft.com> wrote in
> message news:9A2E8820-DEFC-4209-B019-8A0996CF7FDF@.microsoft.com...
>|||Sorry I don't have another answer for you. I have not heard of or seen this
particular issue before.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@.microsoft.com...[vbcol=seagreen]
> Thank you for the suggestion.
> We have not tried the native client, because the FAQ says:
> Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
> server?
> A. Applications deployed before SQL Server 2005 was released can and
> should
> continue to use MDAC.
> Most likely it is a server configuration problem. Our program is used by
> many clients, accessing the datebase from different
> computers/configurations,
> and all of them experience this error message when conneting to a given
> SQL
> Server 2005 Server. Some of our clients from other firms also have their
> own
> SQL Server 2005 running, and they have successfully managed to connect to
> their database using MDAC and never experience this error message.
>
> "Andrew J. Kelly" wrote:
>|||Ah, I would STILL upgrade to SNAC. I agree that if the application is
working and deployed it should not be disturbed, but yours is not working
and SNAC solves any number of issues like this.
________________________________________
__________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
________________________________________
____________________________________
________________
"Glenn Handeland" <GlennHandeland@.discussions.microsoft.com> wrote in
message news:C425386F-DA1A-4D79-AEFB-AE29F7AC6606@.microsoft.com...[vbcol=seagreen]
> Thank you for the suggestion.
> We have not tried the native client, because the FAQ says:
> Q. Must I upgrade clients to use SQL Native Client as soon as I upgrade my
> server?
> A. Applications deployed before SQL Server 2005 was released can and
> should
> continue to use MDAC.
> Most likely it is a server configuration problem. Our program is used by
> many clients, accessing the datebase from different
> computers/configurations,
> and all of them experience this error message when conneting to a given
> SQL
> Server 2005 Server. Some of our clients from other firms also have their
> own
> SQL Server 2005 running, and they have successfully managed to connect to
> their database using MDAC and never experience this error message.
>
> "Andrew J. Kelly" wrote:
>
Thursday, March 8, 2012
Connection To Remote Server
I have recently installed SQL Server 2005 onto my development machine and
another developers machine. I am trying to connect to his server via my SQL
Server Management Studio but I am getting the following error.
==================================================
"A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. When connecting to SQL Server
2005, this failure may be caused by the fact that under the default settings
SQL Server does not allow remote connections. (provider: Named Pipes
Provider, error: 0 - No process is on the other end of the pipe.) (.Net
SqlClient Data Provider)"
==================================================
His server is set to allow remote connections. How do I resolve this?
Hello Terry,
I would like to know if you try to add an alias to the remote server, will
it resolve this issue?
1. Open the SQL Server Configuration Manager.
2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
3. In the Alias - New dialogbox, please type the Alias Name, the Server
name and the TCP/IP port.
4. Click OK and try to connect to the remote server.
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community 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.
|||Im not sure if I followed instructions correctly but I am still getting the
same problem.
This is what I did:
I did the following on my dev machine - im not sure what port to use so i
tried a range from 100 - 9999
> 1. Open the SQL Server Configuration Manager.
> 2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
> 3. In the Alias - New dialogbox, please type the Alias Name, the Server
> name and the TCP/IP port.
> 4. Click OK and try to connect to the remote server.
>
|||Hello Terry,
First, I would like to suggest you follow the KB article to check the
connection issue:
827422How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;827422
Although this article is for the SQL 2000, you could follow the general
troubleshoot steps to narrow down the issue.
Then, please make sure you have typed the correct instance name when you
use my previous approach.
The TCP/IP port is 1433 for the default configuration.
Sincerely,
Wei Lu
Microsoft Online Community 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.
|||Thank you for your attempts to solve this problem. It is still not resolved
so I am calling microsoft as i need a quick solution.
|||I have solved the problem with the help of microsoft telephone support and I
am posting the solution fyi
=======================================
Enabled “Local and remote connections – Using TCP and Named pipes” in
SQL server surface area configuration tool and the issue is resolved.
another developers machine. I am trying to connect to his server via my SQL
Server Management Studio but I am getting the following error.
==================================================
"A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. When connecting to SQL Server
2005, this failure may be caused by the fact that under the default settings
SQL Server does not allow remote connections. (provider: Named Pipes
Provider, error: 0 - No process is on the other end of the pipe.) (.Net
SqlClient Data Provider)"
==================================================
His server is set to allow remote connections. How do I resolve this?
Hello Terry,
I would like to know if you try to add an alias to the remote server, will
it resolve this issue?
1. Open the SQL Server Configuration Manager.
2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
3. In the Alias - New dialogbox, please type the Alias Name, the Server
name and the TCP/IP port.
4. Click OK and try to connect to the remote server.
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community 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.
|||Im not sure if I followed instructions correctly but I am still getting the
same problem.
This is what I did:
I did the following on my dev machine - im not sure what port to use so i
tried a range from 100 - 9999
> 1. Open the SQL Server Configuration Manager.
> 2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
> 3. In the Alias - New dialogbox, please type the Alias Name, the Server
> name and the TCP/IP port.
> 4. Click OK and try to connect to the remote server.
>
|||Hello Terry,
First, I would like to suggest you follow the KB article to check the
connection issue:
827422How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;827422
Although this article is for the SQL 2000, you could follow the general
troubleshoot steps to narrow down the issue.
Then, please make sure you have typed the correct instance name when you
use my previous approach.
The TCP/IP port is 1433 for the default configuration.
Sincerely,
Wei Lu
Microsoft Online Community 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.
|||Thank you for your attempts to solve this problem. It is still not resolved
so I am calling microsoft as i need a quick solution.
|||I have solved the problem with the help of microsoft telephone support and I
am posting the solution fyi
=======================================
Enabled “Local and remote connections – Using TCP and Named pipes” in
SQL server surface area configuration tool and the issue is resolved.
Connection To Remote Server
I have recently installed SQL Server 2005 onto my development machine and
another developers machine. I am trying to connect to his server via my SQL
Server Management Studio but I am getting the following error.
========================================
==========
"A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. When connecting to SQL Serve
r
2005, this failure may be caused by the fact that under the default settings
SQL Server does not allow remote connections. (provider: Named Pipes
Provider, error: 0 - No process is on the other end of the pipe.) (.Net
SqlClient Data Provider)"
========================================
==========
His server is set to allow remote connections. How do I resolve this?Hello Terry,
I would like to know if you try to add an alias to the remote server, will
it resolve this issue?
1. Open the SQL Server Configuration Manager.
2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
3. In the Alias - New dialogbox, please type the Alias Name, the Server
name and the TCP/IP port.
4. Click OK and try to connect to the remote server.
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==========
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community 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.|||Im not sure if I followed instructions correctly but I am still getting the
same problem.
This is what I did:
I did the following on my dev machine - im not sure what port to use so i
tried a range from 100 - 9999
> 1. Open the SQL Server Configuration Manager.
> 2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
> 3. In the Alias - New dialogbox, please type the Alias Name, the Server
> name and the TCP/IP port.
> 4. Click OK and try to connect to the remote server.
>|||Hello Terry,
First, I would like to suggest you follow the KB article to check the
connection issue:
827422 How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/defaul...kb;EN-US;827422
Although this article is for the SQL 2000, you could follow the general
troubleshoot steps to narrow down the issue.
Then, please make sure you have typed the correct instance name when you
use my previous approach.
The TCP/IP port is 1433 for the default configuration.
Sincerely,
Wei Lu
Microsoft Online Community 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.|||Thank you for your attempts to solve this problem. It is still not resolved
so I am calling microsoft as i need a quick solution.|||I have solved the problem with the help of microsoft telephone support and I
am posting the solution fyi
=======================================
Enabled “Local and remote connections – Using TCP and Named pipes” in
SQL server surface area configuration tool and the issue is resolved.
another developers machine. I am trying to connect to his server via my SQL
Server Management Studio but I am getting the following error.
========================================
==========
"A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. When connecting to SQL Serve
r
2005, this failure may be caused by the fact that under the default settings
SQL Server does not allow remote connections. (provider: Named Pipes
Provider, error: 0 - No process is on the other end of the pipe.) (.Net
SqlClient Data Provider)"
========================================
==========
His server is set to allow remote connections. How do I resolve this?Hello Terry,
I would like to know if you try to add an alias to the remote server, will
it resolve this issue?
1. Open the SQL Server Configuration Manager.
2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
3. In the Alias - New dialogbox, please type the Alias Name, the Server
name and the TCP/IP port.
4. Click OK and try to connect to the remote server.
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==========
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community 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.|||Im not sure if I followed instructions correctly but I am still getting the
same problem.
This is what I did:
I did the following on my dev machine - im not sure what port to use so i
tried a range from 100 - 9999
> 1. Open the SQL Server Configuration Manager.
> 2. Click the SQL Native Client Configuration and right click the Aliases
node. Then Click New Alias...
> 3. In the Alias - New dialogbox, please type the Alias Name, the Server
> name and the TCP/IP port.
> 4. Click OK and try to connect to the remote server.
>|||Hello Terry,
First, I would like to suggest you follow the KB article to check the
connection issue:
827422 How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/defaul...kb;EN-US;827422
Although this article is for the SQL 2000, you could follow the general
troubleshoot steps to narrow down the issue.
Then, please make sure you have typed the correct instance name when you
use my previous approach.
The TCP/IP port is 1433 for the default configuration.
Sincerely,
Wei Lu
Microsoft Online Community 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.|||Thank you for your attempts to solve this problem. It is still not resolved
so I am calling microsoft as i need a quick solution.|||I have solved the problem with the help of microsoft telephone support and I
am posting the solution fyi
=======================================
Enabled “Local and remote connections – Using TCP and Named pipes” in
SQL server surface area configuration tool and the issue is resolved.
Connection to Red Brick
Hi all,
Is it possible to connect to an IBM Redbrick Database via Data Sources in AS 2005? I can't get to ODBC's and don't see an OLE driver.
Thanks in advance,
Mark
You must have a driver AND a cartridge that will work with Redbrick. The driver is pretty straightforward. The cartridge is an XSLT file that translates an internally generated XML-based query into a valid SQL statement for submission to the source system. On my system, the cartidges are available at:
C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\Cartridges
If a cartridge is not available for your specific system (which is the case for Redbrick), SSAS attempts to use the sql2000.xsl cartridge. This might work for you, but I'm not certain.
Another optoin for you is to create a set of views in SQL Server that use the OPENROWSET function to establish the connection to Redbrick for you. You might be able to then expose those views to SSAS and since SSAS has cartridges for SQL Server this might work out.
Good luck,
Bryan
|||Thanks for the suggestions/guidance Bryan.
I appreciate the help.
Wednesday, March 7, 2012
Connection Timeout
I am trying to upload data to my sql database via a web service installed on
the same machine as sql server. When my upload takes more than about 2
minutes I get a timeout error message from my web service and the data
tranfer was not completed. Transfers taking less time complete
satisfactorily. My web.config file for the web service has httpRuntime
executionTimeout set to 360 and maxRequestLength set to 30720. I continue to
get timeout error messages from my web service. I need my connection to stay
open for upto 5 minutes for those situations when I have large files to move
or my client computer has a slow internet upload capability. Am I forgetting
some setting that still needs to be made?
Thanks,
Fred Herring
there is a proxytimeout setting somewhere increase it like this
proxy.Timeout=2000;
see here
http://www.dotnetbips.com/displayarticle.aspx?id=112
we had the same problem and this fixed it
"Fred Herring" <FredHerring@.discussions.microsoft.com> wrote in message
news:B5CBD211-81B5-4693-A2A3-32FBA66780AF@.microsoft.com...
>I am trying to upload data to my sql database via a web service installed
>on
> the same machine as sql server. When my upload takes more than about 2
> minutes I get a timeout error message from my web service and the data
> tranfer was not completed. Transfers taking less time complete
> satisfactorily. My web.config file for the web service has httpRuntime
> executionTimeout set to 360 and maxRequestLength set to 30720. I continue
> to
> get timeout error messages from my web service. I need my connection to
> stay
> open for upto 5 minutes for those situations when I have large files to
> move
> or my client computer has a slow internet upload capability. Am I
> forgetting
> some setting that still needs to be made?
> Thanks,
> Fred Herring
>
>
the same machine as sql server. When my upload takes more than about 2
minutes I get a timeout error message from my web service and the data
tranfer was not completed. Transfers taking less time complete
satisfactorily. My web.config file for the web service has httpRuntime
executionTimeout set to 360 and maxRequestLength set to 30720. I continue to
get timeout error messages from my web service. I need my connection to stay
open for upto 5 minutes for those situations when I have large files to move
or my client computer has a slow internet upload capability. Am I forgetting
some setting that still needs to be made?
Thanks,
Fred Herring
there is a proxytimeout setting somewhere increase it like this
proxy.Timeout=2000;
see here
http://www.dotnetbips.com/displayarticle.aspx?id=112
we had the same problem and this fixed it
"Fred Herring" <FredHerring@.discussions.microsoft.com> wrote in message
news:B5CBD211-81B5-4693-A2A3-32FBA66780AF@.microsoft.com...
>I am trying to upload data to my sql database via a web service installed
>on
> the same machine as sql server. When my upload takes more than about 2
> minutes I get a timeout error message from my web service and the data
> tranfer was not completed. Transfers taking less time complete
> satisfactorily. My web.config file for the web service has httpRuntime
> executionTimeout set to 360 and maxRequestLength set to 30720. I continue
> to
> get timeout error messages from my web service. I need my connection to
> stay
> open for upto 5 minutes for those situations when I have large files to
> move
> or my client computer has a slow internet upload capability. Am I
> forgetting
> some setting that still needs to be made?
> Thanks,
> Fred Herring
>
>
Saturday, February 25, 2012
Connection Timeout
I am trying to upload data to my sql database via a web service installed on
the same machine as sql server. When my upload takes more than about 2
minutes I get a timeout error message from my web service and the data
tranfer was not completed. Transfers taking less time complete
satisfactorily. My web.config file for the web service has httpRuntime
executionTimeout set to 360 and maxRequestLength set to 30720. I continue t
o
get timeout error messages from my web service. I need my connection to sta
y
open for upto 5 minutes for those situations when I have large files to move
or my client computer has a slow internet upload capability. Am I forgettin
g
some setting that still needs to be made?
Thanks,
Fred Herringthere is a proxytimeout setting somewhere increase it like this
proxy.Timeout=2000;
see here
http://www.dotnetbips.com/displayarticle.aspx?id=112
we had the same problem and this fixed it
"Fred Herring" <FredHerring@.discussions.microsoft.com> wrote in message
news:B5CBD211-81B5-4693-A2A3-32FBA66780AF@.microsoft.com...
>I am trying to upload data to my sql database via a web service installed
>on
> the same machine as sql server. When my upload takes more than about 2
> minutes I get a timeout error message from my web service and the data
> tranfer was not completed. Transfers taking less time complete
> satisfactorily. My web.config file for the web service has httpRuntime
> executionTimeout set to 360 and maxRequestLength set to 30720. I continue
> to
> get timeout error messages from my web service. I need my connection to
> stay
> open for upto 5 minutes for those situations when I have large files to
> move
> or my client computer has a slow internet upload capability. Am I
> forgetting
> some setting that still needs to be made?
> Thanks,
> Fred Herring
>
>
the same machine as sql server. When my upload takes more than about 2
minutes I get a timeout error message from my web service and the data
tranfer was not completed. Transfers taking less time complete
satisfactorily. My web.config file for the web service has httpRuntime
executionTimeout set to 360 and maxRequestLength set to 30720. I continue t
o
get timeout error messages from my web service. I need my connection to sta
y
open for upto 5 minutes for those situations when I have large files to move
or my client computer has a slow internet upload capability. Am I forgettin
g
some setting that still needs to be made?
Thanks,
Fred Herringthere is a proxytimeout setting somewhere increase it like this
proxy.Timeout=2000;
see here
http://www.dotnetbips.com/displayarticle.aspx?id=112
we had the same problem and this fixed it
"Fred Herring" <FredHerring@.discussions.microsoft.com> wrote in message
news:B5CBD211-81B5-4693-A2A3-32FBA66780AF@.microsoft.com...
>I am trying to upload data to my sql database via a web service installed
>on
> the same machine as sql server. When my upload takes more than about 2
> minutes I get a timeout error message from my web service and the data
> tranfer was not completed. Transfers taking less time complete
> satisfactorily. My web.config file for the web service has httpRuntime
> executionTimeout set to 360 and maxRequestLength set to 30720. I continue
> to
> get timeout error messages from my web service. I need my connection to
> stay
> open for upto 5 minutes for those situations when I have large files to
> move
> or my client computer has a slow internet upload capability. Am I
> forgetting
> some setting that still needs to be made?
> Thanks,
> Fred Herring
>
>
Subscribe to:
Posts (Atom)