Remote ODBC connections fail to SQL 2005 database (Error: 18456, Severity: 14, State: 8.)

I have reviewed the blog posting "Understanding "login failed" (Error
18456) error messages in SQL Server 2005" at
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
2007-03-21 11:49:14.55 Logon Error: 18456, Severity: 14, State: 8.
2007-03-21 11:49:14.55 Logon Login failed for user 'USERNAMEOBSCURED'.
[CLIENT: 192.168.183.144]
According to the blog, this indicates that the password is invalid, but I
have reset it 5 times, making sure the password is the same at both ends.
This username, USERNAMEOBSCURED, is a SQL Server authentication type user,
and I have verfied that Enforce password policy, expiration, must change
password are all unchecked and the account is not set to locked out.
The ODBC client is another Windows Server 2003 SP1 computer in the same
workgroup as the SQL 2005 SP1 server. I am using the Microsoft SQL Server
ODBC Driver Version 03.86.1830 via TCP/IP.
Since I don't have that much experence running SQL server, which and
what database permissions should USERNAMEOBSCURED be given? If I want to
create a new username to test it, how should that be done for SQL Server
authentication? If these are in the books online, please point me to the
right location.
Hi,
I understand that you encountered the error:
Login failed for user 'USERNAMEOBSCURED'
When you remotely use ODBC driver to connect to your SQL 2005 instance.
If I have misunderstood, please let me know.
For troubleshooting the login errors, you may refer to:
Troubleshooting: Login failed for user 'x'
http://msdn2.microsoft.com/en-us/library/ms366351.aspx
How to: Change Server Authentication Mode
http://msdn2.microsoft.com/en-us/library/ms188670.aspx
Though the error state indicates that it is a password error, I recommend
that also check the following and let me know the results:
1. Check if you can log on your SQL Server locally with the login and
password;
2. Open SQL Server Configuration Manager to see if the TCP/IP protocol has
been enabled;
3. Open SQL Server Surface Area Configuration, click Surface Area
Configuration for Services and Connections to see if Local and remote
connections is selected under the Remote Connections.
4. If the issue persists, try creating a new login to see if this issue
persists;
5. Run "osql /S<server name> /U<login id> /P<password>" from command line
on your client computer to check if you can connect to your SQL Server;
6. Disable the firewall on your SQL Server computer and run "netstat -nba
>C:\serviceslist.log" to check which TCP port has been listened by your SQL
Server service (sqlservr.exe); then run "telnet <server name> <TCP port>"
from command on the client computer to check if you can log on the port.
7. Run "cliconfg.exe" from command line on the client computer, switch to
the Alias tab, add an alias with TCP/IP protocol for the SQL instance.
Please note that fill in the correct Tcp port and server name (the SQL
Server computer name) in the input fields. Then run the step 2 again.
If all above methods still cannot make it work, please use NetMon to
monitor the network stream by filter the TCP protocal and port.
You may refer to:
Microsoft Network Monitor 3
http://www.microsoft.com/downloads/details.aspx?familyid=AA8BE06D-4A6A-4B69-
B861-2043B665CB53&displaylang=en
How To Capture TCP and HTTP Data Frames Using Network Monitor and MSXML
HTTP Code
http://support.microsoft.com/kb/295405
How to capture network traffic with Network Monitor
http://support.microsoft.com/kb/148942
Troubleshooting by Using Network Monitor
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/intwork/
inbc_ias_ykqb.mspx?mfr=true
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.
================================================== ====
|||Using suggestion 4 by creating a new user USERNAMEOBSCUREDTEST and
setting the User Mapping set to DATABASENAMEOBSCURED database under Default
Schema dbo is proving to be a temporary workaround. I am consulting with
the 3rd party creator of the database to try and understand why the username
is already in the database but is not mapped according to SQL 2005. I am
wondering if this is due to the fact that the database was not created fresh
in SQL 2005, it was imported from an existing SQL 7 database from another
machine. Apparently USERNAMEOBSCURED is not mapped to any database according
to the view in Microsoft SQL Server Management Studio, and when I attempt to
map the username to DATABASENAMEOBSCURED with the default Database role
membership of public I get this error:
"TITLE: Microsoft SQL Server Management Studio
Create failed for User 'USERNAMEOBSCURED'. (Microsoft.SqlServer.Smo)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=Create+User&LinkId=20476[/url]
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
User, group, or role 'USERNAMEOBSCURED' already exists in the current
database. (Microsoft SQL Server, Error: 15023)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .2047&EvtSrc=MSSQLServer&EvtID=15023&LinkId=20476[ /url]
BUTTONS:
OK
--"
"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:ic0m3bFbHHA.1028@.TK2MSFTNGHUB02.phx.gbl...
> Hi,
> I understand that you encountered the error:
> Login failed for user 'USERNAMEOBSCURED'
> When you remotely use ODBC driver to connect to your SQL 2005 instance.
> If I have misunderstood, please let me know.
> For troubleshooting the login errors, you may refer to:
> Troubleshooting: Login failed for user 'x'
> http://msdn2.microsoft.com/en-us/library/ms366351.aspx
> How to: Change Server Authentication Mode
> http://msdn2.microsoft.com/en-us/library/ms188670.aspx
> Though the error state indicates that it is a password error, I recommend
> that also check the following and let me know the results:
> 1. Check if you can log on your SQL Server locally with the login and
> password;
> 2. Open SQL Server Configuration Manager to see if the TCP/IP protocol has
> been enabled;
> 3. Open SQL Server Surface Area Configuration, click Surface Area
> Configuration for Services and Connections to see if Local and remote
> connections is selected under the Remote Connections.
> 4. If the issue persists, try creating a new login to see if this issue
> persists;
> 5. Run "osql /S<server name> /U<login id> /P<password>" from command line
> on your client computer to check if you can connect to your SQL Server;
> 6. Disable the firewall on your SQL Server computer and run "netstat -nba
> Server service (sqlservr.exe); then run "telnet <server name> <TCP port>"
> from command on the client computer to check if you can log on the port.
> 7. Run "cliconfg.exe" from command line on the client computer, switch to
> the Alias tab, add an alias with TCP/IP protocol for the SQL instance.
> Please note that fill in the correct Tcp port and server name (the SQL
> Server computer name) in the input fields. Then run the step 2 again.
> If all above methods still cannot make it work, please use NetMon to
> monitor the network stream by filter the TCP protocal and port.
> You may refer to:
> Microsoft Network Monitor 3
> http://www.microsoft.com/downloads/details.aspx?familyid=AA8BE06D-4A6A-4B69-
> B861-2043B665CB53&displaylang=en
> How To Capture TCP and HTTP Data Frames Using Network Monitor and MSXML
> HTTP Code
> http://support.microsoft.com/kb/295405
> How to capture network traffic with Network Monitor
> http://support.microsoft.com/kb/148942
> Troubleshooting by Using Network Monitor
> http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/intwork/
> inbc_ias_ykqb.mspx?mfr=true
> 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,
Thanks for your response.
Since your database is migrated from SQL 7.0, this issue is indeed
possible. Please try the tool mapsids.exe according to this article to see
if this issue persists:
How to resolve permission issues when you move a database between servers
that are running SQL Server
http://support.microsoft.com/kb/240872/EN-US/
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://support.microsoft.com/kb/274188/
Hope this helps.
Best regards,
Charles Wang
Microsoft Online Partner Support
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
================================================== ====
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,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
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.
================================================== ====
|||Sorry for the long delay, we were able to fix the issue with the
duplicate users, I'll have to dig up my notes from two weeks ago to recall
the procedure we used. Sorry for not closing this issue sooner.
"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:Y6QkJsFcHHA.2060@.TK2MSFTNGHUB02.phx.gbl...
> Hi,
> I am interested in this issue. Would you mind letting me know the result
> of
> the suggestions? If you need further assistance, feel free to let me know.
> I will be more than happy to be of assistance.
> 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.
> ================================================== ====
>
|||Hi,
Thanks for your updating and response. Please do not worry about it.
Anytime your posting back is welcome.
Have a good day!
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.
================================================== ====

