B1i (2005) installation failedSo far:  windows XP, MS-SQL 2005 express: ok

Dear All,
I try to install B1i for NW 2005 on a SBO 2005B installation. I have installed all prerequisites like JDK, MSXML, Tomcat (no blanks in path). When running the setup program and after all information gathered, the connection to the MS-SQL 2005 database succeeds and the final installation step starts but returns the message:
"Initail database failed, make sure Tomcat or mini-http is shut down and please check your database's status and try again"
Looking into MS-SQL shows a database beeing created named localhost/B1i. Tomcat and mini-http are definately shut down. When starting Tomcat, it is accessible via http://localhost:8080.
System Parameters:
windows server 2003
SBO 2005B
java: 1.4.2.19
tomcat 5.5.27 including compat package for 1.4.2.19)
sql jdbc 1.2.2828.100
msxml 4.0 SP 2
I can not find an error in the system. Is there a way to diagnose what is happening and does anyone have an idea where the problem lies?
Ciao, Mathias
[Update]
I have tried JDBC 2.0.1008 and JDBC 2.0.1607 - both lead to a fatal error when trying to connect to the database. I assume this is due to Java JDK 1.4.2 as JDBC requires Java 5.0 (1.5.0)
Does anybody know if I can use JDK 1.5.0_17 instead of 1.4.2_19?
[Update 2]
I have tried to install the B1i on two other servers with identical setup and it worked. However, this will not help me with this machine... On the other side, it shows, that there is nothing wrong with the procedure I am using
I found by the way: B1i works fine with MSSQL 2005 Express, it works with jdk 1.5.0.17 (and then JDBC 2.0)
[Update 3]
So far:
windows XP, MS-SQL 2005 express: ok
windows XP, MS-SQL 2005 express, SBO2005A: ok
windows 2003, MS-SQL 2005 SBO2005A: fail
windows 2003, MS-SQL 2005 SBO2005B: fail
windows 2003, MS-SQL 2005 SBO2007A: ok
windows 2003, MS-SQL 2005 Netweaver 2004S: fail
Unfortunately the three servers where it fails are the ones I need to use for production
The precise error state is that the install routine creates the database in SQL 2005 and then reports that it can not create the database. Is there something I should check in SQL 2005?
Edited by: Mathias Wilhelm on Feb 11, 2009 5:17 PM

Salut Eddy,
I tried it with tomcat 5.0.30 - no success. JDK is 1.4.2.19
I tried it with tomcat 5.5.27 - no success. JDK was 1.4.2.19 and 1.5.17
I checked the database: The structure is created but the tables are not created. As the user 'sa' has full admin rights it must be with the access path to the database that is wrong. What I do not understand is, why the installation routine is able to connect to the database to create B1i and then unable to create the tables. I checked in the log files of the db and found no error messages. I tested this as well by using a wrong password for sa or a wrong user. In both cases, the installation routine fails already when checing the existence of B1i database
[Update]
In the meantime:
Checked permissions on database
Checked that administrator is member of local admin group
Checked JAVA_HOME environment variable
Found collation SQL_Latin1_General_CP1_CI_AS for working setup and SQL_Latin1_General_CP1_CS_AS in failing setup
Checked all security settings by comparing to working setup
Checked event viewer and found no errors
Checked all log files and found no errors
Checked that sa can create tables manually in localhost\B1i
Ciao, Mathias
Edited by: Mathias Wilhelm on Feb 12, 2009 2:36 PM

