As I had discussed yesterday, the System Admin team rebuilt the Server on which had an instance running SQL 2000. Since we had the file level backup of all the drives, SQL Server Installation was supposed to be a cake-walk.
No! Today morning, I got a call stating that the SQL Server 2000 installation was failing with Network error. Thinking the System Admins had messed up something during the Operating System installation, logged on to the server to check if anything was wrong with the network setup. The network configuration was good.
The SQL Server installation log had this message.
Connecting to Server …
[Microsoft][ODBC SQL Server Driver][DBMSLPCN]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][DBMSLPCN]ConnectionRead (recv())
From the error message it seemed to be a network related issue. Checked the setting in Server Network Utility and everything was correctly set. The installation would run fine till it tried installing the SQL Server services. For a while I could not realize what was going on.
Eureka! I realized that I had faced this issue almost 5 years ago. Guess what? This issue is caused by the Server Name! Our server name was entered in lowercase and SQL Server 2000 installation does not succeed if the server name is in lowercase. The workaround suggested by this fix on Microsoft site, suggests that the Server Name be entered in UPPERCASE.
Now we got to know the failure root cause and asked the System Admins to change the server name to uppercase. He entered the server name in uppercase and rebooted the server. Still the server name showed up in lower case. Then we suggested him to give a new name to the server and then enter the actual server name in uppercase after reboot.
As expected, the server name was in upper case now and the SQL Server 2000 installation completed successfully !