SQL Server 2005 SP 3

  • Okay, I donwloaded SP 3 for both x86 and x64 systems. I successfully applied the x86 SP 3 to my system at home and my desktop at work, no problems.

    This evening I was applying SP 3 x64 to 2 of my development systems. The first system, no problems applying the service pack. The second, I got failures on the database engine (2 instances, both failed), SSIS, and client tools. Everything else, sucessful.

    The error messages indicated it couldn't find the msp files in WINDOWS\Installer directory so it tried to use the source directory on the d: drive where the files where loaded when I started the process, but couldn't find it there. Of course, looking at the output i the log files it was looking in a directory that had been created when I installed SP 2 quite awhile ago.

    Please realize, I used the same downloaded file for load SP 3 on both systems. One install ran fine the other failed. Has anyone else run into this problem, or am I the first to try loading SP 3?

    If anyone would like to see the log files, let me know, and I will zip them up from BOTH systems and post them here. I'd consider doing it now, but it's late, I'm tired, and I don't really want to fight with downloading the files (even if they are only text files) from work to home to post them.

    ANY thoughts, suggestions, etc are welcome. Oh, I have already tried rebooting the server and that did nothing.

    Cheers!

  • You are the first that I know of. I was thinking about doing it on my dev server (64-bit), but now I think I'll wait until you are done.

    Thanks for jumping to thte front of the line.

  • Lynn,

    I have installed it onto two x86 servers with no issues so far. I have a x64 QA server I can apply it to later today and let you know how it goes. I haven't done one of my multi-instance servers yet, but would be willing to apply it to one of the development ones later tonight. I'll let you know how it goes.

    Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
    My Blog | Twitter | MVP Profile
    Training | Consulting | Become a SQLskills Insider
    Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]

  • Only reason I jumped up front was because of Christmas break. Of course I'm off over Christmas as well, but not much else is going on as we are a K12 school distrct.

    Again, any thoughts, suggestions, snide comments even, are welcome.

    When I get to work, I will zip and post the log files from both systems and post them for everyone to read.

    Thanks!

  • On one of the car forums I am a member of for classic mustangs, they have this say "This post is worthless without pictures."

    I guess I could morph that to "This post is worthless without log information."

    Without the logs it is going to be pretty hard to make recommendations or even ask questions of others to try and get help with this. Are all the services able to start on the server that is having issues, or is one/some of them disabled? I know you said that it was complaining about a missing file, but just throwing other stuff out there that I've seen block updates in the past.

    Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
    My Blog | Twitter | MVP Profile
    Training | Consulting | Become a SQLskills Insider
    Troubleshooting SQL Server: A Guide for Accidental DBAs[/url]

  • For those of you following this thread, I am at work and I am getting the logs ready now. I will have them posted in the next 15 minutes or so.

    Thanks

  • Here are the logs from both servers.

  • One thing I noticed pretty quickly is that the 2 servers have different builds and the one that worked has a later build. I don't know why that would cause a failure, but maybe it does.

    When was the last time you did windows updates on DEV01, the failed install? Maybe there is an update to Windows Installer that you are missing?

  • My eyes are going buggy still, Jack. Any way you can "point out" where you saw that in the logs for me?

  • And which log you saw it in.

    I'm guessing I'm too close to the trees to see the forest.

  • Lynn,

    I went the simply route and looked at the Summary logs first, side by side. Here are the sections:

    Dev01:

    Products Detected Language Level Patch Level Platform Edition

    Setup Support Files ENU 9.3.4035 x64

    Database Services (MSSQLSERVER) ENU SP2 2005.090.3068.00 x64 DEVELOPER

    Database Services (QA) ENU SP2 2005.090.3068.00 x64 DEVELOPER

    Integration Services ENU SP2 9.00.3068.00 x64 DEVELOPER

    SQL Server Native Client ENU 9.00.4035.00 x64

    Client Components ENU SP2 9.2.3068 x64 DEVELOPER

    MSXML 6.0 Parser ENU 6.20.1099.0 x64

    SQLXML4 ENU 9.00.4035.00 x64

    Backward Compatibility ENU 8.05.2312 x64

    Microsoft SQL Server VSS Writer ENU 9.00.4035.00 x64

    Dev02:

    Products Detected Language Level Patch Level Platform Edition

    Setup Support Files ENU 9.2.3042 x64

    Database Services (MSSQLSERVER) ENU SP2 2005.090.3073.00 x64 DEVELOPER

    Analysis Services (MSSQLSERVER) ENU SP2 2005.090.3073.00 x64 DEVELOPER

    Reporting Services (MSSQLSERVER) ENU SP2 9.00.3073.00 x64 DEVELOPER

    Integration Services ENU SP2 9.00.3073.00 x64 DEVELOPER

    SQL Server Native Client ENU 9.00.3042.00 x64

    Client Components ENU SP2 9.2.3073 x64 DEVELOPER

    MSXML 6.0 Parser ENU 6.20.1099.0 x64

    SQLXML4 ENU 9.00.3042.00 x64

    Backward Compatibility ENU 8.05.2004 x64

    Microsoft SQL Server VSS Writer ENU 9.00.3042.00 x64

    Notice that "core" components are at 2005.090.3068.00 in DEV01 and 2005.090.3073.00 in DEV02.

  • Too old to fine the trees.....?

    Too much snow in your eyes this morning? 🙂

  • Steve Jones - Editor (12/19/2008)


    Too old to fine the trees.....?

    Too much snow in your eyes this morning? 🙂

    I've been working on this for 4 hours last night (8:00 Pm to 12:00 AM) and then up around 6:00 AM this morning so I didn't get much sleep.

  • My network people are busy on other issues, so I'm not getting a lot of response from them. I am hitting a wall, and don't know what else to do at the moment.

    I did a little research on what Jack pointed out and it looks like DWDEV02 was automatically updated with a GDI+ update but DWDEV01 wasn't. Not sure if that is an issue however, but I haven't found anything else that it may be.

    I have googled and searched and haven't found anything of value yet. I'm going to go on and work on something else for a bit. Maybe getting away from the upgrade issue will help clear the mind some.

    Please, if anyone has any ideas, thoughts, or suggestions please post them. I'd like to resolve this issue as soon as possible.

  • Wish I could do more, but I don't have a 64-bit box to experiment with right now.

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

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