Remote ODBC connections fail to SQL 2005 database (Error: 18456, Severity: 14, State: 8.)

I have reviewed the blog posting "Understanding "login failed" (Error
18456) error messages in SQL Server 2005" at
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
2007-03-21 11:49:14.55 Logon Error: 18456, Severity: 14, State: 8.
2007-03-21 11:49:14.55 Logon Login failed for user 'USERNAMEOBSCURED'.
[CLIENT: 192.168.183.144]
According to the blog, this indicates that the password is invalid, but I
have reset it 5 times, making sure the password is the same at both ends.
This username, USERNAMEOBSCURED, is a SQL Server authentication type user,
and I have verfied that Enforce password policy, expiration, must change
password are all unchecked and the account is not set to locked out.
The ODBC client is another Windows Server 2003 SP1 computer in the same
workgroup as the SQL 2005 SP1 server. I am using the Microsoft SQL Server
ODBC Driver Version 03.86.1830 via TCP/IP.
Since I don't have that much experence running SQL server, which and
what database permissions should USERNAMEOBSCURED be given? If I want to
create a new username to test it, how should that be done for SQL Server
authentication? If these are in the books online, please point me to the
right location.Hi,
I understand that you encountered the error:
Login failed for user 'USERNAMEOBSCURED'
When you remotely use ODBC driver to connect to your SQL 2005 instance.
If I have misunderstood, please let me know.
For troubleshooting the login errors, you may refer to:
Troubleshooting: Login failed for user 'x'
http://msdn2.microsoft.com/en-us/library/ms366351.aspx
How to: Change Server Authentication Mode
http://msdn2.microsoft.com/en-us/library/ms188670.aspx
Though the error state indicates that it is a password error, I recommend
that also check the following and let me know the results:
1. Check if you can log on your SQL Server locally with the login and
password;
2. Open SQL Server Configuration Manager to see if the TCP/IP protocol has
been enabled;
3. Open SQL Server Surface Area Configuration, click Surface Area
Configuration for Services and Connections to see if Local and remote
connections is selected under the Remote Connections.
4. If the issue persists, try creating a new login to see if this issue
persists;
5. Run "osql /S<server name> /U<login id> /P<password>" from command line
on your client computer to check if you can connect to your SQL Server;
6. Disable the firewall on your SQL Server computer and run "netstat -nba
>C:\serviceslist.log" to check which TCP port has been listened by your SQL
Server service (sqlservr.exe); then run "telnet <server name> <TCP port>"
from command on the client computer to check if you can log on the port.
7. Run "cliconfg.exe" from command line on the client computer, switch to
the Alias tab, add an alias with TCP/IP protocol for the SQL instance.
Please note that fill in the correct Tcp port and server name (the SQL
Server computer name) in the input fields. Then run the step 2 again.
If all above methods still cannot make it work, please use NetMon to
monitor the network stream by filter the TCP protocal and port.
You may refer to:
Microsoft Network Monitor 3
http://www.microsoft.com/downloads/details.aspx?familyid=AA8BE06D-4A6A-4B69-
B861-2043B665CB53&displaylang=en
How To Capture TCP and HTTP Data Frames Using Network Monitor and MSXML
HTTP Code
http://support.microsoft.com/kb/295405
How to capture network traffic with Network Monitor
http://support.microsoft.com/kb/148942
Troubleshooting by Using Network Monitor
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/intwork/
inbc_ias_ykqb.mspx?mfr=true
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.
======================================================|||Using suggestion 4 by creating a new user USERNAMEOBSCUREDTEST and
setting the User Mapping set to DATABASENAMEOBSCURED database under Default
Schema dbo is proving to be a temporary workaround. I am consulting with
the 3rd party creator of the database to try and understand why the username
is already in the database but is not mapped according to SQL 2005. I am
wondering if this is due to the fact that the database was not created fresh
in SQL 2005, it was imported from an existing SQL 7 database from another
machine. Apparently USERNAMEOBSCURED is not mapped to any database according
to the view in Microsoft SQL Server Management Studio, and when I attempt to
map the username to DATABASENAMEOBSCURED with the default Database role
membership of public I get this error:
"TITLE: Microsoft SQL Server Management Studio
--
Create failed for User 'USERNAMEOBSCURED'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+User&LinkId=20476
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
User, group, or role 'USERNAMEOBSCURED' already exists in the current
database. (Microsoft SQL Server, Error: 15023)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=15023&LinkId=20476
--
BUTTONS:
OK
--"
"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:ic0m3bFbHHA.1028@.TK2MSFTNGHUB02.phx.gbl...
> Hi,
> I understand that you encountered the error:
> Login failed for user 'USERNAMEOBSCURED'
> When you remotely use ODBC driver to connect to your SQL 2005 instance.
> If I have misunderstood, please let me know.
> For troubleshooting the login errors, you may refer to:
> Troubleshooting: Login failed for user 'x'
> http://msdn2.microsoft.com/en-us/library/ms366351.aspx
> How to: Change Server Authentication Mode
> http://msdn2.microsoft.com/en-us/library/ms188670.aspx
> Though the error state indicates that it is a password error, I recommend
> that also check the following and let me know the results:
> 1. Check if you can log on your SQL Server locally with the login and
> password;
> 2. Open SQL Server Configuration Manager to see if the TCP/IP protocol has
> been enabled;
> 3. Open SQL Server Surface Area Configuration, click Surface Area
> Configuration for Services and Connections to see if Local and remote
> connections is selected under the Remote Connections.
> 4. If the issue persists, try creating a new login to see if this issue
> persists;
> 5. Run "osql /S<server name> /U<login id> /P<password>" from command line
> on your client computer to check if you can connect to your SQL Server;
> 6. Disable the firewall on your SQL Server computer and run "netstat -nba
>>C:\serviceslist.log" to check which TCP port has been listened by your SQL
> Server service (sqlservr.exe); then run "telnet <server name> <TCP port>"
> from command on the client computer to check if you can log on the port.
> 7. Run "cliconfg.exe" from command line on the client computer, switch to
> the Alias tab, add an alias with TCP/IP protocol for the SQL instance.
> Please note that fill in the correct Tcp port and server name (the SQL
> Server computer name) in the input fields. Then run the step 2 again.
> If all above methods still cannot make it work, please use NetMon to
> monitor the network stream by filter the TCP protocal and port.
> You may refer to:
> Microsoft Network Monitor 3
> http://www.microsoft.com/downloads/details.aspx?familyid=AA8BE06D-4A6A-4B69-
> B861-2043B665CB53&displaylang=en
> How To Capture TCP and HTTP Data Frames Using Network Monitor and MSXML
> HTTP Code
> http://support.microsoft.com/kb/295405
> How to capture network traffic with Network Monitor
> http://support.microsoft.com/kb/148942
> Troubleshooting by Using Network Monitor
> http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/intwork/
> inbc_ias_ykqb.mspx?mfr=true
> 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,
Thanks for your response.
Since your database is migrated from SQL 7.0, this issue is indeed
possible. Please try the tool mapsids.exe according to this article to see
if this issue persists:
How to resolve permission issues when you move a database between servers
that are running SQL Server
http://support.microsoft.com/kb/240872/EN-US/
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://support.microsoft.com/kb/274188/
Hope this helps.
Best regards,
Charles Wang
Microsoft Online Partner Support
PLEASE NOTE: The partner managed newsgroups are provided
to assist with break/fix issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader:
microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================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,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
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.
======================================================|||Sorry for the long delay, we were able to fix the issue with the
duplicate users, I'll have to dig up my notes from two weeks ago to recall
the procedure we used. Sorry for not closing this issue sooner.
"Charles Wang[MSFT]" <changliw@.online.microsoft.com> wrote in message
news:Y6QkJsFcHHA.2060@.TK2MSFTNGHUB02.phx.gbl...
> Hi,
> I am interested in this issue. Would you mind letting me know the result
> of
> the suggestions? If you need further assistance, feel free to let me know.
> I will be more than happy to be of assistance.
> 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.
> ======================================================>|||Hi,
Thanks for your updating and response. Please do not worry about it.
Anytime your posting back is welcome.
Have a good day!
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.
======================================================

Remote DTSX execution, when sql25k fails.

Hi everyone,

This is my snippet of code. It works fine with remote DTSX but when they have got connections against Sql Server 2005, ending given the following error:

Event: (On error)

12:21:52,-1071611876,0x,Error de la llamada del mtodo AcquireConnection al administrador de conexión "LOCALHOST.BDAplis"

That means more or less "Error on calling method AcquireConnection to Connection Manager localhost...

It's curious. I've got other packages which are using Sql Server 2000 connections without errors.

Thanks for your help,

pkgResults = pkg.Validate(Nothing, Nothing, EventsSSIS, Nothing)

If pkgResults = DTSExecResult.Success Then

pkg = app.LoadPackage(ActObject.packageName, Nothing, True)

endif

pkg.InteractiveMode = False

pkgResults = pkg.Execute()

Is this really remote execution? SSIS is really a client side tool. The user trying to make the connection to the SQL server, through a SQL connection in the package, is the user running your code. So who is running your code, and do they have rights to connect to your SQL Server? I would check the SQL server error log. Good practice says we have set the server level security option to log failed connections, and that should tell you who the user is. Alternatively run a SQL Server profiler trace against the server concerned, and select the login failed event. When the failure happens, you should see the event in the profiler output, and can see who the user is.|||

Hi DarrenSQLIS,

Thanks for you reply.

Ok, my user domain is doing the connection but how to select for LoadPackage(,,,) method another user, an Administrator user, for example.

Otherwise loadfromsqlserver offer the possibility to define user and password.

thanks

Remote database Connection Error!

