SQL 2005 mirroring - time taken to fail over?

I'm looking for an easy way to 'measure' the amount of time it takes our principal Database Server to fail over to our mirror Server in which all regular service will be resumed.
Any help would be hugely appreciated 
Thanks guys
ras

http://technet.microsoft.com/en-us/library/ms187465.aspx
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Similar Messages

  • SQL 2005 mirroring : Abrupt Automatic failover

    hi All, 
    We have a SQL 2005 SP4 mirroring  setup of 15 DBs with Principal(P), Mirror(M) & Witness (W).
    We have now seen abrupt DB failovers for some of the databases (yest it was 4 out of 15) from P to M.
    Errors were seen on Witness server as follows for all Dbs that failed over:
    Date 07/01/2015 11:07:48 PM
    Log SQL Server (Current - 08/01/2015 12:00:00 AM)
    Source spid19s
    Message
    The mirroring connection to "TCP://<server.domain.com>:5022" has timed out for database "<DBName>" after 10 seconds without a response.  Check the service and network connections.
    Actions taken:
    1. Network and Firewall team reverted that no error detected and no network traffic between the witness server and db server during the db auto failover period.
    2. On the system side, we have verified that no hardware error found on either VM or SAN storage, and no Symantec SQL backup jobs running nor anti virus scanning during the db auto failover period too.
    3. We did see some high amount of IO activity on P server around failover time. Some IO errors similar to below were seen, however point to note is these errors were not only for the DBs that failed over, but for others including TEMPDB:
    Date 07/01/2015 11:07:38 PM
    Log SQL Server (Current - 08/01/2015 4:06:00 AM)
    Source spid2s
    Message
    SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [R:\SQLDATA\MSSQL.1\MSSQL\Data\<DBName>.mdf] in database [DBName] (5).  The OS file handle is 0x000000000000095C.  The offset of the
    latest long I/O is: 0x0000054ff22000
    Questions:
    1. I assumed that the Witness keeps polling P & M on DB mirroring endpoints (in our case 5022) to check that the DBs are online, but Network team says there is no activity on that port, is my understanding correct?
    2. Is there any other reason for DB failover ? 
    Link referred:  
    http://dba.stackexchange.com/questions/22402/what-can-cause-a-mirroring-session-to-timeout-then-failover-sql-server-2005
    http://msdn.microsoft.com/en-us/library/ms179344(v=sql.90).aspx
    Any help is highly appreciated!!!
    Regards,
    Mandar

    This is common with Mirroring server it is not as resilient to changes as log shipping. Are you aware about
    below fact although not directly related to your question
    If you plan to use high-safety mode with automatic failover, the normal load on each failover partner should be less than 50 percent of the CPU. If your work load overloads the CPU, a failover partner might be unable to ping the other server instances in
    the mirroring session. This causes a unnecessary failover. If you cannot keep the CPU usage under 50 percent, we recommend that you use either high-safety mode without automatic failover or high-performance mode.
    Now to your problem
    The mirroring connection to "TCP://<server.domain.com>:5022" has timed out for database "<DBName>" after 10 seconds without a response.  Check the service and network connections.
    I would say there was network dip for more than 10 seconds and since default failover time is 10 seconds and for few databases witness thought principal cannot be reached it initiated failover.
    Network team is incorrect to say there was no dip (its common with NOC team not to take responsibility)
    This Support Article is worth reading specially the network part
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • DPM 2010 SharePoint 2007 and SQL 2005 long time Recovery point

    Hi, i have two farms with two dedicated DPM for each of them
    SP 2010 with SQL 2008 R2
    SP 2007 with SQL 2005
    While recovery point is running for 2010 multiple databases are taken simultaneously while in 2007 only one database at time in sequential order which leads in large time for recovery point of farm.
    any recommendations or modification known for this behavior
    Thanks
    Mina

    Hi,
    I have not tried this with SharePoint workload - but give this a try.
    Steps to enable parallel backups for SQL 2005 databases:
    1. The fix in SQL Writer to enable parallel backups has been rolled out as part of SQL server SP4. So please update SQL Server 2005 to SP4.
    2. On DPM Server, create Registry Key “SQL2005_ParallelBackup” under “HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration”
    3. Create String Value with Name equals FQDN of SQL Server
    and empty value, under registry key “SQL2005_ParallelBackup”
    Let me know if that worked.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This
    posting is provided "AS IS" with no warranties, and confers no rights.

  • Two wistnesses in a SQL Server fail over group

    Is it possible to have two witnesses in a SQL Server Always on Availability Group Fail Over Cluster? Our goal is to have redundant witnesses in an Azure availability set.
    Thanks,
    Mike

    AlwaysOn uses Windows Failover Clustering for quorum.  See, eg Understanding Quorum Configurations in a Failover Cluster
    You can do this, but with Dynamic Quorum it's probably not helpful.  If you loose your witness vote, the cluster will adjust the quorum requirements.
    David
    David http://blogs.msdn.com/b/dbrowne/

  • SQL 2005 cluster rejects SQL logins when in failed over state

    When SQL 2005 SP4 on Windows 2003 server cluster is failed over from Server_A to Server_B, it rejects all SQL Server logins. domain logins are OK. The message is "user is not associated with a trusted server connection", then the IP of the
    client. This is error 18452. Anyone know how to fix this? They should work fine from both servers. We think this started just after installing SP4.
    DaveK

    Hello,
    The connection string is good, you're definitely using sql auth.
    LoginMode on Server_B is REG_DWORD 0x00000001 (1) LoginMode on Server_A is REG_DWORD 0x00000002 (2) Looks like you are on to something. I will schedule another test failover. I assume a 2 is mixed mode? If so, why would SQL allow two different modes
    on each side of a cluster?
    You definitely have a registry replication issue, or at the very least a registry that isn't in sync with the cluster. This could happen for various reasons, none of which we'll probably find out about now, but never the less...
    A good test would be to set it to windows only on Node A, wait a minute and then set it to Windows Auth and see if that replicates the registry setting across nodes correctly - this is actually the windows level and doesn't have anything to do with SQL Server.
    SQL Server reads this value from the registry and it is not stored inside any databases (read, nothing stored in the master database) as such it's a per machine setting. Since it's not set correctly on Node B, when SQL server starts up it correctly reads
    that registry key and acts on it as it should. The culprit isn't SQL Server, it's Windows Clustering.
    Hopefully this makes a little more sense now. You can actually just edit the registry setting to match Node A and fail over to B, everything should work correctly. It doesn't help you with a root cause analysis which definitely needs to be done as who knows
    what else may not be correctly in sync.
    Sean Gallardy | Blog |
    Twitter

  • OCS 2007 R2 with SQL 2005 database mirroring failover?

    We have OCS 2007 Enterprise Edition installed fine and with the databases mirrored to a backup server/location.  I'm testing our environment for a potential disaster, including losing our primary SQL server (SQL 2005).  I fail the databases over and update the backend pool to the backup SQL server name, but we cannot connect via Office Communicator and I see this error on the OCS server:
    OCS User Services, error category 1006, event id 30962:
    Connection to back-end database succeeded, but failed to execute registration stored procedure on the back-end. This error should not occur under normal operating conditions. Contact product support.
    Back-end Server: databkp Database: rtc Sql native error: 515 Connection string of:
    driver={SQL Native Client};Trusted_Connection=yes;AutoTranslate=no;server=databkp;database=rtc;
    Cause: Possible issues with back-end database.
    Resolution:
    Ensure the back-end is functioning correctly.
    Can anyone shed some light on this SQL 515 error?  Thanks in advance!
    -Erik

    We're having a similar issue but with error number 601. I've tried a million different things aside from restoring the database, which may be next. I tried editing the procedure and I *think* I edited the right lines 77 and 105 for me. Changed:
        delete dbo.DbConfigDateTime
          from @DbTime as t
         where dbo.DbConfigDateTime.Name = t.ValueName
           and t.StoredDbName = N'rtc'
           and t.Value is null
    to:
        delete dbo.DbConfigDateTime
          from @DbTime as t
         where dbo.DbConfigDateTime.Name = t.ValueName
           and t.StoredDbName = N'rtc'
           and t.Value is not null
    and 
        delete rtcdyn.dbo.DbConfigDateTime
        from @DbTime as t
        where rtcdyn.dbo.DbConfigDateTime.Name = t.ValueName
        and t.StoredDbName = N'rtcdyn'
        and t.Value is null
    to:
        delete rtcdyn.dbo.DbConfigDateTime
        from @DbTime as t
        where rtcdyn.dbo.DbConfigDateTime.Name = t.ValueName
        and t.StoredDbName = N'rtcdyn'
        and t.Value is not null
    Not sure if that's where the modification is supposed to go. Any clarity here? Anyone else get a 601 error?

  • SQL Server 2014 Always on HA takes 8-14 seconds to fail over. Application side timeouts occur

    Hi All,
    I have a very similar post in the SQL Server 2014 forums too (https://social.technet.microsoft.com/Forums/sqlserver/en-US/adb5e338-907e-4405-aa62-d3ea93c7a98a/sql-server-2014-always-on-ha-takes-814-seconds-to-fail-over-application-side-timeouts-occur?forum=sqldisasterrecovery) -
    advice in the end was to post a question here.
    SQL Server Nodes, 2014 (12.0.2480.0)
    1 Share witness (on separate subnet)
    1 Cluster
    1 Listener
    I have been testing the response time to failovers – both manual (right-click, fail over in SSMS) and Automatic (shut down the primary host). The way I am testing response is to have a SSMS query running on my desktop, connected to the listener querying
    a small table and hit execute.
    The Query response time, from execute to receiving the result, has been between 8 and 14 seconds based on my testing. My previous experience (in a separate environment) showed around 2 second fail over times in a very similar configuration.
    Availability DB is 200Mb and is not actively used. The nodes are synchronised.
    SQL Server Hosts: Windows 2012, 2 cpu, 8gb RAM.
    Questions:
    1: It’s a big question but what should I expect for a ‘normal’ fail over time. Keep in mind this scenario is about as simple as it gets.
    2: As it stands an 8 to 14 second ‘outage’ could cause some applications to time out. Or am I being un-reasonable? I am seeing the very simple query in SSMS to time out with this:
    Msg 983, Level 14, State 1, Line 2
    Unable to access availability database 'DATABASE' because the database replica is not in the PRIMARY or SECONDARY role. Connections to
    an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later.
    Cluster logs are long - this section accounts for 8 seconds of the 11 second outage I experienced. I can supply the full log if required. Also this log is just the 2 cluster nodes, I removed the witness share to make sure it was as simple as possible.
    00001090.00002128::2015/02/25-03:05:08.255 INFO  [GEM] Node 2: Deleting [1:65 , 1:71] (both included) as it has been ack'd by every node
    00001ee4.00002130::2015/02/25-03:05:10.107 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
    00001090.00002128::2015/02/25-03:05:11.888 INFO  [GEM] Node 2: Deleting [1:72 , 1:73] (both included) as it has been ack'd by every node
    00001090.00002698::2015/02/25-03:05:11.889 INFO  [GUM] Node 2: Processing RequestLock 2:49
    00001090.00002128::2015/02/25-03:05:11.890 INFO  [GUM] Node 2: Processing GrantLock to 2 (sent by 1 gumid: 67)
    00001090.00002698::2015/02/25-03:05:11.890 INFO  [GUM] Node 2: executing request locally, gumId:68, my action: /dm/update, # of updates: 1
    00001090.00002128::2015/02/25-03:05:12.890 INFO  [GEM] Node 2: Deleting [1:74 , 1:74] (both included) as it has been ack'd by every node
    00001ee4.00002130::2015/02/25-03:05:15.107 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
    00001090.00002128::2015/02/25-03:05:16.988 INFO  [GUM] Node 2: Processing RequestLock 1:28
    Thanks in advance.
    Keegan

    Hi Keegan,
    From these event log , what I can see is "Sending request Netname" wasted the time .
    Could you please tell us the network configuration of that cluster nodes ?
    If I recall correctly , it is recommended to only remain Tcp/IP protocol and disable NetBIOS over TCP/IP for "Private Network" , also do not configure DNS/Wins default gateway for "Private Network" :
    https://support.microsoft.com/kb/258750?wa=wsignin1.0
    After that please test again .
    Best Regards,
    Elton JI
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

  • Installation failed SQL 2005

    Hi all ~ I have problem on installing SQL 2005: please have a look on the following log:
    === Verbose logging started: 2/23/2015  10:59:24  Build type: SHIP UNICODE 4.05.6002.00  Calling process: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe ===
    MSI (c) (FC:98) [10:59:24:019]: Resetting cached policy values
    MSI (c) (FC:98) [10:59:24:019]: Machine policy value 'Debug' is 0
    MSI (c) (FC:98) [10:59:24:019]: ******* RunEngine:
               ******* Product: {90A40409-6000-11D3-8CFE-0150048383C9}
               ******* Action:
               ******* CommandLine: **********
    MSI (c) (FC:98) [10:59:24:020]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (FC:98) [10:59:24:020]: Grabbed execution mutex.
    MSI (c) (FC:98) [10:59:24:022]: Cloaking enabled.
    MSI (c) (FC:98) [10:59:24:022]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (FC:98) [10:59:24:022]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (EC:B8) [10:59:24:030]: Running installation inside multi-package transaction {90A40409-6000-11D3-8CFE-0150048383C9}
    MSI (s) (EC:B8) [10:59:24:030]: Grabbed execution mutex.
    MSI (s) (EC:5C) [10:59:24:032]: Resetting cached policy values
    MSI (s) (EC:5C) [10:59:24:032]: Machine policy value 'Debug' is 0
    MSI (s) (EC:5C) [10:59:24:032]: ******* RunEngine:
               ******* Product: {90A40409-6000-11D3-8CFE-0150048383C9}
               ******* Action:
               ******* CommandLine: **********
    MSI (s) (EC:5C) [10:59:24:032]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (EC:5C) [10:59:24:038]: SRSetRestorePoint skipped for this transaction.
    MSI (s) (EC:5C) [10:59:24:039]: End dialog not enabled
    MSI (s) (EC:5C) [10:59:24:039]: Original package ==> C:\WINDOWS\Installer\180ca.msi
    MSI (s) (EC:5C) [10:59:24:039]: Package we're running from ==> C:\WINDOWS\Installer\180ca.msi
    MSI (s) (EC:5C) [10:59:24:043]: APPCOMPAT: looking for appcompat database entry with ProductCode '{90A40409-6000-11D3-8CFE-0150048383C9}'.
    MSI (s) (EC:5C) [10:59:24:043]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (EC:5C) [10:59:24:050]: MSCOREE already loaded, using loaded copy
    MSI (s) (EC:5C) [10:59:24:054]: Opening existing patch 'C:\WINDOWS\Installer\57492f7.msp'.
    MSI (s) (EC:5C) [10:59:24:054]: Note: 1: 2203 2: C:\WINDOWS\Installer\57492f7.msp 3: -2147287038
    MSI (s) (EC:5C) [10:59:24:054]: Couldn't find local patch 'C:\WINDOWS\Installer\57492f7.msp'. Looking for it at its source.
    MSI (s) (EC:5C) [10:59:24:054]: Resolving Patch source.
    MSI (s) (EC:5C) [10:59:24:054]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (EC:5C) [10:59:24:054]: User policy value 'DisableMedia' is 0
    MSI (s) (EC:5C) [10:59:24:054]: Machine policy value 'AllowLockdownMedia' is 0
    MSI (s) (EC:5C) [10:59:24:054]: SOURCEMGMT: Media enabled only if package is safe.
    MSI (s) (EC:5C) [10:59:24:054]: SOURCEMGMT: Looking for sourcelist for product {34E1EB8F-BDB2-475C-BD80-A86217C41B4D}
    MSI (s) (EC:5C) [10:59:24:054]: SOURCEMGMT: Adding {34E1EB8F-BDB2-475C-BD80-A86217C41B4D}; to potential sourcelist list (pcode;disk;relpath).
    MSI (s) (EC:5C) [10:59:24:055]: SOURCEMGMT: Now checking product {34E1EB8F-BDB2-475C-BD80-A86217C41B4D}
    MSI (s) (EC:5C) [10:59:24:055]: SOURCEMGMT: Media is enabled for product.
    MSI (s) (EC:5C) [10:59:24:055]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
    MSI (s) (EC:5C) [10:59:24:055]: SOURCEMGMT: Processing net source list.
    MSI (s) (EC:5C) [10:59:24:055]: Note: 1: 1402 2: UNKNOWN\Net 3: 2
    MSI (s) (EC:5C) [10:59:24:055]: Note: 1: 1706 2: -2147483647 3: OWC11SP3.MSP
    MSI (s) (EC:5C) [10:59:24:055]: SOURCEMGMT: Processing media source list.
    MSI (s) (EC:5C) [10:59:25:063]: SOURCEMGMT: Resolved source to: 'OWC11SP3.MSP'
    MSI (s) (EC:5C) [10:59:51:327]: Note: 1: 1314 2: OWC11SP3.MSP
    MSI (s) (EC:5C) [10:59:51:327]: Unable to create a temp copy of patch 'OWC11SP3.MSP'.
    MSI (s) (EC:5C) [10:59:51:327]: Searching provided command line patches for patch code {34E1EB8F-BDB2-475C-BD80-A86217C41B4D}
    MSI (s) (EC:5C) [10:59:51:329]: Note: 1: 1708
    MSI (s) (EC:5C) [10:59:51:329]: Product: Microsoft Office 2003 Web Components -- Installation failed.
    MSI (s) (EC:5C) [10:59:51:330]: Windows Installer installed the product. Product Name: Microsoft Office 2003 Web Components. Product Version: 11.0.6558.0. Product Language: 1033. Installation success or error status: 1635.
    MSI (s) (EC:5C) [10:59:51:332]: MainEngineThread is returning 1635
    MSI (s) (EC:B8) [10:59:51:332]: No System Restore sequence number for this installation.
    This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package.
    C:\WINDOWS\Installer\180ca.msi
    MSI (s) (EC:B8) [10:59:51:333]: User policy value 'DisableRollback' is 0
    MSI (s) (EC:B8) [10:59:51:333]: Machine policy value 'DisableRollback' is 0
    MSI (s) (EC:B8) [10:59:51:333]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (EC:B8) [10:59:51:334]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (EC:B8) [10:59:51:334]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (EC:B8) [10:59:51:335]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (EC:B8) [10:59:51:335]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (EC:B8) [10:59:51:335]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (EC:B8) [10:59:51:335]: Restoring environment variables
    MSI (c) (FC:98) [10:59:51:337]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (FC:98) [10:59:51:337]: MainEngineThread is returning 1635
    === Verbose logging stopped: 2/23/2015  10:59:51 ===
    Please help help

    this problem solved, i replace back the .msi to the windows\installer, now i have another probelm::
    === Verbose logging started: 2/23/2015  14:02:33  Build type: SHIP UNICODE 4.05.6002.00  Calling process: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe ===
    MSI (c) (44:50) [14:02:33:615]: Resetting cached policy values
    MSI (c) (44:50) [14:02:33:615]: Machine policy value 'Debug' is 0
    MSI (c) (44:50) [14:02:33:615]: ******* RunEngine:
               ******* Product: {E46A76D1-9FB9-4770-BA24-3975EF4D120A}
               ******* Action:
               ******* CommandLine: **********
    MSI (c) (44:50) [14:02:33:616]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (44:50) [14:02:33:616]: Grabbed execution mutex.
    MSI (c) (44:50) [14:02:33:618]: Cloaking enabled.
    MSI (c) (44:50) [14:02:33:618]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (44:50) [14:02:33:619]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (B8:9C) [14:02:33:626]: Running installation inside multi-package transaction {E46A76D1-9FB9-4770-BA24-3975EF4D120A}
    MSI (s) (B8:9C) [14:02:33:626]: Grabbed execution mutex.
    MSI (s) (B8:64) [14:02:33:626]: Resetting cached policy values
    MSI (s) (B8:64) [14:02:33:626]: Machine policy value 'Debug' is 0
    MSI (s) (B8:64) [14:02:33:626]: ******* RunEngine:
               ******* Product: {E46A76D1-9FB9-4770-BA24-3975EF4D120A}
               ******* Action:
               ******* CommandLine: **********
    MSI (s) (B8:64) [14:02:33:626]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (B8:64) [14:02:33:632]: SRSetRestorePoint skipped for this transaction.
    MSI (s) (B8:64) [14:02:33:632]: End dialog not enabled
    MSI (s) (B8:64) [14:02:33:633]: Original package ==> C:\WINDOWS\Installer\23e28752.msi
    MSI (s) (B8:64) [14:02:33:633]: Package we're running from ==> C:\WINDOWS\Installer\23e28752.msi
    MSI (s) (B8:64) [14:02:33:637]: APPCOMPAT: looking for appcompat database entry with ProductCode '{E46A76D1-9FB9-4770-BA24-3975EF4D120A}'.
    MSI (s) (B8:64) [14:02:33:637]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (B8:64) [14:02:33:644]: MSCOREE already loaded, using loaded copy
    MSI (s) (B8:64) [14:02:33:648]: Machine policy value 'DisablePatch' is 0
    MSI (s) (B8:64) [14:02:33:648]: Machine policy value 'AllowLockdownPatch' is 0
    MSI (s) (B8:64) [14:02:33:648]: Machine policy value 'DisableLUAPatching' is 0
    MSI (s) (B8:64) [14:02:33:648]: Machine policy value 'DisableFlyWeightPatching' is 0
    MSI (s) (B8:64) [14:02:33:649]: APPCOMPAT: looking for appcompat database entry with ProductCode '{E46A76D1-9FB9-4770-BA24-3975EF4D120A}'.
    MSI (s) (B8:64) [14:02:33:649]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (B8:64) [14:02:33:649]: Transforms are not secure.
    MSI (s) (B8:64) [14:02:33:650]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0018_SV53749_MSXML6_1.log'.
    MSI (s) (B8:64) [14:02:33:650]: Command Line: STPSETUPTHREADID=1484 STPSETUPPROCESSID=9540 EXTERNALCONTROL=1 ADDLOCAL=ALL SKIPPENDINGREBOOTCHECK=1 APPGUID={FFFA78A7-BD51-4255-8470-C4D4A85B49F5} REBOOT=ReallySuppress CURRENTDIRECTORY=C:\Program Files\Microsoft
    SQL Server\90\Setup Bootstrap CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=9540
    MSI (s) (B8:64) [14:02:33:650]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{EE6525FC-1729-4E76-A8C1-12C756BA0AD0}'.
    MSI (s) (B8:64) [14:02:33:650]: Product Code passed to Engine.Initialize:           '{E46A76D1-9FB9-4770-BA24-3975EF4D120A}'
    MSI (s) (B8:64) [14:02:33:650]: Product Code from property table before transforms: '{E46A76D1-9FB9-4770-BA24-3975EF4D120A}'
    MSI (s) (B8:64) [14:02:33:650]: Product Code from property table after transforms:  '{E46A76D1-9FB9-4770-BA24-3975EF4D120A}'
    MSI (s) (B8:64) [14:02:33:650]: Product registered: entering maintenance mode
    MSI (s) (B8:64) [14:02:33:650]: Product {E46A76D1-9FB9-4770-BA24-3975EF4D120A} is admin assigned: LocalSystem owns the publish key.
    MSI (s) (B8:64) [14:02:33:650]: Product {E46A76D1-9FB9-4770-BA24-3975EF4D120A} is managed.
    MSI (s) (B8:64) [14:02:33:650]: MSI_LUA: Credential prompt not required, user is an admin
    MSI (s) (B8:64) [14:02:33:650]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
    MSI (s) (B8:64) [14:02:33:650]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
    MSI (s) (B8:64) [14:02:33:651]: Package name retrieved from configuration data: 'msxml6.msi'
    MSI (s) (B8:64) [14:02:33:651]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
    MSI (s) (B8:64) [14:02:33:654]: Note: 1: 2262 2: AdminProperties 3: -2147287038
    MSI (s) (B8:64) [14:02:33:654]: Machine policy value 'DisableMsi' is 1
    MSI (s) (B8:64) [14:02:33:654]: Machine policy value 'AlwaysInstallElevated' is 0
    MSI (s) (B8:64) [14:02:33:654]: User policy value 'AlwaysInstallElevated' is 0
    MSI (s) (B8:64) [14:02:33:654]: Product {E46A76D1-9FB9-4770-BA24-3975EF4D120A} is admin assigned: LocalSystem owns the publish key.
    MSI (s) (B8:64) [14:02:33:654]: Product {E46A76D1-9FB9-4770-BA24-3975EF4D120A} is managed.
    MSI (s) (B8:64) [14:02:33:654]: Running product '{E46A76D1-9FB9-4770-BA24-3975EF4D120A}' with elevated privileges: Product is assigned.
    MSI (s) (B8:64) [14:02:33:654]: PROPERTY CHANGE: Adding STPSETUPTHREADID property. Its value is '1484'.
    MSI (s) (B8:64) [14:02:33:654]: PROPERTY CHANGE: Adding STPSETUPPROCESSID property. Its value is '9540'.
    MSI (s) (B8:64) [14:02:33:654]: PROPERTY CHANGE: Adding EXTERNALCONTROL property. Its value is '1'.
    MSI (s) (B8:64) [14:02:33:654]: PROPERTY CHANGE: Adding ADDLOCAL property. Its value is 'ALL'.
    MSI (s) (B8:64) [14:02:33:654]: PROPERTY CHANGE: Adding SKIPPENDINGREBOOTCHECK property. Its value is '1'.
    MSI (s) (B8:64) [14:02:33:654]: PROPERTY CHANGE: Adding APPGUID property. Its value is '{FFFA78A7-BD51-4255-8470-C4D4A85B49F5}'.
    MSI (s) (B8:64) [14:02:33:654]: PROPERTY CHANGE: Adding REBOOT property. Its value is 'ReallySuppress'.
    MSI (s) (B8:64) [14:02:33:655]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap'.
    MSI (s) (B8:64) [14:02:33:655]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
    MSI (s) (B8:64) [14:02:33:655]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is '1'.
    MSI (s) (B8:64) [14:02:33:655]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '9540'.
    MSI (s) (B8:64) [14:02:33:655]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
    MSI (s) (B8:64) [14:02:33:655]: PROPERTY CHANGE: Adding MsiRestartManagerSessionKey property. Its value is '2bacf19a1da7c4438b188852d7df058c'.
    MSI (s) (B8:64) [14:02:33:655]: RESTART MANAGER: Session opened.
    MSI (s) (B8:64) [14:02:33:655]: TRANSFORMS property is now:
    MSI (s) (B8:64) [14:02:33:655]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.
    MSI (s) (B8:64) [14:02:33:655]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '300'.
    MSI (s) (B8:64) [14:02:33:658]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming
    MSI (s) (B8:64) [14:02:33:660]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\Favorites
    MSI (s) (B8:64) [14:02:33:662]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Network Shortcuts
    MSI (s) (B8:64) [14:02:33:663]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\Documents
    MSI (s) (B8:64) [14:02:33:665]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
    MSI (s) (B8:64) [14:02:33:667]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Recent
    MSI (s) (B8:64) [14:02:33:668]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\SendTo
    MSI (s) (B8:64) [14:02:33:671]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Templates
    MSI (s) (B8:64) [14:02:33:671]: SHELL32::SHGetFolderPath returned: C:\ProgramData
    MSI (s) (B8:64) [14:02:33:673]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Local
    MSI (s) (B8:64) [14:02:33:675]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\Pictures
    MSI (s) (B8:64) [14:02:33:679]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
    MSI (s) (B8:64) [14:02:33:681]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
    MSI (s) (B8:64) [14:02:33:682]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
    MSI (s) (B8:64) [14:02:33:685]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
    MSI (s) (B8:64) [14:02:33:687]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
    MSI (s) (B8:64) [14:02:33:691]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
    MSI (s) (B8:64) [14:02:33:693]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
    MSI (s) (B8:64) [14:02:33:695]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
    MSI (s) (B8:64) [14:02:33:697]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu
    MSI (s) (B8:64) [14:02:33:698]: SHELL32::SHGetFolderPath returned: C:\Users\Administrator\Desktop
    MSI (s) (B8:64) [14:02:33:701]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
    MSI (s) (B8:64) [14:02:33:701]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
    MSI (s) (B8:64) [14:02:33:702]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
    MSI (s) (B8:64) [14:02:33:711]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
    MSI (s) (B8:64) [14:02:33:711]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is '1'.
    MSI (s) (B8:64) [14:02:33:711]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
    MSI (s) (B8:64) [14:02:33:711]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'Sun Life'.
    MSI (s) (B8:64) [14:02:33:711]: PROPERTY CHANGE: Adding COMPANYNAME property. Its value is 'Sun Life Hong Kong Limited'.
    MSI (s) (B8:64) [14:02:33:711]: PROPERTY CHANGE: Adding Installed property. Its value is '00:00:00'.
    MSI (s) (B8:64) [14:02:33:711]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\WINDOWS\Installer\23e28752.msi'.
    MSI (s) (B8:64) [14:02:33:711]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'C:\WINDOWS\Installer\23e28752.msi'.
    MSI (s) (B8:64) [14:02:33:711]: Machine policy value 'MsiDisableEmbeddedUI' is 0
    MSI (s) (B8:64) [14:02:33:711]: EEUI - Disabling MsiEmbeddedUI due to existing external or embedded UI
    MSI (s) (B8:64) [14:02:33:711]: EEUI - Disabling MsiEmbeddedUI for service because it's not a quiet/basic install
    MSI (s) (B8:64) [14:02:33:712]: Note: 1: 2205 2:  3: PatchPackage
    MSI (s) (B8:64) [14:02:33:712]: Machine policy value 'DisableRollback' is 0
    MSI (s) (B8:64) [14:02:33:712]: User policy value 'DisableRollback' is 0
    MSI (s) (B8:64) [14:02:33:712]: PROPERTY CHANGE: Adding UILevel property. Its value is '2'.
    === Logging started: 2/23/2015  14:02:33 ===
    MSI (s) (B8:64) [14:02:33:713]: PROPERTY CHANGE: Adding Preselected property. Its value is '1'.
    MSI (s) (B8:64) [14:02:33:713]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
    MSI (s) (B8:64) [14:02:33:713]: Doing action: INSTALL
    Action start 14:02:33: INSTALL.
    MSI (s) (B8:64) [14:02:33:717]: Running ExecuteSequence
    MSI (s) (B8:64) [14:02:33:717]: Doing action: SkipInstallCA
    MSI (s) (B8:64) [14:02:33:720]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SkipInstallCA'
    MSI (s) (B8:B8) [14:02:33:730]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI92BC.tmp, Entrypoint: SkipInstall
    MSI (s) (B8:B0) [14:02:33:730]: Generating random cookie.
    MSI (s) (B8:B0) [14:02:33:743]: Created Custom Action Server with PID 8820 (0x2274).
    MSI (s) (B8:20) [14:02:33:788]: Running as a service.
    MSI (s) (B8:20) [14:02:33:791]: Hello, I'm your 32bit Impersonated custom action server.
    Action start 14:02:33: SkipInstallCA.
    This package is not supported on this operating system.
    Action ended 14:02:33: SkipInstallCA. Return value 3.
    Action ended 14:02:33: INSTALL. Return value 3.
    Property(S): ProductCode = {E46A76D1-9FB9-4770-BA24-3975EF4D120A}
    Property(S): Manufacturer = Microsoft Corporation
    Property(S): ProductVersion = 6.20.2016.0
    Property(S): ProductLanguage = 1033
    Property(S): UpgradeCode = {1B117BA7-5BC1-419E-820E-7D4F3F412C7B}
    Property(S): ARPPRODUCTICON = ARPIco
    Property(S): PIDTemplate = 53934<````=````=````=````=`````>@@@@@
    Property(S): PROMPTROLLBACKCOST = P
    Property(S): DiskPrompt = [1]
    Property(S): INSTALLLEVEL = 100
    Property(S): ALLUSERS = 1
    Property(S): InstallMode = Typical
    Property(S): ErrorIcon = ErrorIco
    Property(S): SuccessIcon = SuccessIco
    Property(S): WarningIcon = WarningIco
    Property(S): LicenseIcon = LicenseIco
    Property(S): SetupIcon = SetupIco
    Property(S): CompleteIcon = CompleteIco
    Property(S): CustomIcon = CustomIco
    Property(S): RepairIcon = RepairIco
    Property(S): RemoveIcon = RemoveIco
    Property(S): ModifyIcon = ModifyIco
    Property(S): NewIcon = NewIco
    Property(S): UpIcon = UpIco
    Property(S): DialogBanner = BannerBmp
    Property(S): WelcomeBmp = WelcomeBmp
    Property(S): ApplicationUsers = AllUsers
    Property(S): Details = 0
    Property(S): AgreeToLicense = No
    Property(S): _IsMaintenance = Reinstall
    Property(S): _IsMaintenance2 = Modify
    Property(S): ReinstallModeText = omus
    Property(S): Display_IsBitmapDlg = 1
    Property(S): Interrupted = 0
    Property(S): ProductID = none
    Property(S): ISENABLEDWUSFINISHDIALOG = 1
    Property(S): SQLServerText1 = 0
    Property(S): SQLServerVersionText1 = 0
    Property(S): SQLServerVersionText2 = 0
    Property(S): SQLServerVersionText3 = 0
    Property(S): CA_ERRORCOUNT = 0
    Property(S): CA_WARNINGCOUNT = 0
    Property(S): CA_SUCCESSCOUNT = 0
    Property(S): MINIMUMOS = true
    Property(S): UI_SHOWCOPYRIGHT = yes
    Property(S): ShowUserRegistrationDlg = 1
    Property(S): ErrorDialog = ErrorDlg
    Property(S): DefaultUIFont = Tahoma8
    Property(S): VersionNT = 600
    Property(S): ARPHELPLINK = http://support.microsoft.com/kb/2758696
    Property(S): SecureCustomProperties = NEWERFOUND.72DE5BCD_5CB0_4335_B118_AB4C4DA70AE1;OLDERFOUND.72DE5BCD_5CB0_4335_B118_AB4C4DA70AE1;OLDERFOUND2.72DE5BCD_5CB0_4335_B118_AB4C4DA70AE1
    Property(S): DesktopFolder = C:\Users\Public\Desktop\
    Property(S): ProgramFilesFolder = C:\Program Files\
    Property(S): ButtonTextStyle = {\ButtonTextStyle}
    Property(S): DlgTextStyle = {\DlgTextStyle}
    Property(S): DlgTextStyleB = {\DlgTextStyleB}
    Property(S): DlgTitleStyle = {\DlgTitleStyle}
    Property(S): DlgTitleStyleB = {\DlgTitleStyleB}
    Property(S): FixedStyle = {\FixedStyle}
    Property(S): Installed = 00:00:00
    Property(S): COMPANYNAME = Sun Life Hong Kong Limited
    Property(S): USERNAME = Sun Life
    Property(S): DialogTitleSetup = Setup
    Property(S): DialogTitlePatch = Patch
    Property(S): DialogTitleUpgrade = Upgrade
    Property(S): Text_ArrowLeft = <
    Property(S): Text_ArrowRight =  >
    Property(S): ButtonText_Next = Next
    Property(S): ButtonText_Next_Hot = &Next
    Property(S): ButtonText_Cancel = Cancel
    Property(S): ButtonText_Cancel_Hot = &Cancel
    Property(S): ButtonText_Back = Back
    Property(S): ButtonText_Back_Hot = &Back
    Property(S): ButtonText_Finish = Finish
    Property(S): ButtonText_Finish_Hot = &Finish
    Property(S): ButtonText_Update = Update >
    Property(S): ButtonText_Update_Hot = &Update >
    Property(S): ButtonText_Ok = OK
    Property(S): ButtonText_Ok_Hot = &OK
    Property(S): ButtonText_Yes = Yes
    Property(S): ButtonText_Yes_Hot = &Yes
    Property(S): ButtonText_No = No
    Property(S): ButtonText_No_Hot = &No
    Property(S): ButtonText_Abort = Abort
    Property(S): ButtonText_Abort_Hot = &Abort
    Property(S): ButtonText_Ignore = Ignore
    Property(S): ButtonText_Ignore_Hot = &Ignore
    Property(S): ButtonText_Retry = Retry
    Property(S): ButtonText_Retry_Hot = &Retry
    Property(S): ButtonText_Change = Change...
    Property(S): ButtonText_Change_Hot = &Change...
    Property(S): ButtonText_Help = Help
    Property(S): ButtonText_Help_Hot = &Help
    Property(S): ButtonText_Install = Install
    Property(S): ButtonText_Install_Hot = &Install
    Property(S): ButtonText_Exit = Exit
    Property(S): ButtonText_Exit_Hot = &Exit
    Property(S): ButtonText_Remove = Remove
    Property(S): ButtonText_Remove_Hot = &Remove
    Property(S): ButtonText_Space = Space
    Property(S): ButtonText_Space_Hot = &Space
    Property(S): ButtonText_Browse = Browse...
    Property(S): ButtonText_Browse_Hot = Bro&wse...
    Property(S): ButtonText_DiskCost = Disk Cost...
    Property(S): ButtonText_DiskCost_Hot = &Disk Cost...
    Property(S): LabelText_Status = Status
    Property(S): LabelText_SerialNumber = &Serial Number:
    Property(S): LabelText_UserName = &User Name
    Property(S): LabelText_PersonName = Name
    Property(S): LabelText_PersonOrganization = Company
    Property(S): LabelText_InstallTo = Install to
    Property(S): LabelText_Modify = &Modify
    Property(S): LabelText_Repair = Re&pair
    Property(S): LabelText_Remove = &Remove
    Property(S): LabelText_Complete = &Complete
    Property(S): LabelText_Custom = Cu&stom
    Property(S): LabelText_NetworkLocation = &Network location:
    Property(S): LabelText_LookIn = &Look in
    Property(S): LabelText_FolderName = &Folder name
    Property(S): LabelText_FeatureDescription = Feature description
    Property(S): LabelText_CopyFilesFrom = Copy Files from
    Property(S): LabelText_InstallFor = Install this application for
    Property(S): HeadText_AdminWelcome = Welcome to the Install Wizard for
    Property(S): HeadText_InstallWelcome = Welcome to the Install Wizard for
    Property(S): HeadText_WelcomePatch = Welcome to the Patch for
    Property(S): HeadText_SetupWelcome = Welcome to the
    Property(S): HeadText_SetupWelcome2 =  Setup
    Property(S): HeadText_ResumeInstall = Resuming the Install Wizard for
    Property(S): HeadText_SetupInterrupted =  Setup Interrupted
    Property(S): HeadText_LicenseAgreement = License Agreement
    Property(S): HeadText_FeatureSelection = Feature Selection
    Property(S): HeadText_NetworkLocation = Network Location
    Property(S): HeadText_ProgramMaintenance = Program Maintenance
    Property(S): HeadText_DiskSpaceRequirements = Disk Space Requirements
    Property(S): HeadText_FilesInUse = Files in Use
    Property(S): HeadText_DatabaseFolder = Database Folder
    Property(S): HeadText_RegistrationInformation = Registration Information
    Property(S): HeadText_CompletingSetup = Completing the
    Property(S): HeadText_CompletingSetup2 =  Setup
    Property(S): HeadText_InstallingProduct = Installing
    Property(S): HeadText_UninstallProduct = Uninstalling
    Property(S): HeadText_ChangeDestinationFolder = Change Current Destination Folder
    Property(S): HeadText_ReadyInstall = Ready to Install the Program
    Property(S): HeadText_ReadyRepair = Ready to Repair the Program
    Property(S): HeadText_ReadyModify = Ready to Modify the Program
    Property(S): HeadText_RemoveProgram = Remove the Program
    Property(S): HeadText_OutOfDiskSpace = Out of Disk Space
    Property(S): DescText_FilesInUse = Some files that need to be updated are currently in use.
    Property(S): DescText_RegistrationInformation = The following information will personalize your installation.
    Property(S): DescText_ServerImage = Setup will create a server image of
    Property(S): DescText_ServerImage2 =  at a specified network location. To continue, click Next.
    Property(S): DescText_InstallModifyRemove = Setup helps you install, modify or remove
    Property(S): DescText_InstallModifyRemove2 = . To continue, click Next.
    Property(S): DescText_PatchInstall = The Install Wizard will install the Patch for
    Property(S): DescText_PatchInstall2 =  on your computer. To continue, click Update.
    Property(S): DescText_WizardComplete = The Install Wizard will complete the installation of
    Property(S): DescText_WizardComplete2 =  on your computer. To continue, click Next.
    Property(S): DescText_CompleteSuspended = The Install Wizard will complete the suspended installation of
    Property(S): DescText_CompleteSuspended2 =  on your computer. To continue, click Next.
    Property(S): DescText_SuccessfulInstallation = Setup has installed
    Property(S): DescText_SuccessfulInstallation2 =  successfully. Click Finish to exit.
    Property(S): DescText_SuccessfulRemove = Setup has removed
    Property(S): DescText_SuccessfulRemove2 =  successfully. Click Finish to exit.
    Property(S): DescText_SuccessfulRepair = Setup has repaired
    Property(S): DescText_SuccessfulRepair2 =  successfully. Click Finish to exit.
    Property(S): DescText_SuccessfulModify = Setup has modified
    Property(S): DescText_SuccessfulModify2 =  successfully. Click Finish to exit.
    Property(S): DescText_SetupInterrupted = Setup was interrupted before
    Property(S): DescText_SetupInterrupted2 =  could be completely installed.
    Property(S): DescText_PreparingSetup =  Setup is preparing the Install Wizard which will guide you through the program setup process. Please wait.
    Property(S): DescText_FeatureSelection = Select the program features you want installed.
    Property(S): DescText_ProgramFeaturesInstall = The program features you selected are being installed.
    Property(S): DescText_ProgramFeaturesUninstall = The program features you selected are being uninstalled.
    Property(S): DescText_ReadLicense = Please read the following license agreement carefully.
    Property(S): DescText_SpecifyNetworkLocation = Specify a network location for the server image of the product.
    Property(S): DescText_BrowseDestination = Browse to the destination folder.
    Property(S): DescText_ModifyRepairRemove = Repair or remove the program.
    Property(S): DescText_ReadyInstallation = Setup is ready to begin installation.
    Property(S): DescText_ChosenRemove = You have chosen to remove the program from your system.
    Property(S): DescText_DiskSpaceRequirements = The disk space required for the installation of the selected features.
    Property(S): DescText_DiskExceedsAvailable = Disk space required for the installation exceeds available disk space.
    Property(S): Text_ReRunSetup = Your system has not been modified. To complete installation at another time, please run setup again.
    Property(S): Text_FinishExit = Click Finish to exit Setup.
    Property(S): Text_RestoreState = You can either keep any existing installed elements on your system to continue this installation at a later time or you can restore your system to its original state prior to the installation.
    Property(S): Text_RestoreClick = Click Restore or Continue Later to exit Setup.
    Property(S): Text_InstallWait = Please wait while the Install Wizard installs
    Property(S): Text_InstallWait2 = . This may take several minutes.
    Property(S): Text_UninstallWaitText = Please wait while the Install Wizard uninstalls
    Property(S): Text_UninstallWaitText2 = . This may take several minutes.
    Property(S): Text_UninstallWait = Please wait while the Install Wizard uninstalls
    Property(S): Text_UninstallWait2 = . This may take several minutes.
    Property(S): Text_ProgressDone = Progress done
    Property(S): Text_Copyright = WARNING: This program is protected by copyright law and international treaties.
    Property(S): Text_BeginInstallation = Click Install to begin the installation.
    Property(S): Text_ReviewChange = If you want to review or change any of your installation settings, click Back. Click Cancel to exit Setup.
    Property(S): Text_AlterFeatureInstall = Click an icon in the following list to change how a feature is installed.
    Property(S): Text_ConfirmExit = The installation is not yet complete. Are you sure you want to exit?
    Property(S): Text_FeatureSelectionDescription = This feature requires 4 MB on your hard drive.
    Property(S): Text_EnterNetworkLocation = Enter the network location or click Change to browse to a location. Click Install to create a server image of
    Property(S): Text_EnterNetworkLocation2 =  at the specified network location or click Cancel to exit Setup.
    Property(S): Text_SelectDifferentDrive = The highlighted volumes do not have enough disk space available for the currently selected features. You can remove files from the highlighted volumes, choose to install less features onto local drives, or select different
    destination drives.
    Property(S): Text_RepairInstallationErrors = Repair installation errors in the program. This option fixes missing or corrupt files, shortcuts, and registry entries.
    Property(S): Text_RemoveFromComputer = Remove
    Property(S): Text_RemoveFromComputer2 =  from your computer.
    Property(S): Text_UsingFilesRetry = The following applications are using files that need to be updated by this setup. Close these applications and click Retry to continue.
    Property(S): Text_ClickRemove = Click Remove to remove
    Property(S): Text_ClickRemove2 =  from your computer. After removal, this program will no longer be available for use.
    Property(S): Text_ReviewChangeBack = If you want to review or change any settings, click Back.
    Property(S): Text_AllUsers = &Anyone who uses this computer (all users)
    Property(S): Text_OnlyMe = Only for &me ([USERNAME])
    Property(S): Text_NotAcceptTerms = I &do not accept the terms in the license agreement
    Property(S): Text_AcceptTerms = I &accept the terms in the license agreement
    Property(S): Text_RegInfoNameAndOrg = Enter your name and the name of your organization in the fields below.
    Property(S): Text_RegInfoOrg = Enter the name of your organization in the field below.
    Property(S): Upgrade_Confirmation = A lower version of this product has been detected on your system. Would you like to upgrade your existing installation?
    Property(S): AdminMessage = Setup requires user to be in the administrator group in order to continue the installation process. Setup is aborting as the current user is not in the administrator group.
    Property(S): SupportedOSMessage = Installation of this product failed because it is not supported on this operating system. For information on supported configurations, see the product documentation.
    Property(S): ShortCutText = MSXML 6 Service Pack 2 (KB2758696)
    Property(S): DialogTitle = MSXML 6 Service Pack 2 (KB2758696) Setup
    Property(S): ProductName = MSXML 6 Service Pack 2 (KB2758696)
    Property(S): ShortName = MSXML 6 Service Pack 2 (KB2758696)
    Property(S): WrongPackage = This MSXML6 Service Pack 2 (KB2758696) package is not supported on the current processor type.
    Property(S): DialogPatchTitle = MSXML 6 Service Pack 2 (KB2758696) Patch
    Property(S): SystemFolder = C:\Windows\system32\
    Property(S): WdSfpCaMainModId.41646F16_4E6C_4E96_BF1B_772105414B9D = 86F857F6_A743_463D_B2FE_98CB5F727E09
    Property(S): AppGuidRegKey = Wdsfpca_Uninstall_RegKey.86F857F6_A743_463D_B2FE_98CB5F727E09
    Property(S): MsiLogFileLocation = C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0018_SV53749_MSXML6_1.log
    Property(S): PackageCode = {EE6525FC-1729-4E76-A8C1-12C756BA0AD0}
    Property(S): ProductState = 5
    Property(S): ProductToBeRegistered = 1
    Property(S): STPSETUPTHREADID = 1484
    Property(S): STPSETUPPROCESSID = 9540
    Property(S): EXTERNALCONTROL = 1
    Property(S): ADDLOCAL = ALL
    Property(S): SKIPPENDINGREBOOTCHECK = 1
    Property(S): APPGUID = {FFFA78A7-BD51-4255-8470-C4D4A85B49F5}
    Property(S): REBOOT = ReallySuppress
    Property(S): CURRENTDIRECTORY = C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap
    Property(S): CLIENTUILEVEL = 3
    Property(S): MSICLIENTUSESEXTERNALUI = 1
    Property(S): CLIENTPROCESSID = 9540
    Property(S): MsiRestartManagerSessionKey = 2bacf19a1da7c4438b188852d7df058c
    Property(S): PRODUCTLANGUAGE = 1033
    Property(S): VersionDatabase = 300
    Property(S): VersionMsi = 4.05
    Property(S): WindowsBuild = 6002
    Property(S): ServicePackLevel = 2
    Property(S): ServicePackLevelMinor = 0
    Property(S): MsiNTProductType = 3
    Property(S): WindowsFolder = C:\Windows\
    Property(S): WindowsVolume = C:\
    Property(S): System16Folder = C:\Windows\system\
    Property(S): RemoteAdminTS = 1
    Property(S): TempFolder = C:\Users\ADMINI~1\AppData\Local\Temp\
    Property(S): CommonFilesFolder = C:\Program Files\Common Files\
    Property(S): AppDataFolder = C:\Users\Administrator\AppData\Roaming\
    Property(S): FavoritesFolder = C:\Users\Administrator\Favorites\
    Property(S): NetHoodFolder = C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
    Property(S): PersonalFolder = C:\Users\Administrator\Documents\
    Property(S): PrintHoodFolder = C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
    Property(S): RecentFolder = C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Recent\
    Property(S): SendToFolder = C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\SendTo\
    Property(S): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
    Property(S): CommonAppDataFolder = C:\ProgramData\
    Property(S): LocalAppDataFolder = C:\Users\Administrator\AppData\Local\
    Property(S): MyPicturesFolder = C:\Users\Administrator\Pictures\
    Property(S): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
    Property(S): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
    Property(S): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
    Property(S): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
    Property(S): FontsFolder = C:\Windows\Fonts\
    Property(S): GPTSupport = 1
    Property(S): OLEAdvtSupport = 1
    Property(S): ShellAdvtSupport = 1
    Property(S): Intel = 6
    Property(S): PhysicalMemory = 2047
    Property(S): VirtualMemory = 2390
    Property(S): AdminUser = 1
    Property(S): LogonUser = Administrator
    Property(S): UserSID = S-1-5-21-752955860-2970973076-2057269693-500
    Property(S): UserLanguageID = 1033
    Property(S): ComputerName = SV53749
    Property(S): SystemLanguageID = 1033
    Property(S): ScreenX = 1024
    Property(S): ScreenY = 768
    Property(S): CaptionHeight = 19
    Property(S): BorderTop = 1
    Property(S): BorderSide = 1
    Property(S): TextHeight = 16
    Property(S): TextInternalLeading = 3
    Property(S): ColorBits = 32
    Property(S): TTCSupport = 1
    Property(S): Time = 14:02:33
    Property(S): Date = 2/23/2015
    Property(S): MsiNetAssemblySupport = 2.0.50727.4016
    Property(S): MsiWin32AssemblySupport = 6.0.6001.18000
    Property(S): RedirectedDllSupport = 2
    Property(S): MsiRunningElevated = 1
    Property(S): Privileged = 1
    Property(S): DATABASE = C:\WINDOWS\Installer\23e28752.msi
    Property(S): OriginalDatabase = C:\WINDOWS\Installer\23e28752.msi
    Property(S): UILevel = 2
    Property(S): Preselected = 1
    Property(S): ACTION = INSTALL
    MSI (s) (B8:64) [14:02:33:948]: Note: 1: 1729
    MSI (s) (B8:64) [14:02:33:948]: Product: MSXML 6 Service Pack 2 (KB2758696) -- Configuration failed.
    MSI (s) (B8:64) [14:02:33:949]: Windows Installer reconfigured the product. Product Name: MSXML 6 Service Pack 2 (KB2758696). Product Version: 6.20.2016.0. Product Language: 1033. Reconfiguration success or error status: 1603.
    MSI (s) (B8:64) [14:02:33:951]: Deferring clean up of packages/files, if any exist
    MSI (s) (B8:64) [14:02:33:951]: MainEngineThread is returning 1603
    MSI (s) (B8:9C) [14:02:33:952]: RESTART MANAGER: Session closed.
    MSI (s) (B8:9C) [14:02:33:952]: No System Restore sequence number for this installation.
    === Logging stopped: 2/23/2015  14:02:33 ===
    MSI (s) (B8:9C) [14:02:33:952]: User policy value 'DisableRollback' is 0
    MSI (s) (B8:9C) [14:02:33:952]: Machine policy value 'DisableRollback' is 0
    MSI (s) (B8:9C) [14:02:33:952]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (B8:9C) [14:02:33:953]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (B8:9C) [14:02:33:953]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (B8:9C) [14:02:33:954]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (B8:9C) [14:02:33:954]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (B8:9C) [14:02:33:954]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (B8:9C) [14:02:33:954]: Restoring environment variables
    MSI (s) (B8:9C) [14:02:33:955]: Destroying RemoteAPI object.
    MSI (s) (B8:B0) [14:02:33:955]: Custom Action Manager thread ending.
    MSI (c) (44:50) [14:02:33:957]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (44:50) [14:02:33:959]: MainEngineThread is returning 1603
    === Verbose logging stopped: 2/23/2015  14:02:33 ===
    MSXML6 problem

  • Is my installation of SQL Server Fail Over cluster correct?

    I made a 2 node SQL Server 2012 fail over cluster but having some problems during installation so I wanted to know if the steps below I performed are correct.
    Hardware
    Node1 192.168.1.10
    Node2 192.168.1.11
    Added following entries in DNS
    cluster.domain.local 192.168.1.12 (for Windows Cluster)
    msdtc.domain.local 192.168.1.13 (for MSDTC)
    sql.domain.local 192.168.1.14 (for SQL Server Cluster)
    Cluster Storage
    Disk1 (for Quorum)
    Disk2 (for MSDTC
    Disk3 (for SQL Server)
    Now comes the installation. I am performing all these steps as DOMAIN ADMIN.
    1. First I installed clustering role on both nodes
    2. Then I ran fail over validation wizard on Node1 adding both nodes which went fine (there were some warnings)
    3. Then I made a Windows Cluster on Node1 using these two nodes. I gave the name and IP to this cluster which I wrote above i.e. cluster.domain.local 192.168.1.12
    4. Cluster was created and boths nodes are UP.
    Now I want to ask a question here. Is it best practice to perform the above operation using DOMAIN ADMIN? Or if I use a standard domain user account with local admin rights, will it work? If not then exactly what rights are required to perform this operation.
    5. Then I installed "Application Server" role on both Node1 and Node2 and also added "Distributed Transaction" feature
    6. Then I right clicked on Windows Cluster I created and added a new role/feature which is "DTC"
    7. I gave it the same name which I wrote above i.e. msdtc.domain.local 192.168.1.13
    8. MSDTC was created but when it tried to UP its service, it threw an error. Upon investigation it turns out the Windows Cluster cluster.domain.local doesn't have proper rights to created some objects in AD. I didn't know what rights to give so I gave it full
    permission and after that when I created MSDTC again, the service went up fine.
    So I want to know what rights does cluster.domain.com require to make MSDTC?
    Am I doing good so far?

    Hello,
    >>Then I made a Windows Cluster on Node1 using these two nodes. I gave the name and IP to this cluster which I wrote above i.e. cluster.domain.local 192.168.1.10
    Hello I suppose this IP was physical node IP windows cluster IP was 192.168.1.12  I suppose yo must have given this IP as windows cluster IP.10 and 11 are physical nodes in Cluster but 12 is Cluster IP .Correct me if I am wrong.
    Did you do failover and failback to check whether cluster is configured correctly or not ,If not please do it .
    >>Then I ran fail over validation wizard on Node1 adding both nodes which went fine (there were some warnings)
    Please remove warnings also ,it might cause issue.Not sure its correct every time but make sure cluster validation should be free of error and warning.
    >>Now I want to ask a question here. Is it best practice to perform the above operation using DOMAIN ADMIN?
    You can do it with domain admin account as this is required to create Cluster NAme object(CNO) in domain and local account might not have that right so I would say its ok.
    >>I gave it the same name which I wrote above i.e. msdtc.domain.local
    192.168.1.11
    again this IP is node 2 IP how can you give it to MSDTC.Use below link for reference
    http://blogs.msdn.com/b/cindygross/archive/2009/02/22/how-to-configure-dtc-for-sql-server-in-a-windows-2008-cluster.aspx
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Failing to install SQL 2005 on server.

    I am failing to install SQL 2005 on the server with message below:-
    TITLE: Microsoft SQL Server 2005 Setup
    The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=MicrosoftSQLServer&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=29503&EvtType=sqlsetuplib%5cservice.cpp%40Do_sqlScript%40sqls%3a%3aService%3a%3aStart%40x42b
    BUTTONS:
    &Retry
    Cancel
    It was removed after it started developing problems. We tried to go to MS SQL site buts its not opening the site. I thought maybe you could help although it is a SQL error. For some time we are failing to run SAP B1 because of this.
    Thank you.

    Hi,
       Check the SQL Services  go to start->AllPrograms->Microsost
    SQL Server 2005->ConfigurationTools->SQL Server Configuration Manager
    Pl check The following Services is Running State
    1.SQL Server Browser
    2.SQLServer(MSSQLSERVER)
    Regards
    JambuLingam.P

  • SQL 2012 Mirror with SQL 2005

    We need to move an SQL DB, so we decided to upgrade at the same time.
    The upgrade will be both in software and hardware.
    My question, can we setup a mirror between SQL 2012 and SQl 2005 in order to migrate the DB's to new hardware and SQL instance?
    Thanks!

    Hi wmikef,
    We cannot set up a mirror between SQL  Server 2012 and SQL Server 2005. Please note that the
    prerequisites for setting up database mirroring.
    • For a mirroring session to be established, the partners and the witness, if any, must be running on the same version of SQL Server.
    • The principal server and mirror server, must be running the same edition of SQL Server. The witness, if any, can run on any edition of SQL Server that supports database mirroring.
    • The database must use the full recovery model.
    • Verify that the mirror server has sufficient disk space for the mirror database.
    • Make sure that you restore the backup of the principal database specifying the same database name WITH NORECOVERY when creating the mirror database on the mirror server.
    For more information, please review the following article.
    http://msdn.microsoft.com/en-us/library/ms366349.aspx
    Thanks,
    Lydia Zhang
    If you have any feedback on our support, please click
    here.

  • SQL 2005 Patch installation fail

    Hi all
    I am having error on installing KB2716429... currently the SQL server is build no. 9.0.5057
    here following is the error
    11/30/2013 09:46:45.484 ================================================================================
    11/30/2013 09:46:45.484 Hotfix package launched
    11/30/2013 09:46:45.500 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
    11/30/2013 09:46:45.500 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
    11/30/2013 09:46:45.500 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
    11/30/2013 09:46:45.500 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
    11/30/2013 09:46:45.515 Local Computer:
    11/30/2013 09:46:45.515 Target Details: SV53704
    11/30/2013 09:46:45.515   commonfilesdir = C:\Program Files\Common Files
    11/30/2013 09:46:45.515   lcidsupportdir = e:\6ce33de16cc8ba67b3e41388bb\1033
    11/30/2013 09:46:45.515   programfilesdir = C:\Program Files
    11/30/2013 09:46:45.515   programfilesdir_wow = C:\Program Files
    11/30/2013 09:46:45.515   supportdir = e:\6ce33de16cc8ba67b3e41388bb
    11/30/2013 09:46:45.515   supportdirlocal = e:\6ce33de16cc8ba67b3e41388bb
    11/30/2013 09:46:45.515   windir = C:\WINDOWS
    11/30/2013 09:46:45.515   winsysdir = C:\WINDOWS\system32
    11/30/2013 09:46:45.515   winsysdir_wow = C:\WINDOWS\SysWOW64
    11/30/2013 09:46:45.515
    11/30/2013 09:46:45.531 Enumerating applicable products for this patch
    11/30/2013 09:46:45.531 Found SQL 2005 product definition
    11/30/2013 09:46:45.531 Warning: Product HotFixSQL is missing LCID value
    11/30/2013 09:46:46.953 Enumeration: Determining QFE level for product instance MSSQLSERVER
    11/30/2013 09:46:46.969 Enumeration: Found following QFE level for product instance MSSQLSERVER: 5057
    11/30/2013 09:46:46.969 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
    11/30/2013 09:46:46.969 Enumeration: Found following GDR branch hotfix for product instance MSSQLSERVER: 5292
    11/30/2013 09:46:46.969 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
    11/30/2013 09:46:46.984 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
    11/30/2013 09:46:46.984 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
    11/30/2013 09:46:46.984 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
    11/30/2013 09:46:46.984 Product discovery completed during the install process for MSSQLSERVER
    11/30/2013 09:46:46.984 SP Level check completed during the install process for MSSQLSERVER
    11/30/2013 09:46:46.984 Product language check completed during the install process for MSSQLSERVER
    11/30/2013 09:46:46.984 Product version check completed during the install process for MSSQLSERVER
    11/30/2013 09:46:46.984 Command-line instance name check completed during the install process
    11/30/2013 09:46:46.984 Baseline build check completed during the installation process for MSSQLSERVER
    11/30/2013 09:46:47.000 Baseline build check completed during the install process
    11/30/2013 09:46:47.000 Found OLAP Server 2005 product definition
    11/30/2013 09:46:47.000 Warning: Product HotFixAS is missing LCID value
    11/30/2013 09:46:48.453 Enumeration: Determining QFE level for product instance MSSQLSERVER
    11/30/2013 09:46:48.453 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\\Bin\msmdsrv.exe
    11/30/2013 09:46:48.453 Enumeration: Found following QFE level for product instance MSSQLSERVER: 5057
    11/30/2013 09:46:48.453 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
    11/30/2013 09:46:48.453 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\\Bin\msmdsrv.exe
    11/30/2013 09:46:48.453 Enumeration: No GDR branch Hotfix found for product instance MSSQLSERVER
    11/30/2013 09:46:48.469 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
    11/30/2013 09:46:48.469 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
    11/30/2013 09:46:48.469 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
    11/30/2013 09:46:48.469 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
    11/30/2013 09:46:48.469 Product discovery completed during the install process for MSSQLSERVER
    11/30/2013 09:46:48.469 SP Level check completed during the install process for MSSQLSERVER
    11/30/2013 09:46:48.469 Product language check completed during the install process for MSSQLSERVER
    11/30/2013 09:46:48.484 Product version check completed during the install process for MSSQLSERVER
    11/30/2013 09:46:48.484 Command-line instance name check completed during the install process
    11/30/2013 09:46:48.484 Baseline build check completed during the installation process for MSSQLSERVER
    11/30/2013 09:46:48.484 Baseline build check completed during the install process
    11/30/2013 09:46:48.484 Found Notification Services 2005 product definition
    11/30/2013 09:46:48.484 Warning: Product HotFixNS is missing LCID value
    11/30/2013 09:46:50.015 Enumeration: Determining QFE level for product instance
    11/30/2013 09:46:50.047 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\\Bin\nsservice.exe
    11/30/2013 09:46:50.062 Enumeration: Found following QFE level for product instance : 5057
    11/30/2013 09:46:50.062 Enumeration: Determining GDR branching Hotfix for product instance
    11/30/2013 09:46:50.062 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\\Bin\nsservice.exe
    11/30/2013 09:46:50.062 Enumeration: Found following GDR branch hotfix for product instance : 5292
    11/30/2013 09:46:50.062 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
    11/30/2013 09:46:50.062 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
    11/30/2013 09:46:50.062 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
    11/30/2013 09:46:50.078 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
    11/30/2013 09:46:50.078 Product discovery completed during the install process for NS
    11/30/2013 09:46:50.078 SP Level check completed during the install process for NS
    11/30/2013 09:46:50.078 Product language check completed during the install process for NS
    11/30/2013 09:46:50.078 Product version check completed during the install process for NS
    11/30/2013 09:46:50.078 Baseline build check completed during the installation process for NS
    11/30/2013 09:46:50.078 Baseline build check completed during the install process
    11/30/2013 09:46:50.078 Found Report Server 2005 product definition
    11/30/2013 09:46:50.109 Warning: Product HotFixRS is missing LCID value
    11/30/2013 09:46:51.687 Enumeration: Determining QFE level for product instance MSSQLSERVER
    11/30/2013 09:46:51.703 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\\ReportServer\bin\ReportingServicesService.exe
    11/30/2013 09:46:51.703 Enumeration: Found following QFE level for product instance MSSQLSERVER: 5057
    11/30/2013 09:46:51.703 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
    11/30/2013 09:46:51.703 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\\ReportServer\bin\ReportingServicesService.exe
    11/30/2013 09:46:51.703 Enumeration: Found following GDR branch hotfix for product instance MSSQLSERVER: 5292
    11/30/2013 09:46:51.703 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
    11/30/2013 09:46:51.703 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
    11/30/2013 09:46:51.703 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
    11/30/2013 09:46:51.703 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
    11/30/2013 09:46:51.703 Product discovery completed during the install process for MSSQLSERVER
    11/30/2013 09:46:51.703 SP Level check completed during the install process for MSSQLSERVER
    11/30/2013 09:46:51.703 Product language check completed during the install process for MSSQLSERVER
    11/30/2013 09:46:51.703 Product version check completed during the install process for MSSQLSERVER
    11/30/2013 09:46:51.719 Command-line instance name check completed during the install process
    11/30/2013 09:46:51.750 Baseline build check completed during the installation process for MSSQLSERVER
    11/30/2013 09:46:51.750 Baseline build check completed during the install process
    11/30/2013 09:46:51.765 Found DTS 2005 product definition
    11/30/2013 09:46:51.765 Warning: Product HotFixDTS is missing LCID value
    11/30/2013 09:46:53.359 Enumeration: Determining QFE level for product instance
    11/30/2013 09:46:53.375 Enumeration: Found following QFE level for product instance : 5057
    11/30/2013 09:46:53.375 Enumeration: Determining GDR branching Hotfix for product instance
    11/30/2013 09:46:53.375 Enumeration: Found following GDR branch hotfix for product instance : 5292
    11/30/2013 09:46:53.375 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
    11/30/2013 09:46:53.375 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
    11/30/2013 09:46:53.375 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
    11/30/2013 09:46:53.375 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
    11/30/2013 09:46:53.375 Product discovery completed during the install process for Integration Services
    11/30/2013 09:46:53.375 SP Level check completed during the install process for Integration Services
    11/30/2013 09:46:53.375 Product language check completed during the install process for Integration Services
    11/30/2013 09:46:53.375 Product version check completed during the install process for Integration Services
    11/30/2013 09:46:53.375 Baseline build check completed during the installation process for Integration Services
    11/30/2013 09:46:53.375 Baseline build check completed during the install process
    11/30/2013 09:46:53.390 Found SQL 2005 Tools product definition
    11/30/2013 09:46:53.390 Warning: Product HotFixTools is missing LCID value
    11/30/2013 09:46:54.953 Enumeration: Determining GDR branching Hotfix for product instance
    11/30/2013 09:46:54.969 Enumeration: Found following GDR branch hotfix for product instance : 5292
    11/30/2013 09:46:54.969 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
    11/30/2013 09:46:54.969 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
    11/30/2013 09:46:54.969 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
    11/30/2013 09:46:54.969 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
    11/30/2013 09:46:54.969 Product discovery completed during the install process for SQL Tools
    11/30/2013 09:46:54.969 SP Level check completed during the install process for SQL Tools
    11/30/2013 09:46:54.969 Product language check completed during the install process for SQL Tools
    11/30/2013 09:46:54.984 Product version check completed during the install process for SQL Tools
    11/30/2013 09:46:54.984 Baseline build check completed during the installation process for SQL Tools
    11/30/2013 09:46:54.984 Baseline build check completed during the install process
    11/30/2013 09:46:55.031 Product Enumeration Results:
    11/30/2013 09:46:55.031   INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixSQL.inf
    11/30/2013 09:46:55.031   arpfolder = SQL9_KB2716429_ENU
    11/30/2013 09:46:55.031   associatedhotfixbuild = 5320
    11/30/2013 09:46:55.031   baselinebuild = 5000
    11/30/2013 09:46:55.031   baselinebuildmax = 5069
    11/30/2013 09:46:55.031   build = 5069
    11/30/2013 09:46:55.031   description = SQL Server Database Services 2005
    11/30/2013 09:46:55.031   details = Patch for SQL Server Database Services 2005
    11/30/2013 09:46:55.031   installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
    11/30/2013 09:46:55.031   kbarticle = KB2716429
    11/30/2013 09:46:55.031   kbarticlehyperlink =
    http://support.microsoft.com/?kbid=2716429
    11/30/2013 09:46:55.031   legalproductname = SQL Server Database Services 2005
    11/30/2013 09:46:55.031   machinetype = x86
    11/30/2013 09:46:55.031   package = HotFixSQL
    11/30/2013 09:46:55.031   packagetype = GDR
    11/30/2013 09:46:55.031   productname = SQL9
    11/30/2013 09:46:55.047   relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
    11/30/2013 09:46:55.047   servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
    11/30/2013 09:46:55.047   splevel = 4
    11/30/2013 09:46:55.047   sqlutility = sqlcmd.exe
    11/30/2013 09:46:55.047   supportdir = e:\6ce33de16cc8ba67b3e41388bb
    11/30/2013 09:46:55.047   version = 9
    11/30/2013 09:46:55.047
    11/30/2013 09:46:55.047   File Group Details: MSP
    11/30/2013 09:46:55.047     parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
    11/30/2013 09:46:55.047     sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
    11/30/2013 09:46:55.047     File Details: sqlrun_sql.msp
    11/30/2013 09:46:55.047
    11/30/2013 09:46:55.047   Instance Details: MSSQLSERVER
    11/30/2013 09:46:55.047     agentservicename = SQLSERVERAGENT
    11/30/2013 09:46:55.047     associatedhotfixbuild = 5292
    11/30/2013 09:46:55.047     clustername =
    11/30/2013 09:46:55.047     default = TRUE
    11/30/2013 09:46:55.047     ftsservicename = MSFTESQL
    11/30/2013 09:46:55.047     fullversion = 2005.090.5057.00
    11/30/2013 09:46:55.047     hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.1
    11/30/2013 09:46:55.047     id = MSSQL.1
    11/30/2013 09:46:55.062     installsqldatadir = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
    11/30/2013 09:46:55.062     installsqldir = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
    11/30/2013 09:46:55.062     lcid = 1033
    11/30/2013 09:46:55.062     name = MSSQLSERVER
    11/30/2013 09:46:55.062     productcode = {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
    11/30/2013 09:46:55.062     qfelevel = 5057
    11/30/2013 09:46:55.062     servicename = MSSQLServer
    11/30/2013 09:46:55.062     sku = STANDARD
    11/30/2013 09:46:55.062     sp = 4
    11/30/2013 09:46:55.094     type = SQL Server Standalone Product
    11/30/2013 09:46:55.094     vermajbld = 5000
    11/30/2013 09:46:55.094     version = 9
    11/30/2013 09:46:55.109
    11/30/2013 09:46:55.125 Product Enumeration Results:
    11/30/2013 09:46:55.140   INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixAS.inf
    11/30/2013 09:46:55.140   arpfolder = OLAP9_KB2716429_ENU
    11/30/2013 09:46:55.140   associatedhotfixbuild = 5320
    11/30/2013 09:46:55.140   baselinebuild = 5000
    11/30/2013 09:46:55.140   baselinebuildmax = 5069
    11/30/2013 09:46:55.140   build = 5069
    11/30/2013 09:46:55.140   description = SQL Server Analysis Services 2005
    11/30/2013 09:46:55.140   details = Patch for Analysis Services 2005
    11/30/2013 09:46:55.140   installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
    11/30/2013 09:46:55.140   kbarticle = KB2716429
    11/30/2013 09:46:55.140   kbarticlehyperlink =
    http://support.microsoft.com/?kbid=2716429
    11/30/2013 09:46:55.140   legalproductname = SQL Server Analysis Services 2005
    11/30/2013 09:46:55.156   machinetype = x86
    11/30/2013 09:46:55.156   package = HotFixAS
    11/30/2013 09:46:55.156   packagetype = GDR
    11/30/2013 09:46:55.156   productname = OLAP9
    11/30/2013 09:46:55.156   relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
    11/30/2013 09:46:55.156   servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
    11/30/2013 09:46:55.156   splevel = 4
    11/30/2013 09:46:55.156   supportdir = e:\6ce33de16cc8ba67b3e41388bb
    11/30/2013 09:46:55.156   validateauthentication = true
    11/30/2013 09:46:55.156   version = 9
    11/30/2013 09:46:55.156
    11/30/2013 09:46:55.156   File Group Details: MSP
    11/30/2013 09:46:55.156     parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
    11/30/2013 09:46:55.156     sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
    11/30/2013 09:46:55.172     File Details: sqlrun_as.msp
    11/30/2013 09:46:55.172
    11/30/2013 09:46:55.172   Instance Details: MSSQLSERVER
    11/30/2013 09:46:55.172     associatedhotfixbuild = 1520
    11/30/2013 09:46:55.172     clustername =
    11/30/2013 09:46:55.187     default = TRUE
    11/30/2013 09:46:55.203     fullversion = 2005.090.5057.00
    11/30/2013 09:46:55.219     hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.2
    11/30/2013 09:46:55.219     id = MSSQL.2
    11/30/2013 09:46:55.219     installsqldatadir = C:\Program Files\Microsoft SQL Server\
    11/30/2013 09:46:55.234     installsqldir = C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\
    11/30/2013 09:46:55.250     lcid = 1033
    11/30/2013 09:46:55.265     name = MSSQLSERVER
    11/30/2013 09:46:55.297     olapservicename = MSSQLServerOLAPService
    11/30/2013 09:46:55.297     productcode = {8ABF8FEB-ABB0-40DC-9945-85AF36EF30A9}
    11/30/2013 09:46:55.297     qfelevel = 5057
    11/30/2013 09:46:55.297     servicename = MSSQLServerOLAPService
    11/30/2013 09:46:55.297     sku = STANDARD
    11/30/2013 09:46:55.297     sp = 4
    11/30/2013 09:46:55.297     type = Olap Standalone Product
    11/30/2013 09:46:55.297     vermajbld = 5000
    11/30/2013 09:46:55.297     version = 9
    11/30/2013 09:46:55.297
    11/30/2013 09:46:55.297 Product Enumeration Results:
    11/30/2013 09:46:55.297   INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixNS.inf
    11/30/2013 09:46:55.297   arpfolder = NS9_KB2716429_ENU
    11/30/2013 09:46:55.297   associatedhotfixbuild = 5320
    11/30/2013 09:46:55.297   baselinebuild = 5000
    11/30/2013 09:46:55.297   baselinebuildmax = 5069
    11/30/2013 09:46:55.297   build = 5069
    11/30/2013 09:46:55.297   description = SQL Server Notification Services 2005
    11/30/2013 09:46:55.297   details = Patch for SQL Server Notification Services 2005
    11/30/2013 09:46:55.297   installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
    11/30/2013 09:46:55.312   kbarticle = KB2716429
    11/30/2013 09:46:55.312   kbarticlehyperlink =
    http://support.microsoft.com/?kbid=2716429
    11/30/2013 09:46:55.312   legalproductname = SQL Server Notification Services 2005 instances
    11/30/2013 09:46:55.312   machinetype = x86
    11/30/2013 09:46:55.312   package = HotFixNS
    11/30/2013 09:46:55.312   packagetype = GDR
    11/30/2013 09:46:55.312   productname = NS9
    11/30/2013 09:46:55.312   recommendinstall = 1
    11/30/2013 09:46:55.312   relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
    11/30/2013 09:46:55.312   servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
    11/30/2013 09:46:55.312   splevel = 4
    11/30/2013 09:46:55.312   supportdir = e:\6ce33de16cc8ba67b3e41388bb
    11/30/2013 09:46:55.312   validateauthentication = true
    11/30/2013 09:46:55.312   version = 9
    11/30/2013 09:46:55.312
    11/30/2013 09:46:55.312   File Group Details: MSP
    11/30/2013 09:46:55.312     parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
    11/30/2013 09:46:55.312     sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
    11/30/2013 09:46:55.312     File Details: sqlrun_ns.msp
    11/30/2013 09:46:55.312
    11/30/2013 09:46:55.312   Instance Details: NS
    11/30/2013 09:46:55.312     associatedhotfixbuild = 5292
    11/30/2013 09:46:55.328     clustername =
    11/30/2013 09:46:55.328     fullversion = 9.00.5057.00
    11/30/2013 09:46:55.328     hiveregpath = Software\Microsoft\Microsoft SQL Server\90\NS
    11/30/2013 09:46:55.328     id =
    11/30/2013 09:46:55.328     installsqldatadir =
    11/30/2013 09:46:55.328     installsqldir = C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\
    11/30/2013 09:46:55.328     lcid = 1033
    11/30/2013 09:46:55.328     name =
    11/30/2013 09:46:55.375     productcode = {37E9AD9F-3217-4229-B5A5-7A0C82364C6C}
    11/30/2013 09:46:55.390     qfelevel = 5057
    11/30/2013 09:46:55.406     sku = STANDARD
    11/30/2013 09:46:55.406     sp = 4
    11/30/2013 09:46:55.406     type = Tools Only
    11/30/2013 09:46:55.406     vermajbld = 5000
    11/30/2013 09:46:55.422     version = 9
    11/30/2013 09:46:55.422
    11/30/2013 09:46:55.422 Product Enumeration Results:
    11/30/2013 09:46:55.422   INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixRS.inf
    11/30/2013 09:46:55.422   arpfolder = RS9_KB2716429_ENU
    11/30/2013 09:46:55.422   associatedhotfixbuild = 5320
    11/30/2013 09:46:55.422   baselinebuild = 5000
    11/30/2013 09:46:55.422   baselinebuildmax = 5069
    11/30/2013 09:46:55.422   build = 5069
    11/30/2013 09:46:55.453   description = SQL Server Reporting Services 2005
    11/30/2013 09:46:55.453   details = Patch for SQL Server Reporting Services 2005
    11/30/2013 09:46:55.453   installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
    11/30/2013 09:46:55.453   kbarticle = KB2716429
    11/30/2013 09:46:55.453   kbarticlehyperlink =
    http://support.microsoft.com/?kbid=2716429
    11/30/2013 09:46:55.453   legalproductname = SQL Server Reporting Services 2005
    11/30/2013 09:46:55.453   machinetype = x86
    11/30/2013 09:46:55.453   package = HotFixRS
    11/30/2013 09:46:55.453   packagetype = GDR
    11/30/2013 09:46:55.453   productname = RS9
    11/30/2013 09:46:55.469   relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
    11/30/2013 09:46:55.469   servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
    11/30/2013 09:46:55.469   splevel = 4
    11/30/2013 09:46:55.469   sqlutility = sqlcmd.exe
    11/30/2013 09:46:55.469   supportdir = e:\6ce33de16cc8ba67b3e41388bb
    11/30/2013 09:46:55.469   validateauthentication = true
    11/30/2013 09:46:55.469   version = 9
    11/30/2013 09:46:55.469
    11/30/2013 09:46:55.469   File Group Details: MSP
    11/30/2013 09:46:55.469     parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
    11/30/2013 09:46:55.469     sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
    11/30/2013 09:46:55.469     File Details: sqlrun_rs.msp
    11/30/2013 09:46:55.469
    11/30/2013 09:46:55.469   Instance Details: MSSQLSERVER
    11/30/2013 09:46:55.469     associatedhotfixbuild = 5292
    11/30/2013 09:46:55.469     clustername =
    11/30/2013 09:46:55.469     default = TRUE
    11/30/2013 09:46:55.469     fullversion = 9.00.5057.00
    11/30/2013 09:46:55.469     hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.3
    11/30/2013 09:46:55.469     id = MSSQL.3
    11/30/2013 09:46:55.469     installsqldatadir =
    11/30/2013 09:46:55.469     installsqldir = C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\
    11/30/2013 09:46:55.484     lcid = 1033
    11/30/2013 09:46:55.484     name = MSSQLSERVER
    11/30/2013 09:46:55.484     productcode = {E930E839-998E-42F9-97E2-71FC960DB1B7}
    11/30/2013 09:46:55.484     qfelevel = 5057
    11/30/2013 09:46:55.484     rsservicename = ReportServer
    11/30/2013 09:46:55.484     servicename =
    11/30/2013 09:46:55.484     sku = STANDARD
    11/30/2013 09:46:55.484     sp = 4
    11/30/2013 09:46:55.484     type = Report Server Standalone Product
    11/30/2013 09:46:55.484     vermajbld = 5000
    11/30/2013 09:46:55.484     version = 9
    11/30/2013 09:46:55.484
    11/30/2013 09:46:55.484 Product Enumeration Results:
    11/30/2013 09:46:55.484   INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixDTS.inf
    11/30/2013 09:46:55.500   arpfolder = DTS9_KB2716429_ENU
    11/30/2013 09:46:55.625   associatedhotfixbuild = 5320
    11/30/2013 09:46:55.625   baselinebuild = 5000
    11/30/2013 09:46:55.625   baselinebuildmax = 5069
    11/30/2013 09:46:55.625   build = 5069
    11/30/2013 09:46:55.625   description = SQL Server Integration Services 2005
    11/30/2013 09:46:55.625   details = Patch for SQL Server Integration Services 2005
    11/30/2013 09:46:55.625   installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
    11/30/2013 09:46:55.625   kbarticle = KB2716429
    11/30/2013 09:46:55.625   kbarticlehyperlink =
    http://support.microsoft.com/?kbid=2716429
    11/30/2013 09:46:55.625   legalproductname = SQL Server Integration Services 2005
    11/30/2013 09:46:55.625   machinetype = x86
    11/30/2013 09:46:55.640   package = HotFixDTS
    11/30/2013 09:46:55.640   packagetype = GDR
    11/30/2013 09:46:55.640   productname = DTS9
    11/30/2013 09:46:55.640   recommendinstall = 1
    11/30/2013 09:46:55.640   relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
    11/30/2013 09:46:55.640   servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
    11/30/2013 09:46:55.640   splevel = 4
    11/30/2013 09:46:55.640   supportdir = e:\6ce33de16cc8ba67b3e41388bb
    11/30/2013 09:46:55.640   version = 9
    11/30/2013 09:46:55.640
    11/30/2013 09:46:55.640   File Group Details: MSP
    11/30/2013 09:46:55.640     parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
    11/30/2013 09:46:55.640     sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
    11/30/2013 09:46:55.640     File Details: sqlrun_dts.msp
    11/30/2013 09:46:55.640
    11/30/2013 09:46:55.640   Instance Details: Integration Services
    11/30/2013 09:46:55.640     associatedhotfixbuild = 5292
    11/30/2013 09:46:55.640     clustername =
    11/30/2013 09:46:55.640     dtsservicename = MsDtsServer
    11/30/2013 09:46:55.640     fullversion = 9.00.5057.00
    11/30/2013 09:46:55.656     hiveregpath = Software\Microsoft\Microsoft SQL Server\90\DTS
    11/30/2013 09:46:55.656     id =
    11/30/2013 09:46:55.656     installsqldatadir =
    11/30/2013 09:46:55.656     installsqldir = C:\Program Files\Microsoft SQL Server\90\DTS\
    11/30/2013 09:46:55.656     lcid = 1033
    11/30/2013 09:46:55.656     name =
    11/30/2013 09:46:55.656     productcode = {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
    11/30/2013 09:46:55.656     qfelevel = 5057
    11/30/2013 09:46:55.656     servicename = MsDtsServer
    11/30/2013 09:46:55.656     sku = STANDARD
    11/30/2013 09:46:55.656     sp = 4
    11/30/2013 09:46:55.656     type = Tools Only
    11/30/2013 09:46:55.656     vermajbld = 5000
    11/30/2013 09:46:55.656     version = 9
    11/30/2013 09:46:55.656
    11/30/2013 09:46:55.656 Product Enumeration Results:
    11/30/2013 09:46:55.672   INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixTools.inf
    11/30/2013 09:46:55.672   arpfolder = SQLTools9_KB2716429_ENU
    11/30/2013 09:46:55.672   associatedhotfixbuild = 5320
    11/30/2013 09:46:55.672   baselinebuild = 5000
    11/30/2013 09:46:55.672   baselinebuildmax = 5069
    11/30/2013 09:46:55.672   build = 5069
    11/30/2013 09:46:55.672   description = SQL Server Tools and Workstation Components 2005
    11/30/2013 09:46:55.672   details = Patch for SQL Server Tools and Workstation Components 2005
    11/30/2013 09:46:55.672   installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
    11/30/2013 09:46:55.672   kbarticle = KB2716429
    11/30/2013 09:46:55.672   kbarticlehyperlink =
    http://support.microsoft.com/?kbid=2716429
    11/30/2013 09:46:55.672   legalproductname = SQL Server Tools and Workstation Components 2005
    11/30/2013 09:46:55.672   machinetype = x86
    11/30/2013 09:46:55.672   package = HotFixTools
    11/30/2013 09:46:55.672   packagetype = GDR
    11/30/2013 09:46:55.672   productname = SQLTools9
    11/30/2013 09:46:55.672   recommendinstall = 1
    11/30/2013 09:46:55.672   relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
    11/30/2013 09:46:55.672   servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
    11/30/2013 09:46:55.672   splevel = 4
    11/30/2013 09:46:55.672   supportdir = e:\6ce33de16cc8ba67b3e41388bb
    11/30/2013 09:46:55.687   version = 9
    11/30/2013 09:46:55.687
    11/30/2013 09:46:55.687   File Group Details: MSP
    11/30/2013 09:46:55.687     parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
    11/30/2013 09:46:55.687     sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
    11/30/2013 09:46:55.687     File Details: sqlrun_tools.msp
    11/30/2013 09:46:55.687
    11/30/2013 09:46:55.687   Instance Details: SQL Tools
    11/30/2013 09:46:55.687     associatedhotfixbuild = 5292
    11/30/2013 09:46:55.687     clustername =
    11/30/2013 09:46:55.687     fullversion = 9.4.5057
    11/30/2013 09:46:55.687     hiveregpath = Software\Microsoft\Microsoft SQL Server\90\Tools
    11/30/2013 09:46:55.687     id =
    11/30/2013 09:46:55.687     installsqldatadir =
    11/30/2013 09:46:55.687     installsqldir = C:\Program Files\Microsoft SQL Server\90\Tools\
    11/30/2013 09:46:55.687     lcid = 1033
    11/30/2013 09:46:55.687     name =
    11/30/2013 09:46:55.687     productcode = {1DD463C0-A50A-4394-B7E4-5895C02F9E0D}
    11/30/2013 09:46:55.687     qfelevel = 5057
    11/30/2013 09:46:55.687     sku = STANDARD
    11/30/2013 09:46:55.687     sp = 4
    11/30/2013 09:46:55.687     type = Tools Only
    11/30/2013 09:46:55.703     vermajbld = 5000
    11/30/2013 09:46:55.703     version = 9
    11/30/2013 09:46:55.703
    11/30/2013 09:47:00.781 Registry: Opened registry key "System\CurrentControlSet\Control\Session Manager"
    11/30/2013 09:47:00.781 Registry: Cannot read registry key value "PendingFileRenameOperations", error 0
    11/30/2013 09:47:00.812 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
    11/30/2013 09:47:00.828 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
    11/30/2013 09:47:00.828 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
    11/30/2013 09:47:00.828 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
    11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
    11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
    11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
    11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
    11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
    11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
    11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
    11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
    11/30/2013 09:47:01.703 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
    11/30/2013 09:47:01.703 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
    11/30/2013 09:47:01.703 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
    11/30/2013 09:47:01.719 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
    11/30/2013 09:47:01.734 Locked file: Checking for locked files
    11/30/2013 09:47:04.328 Attempting to pause the 32 bit ngen queue
    11/30/2013 09:47:04.968 Installing product: SQL9
    11/30/2013 09:47:05.781 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
    11/30/2013 09:47:05.781 Installing instance: MSSQLSERVER
    11/30/2013 09:47:05.812 Installing target: SV53704
    11/30/2013 09:47:05.828 Installing file: sqlrun_sql.msp
    11/30/2013 09:47:05.828 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2716429_sqlrun_sql.msp.log
    11/30/2013 09:47:05.828 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
    11/30/2013 09:47:05.828 Registry: Cannot read registry key value "Debug", error 0
    11/30/2013 09:47:06.203 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
    11/30/2013 09:47:06.203 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
    11/30/2013 09:47:06.203 Registry: Cannot read registry key value "Debug", error 0
    11/30/2013 09:47:06.218 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixSQL\Files\sqlrun_sql.msp
    11/30/2013 09:47:06.218 The following exception occurred: Unable to install Windows Installer MSP file  Date: 11/30/2013 09:47:06.218  File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp  Line: 807
    11/30/2013 09:47:06.640 Watson: Param1 = Unknown
    11/30/2013 09:47:06.640 Watson: Param2 = 0x66e
    11/30/2013 09:47:06.640 Watson: Param3 = Unknown
    11/30/2013 09:47:06.640 Watson: Param4 = 0x66e
    11/30/2013 09:47:06.656 Watson: Param5 = copyengine.cpp@807
    11/30/2013 09:47:06.656 Watson: Param6 = Unknown
    11/30/2013 09:47:06.656 Watson: Param7 = SQL9
    11/30/2013 09:47:06.656 Watson: Param8 = @
    11/30/2013 09:47:06.656 Watson: Param9 = x86
    11/30/2013 09:47:06.656 Watson: Param10 = 5069
    11/30/2013 09:47:06.656 Installed product: SQL9
    11/30/2013 09:47:06.656 Installing product: OLAP9
    11/30/2013 09:47:07.468 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
    11/30/2013 09:47:07.484 Installing instance: MSSQLSERVER
    11/30/2013 09:47:07.484 Installing target: SV53704
    11/30/2013 09:47:07.500 Installing file: sqlrun_as.msp
    11/30/2013 09:47:07.500 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\OLAP9_Hotfix_KB2716429_sqlrun_as.msp.log
    11/30/2013 09:47:07.515 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
    11/30/2013 09:47:07.515 Registry: Cannot read registry key value "Debug", error 0
    11/30/2013 09:47:07.640 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
    11/30/2013 09:47:07.640 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
    11/30/2013 09:47:07.640 Registry: Cannot read registry key value "Debug", error 0
    11/30/2013 09:47:07.656 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixAS\Files\sqlrun_as.msp
    11/30/2013 09:47:07.656 The following exception occurred: Unable to install Windows Installer MSP file  Date: 11/30/2013 09:47:07.656  File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp  Line: 807
    11/30/2013 09:47:08.078 Watson: Param1 = Unknown
    11/30/2013 09:47:08.078 Watson: Param2 = 0x66e
    11/30/2013 09:47:08.078 Watson: Param3 = Unknown
    11/30/2013 09:47:08.078 Watson: Param4 = 0x66e
    11/30/2013 09:47:08.078 Watson: Param5 = copyengine.cpp@807
    11/30/2013 09:47:08.078 Watson: Param6 = Unknown
    11/30/2013 09:47:08.078 Watson: Param7 = OLAP9
    11/30/2013 09:47:08.078 Watson: Param8 = @
    11/30/2013 09:47:08.078 Watson: Param9 = x86
    11/30/2013 09:47:08.078 Watson: Param10 = 5069
    11/30/2013 09:47:08.078 Installed product: OLAP9
    11/30/2013 09:47:08.078 Installing product: RS9
    11/30/2013 09:47:08.875 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
    11/30/2013 09:47:08.875 Installing instance: MSSQLSERVER
    11/30/2013 09:47:08.890 Installing target: SV53704
    11/30/2013 09:47:08.890 Installing file: sqlrun_rs.msp
    11/30/2013 09:47:08.890 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\RS9_Hotfix_KB2716429_sqlrun_rs.msp.log
    11/30/2013 09:47:08.890 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
    11/30/2013 09:47:08.890 Registry: Cannot read registry key value "Debug", error 0
    11/30/2013 09:47:09.015 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
    11/30/2013 09:47:09.015 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
    11/30/2013 09:47:09.015 Registry: Cannot read registry key value "Debug", error 0
    11/30/2013 09:47:09.031 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixRS\Files\sqlrun_rs.msp
    11/30/2013 09:47:09.047 The following exception occurred: Unable to install Windows Installer MSP file  Date: 11/30/2013 09:47:09.047  File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp  Line: 807
    11/30/2013 09:47:09.593 Watson: Param1 = Unknown
    11/30/2013 09:47:09.593 Watson: Param2 = 0x66e
    11/30/2013 09:47:09.593 Watson: Param3 = Unknown
    11/30/2013 09:47:09.609 Watson: Param4 = 0x66e
    11/30/2013 09:47:09.609 Watson: Param5 = copyengine.cpp@807
    11/30/2013 09:47:09.609 Watson: Param6 = Unknown
    11/30/2013 09:47:09.609 Watson: Param7 = RS9
    11/30/2013 09:47:09.609 Watson: Param8 = @
    11/30/2013 09:47:09.609 Watson: Param9 = x86
    11/30/2013 09:47:09.609 Watson: Param10 = 5069
    11/30/2013 09:47:09.625 Installed product: RS9
    11/30/2013 09:47:09.625 Installing product: NS9
    11/30/2013 09:47:10.406 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
    11/30/2013 09:47:10.406 Installing instance: NS
    11/30/2013 09:47:10.422 Installing target: SV53704
    11/30/2013 09:47:10.422 Installing file: sqlrun_ns.msp
    11/30/2013 09:47:10.422 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\NS9_Hotfix_KB2716429_sqlrun_ns.msp.log
    11/30/2013 09:47:10.422 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
    11/30/2013 09:47:10.422 Registry: Cannot read registry key value "Debug", error 0
    11/30/2013 09:47:10.531 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
    11/30/2013 09:47:10.531 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
    11/30/2013 09:47:10.531 Registry: Cannot read registry key value "Debug", error 0
    11/30/2013 09:47:10.547 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixNS\Files\sqlrun_ns.msp
    11/30/2013 09:47:10.547 The following exception occurred: Unable to install Windows Installer MSP file  Date: 11/30/2013 09:47:10.547  File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp  Line: 807
    11/30/2013 09:47:10.890 Watson: Param1 = Unknown
    11/30/2013 09:47:10.890 Watson: Param2 = 0x66e
    11/30/2013 09:47:10.890 Watson: Param3 = Unknown
    11/30/2013 09:47:10.890 Watson: Param4 = 0x66e
    11/30/2013 09:47:10.890 Watson: Param5 = copyengine.cpp@807
    11/30/2013 09:47:10.890 Watson: Param6 = Unknown
    11/30/2013 09:47:10.890 Watson: Param7 = NS9
    11/30/2013 09:47:10.890 Watson: Param8 = @
    11/30/2013 09:47:10.890 Watson: Param9 = x86
    11/30/2013 09:47:10.890 Watson: Param10 = 5069
    11/30/2013 09:47:10.890 Installed product: NS9
    11/30/2013 09:47:10.890 Installing product: DTS9
    11/30/2013 09:47:11.703 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
    11/30/2013 09:47:11.703 Installing instance: Integration Services
    11/30/2013 09:47:11.703 Installing target: SV53704
    11/30/2013 09:47:11.703 Installing file: sqlrun_dts.msp
    11/30/2013 09:47:11.703 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log
    11/30/2013 09:47:11.703 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
    11/30/2013 09:47:11.718 Registry: Cannot read registry key value "Debug", error 0
    11/30/2013 09:47:11.890 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
    11/30/2013 09:47:11.890 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
    11/30/2013 09:47:11.906 Registry: Cannot read registry key value "Debug", error 0
    11/30/2013 09:47:11.906 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixDTS\Files\sqlrun_dts.msp
    11/30/2013 09:47:11.922 The following exception occurred: Unable to install Windows Installer MSP file  Date: 11/30/2013 09:47:11.922  File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp  Line: 807
    11/30/2013 09:47:12.328 Watson: Param1 = Unknown
    11/30/2013 09:47:12.328 Watson: Param2 = 0x66e
    11/30/2013 09:47:12.328 Watson: Param3 = Unknown
    11/30/2013 09:47:12.328 Watson: Param4 = 0x66e
    11/30/2013 09:47:12.328 Watson: Param5 = copyengine.cpp@807
    11/30/2013 09:47:12.328 Watson: Param6 = Unknown
    11/30/2013 09:47:12.328 Watson: Param7 = DTS9
    11/30/2013 09:47:12.328 Watson: Param8 = @
    11/30/2013 09:47:12.328 Watson: Param9 = x86
    11/30/2013 09:47:12.328 Watson: Param10 = 5069
    11/30/2013 09:47:12.343 Installed product: DTS9
    11/30/2013 09:47:12.343 Installing product: SQLTools9
    11/30/2013 09:47:13.125 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
    11/30/2013 09:47:13.140 Installing instance: SQL Tools
    11/30/2013 09:47:13.140 Installing target: SV53704
    11/30/2013 09:47:13.156 Installing file: sqlrun_tools.msp
    11/30/2013 09:47:13.172 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB2716429_sqlrun_tools.msp.log
    11/30/2013 09:47:13.172 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
    11/30/2013 09:47:13.172 Registry: Cannot read registry key value "Debug", error 0
    11/30/2013 09:47:13.484 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
    11/30/2013 09:47:13.484 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
    11/30/2013 09:47:13.484 Registry: Cannot read registry key value "Debug", error 0
    11/30/2013 09:47:13.500 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixTools\Files\sqlrun_tools.msp
    11/30/2013 09:47:13.500 The following exception occurred: Unable to install Windows Installer MSP file  Date: 11/30/2013 09:47:13.500  File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp  Line: 807
    11/30/2013 09:47:13.828 Watson: Param1 = Unknown
    11/30/2013 09:47:13.828 Watson: Param2 = 0x66e
    11/30/2013 09:47:13.843 Watson: Param3 = Unknown
    11/30/2013 09:47:13.843 Watson: Param4 = 0x66e
    11/30/2013 09:47:13.843 Watson: Param5 = copyengine.cpp@807
    11/30/2013 09:47:13.843 Watson: Param6 = Unknown
    11/30/2013 09:47:13.843 Watson: Param7 = SQLTools9
    11/30/2013 09:47:13.843 Watson: Param8 = @
    11/30/2013 09:47:13.843 Watson: Param9 = x86
    11/30/2013 09:47:13.843 Watson: Param10 = 5069
    11/30/2013 09:47:13.843 Installed product: SQLTools9
    11/30/2013 09:47:13.843 Hotfix package completed
    11/30/2013 09:47:13.859 Attempting to continue the 32 bit ngen queue

    Hi ~ any idea on this case ? here is the one MSP installation log:
    === Verbose logging started: 11/30/2013  21:28:15  Build type: SHIP UNICODE 4.05.6001.00  Calling process: e:\de60d5388bc787220900e629b152c9\hotfix.exe ===
    MSI (c) (D4:28) [21:28:15:681]: Resetting cached policy values
    MSI (c) (D4:28) [21:28:15:681]: Machine policy value 'Debug' is 0
    MSI (c) (D4:28) [21:28:15:681]: ******* RunEngine:
               ******* Product: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
               ******* Action: 
               ******* CommandLine: **********
    MSI (c) (D4:28) [21:28:15:681]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (D4:28) [21:28:15:681]: Grabbed execution mutex.
    MSI (c) (D4:28) [21:28:15:697]: Cloaking enabled.
    MSI (c) (D4:28) [21:28:15:697]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (D4:28) [21:28:15:697]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (A8:C0) [21:28:15:697]: Running installation inside multi-package transaction {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
    MSI (s) (A8:C0) [21:28:15:697]: Grabbed execution mutex.
    MSI (s) (A8:04) [21:28:15:697]: Resetting cached policy values
    MSI (s) (A8:04) [21:28:15:697]: Machine policy value 'Debug' is 0
    MSI (s) (A8:04) [21:28:15:697]: ******* RunEngine:
               ******* Product: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
               ******* Action: 
               ******* CommandLine: **********
    MSI (s) (A8:04) [21:28:15:697]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (A8:04) [21:28:15:931]: End dialog not enabled
    MSI (s) (A8:04) [21:28:15:931]: Original package ==> C:\WINDOWS\Installer\181c1.msi
    MSI (s) (A8:04) [21:28:15:931]: Package we're running from ==> C:\WINDOWS\Installer\181c1.msi
    MSI (s) (A8:04) [21:28:15:994]: APPCOMPAT: looking for appcompat database entry with ProductCode '{EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}'.
    MSI (s) (A8:04) [21:28:15:994]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (A8:04) [21:28:15:994]: Opening existing patch 'C:\WINDOWS\Installer\e9ff36e.msp'.
    MSI (s) (A8:04) [21:28:16:010]: Opening existing patch 'C:\WINDOWS\Installer\239697ae.msp'.
    MSI (s) (A8:04) [21:28:16:056]: File will have security applied from OpCode.
    MSI (s) (A8:04) [21:28:16:056]: Original patch ==> e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp
    MSI (s) (A8:04) [21:28:16:056]: Patch we're running from ==> C:\WINDOWS\Installer\1f80a9f.msp
    MSI (s) (A8:04) [21:28:16:072]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp' against software restriction policy
    MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: DigitalSignature 3: -2147287038 
    MSI (s) (A8:04) [21:28:16:072]: SOFTWARE RESTRICTION POLICY: e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp is not digitally signed
    MSI (s) (A8:04) [21:28:16:072]: SOFTWARE RESTRICTION POLICY: e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp is permitted to run at the 'unrestricted' authorization level.
    MSI (s) (A8:04) [21:28:16:072]: SequencePatches starts. Product code: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}, Product version: 9.00.1399.06, Upgrade code: {2B33A057-4470-45CD-8E63-863CB78FC626}, Product language 1033
    MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Tables 3: -2147287038 
    MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Columns 3: -2147287038 
    MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Tables 3: -2147287038 
    MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Columns 3: -2147287038 
    MSI (s) (A8:04) [21:28:16:072]: PATCH SEQUENCER: verifying the applicability of QFE patch e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp against product code: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}, product version: 9.00.1399.06, product language
    1033 and upgrade code: {2B33A057-4470-45CD-8E63-863CB78FC626}
    MSI (s) (A8:04) [21:28:16:072]: PATCH SEQUENCER: QFE patch e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp is not applicable.
    MSI (s) (A8:04) [21:28:16:072]: SequencePatches returns success.
    MSI (s) (A8:04) [21:28:16:072]: Final Patch Application Order:
    MSI (s) (A8:04) [21:28:16:072]: Other Patches:
    MSI (s) (A8:04) [21:28:16:072]: Unknown\Absent: {4C3BC5C8-67A5-40F1-85B7-D9341A5F7B6C} - e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp
    MSI (s) (A8:04) [21:28:16:072]: Superseded: {5E9ADA2D-3132-42CF-8628-D2ADA0F335EE} - 
    MSI (s) (A8:04) [21:28:16:072]: Superseded: {32BCE9F2-8686-487A-80A9-A401C0F7DCBD} - 
    MSI (s) (A8:04) [21:28:16:072]: Unknown\Absent: {D23D25E7-0AB4-41EE-81B5-F0CF34D1BA2B} - 
    MSI (s) (A8:04) [21:28:16:072]: Unknown\Absent: {CF321155-04AA-4CF8-BB9A-DA3144835E3E} - 
    MSI (s) (A8:04) [21:28:16:072]: Machine policy value 'DisablePatch' is 0
    MSI (s) (A8:04) [21:28:16:072]: Machine policy value 'AllowLockdownPatch' is 0
    MSI (s) (A8:04) [21:28:16:072]: Machine policy value 'DisableLUAPatching' is 0
    MSI (s) (A8:04) [21:28:16:072]: Disallowing uninstallation of patch {CF321155-04AA-4CF8-BB9A-DA3144835E3E} because the patch is marked as not uninstallable
    MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services - Update 'Service Pack 4 for SQL Server Integration Services 2005 ENU (KB2463332)' could not be removed. Error code 1646. Additional information is available in the log
    file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log.
    MSI (s) (A8:04) [21:28:16:072]: Windows Installer removed an update. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Update Name: Service Pack 4 for SQL Server Integration Services 2005 ENU
    (KB2463332). Removal success or error status: 0.
    MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services - Update '{4C3BC5C8-67A5-40F1-85B7-D9341A5F7B6C}' could not be installed. Error code 1646. Additional information is available in the log file C:\Program Files\Microsoft
    SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log.
    MSI (s) (A8:04) [21:28:16:072]: Windows Installer installed an update. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Update Name: {4C3BC5C8-67A5-40F1-85B7-D9341A5F7B6C}. Installation success
    or error status: 1646.
    MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services - Update 'GDR 5057 for SQL Server Integration Services 2005 ENU (KB2494120)' could not be removed. Error code 1646. Additional information is available in the log file C:\Program
    Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log.
    MSI (s) (A8:04) [21:28:16:072]: Windows Installer removed an update. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Update Name: GDR 5057 for SQL Server Integration Services 2005 ENU (KB2494120).
    Removal success or error status: 1646.
    MSI (s) (A8:04) [21:28:16:072]: Note: 1: 1708 
    MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services -- Installation failed.
    MSI (s) (A8:04) [21:28:16:072]: Windows Installer installed the product. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Installation success or error status: 1646.
    MSI (s) (A8:04) [21:28:16:088]: Attempting to delete file C:\WINDOWS\Installer\1f80a9f.msp
    MSI (s) (A8:04) [21:28:16:088]: MainEngineThread is returning 1646
    MSI (s) (A8:C0) [21:28:16:088]: No System Restore sequence number for this installation.
    Uninstallation of the patch package is not supported.
    C:\WINDOWS\Installer\181c1.msi
    MSI (s) (A8:C0) [21:28:16:088]: User policy value 'DisableRollback' is 0
    MSI (s) (A8:C0) [21:28:16:088]: Machine policy value 'DisableRollback' is 0
    MSI (s) (A8:C0) [21:28:16:088]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2 
    MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2 
    MSI (s) (A8:C0) [21:28:16:088]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (A8:C0) [21:28:16:088]: Restoring environment variables
    MSI (c) (D4:28) [21:28:16:088]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (D4:28) [21:28:16:088]: MainEngineThread is returning 1646
    === Verbose logging stopped: 11/30/2013  21:28:16 ===

  • Time out fail over

    On this system:
    OS: Solaris 10 11/06 s10s_u3wos_10 SPARC
    Cluster version: 3.1u4
    A- Normally after how much time resource is moved to the other node if ipmp fails (e.g. gateway is unreacheable) ?
    B- What happens if ipmp fails in both server ? packages are kept on their nodes ?
    C- Does it exist timeout over 10 minutes in cluster configuration ?

    u have 2 options - u could increase the back end time out to a very large value so that server can wait rather than timing out rather than failing over or to do some thing like
    <Object name=�default�>
    NameTrans fn=map from=/ name=reverse-proxy-/
    </Object>
    <Object name=�reverse-proxy-/�>
    Route fn=set-origin-server server=server1
    ObjectType fn=http-client-config timeout=600
    </Object>
    see - http://docs.sun.com/app/docs/doc/820-4841/gdhrg?a=view
    ( or simply disable any fail over but have different individual servers distributing load across different application)
    split your uri or application so that each application goes to 1 back end server. for example, let us say - u have 2 java applications that u would like jboss to do the job for you, u could do some thing like
    now, u could edit your obj.conf or (<vs>-obj.conf) depending on your configuration so that it looks like this
    <Object name=�default�>
    NameTrans fn=map from=/ name=reverse-proxy-/
    </Object>
    <Object name=�reverse-proxy-/�>
    <If $uri =~ /foo1>
    Route fn=set-origin-server server=<&#349;erver1>
    </If>
    <If $uri =~ /foo2>
    Route fn=set-origin-server server=<&#349;erver2>
    </If>
    </Object>
    btw - i will file a RFE on your behalf for this feature.

  • Compare time taken by sqls

    Hi experts,
    Can any one refer me any tool or utility by which i can get time taken by different sql's without using explain plan..
    Regards,
    SKP

    If you are running it from SQL*Plus, just set timing on
    SQL> set timing on
    SQL> select empno,ename from emp where deptno=10;
    EMPNO ENAME
    7782 CLARK
    7839 KING
    7934 MILLER
    Elapsed: 00:00:01.97
    SQL> select empno,ename from emp where deptno=20;
    EMPNO ENAME
    7369 SMITH
    7566 JONES
    7788 SCOTT
    7876 ADAMS
    7902 FORD
    Elapsed: 00:00:01.91
    SQL>

  • Time Machine Failing Over and Over

    So I am backing up my EX HD with Time Machine for the first time and it keep failing. It stops between 3 gb and about 20gb (I have 180 total). Keeps giving the error "The backup was not performed because an error occurred while copying files to the backup disk ". The HD I was using is a brand new Western Digital that I formatted two partitions. One for my old windows machine and this MBP. I formatted it exactly several times and it keeps failing.
    My neighbor said I need to have a HD that is completely clean, so i went and bought a brand new Iomega HD just for Mac. It also failed over and over! I have read about every thread out there and cant seem to find a possible cause other than my internal HD is toast.
    Has anyone else had this experience before?
    -T

    Sorry I'm not sure I understand your question now.
    Let me try: if you excluded your Documents folder and TM now works, your backup size was likely the problem.
    So if you simply remove Documents from the TM exclusion list you will run back into the size problem... no good.
    If you first delete the large contents from the documents folder on your startup disk, then you can ask TM to backup again the Documents folder by removing it from the TM exclusion list, but obviously only what remains there (not the deleted material) will be saved by TM.
    In other words, if you want to keep your 80 GB files on your startup disk, either you do not backup them or you use a larger backup disk. Otherwise you may remove the 80 GB from your startup disk; but now you probably want to keep 2 copies of them in 2 different external disks, for safety reasons, without using TM.
    Did I answer your question ?
    Piero
    Message was edited by: PieroF

Maybe you are looking for

  • Error in attach PDF file into email

    Hi, currently i have problem in sending out email as i try to go through the <b>Offline Interactive PDF Form Using E-Mail</b> and also <b>Uploading and Downloading Files in Web Dynpro Java</b> and then i manage to get the file that i want to upload i

  • Java wont install/unable to access jarfileC:\documents and settings

    Help! I can not get the Java installed...keep getting a javaws corrupt file error and the program fails to launch. (Java Virtual Machine Launcher) Keep uninstalling and reinstalling program...nothing is working. PLS HELP!

  • OpenOffice and Thunderbird

    Some time ago (a few months maybe), Thunderbird stopped letting me open OpenOffice document types by double clicking the attachment. Anyone know why this behavior changed and how to fix it? Obviously being able to open attachments by double clicking

  • Replacing natural keys with surrogate keys

    Hi, We have database that is runnig with some old applications since many years. In the database, all the primary key are natural keys (composed with many columns). The applications are developped with mod pl/sql and oracle forms6i / designer6i. We a

  • CSM in Bridge mode and Server initiated connections

    I know one can use Source NAT for server initiated connections back to VIP using CSM in routed mode. How do I achieve the same for bridge mode? Thanks in advance, Shahid