Read uncommited against sql 2005?

Hi
Has anybody done a read uncommited against a database?
Is there a setting on the Datastore to do so, or anywhere else?
Or do I have to make my own SQL-Block with SET TRANSACTION ISOLATION LEVEL ....
Thanks in advance
Michael

Hi Michael,
Have you tried the SQLServerReadUncommited job server setting?
Here is the official description of it, hopefully this might help you.  We've used this in a few scenarios and it's proved very useful in preventing locks.  Let me know if it's any use.
Fixed in 11.5.1.0
33348
When a SQL Server table is being updated by a third-party application,
if
Data Integrator tries to read from the table, it hangs until the change
commits. The new SQLServerReadUncommitted configuration parameter
eliminates this scenario and allows reading of uncommitted data from SQL
Server. In addition, Data Integrator issues no share locks when
SQLServerReadUncommitted is activated. This parameter affects all SQL
Server datastores. To set the option, from the Designer select Tools >
Options > Job Server > General and enter the following:
Section: al_engine
Key: SQLServerReadUncommitted
Value:'1'
(Note that if you use the default value of '0', Data Integrator will
only read
committed data.)

Similar Messages

  • ALUI 6.x SQL 2005 SP3

    Is anyone running ALUI 6.x on MS SQL Server 2005 SP3?
    We are being told my Microsoft that we need to apply SP3 to our SQL servers by the end of the year to maintain support.
    Oracle is telling us that ALUI 6.x is not certified on SP3. I would think with Applications Unlimited Oracle would want to certify applications on newer database levels.
    ALUI 6.1 - MS SQL Server 2005
    ALUI 6.1 MP1 - MS SQL Server 2005 SP2
    ALUI 6.5 and 6.5 MP1 - MS SQL Server 2005 SP2
    WCI 10.3.0 - MS SQL Server 2005 SP2 and higher

    Hi Tim,
    To argument what Mike stated....
    Take a look at the interoperability matrix here:
    [http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/BIDExtInteroSupportMatrix3.xls#PortalWksheet|http://download.oracle.com/docs/cd/E13196_01/platform/suppconfigs/BIDExtInteroSupportMatrix3.xls#PortalWksheet]
    This is considered the most up-to-date document on supported configurations against the Web Center Interaction product line.
    You can see here for for WCI 10.3.0.0 the product is certified against SQL 2005 with SP2^. The symbol ^ next to SP2, indicates we support Service pack 2 or higher (ie SP3). Keep in mind with all SQL server 2005 databases we still require them to run in SQL 2000 compatibility level.
    6.5 and 6.5mp1 it is certified against SQL 2005 SP2 (but not SP3).
    6.1 MP1 is certified against SQL 2005 SP2 (but not SP3).
    6.1 is certified against SQL 2005
    6.0.x is not certfied against SQL 2005
    By certified this means that these products have had full test cycles against these versions of the database.
    While support will attempt to assist you with technical issues, if your 6.x alui portal is installed against an uncertfied version of SQL server, and it comes down to the problem being caused by you being on that uncertfied version of db, then you might need to downgrade your database to a certified release. And I would think this would be unlikely, but it's good to be aware of.
    The recommendation would be for you to work towards upgrading your portal from 6.x to 10.3 which is supported against SQL 2005 SP3.
    Hope that clarifies things.
    Regards,
    RyanO
    WCI Support

  • Migrate SQL 2005 to 2008r2 to diferent server running 2008r2

    I need to migrate sql server 2005 to a diferent server running windows server 2008r2 and install SQL 2008r2 can some one help with that step by step please
    UPDATE:: i just realize its sql 2014 not 2008, does it make it easier or more difficult or same or there is any tool that make it easier?
     thanks for all your response and help.

    This is what I follow.
    First Run upgrade advisor 2008 r2 against sql 2005 to confim there are no issues,.
    Check depreceated features , discontinued functionality, breaking changes etc in sql 2008 r2.
    http://msdn.microsoft.com/en-us/library/ms143729(v=sql.105).aspx
    http://msdn.microsoft.com/en-us/library/ms144262(v=sql.105).aspx
    http://msdn.microsoft.com/en-us/library/ms143179(v=sql.105).aspx
    Once this is done, depending upon the criticality of databases I do a performance test on the new server. If doing performance tests then I do all these below steps before hand and do a database refresh during cutover.
    So basically take backup of all databases and move it to the new server.
    Now need to move the logins using this KB article - <cite class="_Rm">support.microsoft.com/kb/918992 </cite>
    Move all jobs/linked servers etc
    Setup all the configuration in sp_configure.
    Update stats of all the databases + Reindexing of all indexes.
    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

  • Reading BLOB from SQL Server 2005 using DB Link from Oracle 10g

    Hi All,
    I am trying to read a table's data from SQL Server 2005 using ODBC DB Link created in Oracle 10g (10.2.0.3/4) database. I am not using oracle gateway.
    I am able read all data except for the BLOB data from SQL server 2005. It gives error given below when I try to execute query SELECT * from T_TRANSACTION_DATA@sdeslink inside a stored procedure:
    ORA-22992: cannot use LOB locators selected from remote tables
    Kindly help how to read BLOB from SQL server 2005 inside Oracle 10g.
    Best Regards!
    Irfan

    Irfan,
    If you can read the blob data using 10.2 HSODBC then there should be no problem using the 11g gateway.
    I recommend you download the latest version which is 11.2.0.3 available from My oracle Support as -
    Patch 10404530: 11.2.0.3.0 PATCH SET FOR ORACLE DATABASE SERVER
    This is a full version and does not need a previous version to have bene installed. When installing it needs to be in a completlely separate ORACLE_HOME from the existing 11.2 install.
    For the Ora-22992 problem have a look at this note in My Oracle Support -
    Ora-22992 has a workaround in 10gR2 (Doc ID 436707.1)
    Regards,
    Mike

  • Reading Large Videos from Varbinary(max) SQL 2005

    We   are storing some somewhat large (15-20MB) videos files in an SQL 2005   table within a varbinary(max) type column.  The video files are used  and  displayed in our CMS web application which is written in  Coldfusion.   Retrieving the videos with a standard SQL select statement  through  Coldfusion is very slow. 
    Does anyone know if there is  a way to  speed up the retrieval of the data through Coldfusion, SQL  Server, T-SQL, or a cfobject call to .NET?
    I appreciate all   suggestions. 
    Thanks ahead of time!

    @tclaremont
    Thanks for the reply.  Ive decided to go the file system route as you were suggesting below.  Seems like the only real answer until we upgrade to SQL 2008, which has the FILESTREAM data type.

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

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

  • SQL 2005 Distributed Transactions from WCF

    Hello,
    I've been redirected here from the Transaction Programming forum becuase I have e peculiar issue with SQL 2005 running INSERT stored procs from multiple WCF services all withing a TransactionScope.
    The original post is http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2720665&SiteID=1&mode=1
    The story goes, I have SRVC A with starts a TransactionScope which in turn calls SRVC B & C in sequence based on processing rules.
    SRVC A is a Sequential Workflow which Starts and Completes the TransactionScope
    SRVC B Creates a new Customer into the database
    SRVC C Creates new Accounts for that Customer and Initialises the accounts with funds
    The DB Tables underneath are Customer, Account and AccountLog
    DDL
    Code Block
    CREATE TABLE [Member].[Customers](
    [CustomerId] [int]
    IDENTITY(1,1) NOT NULL,
    [Name] [varchar](32) NOT NULL,
    [CreatedUtc] [datetime] NOT NULL ,
    CONSTRAINT [PK_Customer] PRIMARY KEY CLUSTERED
    [CustomerId]
    ASC
    CREATE TABLE [Bank].[Accounts](
    [AccountId] [int]
    IDENTITY(1,1) NOT NULL,
    [CustomerId] [int] NOT NULL,
    [CurrentBalance] [money] NOT NULL,
    [LastUpdateDate] [datetime] NULL,
    [CreatedDate] [datetime] NOT NULL,
    [timestamp] [timestamp] NOT NULL,
    CONSTRAINT [PK_Bank_Account] PRIMARY KEY CLUSTERED
    [AccountId]
    ASC
    ) ON [PRIMARY]
    GO
    ALTER TABLE [Bank].[Accounts] WITH CHECK ADD CONSTRAINT [FK_Account_Customer] FOREIGN KEY([CustomerId])
    REFERENCES [Member].[Customers] ([CustomerId])
    CREATE TABLE [Bank].[AccountLog](
    [AccountLogId] [int]
    IDENTITY(1,1) NOT NULL,
    [AccountId] [int] NOT NULL,
    [Amount] [money] NOT NULL,
    [UtcDate] [datetime] NOT NULL,
    CONSTRAINT [PK_Bank_AccountLog] PRIMARY KEY CLUSTERED
    [AccountLogId]
    ASC
    ) ON [PRIMARY]
    GO
    ALTER TABLE [Bank].[AccountLog] WITH CHECK ADD CONSTRAINT [FK_AccountLog_Account] FOREIGN KEY([AccountId])
    REFERENCES [Bank].[Accounts] ([AccountId])
    NB. I've removed most fields not essential for this example.
    So from SRVC A I invoke SRVC B and the Customer is created, however when I get to SRVC C and the accounts are to be created I get a lock.  Only when the Transaction aborts due to timeout, do I see in SQL Profiler that the call to the SP that created the Account is executed but eventually rolls back as it is part of the distributed transaction.
    Now, If I set the Isolation level in the TransactionScope to ReadUncommitted (urgh) the problem remains.  When I set the IsolationLevel to Read Uncommitted in the SP that creates the account the problem remains but when I remove the FK constraint the problem disappers.  The other curious thing is that with the Customer -> Account FK removed and when SRVC C calls to insert funds into the AccountLog which also updates an aggregated total in the Account from within the same transaction scope and with Account -> AccountLog FK constraints in place there is no locking even with Isolation Serializable.
    I'm quite at a loss as to what could be causing these issues.  If anyone has any suggestions I would greatly appreciate any help.
    Thanks
    Andy
     

    Andy,
    Is this still an issue?
    Thanks!
    Ed Price, Power BI & SQL Server Customer Program Manager (Blog,
    Small Basic,
    Wiki Ninjas,
    Wiki)
    Answer an interesting question?
    Create a wiki article about it!

  • Upgrade Process from SQL 2005 to SQL 2012

    Hi All,
    I have gone thru multiple threads and would like to understand some steps in detail for me to upgrade SQL 2005 to SQL 2012.
    Below is my understanding and questions around it, I would be setting up a new environment with OS 2007/2008 with SQL 2012:
    Environment Readiness - Ensure new environment is ready with Win 2007/2008 with SQL 2012 Server
    Run Upgrade Advisor on the new environment and point to SQL 2005 instance
    Find the breaking/discontinued changes to be done before or After Upgrade
    <Question>: Over here I would like to know what should be our approach to make the required changes
    <Question>: Obviously I should not be making changes directly on the Production SQL 2005 server, then in that case should I take a backup/restore on the new SQL Server 2012 and then make the required changes to the database objects
    like (Table schema(changing column names/datatypes etc.), Stored Procedure, Functions & Views)
    <Question>: When I do a backup/restore I would also get the data along with it, so is this a recommended approach or should we only run/use the table schema creation scripts, fix the issues identified by UA and then do an Table to Table import,
    any thoughts on this ?
    <Question>: If I have to do a table to table Import then I should ensure there's a downtime during the Import or would I have any other better approach          
    So, basically my questions are around the approach of fixing the issues identified by UA and moving the database to SQL Server 2012 environment, I have around 300 databased to me upgraded.
    Please do let me know what should be a good/proven approach ? Pl. do let me know if you would need any more details from me.
    ---Umesh

    Thanks all for the replies.
    I am trying summarize what I have understood here:
    Document SQL Server 2005 environment details, Is there any tool which could give us all relevant details
    I would take the backup from the SQL Server 2005 Production environment and then restore the same in a test environment which again has SQL Server 2005 and Run Upgrade Advisor on that
    Probbaly run SQL Profiler as well to find out the deprecated changes to be done
    I should fix all the breaking, discontinued changes on the Test system identified by UA
    I should fix all the deprecated changes on the Test system identified by SQL Profiler
    Steps 3 & 4 should give me the changed scripts for all database objects (i.e. Table Schema, Stored Procedures, Functions & Views)
    <Question> Perform test, I understand this acitivity test can be captured by having SQL profiler running in the background on the SQL Server 2005 production environment where we can identify some days in a week or a month where maximum activity is
    expected to ensure we cover most the scenarios, let me know is this approach looks fine or is there a better approach
    Now, with regards to acutal upgrade I need to identify a time window where in less activity is done during which I could have a downtime for the actual SQL Server 2005 production environment
    Post downtine, I should do a BackUp for all databases from SQL Server 2005 production environment
    Test on environment readiness of SQL Server 2012 can be compared against the documentation done as part of the first Step
    <Question> Ideally I should a restore first in the new environment which has SQL Server 2012
    <Question> Then run the Scripted changes where we fixed all the breaking, discontinued & deprecated changes
    <Question> Does above sequence of Step 9 & 10 make sense or is there a better approach of doing it
    <Question> Post Upgrade and running of changed scripts, I should run the Upgrade Advisor again and see if everything looks fine
    <Question> Perform test again which we ran on SQL Server 2005 Test environment
    <Question> These steps should complete the Upgrade process.
    Please do let me know if the above sequence look ok to all of you and does it really work in a practical scenario, do let me know your feedback or any change in sequence/process or any other tools that can be used here.
    Thanks Again ...

  • Gathering physical memory for SQL 2005..SQL 2014

    Hi All,
    I'm trying to write a query to gather physical memory across my SQL servers (from SQL 2005 to SQL 2012).
    However, the sys.dm_os_sys_info DMV (the column for physical memory) is not the same after the switch to SQL 2012+.
    Here is the original query:
    SELECT
    @@SERVERNAME AS ServerName,
    CASE WHEN LEFT(CAST(serverproperty('productversion') as char), 1) = 9 THEN '2005'
    WHEN LEFT(CAST(serverproperty('productversion') as char), 4) = 10.0 THEN '2008'
    WHEN LEFT(CAST(serverproperty('productversion') as char), 4) = 10.5 THEN '2008R2'
    WHEN LEFT(CAST(serverproperty('productversion') as char), 2) = 11 THEN '2012'
    END AS MajorVersion,
    SERVERPROPERTY ('productlevel') AS MinorVersion,
    SERVERPROPERTY('productversion') AS FullVersion,
    SERVERPROPERTY ('edition') AS Edition,
    SERVERPROPERTY('collation') as Collation,
    cpu_count as CpuCount,
    physical_memory_in_bytes/1024/1024 as PhysMemMB
    FROM [sys].[dm_os_sys_info]
    If I run that on SQL 2014, it fails because 'physical_memory_in_bytes' is now called 'physical_memory_kb'
    I tried to do an IF..THEN..ELSE:
    IF (cast(serverproperty('productversion') as char) like '11.%')
    Then change the query accordingly but it would fail because i guess when it tried to parse the whole code, one of the T-SQL variations would have a column that did not exist in that particular version of SQL Server.
    Is there a way I can get physical memory across SQL 2005..SQL 2012 or rewrite the T-SQL above to be able to run on both?
    Thanks in advance

    Oh it seemed like you are asking SQL Server memory. the name for physical memory column ha changed only in SQL Server 2012. I wrote below script  just first run select SERVERPROPERTY('ResourceVersion')  to get exact resource database version of
    SQL Server 2012 and then replace it in below script
    IF cast ( SERVERPROPERTY('ResourceVersion') as char (10) )= '11.00.2000'--2012 resource database version
    select (physical_memory_kb/1024)as Physical_mem_MB from sys.dm_os_sys_info
    else
    select (physical_memory_in_bytes/1024/1024) as physical_mem_MB from sys.dm_os_sys_info
    Edit: A more optimized query
    If cast (LEFT( CAST(SERVERPROPERTY('ResourceVersion') AS VARCHAR(20)),2) as INT) in ('11','12')
    select (physical_memory_KB/1024) as Physical_Mem_MB from sys.dm_os_sys_info
    --else it uses for 2005-08R2
    else select (physical_memory_in_bytes/1024/1024) as Physical_Mem_MB from sys.dm_os_sys_info
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Articles
    Hi Shanky,
    Doesn't work and that's what I meant in my initial post..when I run that code against a SQL 2012 instance, it parses fine but when I execute it I get:
    Msg 207, Level 16, State 1, Line 6
    Invalid column name 'physical_memory_in_bytes'.

  • Updaing SQL 2005 Report Builder Reports (based on Report Models) to SQL 2012 Report Builder Reports?

    We are upgrading from SQL 2005 to SQL 2012 directly (no SQL 2008 to be installed).  We have many SSRS Reports written in Report Builder 1.0 against Report Models generated from an OLAP datasource.  In SQL 2012, Report Models can no longer
    be created or edited.  I have found many posts on this topic, including this: 
    http://social.msdn.microsoft.com/Forums/en-US/896522da-45c3-46c0-848a-16f8f02ab051/how-to-upgrade-report-models-from-report-builder-1020-to-30. which the 'answered' response states: 
    SQL Server 2012 Reporting Services does not include tools for creating or updating report models. Although you can continue
    to use existing report models as data sources in SQL Server 2012 Reporting Services reports you should consider updating your reports to remove their dependency on report models.
    But I cannot locate any instructions/documentation, etc. on how to go about "updating your reports to remove
    their dependency on report models.".  How do I take existing Report Builder 1.0 reports that point to Report Models and upgrade them to the new SQL 2012 without Report Models?  Is there a way to convert them?  Or, do they need to be rewritten
    from scratch?  If there is a link to these instructions, please post as I cannot locate it any where.  Thank you.

    Katherine thank you for helping with this.  Here is what I have tried:
    On the Report Manager (2012) site, I created a new OLAP data source.  And when I test the connection, I get the pop up "Connection created successfully."
    I then pointed my Report Builder (v1.0) report to this new Data Source (from Report Manager site, selected 'Manage' for the report, from Data Sources, selected Browse and drilled down to the new Data Source I created and selected Apply). 
    Now when I try to View the report, I receive the following error:
    An error has occurred during report processing. (rsProcessingAborted) Query execution failed for dataset 'paramDataSet'. (rsErrorExecutingCommand) The SemanticQuery element at line 7, column 279 (namespace http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling)
    cannot appear under Envelope/Body/Execute/Command.
    I then exited IE and reopened the Report Manager site.  I opened Report Builder 3.0,, selected Open and opened this same report.  Idrilled donw to Data Sources and  right clicked on dataSource1 (the only one listed) and selected Data
    Source Properties.  I kept the same name, but selected the new shared datasource I created (New DataSource), and selected OK.
    Next, I drilled down to Datasets.  There are two listed, dataSet and paramDataSet (yes, this report has parameters).  I right clicked on the dataSet and selected dataSet properties, and see that it points to dataSource1 (which is the dataSource
    I just pointed to my New DataSource).  I cancelled and checked the Data Source for paramDataSet, and it also points to dataSource1.  Selected cancel and went back to the main dataSet.
    So both datasets point to the new DataSource I created.
    If I select Run, I get the following error: 
    I select OK and right click on dataSet and select Refresh Fields and get this error:
    Can you (anyone) please explain what I am doing incorrectly?  Thank you.

  • Cant get CFADmin to verify datasource w/ SQL 2005

    OK I've been beating my head against the wall for a week
    trying to figure out why could fusion wont recoginze my datasource.
    I'm running vista, sql 2005 express and cf 8 devleopers
    edition.
    Heres the error:
    * Connection verification failed for data source: TestDB
    An exception occurred when executing method verifydatasource.
    The cause of this exception was that:
    coldfusion.sql.Executive$ConnectionVerificationFailedException:
    java.sql.SQLException: [Macromedia][SQLServer JDBC
    Driver][Macromedia][SQLServer JDBC Driver]The requested instance is
    either invalid or not running..
    SQLCritUpdPkg_ENU
    What does this mean?...
    Here's what I tried so far to resolve this:
    1. enabled tcp/ip in sql config manager, verfied that it's
    using port 1433 in IPALL
    2. telnet 127.0.0.1 1433 - that works ok
    3. dowloaded SQLCritUpdPkg_ENU.exe and installed it - I read
    on a fourm somewhere that this disabled some ports due to a worm..
    but i dont think that was the problem anyway since i ping'd 1433
    and it was ok
    4. And yes I've logged in directly to SQL server using the
    u/p..
    and I've changed the security settings in SQL to use both sql
    server and windows authenticaion
    Any help from anyone would be awesome..
    PS: I've also gotten this same error when I had CFMX 7
    installed...

    Interesting.  I was extremely clear.  Short & concise w/ minimal irritation as compared to how I feel. 
    My subject tells what's going on.  The commentary states how I got there. Pretty straight forward.
    Maybe if you do not understand the question, you shouldn't reply?

  • Browse Data & Parameter flds no longer fully populated after upgd  SQL 2005

    I upgrade our SQL 2000 Server last weekend to SQL 2005 (sp2).
    Now our Crystal reports that access SQL data are not working correctly. Parameter Fields are showing little to no data, where before the upgrade we were seeing many more rows in the list.
    Digging further, I looked at the fields used for the dynamic LOV. If I use Browse Data on those fields I am seeing the same lack of data. One "Browse Data" that would typically return 80 items now returns 3 items. In that report the data field is DateTime. In another report, the field is string.
    I am also seeing an extra check for User Name and password before getting to the Enter values screen for the parameter.
    I am using Crystal Developer 11.0.0.1994. It is happening on multiple PCs. I tried with both the original SQL ODBC Driver and the newer SQL Native Client ODBC driver, with the same result.
    I've looked at this for 3 days with no luck. Any ideas?

    Full SysAdmin rights.
    I use a dedicated ODBC connection and have tried both "SQL Server" odbc driver and "SQL NativeClient" (2005) odbc driver.
    If I go to Crystal, to the Field Explorer, to the one of the fields, right-click and "Browse Data..." I get two results (I expect 82 results and have seen that in the past.) If I paste the query from Crystal, Database, "Show SQL Query.."  to SQL Server Management Studio, I see the full, correct results.
    In one example the field browsed is called "PeriodEndDate" (DateTime). A dynamic Parameter Field was created accessing this field. Here is the security curiosity...refreshing now asks for the user login each time "Prompt for new parameter values" is selected. It used to ask only the first time. The Crystal: Data Explorer" shows the current connection logged in ok.
    The two issues may or may not be related. Certainly if #1 were fixed, dynamic parameters would return the correct results. Even if it asked for the password each time.
    1.) "Browse Data" returning a smaller result than normal.
    2.) "Parameter Prompt" asks for Server Name, Database Name, User Name, and Password on
         each refresh selecting "Prompt for new parameter values".

  • Dsml and SQL 2005 reporting services?

    I usually post over in the IDM forum so be nice to the newbie here :)
    I have a Sun Directory server that I've enabled DSML on. On that side everything is good. However, ideally I want to pull this data into a MS SQL 2005 reporting services report. They have support for XML and web services, but the DSML front end doesn't accept GET requests and I don't know how to send the request as post in reporting services.
    Has anyone else be able to get something like this working?
    Thanks!

    No idea about MS SQL, but is your reporting service able to use files on disk? If so I guess your problem is easily solved by using an app to fetch data from directory server to disk. If you're more adventerous, you write a script in perl/python which acts as a proxy and translates GET requests to POST and relays data back in real time. Not sure if these help or not, just my thoughts.

  • SAP IDES ECC5.0 (SQL 2005 Database) installation Error at  Database instan.

    At the time IDES ECC 5.0 installation (SQL 2005 database), I was copy all DVD on Hard drive and start setup then at installation of database instance, following Errors are occured. so I cant continue with the installation, if anyone have installation guide/or solve the following error please mail me at [email protected]
    from Log file SAPCLUST
    Interface access functions from dynamic library dbmssslib.dll loaded.myCluster
    (3.5.Imp): 613: error when retrieving table description for physical table AABLG.
    myCluster (3.5.Imp): 614: return code received from nametab is 32
    myCluster (3.5.Imp): 296: error when retrieving physical nametab for table AABLG.
    (CNV) ERROR: code page conversion failed
                 rc = 2
    from sappool.log
    Interface access functions from dynamic library dbmssslib.dll loaded.failed to read short nametab of table ARCH_NUM     (rc=32)conversion failed for row 0 of table  VARKEY = &#8280;††††††††††††††††††††††††
    (CNV) ERROR: code page conversion failed
    So please send me solution/ or any configuration need for SQL 2005 / installation guide thanks

    This may be hard disk problem, some file not able to write on HDD.
    Regards
    Rajnish

Maybe you are looking for

  • Is there a way to edit songs in itunes?

    I am working on creating a dvd and am making slideshows of pictures from iphoto. I only want to use a portion of a song I have in itunes. Is there a way to edit the music? If so, how? Thanks

  • 720p60 3:2 Pulldown to 720p24 in Final Cut?

    We shot a feature film with a Panasonic Varicam at 24p and captured directly to a computer via HD-SDI through a BlackMagic Design Decklink HD Extreme using Apple's ProRes codec (looks fantastic by the way... for those interested there is definitely a

  • Facebook and Twitter resolution problems in iOS 7.0.3

    Yesterday i updated my iOS to 7.0.3, since the update both my Twitter and Facebook apps have shrunk to the middle of the screen with all the text overlapping. i have rebooted iPhone several times and reinstalled both apps and still the problem is the

  • Changing a Once Blank Password

    I set my password to blank and now when I try to change it, it asks me to put in a password for my old password in the users section. What do I do? PS. I don't recommend a blank password because it can screw up your computer when you first turn it on

  • In After Effects CC, images added to listboxes fail to appear at first

    Given a simple listbox with images, created like so: function buildUI(this_obj_) { var winDef = (this_obj_ instanceof Panel) ? this_obj_ : new Window('palette', 'testing listbox',[194,174,644,406]); winDef.ctl_list1 = winDef.add('listbox', [10,20+10+