Results 1 to 11 of 11
  1. #1
    Join Date
    Oct 2004
    Posts
    2

    Unanswered: SQL6.5 upgrade wizard error

    I am having the following error when running the SQL upgrade wizard trying to upgrade SQL 6.5 to SQL 2000. Does anyone here know what is the problem ?

    Version Switch has aborted because you do not have "Full Control" permission to one of the HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServ* registry keys. Please use regedit32.exe to correct this problem and try again.

    I have already checked the registry and I do have full control permission on HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServ*. Please help.

  2. #2
    Join Date
    May 2003
    Location
    UK
    Posts
    220
    to make it easy on yourself, log in as a member of the local adminstrators group on the box. Then you will have full access and very little problem.

    Cheers,

  3. #3
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    You need to run upgrade wizard on 7.0 from 6.5 before touching 2K. I never heard of 2K coming with a wizard to upgrade from 6.5 to 2K directly.
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

  4. #4
    Join Date
    Jul 2004
    Location
    Inverurie
    Posts
    628
    It states in the BOL that 2k cannot do a direct upgrade from 6.5. You will need to go to 7.0 first then up to 2k, unless you want to start everything from scratch.

    Im also pretty sure you could bcp out all the tables from 6.5 database and put them into a 2k database.

  5. #5
    Join Date
    Oct 2004
    Posts
    2
    Thank you everyone for their input.

    I am done several time upgrading from SQL 6.5 to SQL 2000 directly using the wizard and only encountered problem this time. I always logon as an administrator on the server and therefore I do have all the permission needed. Please help.

  6. #6
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    I've never used a wizard to upgrade from 6.5 to 2000, but it wouldn't surprise me in the least if such a thing existed. I'd just install 2000, then use its Enterprise Mangler to script out the 6.5 schema without the referential integrity constraints, play that script into an empty 2000 database, move the data, then script and play the RI constraints that I'd skipped earlier.

    -PatP

  7. #7
    Join Date
    Oct 2003
    Posts
    232

    Arrow

    Interesting
    for schema i should use

    1) ALL OBjects

    scripting options
    i should check mark
    a)object creation
    b)object dependencies
    c) table indexes
    d) table triggers

    But not table keys/dri & use quoted identifiers--- IS THIS OK

    security
    a) all users/groups
    b) all logins and
    c) all permission


    Than i do data transfer from old to new

    HOW ????

    i MANY nsp does the code changes for that from 6.5 to 2000 ??
    bigfoots

  8. #8
    Join Date
    Oct 2003
    Posts
    232

    Arrow

    Interesting
    for schema i should use

    1) ALL OBjects

    scripting options
    i should check mark
    a)object creation
    b)object dependencies
    c) table indexes
    d) table triggers

    But not table keys/dri & use quoted identifiers--- IS THIS OK

    security
    a) all users/groups
    b) all logins and
    c) all permission


    Than i do data transfer from old to new

    HOW ????

    i have MANY stored procedure does the code changes for that from 6.5 to 2000 ??
    bigfoots

  9. #9
    Join Date
    Oct 2003
    Posts
    232

    Arrow

    can i do transfer of data directly from 6.5 to 2000?????


    after copying the schema to objects so i dont use wizard unnessary


    how
    Last edited by sjumma; 10-21-04 at 17:24.
    bigfoots

  10. #10
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    My suggestions would be:

    1) INSERT INTO (using a linked server)
    2) DTS
    3) BCP

    -PatP

  11. #11
    Join Date
    Feb 2005
    Posts
    1
    I had the same (original) problem and discovered that a couple of the sub-keys didn't have the correct permissions. The ones I had to amend were:
    1) MSSQLSERV65\MSSQLSERVER - I added Full Control to Administrators group
    2) MSSQLSERV80\MSSQLSERVER\SUPERSOCKETNETLIB\LPC - I tried adding the Administrators group with Full Control but it kept getting removed (don't know by what), so I ended up giving Full Control to Everyone.

    It will be worth checking all subkeys though.

    The Version Switch worked after that.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •