Post reply

SQL 2000 SP3 install Failed.

  • January 21, 2003 at 5:18 am

    #158814

    After running the setup.bat of SQL 2000 SP3 I get to the point where the wizard prompts me for a valid ID (SQL or trusted) to continue applying the SP. Whether I use a trusted or the sa ID it tells me that it cannot validate the user. I have tried this on 2 different test servers both running SQL 2000 SP2. Is anyone else having this issue or able to make any suggestions?

    Thanks,

    rearasi

  • January 21, 2003 at 8:37 pm

    #446938

    1) Is the server set for mixed mode security (if not, sa won't work)

    2) When you logged on to the server, are you able to talk to a DC (domain controller) or are you merely logging on with cached credentials?

    K. Brian Kelley

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

    K. Brian Kelley
    @kbriankelley

  • January 22, 2003 at 3:50 am

    #446947

    Are you using Terminal Services perhaps?

  • January 22, 2003 at 9:51 am

    #446967

    Server set to mixed mode security and I am not using Terminal Services.

    Still having problems.

    Thanks,

    Rearasi

  • January 22, 2003 at 12:07 pm

    #446978

    Ok sitting at the server. Have you tried to log in with the SA credentials or a trusted account with QA or EM to verify if there is an underlying issue. Also, does this box have more than one instance on it?

  • January 22, 2003 at 12:40 pm

    #446981

    Yes,

    Both QA and EM both worked fine with sa and or trusted connections.

    No problem with that.

    Thanks,rearasi

  • January 22, 2003 at 12:54 pm

    #446982

    Ok then again what about multiple instances?

    And what is the name of the package file you downloaded? Are you sure you grabbed the right one (should bark this but...)

    Have you checked the log file that is generated (I believe in the Temp folder)? And check both the Event Viewer Logs and SQL Server Logs to see if anything reported to either.

  • January 22, 2003 at 2:38 pm

    #446994

    Had this problem during the Beta. You have a service which is running on the server leaving a connection to SQL Server open. Once you stop that service / close that connection all will proceed nicely.

    I made a comment to MS that they should change the error message for this but didn't get a response. Hope this helps.

    David

    David

    @SQLTentmaker

    “He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

  • January 22, 2003 at 3:10 pm

    #447004

    Ah, good someone on the Beta who saw this. Sorry I did like 20 test installs under various conditions I may see and never hit this one. Hope Davids on the right track.

  • January 23, 2003 at 2:02 am

    #447034

    you must close all connection, when you install SQL Server 2000 SP3

    I also close all SQL services on (SQL Server Service Manager) ..

    and write sa passord if you use mixed

    hope this helps

    bye

    Alamir mohamed Reda

    Alamir Mohamed


    Alamir Mohamed
    Alamir_mohamed@yahoo.com

  • January 23, 2003 at 2:12 am

    #447035

    you must close all connection, when you install SQL Server 2000 SP3

    I also close all SQL services on (SQL Server Service Manager) ..

    and write sa passord if you use mixed

    hope this helps

    bye

    Alamir mohamed Reda

    Alamir Mohamed


    Alamir Mohamed
    Alamir_mohamed@yahoo.com

  • January 23, 2003 at 6:27 am

    #447050

    I had the same problem, then got trapped with it set to single user mode (argh!)

    I rebooted the machine, then realized my

    application had several OS services that auto-magically connected to a database.

    I stopped those services, Plus EM & QA, then the service pack setup would let me proceed.

  • January 23, 2003 at 7:50 am

    #447053

    During the beta testing period, we had a similar error.

    Our problem was that, the new option to carry or change database ownership (new with sp3) option before you enter the user id, was checked.

    We had to uninstall SQL Server, re-install, reapply sp2, restore master, model and msdb, and then run the beta sp3 again LEAVING THE OWNERSHIP option uncheck.

    This solved the problem. So far, I applied sp3 (released on 1/17/2003) to two servers without any problem (still not live system yet, only develpment servers to test other applications before we go to production servers.) But the road was quite bumpy!

    Good luck!!

  • January 23, 2003 at 2:13 pm

    #447092

    Yes, I did the same procedure. I uninstall the SQL Server and reinstall SQL Server and restored all my system and user databases. This time I didn't stop any services, SP3 worked fine. I install on another production servers without stopping any services and it worked fine.

    It is really unique and unexplainable at this moment.

    Thanks for all the help with various suggestions.

    Thanks,

    rearasi

  • January 27, 2003 at 4:54 pm

    #447364

    as suggested by rearsi, i was about ready to remove sql server and re-install. but when attempting the remove, i got message that isqlw.exe needed to be stopped first.

    so rather that uninstall, i just stopped isqlw and them ran the service pack install. it worked..

Viewing 15 posts - 1 through 15 (of 15 total)

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