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
>

Connectivty problem from NON domain users

I have a problem esteblishing a connection to a SQL server with a SQL user,
while I am logged to the computer with a local computer.
Any domain account can has no problem.
What can ause this?
Thanks in advance,
Ido Friedman
What tool are you connecting from?
How are you trying to connect?
Do you know for sure that you are trying to connect via SQL Authentication?
Have you tried hitting the Data Sources (ODBC) applet within the Control
Panel and creating a test connection?
Keith Kratochvil
"Ido friedman" <Idofriedman@.discussions.microsoft.com> wrote in message
news:934F22F5-2624-49B2-AC35-1970C1AE876D@.microsoft.com...
>I have a problem esteblishing a connection to a SQL server with a SQL user,
> while I am logged to the computer with a local computer.
> Any domain account can has no problem.
> What can ause this?
> Thanks in advance,
> Ido Friedman
|||Do you have mixed mode authentication enabled?
To enable...
SQL 2005
In SQL Server Management Studio Object Explorer, right-click your server,
and then click Properties.
On the Security page, under Server authentication, select the new server
authentication mode, and then click OK.
In the SQL Server Management Studio dialog box, click OK, to acknowledge the
need to restart SQL Server.
SQL 2000
Expand a server group.
Right-click a server, and then click Properties.
Click the Security tab.
Under Authentication, click SQL Server and Windows.
Under Audit level, select the level at which user accesses to Microsoft SQL
ServerT are recorded in the SQL Server error log:
None causes no auditing to be performed.
Success causes only successful login attempts to be audited.
Failure causes only failed login attempts to be audited.
All causes successful and failed login attempts to be audited.
Hope that helps...
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Ido friedman" <Idofriedman@.discussions.microsoft.com> wrote in message
news:934F22F5-2624-49B2-AC35-1970C1AE876D@.microsoft.com...
>I have a problem esteblishing a connection to a SQL server with a SQL user,
> while I am logged to the computer with a local computer.
> Any domain account can has no problem.
> What can ause this?
> Thanks in advance,
> Ido Friedman
|||Thanks for your reply,
I am using the following ASP page:
The page is running in IIS under the local user IUser_computername.
When I run the same code with a domain account it successeds.
Thanks in advance,
Ido Friedman
<%
Dim dataSource
On Error Resume Next
Set cnn = Server.CreateObject("ADODB.Connection")
cnn.open "PROVIDER=SQLOLEDB;DATA
SOURCE=servername";UID=user;PWD=user;DATABASE=nort hwind"
If err.number = 0 Then
Response.Write(cnn.State)
cnn.Close
Else
Response.Write( err.Description )
End If
Response.End
%>
"Warren Brunk" wrote:

> Do you have mixed mode authentication enabled?
> To enable...
> SQL 2005
> In SQL Server Management Studio Object Explorer, right-click your server,
> and then click Properties.
> On the Security page, under Server authentication, select the new server
> authentication mode, and then click OK.
> In the SQL Server Management Studio dialog box, click OK, to acknowledge the
> need to restart SQL Server.
>
> SQL 2000
> Expand a server group.
>
> Right-click a server, and then click Properties.
>
> Click the Security tab.
>
> Under Authentication, click SQL Server and Windows.
>
> Under Audit level, select the level at which user accesses to Microsoft? SQL
> ServerT are recorded in the SQL Server error log:
> None causes no auditing to be performed.
>
> Success causes only successful login attempts to be audited.
>
> Failure causes only failed login attempts to be audited.
>
> All causes successful and failed login attempts to be audited.
>
> Hope that helps...
>
> --
> /*
> Warren Brunk - MCITP - SQL 2005, MCDBA
> www.techintsolutions.com
> */
>
> "Ido friedman" <Idofriedman@.discussions.microsoft.com> wrote in message
> news:934F22F5-2624-49B2-AC35-1970C1AE876D@.microsoft.com...
>
>

ConnectionOpen (PreLoginHandshake()). General Network Error

Hi all,
I'm getting the following error on my SQL on a local machine when running a
client program that connects to sql server located at the same machine. What
does it means? Do i have to configure in SQL settings?
[DBNETLIB]ConnectionOpen (PreLoginHandshake()). General Network Error.
thanks,
joelNormally this message would indicate a timeout of some kind attempting to
connect. Open the SQL Client Network Utility and see if Shared Memory is
enabled. If it is not enable it and see if the problem goes away. Local
connections by default should use shared memory so it would appear that
this is not enabled.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Connectiong problem Sqlserver 2005 Express

I'm working with an Sqlserver 2005 Express database on my local machine, and using vs.net 2005.I need to enable the sqlserver cache by the way:

aspnet_regsql -E -d Northwind -ed

I encountered the remote connection problem(error:40).The northwind database was restored to the sqlserver 2005 express by the db file downloaded,and I added the ASPNET user.I also enabled the TCP/IP by using SQL Server Configuration Manager.

But all the web application connected to the Northwind database is working through the connection string:

"Data Source=WKS-DEV-04\SQLEXPRESS;Initial Catalog=Northwind;Integrated Security=True"

Any help will be much appreciated, thank you very much for reading my post

Can you telnet to the remote SQL Express service from the client? Using such command from commandline:

telnet xxx.xx.xx.xxx yyyy

Where Xs stand for ip address of the remote server, and Ys stand for TCP port of the service. You can check the TCP port of the SQL service in 'SQL Server Configuration Manager'->SQL Server 2005 Network Configuration

|||Thank you for your reply very much.I have got it done.

Connection: "(local)" vs "ComputerName"

