A domain error occurred. from SQL statement, only when above 10

Attempting to run a query that is looping through cursor, anything over
choosing the TOP 10 from a table for the cursor results in a
"A domain error occurred."
error message? below 10 all runs fine. What is this message caused by?It usually happens when performing mathematical functions
and using values outside of acceptable ranges.
-Sue
On Thu, 20 Nov 2003 11:51:01 -0600, "Kory"
<kory@.removeme-mlsc.com> wrote:
>Attempting to run a query that is looping through cursor, anything over
>choosing the TOP 10 from a table for the cursor results in a
>"A domain error occurred."
>error message? below 10 all runs fine. What is this message caused by?
>

A connection was successfully established with the server, but then an error occurred during the

Hi All,

When i'm trying to access a sql server from a different pc,i'm getting the following error..

Plz help me how to fix this..

A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (.Net SqlClient Data Provider)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=64&LinkId=20476

Server Name: 10.11.144.145
Error Number: 64
Severity: 20
State: 0

Program Location:

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Regards,

Sailendra.

Hi ,

This problem generally occurs in windows 2003 server with service pack 1.

Solution is :-

Steps

<!--[if !supportLists]-->1. <!--[endif]-->regedit

<!--[if !supportLists]-->2. <!--[endif]-->HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\\Parameters

<!--[if !supportLists]-->3. <!--[endif]-->Add Dword value with name “SynAttackProtect” and set value “00000000 “in hexdecimal.

Regards
Rajesh

A connection was successfully established with the server, but then an error occurred during the

I have just installed MS SQL Server 2005 Express edition along with the SSMSE. I am using windows authentication. When I open SSMSE it connects me to a 'local instance' of the server. From there I right click on Database and select to add a new Database and I get the error above. I think I only need to allow local connections to the engine but I have tried allowing remote conections with all varations of named pipes and TCP/IP. I am running on Windows XP SP2 (home).Hi,

could you please post the whole error message ?

You might take a look at this site in the meantime: http://blogs.msdn.com/sql_protocols/Default.aspx?p=2

HTH; Jens K. Suessmeyer.

http://www.sqlserver2005.de

A connection was successfully established with the server, but then an error occurred during the

Hi All,

When i'm trying to access a sql server from a different pc,i'm getting the following error..

Plz help me how to fix this..

A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (.Net SqlClient Data Provider)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=64&LinkId=20476

Server Name: 10.11.144.145
Error Number: 64
Severity: 20
State: 0

Program Location:

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Regards,

Sailendra.

Hi ,

This problem generally occurs in windows 2003 server with service pack 1.

Solution is :-

Steps

<!--[if !supportLists]-->1. <!--[endif]-->regedit

<!--[if !supportLists]-->2. <!--[endif]-->HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\\Parameters

<!--[if !supportLists]-->3. <!--[endif]-->Add Dword value with name “SynAttackProtect” and set value “00000000 “in hexdecimal.

Regards
Rajeshsql

A connection was successfully established with the server, but then an error occurred during the

I get the following error when trying to view my page.

Can someone please help me with this error. What does it mean and what is the solution to it? Here is the complete error message. -

A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)

See following post:

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

HTH

Ming.

|||

Please check these two posts see whether it solves your problem

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

Otherwise, please check your errorlog file see if there is any abnormal.

A connection was successfully established with the server, but then an error occurred during

I get the following error when trying to view my page.

Can someone please help me with this error. What does it mean and what is the solution to it? Here is the complete error message. -

A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)

See following post:

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

HTH

Ming.

|||

Please check these two posts see whether it solves your problem

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

Otherwise, please check your errorlog file see if there is any abnormal.

A connection was successfully established with the server, but then an error occurred duri

Hi,

I am having such a problem. I have SQL Express installed on the windows 2003 server and originally I installed instance1 of SQL Server 2005. When I installed Instance1, I remember having problems with remotely connecting to that instance1, but somehow I fixed it. Now I installed instance2 and I started having remote connection issues again with that instance2. I am able to connect to instance1 but not instance2. I checked settings for both instances and they look identical.

I turned firewall off for now. I checked TCP settings using surface area configuration (allowing both local and remote connections). I turned off VIA protocol. I specified TCP properties to use dynamic port for that instance2.

In the sql native client configuration I have the following order#: 1. Shared memory, 2. tcp, 3. np, 4. VIA(Disabled). TCP is configured to use 1433.

I have no clue about what is going on. Sometimes I am able to connect remotely and sometimes I get the following error:

"A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (.Net SqlClient Data Provider)."

When I connect locally - everything connects fine. File sharing is also checked, it works etc...

Thanks for help!!!

GK

I just noticed that I was able to connect from different computer on the different network.

What kind of account are you trying to connect with, Windows or SQL? I'm guessing it is trying to do a windows authentication but the remote computer isn't authenticated to the domain.

|||

No. It is SQL server account. I connect remotely to the sql server on different network.

Thanks,
GK

|||

You say it only happens sometimes? It sounds like a timeout issue. Changing the connection timeout property in the connection string will temporarily solve your problem but it sounds like there is a greater underlying network problem between the client and sql server.

Connection timeout and other connection string properties:http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring(VS.71).aspx

|||

I am connecting using Client Tools (Enterprise Manager).

You are correct about network problem. I am not sure how to configure network on the server.

It is not timeout.

Also, I am not the only one. It happends to everyone who just installed sql server 2005 with sql express. There so many posts on Google, but not a single solution.

Thanks,
GK

|||

Just to be clear, when you set up sql server 2005 you went in to sql security and cre-created all your logins?

Also, is there SSL or any other kind of extra security on the sql server?

|||

All the accounts have same privilidges, I connect using dbo.

No SSL or anything like that.

Thanks,
GK

|||

I asked whether or not you re-created the accounts when you installed sql server 2005. Did you actually go into sql 2005 and re-create all the accounts.

Also, here is a post that seemed to have helped a couple othershttp://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=984492&SiteID=1