A Win95 PC was having some TCP/IP problems that were corrected by the helpdesk. After that, SQL 6.5 client utilities were not working properly.
When trying to configure TCP/IP sockets in the Client Config, there is an error "Unable to locate the Net Library in Path". The necessary files appear to be in the correct path when I choose locate. I deinstalled and reinstalled the client utilities with no luck.
Also, when I enter the SQL Enterprise Manager, the error "Network Communications layer not loaded" appears.
Any ideas?
Thanks,
Christi Fischer
fischerc@mail1.monmouth.army.mil
Assuming that IP/Sockets was added during the SQL installation. Forgetting the known reasons for selecting them (Integrated security, etc.)
I've never fully understood why one connect method worked in some cases and the other did not. Can someone attempt to convey what the real differences are. What are required to use Pipes/Sockets. Do you need to be in same Workgroup/Domain, have a name server, etc.
I believe we all could benefit from a good explanation of this.
Has anyone encountered this error and found a solution? A batch process received this error for the first time last night. We are running SQL 7 on an NT4 server, and the client machine is a Win2K box. The process is a VB application, using ADO to connect to the database. We are using TCP/IP protocol. We were using the Named Pipes protocol in the past, but changed to TCP/IP a few weeks ago, because we kept getting a "ConnectionWrite(GetOverLappedResults)" error, and found information that stated the error was due to the Named Pipes protocol, and the solution was to switch to TCP/IP. FYI, since switching protocols we have not seen the ConnectionWrite(GetOverLappedResults) error, and we used to get it everytime the process ran.
Any help or suggestions are appreciated. If any further information about our systems or the process would help, let mw know and I will provide it.
We would like to use dns entries (CNAME) to create transparency between server infrastructure and logical servernames. So we could physically move databases onto another server and changing the dns entry without reconfiguring all client applications.
Old situation: - Financeapplication connects to SERVERA (wins) through a .ini file.
New situation: - Financeapplication connects to finserver.mydomain.be (CNAME) - finserver.mydomain.be points to servera.mydomain.be (A record) in dns - servera.mydomain.be is refering to the ip address of SERVERA
We tried to connect and got a 'get_overlapped_results' (clientside) when using a dns name in combination with named pipes. At the server we are getting this error:
Error: 17832, Severity: 18, State: 8 2001-08-24 13:10:16.64 ods Connection opened but invalid login packet(s) sent. Connection closed.
Connecting to the wins name of the server does work! Connecting to the dns name also works when using tcp sockets instead of named pipes.
Though, on some client pc's this does work with named pipes too, but we couldn't find any regularity or logic when it works or when it doesn't (service packs, mdac versions, NT/95/98/2000, ... etc).
We also noticed that integrated security works with tcp sockets when using dns names, but it doesn't when using wins names.
NT EE, MSCS, SQL 7.0 in Active/Passive environment. Add'l SQL installed on Passive server is hosting our Report database(any tips on Log Shipping?). Anyway, I am unable to configure a client to connect to the secondary server via TCP/IP sockets.(Error 10061). I use the standard port 1433 and I've tried using both the name and the IP address for the server name.
What it looks like it's doing is only listening to port 1433 on the hearbeat nic. The reason I believe this is because when I ping the server name from that server, it returns a succesful ping, but using the heartbeat(seperate subnet)nics IP address.
Ping from a remote box works fine(DNS/Wins Resolution), and I connect fine with Named Pipes.
Both the primary and secondary server display the same results, the difference appears to be that only a virtual server in a clustered environment can have TCP/IP clients connect to it.
Can anyone verify this for me? Thanks a bunch...
MS says to go Active/Active and I am willing to do so, eventually. Looking for a short term solution.
I'm not able to listen on a different port(again, appears only a Virtual server can).
We are having some problems using TCP/IP connection and was wondering what the benefits are to using this versus Named Pipes. The company that provides our software stated that this would improve performance but I do not see it and I am getting a lot of errors connecting. This also locks many of the users and I end up having to stop and start the database to clear the locks because there are so many. Would it be better to place the clients on Multi-protocol. It seems more powerful to use but I wanted to get some feedback from some people that may have dealt with this issue before.
Since we change the web server to window 2003, we occasionally receive the message [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite (send())
We use ASP and ODBC to access sql 2005. I have specified to use TCP/IP and port 1433 in ODBC.
One of our customers is experiencing a problem that makes me think there is a network problem, because we make a request and never return from the driver, but the transaction is still open on the server awaiting the next command (and holding locks blocking other processes). I see a number of other driver writers have described similar problems, and their "workaround" is to set SO_TIMEOUT on the sockets (setSoTimeout) they create which is a last defense so that the transaction won't block forever.
I do not see this in the API documentation- how can I set this? Many other drivers use a connection string parameter, do you offer the same?
Is there any logging I can enable that can show me for sure that the driver is waiting indefinately on socket.read (thats not terribly expensive)?
I am running Windows 2003 Standard edition with IIS and SQL 2000 SP3a installed on it.
The web clients use ASP pages which use DSN to connect to SQL 2000 database. It has been working fine since last 1.5 years except 2 days ago when I faced this error suddenly on server:
I checked the error logs of SQL server and didn't find anything. Only entries were that the SQL is starting database, ports and IPs on which it is listening etc. The usual stuff. No errors in starting.
The SQL Agent log showed following errors:
2004-11-30 04:45:33 - ! [298] SQLServer Error: 2, ConnectionOpen (Connect()). [SQLSTATE 01000] 2004-11-30 04:45:33 - ! [382] Logon to server '(local)' failed (JobManager) 2004-11-30 04:45:36 - ! [298] SQLServer Error: 17, SQL Server does not exist or access denied. [SQLSTATE
I don't understand what was the problem. It first occured when nothing on server was changed, next it occured 30-32 hours later, and still now it hasn't happened again.