use sql2k5 surface area configuration tool to enable 'remote connections'.
-oj
"Sujata P" <SujataP@.discussions.microsoft.com> wrote in message
news:94D32EEB-9098-4A51-B55D-95BD84B5AA96@.microsoft.com...
> Hi,
> My Application which is written in VB.Net uses database connection to my
> Local Instance of SQL Server Express version.
> My connection string is " Data
> Source=SM5\SQLEXPRESS;AttachDbFilename=C
:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\MgmtSystem.mdf;Initial
> Catalog=MgmtSystem;Persist
> Security Info=True;User ID=sa;Password=belmont". When I run my application
> from the same machine where SQL Server instance is installed, it works
> fine.
> But now I am intending to use it as Client-Server type as database on
> Server
> and application running from another machine. To test this I have
> deployed
> my application on another machine. When I run it I get following error,
> "An
> error has occured while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default setting SQL Server does not allow remote
> connections.(provider: SQL Network Interface, error: 26 - Error Locating
> Server/Instance specified)(Microsoft SQL Server Error:-1).
> To Fix this I did try enabling all protocols(Shared Memory, TCP/IP, Named
> Pipe). Then I even started SQL Browser service to enable the instance to
> be
> browsed by client. Then Checked if Hide Instance property. Still no Luck.
> I am really going crazy. This is really important for me since we are
> migrating from Access to SQL Server Express. Since in Access my
> application
> can have client server
> Architecture. Same thing I need to have in SQL Express.
> Any help is really appreciated.
> Thanks,
> SujataHi,
My Application which is written in VB.Net uses database connection to my
Local Instance of SQL Server Express version.
My connection string is " Data
Source=SM5\SQLEXPRESS;AttachDbFilename=C
:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data\MgmtSystem.mdf;Initial Catalog=MgmtSystem;Persist
Security Info=True;User ID=sa;Password=belmont". When I run my application
from the same machine where SQL Server instance is installed, it works fine.
But now I am intending to use it as Client-Server type as database on Server
and application running from another machine. To test this I have deployed
my application on another machine. When I run it I get following error, "An
error has occured while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default setting SQL Server does not allow remote
connections.(provider: SQL Network Interface, error: 26 - Error Locating
Server/Instance specified)(Microsoft SQL Server Error:-1).
To Fix this I did try enabling all protocols(Shared Memory, TCP/IP, Named
Pipe). Then I even started SQL Browser service to enable the instance to be
browsed by client. Then Checked if Hide Instance property. Still no Luck.
I am really going crazy. This is really important for me since we are
migrating from Access to SQL Server Express. Since in Access my application
can have client server
Architecture. Same thing I need to have in SQL Express.
Any help is really appreciated.
Thanks,
Sujata|||use sql2k5 surface area configuration tool to enable 'remote connections'.
-oj
"Sujata P" <SujataP@.discussions.microsoft.com> wrote in message
news:94D32EEB-9098-4A51-B55D-95BD84B5AA96@.microsoft.com...
> Hi,
> My Application which is written in VB.Net uses database connection to my
> Local Instance of SQL Server Express version.
> My connection string is " Data
> Source=SM5\SQLEXPRESS;AttachDbFilename=C
:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data\MgmtSystem.mdf;Initial
> Catalog=MgmtSystem;Persist
> Security Info=True;User ID=sa;Password=belmont". When I run my application
> from the same machine where SQL Server instance is installed, it works
> fine.
> But now I am intending to use it as Client-Server type as database on
> Server
> and application running from another machine. To test this I have
> deployed
> my application on another machine. When I run it I get following error,
> "An
> error has occured while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default setting SQL Server does not allow remote
> connections.(provider: SQL Network Interface, error: 26 - Error Locating
> Server/Instance specified)(Microsoft SQL Server Error:-1).
> To Fix this I did try enabling all protocols(Shared Memory, TCP/IP, Named
> Pipe). Then I even started SQL Browser service to enable the instance to
> be
> browsed by client. Then Checked if Hide Instance property. Still no Luck.
> I am really going crazy. This is really important for me since we are
> migrating from Access to SQL Server Express. Since in Access my
> application
> can have client server
> Architecture. Same thing I need to have in SQL Express.
> Any help is really appreciated.
> Thanks,
> Sujata|||Thanks oj...but I found answer...Actually I did everything last time except
creating exceptions in Windows Firewall for instance of my SQL Server to
unblock the connection.
For anyone who is facing similar problem, Follow
http://support.microsoft.com/?id=914277..it is very useful for creating
remote connection.
"oj" wrote:

> use sql2k5 surface area configuration tool to enable 'remote connections'.
> --
> -oj
>
> "Sujata P" <SujataP@.discussions.microsoft.com> wrote in message
> news:94D32EEB-9098-4A51-B55D-95BD84B5AA96@.microsoft.com...
>
>|||Thanks oj...but I found answer...Actually I did everything last time except
creating exceptions in Windows Firewall for instance of my SQL Server to
unblock the connection.
For anyone who is facing similar problem, Follow
http://support.microsoft.com/?id=914277..it is very useful for creating
remote connection.
"oj" wrote:

> use sql2k5 surface area configuration tool to enable 'remote connections'.
> --
> -oj
>
> "Sujata P" <SujataP@.discussions.microsoft.com> wrote in message
> news:94D32EEB-9098-4A51-B55D-95BD84B5AA96@.microsoft.com...
>
>

Remote Connections with SQL Developers Edition

Hi,

I want to allow someone to update the data in a database being developed in SQL Developers Edition. The idea is while I'm developing the database the person who's database it is can do the data entry. The data monkey lives no where near me so I cannot keep keep updating a local copy there...

I've tried to set up and connect but the server keeps refusing the connection. So question is... can SQL Developers Edition allow remote connections... and if so, which I hope it can, whats the way to go about setting it up.

Far as I can tell I'm ok in regards to specifying the location of the server, the SQL user account is set up and has access to the database.... can anyone help.

Yes dev edition supports remote connections, you need to go into the
surface area config tool and enable them however|||

Thank you Euan, thank you very much.

Can I also ask... can it work over a secured connection using TCP/IP and what would be involved in setting that up?

|||Whats your definition of secure? SQL Server supports SSL over the wire
is one way of securing it.|||Thats what I wanted to hear. Need to try find out to set it up so I may post again. Thanks.|||Try the security forum, they will be able to help.|||good idea thanks

Remote Connections using SQL Server 2005 Developers Enterprise Edition

I have a problem. I am using the developers version of SQL Server Enterprise edition.

I am trying to run a command in MS command prompt:

Aspnet_regsql -E -S localhost -ssadd -sstype p

After I execute this command, I receive a Name Pipe
error that under the default settings, SQL Server
doesn't allow remote connections. I took some steps
to try to resolve the problem:

1) I googled the interrnet to see if there was any one
else who ran into the same problem and if there was a
quick resolution.

2) I check SQL Server Books on line about SQL server
configuration manager and how to enable remote
connections using Name Pipes and TCP/IP.

3) I used C:\WINDOWS\system32\cliconfg.exe to enable
Name Pipes and TCPIP to be enable on the client.

4) I enabled SQl Server Browser to help me with my
problem

5) I stopped the Database engine, enable local and
remote connections using Name pipes and TCP/IP,then I
restarted the database engine along with SQl server
Agent.

6) I did check SQl Server error logs to see what port
it was listening on , but I thought that SQl Server
was suppose to listen on port 1433 by default, and
Name pipes /SQL/query.

7)I have check the error logs to see what port that SQL Server was listening to
and trying to use the port number in the client config utility. I am still getting the same error.

8) I tried to remove name pipes in the SQL Server Surface Manager and allow local and remote connections using only TCP/IP. I still get the same error. I did stop and restarted the Database Engine.

What steps have I not taken , and what should I do to correct this problem?

Hi,

have you refered below links?

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

http://support.microsoft.com/kb/914277/en-us

Hemantgiri S. Goswami

|||

Hi Hemantgiri,

Thank you for your reply.

I have reviewed the links that you recommended. I have completed most of the steps recommended. I am using a different firewall than Windows, and I will have to contact ZoneAlarm to receive more information about adding exceptions for SQL Server and SQL Server Browser. Usually, ZoneAlarm notify me to allow certain transactions to occur on my machine. I will ask the technical service people at ZoneAlarm why ZoneAlarm firewall was not informing me that it was blocking a remote connection to SQL Server from this machine. When I receive my requested information from ZoneAlarm and apply it to my firewall, I will let you know what happen next.

|||

Hi again,

I have taken the following steps to see if ZoneAlarm was presenting a problem. Please note that I have not heard from ZoneAlarm yet. I removed my wireless network card that I am using to conect to the internet. I disabled my ZoneAlarm and Windows firewall. I followed the steps in the article that was more focused on SQL Server Developer since I am not using SQL Express. I executed the command I mentioned earlier to see if I could connect to SQL Server remotely with out any firewall interference. I could not,and I received the same error. I did look at the other article that was more SQLExpress focused, but I am not sure how I would apply some commands in that article to SQL Server Developer. I have used the SQL Server Surface Configration to enable local and remote settings and using TCP/IP and Name Pipes. It shows that the radio buttons for both are selected, so I know that those choices are selected. As far as selecting a port, I am asking you what would be the SQLCMD command version for SQL Developer? The one for SQL Express is stated in the article, is there a similar one that I can use for SQL Developer? I tried to set the port using clientconfig.exe but that doesn't seem to work.

|||

Hi,

AFAIK their is no difference for the editions , you can perform the same steps.

Hemantgiri S. Goswami

|||

Hi everyone,

I am still looking into this situation. I do not know what to run the SQLCMD for SQL Developer. One article has it for SQL Express : SQLCMD -E -S YourServer\SQLEXPRESS,port #. My question is would I enter SQLCMD -E -S myserver\SQLDEVELOPER,port# or is there another way to state this?

|||

Hi everyone,

I have uninstalled the version of SQL Server 2005 and used an advanced version of SQL Express 2005. I have been successful in configuring remote connections and enabling Named Pipes and TCP/IP using this version. Even though I was not told by the previous version of SQL server 2005, I think that I did not correctly add myself to the Admin group to have the rights to change from local to local /remote connections and enable Named Pipes and TCP/IP. I will test my theory when I install my Standard edition of SQL Server 2005 during May or June.

I would like to thank everyone who replied to my post or who thought hard on a solution to my problem, but have not replied at this time.

Remote Connections using SQL Server 2005 Developers Enterprise Edition

I have a problem. I am using the developers version of SQL Server Enterprise edition.

I am trying to run a command in MS command prompt:

Aspnet_regsql -E -S localhost -ssadd -sstype p

After I execute this command, I receive a Name Pipe
error that under the default settings, SQL Server
doesn't allow remote connections. I took some steps
to try to resolve the problem:

1) I googled the interrnet to see if there was any one
else who ran into the same problem and if there was a
quick resolution.

2) I check SQL Server Books on line about SQL server
configuration manager and how to enable remote
connections using Name Pipes and TCP/IP.

3) I used C:\WINDOWS\system32\cliconfg.exe to enable
Name Pipes and TCPIP to be enable on the client.

4) I enabled SQl Server Browser to help me with my
problem

5) I stopped the Database engine, enable local and
remote connections using Name pipes and TCP/IP,then I
restarted the database engine along with SQl server
Agent.

6) I did check SQl Server error logs to see what port
it was listening on , but I thought that SQl Server
was suppose to listen on port 1433 by default, and
Name pipes /SQL/query.

7)I have check the error logs to see what port that SQL Server was listening to
and trying to use the port number in the client config utility. I am still getting the same error.

8) I tried to remove name pipes in the SQL Server Surface Manager and allow local and remote connections using only TCP/IP. I still get the same error. I did stop and restarted the Database Engine.

What steps have I not taken , and what should I do to correct this problem?

Hi,

have you refered below links?

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

http://support.microsoft.com/kb/914277/en-us

Hemantgiri S. Goswami

|||

Hi Hemantgiri,

Thank you for your reply.

I have reviewed the links that you recommended. I have completed most of the steps recommended. I am using a different firewall than Windows, and I will have to contact ZoneAlarm to receive more information about adding exceptions for SQL Server and SQL Server Browser. Usually, ZoneAlarm notify me to allow certain transactions to occur on my machine. I will ask the technical service people at ZoneAlarm why ZoneAlarm firewall was not informing me that it was blocking a remote connection to SQL Server from this machine. When I receive my requested information from ZoneAlarm and apply it to my firewall, I will let you know what happen next.

|||

Hi again,

I have taken the following steps to see if ZoneAlarm was presenting a problem. Please note that I have not heard from ZoneAlarm yet. I removed my wireless network card that I am using to conect to the internet. I disabled my ZoneAlarm and Windows firewall. I followed the steps in the article that was more focused on SQL Server Developer since I am not using SQL Express. I executed the command I mentioned earlier to see if I could connect to SQL Server remotely with out any firewall interference. I could not,and I received the same error. I did look at the other article that was more SQLExpress focused, but I am not sure how I would apply some commands in that article to SQL Server Developer. I have used the SQL Server Surface Configration to enable local and remote settings and using TCP/IP and Name Pipes. It shows that the radio buttons for both are selected, so I know that those choices are selected. As far as selecting a port, I am asking you what would be the SQLCMD command version for SQL Developer? The one for SQL Express is stated in the article, is there a similar one that I can use for SQL Developer? I tried to set the port using clientconfig.exe but that doesn't seem to work.

|||

Hi,

AFAIK their is no difference for the editions , you can perform the same steps.

Hemantgiri S. Goswami

|||

Hi everyone,

I am still looking into this situation. I do not know what to run the SQLCMD for SQL Developer. One article has it for SQL Express : SQLCMD -E -S YourServer\SQLEXPRESS,port #. My question is would I enter SQLCMD -E -S myserver\SQLDEVELOPER,port# or is there another way to state this?

|||

Hi everyone,

I have uninstalled the version of SQL Server 2005 and used an advanced version of SQL Express 2005. I have been successful in configuring remote connections and enabling Named Pipes and TCP/IP using this version. Even though I was not told by the previous version of SQL server 2005, I think that I did not correctly add myself to the Admin group to have the rights to change from local to local /remote connections and enable Named Pipes and TCP/IP. I will test my theory when I install my Standard edition of SQL Server 2005 during May or June.

I would like to thank everyone who replied to my post or who thought hard on a solution to my problem, but have not replied at this time.

Remote connections to named instances fails on SQL 2005 cluster

