登入
Microsoft.com
 
Microsoft
 
 
 

none
How to Install SQL 2005 Service Pack3 on DB Cluster RRS feed

 > 

  • 問題

  • Question
    登入以投票
    0
    登入以投票

    1. 是否各位大大能提供安裝SQL 2005 DB Cluster (容錯叢集) Service Pack3 步驟 
    2.     我試著安裝Service PACK3 在Standand by DB Cluster, 當要勾選更新Service Pack3 選項時 Database service 和Analysis Service 確無法選取,我試著繼續執行安裝到
            安裝結束,結果Database service 和Analysis Service 並無更新.其於項目階更新. 執行select @@version 指令. SQL 代號依舊停留在Service Pack2.想請問各位大大如何
            安裝SQL 2005 Service Pack3 的 Database Service 和Analysis Service 在DB Cluster.  thanks. 

    grace
    2009年12月9日 下午 04:17
    |

解答

  • Question
    登入以投票
    0
    登入以投票
    SSIS, client and some other components are not cluster awared, have to apply sp for them on all notes in the cluster. Ensure task scheduler service is running on all nodes and no any people logon to any node except you on active node. 
    2009年12月19日 下午 04:44
    |

所有回覆

  • Question
    登入以投票
    0
    登入以投票

    1. 是否各位大大能提供安裝SQL 2005 DB Cluster (容錯叢集) Service Pack3 步驟 
    2. 我試著安裝Service PACK3 在Standand by DB Cluster, 當要勾選更新Service Pack3 選項時 Database service 和Analysis Service 確無法選取,我試著繼續執行安裝到
        安裝結束,結果Database service 和Analysis Service 並無更新.其於項目階更新. 執行select @@version 指令. SQL 代號依舊停留在Service Pack2.想請問各位大大如何
        安裝SQL 2005 Service Pack3 的 Database Service 和Analysis Service 在DB Cluster.  thanks. 

    grace
    2009年12月9日 下午 03:43
    |
  • Question
    登入以投票
    0
    登入以投票
    Install it on active node, can only patch ssis and client tools on passive node. Sp3 readme file has details.
    2009年12月10日 上午 01:14
    |
  • Question
    登入以投票
    0
    登入以投票

    Hi,
    Please take a look at the following article.
    http://www.db-staff.com/index.php/microsoft-sql-server/87-upgrade-sql-2005-cluster-to-sp3
    Microsoft Online Community Support
    2009年12月10日 上午 04:14
    |
  • Question
    登入以投票
    0
    登入以投票
    Hi rmiao,
                 thanks for your information.   
                  
                 the first time, I did not select feature of database and analysis service on SP3. but others SQL Service had been upgrade SP3 successfully on passive node.   After I try to re-upgrade service pack3 of database service and analysis service on active node.  it was fail.  how could i find fail error message from log.  
                 From SP3 readme file mention I should install SP3 on active node.  before I install SP3 on passive node.  do I need to remove those upgrade to SP3 Service. and try to upgrade SP3 on active node.  could you give any suggestion?  thanks.               
                   
    grace
    2009年12月10日 下午 05:07
    |
  • Question
    登入以投票
    0
    登入以投票
    Dear KeFang,
                         thanks for your information.   After read this article, I know I did the wrong step.  I should install SP3 on active node.   but I install on passive node.  I try to upgrade again on active node.  active node allow me to selectg feature of database and analysis service. but it was not install  successful. Server only display install fail.  after message send to microsoft, error message close by itself.   I am confused that how could I find  the error message.  what should I do not.  Could you give me some suggestion. thanks.
    grace
    2009年12月10日 下午 05:17
    |
  • Question
    登入以投票
    0
    登入以投票
    You can take look at installation log files, defaulot path is C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG.
    2009年12月11日 上午 01:28
    |
  • Question
    登入以投票
    0
    登入以投票
    Dear Rmiao,
                      thanks. I will check log information.  If I still have question, I will discuss with you.
    grace
    2009年12月12日 上午 08:17
    |
  • Question
    登入以投票
    0
    登入以投票

    Hi Rmiao,

                 After look at log.   Los shows below message.   Could you give me some suggestion? what should I solve below error message.  thanks 


    Products Disqualified & Reason

    Processes Locking Files

    Process Name                   Feature                      TYPE                                USER NAME
    MSSQLSERVER                  Database Service       服務 (Service)                   5468
    resrcmin.exe                     Database Service       應用程式 (Application)        Cluster-DB\ib_cluster 4176 
    srmagent.exe                    Database Service       應用程式 (application)        AUTHORITY\SYSTEM 3140
    SQL SERVERAGENT            Database Service       服務 (Service)                  4524
    SQLBrowser                      Database Service       服務 (Service)                  3068
    MSSQLServerOLAPService Analysis Service         服務 (Service)                  5548


    Product                              | Database Services (MSSQLSERVER)     
    Product Version (Previous)   | 3233
    Product Version (Final)         |
    Status                                | 失敗
    Log File                              | 11009
    Error Description                 | 沒有Passive 節點己成功修補

     

    Product                              | Analysis Services (MSSQLSERVER)     
    Product Version (Previous)   | 3233
    Product Version (Final)         |
    Status                                 | 失敗
    Log File                               | 11009
    Error Description                 | 沒有Passive 節點己成功修補

     

    SUMMARY
           沒有Passive 節點己成功修補
           Exit Code Returned:11009

    grace
    2009年12月14日 下午 03:51
    |
  • Question
    登入以投票
    0
    登入以投票
    Can't tell from that. Should generates several log files, did you check all of them? One thing to try: failover sql resources to passive node then apply sp again.
    2009年12月14日 下午 04:03
    |
  • Question
    登入以投票
    0
    登入以投票

    Dear Rmiao,
                      Previous mail I only put part of summary.txt information.    After check hotfix.log,   I am install database and analysis service with SP3 on active node (TWASPRTW010016).  Why hotfix.log shows passive node (twasprtw010015) informaiton
    "Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015"
                      I went to check active and passive node's service.  When I install sp3 active node, should I disable task scheduler service and SQL Server Browser service on passive node. then reinstall sp3 on active node.   Below is part of HotFix log.  Hope you can give me some suggestion from hotfix log.  thanks.

    Below is part of HotFix log  

    12/07/2009 02:44:44.592 Registry: Opened registry key "System\CurrentControlSet\Control\Session Manager"
    12/07/2009 02:44:44.607 Registry: Cannot read registry key value "PendingFileRenameOperations", error 0
    12/07/2009 02:44:47.607 Authenticating user using Windows Authentication
    12/07/2009 02:44:48.404 Authenticating user using Windows Authentication
    12/07/2009 02:44:48.420 Validating database connections using Windows Authentication
    12/07/2009 02:44:48.795 Pre-script database connection check was successful - proceeding with script execution
    12/07/2009 02:44:49.217 Received sysadmin status for instance: MSSQLSERVER
    12/07/2009 02:44:49.233 Validating database connections using Windows Authentication
    12/07/2009 02:44:49.623 Pre-script database connection check was successful - proceeding with script execution
    12/07/2009 02:44:49.639 User authentication was successful
    12/07/2009 02:45:05.202 Authenticating user using Windows Authentication
    12/07/2009 02:45:05.592 Authenticating user using Windows Authentication
    12/07/2009 02:45:05.608 Validating database connections using Windows Authentication
    12/07/2009 02:45:05.999 Pre-script database connection check was successful - proceeding with script execution
    12/07/2009 02:45:06.452 Received sysadmin status for instance: MSSQLSERVER
    12/07/2009 02:45:06.467 Validating database connections using Windows Authentication
    12/07/2009 02:45:07.030 Pre-script database connection check was successful - proceeding with script execution
    12/07/2009 02:45:07.045 User authentication was successful
    12/07/2009 02:47:02.861 Registry: Read registry key value "EnableErrorReporting", DWORD value = 1
    12/07/2009 02:47:02.877 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
    12/07/2009 02:47:02.892 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
    12/07/2009 02:47:02.908 Registry: Read registry key value "CustomerFeedBack", DWORD value = 1
    12/07/2009 02:47:02.923 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
    12/07/2009 02:47:02.939 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
    12/07/2009 02:47:14.002 Locked file: Checking for locked files
    12/07/2009 02:47:17.486 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\resources\1033\sqlevn70.rll (MSSQLSERVER [sqlservr.exe] - 5468)
    12/07/2009 02:47:17.564 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\resources\1028\sqlevn70.rll (MSSQLSERVER [sqlservr.exe] - 5468)
    12/07/2009 02:47:17.611 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\resources\1028\xpstar90.rll (MSSQLSERVER [sqlservr.exe] - 5468)
    12/07/2009 02:47:17.877 Locked file: C:\WINDOWS\system32\sqsrvres.dll (resrcmon.exe - 4176)
    12/07/2009 02:47:17.955 Locked file: C:\WINDOWS\system32\sqlctr90.dll (srmagent.exe - 3140)
    12/07/2009 02:47:18.080 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlsvc90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4524)
    12/07/2009 02:47:18.111 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\xpstar90.dll (MSSQLSERVER [sqlservr.exe] - 5468)
    12/07/2009 02:47:18.143 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlos.dll (MSSQLSERVER [sqlservr.exe] - 5468)
    12/07/2009 02:47:18.174 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\xpsqlbot.dll (MSSQLSERVER [sqlservr.exe] - 5468)
    12/07/2009 02:47:18.189 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\xplog70.dll (MSSQLSERVER [sqlservr.exe] - 5468)
    12/07/2009 02:47:18.252 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlservr.exe (MSSQLSERVER [sqlservr.exe] - 5468)
    12/07/2009 02:47:18.330 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\batchparser90.dll (MSSQLSERVER [sqlservr.exe] - 5468)
    12/07/2009 02:47:18.346 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\batchparser90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4524)
    12/07/2009 02:47:18.393 Locked file: C:\WINDOWS\system32\sqlagentctr90.dll (srmagent.exe - 3140)
    12/07/2009 02:47:18.502 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\resources\1028\sqlagent90.rll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4524)
    12/07/2009 02:47:18.580 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqldtsss90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4524)
    12/07/2009 02:47:18.611 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlrepss90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4524)
    12/07/2009 02:47:18.627 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlolapss90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4524)
    12/07/2009 02:47:18.658 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlagent90.exe (SQLSERVERAGENT [SQLAGENT90.EXE] - 4524)
    12/07/2009 02:47:18.830 Locked file: C:\Program Files\microsoft sql server\90\shared\resources\1028\msmdsrv.rll (SQLBrowser [sqlbrowser.exe] - 3068)
    12/07/2009 02:47:18.908 Locked file: C:\Program Files\microsoft sql server\90\shared\msmdredir.dll (SQLBrowser [sqlbrowser.exe] - 3068)
    12/07/2009 02:47:19.221 Locked file: C:\Program Files\microsoft sql server\90\shared\sqlbrowser.exe (SQLBrowser [sqlbrowser.exe] - 3068)
    12/07/2009 02:47:24.862 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\msmdctr90.dll (srmagent.exe - 3140)
    12/07/2009 02:47:25.362 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\resources\1028\msmdsrv.rll (MSSQLServerOLAPService [msmdsrv.exe] - 5548)
    12/07/2009 02:47:25.565 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\sqlboot.dll (MSSQLServerOLAPService [msmdsrv.exe] - 5548)
    12/07/2009 02:47:25.596 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\msmgdsrv.dll (MSSQLServerOLAPService [msmdsrv.exe] - 5548)
    12/07/2009 02:47:25.690 Locked file: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\msmdsrv.exe (MSSQLServerOLAPService [msmdsrv.exe] - 5548)
    12/07/2009 02:47:25.877 Locked file: C:\Program Files\microsoft sql server\90\shared\resources\1028\msmdsrv.rll (SQLBrowser [sqlbrowser.exe] - 3068)
    12/07/2009 02:47:25.893 Locked file: C:\Program Files\microsoft sql server\90\shared\msmdredir.dll (SQLBrowser [sqlbrowser.exe] - 3068)
    12/07/2009 02:47:25.924 Locked file: C:\Program Files\microsoft sql server\90\shared\sqlbrowser.exe (SQLBrowser [sqlbrowser.exe] - 3068)
    12/07/2009 02:47:39.018 Attempting to pause the 32 bit ngen queue
    12/07/2009 02:47:39.878 Installing product: SQL9
    12/07/2009 02:47:39.893 Installing instance: MSSQLSERVER
    12/07/2009 02:47:39.909 Enumerating passive cluster nodes
    12/07/2009 02:47:39.940 Patching available passive node: TWASPRTW010015
    12/07/2009 02:47:39.940 Patching passive node: TWASPRTW010015
    12/07/2009 02:47:39.956 Waiting for first completed passive node
    12/07/2009 02:47:40.159 Task Scheduler: Created remote folder for product instance target \\TWASPRTW010015
    12/07/2009 02:48:41.723 Task Scheduler: Transferred payload to remote product instance target \\TWASPRTW010015
    12/07/2009 02:48:41.738 Task Scheduler: Transferred payload to remote product instance target \\TWASPRTW010015
    12/07/2009 02:48:41.801 Task Scheduler: Created new scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:48:41.817 Task Scheduler: SaveTaskToDisk(): Got task interface
    12/07/2009 02:48:41.848 Task Scheduler: SaveTaskToDisk(): Error -2147216624
    12/07/2009 02:48:42.879 Task Scheduler: Saved new scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:48:42.895 Task Scheduler: Created scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:48:42.926 Task Scheduler: Started scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:48:42.942 Task Scheduler: Started scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:48:45.973 Task Scheduler: Scheduled task for product instance target has completed
    12/07/2009 02:48:45.989 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:48:51.020 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:48:56.051 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:49:01.083 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:49:06.145 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:49:11.175 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:49:16.205 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:49:21.251 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:49:26.282 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:49:31.313 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:49:36.329 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:49:41.360 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:49:46.391 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:49:51.423 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:49:56.470 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:50:01.501 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:50:06.532 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:50:11.564 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:50:16.595 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:52:32.458 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:52:37.489 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:52:42.521 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:52:47.583 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:52:52.615 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:52:57.646 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:53:02.740 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:53:07.771 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:53:12.803 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:53:17.834 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:53:22.866 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:53:27.897 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:57:49.747 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:57:54.779 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:57:59.810 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:58:04.841 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:58:09.904 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:58:14.920 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:58:19.967 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:58:24.983 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:58:30.014 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:58:35.061 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:58:40.077 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:58:45.108 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:58:50.140 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 02:58:55.171 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:03:47.256 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:03:52.304 Task Scheduler: Error, timed out waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:03:52.319 Task Scheduler: Error, result code for scheduled task for product instance target was not received
    12/07/2009 03:03:52.366 Task Scheduler: Removed scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:03:53.085 Task Scheduler: Removed remote folder for product instance target \\TWASPRTW010015
    12/07/2009 03:03:53.100 Error, remote process failed for product instance target
    12/07/2009 03:03:53.116 Exit code for passive node: TWASPRTW010015 = 1603
    12/07/2009 03:03:55.007 The following exception occurred: 沒有 Passive 節點已成功修補  Date: 12/07/2009 03:03:54.991  File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\instance.cpp  Line: 3510
    12/07/2009 03:03:59.507 Watson: Param1 = Unknown
    12/07/2009 03:03:59.538 Watson: Param2 = 0x2b01
    12/07/2009 03:03:59.554 Watson: Param3 = Unknown
    12/07/2009 03:03:59.569 Watson: Param4 = 0x0
    12/07/2009 03:03:59.585 Watson: Param5 = instance.cpp@3510
    12/07/2009 03:03:59.616 Watson: Param6 = Unknown
    12/07/2009 03:03:59.632 Watson: Param7 = SQL9
    12/07/2009 03:03:59.647 Watson: Param8 = Hotfix@
    12/07/2009 03:03:59.663 Watson: Param9 = x86
    12/07/2009 03:03:59.679 Watson: Param10 = 4035
    12/07/2009 03:03:59.694 Installed product: SQL9
    12/07/2009 03:03:59.710 Installing product: OLAP9
    12/07/2009 03:03:59.726 Installing instance: MSSQLSERVER
    12/07/2009 03:03:59.757 Enumerating passive cluster nodes
    12/07/2009 03:03:59.772 Patching available passive node: TWASPRTW010015
    12/07/2009 03:03:59.788 Patching passive node: TWASPRTW010015
    12/07/2009 03:03:59.804 Waiting for first completed passive node
    12/07/2009 03:03:59.944 Task Scheduler: Created remote folder for product instance target \\TWASPRTW010015
    12/07/2009 03:05:05.212 Task Scheduler: Transferred payload to remote product instance target \\TWASPRTW010015
    12/07/2009 03:05:05.212 Task Scheduler: Transferred payload to remote product instance target \\TWASPRTW010015
    12/07/2009 03:05:05.258 Task Scheduler: Created new scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:05:05.274 Task Scheduler: SaveTaskToDisk(): Got task interface
    12/07/2009 03:05:05.305 Task Scheduler: SaveTaskToDisk(): Error -2147216624
    12/07/2009 03:05:06.337 Task Scheduler: Saved new scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:05:06.352 Task Scheduler: Created scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:05:06.415 Task Scheduler: Started scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:05:06.430 Task Scheduler: Started scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:05:09.462 Task Scheduler: Scheduled task for product instance target has completed
    12/07/2009 03:05:09.477 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:05:14.509 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:05:19.571 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:05:24.603 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:05:29.634 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:05:34.665 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:05:39.697 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:05:44.728 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:05:49.760 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:05:54.791 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:05:59.822 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:06:04.854 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:06:09.885 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:06:14.917 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:06:19.948 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:06:24.979 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:06:30.011 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:06:35.042 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:06:40.073 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:06:45.105 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:06:50.121 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:06:55.152 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:07:00.183 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:07:05.230 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:07:10.246 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:07:15.293 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:09:26.453 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:09:31.484 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:09:36.500 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:09:41.594 Task Scheduler: Waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:20:16.376 Task Scheduler: Error, timed out waiting for exit code from scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:20:16.391 Task Scheduler: Error, result code for scheduled task for product instance target was not received
    12/07/2009 03:20:16.407 Task Scheduler: Removed scheduled task for product instance target \\TWASPRTW010015
    12/07/2009 03:20:17.719 Task Scheduler: Removed remote folder for product instance target \\TWASPRTW010015
    12/07/2009 03:20:17.813 Error, remote process failed for product instance target
    12/07/2009 03:20:17.938 Exit code for passive node: TWASPRTW010015 = 1603
    12/07/2009 03:20:19.844 The following exception occurred: 沒有 Passive 節點已成功修補  Date: 12/07/2009 03:20:19.844  File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\instance.cpp  Line: 3510
    12/07/2009 03:20:24.688 Watson: Param1 = Unknown
    12/07/2009 03:20:24.720 Watson: Param2 = 0x2b01
    12/07/2009 03:20:24.720 Watson: Param3 = Unknown
    12/07/2009 03:20:24.735 Watson: Param4 = 0x0
    12/07/2009 03:20:24.751 Watson: Param5 = instance.cpp@3510
    12/07/2009 03:20:24.766 Watson: Param6 = Unknown
    12/07/2009 03:20:24.782 Watson: Param7 = OLAP9
    12/07/2009 03:20:24.798 Watson: Param8 = Hotfix@
    12/07/2009 03:20:24.798 Watson: Param9 = x86
    12/07/2009 03:20:24.813 Watson: Param10 = 4035
    12/07/2009 03:20:24.829 Installed product: OLAP9
    12/07/2009 03:20:24.860 Hotfix package completed
    12/07/2009 03:20:24.876 Attempting to continue the 32 bit ngen queue

    grace
    2009年12月17日 上午 07:58
    |
  • Question
    登入以投票
    0
    登入以投票
    When apply sp for sql engine and so on cluster, it'll apply on all related nodes in the cluster and passive ones first.
    2009年12月17日 下午 03:10
    |
  • Question
    登入以投票
    0
    登入以投票
    Hi rmiao,
                  May I double check with Your means that  when install service pack3, SP3 will automatically check and install on passive node first.  In the first time, I had been install some service with SP3 successful.  thus I try to reinstall database service and analysis service on active node, it  shows message which I post pre-description log.  Do I need to remove all service which has been install sp3 successful service?  such as integration service,  afer remove and reinstall sp3 withe all related node again on active node.  May I right?    If I am not correct, please kindly give me some suggestion.  thanks.
    grace
    2009年12月19日 下午 03:22
    |
  • Question
    登入以投票
    0
    登入以投票
    SSIS, client and some other components are not cluster awared, have to apply sp for them on all notes in the cluster. Ensure task scheduler service is running on all nodes and no any people logon to any node except you on active node. 
    2009年12月19日 下午 04:44
    |
  • Question
    登入以投票
    0
    登入以投票
    Dear Rmiao,
                      thanks for your information.  I will try again.
    grace
    2009年12月22日 上午 09:52
    |
  • Question
    登入以投票
    0
    登入以投票

    Problem had been solved.  Stop Passived node (inactive server)  task schedule Service. Active node will continue to insall SP3. 

    grace
    • 已提議為解答 Martin POON 2010年11月3日 下午 03:12
    2010年9月26日 下午 03:08
    |