Upgrade SQL 2008 to SQL 2008 R2

  • I had asked if sql agent is running currently.can you find out

  • Grant Fritchey (2/22/2011)


    Fox87 (2/22/2011)


    Hi There,

    The SQL Upgrade Advisor doesn't work if I run it on my SQL 2008 instance.

    It give the following error:

    SQL Server version: 10.00.4000 is not supported by this release of Upgrade Advisor, only SQL2000 or SQL2005 is supported.

    Do you have any idea how I can run it or why it is giving me this error? The current version is:

    Microsoft SQL Server 2008 (SP2) - 10.0.4000.0 (X64) Sep 16 2010 19:43:16 Copyright (c) 1988-2008 Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) (VM)

    I don't think there are any differences between 2008 & R2 for the upgrade advisor to deal with.

    It works on 2008R2 succefully.

    Sagar Sonawane
    ** Every DBA has his day!!:cool:

  • Saga... (8/4/2011)


    Grant Fritchey (2/22/2011)


    Fox87 (2/22/2011)


    Hi There,

    The SQL Upgrade Advisor doesn't work if I run it on my SQL 2008 instance.

    It give the following error:

    SQL Server version: 10.00.4000 is not supported by this release of Upgrade Advisor, only SQL2000 or SQL2005 is supported.

    Do you have any idea how I can run it or why it is giving me this error? The current version is:

    Microsoft SQL Server 2008 (SP2) - 10.0.4000.0 (X64) Sep 16 2010 19:43:16 Copyright (c) 1988-2008 Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) (VM)

    I don't think there are any differences between 2008 & R2 for the upgrade advisor to deal with.

    It works on 2008R2 succefully.

    Good to know. Thanks.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • chandan_jha18 (8/3/2011)


    I had asked if sql agent is running currently.can you find out

    Currently, after my failed upgrade attempt to go to R2, the SQL Server Agent is not running. I do not know if it was running before I tried to upgrade or not. I still haven't had a chance to manually remove all the installation bits to re-install a clean version of 2008 so I can try to update to R2 again.

  • Mary Truesdell (8/4/2011)


    chandan_jha18 (8/3/2011)


    I had asked if sql agent is running currently.can you find out

    Currently, after my failed upgrade attempt to go to R2, the SQL Server Agent is not running. I do not know if it was running before I tried to upgrade or not. I still haven't had a chance to manually remove all the installation bits to re-install a clean version of 2008 so I can try to update to R2 again.

    Do you really have luxury of so much downtime 🙂

  • It's on my actual computer and not my server (thank God!). It just means to use SQL Server I have to remote into a server, which is faster than the 2 hrs it takes to clean up my shattered install.

  • Mary Truesdell (8/4/2011)


    It's on my actual computer and not my server (thank God!). It just means to use SQL Server I have to remote into a server, which is faster than the 2 hrs it takes to clean up my shattered install.

    This is nice now. Anyways you are planning to uninstall, play with it for a day or two.

    You said agent is not running, can you see if the location of agent executables are located in right place. Even if it is, do something funny. Delete all those files and then reboot. Then run the 2008R2 setup again!

  • Ok, I have a question about the process you suggested.

    Is this what you want me to do:

    clear out broken install

    re-install SQL 2008

    [make a restore pt!]

    delete the SQL Server Agent Files? [what are these? Where are they?]

    reboot

    run upgrade from 2008 to 2008 R2

    ORR, are you wanting me to do this:

    delete SQL Server Agent files

    reboot

    run upgrade from 2008 to 2008 R2

    thanks

  • Mary Truesdell (8/5/2011)


    Ok, I have a question about the process you suggested.

    Is this what you want me to do:

    clear out broken install

    re-install SQL 2008

    [make a restore pt!]

    delete the SQL Server Agent Files? [what are these? Where are they?]

    reboot

    run upgrade from 2008 to 2008 R2

    ORR, are you wanting me to do this:

    delete SQL Server Agent files

    reboot

    run upgrade from 2008 to 2008 R2

    thanks

    This is your test machine and it is why I am taking a bad route. But we can learn from it.At the end, if nothing comes out, you have an option of uninstalling everything.

    1) I suspect that it is your agent that was halting the upgrade process.

    2) Run- type- services.msc and find the sql agent service.

    3) Right click on it and find the path of its executable file

    4) go to that folder where that sqlagent.exe (something like this) exists and delete all the files from the folder.

    5) We are just deleting executables and not msdb so your jobs or packages will be safe.

    6) Now, reboot and make sure SQL Server is running. SQL agent will not run and will show in disabled state in management studio.

    7) Now run the upgrade and tell me what you find out.

    Do this as a risky learning excercise. Never do it in prod.

    Go for it and let me know how it works for you.

  • Looks like this thread is not active, but did not find another one. I did a direct upgrade and the upgrade and gave me errors that rsctr.dll is being used by another process. This seems to be a known issue and stopping wmi helped to move forward

    http://connect.microsoft.com/SQLServer/feedback/details/363653/error-messages-when-upgrading-from-sql-2008-rc0-to-rtm#

    However, after installing sp2, I am not able to run SQL Agent jobs saying explicitly set database cannot be accessed. I tried work arounds with

    http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/38de5a7c-a02d-4833-a3e0-1f0df9f0fb8d/

    http://www.sqldbadiaries.com/2010/12/06/server-is-in-script-upgrade-mode-only-administrator-can-connect-at-this-time/

    https://connect.microsoft.com/SQLServer/feedback/details/416860/error-18401-after-starting-service-after-successfull-sp1-install#, but still getting the same error. Anyone has any idea how to get out of this? Any help appreciated. Thanks in advance!

  • I found that when rsctr.dll is being used by a process, the SQL Full TXT Search service hadnt been stopped by the upgrade. it was still running. I stopped the service and clicked retry and the upgrade continued.

Viewing 11 posts - 16 through 25 (of 25 total)

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