I have a new SQL Server 2005 cluster with multiple named instances of SQL
Server 2005 running. From any cluster machine, I can connect to any instanc
e
of SQL Server running in the cluster. From remote machines, I can connect t
o
the default instance of SQL Server, but I can not connect to any named
instances. Help?
+ SQL Browser is running on one physical machine in the cluster
+ Surface Area Configuration has "remote clients" enabled for all instances
+ Named pipes and TCP/IP are enabled
+ DTC is running on the cluster. It is configured to allow network access
on each physical machine.
+ Windows firewall is disabled. Remote machines on same subnet as cluster
machines.
+ Client machine can ping virtual servers?
After waiting a few hours, remote connections now work
?
"Bill Q" wrote:

> I have a new SQL Server 2005 cluster with multiple named instances of SQL
> Server 2005 running. From any cluster machine, I can connect to any insta
nce
> of SQL Server running in the cluster. From remote machines, I can connect
to
> the default instance of SQL Server, but I can not connect to any named
> instances. Help?
> + SQL Browser is running on one physical machine in the cluster
> + Surface Area Configuration has "remote clients" enabled for all instance
s
> + Named pipes and TCP/IP are enabled
> + DTC is running on the cluster. It is configured to allow network access
> on each physical machine.
> + Windows firewall is disabled. Remote machines on same subnet as cluster
> machines.
> + Client machine can ping virtual servers

Remote Connections Refused when server under load

