I am attempting to install the first of the cumulative hotfix packages ( SQL2005-KB918222-x64-ENU.exe) after applying Service Pack 1 to a SQL Server 2005 std edn 64-bit installation. The service pack installed no problem but the hot fix fails with the following errors in the log file below.
I have installed the 32-bit versions of the hotfix packages onto a different server and I did not get these errors.
Any help on how to sort this out would be much appreciated!
08/23/2006 15:03:44.592 ================================================================================
08/23/2006 15:03:44.608 Hotfix package launched
08/23/2006 15:03:45.842 Product discovery successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.858 SP Level check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.889 Product language check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.905 Product version check successfully completed during the install process for MSSQLSERVER
08/23/2006 15:03:45.920 Command-line instance name check completed during the install process
08/23/2006 15:03:45.936 Baseline build check completed during the install process
08/23/2006 15:03:52.107 Attempting to install instance: MSSQLSERVER
08/23/2006 15:03:52.154 Attempting to install target: SRVLEBIZTALK
08/23/2006 15:03:52.170 Attempting to check for locked files: sqlrun_sql.msp
08/23/2006 15:03:52.232 Attempting to check for locked files: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp
08/23/2006 15:03:52.248 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB918222_sqlrun_sql.msp.out
08/23/2006 15:04:02.107 MSP returned 1602: The user cancels installation.
08/23/2006 15:04:02.310 Successfully checked file: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp
08/23/2006 15:04:02.326 Successfully opened registry key: SystemCurrentControlSetControlSession Manager
08/23/2006 15:04:02.357 Failed to read registry key: PendingFileRenameOperations
08/23/2006 15:04:02.373 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll
08/23/2006 15:04:02.388 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll
08/23/2006 15:04:02.435 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll
08/23/2006 15:04:02.451 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
ls400.dll.
-----------------------
It carries on with errors like the above but my post will be massive if I include it all, so below is the last few lines of the log file.
--------------------------
08/23/2006 15:04:07.591 Failed to read associated hotfix build information for the following file: C:Program Files (x86)Microsoft SQL Server90SharedMicrosoft.SqlSac.Public.dll
08/23/2006 15:04:07.653 Attempting to install file: sqlrun_sql.msp
08/23/2006 15:04:07.700 Attempting to install file: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp
08/23/2006 15:04:07.716 Creating MSP install log file at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB918222_sqlrun_sql.msp.log
08/23/2006 15:04:07.732 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
08/23/2006 15:04:07.747 Failed to read registry key: Debug
08/23/2006 15:05:11.197 MSP returned 1603: A fatal error occurred during installation.
08/23/2006 15:05:11.212 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
08/23/2006 15:05:11.244 Failed to read registry key: Debug
08/23/2006 15:05:11.259 Unable to install MSP file: \SRVLEBIZTALKd$dd32a156dacc8dbe70a862647d70hotfixsqlFilessqlrun_sql.msp
08/23/2006 15:05:11.275 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/23/2006 15:05:11.275 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 856
08/23/2006 15:05:11.322
08/23/2006 15:05:11.353 Product Status Summary:
08/23/2006 15:05:11.369 Product: SQL Server Database Services 2005 (64-bit)
08/23/2006 15:05:11.384 MSSQLSERVER - Failure
08/23/2006 15:05:11.415 Details: Unable to install Windows Installer MSP file
I believe that I mistakenly attempted to apply the Analysis Services component of this update before applying the SQL Server component. The update now fails continuously with the following message:
02/05/2007 17:58:24.990 ================================================================================ 02/05/2007 17:58:25.021 Hotfix package launched 02/05/2007 17:58:27.615 Product discovery successfully completed during the install process for MSSQLSERVER 02/05/2007 17:58:27.630 SP Level check successfully completed during the install process for MSSQLSERVER 02/05/2007 17:58:27.646 Product language check successfully completed during the install process for MSSQLSERVER 02/05/2007 17:58:27.661 Product version check successfully completed during the install process for MSSQLSERVER 02/05/2007 17:58:27.677 Command-line instance name check completed during the install process 02/05/2007 17:58:27.693 Baseline build check completed during the install process 02/05/2007 17:58:34.864 Attempting to install instance: MSSQLSERVER 02/05/2007 17:58:34.974 Attempting to install target: CHARLIDEVSRV 02/05/2007 17:58:35.005 Attempting to check for locked files: sqlrun_sql.msp 02/05/2007 17:58:35.052 Attempting to check for locked files: \CHARLIDEVSRVf$44923e05996203228c1608bea1hotfixsqlFilessqlrun_sql.msp 02/05/2007 17:58:35.067 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB918222_sqlrun_sql.msp.out 02/05/2007 18:01:52.978 MSP returned 1635: This patch package could not be opened. Verify that the patch package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer patch package. 02/05/2007 18:01:53.009 Unable to check MSP file: \CHARLIDEVSRVf$44923e05996203228c1608bea1hotfixsqlFilessqlrun_sql.msp 02/05/2007 18:01:53.025 The following exception occurred: Unable to install Windows Installer MSP file Date: 02/05/2007 18:01:53.025 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 689 02/05/2007 18:01:53.212 Failed to install instance: MSSQLSERVER 02/05/2007 18:01:53.259 02/05/2007 18:01:53.259 Product Status Summary: 02/05/2007 18:01:53.290 Product: SQL Server Database Services 2005 02/05/2007 18:01:53.306 MSSQLSERVER - Failure 02/05/2007 18:01:53.321
The update fails although I have cleaned the registry of any reference to it. Another article indicated that the hotfix may delete registry keys required, for instance, to operated SSIS if applied in the wrong order. Here, it appears to be preventing the hotfix from being reapplied. I have ensured that all necessary permissions are available and the services are running in domain user accounts with the necessary rights. I'm the administrator on the machine.
Is there a way to get this hotfix applied without having to completely rip and rebuild my server instance?
I do experiment a problem when trying to install the mentionned patch on my Windows XP SP2 machine (fully patched).
Interestingly, the patch works fine for the named instance, which is a "clean" install of SQL Server 2005 SP1, while it fails on the default instance, which is a SQL 2005 SP1 upgraded in place from SQL Server 2000 SP4. Both instances are Developer editions...
The error is along the following lines:
[snip]
08/10/2006 09:22:06.728 Unable to install MSP file: \DHDHY0Jc$1c7c01591e524f9a092159a233hotfixsqlFilessqlrun_sql.msp 08/10/2006 09:22:06.818 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/10/2006 09:22:06.818 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 856 08/10/2006 09:22:06.948 08/10/2006 09:22:06.998 Product Status Summary: 08/10/2006 09:22:07.048 Product: SQL Server Database Services 2005 08/10/2006 09:22:07.088 MSSQLSERVER - Failure 08/10/2006 09:22:07.138 Details: Unable to install Windows Installer MSP file 08/10/2006 09:22:07.228 SQL2K5 - Not Selected 08/10/2006 09:22:07.338 08/10/2006 09:22:42.409 Hotfix package closed
I am trying to install sql2005-kb918222-x86-enu.exe, first one in the x86 family. I am getting "This machine does not have a product that matches this installation package".
I have SP1 is installed. Version and patch level are 9.1.2047. on
We are trying to Install the Hot fix KB936305 on our SQL 2005 SP2 on Win2k3 machine. We are able to install the hotfix in our test environment but its failing in our PILOT environment. Below is the log for the installation. Any clues on why this happens??
=== Verbose logging started: 4/17/2008 4:46:37 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: o:94d5ea5728f26407a1d7f52282hotfix.exe === MSI (c) (94:C0) [04:46:37:781]: Resetting cached policy values MSI (c) (94:C0) [04:46:37:781]: Machine policy value 'Debug' is 0 MSI (c) (94:C0) [04:46:37:781]: ******* RunEngine: ******* Product: {EB76B218-8FC5-41DF-9F1F-7FF3E0448383} ******* Action: ******* CommandLine: ********** MSI (c) (94:C0) [04:46:37:781]: Client-side and UI is none or basic: Running entire install on the server. MSI (c) (94:C0) [04:46:37:781]: Grabbed execution mutex. MSI (c) (94:C0) [04:46:37:875]: Cloaking enabled. MSI (c) (94:C0) [04:46:37:875]: Attempting to enable all disabled priveleges before calling Install on Server MSI (c) (94:C0) [04:46:37:890]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (s) (C8:90) [04:46:37:937]: Grabbed execution mutex. MSI (s) (C8:34) [04:46:37:937]: Resetting cached policy values MSI (s) (C8:34) [04:46:37:937]: Machine policy value 'Debug' is 0 MSI (s) (C8:34) [04:46:37:937]: ******* RunEngine: ******* Product: {EB76B218-8FC5-41DF-9F1F-7FF3E0448383} ******* Action: ******* CommandLine: ********** MSI (s) (C8:34) [04:46:37:937]: Machine policy value 'DisableUserInstalls' is 0 MSI (s) (C8:34) [04:46:37:937]: Adding MSIINSTANCEGUID to command line. MSI (s) (C8:34) [04:46:37:953]: End dialog not enabled MSI (s) (C8:34) [04:46:37:953]: Original package ==> C:WINDOWSInstaller82f71.msi MSI (s) (C8:34) [04:46:37:953]: Package we're running from ==> C:WINDOWSInstaller82f71.msi MSI (s) (C8:34) [04:46:38:062]: APPCOMPAT: looking for appcompat database entry with ProductCode '{EB76B218-8FC5-41DF-9F1F-7FF3E0448383}'. MSI (s) (C8:34) [04:46:38:062]: APPCOMPAT: no matching ProductCode found in database. MSI (s) (C8:34) [04:46:38:062]: Detected that this product uses a multiple instance transform. MSI (s) (C8:34) [04:46:38:078]: MSCOREE not loaded loading copy from system32 MSI (s) (C8:34) [04:46:38:078]: Applying multiple instance transform 'qlRun01.mst'... MSI (s) (C8:34) [04:46:38:078]: Looking for storage transform: SqlRun01.mst MSI (s) (C8:34) [04:46:38:078]: Validating transform 'SqlRun01.mst' with validation bits 0x809 MSI (s) (C8:34) [04:46:38:078]: Transform 'SqlRun01.mst' is valid. MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2205 2: 3: Patch MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2205 2: 3: PatchPackage MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _Tables 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _Columns 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Media 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: File 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: TRANSFORM: 'PatchPackage' table is missing or empty. No pre-transform fixup necessary. MSI (s) (C8:34) [04:46:38:078]: TRANSFORM: Applying regular transform to database. MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _Tables 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _Columns 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _Validation 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: File 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: MsiFileHash 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Signature 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: RegLocator 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: AppSearch 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: CompLocator 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: DrLocator 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Binary 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: CustomAction 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Directory 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Registry 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Condition 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: CreateFolder 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _sqlObjectSecurity 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Icon 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: InstallUISequence 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: AdminExecuteSequence 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: AdminUISequence 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: AdvtExecuteSequence 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: AdvtUISequence 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _sqlAction 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _sqlActionsModule 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: _sqlDriveType 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: ReserveCost 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: TypeLib 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Feature 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: MsiAssembly 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Class 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: Extension 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: PublishComponent 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: ServiceControl 3: -2147287038 MSI (s) (C8:34) [04:46:38:078]: Note: 1: 2262 2: ModuleDependency 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ModuleSignature 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ModuleExclusion 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ModuleComponents 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlBuiltInAccounts 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: MsiAssemblyName 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ServiceInstall 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlNativeImage 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlPropertyValues 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlUserSecurity 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlRegistry 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlServiceControl 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlHiveCopy 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlRegSecurity 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlGroup 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlGroupMember 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlConfig 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlUpgradeScript 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlHotfixScript 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlScript 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ActionText 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlSku 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlStart 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlServiceAccount 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlDelimitProperty 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlEquivalent 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlWizardSequence 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: Dialog 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlMofcomp 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlWMISecurity 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlInstanceProperty 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlInstanceComponents 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlAssembly 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlPerfCounters 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlCollation 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlExecutable 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlFileSR 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlUnmanagedComponent 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlUpgradeComponent 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlProducts 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlTopLevelFeatureProducts 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlFileRename 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlFollowComponents 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlLocalServers 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlVerIndependentProgID 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlServiceState 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlServiceProperty 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlServiceConfig 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlSupportFiles 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlDomainGroup 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: FeatureComponents 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: Control 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ControlEvent 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ControlCondition 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ListBox 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ListView 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: ComboBox 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: CheckBox 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: EventMapping 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: RadioButton 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: Upgrade 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: TextStyle 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: UIText 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: Media 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: Shortcut 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: SxsMsmGenComponents 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: MsiSFCBypass 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: RemoveFile 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: RemoveRegistry 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: Environment 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlUpgradeFile 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlUpgradeRegistry 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _sqlUpgradeFolders 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2262 2: _MsiPatchTransformView 3: -2147287038 MSI (s) (C8:34) [04:46:38:094]: Couldn't find local patch ''. Looking for it at its source. MSI (s) (C8:34) [04:46:38:094]: Resolving Patch source. MSI (s) (C8:34) [04:46:38:094]: User policy value 'SearchOrder' is 'nmu' MSI (s) (C8:34) [04:46:38:094]: User policy value 'DisableMedia' is 0 MSI (s) (C8:34) [04:46:38:094]: Machine policy value 'AllowLockdownMedia' is 0 MSI (s) (C8:34) [04:46:38:094]: SOURCEMGMT: Media enabled only if package is safe. MSI (s) (C8:34) [04:46:38:094]: SOURCEMGMT: Looking for sourcelist for product {4A35EF4A-D868-4B15-A84D-3E8925AA9558} MSI (s) (C8:34) [04:46:38:094]: Note: 1: 1706 2: {4A35EF4A-D868-4B15-A84D-3E8925AA9558} 3: MSI (s) (C8:34) [04:46:38:094]: SOURCEMGMT: Failed to resolve source MSI (s) (C8:34) [04:46:38:094]: Note: 1: 1708 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2729 MSI (s) (C8:34) [04:46:38:094]: Note: 1: 2729 MSI (s) (C8:34) [04:46:38:094]: Product: Microsoft SQL Server 2005 -- Installation failed.
MSI (s) (C8:34) [04:46:38:140]: MainEngineThread is returning 1612 The installation source for this product is not available. Verify that the source exists and that you can access it. C:WINDOWSInstaller82f71.msi MSI (c) (94:C0) [04:46:38:140]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (94:C0) [04:46:38:140]: MainEngineThread is returning 1612 === Verbose logging stopped: 4/17/2008 4:46:38 ===
I am trying to install sql2005-kb918222-x86-enu.exe, first one in the x86 family. I am getting "This machine does not have a product that matches this installation package".
I have SP1 is installed. Version and patch level are 9.1.2047. on
The Kb article says to install all component patches, even if you are not running them, to avoid errors...the reporting services hotfix would not install(obviously since reporting svcs is not installed).....now I get the following erro, when trying to connect to the SSIS on my sql server...oh, I am trying to connect locally on the server it self too....
Cannot connect to CRP-DAY1-SQLs1.
===================================
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------ Program Location:
at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server) at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
===================================
Connect to SSIS Service on machine "CRP-DAY1-SQLs1" failed: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. .
------------------------------ Program Location:
at Microsoft.SqlServer.Dts.Runtime.Application.GetServerInfo(String server, String& serverVersion) at Microsoft.SqlServer.Dts.SmoEnum.DTSEnum.GetData(EnumResult erParent) at Microsoft.SqlServer.Management.Smo.Environment.GetData() at Microsoft.SqlServer.Management.Smo.Environment.GetData(Request req, Object ci) at Microsoft.SqlServer.Management.Smo.Enumerator.GetData(Object connectionInfo, Request request) at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request)
===================================
Connect to SSIS Service on machine "CRP-DAY1-SQLs1" failed: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. .
------------------------------ Program Location:
at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.GetServerInfo(String bstrMachineName, String& serverVersion) at Microsoft.SqlServer.Dts.Runtime.Application.GetServerInfo(String server, String& serverVersion)
I've read about this hotfix at http://www.kbalertz.com/Feedback_933097.aspx but I can't find anything on microsoft.com about it. It sounds like a worthwhile hotfix, but I'm wondering about the absence of an announcement on microsoft.com.
I get an error when trying to install the SQL Native Client. It says it cannot find the installation package and to use a valid copy of 'sqlncli.msi'. I've downloaded the Express setup twice and get the same error from both of them.
I'm attempting this in a VMWare session setup for Windows 2K, Advanced Server. I am trying to test my installation and setup procedures. This is not a production setup, just install testing and documentation. I have allocated only 272MB to the VMWare session, which is why the system doesn't meet the recommended settings.
Any help would be greatly appreciated.
Below is the Summary.txt output file.
Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows 2000 Advanced Server Service Pack 4 (Build 2195)
Time : Wed May 03 09:54:23 2006
CPCWIN2KVM1 : The current system does not meet recommended hardware requirements for this SQL Server release. For detailed hardware requirements, see the readme file or SQL Server Books Online.
Machine : CPCWIN2KVM1
Product : Microsoft SQL Server Setup Support Files (English)
Error : An installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'.
Error String : An installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'.
We just upgraded 2 sql servers from sql server 2000 sp3a to sql server 2005 build 2153, and merge rep exists between these 2 servers.
However, after sql server upgrade, we had to reinitialize merge replication and now the merge agent is reporting 2 errors
1)
Error messages:
The Merge Agent failed to upgrade triggers, metadata and stored procedures on the Subscriber to versions compatible with SQL Server 2005. Restart synchronization, and if this failure continues to occur reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199403) Get help: http://help/MSSQL_REPL-2147199403
Invalid column name 'metadata_select_proc'. (Source: MSSQLServer, Error number: 207) Get help: http://help/207
Invalid column name 'delete_proc'. (Source: MSSQLServer, Error number: 207) Get help: http://help/207
The merge process could not connect to the Publisher 'Server:database'. Check to ensure that the server is running. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199368) Get help: http://help/MSSQL_REPL-2147199368
Another merge agent for the subscription(s) is running or the server is working on a previous request by the same agent. (Source: MSSQLServer, Error number: 21036) Get help: http://help/21036
looking inside the sp_MSensure_single_instance stored procedure, it's trying to obtain an exclusive lock on resource 'Merge Agent Name' but fails and returns -1
this is the stored procedure executed by sp_MSensure_single_instance and @retcode = -1 and thus cannot obtain exclusive lock on resource
so i think it's failing because for some reason MSmerge_PAL_role database role does not have enough rights to obtain exclusive lock on necessary resources
i've tried many things to fix this, including scripting out and dropping all merge rep, turning off replication db option and reapplying replication create scripts on the server, and even manually deleting the MSmerge_PAL_role database role but still doesn't work
Hotfix fails to install on server. Msg error message below...
SS2K5 - 9.0.3050 - X64 Running as Local Admin Referred file does not exist and has never existed.
Any ideas on how to get this to apply?
Thanks - Covi
SQL Server Database Services 2005 (PROD02) Product Version (Previous): 3050 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB933097_sqlrun_sql.msp.log Error Number : 29538 Error Description : MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: E:MSSQL.2MSSQLDATAdistmdl1.ldf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again. ----------------------------------------------------------------------------------
There are special instructions for installing service packs on desktop edition installations -- command line options etc. How do you install hotfix roll-ups? Does build 2187 apply to desktop edition?
The 6:th of march Sql server data tools for Visual Studio 2012 was released.
[URL]
I seem to be unable to install this using the link provided on the blog page. I'm getting a "Same architecture installation" error. Running on the machine is Visual Studio 2012 Premium & Sql Server 2012 (64bit).
Please help,I am trying to install MSDE 2000 so that Backup exec will run on thisserver. I have gotten so far as to find an entry in my SQLSTP.TXT filethat says that c:mssql7 was detected so the install fails.Now, to start with there is no directory called C:mssql7 on thisserver. I have gone through all MS articles on manual removal of SQLserver and instances. I have searched the registry for mssql7 andremoved any keys that matched, as per MS article I have searched onSQLBOOT.dll and it is not present anywhere on my system and I still getthe same results.2:07:44 Begin Action: Detection12:07:44 SQL Server version already installed: 7.00.62312:07:44 Previous Install SQL Path: C:MSSQL712:07:44 Previous Install SQL Data Path: C:MSSQL712:07:44 End Action Detection12:07:44 Begin Action: ODBCLocked12:07:44 End Action ODBCLocked12:07:44 GetDefinition returned: 112:07:44 Previous SQL Server ProductType: MSDE [0x4]12:07:44 This combination of Package and Operating System allows a fullproduct install.can anyone think of anything here..what else could be causing the server to think there is a previousversion of SQL 7 on this box!!!?
Hi all, I have newly implemented a Try, Catch in my code (pasted below) and for some reason when I try to have the text of a label changed in the Catch exception, it says "Build failed" and doesn't tell me where the error is. Could anyone tell me what they can see is wrong please? Public Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click
Try 'error handler for if there is a dulplicate tillname in database (e.g. when user clicks refresh after submit)
Catch ex As SqlException 'What to do if there is a duplicate tillname
'Label2.Text = "test" errorLabel.Text = "This till already exists" Finally SQLDataSource1.Dispose() 'errorLabel.Text = "Till sucessfully added" End Try
End Sub
Protected Sub SqlDataSource1_Selecting(ByVal sender As Object, ByVal e As System.Web.UI.WebControls.SqlDataSourceSelectingEventArgs) Handles SQLDataSource1.Selecting
End Sub
Protected Sub GridView1_SelectedIndexChanged(ByVal sender As Object, ByVal e As System.EventArgs) Handles GridView1.SelectedIndexChanged
End Sub
Protected Sub SqlDataSource2_Selecting(ByVal sender As Object, ByVal e As System.Web.UI.WebControls.SqlDataSourceSelectingEventArgs) Handles SqlDataSource2.Selecting
I am having problems installing the SP1 for SQL server 2005 on a W2K3 R2 server. It appears that the Database Services and Analysis Services are not being updated. I would appreciate any help with this if anyone has seen or had experience with this issue.
Thanks, the basic log file is listed below.
Redist9_Hotfix_KB913090_3.log
09/17/2006 19:15:53.408 ================================================================================ 09/17/2006 19:15:53.408 Hotfix package launched 09/17/2006 19:16:57.719 Attempting to install instance: SQL Server Native Client 09/17/2006 19:16:57.735 Attempting to install target: HOSPSQL 09/17/2006 19:16:57.735 Attempting to install file: sqlncli.msi 09/17/2006 19:16:57.782 Attempting to install file: \HOSPSQLc$a9c93a7747dec24c4a58HotFixSqlncliFilessqlncli.msi 09/17/2006 19:16:57.782 Creating MSI install log file at: C:WINDOWSHotfixRedist9LogsRedist9_Hotfix_KB913090_sqlncli.msi.log 09/17/2006 19:16:57.782 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 09/17/2006 19:16:57.782 Failed to read registry key: Debug 09/17/2006 19:16:59.610 MSP returned 0: The action completed successfully. 09/17/2006 19:16:59.626 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 09/17/2006 19:16:59.626 Failed to read registry key: Debug 09/17/2006 19:16:59.626 Successfully installed file: \HOSPSQLc$a9c93a7747dec24c4a58HotFixSqlncliFilessqlncli.msi 09/17/2006 19:16:59.626 Successfully installed target: HOSPSQL 09/17/2006 19:16:59.626 Successfully installed instance: SQL Server Native Client 09/17/2006 19:16:59.626 09/17/2006 19:16:59.626 Product Status Summary: 09/17/2006 19:16:59.626 Product: SQL Server Native Client 09/17/2006 19:16:59.626 SQL Server Native Client (RTM ) - Success 09/17/2006 19:16:59.626 09/17/2006 19:16:59.626 Product: Setup Support Files 09/17/2006 19:16:59.626 Setup Support Files (RTM ) - Not Applied 09/17/2006 19:16:59.626 09/17/2006 19:16:59.626 Product: Database Services 09/17/2006 19:16:59.626 Database Services (RTM 1399 ENU) - Not Applied 09/17/2006 19:16:59.626 Analysis Services (RTM 1399 ENU) - Not Applied 09/17/2006 19:16:59.626 Reporting Services (SP1 2047 ENU) - Not Applied 09/17/2006 19:16:59.626 09/17/2006 19:16:59.626 Product: Notification Services 09/17/2006 19:16:59.626 Notification Services (SP1 2047 ENU) - Not Applied 09/17/2006 19:16:59.626 09/17/2006 19:16:59.626 Product: Integration Services 09/17/2006 19:16:59.626 Integration Services (SP1 2047 ENU) - Not Applied 09/17/2006 19:16:59.626 09/17/2006 19:16:59.626 Product: Client Components 09/17/2006 19:16:59.626 Client Components (SP1 2047 ENU) - Not Applied 09/17/2006 19:16:59.626 09/17/2006 19:16:59.626 Product: MSXML 6.0 Parser 09/17/2006 19:16:59.626 MSXML 6.0 Parser (RTM ) - Not Applied 09/17/2006 19:16:59.626 09/17/2006 19:16:59.626 Product: SQLXML4 09/17/2006 19:16:59.626 SQLXML4 (RTM ) - Not Applied 09/17/2006 19:16:59.626 09/17/2006 19:16:59.626 Product: Backward Compatibility 09/17/2006 19:16:59.626 Backward Compatibility (RTM ) - Not Applied 09/17/2006 19:16:59.626 09/17/2006 19:16:59.626 Product: Microsoft SQL Server VSS Writer 09/17/2006 19:16:59.626 Microsoft SQL Server VSS Writer (RTM ) - Not Applied 09/17/2006 19:16:59.626 09/17/2006 19:26:59.494 Hotfix package closed
I am trying to go through the Data Mining Web Controls Library sample found at http://msdn2.microsoft.com/en-us/library/ms160727(SQL.90).aspx
I have all the prerequisites installed on my local machine.
When I get to step 4 (On the Build menu, click Rebuild Solution.) in the "To build and install the Data Mining Web Controls" section.. I just get the below error.
Code SnippetError 3 Could not find file 'C:Program FilesMicrosoft SQL Server90SamplesAnalysis ServicesDataMiningData Mining Web ControlsWebControlsobjDebugMicrosoft.AnalysisServices.DataMiningHtmlViewers.dll' 'The system cannot find the file specified.' C:Program FilesMicrosoft SQL Server90SamplesAnalysis ServicesDataMiningData Mining Web ControlsWebControlsSetupDMHTMLViewersSetup.vdproj DMHTMLViewersSetup
I am running SQL Server 2005 SP2 developer edition. I have downloaded all the updated files for the AS project and samples.
I have search online for this error and come up w/ very little. Am I missing something? Is this an old sample that doesn't jive w/ SP2?
I am working on the build of a product where we build all software needed for the various servers automatically (web, SQL, SSAS etc.). Of course, all the standard builds work fine.
However, when building the SSIS project from the command-line, the binDeployment sub-folder is not created and therefore no SSISDeploymentManifest file is created. Even if the binDeployment sub-folder is present then SSISDeploymentManifest file is not created.
The command-line I am using is "C:Program FilesMicrosoft Visual Studio 8Common7IDEdevenv.exe" MyPackages.dtproj /build Release /project MyPackages
Of course, opening the project in Visual Studio and pressing build does indeed create the SSISDeploymentManifest, so the project is configured correctly.
We need a fully automated build, so can anyone help?
I want to build a silent setup/installation of MS-SQL-Server-Express 2005 for installation on customers computers. I want to integrate it in my own setup/installation routine of my application. How can I do that? Where can I get Infos or tutorials? Perhaps here ?
I did a small package with only one ODBC connection (Merant 3.70 32-Bit Progess). This package runs well in Visual Studio and fails when runs by SQL Server Agent.
Configuration:
SQL Server Agent on a 32Bit server.
The ODBC connection configuration in available on System DSN on this server.
The user of Server Agent have full access (Admin).
Connect Manager Provider: ".Net ProvidersOdbc Data Provider"
SQL Server version: 9.0.3042
Error Message:
Executed as user: TEKCON cadmin. ...ion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 16:50:33 Error: 2007-06-11 16:50:33.62 Code: 0xC0047062 Source: Data Flow Task DataReader Source [1] Description: System.Data.Odbc.OdbcException: ERROR [HYC00] [MERANT][ODBC PROGRESS driver]Optional feature not implemented. ERROR [HY000] [MERANT][ODBC PROGRESS driver]msgOpen: unable to open message file: PROMSGS ERROR [IM006] [MERANT][ODBC PROGRESS driver]Driver's SQLSetConnectAttr failed. ERROR [HYC00] [MERANT][ODBC PROGRESS driver]Optional feature not implemented. ERROR [HY000] [MERANT][ODBC PROGRESS driver]msgOpen: unable to open message file: PROMSGS ERROR [IM006] [MERANT][ODBC PROGRESS driver]Driver's SQLSetConnectAttr failed. at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode) at System.Data.Odbc.OdbcConnectionHandle..ctor(OdbcConnection connection, OdbcCon... The package execution fa... The step failed.
I created a .bat file with this instruction and It's run well:
My SSIS solution has about hundred packages and time to time I have to edit a package. I understand I could use 'Build' command to compile only updated package, as opposed to Rebuild which recomplies all of the packages.
Nevertheless, in both cases SSIS opens all of the packages in design environment before compilation. My packages are saved in SourceSafe and that process takes quite long and I was wondering if there was any other way to compile only updated package where none of the other packages are opened during Build/Rebuild process? For example we could use dtutil to deploy only updated packages without running Package Installation Wizard.
I couldn't manage to install SQL Server 2005 Express or Standart Edition on Windows Vista. The installation fails with the error message I pasted below:
TITLE: Microsoft SQL Server 2005 Setup ------------------------------
SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Windows NT user or group 'FUSIONSQLServer2005MSSQLUser$FUSION$MSSQLSERVER' not found. Check the name again.. Refer to the server error logs and Setup logs for detailed error information.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=29521&EvtType=lib%5codbc_statement.h%40Do_sqlScript%40OdbcStatement%3a%3aexecute_batch%40CnfgSQL%4080%40x3c29
Can someone please help me on this as this is an urgent situation...
The setup athenticates the Database Services and the Reporting Services. Database Services login is successful, but the setup raises an error on the authentication of the reporting Services.
It seems that all of a sudden my companies clients are running into problems with the installation of servicepack 5a on SQL Server 6.5 workstations. The servicepack is apparently getting to the point where it checks the master DB and then Chkmast.exe returns a value of 0 which seems to indicate that there is not enough space in the master DB for the service pack to install. I have expanded master databases well beyond the capacity where this would ever be a problem but the service pack continues to fail on chkmast.exe. What nweeds to be done to allow the service pack installation to complete?
We're trying to use the unattended installation method for installing SQL 2000 on Windows 2000 servers. I've installed it (through terminal server) on two machines successfully, and two machines unsuccessfully. On the unsuccessful machines, it fails with no errors, and no SQL files are installed (bombs out almost immediately).
Anyone else had this problem? Could it possibly be a hardware issue?
Installing SQL Server Express on Vista, directly after the "Compatibility Issues" dialogue, I get the error:
SQL Server setup unexpectedly failed. For more information, review the setup summary log file in %Program Files%Microsoft SQL Server90Setup BootstrapLOGSummary.txt
This file mentioned is virtually blank, but the Files subdirectory of LOG contains a setup log which contains:
Microsoft SQL Server 2005 Setup beginning at Sat Jun 23 12:44:49 2007 Process ID : 5068 C:UsersdajaboDesktop 8c1e33f5803c0da83setup.exe Version: 2005.90.2047.0 Running: LoadResourcesAction at: 2007/5/23 12:44:49 Complete: LoadResourcesAction at: 2007/5/23 12:44:49, returned true Running: ParseBootstrapOptionsAction at: 2007/5/23 12:44:49 Loaded DLL:C:UsersdajaboDesktop 8c1e33f5803c0da83xmlrw.dll Version:2.0.3609.0 Complete: ParseBootstrapOptionsAction at: 2007/5/23 12:44:49, returned falseError: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run:Could not parse command line due to datastore exception. Source File Name: utillibpersisthelpers.cpp Compiler Timestamp: Wed Oct 26 16:38:20 2005 Function Name: writeEncryptedString Source Line Number: 124 ---------------------------------------------------------- writeEncryptedString() failed Source File Name: utillibpersisthelpers.cpp Compiler Timestamp: Wed Oct 26 16:38:20 2005 Function Name: writeEncryptedString Source Line Number: 123 ---------------------------------------------------------- Error Code: 0x80070005 (5) Windows Error Text: Access is denied.
Source File Name: cryptohelpercryptsameusersamemachine.cpp Compiler Timestamp: Wed Oct 26 16:37:25 2005 Function Name: sqls::CryptSameUserSameMachine:rotectData Source Line Number: 50
5 Could not skip Component update due to datastore exception. Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Wed Oct 26 16:37:20 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "5068"} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Wed Oct 26 16:37:21 2005 Function Name: SetupBootstrapOptionsScope.InstallMediaPath Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupBootstrapOptionsScope" Running: ValidateWinNTAction at: 2007/5/23 12:44:49 Complete: ValidateWinNTAction at: 2007/5/23 12:44:49, returned true Running: ValidateMinOSAction at: 2007/5/23 12:44:49 Complete: ValidateMinOSAction at: 2007/5/23 12:44:49, returned true Running: PerformSCCAction at: 2007/5/23 12:44:49 Complete: PerformSCCAction at: 2007/5/23 12:44:49, returned true Running: ActivateLoggingAction at: 2007/5/23 12:44:49 Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run: Datastore exception while trying to write logging properties. Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Wed Oct 26 16:37:20 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Wed Oct 26 16:37:21 2005 Function Name: SetupStateScope.primaryLogFiles Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupStateScope" 038DCFACUnable to proceed with setup, there was a command line parsing error. : 2 Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified.
Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Wed Oct 26 16:37:21 2005 Function Name: SetupBootstrapOptionsScope.InstallMediaPath Source Line Number: 44
The installation fails and crashes with "Error 110", while attempting to install the SQL Native Client... then crashes (DrWatson). This happens on every OS and test machines that we have within our company... flavors of W2K and WXP, all with .Net Framework 2.0.
If the SQL Native Client exists, the installation continues without error. If SQLEXPR32.EXE is run directly from the command line, the installation will succeed.
If SQLEXPR32.EXE is called from a Windows Installer Custom Action type 50, it will always fail. This is the method we used to successfully install MSDE previously.
When trying to install SQL 2005, I keep getting the foll. error:
Error 1706. Setup cannot find the required files. Check your connection to the network or CD-Rom drive. For other potential soltions to this problem, see C:Program ....1033setup.chm
I have tried using two different DVDs, and also downloaded SQL 2005 from msdn, but none of them work.
I have tried this many times....cleaned all previous MS SQL installations...rebooted....all with the same result below.
I insert Disc 1 of the Developer edition and all is find until it gets to the main installation...then OWC fails ("Setup cannot find the files specified") although I have an open Internet connection from where it can be downloaded.
Then the main Database server and Integration services installation fails, and other components succeed. When I click the error message it says "Please insert Disc 2" - although the main installation never prompts for Disc 2 (which are the Tools I believe).
Even if I install Disc 2, the installation never succeeds - and the main componets I am interested in - Database server and Integration services - always fails.
I have a table with embedded files in it and also ftp server/user/pwd fields so that each record has all the data and information required and need to configure an SSIS package to to FTP them to the destination as specified in the record within the databaseAt the moment I have a data flow task which uses a Derived Column and an Export Column transformation which creates the files to a temp folder then it runs a ForEach loop container back on the control flow to FTP each file and to then move each file to an archive folder.
All I think I need to know how to do is to somehow control the FTP connection settings with the fields from the database within this foreach loop, but it is a for each file collection. I also need to update each record saying it has been FTP'd as well Do I need to have an initial query outside of this foreach loop to populate an array which can be used for the 4 FTP connection fields (server/user/pwd/directory), if so how?
Any ideas as to how to correctly finish this package.