Similar Messages

  • Xp_logininfo "Installation problem on windows 2003 with Sql 2005"

    Hi every one
    I am facing a problem during the installation of Solution Manager 4.0 on Windows 2003 server with Ms Sql 2005, I received the following error
    Msg 15404, Level 16, State 19, Procedure xp_logininfo, Line 60.
    Its some how look likes that the user "SID"ADM
    Can any one give me a clue
    thanks
    Kind Regards
    Sohail

    Hi All,
    This would solve your problem
    First of all this error is <b>MSSQL error</b>.
    When you perform an action on an instance of SQL Server that requires SQL Server to resolve the credentials of a Microsoft Windows NT domain user account, you may receive an error message that is similar
    Server: Msg 8198, Level 16, State XX, Procedure <Stored Procedure Name>, Line <line Number>
    Could not obtain information about Windows NT group/user '<Domain\Account Name>'.
    To resolve the credentials of a Windows NT domain user account, SQL Server uses the xp_logininfo system stored procedure. Here is a list of the common scenarios where you may notice that the xp_logininfo system stored procedure fails and causes the 8198 error.
    • When you use an xp_sendmail extended stored procedure.
    • When you set up replication.
    • When you run a SQL Server Agent job.
    SQL Server may run the xp_logininfo system stored procedure to retrieve information about the Windows domains and the user accounts, even if the user does not do so explicitly. Therefore, if you receive an 8198 error message and the error message mentions the xp_logininfo system stored procedure as the procedure, you must use <b>SQL Profiler</b> to trace and to troubleshoot the exact point of failure.
    You can go through this link for more info...
    http://support.microsoft.com/?kbid=834124
    Feel Free to Revert back...
    --Thanks and Regards,
    Ragu
    ERP,
    Suzlon Energy Limted, Pune
    Extn: 2638
    +919370675797
    I have no limits for others sky is only a reason

  • Windows authentication for SQL 2005 DB connect

    Hi all,
    I'm trying to create a DB connect
    in the connection parameters when I mention a user name and password who is created as a SQL authentication then it is working fine.
    but in my connection parameters if I mention a user name password who have a Windows authentication in the SQL 2005 which we are trying to connect then it gives an error. It is not connecting .
    Can you please tell me how can we connect using a windows authentication.
    Mey

    Solution to solve the actual issue :
    For the SAP system to use standard default NT authentication
    Please refer to this link: http://help.sap.com/saphelp_nw04s/helpdata/en/9c/d736b880c34f76b507bac7751a0474/content.htm
    1.       Database login:
    SQL Server login with System Administrator privileges, that is this login should be member of the sysadmin fixed server role on the target SQL Server. If such a login does not exist, you have to create it on the target SQL Server. The SAP multi-connect mechanism allows both integrated security logins and the use of SQL Server authentication. For security reasons, we highly recommend to use integrated security (Windows authentication). If you use Windows security, leave this field empty.
    2.     &#61601;        Password / Re-enter password :
    If you have decided to use integrated security, leave these fields empty. Otherwise enter the password of the SQL Server login.
    The above pointer was used to solve the login issue but we still had issues in getting the schema visible in SAP BW. As the user ID was left blank we were not able to get the schema view for the <blank> user.
    Note to be applied to solve the Schema issue :
    note 1091929 : &#61664; Link
    so now you can enter the schema to be used in DS creaton screen.

  • SQL 2005 x64 poor performance after migration from SQL 2005 x86

    Recently We've migrated SQL 2005 x86 SP1 Enterprise running on Windows 2003 Enterprise to new hardware where is running Windows 2008 SP2 and SQL 2005 x64 SP4 with CU3.
    In the work day, there are sometime SQL excpetions like this below. On other hand i can also tell that we already found some queries which has some inner joins and where clauses on nvarchar fileds, because of the nature of application. Such a query
    is running for about 11 seconds on old SQL server, and about 6 minutes on new SQL server. My main question if is this possible just with a change to new architecture of SQL and more last patches and updates for SQL 2005. Is there any way how to get
    this queries running faster, without rewritng them with new ones? Is this also possible this could be also cause for SQL exceptions, which we are facing on SQL server?
    About new hardware, for now we can't find it something wrong. There is basic configuration:
    Cisco UCS  C220 M3S (1U server)
    32GB RAM
    Intel(R)Xeon® CPU [email protected], 6 core
    Disk system: 4xSAS 300GB in RAID5 (OS and DATA) and 2xSATA 1TB in RAID1 (SQL backup)
    RAID controller: LSI MegaRAID SAS 9271-8i (with latest driver and firmware)
    Part of log of dump file:
    2014-05-09 08:30:07.08 spid86      Error: 17311, Severity: 16, State: 1.
    2014-05-09 08:30:07.08 spid86      SQL Server is terminating because of fatal exception c0000264. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling.
    Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
    2014-05-09 08:30:07.08 spid86      Using 'dbghelp.dll' version '4.0.5'
    2014-05-09 08:30:07.08 spid86      **Dump thread - spid = 86, PSS = 0x0000000132A67ED0, EC = 0x0000000132A67EE0
    2014-05-09 08:30:07.08 spid86      ***Stack Dump being sent to D:\MSSQL.1\MSSQL\LOG\SQLDump0087.txt
    2014-05-09 08:30:07.08 spid86      * *******************************************************************************
    2014-05-09 08:30:07.08 spid86      *
    Thanks for any help,
    Matjaž

    >Is there any way how to get this queries running faster, without rewriting them with new ones?
    You need to perform basic performance tuning steps in the new environment.
    Software optimization:
    http://www.sqlusa.com/articles/query-optimization/
    Disk optimization:
    http://www.sqlusa.com/bestpractices/configureharddisk/
    Memory optimization:
    http://www.sqlusa.com/bestpractices/memory-configuration/
    REBUILD INDEXES, eliminate missing indexes & UPDATE STATISTICS.
    If there is still a problem, look in Activity Monitor for expensive queries. Optimize them. As a general rule, you don't want to have expensive queries in RDBMS.
    Kalman Toth Database & OLAP Architect
    SQL Server 2014 Design & Programming
    New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

  • CRM 7.0 installation failed on Windows 2008 R2  SQL Server 2008 SP1

    Hello I'm currently trying to install CRM 7.0 on a windows 2008 R2 (64B) plateform  with SQL Server 2008 SP1 as database engine
    while launching sapinst.exe i'm facing this issue  that i cannot get rid of it 
    Could someone Help , would really be appreciated as i'm a newby on SAP world
    thanks a lot
    Unable to start a service execution.  Please check the following information for the possibble reason and inform the installation development :  Opened sylib701_1.dll exe dir is C:/Users/SAPINS1/AppData/Local/Temp/2/sapinst_exe.3492.1286357336 Opened C:/Users/SAPINS1/AppData/Local/Temp/2/sapinst_exe.3492.1286357336/iaguieng701_1.dll receiving and sending on port 21200 Environment variable SAPINST_JRE_HOME set to value 'C:/Users/SAPINS1/AppData/Local/Temp/2/sapinst_exe.3492.1286357336/jre'. exe dir is C:/Users/SAPINS1/AppData/Local/Temp/2/sapinst_exe.3492.1286357336 Creating file C:\Program Files\sapinst_instdir\x. Removing file C:\Program Files\sapinst_instdir\x. Opened C:/Users/SAPINS~1/AppData/Local/Temp/2/sapinst_exe.3492.1286357336/iakdblib701_1.dll  This is SAPinst, version 701_1, make variant 701_REL, build 1015514 compiled on Oct 3 2008, 01:51:15  MessageLib initialized successfully. showing dlg diProductChoice <dialog sid="diProductChoice"> <title>Welcome to SAP Installation Master</title> <dialog/> Login in progress Connection request to guiengine backend by host 169.254.138.68 Protocol version is 3.1 Send connect information client logged on Waiting for an answer from GUI CDialogHandler: ACTION_NEXT requested <dialog sid="diProductChoice"> <dialog/> Creating file C:\Windows\System32\x. Removing file C:\Windows\System32\x. showing dlg diRestartOrCancel <dialog sid="diRestartOrCancel"> Dialog does not contain standard input handler, so the backend is not able to generate a log entry <dialog/> Waiting for an answer from GUI current working directory is C:/Windows/System32 Creating file C:\Program Files\sapinst_instdir\x. Removing file C:\Program Files\sapinst_instdir\x. Unable to open URL file://C:\Windows\System32\control.xml.  The execution will be terminated now.

    Hi!
    Windows 2008 R2 is not yet listed in the PAM - and hence not yet supported. The technical prerequisites are met (with a special kernel patch) but not all software is released, so you may get it to run technically but not everything is tested and so, you should not install any SAP system on it!
    In fact, and just to provide you further details it is not possible to expect the 710 products released for Windows Server 2008 R2 before around four weeks; 700 products will be released even after 710.
    See [SAP note 1383873|https://service.sap.com/sap/support/notes/1383873]  ("Windows Server 2008 R2 Support").
    You can be always up to date with the latest Windows news at:
    [SAP on Microsoft Windows|SAP on Microsoft Windows] --> Support of Microsoft Windows Server 2008 R2
    Cheers!

  • SQL Server Express 2012 SP2 installation hangs during extract phase

    Greetings!
    I am having an issue with trying to silent install SQL Server Express 2012 SP2 (x86).
    I have a proprietary installation framework, which is calling the SQL Server Express installer.
    The SQL Server Express installer starts extracting files to c:\{some guid}. The folder reaches about 11 mb in size, and then nothing further happens. No activity on the machine, CPU or disk - I have waited up to 15 minutes to verify this. On the normal installation,
    the size of this folder is ~650 mb.
    Here are the things I've also tested:
    - I'm experiencing these symptoms on both Windows 7 and Windows Server 2012 R2 (haven't tested other platforms)
    - If I launch exactly the same command from the command prompt, the installation goes through as normal
    - If I replace the SQL Server Express 2012 SP2 with SQL Server Express 2012 SP1, and install via our installation framework, the installation goes through as normal
    - I have checked and double-checked that our installation framework is started with administrative privileges.
    - From my previous search attempts, I have seen issues where the installer would hang or fail when launched from inside an msi, which would result in a log in C:\Program Files (x86)\Microsoft SQL Server\<something something>. These are not the symptoms
    I am experiencing. The C:\Program Files (x86)\Microsoft SQL Server\ folder is not even created!
    Any suggestions, or places I can look to figure out why it's not proceeding? For now, I have worked around the issue by including SP1 instead of SP2, but ideally I'd like to base my solution on the most recent service pack.

    Hello Alberto!
    The installation framework does check for this. I'm also certain that these prerequisites are fulfilled. 
    When the SQL Server process hangs, I can kill the process, copy/paste the exact command that was executed from the installation framework's log files, and execute that command in a command prompt - and then the installation runs as expected.
    The installation framework installs SQL Server Express correctly if I use the 2008 R2 SP1 express or the 2012 SP1 Express installer. It's just the SP2 installer that is giving me problems.
    The only difference I can think of is that the installation framework is a 32-bit process, which calls the SQL Server installer, while the command prompt is a 64-bit application. I am installing the SQLEXPR_x86_ENU.exe
    from http://www.microsoft.com/en-us/download/details.aspx?id=43351, so it should be compatible with my 32 bit environment - 
     "SQLEXPR_x86 is the same product but supports installation onto both 32-bit and 64-bit (WoW) operating systems"
    Tomorrow, I will try:
    - Installing on Windows 7 32-bit
    - Trying to launch the SQL Server installer from a powershell (x86) prompt, to emulate a 32-bit environment on a 64-bit machine

  • Bajo rendimiento con windows 2008 y sql 2008

    Instale windows 2008,Sql 2008 y le hice un upgrade a Sap Business one pl42 pero el rendimiento es un 80% menos que cuando tenia windows 2003 y sql 2005  .
    El rendimiento me bajo considerablemente y no se donde buscar el por que , me pueden ayudar

    Hola evelyn, buen día.
    Vale la pena preguntarte lo siguiente: estás utilizando para la instalación de MS Windows Server 2008 y MS SQL Server 2008 el mismo hardware (Servidor) que estaban usando para MS Windows Server 2003 y MS SQL Srever 2005?
    Yo tengo instalado SAP BO, PL42 en un servidor IBM x3650, con 1 procesador Quadcore, 4GB de RAM y 3 Discos SAS 15K de 146GB, además de eso MS Windows Server 2008 Standard Edition x64Bit con Hyper-V, como servidor virtual MS Windows Server 2008 Standard Edition 32Bit con MS SQL Server 2005, el rendimiento es óptimo (vuela literalmente).
    Resumen: el problema de performance pudiera estar vinculado a las capacidades del Hardware que estás usando como servidor. ¿Qué piensas al respecto?
    Saludos,
    Erick Gómez

  • Has anyone upgraded sql 2005 to sql 2008 and win 2008 Netweaver 7.0, ECC 6?

    We are currently running the following landscapes
    Netweaver BI 7..0 on windows 2003 , sql 2005,
    ECC 6.0 on windows 2003, sql 2005
    SAP Portal 7 on windoes 2003 , sql 2005
    And would like to plan the migration to windows 2008, sql 2008 IE 7.0
    I just wanted to get some feedback regarding if someone has already done this and how you all went about to upgrade? Issues you encountered, things to avoid, all that good stuff
    Without doing much research yet, and having just completed the migration from 32bit OS to 64bit and sql 2000 to sql 2005, I had to perform a NEW install of SAP on parallel servers , export from 32bit and import to 64bit servers
    When we upgrade to windows 2008 and sql 2008, will we ALSO require to do a NEW install of SAP? just like what I just finished?
    Please advise?
    Regards & Thank You in Advance
    Maria

    Hello Maria,
    Refer to http://www.microsoft.com/sqlserver/2008/en/us/upgrade.aspx
    Also you can refer to SAP guide for database upgrade to SQL server 2008 ,just go to the followng link
    http://service.sap.com/instguides --> Other Documentation --> Database Upgrades --> MS SQL Server
    Hope it helps
    Rohit

  • Not able to connect to MS SQL 2005 Evaluation version

    Hi,
    I have installed MS SQL 2005 Evaluation version(downloaded from microsoft site) on my win2k3 Enterprise Edition I am writing a java application that connects to MS SQL 2005.
    I have downloaded the MS SQL 2005 JDBC driver. And i unjarred the
    I have unjarred the sqljdbc.jar file and kept the com folder and my .java file in the same folder.
    When i am trying to connect, I am getting the following error:
    com.microsoft.sqlserver.jdbc.SQLServerException: Failed Logon:com.microsoft.sqlserver.jdbc.SQLServerException: TCP/IP connection failed to host:155.35.54.160 java.net.ConnectException: Connection refused:connect
    My code look like this:
    try {
    Class.forName ("com.microsoft.sqlserver.jdbc.SQLServerDriver");
    String fs = File.separator;
    String conn_str = "jdbc:sqlserver://155.35.54.160:1433;user=sa;password=SA;databaseName=asdb";
    conn = DriverManager.getConnection ( conn_str );
    catch (Exception e) {System.out.println(e); }
    Please reply.
    Thanks and Regards,
    Sudheer Gajula

    First aid check list for "connection refused":
    - Check host name in connect string.
    - Check port number in connect string.
    - Try numeric IP address of server host in connect string, in case name server is hosed.
    - Are there any firewalls between client and server blocking the port.
    - Check that the db server is running.
    - Check that the db server is listening to the port. On the server, try: "telnet localhost the-port-number". Or "netstat -an", there should be a listening entry for the port. You need to configure the database to accept TCP connections; read the documentation or google.
    - Try "telnet server-host-name the-port-number" from the client, to see if firewalls are blocking it.
    - If "telnet" fails: try telnet with the numeric ip address.
    - If "telnet" fails: does it fail immediately or after an obvious timeout? How long is the timeout?
    - Does the server respond to "ping serverhost" or "telnet serverhost" or "ssh serverhost"?

  • Unable to install SQL 2005 Service Pack 3 (Unable to install Windows Installer MSI file)

    I'm unable to install SQL 2005 Service Pack 3. This results in the following error message: Unable to install Windows Installer MSI file.
    Could someone please help me. Thanks in advance!
    === Verbose logging started: 3-4-2009  9:33:00  Build type: SHIP UNICODE 4.05.6001.00  Calling process: d:\5ddfa356349ddf2e676c336d95c5\hotfix.exe ===
    MSI (c) (E0:88) [09:33:00:404]: Resetting cached policy values
    MSI (c) (E0:88) [09:33:00:404]: Machine policy value 'Debug' is 0
    MSI (c) (E0:88) [09:33:00:404]: ******* RunEngine:
               ******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
               ******* Action:
               ******* CommandLine: **********
    MSI (c) (E0:88) [09:33:00:404]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (E0:88) [09:33:00:404]: Grabbed execution mutex.
    MSI (c) (E0:88) [09:33:00:419]: Cloaking enabled.
    MSI (c) (E0:88) [09:33:00:419]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (E0:88) [09:33:00:419]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (28:28) [09:33:01:747]: Running installation inside multi-package transaction C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
    MSI (s) (28:28) [09:33:01:747]: Grabbed execution mutex.
    MSI (s) (28:CC) [09:33:02:029]: Resetting cached policy values
    MSI (s) (28:CC) [09:33:02:029]: Machine policy value 'Debug' is 0
    MSI (s) (28:CC) [09:33:02:029]: ******* RunEngine:
               ******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
               ******* Action:
               ******* CommandLine: **********
    MSI (s) (28:CC) [09:33:02:685]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (28:CC) [09:33:03:450]: File will have security applied from OpCode.
    MSI (s) (28:CC) [09:33:03:841]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi' against software restriction policy
    MSI (s) (28:CC) [09:33:03:841]: SOFTWARE RESTRICTION POLICY: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi has a digital signature
    MSI (s) (28:CC) [09:33:04:841]: SOFTWARE RESTRICTION POLICY: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi is permitted to run at the 'unrestricted' authorization level.
    MSI (s) (28:CC) [09:33:04:888]: End dialog not enabled
    MSI (s) (28:CC) [09:33:04:888]: Original package ==> C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
    MSI (s) (28:CC) [09:33:04:888]: Package we're running from ==> C:\WINDOWS\Installer\3d3a713.msi
    MSI (s) (28:CC) [09:33:05:497]: APPCOMPAT: looking for appcompat database entry with ProductCode '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'.
    MSI (s) (28:CC) [09:33:05:497]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (28:CC) [09:33:05:685]: MSCOREE not loaded loading copy from system32
    MSI (s) (28:CC) [09:33:05:825]: Note: 1: 2203 2: C:\WINDOWS\Installer\2f1994e.msi 3: -2147287038
    MSI (s) (28:CC) [09:33:05:825]: Opening existing patch 'C:\WINDOWS\Installer\e6ba0.msp'.
    MSI (s) (28:CC) [09:33:05:825]: Note: 1: 2203 2: C:\WINDOWS\Installer\e6ba0.msp 3: -2147287038
    MSI (s) (28:CC) [09:33:05:825]: Couldn't find local patch 'C:\WINDOWS\Installer\e6ba0.msp'. Looking for it at its source.
    MSI (s) (28:CC) [09:33:05:825]: Resolving Patch source.
    MSI (s) (28:CC) [09:33:05:825]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (28:CC) [09:33:05:825]: User policy value 'DisableMedia' is 0
    MSI (s) (28:CC) [09:33:05:825]: Machine policy value 'AllowLockdownMedia' is 0
    MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Media enabled only if package is safe.
    MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Looking for sourcelist for product {EE92F683-5F5C-4970-BB0B-9AC591B60268}
    MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Adding {EE92F683-5F5C-4970-BB0B-9AC591B60268}; to potential sourcelist list (pcode;disk;relpath).
    MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Now checking product {EE92F683-5F5C-4970-BB0B-9AC591B60268}
    MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Media is enabled for product.
    MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
    MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Trying source \\NF04\d$\3db7739bf5c1bb9c50076c418420\HotFixSqlSupport\Files\.
    MSI (s) (28:CC) [09:33:06:607]: Note: 1: 2203 2: \\NF04\d$\3db7739bf5c1bb9c50076c418420\HotFixSqlSupport\Files\SqlSupport.msp 3: -2147287037
    MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
    MSI (s) (28:CC) [09:33:06:607]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp
    MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Processing net source list.
    MSI (s) (28:CC) [09:33:06:607]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp
    MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Processing media source list.
    MSI (s) (28:CC) [09:33:07:654]: SOURCEMGMT: Resolved source to: 'SqlSupport.msp'
    MSI (s) (28:CC) [09:33:37:732]: Note: 1: 1314 2: SqlSupport.msp
    MSI (s) (28:CC) [09:33:37:732]: Unable to create a temp copy of patch 'SqlSupport.msp'.
    MSI (s) (28:CC) [09:33:37:732]: Searching provided command line patches for patch code {EE92F683-5F5C-4970-BB0B-9AC591B60268}
    MSI (s) (28:CC) [09:33:37:763]: Note: 1: 1708
    MSI (s) (28:CC) [09:33:37:763]: Product: Microsoft SQL Server Setup Support Files (English) -- Installation failed.
    MSI (s) (28:CC) [09:33:37:763]: Windows Installer installed the product. Product Name: Microsoft SQL Server Setup Support Files (English). Product Version: 9.00.4035.00. Product Language: 1033. Installation success or error status: 1635.
    MSI (s) (28:CC) [09:33:37:779]: MainEngineThread is returning 1635
    MSI (s) (28:28) [09:33:37:888]: No System Restore sequence number for this installation.
    This patch package could not be opened.  Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.
    C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
    MSI (s) (28:28) [09:33:37:888]: User policy value 'DisableRollback' is 0
    MSI (s) (28:28) [09:33:37:888]: Machine policy value 'DisableRollback' is 0
    MSI (s) (28:28) [09:33:37:888]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (28:28) [09:33:37:904]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
    MSI (s) (28:28) [09:33:37:919]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (s) (28:28) [09:33:37:919]: Restoring environment variables
    MSI (c) (E0:88) [09:33:37:935]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (E0:88) [09:33:37:935]: MainEngineThread is returning 1635
    === Verbose logging stopped: 3-4-2009  9:33:37 ===

    This post should definitely help you
    http://blogs.msdn.com/sqlserverfaq/archive/2009/01/30/part-1-sql-server-2005-patch-fails-to-install-with-an-error-unable-to-install-windows-installer-msp-file.aspx?CommentPosted=true
    Feroz
    Mark as Answer if it helps. This posting is provided "AS IS" with no warranties and confers no rights.

  • The acount information could not be verified - SQL 2005 SP3 installation on Windows 2008 R2 Failover Cluster

    Hi,
    We have a problem when we are trying to install SQL SP3 on SQL 2005 cluster.
    The problem is described bellow:
    We installed a new Windows 2008 R2 x64 failover cluster with two nodes.
    As a next step we installed SQL 2005 Enterprise edition x64 on this failover cluster. We have finished the installation without problems. After SQL installation we are trying to install SQL SP3 . We have logged on using a domain administrator account and
    we start the installation of SP3 with that user. In authentication mode screen the test gives a success status using either domain administrator-windows authentication or sa-sql authentication. On remote user account screen, when we give the domain
    administrator account we get the message "the account information could not be verified. Press ok to return to authentication mode screen to determine the reason for failure".
    We have tried to give the SQL services startup user on remote user account screen but the error is the same.
    the domain administrator account exists on security logins of SQL with sysadmin rights.
    Can someone help?
    Thanks. 

    Hi StelioMavro,
    According to your error message, when you install SQL Server 2005 SP3 in your failover cluster, we need to verify if there was other instance that had been removed and the installation did not pass the login check. I recommend you use windows authentication
    instead of SQL Server authentication when applying SP3. And the windows account used to run the SP3 setup program must have administrator privileges on the computer where SP3 will be installed.
    For more information about how to install SQL Server 2005 SP3 in failover cluster, you can review the following article.
    http://www.sqlcoffee.com/Tips0007.htm
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • ERP 6 installation Problem on windows clustring

    i am installing SAP ERP 6 EHP4 on windows 2003 with clustering 2 nodes only and DB as MS SQL 2005. i have Domain controller on one node and other is member of it , i want ACTIVE/ACTIVE clustering , so i installed MS SQL on one node and on other node i installed ASCS from SAP High Availability environment, and now i am configuring the first NODE on MSCS step ,here after accepting the password of the two domain user , it gives the problem:-      ****************************         
    Number value 0x-3f580000 is bigger than 0xFFFFFFFF      *******************************
    the last lines of sapinst.log files are like this :-       *******************************
    INFO 2010-08-18 14:13:31.984
    Execute step dAskForKernelDVD of component |MSCS_A|windows|ind|ind|ind|0|0|UserDialogs|windows |ind|ind|ind|2|0
    INFO 2010-08-18 14:14:01.298
    Execute step dAskForSecondKernelDVD of component |MSCS_A|windows|ind|ind|ind|0|0|UserDialogs|windows |ind|ind|ind|2|0
    INFO 2010-08-18 14:14:01.314
    Execute step dAskForuserDomain of component |MSCS_A|windows|ind|ind|ind|0|0|UserDialogs|windows |ind|ind|ind|2|0
    INFO 2010-08-18 14:14:03.126
    Execute step dBuildAccountInformation of component |MSCS_A|windows|ind|ind|ind|0|0|UserDialogs|windows |ind|ind|ind|2|0
    INFO 2010-08-18 14:14:03.142
    Execute step dAskForUserPAsswords of component |MSCS_A|windows|ind|ind|ind|0|0|UserDialogs|windows |ind|ind|ind|2|0
    INFO 2010-08-18 14:14:32.143
    Execute step dCollectMSCSNodesInformations of component |MSCS_A|windows|ind|ind|ind|0|0|CollectClusterParam eters|windows|ind|ind|ind|3|0
    INFO 2010-08-18 14:14:32.174
    Execute step dGetSAPClusterParameters of component |MSCS_A|windows|ind|ind|ind|0|0|CollectClusterParam eters|windows|ind|ind|ind|3|0
    WARNING[E] 2010-08-18 14:14:32.174
    MUT-03028 Number value 0x-3f580000 is bigger than 0xFFFFFFFF.
    ERROR 2010-08-18 14:14:32.268
    FCO-00011 The step dGetSAPClusterParameters with step key |MSCS_A|windows|ind|ind|ind|0|0|CollectClusterParam eters|windows|ind|ind|ind|3|0|dGetSAPClusterParameters was executed with status ERROR .
    INFO 2010-08-18 14:14:44.237
    An error occured and the user decided to retry the current step: "|MSCS_A|windows|ind|ind|ind|0|0|CollectClusterParam eters|windows|ind|ind|ind|3|0|dGetSAPClusterParameters" .
    WARNING[E] 2010-08-18 14:14:44.253
    MUT-03028 Number value 0x-3f580000 is bigger than 0xFFFFFFFF.
    ERROR 2010-08-18 14:14:44.268
    FCO-00011 The step dGetSAPClusterParameters with step key |MSCS_A|windows|ind|ind|ind|0|0|CollectClusterParam eters|windows|ind|ind|ind|3|0|dGetSAPClusterParameters was executed with status ERROR .
    INFO 2010-08-18 14:14:44.878
    An error occured and the user decided to retry the current step: "|MSCS_A|windows|ind|ind|ind|0|0|CollectClusterParam eters|windows|ind|ind|ind|3|0|dGetSAPClusterParameters" .
    WARNING[E] 2010-08-18 14:14:44.893
    MUT-03028 Number value 0x-3f580000 is bigger than 0xFFFFFFFF.                     
    Help Me if you can thank you in advance

    >> i am installing SAP ERP 6 EHP4 on windows 2003 with clustering 2 nodes only and DB as MS SQL 2005. i have Domain controller on one node and other is member of it
    Installations on domain controllers are not supported:
    Installation guide "2.2.4 Requirements for a High-Availability System":
    <...>
    You cannot use a host with a domain controller as an MSCS cluster node.
    <...>
    It's pretty clear why: If the first node, the domain controller, fails, the second node can't authenticate any more and hence the system won't start/run.
    Markus

  • 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 ===

  • Cluster Installation - SQL 2005 / 2003 - Creating cluster group

    Hi All,
    I am working on the cluster Installation in our environment and facing some issues at the time of installing first node MSCS  Installation. let me summarize the activities done so far
    Environment Details
    Physical Disk :
    G: (Physical Disk - SAN )
    I : (Physical Disk - SAN )
    C: Local disk
    Q: (Physical Disk Quorum - SAN )
    F: (Database and logs)
    -- > SCS installed locally in the server in G drive
    Virtual Hostname and IP : SeparateIP & cluster1
    Node 1: Hostname and separate IP
    Node 2 : hostname and Separate IP
    Installed MSCS service and tested the same - its working fine
    Installed SQL 2005 database in cluster mode and its working fine
    Started installing SAP
    Step 1: Installation of SCS instance in node A (Used F drive) - Successfull Installed
    Step 2: Installation of First node MSCS in node A
    Here I am facing an issue, in the end phase of the installation it will ask for creating cluster group -- > There I need to define the Global disk as F (Which is defined at the time of installing SCS instance) - But i dont see that disk is available in the drop down box .
    Is there any other workaround to bring the Global disk while creating the cluster group (First node MSCS installation)
    Looking forward for your suggestions
    Thanks and Regards
    Vijay

    Regret for the late update
    112266 solved my problem and In my case, I have bisected the disk as two but in the cluster environment that should not be the case. Ensure the the same in disk management
    Regards
    Vijay

  • Custom AddOn installation error on Windows Server 2008 64 bits

    Hi All,
    We have developed an AddOn that our client is currently testing on several Windows XP machines.
    My client requested to install it also on a Windows Serer 2008 64bits machine, so we have compiled it (both the AddOn and the Setup Installer) to x64 bits with Visual Studio 2005.
    However when we try to install it on the server and inside the SBO, we get the following error:
       An attempt was made to load a program with an incorrect format (Exception HRESULT 0x8007000B)
    The problem is that both EXE files (addon and installer) are in fact in x64 bit format because we get the standard error when we run with an 32bit machine (xxxx is not a valid Win32 application).
    Does anybody know how to solve this problem?
    Regards
    Manuel Dias

    Hi Manuel,
    This topic did come up in the forum, many a times by now, find the below links to the same.
    [Re: 64 bit windows (Exception from HRESULT: 0x8007000B)|Re: 64 bit windows (Exception from HRESULT: 0x8007000B)]
    [ Re: 64 Bit Programming SAP Add-ons|Re: 64 Bit Programming SAP Add-ons]
    HTH,
    Siju Dasan

Maybe you are looking for

  • How to move selected values in a table in one view to another

    Dear Experts, In my application,I have a table populated with data.My requirement is to select a row in the table and move the selected values of the row to the next view. Can anybody tell how to do this?? Regards, Mamai.

  • New Field Addition in  Allowed Field Catalogs -Pricing.

    *Hi, We have requirement of having Material Description field in the Allowed Field Catalogs in SPRO --> SD --> Basic Functions --> Pricing --> Pricing Controls --> Define Condition tables --> Allowed Field Catalogs in order to fetch the same for Pric

  • Trying to restore adobe acrobat 8 professional for the mac version 8.3.1

    Is there a specific site for this product?  I was directed to the Acrobat XI Pro site, but my serial number will not work for that product.  Any suggestions?

  • Suddenly no sound on Audigy 2

    Until today my computer has been working fine. Suddenly, i get no sound from my Audigy 2 zs (including Windows signature sign on or sign off). I have not installed anything new except the usual Windows updates (automatic). What is really strange is t

  • Safe to upgrade to lion

    I know I have left it late to upgrade to Lion, but I would like to take advantage of some of the lion only apps. My woory is that the apps I currently have will be deleted/damaged/Or I have to pay for the same software just for Lion? These are the ap