Hi All,
We have a .NET 2.0 web application. Occasionally, we get the following
error below when we are doing performance testing. It is not consistent and
only happens every once in awhile. We are using TCP/IP and only have one
instance of SQL running. We do specify connection pooling in the connection
string. There is virtually nothing happening on the database server - it
only contains a few rows of data to control navigation for the site.
System.Data.SqlClient.SqlException: An error has occurred while establishing
a connection to the server. When connecting to SQL Server 2005, this failure
may be caused by the fact that under the default settings SQL Server does not
allow remote connections. (provider: Named Pipes Provider, error: 40 - Could
not open a connection to SQL Server
This is a different error and not quite what you describe but it might be
involved in your problem. This is from the Books Online topic "Server
Network Configuration."
Connections May Be Forcibly Closed When Running on Windows Server 2003 SP1
When testing scalability with a large number of client connection attempts
to an instance of the SQL Server Database Engine running on Windows Server
2003 Service Pack 1, Windows may drop connections if the requests arrive
faster than SQL Server can service them. This is a security feature of
Windows Server 2003 Service Pack 1, which implements a finite queue for
incoming TCP connection requests. It results in the following error:
ProviderNum: 7, Error: 10054, ErrorMessage: "TCP Provider: An existing
connection was forcibly closed by the remote host ...
To resolve this issue, use the regedit.exe utility to add the following
registry key:
Key Type Name Value
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\
DWORD
SynAttackProtect
00000000
Security Note:
Setting this registry key may expose the server to a SYN flood,
denial-of-service attack. Add this registry value only if necessary and with
an understanding of the security risks. Remove this registry value when
testing is complete.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bill P" <Bill P@.discussions.microsoft.com> wrote in message
news:2D3D349D-EE1C-4945-82FE-D3717AD02E2F@.microsoft.com...
> Hi All,
> We have a .NET 2.0 web application. Occasionally, we get the following
> error below when we are doing performance testing. It is not consistent
> and
> only happens every once in awhile. We are using TCP/IP and only have one
> instance of SQL running. We do specify connection pooling in the
> connection
> string. There is virtually nothing happening on the database server - it
> only contains a few rows of data to control navigation for the site.
> System.Data.SqlClient.SqlException: An error has occurred while
> establishing
> a connection to the server. When connecting to SQL Server 2005, this
> failure
> may be caused by the fact that under the default settings SQL Server does
> not
> allow remote connections. (provider: Named Pipes Provider, error: 40 -
> Could
> not open a connection to SQL Server
|||Rick,
Thank you for the reply. It very well could have something to do with this.
I am going to give it a try. It may be a few days before I find anything
out since this happens only once in a while.
Bill Portman
"Rick Byham, (MSFT)" wrote:

> This is a different error and not quite what you describe but it might be
> involved in your problem. This is from the Books Online topic "Server
> Network Configuration."
> Connections May Be Forcibly Closed When Running on Windows Server 2003 SP1
> When testing scalability with a large number of client connection attempts
> to an instance of the SQL Server Database Engine running on Windows Server
> 2003 Service Pack 1, Windows may drop connections if the requests arrive
> faster than SQL Server can service them. This is a security feature of
> Windows Server 2003 Service Pack 1, which implements a finite queue for
> incoming TCP connection requests. It results in the following error:
> ProviderNum: 7, Error: 10054, ErrorMessage: "TCP Provider: An existing
> connection was forcibly closed by the remote host ...
> To resolve this issue, use the regedit.exe utility to add the following
> registry key:
> Key Type Name Value
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\
> DWORD
> SynAttackProtect
> 00000000
> Security Note:
> Setting this registry key may expose the server to a SYN flood,
> denial-of-service attack. Add this registry value only if necessary and with
> an understanding of the security risks. Remove this registry value when
> testing is complete.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Bill P" <Bill P@.discussions.microsoft.com> wrote in message
> news:2D3D349D-EE1C-4945-82FE-D3717AD02E2F@.microsoft.com...
>

Remote Connections Refused when server under load

Hi All,
We have a .NET 2.0 web application. Occasionally, we get the following
error below when we are doing performance testing. It is not consistent and
only happens every once in awhile. We are using TCP/IP and only have one
instance of SQL running. We do specify connection pooling in the connection
string. There is virtually nothing happening on the database server - it
only contains a few rows of data to control navigation for the site.
System.Data.SqlClient.SqlException: An error has occurred while establishing
a connection to the server. When connecting to SQL Server 2005, this failur
e
may be caused by the fact that under the default settings SQL Server does no
t
allow remote connections. (provider: Named Pipes Provider, error: 40 - Could
not open a connection to SQL ServerThis is a different error and not quite what you describe but it might be
involved in your problem. This is from the Books Online topic "Server
Network Configuration."
Connections May Be Forcibly Closed When Running on Windows Server 2003 SP1
When testing scalability with a large number of client connection attempts
to an instance of the SQL Server Database Engine running on Windows Server
2003 Service Pack 1, Windows may drop connections if the requests arrive
faster than SQL Server can service them. This is a security feature of
Windows Server 2003 Service Pack 1, which implements a finite queue for
incoming TCP connection requests. It results in the following error:
ProviderNum: 7, Error: 10054, ErrorMessage: "TCP Provider: An existing
connection was forcibly closed by the remote host ...
To resolve this issue, use the regedit.exe utility to add the following
registry key:
Key Type Name Value
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\Tcpip\Parameters\
DWORD
SynAttackProtect
00000000
Security Note:
Setting this registry key may expose the server to a SYN flood,
denial-of-service attack. Add this registry value only if necessary and with
an understanding of the security risks. Remove this registry value when
testing is complete.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bill P" <Bill P@.discussions.microsoft.com> wrote in message
news:2D3D349D-EE1C-4945-82FE-D3717AD02E2F@.microsoft.com...
> Hi All,
> We have a .NET 2.0 web application. Occasionally, we get the following
> error below when we are doing performance testing. It is not consistent
> and
> only happens every once in awhile. We are using TCP/IP and only have one
> instance of SQL running. We do specify connection pooling in the
> connection
> string. There is virtually nothing happening on the database server - it
> only contains a few rows of data to control navigation for the site.
> System.Data.SqlClient.SqlException: An error has occurred while
> establishing
> a connection to the server. When connecting to SQL Server 2005, this
> failure
> may be caused by the fact that under the default settings SQL Server does
> not
> allow remote connections. (provider: Named Pipes Provider, error: 40 -
> Could
> not open a connection to SQL Server|||Rick,
Thank you for the reply. It very well could have something to do with this.
I am going to give it a try. It may be a few days before I find anything
out since this happens only once in a while.
Bill Portman
"Rick Byham, (MSFT)" wrote:

> This is a different error and not quite what you describe but it might be
> involved in your problem. This is from the Books Online topic "Server
> Network Configuration."
> Connections May Be Forcibly Closed When Running on Windows Server 2003 SP1
> When testing scalability with a large number of client connection attempts
> to an instance of the SQL Server Database Engine running on Windows Server
> 2003 Service Pack 1, Windows may drop connections if the requests arrive
> faster than SQL Server can service them. This is a security feature of
> Windows Server 2003 Service Pack 1, which implements a finite queue for
> incoming TCP connection requests. It results in the following error:
> ProviderNum: 7, Error: 10054, ErrorMessage: "TCP Provider: An existing
> connection was forcibly closed by the remote host ...
> To resolve this issue, use the regedit.exe utility to add the following
> registry key:
> Key Type Name Value
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\Tcpip\Parameters\
> DWORD
> SynAttackProtect
> 00000000
> Security Note:
> Setting this registry key may expose the server to a SYN flood,
> denial-of-service attack. Add this registry value only if necessary and wi
th
> an understanding of the security risks. Remove this registry value when
> testing is complete.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Bill P" <Bill P@.discussions.microsoft.com> wrote in message
> news:2D3D349D-EE1C-4945-82FE-D3717AD02E2F@.microsoft.com...
>

Remote Connections in 2005

This has probably been answered before, but...
I have a local SQL Server 2005 instance running, and I would like to
have another user on my network connect to this instance. However,
when he tries to connect, he always receives the same error message:
"An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error 28: - Server
doesnt' support requested protocol)"
So, I checked the properties for the server, and under the connections
tab the allow remote connection box is checked.
Any clue where to look next?
Thanks In Advancechris.teter@.gmail.com wrote:
> This has probably been answered before, but...
> I have a local SQL Server 2005 instance running, and I would like to
> have another user on my network connect to this instance. However,
> when he tries to connect, he always receives the same error message:
> "An error has occured while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (provider: SQL Network Interfaces, error 28: - Server
> doesnt' support requested protocol)"
> So, I checked the properties for the server, and under the connections
> tab the allow remote connection box is checked.
> Any clue where to look next?
> Thanks In Advance
>
is tcp and/or named pipes enabled - they are disabled by default

Remote Connections in 2005

This has probably been answered before, but...
I have a local SQL Server 2005 instance running, and I would like to
have another user on my network connect to this instance. However,
when he tries to connect, he always receives the same error message:
"An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error 28: - Server
doesnt' support requested protocol)"
So, I checked the properties for the server, and under the connections
tab the allow remote connection box is checked.
Any clue where to look next?
Thanks In Advancechris.teter@.gmail.com wrote:
> This has probably been answered before, but...
> I have a local SQL Server 2005 instance running, and I would like to
> have another user on my network connect to this instance. However,
> when he tries to connect, he always receives the same error message:
> "An error has occured while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (provider: SQL Network Interfaces, error 28: - Server
> doesnt' support requested protocol)"
> So, I checked the properties for the server, and under the connections
> tab the allow remote connection box is checked.
> Any clue where to look next?
> Thanks In Advance
>
is tcp and/or named pipes enabled - they are disabled by default

Remote Connections in 2005

This has probably been answered before, but...
I have a local SQL Server 2005 instance running, and I would like to
have another user on my network connect to this instance. However,
when he tries to connect, he always receives the same error message:
"An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: SQL Network Interfaces, error 28: - Server
doesnt' support requested protocol)"
So, I checked the properties for the server, and under the connections
tab the allow remote connection box is checked.
Any clue where to look next?
Thanks In Advance
chris.teter@.gmail.com wrote:
> This has probably been answered before, but...
> I have a local SQL Server 2005 instance running, and I would like to
> have another user on my network connect to this instance. However,
> when he tries to connect, he always receives the same error message:
> "An error has occured while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (provider: SQL Network Interfaces, error 28: - Server
> doesnt' support requested protocol)"
> So, I checked the properties for the server, and under the connections
> tab the allow remote connection box is checked.
> Any clue where to look next?
> Thanks In Advance
>
is tcp and/or named pipes enabled - they are disabled by default

Remote connections error SQL Server 2005

I am getting "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) " when I access my application
But sql server is found to be running
what may be the reason
can any one guide me on thisEverything you could possibly want to know on connectivity issues:

http://blogs.msdn.com/sql_protocols.../22/506607.aspx

Brett
Perfect Computing, Inc

Remote Connections error

While trying to transfer my website project to another computer I am encountering an error when tryng to run the solution. It gives me a "Does not allow remote connections". Why is this when on the original computer everything worked fine.

Walter

Does the error has anything to do with SQL server?

This error is common when there is a connection problem to SQL server.

Verify your connection string.Make sure SQL server is running. Make sure you are able to connect to the database.

Regards,

David

|||

I think I had an error similar to this before and therefore I'll assume that your problem is like mine and is associated with SQL Server. (I thinkneutrino is of the same persuasion.)

Now if I understand you correctly, you're trying to run a project on one pc and connect to a database on another pc. Therefore I think the problem is that SQL Server is rejecting your remote connection because it's not configured to accept it! You need to allow remote connections to that server.

See this article (How to configure SQL Server 2005 to allow remote connections ).

Now.. if you're problem isn't related to SQL Server ... well.. Ignore all of the above.

Remote Connections Enabled, but I still get error that Remote is not configured - Sql 2005

Fellow Devs,

I have an instance of SQL Server Express 2005 running on another box and I have Remote Connections enabled over both TCP/IP and Named Pipes, but on my other box I keep getting the error that the server does not accept Remote Connections.

Any ideas why this might be happening? Is there some other configuration?

start server configuration manager

click on protocols > TCP/IP and properties

go to IP addresses and under IPALL remove everythink from TCP dynamic port , under TCP Port enter port you want to use like 1433

save all changes restart service and should work

|||and if you have windows firewall on you have to allow to accept connection on this port|||

I don't see that option in my server configuration manager. I just see "File Server", "Application Server" and "Remote Access/VPN Server". Where do I modify thse settings?

Thanks!

|||

1) open SQL Server configuration manager
2) on the left under "Sql server 2005 network configuration" click on protocols for SQL
3) on right side right click TCP/IP > properties and tab IP addresses

|||

I was having the same problem and I followed your instructions, but now VS doesn't even detect the sql server. Any solutions?

Thanks.

|||

Swackhammer1:

I was having the same problem and I followed your instructions, but now VS doesn't even detect the sql server. Any solutions?

Thanks.

If VS is not detecting the SQL Server it may mean your SQL Server service maybe off. You may want to download the advanced version from the link below if not first get the eval and then spend $33 to get the developer edition. Hope this helps.

http://msdn.microsoft.com/vstudio/express/sql/compare/default.aspx

|||

looool what kind of solution is that ? doesn't work pay $33.

here is an article explaining step by step what you can do to enable remote connections - pretty much same idea i gave you , but when you will follow it must work

|||You have given the original poster very low level usually not adviced connection to SQL Server and it is not working, Express is best used for small company intranet hosted application nothing more. I have used SQL Server since 1998 and I have not got the need to connect to SQL Server on those layers. So mine will cost after 180 days but it is pain free.|||

i saw many of your posts and i KNOW that you work with SQL for long time and you know about it much more than i do.
I agree that SQL express is perfect for small project, intranet & for development and i believe that is what this person needs - when someone ask how to enable remote connections in SQL express- my guess would be that he/she doesn't work for BIG corporation that has billions of transaction / day

My point is that there is no reason to buy anything cos EXPRESS edition can work perfectly all you need is to spend few minutes with it and make the setup + maybe change firewall settings.

|||Yes but connecting to SQL Server through TCP port is not good advice because there is also the known UDP port and two others Microsoft admit to have reserved but only give to customers as needed which opens you up to known security issues. Microsoft was like Oracle selling the developer edition for hundreds we asked for the lower price for access and got it. Fighting with Express eats into development time.|||Ok. Here's the thing. I'm using SQL EXPRESS and VS 2005 on my machine, but the company I'm developing for has the full SQL SERVER 2005. Before I changed the tcp/ip setting, I could see my server in VS. After changing the settings though, it no longer shows up. I do have the service running. I double checked.|||OK. I decided to get the trial version of SQL SERVER 2005 for now. Let's see how that works out.|||

The links below from Microsoft covers most of what you need and some of what I have been trying to explain in details. Hope this helps.

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

|||

Caddre - very good links :)

BTWSwackhammer1 where in VS you can not see your SQL server ? in databse explorer when you click "add connection" ? if that is the problem just enter ".\SQLEXPRESS" in server name field or IP address of you server or "YOUR_COMPUTER_NEME\SQLEXPRESS"

Remote Connections

Hi,

I'm having problems setting up remote connections in SQL Server 2005 Dev. I can't see what I've done wrong maybe some else can. I'm trying to connect to the database through a .NET 2005 application which uses table adapters, the software works fine when using trusted connections.

I've turned on TCP/IP remote connections and I restarted the SQL Server instance. I've added a SQL login user account and SQL authentication is on. I've given this account access to the server and database and granted CONNET, SELECT, UPDATE, etc access rights, I've even made them admin and owner etc and I've opened the default ports in the firewall.

I'm using a connection string in this format

"Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=pubs;User ID=sa;Password=fgdgfdgs;"

Every time I connect the error message says the targed machine actively refused the connection.

Anyone got an idea or a checklist of how to set up remotre connections ?

Thanks

I've got it to work!!

The connection string needed the SQL Instance, doh! Learned a lesson there but that's a result.

However I cannot specify a port and have to use the default. I've tried...

Data Source=190.190.200.100,1433\SQLInstance

Data Source=190.190.200.100\SQLInstance,1433

and neither are working, not a problem but any idea.

remote connection to 2005 express: Login Failed?

I followed the steps outlined in a blog I found to setup SS2005 express for remote connections. Everything appeared to go smooth until I actually tried to logon ;)

I have Sql Server 2005 Express installed on my WinXP PRO machine at home (no domain). I have opened the ports on the firewall, etc.

When I try and login from the SQLCMD command line tool I get a Login Failed error. Here is the connection string that I'm trying to use:
SQLCMD -S **.***.**.*\SQLEXPRESS -U Steve -P MyPassword

The error:
Login failed for user 'Steve'.

When I use Management Studio Express on the same machine running Sql Server, it shows the User name: NEVERSTILL\Steve

'NEVERSTILL' is the name of my computer.

If I try and use that same username with a remote connection I get the same error.

I have googled for the error and msg code, but nothing fitting my situation is coming up.

Anyone have any ideas for me?

Check the error log and please post the error state that shows there before the login failed message.

Thanks
Laurentiu

Remote connection setup

Hi, new to remote SQL Connections. Hoping someone can help with a definitive tutorial for setting up remote connections in SQL2005. I have a SQLExpress installation at our office behind an ADSL router. I want to connect with SQL Server Management Studio from my home PC, which is also behind an ADSL router. What settings do I have to alter, both loal amd remote.

regards
OK fixed it myself. Nothing like trial and error to overcome a problem :)

Remote connection refused when creating ODBC connection to SQL Server 2005

When I create a new odbc connection to a SQL server 2005 Db I get a failure telling me dat de SQL server does not allow remote connections.

How can I allow the server to allow this.

Any help appreciated

regards

I would recommend looking at the following post, hopefully it already contains the answer to your issue:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=297514&SiteID=1

If the information here is not enough to fix your problem, let us know, we will be glad to help.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine