Post reply

Upgrade 6.5 to 2000

  • October 2, 2003 at 7:42 am

    #159929

    To all,

    I am trying to update a database from 6.5 to 2000. Both servers are in the

    same domain and SQL Server on both machines start up with the same domain

    administrators account. It is able to create the database on the 2000

    machine, but when it goes to import the data it fails. I keep getting the

    error: Couldn't connect to the ADMIN$ share on the export machine. Verify

    that the MSSQLServer service uses a NT Domain account that is part of the

    AMDINISTRATORS group of the export machine and both machines are in the same

    domain.

    I verified this. Why is not working?

    Any help is appreciated.

    Thanks in advance,

  • October 2, 2003 at 8:33 am

    #476783

    I would double chcek to ensure both domain service accounts are in the administrators groups in both servers and they are able to access admin shares such as C$, D$ etc.

    Edited by - allen_cui on 10/02/2003 08:33:59 AM

  • October 2, 2003 at 9:05 am

    #476795

    I went on to both servers and was able to access the admin$ share and all other admin shares with no problem for both sides.

  • October 2, 2003 at 9:36 am

    #476810

    Have you reviewed logs created by SQL Server Upgrade Wizard?

  • October 2, 2003 at 9:40 am

    #476814

    I was able to get the upgrade to work finally! The reaon why it did not work in the first place was because there was a file (CNV6x70.dll) on the 6.5 machine that was created prior to the upgrade. The upgrade creates this file when it is importing the data. This file should not be on the machine prior to that, if it is, it must be deleted. Just an FYI in case anyone else runs into the same problem. Thanks for the help.

  • October 2, 2003 at 9:47 am

    #476819

    So the erorr message is kind of miss-leading, isn't it?

  • October 2, 2003 at 10:00 am

    #476826

    Yes, I guess you can say that. But you can also look at it as SQL Server is trying to create this dll in that particular share and since the dll is already there it can not create it. SQL Server thinks that there is insufficient permissions.

  • October 3, 2003 at 9:22 am

    #476999

    quote:

    Yes, I guess you can say that. But you can also look at it as SQL Server is trying to create this dll in that particular share and since the dll is already there it can not create it. SQL Server thinks that there is insufficient permissions.

    you're making excuses for Microsoft


    -Ken

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply