TDSSNIClient initialization failed with error 0x7e, status code 0x60, stopped me from connecting to SQL Server 2008. Here is how I solved it.
SQL SERVER – Fix : Error : 40 – could not open a connection to SQL server – Fix Connection Problems of SQL Server
Still stuck on Error 40, could not open a connection to SQL server? Here are more suggestions to fix connection problems, beyond my first two articles.
SQL SERVER – Detailed Explanation of Transaction Lock, Lock Type, Avoid Locks
How do you find which table has a transaction lock and what lock type it is? Imran Mohammed explains it for SQL Server 2000 and 2005, and how to avoid locks.
ABS: Widen an Integer Before Taking Its Magnitude
ABS can overflow even when the negative input fits its signed integer type. I widen the input before asking for its magnitude. Casting the output afterward would be too late to protect the calculation.
SQL SERVER – Fix : Error : 1326 Cannot connect to Database Server Error: 40 – Could not open a connection to SQL Server
If you are receiving the following error related to connection to SQL Server, this blog is for you.
SQL SERVER – FIX – ERROR : 9004 An error occurred while processing the log for database. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
Error 9004 means an error occurred while processing the log for database, so it will not attach. Here are the steps that worked for me, starting with emergency mode.
SQL Server – Fix – Error : 9692 The _MSG protocol transport cannot listen on port because it is in use by another process.
Error 9692 says the Service Broker transport cannot listen on port because another process uses it. Find that program with netstat, or move the port.