October 3, 2005 at 6:04 am
Hi,
I have a 64 bit machine running on Windows 2003 SP1. I've installed the SQL Server 2005 64 bit edition. When I try accessing it with the management studio from a 32 bit machine, it gives me an error that says, "error: 0 Provider Error TCP error 10054.. Connection forcibly closed by remote host ..." How to proceed ?
October 3, 2005 at 6:34 am
I don't think you can access 64BIT from 32BIT. I know you can do the reverse however. Also, there are certain things that will not run in 64BIT only 32BIT currently (DTS being one I think).
Good Hunting!
AJ Ahrens
webmaster@kritter.net
October 3, 2005 at 6:49 am
Hi,
I dont find the management studio when I install the 64 bit version of SQL Server 2005 Beta 2. So how do I access the server without the client tools??
October 3, 2005 at 6:54 am
It is my understanding that there are no 64 bit Enterprise Manager nor do you have the ability to save DTS packages in 64 bit. You must access them via Ent. Manager on 32 bit. I cannot explain why you cannot access a 64 bit install though. We do not have any 64 bit installs here so I am of no help, you will probably have to open up a case with Microsoft.
October 4, 2005 at 3:58 am
Don't forget you are running a beta - things that should work may not do so.
Try downloading and using the June or September CTP, as these have fixed a lot of problems with earlier beta versions such as yours.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
October 4, 2005 at 5:30 am
Hi,
Well, let me be clear in my description of the current system. Here's what I have,
Hardware : Intel Xeon 3.6 GHz MP * 2 (64 bit processor)
Software :
Windows Server 2003 (X64 version)
SQL Server 2005 build version 2.0.40607.0 (64 bit)
IIS 6.0
.NET 64 bit Framework version 2.0.40607
This is the server copnfiguration I have.
Now when I try to connect to this system through network, it is fine. I mean to say, I'm able to carry out normal network operations to this machine from other 32-bit machines.
But when I try to connect to the SQL Server Database engine in the 64 bit machine, from SQL Server Management Studio on the 32-bit machine (meaning SQL Server 32 bit installed on the 32 bit machine with the client tools), I'm getting the following error. I have copied the entire error message here for more clarity.
=============================================
Cannot connect to server01.
=============================================
A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (.Net SqlClient Data Provider)
----------------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=10054&LinkId=20476
----------------------------------------
Server Name: server01
Error Number: 10054
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, Boolean freePacket)
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.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(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()
Please help.
Thanks and Regards,
Tikkam.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply