Results 1 to 4 of 4
  1. #1
    Join Date
    May 2008

    Exclamation Unanswered: Upgrade from MSDE SP4 to SQL Server Express 2005


    I am upgrading the MSDE Instance in my application to SQL Server Express 2005.
    This is a named instance and was installed using mixed authentication i.e SA authentication.

    When I try to upgrade using SA authentication it gives me an error message saying:
    " SQL Server cannot upgrade the specified instance by using SQL Server Credentials.You must user windows authentication credentials for upgrade."

    but when I used Windows Authentication, it gives following error:
    "SQL Sever could not connect to the database to validate upgrade options.There was an error: Login failed for user [User Name]"

    User is having Admin right on machine where instance is installed.
    I am unable to comprehend the cause of error . Can please someone help me with this.


  2. #2
    Join Date
    Nov 2004
    on the wrong server
    Provided Answers: 6
    are you sure you are signed into the machine as a local admin? and that your windows auth account is a sysadmin within sql server?
    “If one brings so much courage to this world the world has to kill them or break them, so of course it kills them. The world breaks every one and afterward many are strong at the broken places. But those that will not break it kills. It kills the very good and the very gentle and the very brave impartially. If you are none of these you can be sure it will kill you too but there will be no special hurry.” Earnest Hemingway, A Farewell To Arms.

  3. #3
    Join Date
    May 2007
    Lost in Translation
    I have found that for named instances with MSDE and SQLSE, you must be logged on as the individual user who installed the original version of the MSDE program (named or unnamed) to be able to do an upgrade on that machine. It's a rights issue.

    You could try using osql and connect to the MSDE main instance (not the named one, but the original one that was installed or the default) and reset the sa password from there. See if that solves the problem using the sa login. BOL has information on how to do these things via osql or you can visit the kb articles here;
    "Passion rebuilds the world for the youth. It makes all things alive and significant. ~Ralph Waldo Emerson

  4. #4
    Join Date
    May 2008
    BUILTIN\administrators was not present in sysadmin. After adding it there I used Windows Authentication to Upgrade.
    It worked.;-)

Posting Permissions

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