Tip: Display unicode data from mySQL DB on a website in PHP.

Before we start we need to make mySQL database capable of supporting unicode characters. For that we need to change the database collation or the table collation to utf8_unicode_ci. This can be done with phpmyadmin portal.

  1. Click the table you need to change.
  2. select Structure tab.
  3. Check the required column and click change or edit.
  4. From the collation drop down select utf8_unicode_ci.
  5. Press Go.

Click here to read more

Error: Could not find any IP address that this SQL Server instance depends upon.

Problem:

We had a requirement to change the SQL Server Fail over cluster group Virtual server name. We did that change through the cluster administrator. That SQL Server was 2008 Enterprise running onĀ  Windows 2008 Enterprise cluster. The change was successfully made from one node and the SQL server came online after that. But when we did fail over testing, we noticed that the SQL Server service is not coming online on the other node. The SQL Server error-log gave below errors while trying to start-up.

  • Could not find any IP address that this SQL Server instance depends upon. Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available. Error code: 0x103.
  • Error: 17182, Severity: 16, State: 1.
  • TDSSNIClient initialization failed with error 0x103, status code 0xa. Reason: Unable to initialize the TCP/IP listener. No more data is available.
  • Error: 17182, Severity: 16, State: 1.
  • TDSSNIClient initialization failed with error 0x103, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. No more data is available.
  • Error: 17826, Severity: 18, State: 3.
  • 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.
  • Error: 17120, Severity: 16, State: 1.
  • SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Click here to continue reading this post and resolution