December 10, 2004 at 10:49 am
The upgrade process using "SQL Sever UPgrade Wizard" fails at the "Import and Export via Named Pipe" part.
With the following Error:
Starting MSSQLServer...............................
Waiting for recovery. Sysmessages # 4002
[Microsoft][ODBC SQL Server Dirver][SQL Server] Login failed
I am using a Network connection between a Windows 2000 Server PC running SQL Server 2000 and a Windows NT PC running SQL Server v6.5.
There is an Error logged on the v6.5 PC indicating that the sa login failed!
EventID 17055 Mesg 1845 from MSSQLServer.
However, to get through all the earlier steps (e.g. copying across the Tables Design), it must have been able to login to the v6.5 PC via sa????
Note my 2 PCs are in different Domains, but with Trusts between them and I am logging onto both as Administrator and have set Security Permissions, for anything I think might be relevant on the v6.5 PC for the v2000 PCs Domain Administrator (and Domain Admins).
MS Article 302850 does not help.
Can anyone help with any ideas or suggestions? - This is holding me up!
December 10, 2004 at 2:01 pm
Hello,
You MUST be logged to BOTH computers as a Domain User that is a valid user in BOTH domains, check what trusts were established, one or two way trusts, this Domain User must be in Administrators on both computers and you have to use Integrated Windows Authentication to connect to SQL Server.
Workaround that I used several times in order not to deal with domains and OS problems:
Installed SQL Server 7 on the development NT computer with SQL 6.5. Used Upgrade Wizard to get to 7.0 on the same 6.5 computer. Detached (or backed up) 7.0 files. Moved to 2000 computer by FTP or CD or Over the Network. Attached (or restored) to SQL 2000 on Windows 2000 computer. Worked well for projects. I tested everything in the development environment first, validated, QAed and then did a production upgrade using a development environment for staging from 6.5 to 7.0
Yelena
Regards,Yelena Varsha
December 13, 2004 at 6:02 am
Thanks for your suggestions.
I already had 2 way Trusts set up and Administrator on both Domains, etc.
I was trying to avoid going via SQL v7.0 as this would require it to be installed on a Development PC and my taking it to the Customer's Site, etc.
Anyway 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 point 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!
In fact if I just manually create a new Database in SQL 2000, I can use DTS to copy the Tables and Data from SQL v6.5. So I do not really know what extra the Upgrade Wizard would do for me? - note I can recreate any Triggers, Stored Procedures, etc. separately once I get to SQL 2000!
Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply