Tuesday, 27 March 2012
connect to SQL 2005 fails
Standard Edition. After the reboot to install MS patches Tuesday AM, it qui
t
accepting any SQL Connections. Prior to the reboot it was accepting
connections and working as we expected it to. I've worked with the Surface
Area configuration tool to make sure it allows connections. We've backed ou
t
the patches. After doing this, we've rebooted the box. Yet, we still are
unable to connect.
The primary error message we are seeing is "A connection was successfully
established with the server, but then an error occurred during the pre-login
handshake. (provider: Shared Memory Provider, error: 0 - No process is on th
e
other end of the pipe.) (type SqlException)"
I am also seeing "A connection was successfully established with the server,
but then an error occurred during the pre-login handshake. (provider: Shared
Memory Provider, error: 0 - No process is on the other end of the pipe.)
(Microsoft SQL Server, Error: 233)"
In addition to SQL2005, we have TFS, Windows SharePointServices, and
Reporting Services running on the machine. They are all experiencing
variations on the same message and unable to connect.
Thanks for the assistance.
JeffSounds like the SQL Server service didn't restart after the reboot. Check
the log at:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG
to see if there is a problem with SQL restarting. If that doesn't work, try
using the SQL Server Configuration Manager tool to enable the TCP/IP
protocol on the client and server to see if the problem is isolated to named
pipes.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Jeff in Alaska" <Jeff in Alaska@.discussions.microsoft.com> wrote in message
news:577AE98A-4170-4C15-859B-1FAA0D89A658@.microsoft.com...
> We have a test SQL 2005 (Developer Edition) machine on Windows2003 SP1
> Standard Edition. After the reboot to install MS patches Tuesday AM, it
> quit
> accepting any SQL Connections. Prior to the reboot it was accepting
> connections and working as we expected it to. I've worked with the
> Surface
> Area configuration tool to make sure it allows connections. We've backed
> out
> the patches. After doing this, we've rebooted the box. Yet, we still are
> unable to connect.
> The primary error message we are seeing is "A connection was successfully
> established with the server, but then an error occurred during the
> pre-login
> handshake. (provider: Shared Memory Provider, error: 0 - No process is on
> the
> other end of the pipe.) (type SqlException)"
> I am also seeing "A connection was successfully established with the
> server,
> but then an error occurred during the pre-login handshake. (provider:
> Shared
> Memory Provider, error: 0 - No process is on the other end of the pipe.)
> (Microsoft SQL Server, Error: 233)"
> In addition to SQL2005, we have TFS, Windows SharePointServices, and
> Reporting Services running on the machine. They are all experiencing
> variations on the same message and unable to connect.
> Thanks for the assistance.
> Jeff|||SQL Server successfully restarted. The SQLFT*.LOG and ERRORLOG files both
indicate a successful restart. On the SQL Server Confiruation Manager tool
"Shared Memory", "Named Pipes" and "TCP/IP" are all enabled. "TCP/IP" is
enabled to listen on all IP Addresses. The machine only has one IP that it
is listening to. The protocol order is Shared Memory, TCP/IP, and Named
Pipes.
When looking at the Process view and the "System Services" view, both
indicate SQL Server is up and operational. the only SQL related tool that
isn't operational is SQL Server Agent and it is failing due to same problems
that cause other apps trying to connect to the SQL Server to fail.
Jeff
"Roger Wolter[MSFT]" wrote:
> Sounds like the SQL Server service didn't restart after the reboot. Check
> the log at:
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG
> to see if there is a problem with SQL restarting. If that doesn't work, t
ry
> using the SQL Server Configuration Manager tool to enable the TCP/IP
> protocol on the client and server to see if the problem is isolated to nam
ed
> pipes.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Jeff in Alaska" <Jeff in Alaska@.discussions.microsoft.com> wrote in messa
ge
> news:577AE98A-4170-4C15-859B-1FAA0D89A658@.microsoft.com...
>
>|||I can connect easily using C# & ADO.NET on standalone programs.
I am trying to connect from a web site program under .NET 1.1 VS 7 and
always get
Login failed for user 'LANDON\ASPNET'.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information abou
t
the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Login failed for user
'LANDON\ASPNET'.
Source Error:
Line 46: private void Page_Load(object sender, System.EventArgs e)
Line 47: {
Line 48: sqlConnection1.Open();
Line 49: ds = new DataSet();
Line 50: daAttendees = new SqlDataAdapter(
Source File: c:\inetpub\wwwroot\pcswebapp2\webform1.aspx.cs Line: 48
having signed in under IE6 using:
http://localhost/PCSWebApp2/WebForm1.aspx
I've tried everything to fix the problem;
"Jeff in Alaska" wrote:
[vbcol=seagreen]
> SQL Server successfully restarted. The SQLFT*.LOG and ERRORLOG files both
> indicate a successful restart. On the SQL Server Confiruation Manager too
l
> "Shared Memory", "Named Pipes" and "TCP/IP" are all enabled. "TCP/IP" is
> enabled to listen on all IP Addresses. The machine only has one IP that i
t
> is listening to. The protocol order is Shared Memory, TCP/IP, and Named
> Pipes.
> When looking at the Process view and the "System Services" view, both
> indicate SQL Server is up and operational. the only SQL related tool that
> isn't operational is SQL Server Agent and it is failing due to same proble
ms
> that cause other apps trying to connect to the SQL Server to fail.
> Jeff
> "Roger Wolter[MSFT]" wrote:
>|||"Landon Kelsey" <landonmkelsey@.hotmail.com> wrote in message
news:AC0C18EB-405E-4C5E-8148-FBAA18C12A46@.microsoft.com...[vbcol=seagreen]
>I can connect easily using C# & ADO.NET on standalone programs.
> I am trying to connect from a web site program under .NET 1.1 VS 7 and
> always get
> Login failed for user 'LANDON\ASPNET'.
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about
> the error and where it originated in the code.
> Exception Details: System.Data.SqlClient.SqlException: Login failed for
> user
> 'LANDON\ASPNET'.
> Source Error:
>
> Line 46: private void Page_Load(object sender, System.EventArgs e)
> Line 47: {
> Line 48: sqlConnection1.Open();
> Line 49: ds = new DataSet();
> Line 50: daAttendees = new SqlDataAdapter(
>
> Source File: c:\inetpub\wwwroot\pcswebapp2\webform1.aspx.cs Line: 48
> having signed in under IE6 using:
> http://localhost/PCSWebApp2/WebForm1.aspx
> I've tried everything to fix the problem;
>
>
>
> "Jeff in Alaska" wrote:
>
Is there any reason you've hijacked several other OP's posts instead of
posting your own message?
Star Fleet Admiral Q @. your service!
Google is your friend!
http://www.google.com|||this problem appears in more than one post so why dilute the
knowledge/proliferate the problem by starting yet another post?
I've noticed that good answewrs have been given in one of the posts.
Do you expect the answerer to search for every post of the problem and
answer it?
"Admiral Q" wrote:
> "Landon Kelsey" <landonmkelsey@.hotmail.com> wrote in message
> news:AC0C18EB-405E-4C5E-8148-FBAA18C12A46@.microsoft.com...
>
> Is there any reason you've hijacked several other OP's posts instead of
> posting your own message?
> --
> Star Fleet Admiral Q @. your service!
> Google is your friend!
> http://www.google.com
>
>|||"Landon Kelsey" <landonmkelsey@.hotmail.com> wrote in message
news:8D5862C0-755A-4523-81B4-CBF7A69686D6@.microsoft.com...[vbcol=seagreen]
> this problem appears in more than one post so why dilute the
> knowledge/proliferate the problem by starting yet another post?
> I've noticed that good answewrs have been given in one of the posts.
> Do you expect the answerer to search for every post of the problem and
> answer it?
> "Admiral Q" wrote:
>
Guess you'll find out you won't get many of your own questions asked if you
keep hijacking other threads - as soon as you learn proper neticate, you'll
get the results you desire, but until then, you'll be living on other's
crumbs.
Star Fleet Admiral Q @. your service!
Google is your friend!
http://www.google.com|||Hey, u had a question and then u found your self arguing on some post
made by a person who got lost maybe (with the mind). I have the same
problem described pretty good in the first post. And I can't solve it.
I really don't want to reinstall my OS or even Sql Server 2005. If by
some miracle someone knows about the problem "give me a call".
Here's the problem described by sql server:
Code:
--
===================================
Cannot connect to NELUSAN\SQLSERVER2005.
===================================
A connection was successfully established with the server, but then an error
occurred during the pre-login handshake. (provider: Shared Memory Provider,
error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Dat
a Provider)
For help, click: http://go.microsoft.com/fwlink?Prod...33&LinkId=20476
Server Name: NELUSAN\SQLSERVER2005
Error Number: 233
Severity: 20
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exceptio
n, Boolean breakConnection)
at System.Data.SqlClient.TdsParser. ThrowExceptionAndWarning(TdsParserStateO
b
ject stateObj)
at System.Data.SqlClient.TdsParser.ConsumePreLoginHandshake(Boolean encrypt,
Boolean trustServerCert, Boolean& marsCapable)
at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Bool
ean& failoverDemandDone, String host, String failoverPartner, String protoco
l, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt,
Boolean trustServerCert,
Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnect
ion owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIden
tity identity, SqlConnectionString connectionOptions, Object providerInfo, S
tring newPassword, SqlConnection owningObject, Boolean redirectedUserInstanc
e)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionO
ptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConne
ction owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(Db
Connection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection o
wningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection o
uterConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExpl
orer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThrea
dUser()
--
nelusan
---
nelusan's Profile: http://www.dbtalk.net/m400
View this thread: http://www.dbtalk.net/t300721
Sunday, 11 March 2012
Connect fails: Error 4064, Can not open user default DB
I never figured it out after many hours of exploring every SQL interface I could find, changing web.config's connection string, and editing the DotNetNuke ODBC Data Source. At one point I was able to intermittently sign in to the SQL Server Management Studio (but never to get DotNetNuke site to connect to the DB).
Late in this process I gave up, decided to reinstall DotNetNuke from scratch, and removed that directory with my default database. Maybe one isn't supposed to do this, but I did it and suspect that is the reason for the error message in the title of this post. I don't see a way to login in as another user either at this point.
If it is indeed possible for one to delete one's default database - and if so - is there any solution except a complete (multi-hour on my old system) reinstall of SQL Server?
If I try to connect using SQL user SA (user names are case insensative, right?!), I get error 18452: "The user is not associated with a trusted SQL Server Connection."
You can change default database for a user using ALTER LOGIN. You can check your current settings for all users using sys.server_principals.
As far as being unable to connect using ‘sa’ credentials, verify that you have mixed mode authentication enabled. If you do not that might explain why you are getting trusted connection error for ‘sa’.
This may also be affecting your inability to connect to the portal.
Overall, it is recommended that you upgrade to CTP 15 (build 1187), so reinstall might be the cleanest option. Make sure you select ‘mixed mode auth’ and set ‘sa’ password during setup.
Regards,
Boris.
|||Boris B is right , I had the same problem when i started using it and it turned out to be the default database i hat for the specific login .Connect fails: Error 4064, Can not open user default DB
I never figured it out after many hours of exploring every SQL interface I could find, changing web.config's connection string, and editing the DotNetNuke ODBC Data Source. At one point I was able to intermittently sign in to the SQL Server Management Studio (but never to get DotNetNuke site to connect to the DB).
Late in this process I gave up, decided to reinstall DotNetNuke from scratch, and removed that directory with my default database. Maybe one isn't supposed to do this, but I did it and suspect that is the reason for the error message in the title of this post. I don't see a way to login in as another user either at this point.
If it is indeed possible for one to delete one's default database - and if so - is there any solution except a complete (multi-hour on my old system) reinstall of SQL Server?
If I try to connect using SQL user SA (user names are case insensative, right?!), I get error 18452: "The user is not associated with a trusted SQL Server Connection."
You can change default database for a user using ALTER LOGIN. You can check your current settings for all users using sys.server_principals.
As far as being unable to connect using ‘sa’ credentials, verify that you have mixed mode authentication enabled. If you do not that might explain why you are getting trusted connection error for ‘sa’.
This may also be affecting your inability to connect to the portal.
Overall, it is recommended that you upgrade to CTP 15 (build 1187), so reinstall might be the cleanest option. Make sure you select ‘mixed mode auth’ and set ‘sa’ password during setup.
Regards,
Boris.
|||Boris B is right , I had the same problem when i started using it and it turned out to be the default database i hat for the specific login .Wednesday, 7 March 2012
Confused...SA Account
I have a two node cluster with SQL2000 SP3. When the node1 fails over to
node2, the SQL Server Agent fails. The log file says "Login Failed for user
'sa'" I don't understand how the SA account can fail on node2 and not on
node1. Can anyone shed some light on this and possibly how to resolve the
issue.
Thank You
Marc
What security account context is the SQL Agent running under? Is it a domain account and does it have adequate permissions/rights on both nodes?
|||Hi Stephen
SQL security is set for "SQL Server and Windows" and the service account is
in the Domain Admins group. Same service account is used for both nodes.
Regards
Marc
"Stephen Strong" <anonymous@.discussions.microsoft.com> wrote in message
news:39A963C4-A818-487F-8B10-C38CC58715FA@.microsoft.com...
> What security account context is the SQL Agent running under? Is it a
domain account and does it have adequate permissions/rights on both nodes?
|||Is the SQL Server Agent startup account a member of the local admin group
on both nodes. If you are using SQL Server authentication for SQL Server
Agent to connect to SQL Server then the SQL Server Agent startup account
has to be a local Admin.
You can check the SQL Agent connection properties by right clicking on SQL
Server Agent - Properties - Connection and see how the connection to SQL
Server is set up.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks Guys
As it turns out, one of our programmers changed the authentication method to
Windows rather than SQL. I changed it back and all is well.
Regards
Marc
"Marc" <Marc@.nospam.com> wrote in message
news:%23u4AZPJJEHA.2736@.TK2MSFTNGP12.phx.gbl...
> Hi
> I have a two node cluster with SQL2000 SP3. When the node1 fails over to
> node2, the SQL Server Agent fails. The log file says "Login Failed for
user
> 'sa'" I don't understand how the SA account can fail on node2 and not on
> node1. Can anyone shed some light on this and possibly how to resolve the
> issue.
> Thank You
> Marc
>
Sunday, 12 February 2012
Configuring a remote server as a subscription server
agent fails announcing that: "The remote server is not defined as a
subscription server (The error number is 14010)".
Here are more details:
The first server (publisher & distributor) has SQL Server enterprise edition
installed using SQL Server authentication. The IP address for this server is
192.168.62.2 and the subnet mask is 255.255.255.0
The second server (subscriber) the same as the publisher however the IP
address is 192.168.64.2 with a subnet mask of 255.255.255.0.
Note that there is no domain connectiong the two server!
I have regisrtered the subscriber at the publisher and cretaed the merge
replciation successfully. However the merge agent fails as specified above!
Thanks in advance,
Shehab.
On the publisher go to Tools, Replication, Configure Publisher, Subscribers,
and Distribution, click on the Subscribers tab and add it there.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Shehab Kamal" <ShehabKamal@.discussions.microsoft.com> wrote in message
news:1BB0A342-B704-4222-B617-B6F70638AC3C@.microsoft.com...
> I'm trying to do a merge replciation between two servers however the merge
> agent fails announcing that: "The remote server is not defined as a
> subscription server (The error number is 14010)".
> Here are more details:
> The first server (publisher & distributor) has SQL Server enterprise
> edition
> installed using SQL Server authentication. The IP address for this server
> is
> 192.168.62.2 and the subnet mask is 255.255.255.0
> The second server (subscriber) the same as the publisher however the IP
> address is 192.168.64.2 with a subnet mask of 255.255.255.0.
> Note that there is no domain connectiong the two server!
> I have regisrtered the subscriber at the publisher and cretaed the merge
> replciation successfully. However the merge agent fails as specified
> above!
> Thanks in advance,
> Shehab.
Friday, 10 February 2012
Configure Report server
When I say start it takes a while and then fails.
What's wrong?
ThanksAnd here is the detailed info:
System.ServiceProcess.TimeoutException: Time out has expired and the
operation has not been completed.
at
System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus
desiredStatus, TimeSpan timeout)
at
ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean
start)
"Mark Goldin" <mgoldin@.ufandd.com> wrote in message
news:%23dVZCzSbFHA.2884@.tk2msftngp13.phx.gbl...
>I have Server status in red.
> When I say start it takes a while and then fails.
> What's wrong?
> Thanks
>