none
How Do I know whether Sql Server Sp2 installation was successfull or not?

    Question

  • Hi Guys,

    I would like to know whether Sql Server Service Pack 2 installation was successfull or not? I have two machines Server A and Server B, now on Server A went to the path "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix" and found there three files Summary.txt,Summary_0.txt,Summary_1.txt

    When I go to Server B for the same path I found multiple files apart from the three which were available in Server A, the additional Files found under Server B was :

    Redist9_Hotfix_KB921896_SQLServer2005_BC.msi.log

    Redist9_Hotfix_KB921896_sqlxml4.msi.log

    Redist9_Hotfix_KB921896_msxml6.msi.log

    SQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log

    Redist9_Hotfix_KB921896_sqlncli.msi.log

    RS9_Hotfix_KB921896_sqlrun_rs.msp.log

    Redist9_Hotfix_KB921896_SqlSupport.msi.log

    Does this mean that Sql Server Service Pack 2 was not successfull completely?

     


    Raju
    Friday, September 03, 2010 12:19 PM

All replies

  • Hello,

    Please run the following command using SQL Server Management Studio:

    SELECT @@version

    If you get build “9.00.3042” then SQL Server 2005 SP2 was installed successfully.


    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Friday, September 03, 2010 12:35 PM
    Moderator
  • Hi Albert,

    I do get the same version as mentioned by you, but wondering why there are more log files note the servers mentioned are for SSIS only not for a database.


    Raju
    Friday, September 03, 2010 12:36 PM
  • If I see the Integration Services Service pack 2 installation Log "DTS9_Hotfix_KB921896_sqlrun_dts.msp.log", I can find these entries in the end of the file:

    Property(S): MsiWin32AssemblySupport = 5.2.3790.3959
    Property(S): MsiNetAssemblySupport = 2.0.50727.42
    Property(S): DTS200564Hotfix3042 = d:\4e179e5ec97a16cf1df81485914158\HotFixDTS\Files\sqlrun_dts.msp
    MSI (s) (D0:5C) [20:13:57:236]: Product: Microsoft SQL Server 2005 Integration Services (64-bit) - Update 'Service Pack 2 for SQL Server Integration Services 2005 (64-bit) ENU (KB921896)' installed successfully.

    MSI (s) (D0:5C) [20:13:57:236]: Note: 1: 1728
    MSI (s) (D0:5C) [20:13:57:236]: Transforming table Error.

    MSI (s) (D0:5C) [20:13:57:252]: Transforming table Error.

    MSI (s) (D0:5C) [20:13:57:252]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (D0:5C) [20:13:57:252]: Transforming table Error.

    MSI (s) (D0:5C) [20:13:57:252]: Transforming table Error.

    MSI (s) (D0:5C) [20:13:57:252]: Note: 1: 2262 2: Error 3: -2147287038
    MSI (s) (D0:5C) [20:13:57:252]: Product: Microsoft SQL Server 2005 Integration Services (64-bit) -- Configuration completed successfully.

    MSI (s) (D0:5C) [20:13:57:267]: Attempting to delete file C:\WINDOWS\Installer\5e094b57.msp
    MSI (s) (D0:5C) [20:13:57:267]: Unable to delete the file. LastError = 32
    MSI (s) (D0:5C) [20:13:57:267]: Cleaning up uninstalled install packages, if any exist
    MSI (s) (D0:5C) [20:13:57:267]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\5e094b57.msp'
    MSI (s) (D0:5C) [20:13:57:283]: MainEngineThread is returning 0
    MSI (s) (D0:80) [20:13:57:283]: Destroying RemoteAPI object.
    MSI (s) (D0:C8) [20:13:57:283]: Custom Action Manager thread ending.
    === Logging stopped: 13/10/2009  20:13:57 ===
    MSI (c) (44:6C) [20:13:57:314]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (44:6C) [20:13:57:314]: MainEngineThread is returning 0
    === Verbose logging stopped: 13/10/2009  20:13:57 ===

    Does this mean it was not successfull?


    Raju
    Friday, September 03, 2010 12:45 PM
  • Hello,

    On the summary.txt log verify the overall summary of the execution.


    http://msdn.microsoft.com/en-us/library/ms143702.aspx

    Search for the words “failed” or “error”.

    The summary.txt log gives the result of the update per component. If you see success on every component, then SP2 was successful.

    Hope this helps.

    Regards,

    Alberto Morillo
    SQLCoffee.com

    Friday, September 03, 2010 12:47 PM
    Moderator
  • It Says successfull in Summary.txt. The reason behind asking this was I have an SSIS package which runs from Server A and Server B. I have a master package which calls the child package and inside the Master package I have a transformation called Execute package task inside this transformation when I says Execute out of process to True then the package would run successfully from Server A but the same package would not run from Server B, in order to run from Server B I have to make Execute out of Process to False.

    Now the second issue, the child packages connects to Oracle and stores the data in Sql Server. I am using 32 bit dtexec to run these packages and for the oracle client the path was C:\Program Files (x86)\..... and under this scenario the SSIS package runs from Server A runs fine without any issues but the same packages does not run Server B giving Acqiuired Connection Fails. So in Order to run this package from Server B I have to copy the entire Program Files (x86) folder to a different location and rename the folder to ProgramFilesX86. So the oracle client patch would look like C:\Programfilesx86\.....

    If you can clearly see the sepcial charecters has been removed and I change the oracle client path in the Path variable of my system to point to this new location now the SSIS package would run fine from Server B.

    I have posted these issues in SSIS forums but didn't find the root cause of this issue as a result I was trying to figure out whether this was an issue with Service pack2.

    Whenever I see the installation logs of Server A I have only Summary files but When i see the same logs in Server B I have several other log files along with Summary files.


    Raju
    Friday, September 03, 2010 1:19 PM
  • Hello Raju,

    I don’t know if that behavior is related to SP2, but I think you will find the following thread interesting:

    http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/86e4071d-e018-4618-91f1-08016bbc6391/

    I would try SScottIS solution.

    Hope this helps.   
     
    Regards,

    Alberto Morillo
    SQLCoffee.com

    Friday, September 03, 2010 1:35 PM
    Moderator
  • Hi ALbert,

     

    SScottIS solution was to call the 32 bit dtexec , even in our Servers we use 32 bit dtexec only and all the packages are run windows batch schdeuled through windows scheduled.


    Raju
    Friday, September 03, 2010 2:34 PM
  • Hi Jagapathi,

     

    Thanks for your post.

    Alberto has provided a perfect method to check if SP2 is installed successfully or not. Meanwhile the issue in your later reply is more related to SQL Server Integration Services. In order to get quicker support, I recommend that you ask it in SQL Server Integration Services.


    Regards,
    Tom Li
    Monday, September 06, 2010 12:40 PM
    Moderator