Hi,
I was reading in a book about SQL 2005 about how connections are made to SQL
2005. Assume I have a SQL Server instance named SQL1 and I have a client app
installed on SQL1. The book claimed that if the app's connection string
sets the datasource to "(local)" then the connection uses Shared Memory, and
if it set the datasource to the computer's name, "SQL1", that it uses the
TCP/IP stack which is slower than Shared Memory.
Reading BOL for SQL 2000, it seems to indicate that a local client will
always use Shared Memory, regardless of how the datasource is specified.
Can someone provide a definitive clarification and indicate whether it is
different for SQL 2000 and SQL 2005?
Thank you,
Daniel Jameson
SQL Server DBA
Children's Oncology Group
www.childrensoncologygroup.org
Hi Daniel,
I am afraid that the book description is not correct. By default any
connection with the following names from local computer will use Shared
Memory protocol:
1. "<computer_name>"
2. "<computer_name>\<instance_name>" for a named instance
3. "(local)"
4. "(local)\<instance_name>" for a named instance
5. "Localhost"
6. "localhost\<instance_name>" for a named instance
7. A single period "."
8. ".\<instance_name>" for a named instance
A local connection may use another protocol under the following
circumstances:
1. Connect to a client alias that specifies a protocol.
2. Prefix the computer name with the protocol (for example,
"np:<computer_name>" or "tcp:<computer_name>").
3. Connect to the IP address which results in a TCP/IP connection.
4. Connect to the fully qualified domain name (FQDN) which results in a
TCP/IP connection (for example, "<computer_name>.<domain_name>.com"
You can run the following statement to check the current protocol for the
local connections:
SELECT net_transport
FROM sys.dm_exec_connections
WHERE session_id = @.@.SPID;
For more information, you may refer to:
Default Client Connection Behavior
http://msdn2.microsoft.com/en-us/library/ms190204.aspx
One interesting thing is that for the forms of <computer_name> and
<computer_name>\<instance_name>, they do not always use Shared Memory
protocol. They just by default use Shared Memory protocol.
Actually in registry there is a value that records which protocol is used
in the latest connection. For the next time local connection, it will use
the latest protocol.
For example:
--This results in Shared Memory connection
sqlcmd /SCharlesXP /E
--This results in Named Pipes connection
sqlcmd /Snp:CharlesXP /E
--This keeps using Named Pipes connection
sqlcmd /SCharlesXP /E
--This results in Shared Memory connection
sqlcmd /Slpc:CharlesXP /E
--This keeps using Shared Memory connection
sqlcmd /SCharlesXP /E
Hope this helps. If you have any other questions or concerns, please feel
free to let me know.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
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.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Charles;
Have you tried it on SQL2005 SP2 running on XP? I tried on two such
instances. Even with Named Pipes disabled, the following query:
SELECT net_transport
FROM sys.dm_exec_connections
WHERE session_id = @.@.SPID;
still returns Named Pipes for many of the server name settings in your first
group, which is supposed to use Shared Memory.
On W2K3 servers, I didn't see this behavior.
Linchi
"Charles Wang[MSFT]" wrote:

> Hi Daniel,
> I am afraid that the book description is not correct. By default any
> connection with the following names from local computer will use Shared
> Memory protocol:
> 1. "<computer_name>"
> 2. "<computer_name>\<instance_name>" for a named instance
> 3. "(local)"
> 4. "(local)\<instance_name>" for a named instance
> 5. "Localhost"
> 6. "localhost\<instance_name>" for a named instance
> 7. A single period "."
> 8. ".\<instance_name>" for a named instance
> A local connection may use another protocol under the following
> circumstances:
> 1. Connect to a client alias that specifies a protocol.
> 2. Prefix the computer name with the protocol (for example,
> "np:<computer_name>" or "tcp:<computer_name>").
> 3. Connect to the IP address which results in a TCP/IP connection.
> 4. Connect to the fully qualified domain name (FQDN) which results in a
> TCP/IP connection (for example, "<computer_name>.<domain_name>.com"
> You can run the following statement to check the current protocol for the
> local connections:
> SELECT net_transport
> FROM sys.dm_exec_connections
> WHERE session_id = @.@.SPID;
> For more information, you may refer to:
> Default Client Connection Behavior
> http://msdn2.microsoft.com/en-us/library/ms190204.aspx
> One interesting thing is that for the forms of <computer_name> and
> <computer_name>\<instance_name>, they do not always use Shared Memory
> protocol. They just by default use Shared Memory protocol.
> Actually in registry there is a value that records which protocol is used
> in the latest connection. For the next time local connection, it will use
> the latest protocol.
> For example:
> --This results in Shared Memory connection
> sqlcmd /SCharlesXP /E
> --This results in Named Pipes connection
> sqlcmd /Snp:CharlesXP /E
> --This keeps using Named Pipes connection
> sqlcmd /SCharlesXP /E
> --This results in Shared Memory connection
> sqlcmd /Slpc:CharlesXP /E
> --This keeps using Shared Memory connection
> sqlcmd /SCharlesXP /E
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ===
> Get notification to my posts through email? Please refer to:
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> If you are using Outlook Express, please make sure you clear the check box
> "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
>
> 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.
> ================================================== ====
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
|||Hi Linchi,
Did you restart your SQL Server service after you disable Named Pipes
protocol on your server by using SQL Server Configuration Manager? or did
you just disable the Named Pipes in SQL Native Client Configuration on your
computer? Per my test, it is no use of disabling Named Pipes on client;
but Shared Memory will be used if you disable the Named Pipes protocol on
server.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
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.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Charles,
Thank you very much for the detailed response.
Thank you,
Daniel Jameson
SQL Server DBA
Children's Oncology Group
www.childrensoncologygroup.org
"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:kdagNzOnHHA.5168@.TK2MSFTNGHUB02.phx.gbl...
> Hi Daniel,
> I am afraid that the book description is not correct. By default any
> connection with the following names from local computer will use Shared
> Memory protocol:
> 1. "<computer_name>"
> 2. "<computer_name>\<instance_name>" for a named instance
> 3. "(local)"
> 4. "(local)\<instance_name>" for a named instance
> 5. "Localhost"
> 6. "localhost\<instance_name>" for a named instance
> 7. A single period "."
> 8. ".\<instance_name>" for a named instance
> A local connection may use another protocol under the following
> circumstances:
> 1. Connect to a client alias that specifies a protocol.
> 2. Prefix the computer name with the protocol (for example,
> "np:<computer_name>" or "tcp:<computer_name>").
> 3. Connect to the IP address which results in a TCP/IP connection.
> 4. Connect to the fully qualified domain name (FQDN) which results in a
> TCP/IP connection (for example, "<computer_name>.<domain_name>.com"
> You can run the following statement to check the current protocol for the
> local connections:
> SELECT net_transport
> FROM sys.dm_exec_connections
> WHERE session_id = @.@.SPID;
> For more information, you may refer to:
> Default Client Connection Behavior
> http://msdn2.microsoft.com/en-us/library/ms190204.aspx
> One interesting thing is that for the forms of <computer_name> and
> <computer_name>\<instance_name>, they do not always use Shared Memory
> protocol. They just by default use Shared Memory protocol.
> Actually in registry there is a value that records which protocol is used
> in the latest connection. For the next time local connection, it will use
> the latest protocol.
> For example:
> --This results in Shared Memory connection
> sqlcmd /SCharlesXP /E
> --This results in Named Pipes connection
> sqlcmd /Snp:CharlesXP /E
> --This keeps using Named Pipes connection
> sqlcmd /SCharlesXP /E
> --This results in Shared Memory connection
> sqlcmd /Slpc:CharlesXP /E
> --This keeps using Shared Memory connection
> sqlcmd /SCharlesXP /E
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ===
> Get notification to my posts through email? Please refer to:
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> If you are using Outlook Express, please make sure you clear the check box
> "Tools/Options/Read: Get 300 headers at a time" to see your reply
> promptly.
>
> 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.
> ================================================== ====
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> ================================================== ====
>
>
|||Positive, I did restart the SQL Server service. In fact, I just tried a few
more times to make sure I wasn't hallucinating.
Linchi
"Charles Wang[MSFT]" wrote:

> Hi Linchi,
> Did you restart your SQL Server service after you disable Named Pipes
> protocol on your server by using SQL Server Configuration Manager? or did
> you just disable the Named Pipes in SQL Native Client Configuration on your
> computer? Per my test, it is no use of disabling Named Pipes on client;
> but Shared Memory will be used if you disable the Named Pipes protocol on
> server.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ===
> Get notification to my posts through email? Please refer to:
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> If you are using Outlook Express, please make sure you clear the check box
> "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
>
> 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.
> ================================================== ====
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
>
>
>
|||Hi Linchi,
It is strange. I have checked that on my computer and I could not reproduce
your issue. My OS is also Windows XP. I also checked that on a Windows 2K
x64 computer. It seemed that the Named Pipes was not disabled on your SQL
Server. Could you please check your SQL Server error logs to see if the
Named Pipes protocol was not disabled during the service startup? or you
may check if you can reproduce your issue on another computer.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====

Connection: "(local)" vs "ComputerName"

Hi,
I was reading in a book about SQL 2005 about how connections are made to SQL
2005. Assume I have a SQL Server instance named SQL1 and I have a client app
installed on SQL1. The book claimed that if the app's connection string
sets the datasource to "(local)" then the connection uses Shared Memory, and
if it set the datasource to the computer's name, "SQL1", that it uses the
TCP/IP stack which is slower than Shared Memory.
Reading BOL for SQL 2000, it seems to indicate that a local client will
always use Shared Memory, regardless of how the datasource is specified.
Can someone provide a definitive clarification and indicate whether it is
different for SQL 2000 and SQL 2005?
Thank you,
Daniel Jameson
SQL Server DBA
Children's Oncology Group
www.childrensoncologygroup.orgHi Daniel,
I am afraid that the book description is not correct. By default any
connection with the following names from local computer will use Shared
Memory protocol:
1. "<computer_name>"
2. "<computer_name>\<instance_name>" for a named instance
3. "(local)"
4. "(local)\<instance_name>" for a named instance
5. "Localhost"
6. "localhost\<instance_name>" for a named instance
7. A single period "."
8. ".\<instance_name>" for a named instance
A local connection may use another protocol under the following
circumstances:
1. Connect to a client alias that specifies a protocol.
2. Prefix the computer name with the protocol (for example,
"np:<computer_name>" or "tcp:<computer_name>").
3. Connect to the IP address which results in a TCP/IP connection.
4. Connect to the fully qualified domain name (FQDN) which results in a
TCP/IP connection (for example, "<computer_name>.<domain_name>.com"
You can run the following statement to check the current protocol for the
local connections:
SELECT net_transport
FROM sys.dm_exec_connections
WHERE session_id = @.@.SPID;
For more information, you may refer to:
Default Client Connection Behavior
http://msdn2.microsoft.com/en-us/library/ms190204.aspx
One interesting thing is that for the forms of <computer_name> and
<computer_name>\<instance_name>, they do not always use Shared Memory
protocol. They just by default use Shared Memory protocol.
Actually in registry there is a value that records which protocol is used
in the latest connection. For the next time local connection, it will use
the latest protocol.
For example:
--This results in Shared Memory connection
sqlcmd /SCharlesXP /E
--This results in Named Pipes connection
sqlcmd /Snp:CharlesXP /E
--This keeps using Named Pipes connection
sqlcmd /SCharlesXP /E
--This results in Shared Memory connection
sqlcmd /Slpc:CharlesXP /E
--This keeps using Shared Memory connection
sqlcmd /SCharlesXP /E
Hope this helps. If you have any other questions or concerns, please feel
free to let me know.
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
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.
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Charles;
Have you tried it on SQL2005 SP2 running on XP? I tried on two such
instances. Even with Named Pipes disabled, the following query:
SELECT net_transport
FROM sys.dm_exec_connections
WHERE session_id = @.@.SPID;
still returns Named Pipes for many of the server name settings in your first
group, which is supposed to use Shared Memory.
On W2K3 servers, I didn't see this behavior.
Linchi
"Charles Wang[MSFT]" wrote:

> Hi Daniel,
> I am afraid that the book description is not correct. By default any
> connection with the following names from local computer will use Shared
> Memory protocol:
> 1. "<computer_name>"
> 2. "<computer_name>\<instance_name>" for a named instance
> 3. "(local)"
> 4. "(local)\<instance_name>" for a named instance
> 5. "Localhost"
> 6. "localhost\<instance_name>" for a named instance
> 7. A single period "."
> 8. ".\<instance_name>" for a named instance
> A local connection may use another protocol under the following
> circumstances:
> 1. Connect to a client alias that specifies a protocol.
> 2. Prefix the computer name with the protocol (for example,
> "np:<computer_name>" or "tcp:<computer_name>").
> 3. Connect to the IP address which results in a TCP/IP connection.
> 4. Connect to the fully qualified domain name (FQDN) which results in a
> TCP/IP connection (for example, "<computer_name>.<domain_name>.com"
> You can run the following statement to check the current protocol for the
> local connections:
> SELECT net_transport
> FROM sys.dm_exec_connections
> WHERE session_id = @.@.SPID;
> For more information, you may refer to:
> Default Client Connection Behavior
> http://msdn2.microsoft.com/en-us/library/ms190204.aspx
> One interesting thing is that for the forms of <computer_name> and
> <computer_name>\<instance_name>, they do not always use Shared Memory
> protocol. They just by default use Shared Memory protocol.
> Actually in registry there is a value that records which protocol is used
> in the latest connection. For the next time local connection, it will use
> the latest protocol.
> For example:
> --This results in Shared Memory connection
> sqlcmd /SCharlesXP /E
> --This results in Named Pipes connection
> sqlcmd /Snp:CharlesXP /E
> --This keeps using Named Pipes connection
> sqlcmd /SCharlesXP /E
> --This results in Shared Memory connection
> sqlcmd /Slpc:CharlesXP /E
> --This keeps using Shared Memory connection
> sqlcmd /SCharlesXP /E
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ========================================
=============
> Get notification to my posts through email? Please refer to:
> [url]http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif[/ur
l]
> ications
> If you are using Outlook Express, please make sure you clear the check box
> "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly
.
>
> 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.
> ========================================
==============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>|||Hi Linchi,
Did you restart your SQL Server service after you disable Named Pipes
protocol on your server by using SQL Server Configuration Manager? or did
you just disable the Named Pipes in SQL Native Client Configuration on your
computer? Per my test, it is no use of disabling Named Pipes on client;
but Shared Memory will be used if you disable the Named Pipes protocol on
server.
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
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.
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Charles,
Thank you very much for the detailed response.
Thank you,
Daniel Jameson
SQL Server DBA
Children's Oncology Group
www.childrensoncologygroup.org
"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:kdagNzOnHHA.5168@.TK2MSFTNGHUB02.phx.gbl...
> Hi Daniel,
> I am afraid that the book description is not correct. By default any
> connection with the following names from local computer will use Shared
> Memory protocol:
> 1. "<computer_name>"
> 2. "<computer_name>\<instance_name>" for a named instance
> 3. "(local)"
> 4. "(local)\<instance_name>" for a named instance
> 5. "Localhost"
> 6. "localhost\<instance_name>" for a named instance
> 7. A single period "."
> 8. ".\<instance_name>" for a named instance
> A local connection may use another protocol under the following
> circumstances:
> 1. Connect to a client alias that specifies a protocol.
> 2. Prefix the computer name with the protocol (for example,
> "np:<computer_name>" or "tcp:<computer_name>").
> 3. Connect to the IP address which results in a TCP/IP connection.
> 4. Connect to the fully qualified domain name (FQDN) which results in a
> TCP/IP connection (for example, "<computer_name>.<domain_name>.com"
> You can run the following statement to check the current protocol for the
> local connections:
> SELECT net_transport
> FROM sys.dm_exec_connections
> WHERE session_id = @.@.SPID;
> For more information, you may refer to:
> Default Client Connection Behavior
> http://msdn2.microsoft.com/en-us/library/ms190204.aspx
> One interesting thing is that for the forms of <computer_name> and
> <computer_name>\<instance_name>, they do not always use Shared Memory
> protocol. They just by default use Shared Memory protocol.
> Actually in registry there is a value that records which protocol is used
> in the latest connection. For the next time local connection, it will use
> the latest protocol.
> For example:
> --This results in Shared Memory connection
> sqlcmd /SCharlesXP /E
> --This results in Named Pipes connection
> sqlcmd /Snp:CharlesXP /E
> --This keeps using Named Pipes connection
> sqlcmd /SCharlesXP /E
> --This results in Shared Memory connection
> sqlcmd /Slpc:CharlesXP /E
> --This keeps using Shared Memory connection
> sqlcmd /SCharlesXP /E
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ========================================
=============
> Get notification to my posts through email? Please refer to:
> [url]http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif[/ur
l]
> ications
> If you are using Outlook Express, please make sure you clear the check box
> "Tools/Options/Read: Get 300 headers at a time" to see your reply
> promptly.
>
> 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.
> ========================================
==============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> ========================================
==============
>
>|||Positive, I did restart the SQL Server service. In fact, I just tried a few
more times to make sure I wasn't hallucinating.
Linchi
"Charles Wang[MSFT]" wrote:

> Hi Linchi,
> Did you restart your SQL Server service after you disable Named Pipes
> protocol on your server by using SQL Server Configuration Manager? or did
> you just disable the Named Pipes in SQL Native Client Configuration on you
r
> computer? Per my test, it is no use of disabling Named Pipes on client;
> but Shared Memory will be used if you disable the Named Pipes protocol on
> server.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ========================================
=============
> Get notification to my posts through email? Please refer to:
> [url]http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif[/ur
l]
> ications
> If you are using Outlook Express, please make sure you clear the check box
> "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly
.
>
> 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.
> ========================================
==============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>
>
>
>|||Hi Linchi,
It is strange. I have checked that on my computer and I could not reproduce
your issue. My OS is also Windows XP. I also checked that on a Windows 2K
x64 computer. It seemed that the Named Pipes was not disabled on your SQL
Server. Could you please check your SQL Server error logs to see if the
Named Pipes protocol was not disabled during the service startup? or you
may check if you can reproduce your issue on another computer.
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============

Connection: "(local)" vs "ComputerName"

Hi,
I was reading in a book about SQL 2005 about how connections are made to SQL
2005. Assume I have a SQL Server instance named SQL1 and I have a client app
installed on SQL1. The book claimed that if the app's connection string
sets the datasource to "(local)" then the connection uses Shared Memory, and
if it set the datasource to the computer's name, "SQL1", that it uses the
TCP/IP stack which is slower than Shared Memory.
Reading BOL for SQL 2000, it seems to indicate that a local client will
always use Shared Memory, regardless of how the datasource is specified.
Can someone provide a definitive clarification and indicate whether it is
different for SQL 2000 and SQL 2005?
--
Thank you,
Daniel Jameson
SQL Server DBA
Children's Oncology Group
www.childrensoncologygroup.orgHi Daniel,
I am afraid that the book description is not correct. By default any
connection with the following names from local computer will use Shared
Memory protocol:
1. "<computer_name>"
2. "<computer_name>\<instance_name>" for a named instance
3. "(local)"
4. "(local)\<instance_name>" for a named instance
5. "Localhost"
6. "localhost\<instance_name>" for a named instance
7. A single period "."
8. ".\<instance_name>" for a named instance
A local connection may use another protocol under the following
circumstances:
1. Connect to a client alias that specifies a protocol.
2. Prefix the computer name with the protocol (for example,
"np:<computer_name>" or "tcp:<computer_name>").
3. Connect to the IP address which results in a TCP/IP connection.
4. Connect to the fully qualified domain name (FQDN) which results in a
TCP/IP connection (for example, "<computer_name>.<domain_name>.com"
You can run the following statement to check the current protocol for the
local connections:
SELECT net_transport
FROM sys.dm_exec_connections
WHERE session_id = @.@.SPID;
For more information, you may refer to:
Default Client Connection Behavior
http://msdn2.microsoft.com/en-us/library/ms190204.aspx
One interesting thing is that for the forms of <computer_name> and
<computer_name>\<instance_name>, they do not always use Shared Memory
protocol. They just by default use Shared Memory protocol.
Actually in registry there is a value that records which protocol is used
in the latest connection. For the next time local connection, it will use
the latest protocol.
For example:
--This results in Shared Memory connection
sqlcmd /SCharlesXP /E
--This results in Named Pipes connection
sqlcmd /Snp:CharlesXP /E
--This keeps using Named Pipes connection
sqlcmd /SCharlesXP /E
--This results in Shared Memory connection
sqlcmd /Slpc:CharlesXP /E
--This keeps using Shared Memory connection
sqlcmd /SCharlesXP /E
Hope this helps. If you have any other questions or concerns, please feel
free to let me know.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
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.
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Charles;
Have you tried it on SQL2005 SP2 running on XP? I tried on two such
instances. Even with Named Pipes disabled, the following query:
SELECT net_transport
FROM sys.dm_exec_connections
WHERE session_id = @.@.SPID;
still returns Named Pipes for many of the server name settings in your first
group, which is supposed to use Shared Memory.
On W2K3 servers, I didn't see this behavior.
Linchi
"Charles Wang[MSFT]" wrote:
> Hi Daniel,
> I am afraid that the book description is not correct. By default any
> connection with the following names from local computer will use Shared
> Memory protocol:
> 1. "<computer_name>"
> 2. "<computer_name>\<instance_name>" for a named instance
> 3. "(local)"
> 4. "(local)\<instance_name>" for a named instance
> 5. "Localhost"
> 6. "localhost\<instance_name>" for a named instance
> 7. A single period "."
> 8. ".\<instance_name>" for a named instance
> A local connection may use another protocol under the following
> circumstances:
> 1. Connect to a client alias that specifies a protocol.
> 2. Prefix the computer name with the protocol (for example,
> "np:<computer_name>" or "tcp:<computer_name>").
> 3. Connect to the IP address which results in a TCP/IP connection.
> 4. Connect to the fully qualified domain name (FQDN) which results in a
> TCP/IP connection (for example, "<computer_name>.<domain_name>.com"
> You can run the following statement to check the current protocol for the
> local connections:
> SELECT net_transport
> FROM sys.dm_exec_connections
> WHERE session_id = @.@.SPID;
> For more information, you may refer to:
> Default Client Connection Behavior
> http://msdn2.microsoft.com/en-us/library/ms190204.aspx
> One interesting thing is that for the forms of <computer_name> and
> <computer_name>\<instance_name>, they do not always use Shared Memory
> protocol. They just by default use Shared Memory protocol.
> Actually in registry there is a value that records which protocol is used
> in the latest connection. For the next time local connection, it will use
> the latest protocol.
> For example:
> --This results in Shared Memory connection
> sqlcmd /SCharlesXP /E
> --This results in Named Pipes connection
> sqlcmd /Snp:CharlesXP /E
> --This keeps using Named Pipes connection
> sqlcmd /SCharlesXP /E
> --This results in Shared Memory connection
> sqlcmd /Slpc:CharlesXP /E
> --This keeps using Shared Memory connection
> sqlcmd /SCharlesXP /E
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> Get notification to my posts through email? Please refer to:
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> If you are using Outlook Express, please make sure you clear the check box
> "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
>
> 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.
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>|||Hi Linchi,
Did you restart your SQL Server service after you disable Named Pipes
protocol on your server by using SQL Server Configuration Manager? or did
you just disable the Named Pipes in SQL Native Client Configuration on your
computer? Per my test, it is no use of disabling Named Pipes on client;
but Shared Memory will be used if you disable the Named Pipes protocol on
server.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
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.
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||Charles,
Thank you very much for the detailed response.
--
Thank you,
Daniel Jameson
SQL Server DBA
Children's Oncology Group
www.childrensoncologygroup.org
"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:kdagNzOnHHA.5168@.TK2MSFTNGHUB02.phx.gbl...
> Hi Daniel,
> I am afraid that the book description is not correct. By default any
> connection with the following names from local computer will use Shared
> Memory protocol:
> 1. "<computer_name>"
> 2. "<computer_name>\<instance_name>" for a named instance
> 3. "(local)"
> 4. "(local)\<instance_name>" for a named instance
> 5. "Localhost"
> 6. "localhost\<instance_name>" for a named instance
> 7. A single period "."
> 8. ".\<instance_name>" for a named instance
> A local connection may use another protocol under the following
> circumstances:
> 1. Connect to a client alias that specifies a protocol.
> 2. Prefix the computer name with the protocol (for example,
> "np:<computer_name>" or "tcp:<computer_name>").
> 3. Connect to the IP address which results in a TCP/IP connection.
> 4. Connect to the fully qualified domain name (FQDN) which results in a
> TCP/IP connection (for example, "<computer_name>.<domain_name>.com"
> You can run the following statement to check the current protocol for the
> local connections:
> SELECT net_transport
> FROM sys.dm_exec_connections
> WHERE session_id = @.@.SPID;
> For more information, you may refer to:
> Default Client Connection Behavior
> http://msdn2.microsoft.com/en-us/library/ms190204.aspx
> One interesting thing is that for the forms of <computer_name> and
> <computer_name>\<instance_name>, they do not always use Shared Memory
> protocol. They just by default use Shared Memory protocol.
> Actually in registry there is a value that records which protocol is used
> in the latest connection. For the next time local connection, it will use
> the latest protocol.
> For example:
> --This results in Shared Memory connection
> sqlcmd /SCharlesXP /E
> --This results in Named Pipes connection
> sqlcmd /Snp:CharlesXP /E
> --This keeps using Named Pipes connection
> sqlcmd /SCharlesXP /E
> --This results in Shared Memory connection
> sqlcmd /Slpc:CharlesXP /E
> --This keeps using Shared Memory connection
> sqlcmd /SCharlesXP /E
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> Get notification to my posts through email? Please refer to:
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> If you are using Outlook Express, please make sure you clear the check box
> "Tools/Options/Read: Get 300 headers at a time" to see your reply
> promptly.
>
> 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.
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> ======================================================>
>|||Positive, I did restart the SQL Server service. In fact, I just tried a few
more times to make sure I wasn't hallucinating.
Linchi
"Charles Wang[MSFT]" wrote:
> Hi Linchi,
> Did you restart your SQL Server service after you disable Named Pipes
> protocol on your server by using SQL Server Configuration Manager? or did
> you just disable the Named Pipes in SQL Native Client Configuration on your
> computer? Per my test, it is no use of disabling Named Pipes on client;
> but Shared Memory will be used if you disable the Named Pipes protocol on
> server.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================> Get notification to my posts through email? Please refer to:
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> If you are using Outlook Express, please make sure you clear the check box
> "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
>
> 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.
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>
>
>
>|||Hi Linchi,
It is strange. I have checked that on my computer and I could not reproduce
your issue. My OS is also Windows XP. I also checked that on a Windows 2K
x64 computer. It seemed that the Named Pipes was not disabled on your SQL
Server. Could you please check your SQL Server error logs to see if the
Named Pipes protocol was not disabled during the service startup? or you
may check if you can reproduce your issue on another computer.
Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

Connection To SQL Server 2005 / 2000

Hi everybody,
I got a bit of a problem with my connection. I wrote a programm in VB.Net wich connects to a sql-server 2005. On my local Computer everything works great, but on another Computer in the Network, I just receving timeouts. I allready check, if the sever allows remote connection.
My connectionstring for the SQL connection looks like this:

"Initial Catalog=Bauvorhaben;Data Source=P4-2400\SQLEXPRESS;Password=?;Persist Security Info=True;User ID=Lars"

I allready tried to get an connection to SQL-Server 2000. But the same here.

Does somebody have a clue, why I can't connect?

Thanks,
Lars

By default SQLExpress do not allow remote conneciton.

You need to

1. Turn on remote connection using SQL Server configuration Manager.

2. Start sqlbrowser service that is collocated with the SQLExpress server. SQL Browser service is needed if the sqlserver is a name instance, such as sqlexpress.

3. Make sure you make exception for sqlservr.exe in the firewall configuration of windows.

http://blogs.msdn.com/sql_protocols/archive/2005/11/14/492616.aspx

Connection to Server Failed - Analysis Services

Hi,
For some unknown reason, we are getting the following "Connection to Server
Failed" error message when we attempt to register our local server using MS
Analysis Services:
"Errors occurred while connecting to '<localservername>'. Cannot open
connection to Analysis server '<localservername>'. Cannot connect to the
server '<localservername>'. The server is either not started or too busy. Do
you still want to register the server?
Please note that we are running the Developer versions of MS SQL Server 2000
and MS Analysis Services with SP3 installed for both components on Windows X
P
Professional.
Also note that we ARE ABLE TO REGISTER A REMOTE SERVER successfully using
Analysis Manager, but we aren't able to either register or connect to a loca
l
server because we get the message above.
We are uttterly confused by this error message and would GREATLY APPRECIATE
any help in resolving this confusing issue as soon as possible.
Thanks,
Raj C.Is the Analysis services service started on the local machine?
Simon Worth
Raj C. wrote:
> Hi,
> For some unknown reason, we are getting the following "Connection to Serve
r
> Failed" error message when we attempt to register our local server using M
S
> Analysis Services:
> "Errors occurred while connecting to '<localservername>'. Cannot open
> connection to Analysis server '<localservername>'. Cannot connect to the
> server '<localservername>'. The server is either not started or too busy.
Do
> you still want to register the server?
> Please note that we are running the Developer versions of MS SQL Server 20
00
> and MS Analysis Services with SP3 installed for both components on Windows
XP
> Professional.
> Also note that we ARE ABLE TO REGISTER A REMOTE SERVER successfully using
> Analysis Manager, but we aren't able to either register or connect to a lo
cal
> server because we get the message above.
> We are uttterly confused by this error message and would GREATLY APPRECIAT
E
> any help in resolving this confusing issue as soon as possible.
> Thanks,
> Raj C.|||If you mean did we launch Analysis Manager on the local machine - than yes.
But for some unknown reason, we can't register the local server but we can
register a remote server on the network. FYI - Our login name is a member o
f
the OLAP admin group.
Please HELP!
Raj C.
"Simon Worth" wrote:

> Is the Analysis services service started on the local machine?
> Simon Worth
> Raj C. wrote:
>|||No, I mean, is the actual Analysis Services Service running on the machine?
To start Microsoft? SQL Server? 2000 Analysis Services, follow these step
s:
Open Control Panel.
If your computer's operating system is Windows? 2000, open the
Administrative Tools folder, and then double-click Services.
If your computer's operating system is Windows NT? 4.0, double-click
Services.
Select MSSQLServerOLAPService, and then on the Action menu click Start.
Simon Worth
Raj C. wrote:[vbcol=seagreen]
> If you mean did we launch Analysis Manager on the local machine - than yes
.
> But for some unknown reason, we can't register the local server but we can
> register a remote server on the network. FYI - Our login name is a member
of
> the OLAP admin group.
> Please HELP!
> Raj C.
> "Simon Worth" wrote:
>|||Yes we are running bot SQL 2000 Enterprise Manager and Analysis Services on
the local machine.
"Simon Worth" wrote:

> No, I mean, is the actual Analysis Services Service running on the machine
?
> To start Microsoft? SQL Server? 2000 Analysis Services, follow these st
eps:
> Open Control Panel.
>
> If your computer's operating system is Windows? 2000, open the
> Administrative Tools folder, and then double-click Services.
> If your computer's operating system is Windows NT? 4.0, double-click
> Services.
> Select MSSQLServerOLAPService, and then on the Action menu click Start.
>
>
> Simon Worth
> Raj C. wrote:
>|||But is the service started? When you view the service in control panel
> services, is the MSSQLServerOLAPService service in a started state?
You can have it installed on the machine, but it doesn't do anything if
you don't actually start the service.
Simon Worth
Raj C. wrote:[vbcol=seagreen]
> Yes we are running bot SQL 2000 Enterprise Manager and Analysis Services o
n
> the local machine.
>
> "Simon Worth" wrote:
>

Connection to Server Failed - Analysis Services

Hi,
For some unknown reason, we are getting the following "Connection to Server
Failed" error message when we attempt to register our local server using MS
Analysis Services:
"Errors occurred while connecting to '<localservername>'. Cannot open
connection to Analysis server '<localservername>'. Cannot connect to the
server '<localservername>'. The server is either not started or too busy. Do
you still want to register the server?
Please note that we are running the Developer versions of MS SQL Server 2000
and MS Analysis Services with SP3 installed for both components on Windows XP
Professional.
Also note that we ARE ABLE TO REGISTER A REMOTE SERVER successfully using
Analysis Manager, but we aren't able to either register or connect to a local
server because we get the message above.
We are uttterly confused by this error message and would GREATLY APPRECIATE
any help in resolving this confusing issue as soon as possible.
Thanks,
Raj C.
Is the Analysis services service started on the local machine?
Simon Worth
Raj C. wrote:
> Hi,
> For some unknown reason, we are getting the following "Connection to Server
> Failed" error message when we attempt to register our local server using MS
> Analysis Services:
> "Errors occurred while connecting to '<localservername>'. Cannot open
> connection to Analysis server '<localservername>'. Cannot connect to the
> server '<localservername>'. The server is either not started or too busy. Do
> you still want to register the server?
> Please note that we are running the Developer versions of MS SQL Server 2000
> and MS Analysis Services with SP3 installed for both components on Windows XP
> Professional.
> Also note that we ARE ABLE TO REGISTER A REMOTE SERVER successfully using
> Analysis Manager, but we aren't able to either register or connect to a local
> server because we get the message above.
> We are uttterly confused by this error message and would GREATLY APPRECIATE
> any help in resolving this confusing issue as soon as possible.
> Thanks,
> Raj C.
|||If you mean did we launch Analysis Manager on the local machine - than yes.
But for some unknown reason, we can't register the local server but we can
register a remote server on the network. FYI - Our login name is a member of
the OLAP admin group.
Please HELP!
Raj C.
"Simon Worth" wrote:

> Is the Analysis services service started on the local machine?
> Simon Worth
> Raj C. wrote:
>
|||No, I mean, is the actual Analysis Services Service running on the machine?
To start Microsoft? SQL Server? 2000 Analysis Services, follow these steps:
Open Control Panel.
If your computer's operating system is Windows? 2000, open the
Administrative Tools folder, and then double-click Services.
If your computer's operating system is Windows NT? 4.0, double-click
Services.
Select MSSQLServerOLAPService, and then on the Action menu click Start.
Simon Worth
Raj C. wrote:[vbcol=seagreen]
> If you mean did we launch Analysis Manager on the local machine - than yes.
> But for some unknown reason, we can't register the local server but we can
> register a remote server on the network. FYI - Our login name is a member of
> the OLAP admin group.
> Please HELP!
> Raj C.
> "Simon Worth" wrote:
>
|||Yes we are running bot SQL 2000 Enterprise Manager and Analysis Services on
the local machine.
"Simon Worth" wrote:

> No, I mean, is the actual Analysis Services Service running on the machine?
> To start Microsoft? SQL Server? 2000 Analysis Services, follow these steps:
> Open Control Panel.
>
> If your computer's operating system is Windows? 2000, open the
> Administrative Tools folder, and then double-click Services.
> If your computer's operating system is Windows NT? 4.0, double-click
> Services.
> Select MSSQLServerOLAPService, and then on the Action menu click Start.
>
>
> Simon Worth
> Raj C. wrote:
>
|||But is the service started? When you view the service in control panel
> services, is the MSSQLServerOLAPService service in a started state?
You can have it installed on the machine, but it doesn't do anything if
you don't actually start the service.
Simon Worth
Raj C. wrote:[vbcol=seagreen]
> Yes we are running bot SQL 2000 Enterprise Manager and Analysis Services on
> the local machine.
>
> "Simon Worth" wrote:
>

Connection to remote sql server db

Hi,
I'm new to SQL and would like to connect to a remote sql server where a
website is hosted and do some updates.
I have a local sqlserver setup here, could you pl guide me
some doc or urls.
I have to backup the db frm the remote sqlserver, my host company told me to
use dts to carry out the back from their server.
Pleaase advice how can I do this
Many Thanks
Shan"shan" <shan@.discussions.microsoft.com> wrote in message
news:670104E2-8986-432A-946C-C2C41931673A@.microsoft.com...
> I'm new to SQL and would like to connect to a remote sql server where a
> website is hosted and do some updates.
> I have a local sqlserver setup here, could you pl guide me
> some doc or urls.
> I have to backup the db frm the remote sqlserver, my host company told me
to
> use dts to carry out the back from their server.
> Pleaase advice how can I do this
The host company could allow a VPN tunnel to the remote server and/or open
the proper firewall ports to/from your computer. You could then use DTS, or
TSQL to issue a BACKUP... or synchronize the updates from your computer to
the hosted version.
Steve

Connection to remote sql server db

Hi,
I'm new to SQL and would like to connect to a remote sql server where a
website is hosted and do some updates.
I have a local sqlserver setup here, could you pl guide me
some doc or urls.
I have to backup the db frm the remote sqlserver, my host company told me to
use dts to carry out the back from their server.
Pleaase advice how can I do this
Many Thanks
Shan
"shan" <shan@.discussions.microsoft.com> wrote in message
news:670104E2-8986-432A-946C-C2C41931673A@.microsoft.com...
> I'm new to SQL and would like to connect to a remote sql server where a
> website is hosted and do some updates.
> I have a local sqlserver setup here, could you pl guide me
> some doc or urls.
> I have to backup the db frm the remote sqlserver, my host company told me
to
> use dts to carry out the back from their server.
> Pleaase advice how can I do this
The host company could allow a VPN tunnel to the remote server and/or open
the proper firewall ports to/from your computer. You could then use DTS, or
TSQL to issue a BACKUP... or synchronize the updates from your computer to
the hosted version.
Steve

Connection to database on a remote server

Here is my environment and problem:

I have VWD 2005 and SSE 2005 installed on my local machine. I also have these installed on my Windows 2003 Server. I developed my database using SSE on my local machine but pointing to directory on my server. I have been developing the web app using VWD on my server. I now want to use VWD on my local machine and point to the project on my server. I am able to open the project. In order to access the database in the "Database Explorer" I use as my "Data Source", "MS SQL Server (SQL Client) and it attaches fine and I can see my tables and data.

Now for my problem:

When I try to run the application "VIew in Browser", which login.aspx page is my first page, I get the page, but it doesn't inherit my master page which has the basic navigation and layout. Then after I try to login I get this message.

The file "W:\BBApp\App_Data\TimeTracker.mdf" is on a network path that is not supported for database files.
An attempt to attach an auto-named database for file W:\BBApp\App_Data\TimeTracker.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

Here is a portion of my web.config file for the connection string.

<connectionStrings>

<removename="LocalSqlServer" />

<addname="LocalSqlServer"connectionString="Data Source=.\SQLExpress;Integrated Security=true;AttachDBFilename=|DataDirectory|TimeTracker.mdf;User Instance=true" />

My website I started with the source code for the TimeTracker start kit and have added more pages and changed the sitemap.

In general I guess I need to know how to handle using VWD on my local machine, but accessing the project on the server. The reason I'm doing this is because my colleague needs to be able to access the web app too to add pages to the site.

Thank you for any help.

Take a read of this articlehttp://www.aspspider.net/resources/Resource170.aspx
should see you right. Also if you are using membership remember you will need to take
care about the aspnetdb.mdf aswell.

Hope it help, if not let me know.

connection to Analysis server failed

May you help for beginner.
I have installed MS SQL server 2005 to local computer. I can not connect to
Server type "Analysis Services" from Management studio.
Message "A connection cannot be made. Ensure that the server is running.
(Microsoft.AnalysisServices.AdomdClient)" appears.
But I can connect to the following Server types: Database Engine
Reporting service
Integration service
I have reinstalled application, but same behaviour.
Please, how I can ensure that AnalysisServices server is running?
Thank you for your help.
Zdenek
You can use the SQL Server Configuration Manager to check
the service.
Open up SQL Server Configuration Manager and on the left,
select SQL Server 2005 Services. On the right, check SQL
Server Analysis Services. You can start it from here if it's
not running and you can configure how, when you want the
service to start (manual, automatic, etc)
-Sue
On Sat, 17 Mar 2007 04:21:03 -0700, Zdenek
<Zdenek@.discussions.microsoft.com> wrote:

>May you help for beginner.
>I have installed MS SQL server 2005 to local computer. I can not connect to
>Server type "Analysis Services" from Management studio.
>Message "A connection cannot be made. Ensure that the server is running.
>(Microsoft.AnalysisServices.AdomdClient)" appears.
>But I can connect to the following Server types: Database Engine
>Reporting service
>Integration service
>I have reinstalled application, but same behaviour.
>Please, how I can ensure that AnalysisServices server is running?
>Thank you for your help.
>Zdenek

connection to Analysis server failed

May you help for beginner.
I have installed MS SQL server 2005 to local computer. I can not connect to
Server type "Analysis Services" from Management studio.
Message "A connection cannot be made. Ensure that the server is running.
(Microsoft.AnalysisServices.AdomdClient)" appears.
But I can connect to the following Server types: Database Engine
Reporting service
Integration service
I have reinstalled application, but same behaviour.
Please, how I can ensure that AnalysisServices server is running?
Thank you for your help.
ZdenekYou can use the SQL Server Configuration Manager to check
the service.
Open up SQL Server Configuration Manager and on the left,
select SQL Server 2005 Services. On the right, check SQL
Server Analysis Services. You can start it from here if it's
not running and you can configure how, when you want the
service to start (manual, automatic, etc)
-Sue
On Sat, 17 Mar 2007 04:21:03 -0700, Zdenek
<Zdenek@.discussions.microsoft.com> wrote:

>May you help for beginner.
>I have installed MS SQL server 2005 to local computer. I can not connect to
>Server type "Analysis Services" from Management studio.
>Message "A connection cannot be made. Ensure that the server is running.
>(Microsoft.AnalysisServices.AdomdClient)" appears.
>But I can connect to the following Server types: Database Engine
>Reporting service
>Integration service
>I have reinstalled application, but same behaviour.
>Please, how I can ensure that AnalysisServices server is running?
>Thank you for your help.
>Zdenek

connection strings

I am trying to develop a web site. I have a local ms sql database on my machine.

I am trying to connect to a ms Sql database on a goDaddy server from the application.

I am trying to understand the connection string and its total properties.

here is what I think should be in my web.config file

<

add name="Personal" connectionString="Server=whsql-v12.prod.mesa1.secureserver.net;

Database=DB_XX10;

User ID=myID;

Password=myypassword;

Trusted_Connection=False" providerName="System.Data.SqlClient"

/>

<remove name="LocalSqlServer"/>

can someone please tell me where I am going wrong, Thanks for your help....

If you search these forums for "GoDaddy" you will find that a lot of people have had problems with them. One being, that Go Daddy does not allow remote SQL Server connections.|||

Do you think it might be possible that somene would share their web.config that would overcome the problem?

Am I asking too much to think that I could develop my site locally and then have some reasonable way of uploading the web site AND update the database on the GODaddy ms sql server with the new data etc.

I am really looking for an overview of the process.

Thanks for your response......

|||You can NOT use a GoDaddy SQL Server from any server except their own, that is how they have things configured. It isn't about the Connection String.|||

So that means I can not access The GODADDY server from my local development enviroment?

SO to set up a development enviroment I would have to update the database directly as well as the web site it self. Is there a overview of such an enviroment available on the net AnyWhere?

Thanks for your quick response

|||

krisfr:

So that means I can not access The GODADDY server from my local development enviroment?

Pretty much. Can't do it. As for your other question, I am not sure. Google can help though.

|||Can I set up the web.config to look for the database locally first, and if it can not find the database then look for the GoDaddy datadase?|||Not really, no. What you can do is setup two connection strings, one for local and another for GoDaddy, and switch them out.

Connection String suddenly Stops working

Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working ?
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaun
Strange. It looks that both strings are correct (although I would put the
network part toward the end as a personal preference).
I often refer to http://www.connectionstrings.com/ for examples and usage of
connection strings.
Keith
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.c om...
> Hi
> Odd one here, I have a local version of SQL running on my laptop for
> demos, been working fine for years yet yesterday I suddenly get an
> error "Invalid Conection Parameter" running a sproc using the
> following connection string (Its an Access 2002 App to SQL 2000)
> strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> Works fine if I use the server based SQL resource
> So I change it to be the following and it starts working ?
> strConnect = "Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> So it started not liking the 'Network=DBMSSOCN' part but both the
> datbases have TCP/IP and Named Pipes setup as network protocols and
> bot have not chnaged config for years
> I did install SP2 for XP a few weeks ago but I'm sure I have run it
> since (mind you I wish I'd never done SP2 with all the unasked for
> 'extras' MS dump on your PC but thats another thread)
> Thanks all
> shaun
|||Thanks for the link Keith
Yep it is odd as I thought both were fine as well and the one now is
not working worked fine for months!!!
Ah well the odditiess of Microsoft
Cheers
Shaun
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message news:<uQts2dgCFHA.3908@.TK2MSFTNGP12.phx.gbl>...[vbcol=seagreen]
> Strange. It looks that both strings are correct (although I would put the
> network part toward the end as a personal preference).
> I often refer to http://www.connectionstrings.com/ for examples and usage of
> connection strings.
> --
> Keith
>
> "Shaun" <shaunsizen@.msn.com> wrote in message
> news:4a2f9143.0502030133.5892ee76@.posting.google.c om...
|||Win XP SP2 also probably updated your MDAC or exposed an MDAC vunerability
that was updated recently through Windows Updates.
Nevertheless, you are using the OLEDB for ODBC, MSADSQL? Why not just use
the SQLOLEDB directly seeing as you are not using the functionality that an
ODBC DSN would give you? If I am wrong, then it is the DRIVER=SQLSERVER
that is throwing you. That's an ODBC Only OLEDB parameter.
Sincerely,
Anthony Thomas

"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.c om...
Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working ?
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaun

Connection String suddenly Stops working

Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaunStrange. It looks that both strings are correct (although I would put the
network part toward the end as a personal preference).
I often refer to http://www.connectionstrings.com/ for examples and usage of
connection strings.
--
Keith
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
> Hi
> Odd one here, I have a local version of SQL running on my laptop for
> demos, been working fine for years yet yesterday I suddenly get an
> error "Invalid Conection Parameter" running a sproc using the
> following connection string (Its an Access 2002 App to SQL 2000)
> strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> Works fine if I use the server based SQL resource
> So I change it to be the following and it starts working '
> strConnect = "Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> So it started not liking the 'Network=DBMSSOCN' part but both the
> datbases have TCP/IP and Named Pipes setup as network protocols and
> bot have not chnaged config for years
> I did install SP2 for XP a few weeks ago but I'm sure I have run it
> since (mind you I wish I'd never done SP2 with all the unasked for
> 'extras' MS dump on your PC but thats another thread)
> Thanks all
> shaun|||Thanks for the link Keith
Yep it is odd as I thought both were fine as well and the one now is
not working worked fine for months!!!
Ah well the odditiess of Microsoft
Cheers
Shaun
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message news:<uQts2dgCFHA.3908@.TK2MSFTNGP12.phx.gbl>...
> Strange. It looks that both strings are correct (although I would put the
> network part toward the end as a personal preference).
> I often refer to http://www.connectionstrings.com/ for examples and usage of
> connection strings.
> --
> Keith
>
> "Shaun" <shaunsizen@.msn.com> wrote in message
> news:4a2f9143.0502030133.5892ee76@.posting.google.com...
> > Hi
> >
> > Odd one here, I have a local version of SQL running on my laptop for
> > demos, been working fine for years yet yesterday I suddenly get an
> > error "Invalid Conection Parameter" running a sproc using the
> > following connection string (Its an Access 2002 App to SQL 2000)
> >
> > strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
> > Server;UID=abc;PWD=def"
> >
> > Works fine if I use the server based SQL resource
> >
> > So I change it to be the following and it starts working '
> >
> > strConnect = "Server=" & DB_Server & ";DRIVER=SQL
> > Server;UID=abc;PWD=def"
> >
> > So it started not liking the 'Network=DBMSSOCN' part but both the
> > datbases have TCP/IP and Named Pipes setup as network protocols and
> > bot have not chnaged config for years
> >
> > I did install SP2 for XP a few weeks ago but I'm sure I have run it
> > since (mind you I wish I'd never done SP2 with all the unasked for
> > 'extras' MS dump on your PC but thats another thread)
> >
> > Thanks all
> > shaun|||Win XP SP2 also probably updated your MDAC or exposed an MDAC vunerability
that was updated recently through Windows Updates.
Nevertheless, you are using the OLEDB for ODBC, MSADSQL? Why not just use
the SQLOLEDB directly seeing as you are not using the functionality that an
ODBC DSN would give you? If I am wrong, then it is the DRIVER=SQLSERVER
that is throwing you. That's an ODBC Only OLEDB parameter.
Sincerely,
Anthony Thomas
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaun

Connection String suddenly Stops working

Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaunStrange. It looks that both strings are correct (although I would put the
network part toward the end as a personal preference).
I often refer to http://www.connectionstrings.com/ for examples and usage of
connection strings.
Keith
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
> Hi
> Odd one here, I have a local version of SQL running on my laptop for
> demos, been working fine for years yet yesterday I suddenly get an
> error "Invalid Conection Parameter" running a sproc using the
> following connection string (Its an Access 2002 App to SQL 2000)
> strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> Works fine if I use the server based SQL resource
> So I change it to be the following and it starts working '
> strConnect = "Server=" & DB_Server & ";DRIVER=SQL
> Server;UID=abc;PWD=def"
> So it started not liking the 'Network=DBMSSOCN' part but both the
> datbases have TCP/IP and Named Pipes setup as network protocols and
> bot have not chnaged config for years
> I did install SP2 for XP a few weeks ago but I'm sure I have run it
> since (mind you I wish I'd never done SP2 with all the unasked for
> 'extras' MS dump on your PC but thats another thread)
> Thanks all
> shaun|||Thanks for the link Keith
Yep it is odd as I thought both were fine as well and the one now is
not working worked fine for months!!!
Ah well the odditiess of Microsoft
Cheers
Shaun
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message news:<uQts2dgCFHA.3908@.TK2MS
FTNGP12.phx.gbl>...[vbcol=seagreen]
> Strange. It looks that both strings are correct (although I would put the
> network part toward the end as a personal preference).
> I often refer to http://www.connectionstrings.com/ for examples and usage
of
> connection strings.
> --
> Keith
>
> "Shaun" <shaunsizen@.msn.com> wrote in message
> news:4a2f9143.0502030133.5892ee76@.posting.google.com...|||Win XP SP2 also probably updated your MDAC or exposed an MDAC vunerability
that was updated recently through Windows Updates.
Nevertheless, you are using the OLEDB for ODBC, MSADSQL? Why not just use
the SQLOLEDB directly seeing as you are not using the functionality that an
ODBC DSN would give you? If I am wrong, then it is the DRIVER=SQLSERVER
that is throwing you. That's an ODBC Only OLEDB parameter.
Sincerely,
Anthony Thomas
"Shaun" <shaunsizen@.msn.com> wrote in message
news:4a2f9143.0502030133.5892ee76@.posting.google.com...
Hi
Odd one here, I have a local version of SQL running on my laptop for
demos, been working fine for years yet yesterday I suddenly get an
error "Invalid Conection Parameter" running a sproc using the
following connection string (Its an Access 2002 App to SQL 2000)
strConnect = "Network=DBMSSOCN;Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
Works fine if I use the server based SQL resource
So I change it to be the following and it starts working '
strConnect = "Server=" & DB_Server & ";DRIVER=SQL
Server;UID=abc;PWD=def"
So it started not liking the 'Network=DBMSSOCN' part but both the
datbases have TCP/IP and Named Pipes setup as network protocols and
bot have not chnaged config for years
I did install SP2 for XP a few weeks ago but I'm sure I have run it
since (mind you I wish I'd never done SP2 with all the unasked for
'extras' MS dump on your PC but thats another thread)
Thanks all
shaun