Comments on: Upgrade from MS SQL Server 6.5 to SQL 2000 Fails http://itknowledgeexchange.techtarget.com/itanswers/upgrade-from-ms-sql-server-65-to-sql-2000-fails/ Fri, 24 May 2013 17:13:17 +0000 hourly 1 By: henrykafeman http://itknowledgeexchange.techtarget.com/itanswers/upgrade-from-ms-sql-server-65-to-sql-2000-fails/#comment-41221 henrykafeman Mon, 13 Dec 2004 07:27:41 +0000 #comment-41221 Thanks for your suggestions.

None helped, BUT I have now found MS KB Article 818550 which says this is a bug!

Note I get “Export Exit Code: 259″ Error on SQL 2000 PC a few seconds before the sa Login failure on the SQL v6.5 PC!

Also note, that when I did a Web search for “Export Exit Code: 259″ I only found the Japanese version of KB Article 818550!

Anyway, I think I have found my own workaround! Having got to the ppoint of failure, I tried the standard DTS Import and Export Data on the SQL 2000 PC. This works fine with default settings and selecting All Tables – I now have my Data in SQL 2000!

Thanks

]]> By: pedwards17 http://itknowledgeexchange.techtarget.com/itanswers/upgrade-from-ms-sql-server-65-to-sql-2000-fails/#comment-41222 pedwards17 Fri, 10 Dec 2004 16:52:54 +0000 #comment-41222 This is true, but SQL2K still wants to talk to itself over named pipes. This comes into play when you’re doing an upgrade (as is the case here) or installing a SQL service pack. Disabling named pipes in these situations will likely cause problems. It may make sense to enable named pipes for the duration of the maintenance, and then disable it after.

]]> By: howard2nd http://itknowledgeexchange.techtarget.com/itanswers/upgrade-from-ms-sql-server-65-to-sql-2000-fails/#comment-41223 howard2nd Fri, 10 Dec 2004 16:34:34 +0000 #comment-41223 Previous answer should help – SQL2k does NOT enable ‘Named Pipes’ by default, instead TCP/IP is the preferred transport. In the deprecation of NetBUI / NetBIOS (i.e. WINS, local ‘Computer Browser’) moving away from ‘Names’ is a good thing. But requires and understanding of DNS and active directory. All my ODBC setups use IP addresses versus ‘names’ to avoid the lookup delay.

]]>