Post reply

after install remote connection

  • July 14, 2005 at 2:29 pm

    #90105

    SLQ Server 2005 June CTP on Windows 2003 sp1

    After initial installation can connect from the server but not remotely.

    Recieve this error

    A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)

    Using SQL Server Configuration manager enable Named pipes and TCPIP for both Client protocols and Protocols for MSSQLSERVER. 

    Still Can not connect remotely Bounce the box.

    Now SQL Server 2005 will not start with the following errors from app log

    SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

    Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

    TDSSNIClient initialization failed with error 0x7e, status code 0x1.

    TDSSNIClient initialization failed with error 0x7e, status code 0x3a.

    From this article

    http://support.microsoft.com/?kbid=900497

    added the certificate key

    Funny thing immediatley preceding the error above is this

    entry from the application log this was before added the certificate key

    A self-generated certificate was successfully loaded for encryption.

    Then disable the

    Named pipes and TCPIP for both Client protocols and Protocols for MSSQLSERVER.

    Bounce the box but back where I started can not connect remotely but can connect locally.

    Any help appreciated.

    Joe

  • July 15, 2005 at 7:02 am

    #574776

    I think I have it figured out. 

    I have heard that developer edition is not configured to allow remote installs?

  • July 19, 2005 at 5:12 am

    #575429

    Try forcing your connection to use named pipes by putting np: in front of the server.

    Another workaround for us seems to be putting the users/groups into Remote access local group on the box.

    Haven't got to the bottom of this yet.

     

     

  • November 9, 2005 at 8:12 pm

    #603157

    Try going into SQL Server Configuration Manager and checking that the protocols for MSSQLSERVER and Client Protocols are what you expect.  I seem to remember that they can be set in the Surface Area Configurator but not enabled in the former utility... Mine's working, so I'm not about to test it; but from memory, that was a problem.

    Cheers,

    david russell

  • November 9, 2005 at 8:13 pm

    #603158

    oh, and then throw away the June CTP.  This product is GA now

    Cheers,

    david russell

  • November 10, 2005 at 11:46 am

    #603301

    Fine dude!  It works on my box.  if you want to bad-mouth the product at every opportunity that is your right; but I am not about to disable my system in order to test something that might help you fix yours.  I have a product to deliver.

    Cheers,

    david russell

  • November 12, 2005 at 11:46 pm

    #603568

    Ok, Remote connection is possible in all versions of SQL 2005, but in Express and developer it is disabled by default. . .

    when enabling don't enable the VIA protocol.

    that should solve the problem!

     

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply