This morning my colleague encountered an error "error establishing connection" while he's trying to connect to his local SQL Server from Weblogic. After some investigation, found that his local SQL Server actually didn't accept any TCP connection. When we're connecting the SQL Server from another machine using the SQL Enterprise Manager, we got an "[ConnectionOpen (Connect()).]SQL Server does not exist or access denied." error and after googling for it, we got to know that the problem is around security for the slammer worm, and a dll called DBNETLIB.dll. When this file is out of date, Server 2003 and perhaps SP2 on XP will actually disable the TCP/IP protocol for SQL Server to limit an attack. So, the solution is applying a
the security updates for SQL Server 2000.
- Database table get altered, updating database design spec is skipped, outcome: "what is that additional flag for?"- A bug get communicated to programmer verbally, entering into bug database is skipped, outcome: "why didn't we accept this
Tracked: Oct 09, 17:57