SQL Server 2005 error 233 solution

I. Error 233
1. Open "Microsoft SQL Server 2005 -- Configuration tool -- SQL Server Configuration Manager"
2. "SQL Server 2005 network configuration" -- "MSSQLSERVER protocol" -- enable "TCP/IP" and "Named Pipes ". after starting the TCP/IP protocol, you must change the TCP port number in its properties to 1433 (dynamic port) or the desired port number.
3. Restart "SQL Server"

After installing Microsoft SQL Server 2005 yesterday, we found that when connecting to the Server from Microsoft SQL Server Management Studio, if the Server name is not the machine name, but the IP address, connection always prompts failed, as shown in the following figure:

Solution: open 'project'-'All projects'-'Microsoft SQL Server 100'-'configuration tool'-'SQL Server configuration manager'. In the displayed form, find 'SQL Server 2005 network configuration', start "Named Pipes" and "TCP/IP" under the 'mssqlserver protocol', and then restart Microsoft SQL Server 2005.

Other error code reference

  
II. Error 18452
1. In Enterprise Manager, select the server (for example, LLQ \ SQLEXPRESS), right-click and select "properties"
2. Select the "security" tab. Under "server authentication", select "SQLServer and Windows authentication mode"
3. OK and restart the SQLServer service
III. Error 18470
1. Log on with "windows Authentication"
2. Extend to "security -- login name -- right-click sa -- switch to" status "-- enable logon ".
Additional: modify the logon password of the system administrator Sa.
1. Open the Enterprise Manager
2. "security" -- "login" -- right-click "Sa"
IV. Error 5123
Cause 1: As a result of database file operation permissions, add an Everyone user, Grant "control permissions", and re-attach the database, and the operation will be successful.
Cause 2: This error occurs if multiple NICs exist in the computer running on a single network segment and you use the NetBEUI network protocol. When NetBEUI protocol tries to register the same computer name in the computer on each network card. This error occurs when NetBEUI tries to register the second card on the network with the same name as the first card.