I just tried to install the file:
D:WINDOWSMicrosoft.NETFrameworkv2.0.50727InstallUtil.exe SQLAgent.exe by running it from a command prompt.
and got an error that the system could not find the file or one of its components. It is a farily new install. I do not think I've lost any files any time.
What is the problem?
Thanks.
Hi,
I'm running SP2 to upgrade my current instance of SP1. At the point of "SQL Server Database Services | Configuring components..." it stops with the following error:
#####
Microsoft SQL Server 2005 Setup
------------------------------
The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed
#####
The setup log contains the following detail in the "LaunchFunction"
#####
<Func Name='LaunchFunction'>
Function=ValidateUpgrade
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
Doing Action: ValidateUpgrade
PerfTime Start: ValidateUpgrade : Tue Feb 27 09:47:13 2007
<Func Name='ValidateUpgrade'>
<Func Name='updateFeatureSellection'>
<Func Name='SqlComponentUpgrade'>
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
<Func Name='ProcessHeaderTable'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
MSI (s) (34!60) [09:47:13:296]: Note: 1: 2205 2: 3: _sqlSqlUpgradeInstallSequence
MSI (s) (34!60) [09:47:13:296]: Note: 1: 2228 2: 3: _sqlSqlUpgradeInstallSequence 4: CREATE TABLE `_sqlSqlUpgradeInstallSequence` (`Action` CHAR(255) NOT NULL, `Sequence` INT NOT NULL, `Param` CHAR(0), `Retryable` INT NOT NULL, `Fatal` INT NOT NULL PRIMARY KEY `Action`, `Sequence`)
MSI (s) (34!60) [09:47:13:296]: Note: 1: 2262 2: _sqlSqlUpgradeInstallSequence 3: -2147287038
<Func Name='GetFileTargetPath'>
MSI (s) (34!60) [09:47:13:328]: PROPERTY CHANGE: Adding Sql_sqlSqlUpgradeInstallSequence property. Its value is '15000000'.
MSI (s) (34!60) [09:47:13:328]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '15000000'. Its new value: '15040000'.
MSI (s) (34!60) [09:47:13:328]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '15040000'. Its new value: '15050000'.
MSI (s) (34!60) [09:47:13:343]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '15050000'. Its new value: '85050000'.
MSI (s) (34!60) [09:47:13:343]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '85050000'. Its new value: '265604600'.
MSI (s) (34!60) [09:47:13:343]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '265604600'. Its new value: '280604600'.
MSI (s) (34!60) [09:47:13:343]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '280604600'. Its new value: '310604600'.
MSI (s) (34!60) [09:47:13:343]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '310604600'. Its new value: '310704600'.
Couldn't find SQL Agent service SQLAgent$GATEKEEPER. Skipping service stop
<EndFunc Name='SqlComponentUpgrade' Return='0' GetLastError='0'>
Added REPL to SqlUpgrade property
<Func Name='updateFeatureSellection'>
Attempt to start service when it is already running
SQL service MSSQL$GATEKEEPER started successfully waiting for SQL service to accept client connections
SQL_SUCCESS_WITH_INFO (1) in OdbcConnection::connect
sqlstate=01000, level=-1, state=-1, native_error=5701, msg=[Microsoft][SQL Native Client][SQL Server]Changed database context to 'master'.
sqlstate=01000, level=-1, state=-1, native_error=5703, msg=[Microsoft][SQL Native Client][SQL Server]Changed language setting to us_english.
<Func Name='SqlComponentUpgrade'>
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
<Func Name='ProcessHeaderTable'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
MSI (s) (34!60) [09:47:13:906]: Note: 1: 2259 2: 3: 4:
<Func Name='GetFileTargetPath'>
Error Code: 0x8007065b (1627)
Windows Error Text: Function failed during execution.
Source File Name: darlibviewinstaller.cpp
Compiler Timestamp: Wed Jun 14 16:19:22 2006
Function Name: sqls::ViewInstaller::modify
Source Line Number: 137
---- Context -----------------------------------------------
Setting status of unmanaged components and removing unmanaged resources
Failed to modify installer view
1: 2259 2: 3: 4:
Error Code: 1627
MSI (s) (34!60) [09:53:40:125]: Product: Microsoft SQL Server 2005 Express Edition -- Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed
Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed
<Failure Type='Fatal' Error='1627'>
<EndFunc Name='LaunchFunction' Return='1627' GetLastError='203'>
#####
I have installed the same SP2 on another machine (Both XP SP2) without further problems. The only difference between the two machines is the one with errors has another instance of SQL 2005 (Not express) as the default instance and the Express named instance I am upgraded. The second machine only has Express named instance.
Any help appreciated.
Rab
I am attempting to install SQL Server express on an XP (SP2) machine with a Pentium processor. The .NET framework version is 2.0. All previous versions of SQL server and related components have been uninstalled, and all related files deleted. Also, during installation, I installed SQL Express using the local service account (vs. network service) per a suggestion in a related thread. I have installed/unistalled numerous times, and continue to receive the same error. At this point, this is becoming a critical issue related to a client ASP.NET application using a SQL express 2005 database. I was hoping by now that MS would have released a new version or patch that would solve this problem, but that does not seem to be the case, that I'm aware of.
Summary Log:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Tue Aug 21 14:59:31 2007
Machine : DEBASER1
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : DEBASER1
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : DEBASER1
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : DEBASER1
Product : MSXML 6.0 Parser (KB933579)
Product Version : 6.10.1200.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : DEBASER1
Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
--------------------------------------------------------------------------------
Machine : DEBASER1
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.2.3042.00
Install : Failed
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SQL.log
Last Action : InstallFinalize
Error String : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (3) The system cannot find the path specified.
Error Number : 29503
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Tue Aug 21 15:15:34 2007
List of log files:
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_Core(Local).log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SQLSupport_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SQLNCLI_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SqlWriter_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_MSXML6_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SQL.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_Datastore.xml
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_.NET Framework 2.0.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_Support.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_Core.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SCC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_WI.log
Core Log:
Microsoft SQL Server 2005 Setup beginning at Tue Aug 21 14:59:31 2007
Process ID : 2960
c:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe Version: 2005.90.3042.0
Running: LoadResourcesAction at: 2007/7/21 14:59:31
Complete: LoadResourcesAction at: 2007/7/21 14:59:31, returned true
Running: ParseBootstrapOptionsAction at: 2007/7/21 14:59:31
Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapxmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2007/7/21 14:59:31, returned true
Running: ValidateWinNTAction at: 2007/7/21 14:59:31
Complete: ValidateWinNTAction at: 2007/7/21 14:59:31, returned true
Running: ValidateMinOSAction at: 2007/7/21 14:59:31
Complete: ValidateMinOSAction at: 2007/7/21 14:59:31, returned true
Running: PerformSCCAction at: 2007/7/21 14:59:31
Complete: PerformSCCAction at: 2007/7/21 14:59:31, returned true
Running: ActivateLoggingAction at: 2007/7/21 14:59:31
Complete: ActivateLoggingAction at: 2007/7/21 14:59:31, returned true
Running: DetectPatchedBootstrapAction at: 2007/7/21 14:59:31
Complete: DetectPatchedBootstrapAction at: 2007/7/21 14:59:31, returned true
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__2960" returned false.
Action "BeginBootstrapLogicStage" will be skipped due to the following restrictions:
Condition "Setup is running locally." returned true.
Running: PerformDotNetCheck2 at: 2007/7/21 14:59:31
Complete: PerformDotNetCheck2 at: 2007/7/21 14:59:31, returned true
Running: InvokeSqlSetupDllAction at: 2007/7/21 14:59:31
Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlspars.dll Version:2005.90.3042.0
<Func Name='DwLaunchMsiExec'>
Examining 'sqlspars' globals to initialize 'SetupStateScope'
Opening 'MachineConfigScope' for [DEBASER1]
Trying to find Product Code from command line or passed transform
If possible, determine install id and type
Trying to find Instance Name from command line.
No Instance Name provided on the command line
If possible, determine action
Machine = DEBASER1, Article = WMIServiceWin32OSWorking, Result = 0 (0x0)
Machine = DEBASER1, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0)
Machine = DEBASER1, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0)
Machine = DEBASER1, Article = WMIServiceReadRegWorking, Result = 0 (0x0)
Machine = DEBASER1, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0)
Machine = DEBASER1, Article = WMIServiceCIMDataWorking, Result = 0 (0x0)
Machine = DEBASER1, Article = XMLDomDocument, Result = 0 (0x0)
Machine = DEBASER1, Article = Processor, Result = 0 (0x0)
Machine = DEBASER1, Article = PhysicalMemory, Result = 0 (0x0)
Machine = DEBASER1, Article = DiskFreeSpace, Result = 0 (0x0)
Machine = DEBASER1, Article = OSVersion, Result = 0 (0x0)
Machine = DEBASER1, Article = OSServicePack, Result = 0 (0x0)
Machine = DEBASER1, Article = OSType, Result = 0 (0x0)
Machine = DEBASER1, Article = AdminShare, Result = 0 (0x0)
Machine = DEBASER1, Article = PendingReboot, Result = 0 (0x0)
Machine = DEBASER1, Article = IEVersion, Result = 0 (0x0)
Machine = DEBASER1, Article = DriveWriteAccess, Result = 0 (0x0)
Machine = DEBASER1, Article = COMPlus, Result = 0 (0x0)
Machine = DEBASER1, Article = ASPNETVersionRegistration, Result = 0 (0x0)
Machine = DEBASER1, Article = MDAC25Version, Result = 0 (0x0)
Machine = DEBASER1, Article = SKUUpgrade, Result = 0 (0x0)
*******************************************
Setup Consistency Check Report for Machine: DEBASER1
*******************************************
Article: WMI Service Requirement, Result: CheckPassed
Article: MSXML Requirement, Result: CheckPassed
Article: Operating System Minimum Level Requirement, Result: CheckPassed
Article: Operating System Service Pack Level Requirement, Result: CheckPassed
Article: SQL Compatibility With Operating System, Result: CheckPassed
Article: Minimum Hardware Requirement, Result: CheckPassed
Article: Pending Reboot Requirement, Result: CheckPassed
Article: Default Installation Path Permission Requirement, Result: CheckPassed
Article: Internet Explorer Requirement, Result: CheckPassed
Article: Check COM+ Catalogue, Result: CheckPassed
Article: ASP.Net Registration Requirement, Result: CheckPassed
Article: Minimum MDAC Version Requirement, Result: CheckPassed
Article: Edition Upgrade Check, Result: CheckPassed
<Func Name='PerformDetections'>
0
<EndFunc Name='PerformDetections' Return='0' GetLastError='0'>
<Func Name='DisplaySCCWizard'>
CSetupBootstrapWizard returned 1
<EndFunc Name='DisplaySCCWizard' Return='0' GetLastError='183'>
Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.3042.0
<EndFunc Name='DwLaunchMsiExec' Return='0' GetLastError='0'>
Complete: InvokeSqlSetupDllAction at: 2007/7/21 15:0:29, returned true
Running: SetPackageInstallStateAction at: 2007/7/21 15:0:29
Complete: SetPackageInstallStateAction at: 2007/7/21 15:0:29, returned true
Running: DeterminePackageTransformsAction at: 2007/7/21 15:0:29
Complete: DeterminePackageTransformsAction at: 2007/7/21 15:0:30, returned true
Running: ValidateSetupPropertiesAction at: 2007/7/21 15:0:30
Complete: ValidateSetupPropertiesAction at: 2007/7/21 15:0:30, returned true
Running: OpenPipeAction at: 2007/7/21 15:0:30
Complete: OpenPipeAction at: 2007/7/21 15:0:30, returned false
Error: Action "OpenPipeAction" failed during execution.
Running: CreatePipeAction at: 2007/7/21 15:0:30
Complete: CreatePipeAction at: 2007/7/21 15:0:30, returned false
Error: Action "CreatePipeAction" failed during execution.
Action "RunRemoteSetupAction" will be skipped due to the following restrictions:
Condition "Action: CreatePipeAction has finished and passed." returned false.
Running: PopulateMutatorDbAction at: 2007/7/21 15:0:30
Complete: PopulateMutatorDbAction at: 2007/7/21 15:0:30, returned true
Running: GenerateRequestsAction at: 2007/7/21 15:0:30
SQL_Engine = 3
SQL_Data_Files = 3
SQL_Replication = -1
SQL_FullText = -1
SQL_SharedTools = 3
SQL_BC_DEP = -1
Analysis_Server = -1
AnalysisDataFiles = -1
AnalysisSharedTools = -1
RS_Server = -1
RS_Web_Interface = -1
RS_SharedTools = -1
Notification_Services = -1
NS_Engine = -1
NS_Client = -1
SQL_DTS = -1
Client_Components = -1
Connectivity = -1
SQL_Tools90 = -1
SQL_WarehouseDevWorkbench = -1
SDK = -1
SQLXML = -1
Tools_Legacy = -1
TOOLS_BC_DEP = -1
SQL_SSMSEE = -1
SQL_Documentation = -1
SQL_BooksOnline = -1
SQL_DatabaseSamples = -1
SQL_AdventureWorksSamples = -1
SQL_AdventureWorksDWSamples = -1
SQL_AdventureWorksASSamples = -1
SQL_Samples = -1
Complete: GenerateRequestsAction at: 2007/7/21 15:0:32, returned true
Running: CreateProgressWindowAction at: 2007/7/21 15:0:32
Complete: CreateProgressWindowAction at: 2007/7/21 15:0:32, returned true
Running: ScheduleActionAction at: 2007/7/21 15:0:32
Complete: ScheduleActionAction at: 2007/7/21 15:0:33, returned true
Skipped: InstallASAction.11
Skipped: Action "InstallASAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.18
Skipped: Action "InstallASAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.22
Skipped: Action "InstallASAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.9
Skipped: Action "InstallASAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "as", install will be skipped as a result.
Skipped: InstallDTSAction
Skipped: Action "InstallDTSAction" was not run. Information reported during analysis:
No install request found for package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.11
Skipped: Action "InstallDTSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.12
Skipped: Action "InstallDTSAction.12" was not run. Information reported during analysis:
No install request found for package: "sqlncli", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.18
Skipped: Action "InstallDTSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.22
Skipped: Action "InstallDTSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.9
Skipped: Action "InstallDTSAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "dts", install will be skipped as a result.
Skipped: InstallNSAction
Skipped: Action "InstallNSAction" was not run. Information reported during analysis:
No install request found for package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.11
Skipped: Action "InstallNSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.12
Skipped: Action "InstallNSAction.12" was not run. Information reported during analysis:
No install request found for package: "sqlncli", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.18
Skipped: Action "InstallNSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.22
Skipped: Action "InstallNSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.9
Skipped: Action "InstallNSAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "ns", install will be skipped as a result.
Skipped: InstallRSAction.11
Skipped: Action "InstallRSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "rs", install will be skipped as a result.
Skipped: InstallRSAction.18
Skipped: Action "InstallRSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "rs", install will be skipped as a result.
Skipped: InstallRSAction.22
Skipped: Action "InstallRSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "rs", install will be skipped as a result.
Running: InstallSqlAction.11 at: 2007/7/21 15:0:33
Installing: sqlsupport on target: DEBASER1
Complete: InstallSqlAction.11 at: 2007/7/21 15:11:8, returned true
Running: InstallSqlAction.12 at: 2007/7/21 15:11:8
Installing: sqlncli on target: DEBASER1
Complete: InstallSqlAction.12 at: 2007/7/21 15:11:17, returned true
Skipped: InstallSqlAction.18
Skipped: Action "InstallSqlAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "sql", install will be skipped as a result.
Running: InstallSqlAction.21 at: 2007/7/21 15:11:17
Installing: sqlwriter on target: DEBASER1
Complete: InstallSqlAction.21 at: 2007/7/21 15:11:22, returned true
Skipped: InstallSqlAction.22
Skipped: Action "InstallSqlAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "sql", install will be skipped as a result.
Running: InstallSqlAction.9 at: 2007/7/21 15:11:22
Installing: msxml6 on target: DEBASER1
Complete: InstallSqlAction.9 at: 2007/7/21 15:11:24, returned true
Skipped: InstallToolsAction.11
Skipped: Action "InstallToolsAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "tools", install will be skipped as a result.
Skipped: InstallToolsAction.12
Skipped: Action "InstallToolsAction.12" was not run. Information reported during analysis:
No install request found for package: "sqlncli", referred by package: "tools", install will be skipped as a result.
Skipped: InstallToolsAction.13
Skipped: Action "InstallToolsAction.13" was not run. Information reported during analysis:
No install request found for package: "PPESku", referred by package: "tools", install will be skipped as a result.
Skipped: InstallToolsAction.18
Skipped: Action "InstallToolsAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "tools", install will be skipped as a result.
Skipped: InstallToolsAction.20
Skipped: Action "InstallToolsAction.20" was not run. Information reported during analysis:
No install request found for package: "BOL", referred by package: "tools", install will be skipped as a result.
Skipped: InstallToolsAction.22
Skipped: Action "InstallToolsAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "tools", install will be skipped as a result.
Skipped: InstallToolsAction.23
Skipped: Action "InstallToolsAction.23" was not run. Information reported during analysis:
No install request found for package: "ssmsee", referred by package: "tools", install will be skipped as a result.
Skipped: InstallToolsAction.9
Skipped: Action "InstallToolsAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "tools", install will be skipped as a result.
Skipped: InstallNSAction.10
Skipped: Action "InstallNSAction.10" was not run. Information reported during analysis:
No install request found for package: "sqlxml4", referred by package: "ns", install will be skipped as a result.
Running: InstallSqlAction at: 2007/7/21 15:11:25
Installing: sql on target: DEBASER1
Failed to install package
Fatal error during installation.
Setting package return code to: 29503
Complete: InstallSqlAction at: 2007/7/21 15:15:29, returned false
Error: Action "InstallSqlAction" failed during execution. Error information reported during run:
Target collection includes the local machine.
Invoking installPackage() on local machine.
Skipped: InstallToolsAction.10
Skipped: Action "InstallToolsAction.10" was not run. Information reported during analysis:
No install request found for package: "sqlxml4", referred by package: "tools", install will be skipped as a result.
Skipped: InstallASAction
Skipped: Action "InstallASAction" was not run. Information reported during analysis:
No install request found for package: "as", install will be skipped as a result.
Skipped: InstallRSAction
Skipped: Action "InstallRSAction" was not run. Information reported during analysis:
No install request found for package: "rs", install will be skipped as a result.
Skipped: InstallToolsAction
Skipped: Action "InstallToolsAction" was not run. Information reported during analysis:
No install request found for package: "tools", install will be skipped as a result.
Skipped: RepairForBackwardsCompatRedistAction
Skipped: Action "RepairForBackwardsCompatRedistAction" was not run. Information reported during analysis:
Action: "RepairForBackwardsCompatRedistAction" will be skipped due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Error: Action "UninstallForMSDE2000Action" failed during execution. Error information reported during run:
Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchMSDE2000" failed due to a precondition.
Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run:
Action: "UninstallForSQLAction" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchLibertySql" failed due to a precondition.
Skipped: UninstallForRS2000Action
Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis:
Action: "UninstallForRS2000Action" will be skipped due to the following condition:
Condition "Action: InstallRSAction was skipped." returned true.
Error: Action "ExposeVistaClusteredResources" failed during execution. Error information reported during run:
Action: "ExposeVistaClusteredResources" will be marked as failed due to the following condition:
Condition "The Clustered SQL Server instance that hosts is installed." returned false.
Running: ReportChainingResults at: 2007/7/21 15:15:29
Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 3
Error Code: 0x80070003 (3)
Windows Error Text: The system cannot find the path specified.
Source File Name: sqlchainingsqlchainingactions.cpp
Compiler Timestamp: Thu Nov 16 20:31:57 2006
Function Name: sqls::ReportChainingResults:erform
Source Line Number: 3521
---- Context -----------------------------------------------
sqls::HostSetupPackageInstallerSynch:ostCommit
sqls::HighlyAvailablePackage:reInstall
led due to cancel code received from cancel source: 29539
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_.NET Framework 2.0.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2007/7/21 15:15:42
Message pump returning: 3
Any ideas ... ?
Carlo
Can some one help me with this ?
C:WINDOWSsystem32Odbc32.dll
Version:
3.525.1117.0
SQL_SUCCESS_WITH_INFO (1) in OdbcConnection::connect
sqlstate=01000, level=-1, state=-1, native_error=444, msg=The driver returned invalid (or failed to return) SQL_DRIVER_ODBC_VER:
sqlstate=01000, level=-1, state=-1, native_error=5701, msg=[Microsoft][SQL Native Client][SQL Server]Changed database context to 'master'.
sqlstate=01000, level=-1, state=-1, native_error=5703, msg=[Microsoft][SQL Native Client][SQL Server]Changed language setting to us_english.
SQL_ERROR (-1) in OdbcConnectionHandle::set_attr
sqlstate=IM001, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Driver does not support this function
SQL_ERROR (-1) in OdbcConnectionHandle::get_attr
sqlstate=IM001, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Driver does not support this function
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
Error Code: 0x8007ea74 (60020)
Windows Error Text: Source File Name: libodbc_handle.h
Compiler Timestamp: Wed Oct 26 16:37:41 2005
Function Name: OdbcConnectionHandle::set_attr@connect
Source Line Number: 168
---- Context -----------------------------------------------
Connecting to SQL Server
ExecuteSqlCommands
Originial error was 8007ea74 (60020)
ipt
SqlScriptHlpr
Error Code: 60020
MSI (s) (D0!0C) [18:24:47:187]: Product: Microsoft SQL Server 2005 Express Edition -- Error 29521. SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][ODBC Driver Manager] Driver does not support this function. Refer to the server error logs and Setup logs for detailed error information.
Hi,
I have been trying to install SQL Express SP2 (SQLEXPR32.exe) on a Window Vista Home Premium for past 2 days . After failing I tried installing SQLEXPR_ADV. (Maybe I have a corrupted download, desperate enough to try anything.). However it keeps showing the following error:
SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:Program FilesMicrosoft SQL Server90Sharedsqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
I have search through the forums. One of the possibilities is due to a WMI repository corruption. Tried fixing it, but the problem still persists. (Maybe I am doing it the wrong way , I have downloaded the WMIDiag scripts, not too sure if i ran it correctly).
Below is the installation summary:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Home Edition (Build 6000)
Time : Thu Mar 15 02:13:51 2007
ATLANTIS : Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.
Machine : ATLANTIS
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0013_ATLANTIS_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : ATLANTIS
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0013_ATLANTIS_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : ATLANTIS
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0013_ATLANTIS_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : ATLANTIS
Product : SQL Server Database Services
Error : SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:Program FilesMicrosoft SQL Server90Sharedsqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
--------------------------------------------------------------------------------
Machine : ATLANTIS
Product : Microsoft SQL Server 2005
Product Version : 9.2.3042.00
Install : Failed
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0013_ATLANTIS_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:Program FilesMicrosoft SQL Server90Sharedsqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
Error Number : 29513
--------------------------------------------------------------------------------
What are the other possibilities and fixes? Please help.
Thanks a million.
with the following log:
Microsoft SQL Server 2005 Setup beginning at Wed Jun 28 19:02:06 2006
Process ID : 1220
E:Serverssetup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2006/5/28 19:2:5
Complete: LoadResourcesAction at: 2006/5/28 19:2:5, returned true
Running: ParseBootstrapOptionsAction at: 2006/5/28 19:2:5
Loaded DLL:E:Serversxmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2006/5/28 19:2:6, returned false
Error: 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: Fri Jul 29 01:13:55 2005
Function Name: writeEncryptedString
Source Line Number: 124
----------------------------------------------------------
writeEncryptedString() failed
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Fri Jul 29 01:13:55 2005
Function Name: writeEncryptedString
Source Line Number: 123
----------------------------------------------------------
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.
Source File Name: cryptohelpercryptsameusersamemachine.cpp
Compiler Timestamp: Mon Jun 13 14:30:00 2005
Function Name: sqls::CryptSameUserSameMachine::ProtectData
Source Line Number: 50
2
Could not skip Component update due to datastore exception.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "1220"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Running: ValidateWinNTAction at: 2006/5/28 19:2:6
Complete: ValidateWinNTAction at: 2006/5/28 19:2:6, returned true
Running: ValidateMinOSAction at: 2006/5/28 19:2:6
Complete: ValidateMinOSAction at: 2006/5/28 19:2:6, returned true
Running: PerformSCCAction at: 2006/5/28 19:2:6
Complete: PerformSCCAction at: 2006/5/28 19:2:6, returned true
Running: ActivateLoggingAction at: 2006/5/28 19:2:6
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: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupStateScope.primaryLogFiles
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
00D9CFC4Unable 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: Fri Jul 29 01:13:50 2005
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
Class not registered.
Failed to create CAB file due to datastore exception
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "1220"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupBootstrapOptionsScope.HostSetup
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Message pump returning: 2
I have created a job with several SSIS packages included in it. There is a failure when I schedule and run the job. Where can I find the information why it is failing? When I run the packages individually, they run fine. Thanks in advance.
View 3 Replies View RelatedI have an issue on SQL Agent and wish you to advice:
Servers Environment:
The SQL Server and SQL Agent Service is installed on clustered Server1 where the Integration Services (IS) is installed on Server2. Deployment of SSIS packages have been done on Server1 and IS on Server2 is pointing to it.
Case:
1. In SQL Managament Studio, connection on Database Engine is up on Server1, connection on IS is up on Server2.
2. Execution of all packages via IS connection on Server2 is working well. No issue on running.
3. SQL Agent Job is created under Server1. The job failed on running. Message from the Log File Viewer:
"The job failed. The Job was invoked by User domainhost. The last step to run was step 1 (tewst)."
"Executed as user: domainhost. ...n 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Code: 0xC0048020 Description: The version of component "Update to DB" (828) is not compatible with this version of the DataFlow."
Please advice ...
HELP>>> I am getting desperate
we recently had a failure which ended up wrecking my replication. The basic layout is from a source server -> Distribution Server then out to several other servers. Long story short the distribution database had to be moved to a new drive and I am now getting the following error message
The specified LSN (0003d4f0:0000721e:001b) for repldone log scan occurs before the current start of replication in the log (0003d63a:00002803:0001).
(Source: fsdpdcis (Data source); Error number: 18768)
---------------------------------------------------------------------------------------------------------------
The process could not set the last distributed transaction.
(Source: fsdpdcis-DPDDATA-1 (Agent); Error number: 22017)
I have reinitialized all subscriptions on the fsdpdcis server and run subscription validation (with no response). The data did re-load during the reinitialization but does not seem to be getting updated. This is driving me crazy and I am desperate. Any suggestions would be greatly appreciated. I have search MS knowledge base with no results and BOL has not been any help so far.
Thanks
Steve
Hi,
I am running transactional replication between a pair of SQL Server 2005 machines using a remote distributor. Occasionally the log reader agent fails with the error
"Replication-Replication Transaction-Log Reader Subsystem: agent * failed. The process could not execute 'sp_MSpub_adjust_identity' on '*'."
The agent starts back up again almost immediately on its own with seemingly no problems. I haven't been able to find any documentation on this error from Microsoft. Any ideas?
It is not a permissions issue as the log reader agent (and all of the other agents at that) are running under windows accounts with domain admin access for the domain that both the publisher and the distributor SQL Servers are on. (I know, I know, that's horrible. I've only been here a week and a half and I just found out about this today, so I didn't have anything to do with such a glaring security issue.) All of the SQL Servers involved with the replication are still granting sysadmin access to the windows administrators group.
I have scheduled a job in SQL Server Agent, as it executes it fails Immediatly. The error history displays the following error details, which i copied from the log file
"Description: Unable to load the package as XML because of package does not have a valid XML format. A specific XML parser error will be posted.
The system cannot find the path specified.". This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format. End Error ... The package could not be f... The step failed."
I am using the File System Type to load my package.
Please assisst me in finding the solution
Regards
ZeEsHaN
Hi all,
I'm new to sql server administration so please show some understanding!
I installed sql server 2000 personal edition (upgrated to sp4) on an windows xp pro OS, but I cannot get the sql server agent service running. I get a message " the service did not start due to a logon failure". The server is my local pc, I'm using windows authentication and the login is "domain/loginname" where domain is my pc name.
Does it have to be installed on a server OS to have this service running?
Thanks George
Hi There
I have a publisher, remote distributor and subscriber all running SS2000.
Under replication monitor on the distributor, under replication alerts i have enabled the "replication agent failure" alert.
All i need to know is should this alert trigger if the distribution agent that runs on the subscriber not the distributor fails?
I have add occurences of the distribution agent failing and the alert is not triggerred, is this because it only triggers for the agents that run on the distributor, ie: snapshot and log reader agents?
Thanx
After upgrading a server from SQL 2000 to SQL 2005, I can't get any SQL Agent jobs to run, giving logon failed messages. MSSQLSERVER and SQLSERVERAGENT services are set up to run as the same domain account which has administrative rights to the server and is a SQL login with the sysadmin role. For basic testing purposes, I created a test job that all it does is run a T-SQL command 'SELECT @@VERSION'. The job is also set to run as the same account that the Agent is running under. Below are the logs (with trace messages on) from the point of starting the Agent to my attempt to run the job (user and server names have been changed to protect the innocent):
2007-10-22 15:31:15 - ? [297] SQLServer Message: 15457, Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install. [SQLSTATE 01000] (DisableAgentXPs)
2007-10-22 15:31:15 - ? [297] SQLServer Message: 15457, Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install. [SQLSTATE 01000] (DisableAgentXPs)
2007-10-22 15:31:15 - ? [297] SQLServer Message: 15457, Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install. [SQLSTATE 01000] (DisableAgentXPs)
2007-10-22 15:31:15 - ? [100] Microsoft SQLServerAgent version 9.00.3042.00 (x86 unicode retail build) : Process ID 5168
2007-10-22 15:31:15 - ? [101] SQL Server TESTSERVER version 9.00.3042 (0 connection limit)
2007-10-22 15:31:15 - ? [102] SQL Server ODBC driver version 9.00.3042
2007-10-22 15:31:15 - ? [103] NetLib being used by driver is DBNETLIB.DLL; Local host server is
2007-10-22 15:31:15 - ? [310] 4 processor(s) and 3328 MB RAM detected
2007-10-22 15:31:15 - ? [339] Local computer is TESTSERVER running Windows NT 5.2 (3790) Service Pack 2
2007-10-22 15:31:15 - ? [431] Populating subsystems cache...
2007-10-22 15:31:15 - ? [432] There are 11 subsystems in the subsystems cache
2007-10-22 15:31:15 - ? [124] Subsystem 'TSQL' successfully loaded (maximum concurrency: 80)
2007-10-22 15:31:16 - ? [124] Subsystem 'ActiveScripting' successfully loaded (maximum concurrency: 40)
2007-10-22 15:31:16 - ? [124] Subsystem 'CmdExec' successfully loaded (maximum concurrency: 40)
2007-10-22 15:31:16 - ? [124] Subsystem 'Snapshot' successfully loaded (maximum concurrency: 400)
2007-10-22 15:31:16 - ? [124] Subsystem 'LogReader' successfully loaded (maximum concurrency: 100)
2007-10-22 15:31:16 - ? [124] Subsystem 'Distribution' successfully loaded (maximum concurrency: 400)
2007-10-22 15:31:16 - ? [124] Subsystem 'Merge' successfully loaded (maximum concurrency: 400)
2007-10-22 15:31:16 - ? [124] Subsystem 'QueueReader' successfully loaded (maximum concurrency: 400)
2007-10-22 15:31:16 - ? [124] Subsystem 'ANALYSISQUERY' successfully loaded (maximum concurrency: 400)
2007-10-22 15:31:16 - ? [124] Subsystem 'ANALYSISCOMMAND' successfully loaded (maximum concurrency: 400)
2007-10-22 15:31:16 - ? [124] Subsystem 'SSIS' successfully loaded (maximum concurrency: 400)
2007-10-22 15:31:16 - ? [129] SQLSERVERAGENT starting under Windows NT service control
2007-10-22 15:31:16 - + [260] Unable to start mail session (reason: No mail profile defined)
2007-10-22 15:31:16 - ? [174] Job scheduler engine started (maximum worker threads: 400)
2007-10-22 15:31:16 - ? [193] Alert engine started (using Eventlog Events)
2007-10-22 15:31:16 - ? [146] Request servicer engine started
2007-10-22 15:31:16 - + [396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
2007-10-22 15:31:16 - ? [110] Starting SQLServerAgent Monitor using '' as the notification recipient...
2007-10-22 15:31:16 - ? [133] Support engine started
2007-10-22 15:31:16 - ? [167] Populating job cache...
2007-10-22 15:31:16 - ? [297] SQLServer Message: 0, SQLServerAgent Monitor started successfully. [SQLSTATE 01000]
2007-10-22 15:31:16 - ? [168] There are 2 job(s) [0 disabled] in the job cache
2007-10-22 15:31:16 - ? [170] Populating alert cache...
2007-10-22 15:31:16 - ? [171] There are 0 alert(s) in the alert cache
2007-10-22 15:32:59 - ? [177] Job Test1 has been requested to run by User DOMAINmyaccount
2007-10-22 15:32:59 - ! [382] Logon to server 'TESTSERVER' failed (ConnAttemptCachableOp)
2007-10-22 15:32:59 - ! [382] Logon to server 'TESTSERVER' failed (ConnAttemptCachableOp)
2007-10-22 15:32:59 - ! [382] Logon to server 'TESTSERVER' failed (ConnAttemptCachableOp)
2007-10-22 15:32:59 - ? [184] Job completion for Test1 is being logged to sysjobhistory
2007-10-22 15:32:59 - ! [382] Logon to server 'TESTSERVER' failed (ConnAttemptCachableOp)
Recently I witnessed a failed SQL 7 Enterprise installation due to an access error on an ado file. Apparently SQL Server was trying to copy an active x component that was already in use when the error occured. Anyone have experience with this?
Server: Intel DK440LX Dual PII Dual SCSI UW
Server OS NT 4 SP4
I have a fresh install of MS SQL 2005 Developer Edition on my local box. I have just tried to install SP2 and the status reads "failure" for the product "Database Services", instance "MSSQLSERVER".
What could cause this? Do I need to turn of the service before applying the service pack? I supplied it the proper credentials which tested ok during the beginning of install...
Should I just try to install the patch again? How can I verify that the patch has been successfully applied?
Thanks for any help.
I am attempting to install SQL 2000 onto a new Win2K Advanced server and it fails. Event log shows event id:4097 with an exception error @ c0000005. Install progress achieves 99% and just hangs at that point. I cannot find anything relating to this issue, any ideas?
View 1 Replies View RelatedWhen I run SharePointRS.msi it ends and rolls back with a failure. Looking at the log i get the following:
copyappbincontents command completed successfully.
Adding Report Server feature to farm.
Install error: Failed to find the XML file at location '12TemplateFeaturesReportServerfeature.xml'
Uninstalling Report Server feature.
Uninstalling Report Server feature.
Report Server feature was uninstalled.
Stopping W3SVC service.
Removing Report Server web application files
Removed file d:InetpubwwwrootwssVirtualDirectories8088App_GlobalResourcesReportServer.resx.
Removed file d:InetpubwwwrootwssVirtualDirectories80App_GlobalResourcesReportServer.resx.
Removed file d:InetpubwwwrootwssVirtualDirectories8080App_GlobalResourcesReportServer.resx.
Removed file d:InetpubwwwrootwssVirtualDirectories36881App_GlobalResourcesReportServer.resx.
Removing DocIcon.xml file updates
Beginning uninstall of cab files.
Cab files uninstalled successfully.
Starting W3SVC service.
SSRSCustomActionError: Failed to find the XML file at location '12TemplateFeaturesReportServerfeature.xml'
Any ideas on how to fix this? I would have thought that the FeaturesReportServerfeature.xml file would be created by the installer.
I have tried redownloading and re running the installer.
This is running on SQL 2005 with SP2 and MOSS 2007 on the same box.
Thanks
Ashu
I have attempted to install SP1 on to my SQL 2005 Server numerous times and cannot get it to be successful. It failes on database services everytime and the log and event log report that my account cannot change permissions on the Data directory. My system is running Server 2003 R2 Ent x64. I have a Cluster setup with no second node at this time (future additon). I am also using a mount point inside the Data directory for logs. I have monitored the install using FileMon and do not see any file access issues during the installation process. I have also looked at the files and directories within the Data directory and all security ACLs seem fine. I am running the install with an account that has admin permission on the box. The service account I am using to run the sql service does not have admin permission but it is in the groups that SQL sets up at install time and those groups are assigned to the Data directory and other directories that the install configures. Any and all help us greatly appriciated!!
Kevin
I've been bulldozing thru a SQL Dev Ed Install. Now I am at the point that many services have been installed but overall the install failed. I do install from cmd prompt (command line). This is how I ran it:
Z:SQLSER~6Servers>start /wait setup.exe /qn USERNAME="Alex BB" COMPANYNAME="Alex BB" INSTALLSQLDIR="C:Program FilesMicrosoft Sql Server" INSTALLSQLDATADIR=INSTALLSQLDIRData ADDLOCAL=ALL INSTANCENAME=MSSQLSERVER SQLACCOUNT="DDMNVT61Alex BB" SQLPASSWORD="***somePW***" SQLACCOUNT="DDMNVT61Alex BB" SQLPASSWORD="***somePW***" AGTACCOUNT="DDMNVT61Alex BB" AGTPASSWORD="***somePW***" ASACCOUNT="DDMNVT61Alex BB" ASPASSWORD="***somePW***" RSACCOUNT="DDMNVT61Alex BB" RSPASSWORD="***somePW***" SQLBROWSERAUTOSTART=0 SQLAUTOSTART=0 AGTAUTOSTART=0 ASAUTOSTART=0 RSAUTOSTART=0 SECURITYMODE=SQL SAPWD="***somePW***"
This cmd line is actually a one after a small correction. The clause highlighed was put before ADDLOCAL=ALL. I assumed that cause the problem and changed the position of the clause but now when I tried to run the same command again I got an error that access was denied. This is the first time I got this error.
These are error messages from summary.txt of the run that I consider to be partially successful:
Machine : DDMNVT61
Product : SQL Server Database Services
Error : Could not access network location INSTALLSQLDIRData.
--------------------------------------------------------------------------------
Machine : DDMNVT61
Product : SQL Server Database Services
Error : Could not access network location INSTALLSQLDIRData.
--------------------------------------------------------------------------------
Machine : DDMNVT61
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_DDMNVT61_SQL.log
Last Action : CostFinalize
Error String : Could not access network location INSTALLSQLDIRData.
Error Number : 1606
---------------------------------------------------------------------------------
Machine : DDMNVT61
Product : Analysis Services
Error : SQL Server Setup could not validate the service accounts. Either the service accounts have not been provided for all of the services being installed, or the specified username or password is incorrect. For each service, specify a valid username, password, and domain, or specify a built-in system account.
--------------------------------------------------------------------------------
Machine : DDMNVT61
Product : Analysis Services
Error : SQL Server Setup could not validate the service accounts. Either the service accounts have not been provided for all of the services being installed, or the specified username or password is incorrect. For each service, specify a valid username, password, and domain, or specify a built-in system account.
--------------------------------------------------------------------------------
Machine : DDMNVT61
Product : Microsoft SQL Server 2005 Analysis Services
Product Version : 9.00.1399.06
Install : Failed
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_DDMNVT61_AS.log
Last Action : Validate_ServiceAccounts
Error String : SQL Server Setup could not validate the service accounts. Either the service accounts have not been provided for all of the services being installed, or the specified username or password is incorrect. For each service, specify a valid username, password, and domain, or specify a built-in system account.
The logon account cannot be validated for the service Analysis Services.
Error Number : 28075
When I checked the Program FilesMicrosoft Sql Server folder I saw no Sql instance MSSQLMSSQL.1 as I used to see in SqlExpress. therefore no DATA folder was created. Was it because I messed up the order of the clauses? If this is the case, then how shall I go about correcting the mishap? Now it seems the access is denied.
I can delete the registry keys and delete the folders again. I did it before while trying to get rid of SQL Express. The Browser (Management Studio) was corrupted and caused many problems.. Is this the way to go, to delete the registry keys?
Any comments will be appreciated.
Thanks.
Hi there,
I am trying to analyze log files from a failed install of Sql Server Dev. Ed. on 4/1/08. I have a Windows Installer Verbose Log Anlyzer for that.
The core log says in part:
Running: OpenPipeAction at: 2008/4/1 13:56:3
Complete: OpenPipeAction at: 2008/4/1 13:56:33, returned fals
Error: Action "OpenPipeAction" failed during execution
Running: CreatePipeAction at: 2008/4/1 13:56:3
Complete: CreatePipeAction at: 2008/4/1 13:56:33, returned fals
Error: Action "CreatePipeAction" failed during execution
Action "RunRemoteSetupAction" will be skipped due to the following restrictions:
Condition "Action: CreatePipeAction has finished and passed." returned false
I appears named pipes failed. My question is why?
From Core_log (Local) in part:
<Func Name='PerformDetections'
0
<EndFunc Name='PerformDetections' Return='0' GetLastError='0'
Error: Action "InvokeSqlSetupDllAction" threw an exception during execution
Failed to find feature:ADDLOCAL=ALL : 7000
Message displayed to use
The feature(s) specified are not valid for any SQL Server products
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DDMNVT61_.NET Framework 2.0.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code :
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DDMNVT61_.NET Framework 2.0 LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code :
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DDMNVT61_.NET Framework Upgrade Advisor.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code :
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DDMNVT61_.NET Framework Upgrade Advisor LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code :
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DDMNVT61_.NET Framework Windows Installer.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code :
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DDMNVT61_.NET Framework Windows Installer LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code :
Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result
Message pump returning: 7000
Message pump returning: 7000
There are other log files but I've decided to limit the "damage."
Thanks.
I have a package from SQL Server 2008 R2, that loads data from .xlsx file to database table.There are total 15 columns and 14000 rows in the .xlsx. The package runs fine in BIDS. But the same package in SQL Agent fails with error "omponent "Excel Source" (1)" failed validation and returned validation status "VS_ISBROKEN".
When I tried to run the package by deleting the half of the records for first 7000 rows it ran successfully in agent. Then the second half (last 7000 rows) also succeed from agent job. So, there is no issue with the data/datatypes.The agent job is able to run with record upyo 11000 rows in .xlsx. When I am running for 12000 rows it is failing.Is there any problem with the number of records in .xlsx or size through SQL Agent?
I am running the package from a Proxy account in sql agent job.
ERROR:
Error: Executed as user: PROXY_ID. Microsoft (R) SQL Server Execute Package Utility Version 10.50.6000.34 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 10:36:09 AM Error: 2015-08-10 10:36:10.87 Code: 0xC0202009 Source:
XX Connection manager "Excel Connection Manager 1"
[code]....
I am trying to install MSDE using settings I always have to install it:
setup sapwd=password instancename=vsdotnet disablenetworkprotocols=0 securitymode=sql
But it gets through the install, then the progress bar goes backwards and it uninstalled, I tried to enable logging and do /q+ but none of this gives usable information, i have redownloaded the MSDE SP3 install files and this has changed nothing, I know this is a common problem as I have seen a few sites mention it, but i can't seem to find the fix.
I am trying to apply MS SQL Server 2005 SP1 onto a 2 node cluster running Windows Server 2003, but it fails for SQL and the Analysis Services components of SQL Server, the error I am getting is MSP returned 1603 for both components. I have tried rebooting the machines but still get the same issue, the only additional dependency for SQL that I have added is for a 2nd physical disk. log details are below.
Many thanks in advance for any help you can provide on this problem.
01/15/2007 12:26:26.937 ================================================================================
01/15/2007 12:26:26.953 Hotfix package launched
01/15/2007 12:26:27.703 Product discovery successfully completed during the install process for MSSQLSERVER
01/15/2007 12:26:27.703 SP Level check successfully completed during the install process for MSSQLSERVER
01/15/2007 12:26:27.734 Product language check successfully completed during the install process for MSSQLSERVER
01/15/2007 12:26:27.750 Product version check successfully completed during the install process for MSSQLSERVER
01/15/2007 12:26:27.765 Command-line instance name check completed during the install process
01/15/2007 12:26:27.781 Baseline build check completed during the install process
01/15/2007 12:29:31.734 Attempting to install instance: MSSQLSERVER
01/15/2007 12:29:31.750 Enumerating passive cluster nodes
01/15/2007 12:29:31.765 Patching available passive node: GBCONV1A002N03
01/15/2007 12:29:31.781 Attempting to patch running passive node: GBCONV1A002N03
01/15/2007 12:29:31.796 Waiting for first successfully completed passive node
01/15/2007 12:29:31.812 Successfully created remote folder for product instance target \GBCONV1A002N03
01/15/2007 12:29:45.859 Successfully transferred payload to remote product instance target \GBCONV1A002N03
01/15/2007 12:29:45.921 Successfully transferred payload to remote product instance target \GBCONV1A002N03
01/15/2007 12:29:45.953 Successfully created new scheduled task for product instance target \GBCONV1A002N03
01/15/2007 12:29:46.562 Successfully saved new scheduled task for product instance target \GBCONV1A002N03
01/15/2007 12:29:46.625 Successfully created scheduled task for product instance target \GBCONV1A002N03
01/15/2007 12:29:46.640 Successfully started scheduled task for product instance target \GBCONV1A002N03
01/15/2007 12:29:46.656 Successfully started scheduled task for product instance target \GBCONV1A002N03
01/15/2007 12:30:28.671 Scheduled task for product instance target has completed
01/15/2007 12:30:28.687 Waiting for exit code from scheduled task for product instance target \GBCONV1A002N03
01/15/2007 12:30:33.718 Received exit code 0 from scheduled task for product instance target \GBCONV1A002N03
01/15/2007 12:30:33.734 Result code for scheduled task for product instance target has been received
01/15/2007 12:30:33.734 Removed scheduled task for product instance target \GBCONV1A002N03
01/15/2007 12:30:33.921 Successfully removed remote folder for product instance target \GBCONV1A002N03
01/15/2007 12:30:33.953 Remote process completed for product instance target
01/15/2007 12:30:33.968 Exit code for passive node: GBCONV1A002N03 = 0
01/15/2007 12:30:36.812 First successful passive node has been completed
01/15/2007 12:30:36.828 Attempting to install target: GBCONV1A002N01
01/15/2007 12:30:36.843 Attempting to check for locked files: sqlrun_as.msp
01/15/2007 12:30:36.890 Attempting to check for locked files: \GBCONV1A002N01d$bf7e520a98fb7a70c268b90HotFixASFilessqlrun_as.msp
01/15/2007 12:30:36.906 Creating MSP locked file check log at: C:WINDOWSHotfixOLAP9LogsOLAP9_Hotfix_KB913090_sqlrun_as.msp.out
01/15/2007 12:30:41.015 MSP returned 1603: A fatal error occurred during installation.
01/15/2007 12:30:41.140 Unable to check MSP file: \GBCONV1A002N01d$bf7e520a98fb7a70c268b90HotFixASFilessqlrun_as.msp
01/15/2007 12:30:41.156 The following exception occurred: Unable to install Windows Installer MSP file Date: 01/15/2007 12:30:41.156 File: depotsqlvaultsetupmainsetupsqlsesqlsedllcopyengine.cpp Line: 689
01/15/2007 12:30:41.187 Attempting to finalize cluster instance: MSSQLSERVER
01/15/2007 12:30:41.203 Waiting for all running passive nodes to complete their patch
01/15/2007 12:30:41.218 All running passive nodes have completed their patch
01/15/2007 12:30:41.234 Successfully finalized cluster instance: MSSQLSERVER
01/15/2007 12:30:41.234 Failed to install instance: MSSQLSERVER
01/15/2007 12:30:41.250
01/15/2007 12:30:41.281 Product Status Summary:
01/15/2007 12:30:41.296 Product: SQL Server Native Client (64-bit)
01/15/2007 12:30:41.312 SQL Server Native Client (64-bit) (RTM ) - Success
01/15/2007 12:30:41.312
01/15/2007 12:30:41.328 Product: Setup Support Files (64-bit)
01/15/2007 12:30:41.343 Setup Support Files (64-bit) (RTM ) - Success
01/15/2007 12:30:41.359
01/15/2007 12:30:41.375 Product: Database Services (64-bit)
01/15/2007 12:30:41.390 Database Services (64-bit) (SP1 2047 ENU GBCONV1A002V03) - Failure
01/15/2007 12:30:41.406 Analysis Services (64-bit) (RTM 1399 ENU GBCONV1A002V04) - Failure
01/15/2007 12:30:41.406
01/15/2007 12:30:41.421 Product: Integration Services (64-bit)
01/15/2007 12:30:41.437 Integration Services (64-bit) (SP1 2047 ENU) - Not Applied
01/15/2007 12:30:41.453
01/15/2007 12:30:41.468 Product: MSXML 6.0 Parser (64-bit)
01/15/2007 12:30:41.484 MSXML 6.0 Parser (64-bit) (RTM ) - Not Applied
01/15/2007 12:30:41.484
01/15/2007 12:30:41.515 Product: Backward Compatibility (64-bit)
01/15/2007 12:30:41.531 Backward Compatibility (64-bit) (RTM ) - Not Applied
01/15/2007 12:30:41.546
01/15/2007 12:30:41.546 Product: Microsoft SQL Server VSS Writer (64-bit)
01/15/2007 12:30:41.578 Microsoft SQL Server VSS Writer (64-bit) (RTM ) - Not Applied
01/15/2007 12:30:41.593
01/15/2007 12:48:34.562 Hotfix package closed
I seem to have gotten myself between a rock and a hard place. I have tried everything I know and am sending this post as a last resort before wiping my computer drive and re-installing everything. This would not be the end of the world. All the software on my computer is registered and legal and all that, but getting things set up again is not something I look forward to. Here's the situation .....
I have been trying out SQL Server 2005 Express on a test server and have worked out all kinds of good things, including working remotely, over our network, from my computer. We decided to get the full version (SQL Server 2005 Standard) before going any further so that I could have all the cool tools and stuff. We got the full version installed on a new server
and I have been working on it using SQL Server Management Studio Express to get things started. Yesterday I decided I was ready to start going thru the tutorials for SSIS and SSAS, so I uninstalled the Express version of Management Studio and all other segments of Express that were on my local computer, got out the Standard version CDs and installed the workgroups segment on my computer. After several false-starts (re having to load things like IIS and reload .NET framework and then restart the SQL Server installation) I thought I finally made it all the way thru. During this last time thru a message popped up about not enough virtual memory, but the installation continued - so I left it going. When the "finish" screen came up and I clicked "finish", I first went to Surface Config and set things up as I had them before, then tried going to Managment Studio, but it was not in the programs list. I went back to Config. Manager and tried to see if something just needed to be turned on, or whatever, and started getting application failure errors, with a message to look at the install log. In that log there is a message about installation failure due to memory shortage. I should not be getting this problem, as far as I can tell. My hard drive has 24 gigs free and I have 1 gig of ram. In any case, I tried un-installing (thru add/remove programs) and when I do I get a failure error there too. Finally, I tried running the install again, figuring - as I have experienced on other software - that sometimes the second time thru straightens things out. No such luck, and another try at un-install gave the same results. I realize I am being somewhat vague about the error messages. I can get them if I need to, but I thought I would just toss this situation out to you all first, since it may not matter exactly what the failure messages are! Any suggestions?
Thanks a billion!
I am a member of the Administrators group, and there is plenty of space in all hard drives, plus the temp directory is open for "everybody" to full-control it. Yet the Service Pack 2 database engine fails, all other components upgrade fine.
----------------------------------------------------------------------------------
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 3033
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29506
Error Description : MSP Error: 29506 SQL Server Setup failed to modify security permissions on file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData for user SYSTEM. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.
-
SQL Server 2005 Enterprise Edition X64 keeps failing during the install. Every single compnent installes EXCEPT the actual database engine. The only error message I get is that the server failed to install because of a fatal error. This happens when the installer is trying to set "internal parameters" on the database engine install phase.
I have tried uninstaling everything and even used the Windows Install Clean up tool to clean out bogus references after my 1st attempt to install the DB server, but nothing has helped. I hope someone has some ideas on how to proceed.
The server is a brand new Dell PowerEdge 1900 SC running 2 Quad Core Xeon 2.0 GHz processors, 8 GB of RAM and Windows Server 20003 RC2 X64 factory installed from Dell.
I attempted to post the verbose setup log in this post, but it was to long. I can email the text file or upload it to our web server and link it in here if some one wants to see it. It wasn't a whole lot of help to me.
When trying to install SQL 2005 as a failover cluster in a Windows 2003 64 bit SP 2 cluster, I receive the following error when trying to select the installation path after choosing to install as a failover cluster.
_________________________
TITLE: Microsoft SQL Server Setup
------------------------------
The drive specified cannot be used for program location. Program files must be installed on a valid local disk available on all cluster nodes. The valid values are
__________________________
There is a knowledge base artical that says this can be from not installing the software with an account with admin permissions on all the servers in the cluster with the 64 bit install, but the account I used is an admin on both servers.
The only thing that I can think is causing the problem is that it is setup to boot from our SAN and it is using one fabric. By default Microsoft Clustering doesnt like this, but we use the newest storeport driver and applied the registry key supplied in KB article 886569 to resolve this. I could not find any documentation showing that this would limit a SQL 2005 Failover Cluster from seeing the shared storage.
Any help would be greatly appreciated.
Below the Error Log Reported in SQL Agent (64 bit SQLServer 2008R2 Enterprise Edition Service pack 2 ,32Core CPU Numa Node and 64GB Ram
[298] SQLServer Error: 10054, TCP Provider: An existing connection was forcibly closed by the remote host. [SQLSTATE 08S01]
[298] SQLServer Error: 10054, Communication link failure [SQLSTATE 08S01]
[165] ODBC Error: 0, A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections.
For more information see SQL Server Books Online. [SQLSTATE 08001]
[382] Logon to server '(local)' failed (ConnUpdateStartExecutionDate)
I am getting an error when installing SP3a of MSDE. I get the error message "The instance name specified is invalid." This is the first SQL database installed, so there is no instance name. I have tried "default" and "MSSQLSERVER" as instance names without success.
your help is appreciated.
Hi we have a two node windows 2003 x64 cluster, each running a SQL 2005 instance. I've added a new node to the cluster and am now trying to set up a new instance of SQL 2005 on the new node (node c). During the install i am getting a failure just after the stage where you choose the features to install. I'm selecting SQL database engine with Failover Cluster. When i click next i get a message which states:
"The drive specified cannot be used for program location. Program Files must be installed on a valid local disk available on all cluster nodes. The valid values are"
I've read a number of articles about possible causes for this and i've checked all the suggested causes but none of these have made a difference. The cluster disk resource is healthy and can be failed between all nodes in the cluster. No errors are generated. I am using an account which has domain admin rights and I can access all admin shares on all nodes. Some of the articles i have referenced are here:
http://support.microsoft.com/kb/907261
http://support.microsoft.com/?kbid=913815
http://blogs.technet.com/mbaher/archive/2007/03/23/clustering-sql-2005-and-administrative-shares.aspx
I've tried uninstalling all components etc but still i can't get it to work. The next step is rebuilding the server completely so does anyone have any suggestions?
Any suggestions would be greatly appreciated.
Thanks
Chris
Hi,
While I installed on the active node I got the following error: A recently applied update, KB921896, failed to install
After that installation finished , but query the server version I get:
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
9.00.1399.06 RTM Standard Edition
On the Visual Studion Manager Help About I get 9.00.3042
Error logs are below. Can you please tell me how can I overcome this?
TIA.
I paste here the summary and the hotfix logs of the primary node.
There is also the Redist9_Hotfix_KB921896_SqlSupport.msi.log but it is too long to paste here.
summary.txt:
Time: 07/29/2007 02:46:28.253
KB Number: KB921896
Machine: DB1
OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
Cluster Installation: Yes
Log Location on Passive Nodes:
(DB1) C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfix
(DB2) C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfix
**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed
**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Setup Support Files ENU 9.1.2047 x86
Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x86 STANDARD
Integration Services ENU SP1 9.00.2047.00 x86 STANDARD
SQL Server Native Client ENU 9.00.2047.00 x86
Client Components ENU SP1 9.1.2047 x86 STANDARD
MSXML 6.0 Parser ENU 6.00.3883.8 x86
SQLXML4 ENU 9.00.2047.00 x86
Backward Compatibility ENU 8.05.1704 x86
Microsoft SQL Server VSS Writer ENU 9.00.2047.00 x86
**********************************************************************************
Products Disqualified & Reason
Product Reason
**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID
**********************************************************************************
Product Installation Status
Product : Setup Support Files
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlSupport.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File :
Error Number : 11009
Error Description : No passive nodes were successfully patched
----------------------------------------------------------------------------------
Product : Integration Services
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixDTS9_Hotfix_KB921896_sqlrun_dts.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : SQL Server Native Client
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Reboot Required
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_sqlncli.msi.log
Error Number : 3010
Error Description :
----------------------------------------------------------------------------------
Product : Client Components
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : MSXML 6.0 Parser
Product Version (Previous): 3883
Product Version (Final) : 6.10.1129.0
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_msxml6.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : SQLXML4
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_sqlxml4.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Backward Compatibility
Product Version (Previous): 1704
Product Version (Final) : 2004
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SQLServer2005_BC.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Microsoft SQL Server VSS Writer
Product Version (Previous): 2047
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlWriter.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
**********************************************************************************
Summary
No passive nodes were successfully patched
Exit Code Returned: 11009
hotfix log:
I paste here only part of the file were I think I see errors (because the post fails on complete logs)
07/29/2007 02:24:37.934 ================================================================================
07/29/2007 02:24:37.949 Hotfix package launched
07/29/2007 02:24:37.965 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
07/29/2007 02:24:37.965 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
07/29/2007 02:24:37.965 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
07/29/2007 02:24:37.965 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
07/29/2007 02:24:37.980 Local Computer:
07/29/2007 02:24:37.980 Target Details: DB1
07/29/2007 02:24:37.980 commonfilesdir = C:Program FilesCommon Files
07/29/2007 02:24:37.980 lcidsupportdir = f:33a341363e4f5937131539f11033
07/29/2007 02:24:37.980 programfilesdir = C:Program Files
07/29/2007 02:24:37.980 programfilesdir_wow = C:Program Files
07/29/2007 02:24:37.980 supportdir = f:33a341363e4f5937131539f1
07/29/2007 02:24:37.996 supportdirlocal = f:33a341363e4f5937131539f1
07/29/2007 02:24:37.996 windir = C:WINDOWS
07/29/2007 02:24:37.996 winsysdir = C:WINDOWSsystem32
07/29/2007 02:24:37.996 winsysdir_wow = C:WINDOWSSysWOW64
07/29/2007 02:24:37.996
07/29/2007 02:24:38.012 Enumerating applicable products for this patch
07/29/2007 02:24:38.027 Found Redist 2005 product definition
07/29/2007 02:24:38.121 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
07/29/2007 02:24:38.121 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
07/29/2007 02:24:38.121 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
07/29/2007 02:24:38.121 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
07/29/2007 02:24:40.105 Found Redist 2005 product definition
07/29/2007 02:24:40.137 Found Redist 2005 product definition
07/29/2007 02:24:40.152 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
07/29/2007 02:24:40.152 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
07/29/2007 02:24:40.152 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
07/29/2007 02:24:40.152 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
07/29/2007 02:24:56.168 Found SQL 2005 product definition
07/29/2007 02:25:00.293 Enumeration: Determining QFE level for product instance MSSQLSERVER
07/29/2007 02:25:00.309 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLServr.exe
07/29/2007 02:25:00.309 Enumeration: Found following QFE level for product instance MSSQLSERVER: 1399
...
07/29/2007 02:30:06.090 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnsqlagent90.exe (SQLSERVERAGENT [SQLAGENT90.EXE] - 3284)
07/29/2007 02:30:06.387 Locked file: C:Program Filesmicrosoft sql server90sharedsqlbrowser.exe (SQLBrowser [sqlbrowser.exe] - 1480)
07/29/2007 02:30:58.137 Attempting to pause the 32 bit ngen queue
07/29/2007 02:30:58.902 Installing product: Redist9
07/29/2007 02:30:58.918 Installing instance: Setup Support Files
07/29/2007 02:30:58.934 Installing target: DB1
07/29/2007 02:30:58.934 Installing file: SqlSupport.msi
07/29/2007 02:30:59.027 Copy Engine: Creating MSI install log file at: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlSupport.msi.log
07/29/2007 02:30:59.027 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
07/29/2007 02:30:59.027 Registry: Cannot read registry key value "Debug"
07/29/2007 02:31:29.730 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
07/29/2007 02:31:29.746 Registry: Cannot read registry key value "Debug"
07/29/2007 02:31:29.762 Copy Engine: Installed file: C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi
07/29/2007 02:31:29.762 Installed target: DB1
07/29/2007 02:31:30.027 Installed instance: Setup Support Files
07/29/2007 02:31:30.043 Installed product: Redist9
07/29/2007 02:31:30.043 Installing product: SQL9
07/29/2007 02:31:30.043 Installing instance: MSSQLSERVER
07/29/2007 02:31:30.059 Enumerating passive cluster nodes
07/29/2007 02:31:30.574 Patching available passive node: DB2
07/29/2007 02:31:30.574 Patching passive node: DB2
07/29/2007 02:31:30.590 Waiting for first completed passive node
07/29/2007 02:31:30.934 Task Scheduler: Created remote folder for product instance target \DB2
07/29/2007 02:31:49.387 Task Scheduler: Transferred payload to remote product instance target \DB2
07/29/2007 02:31:49.402 Task Scheduler: Transferred payload to remote product instance target \DB2
07/29/2007 02:31:49.574 Task Scheduler: Error, cannot create scheduled task for product instance target \DB2
07/29/2007 02:31:50.449 Task Scheduler: Removed remote folder for product instance target \DB2
07/29/2007 02:31:50.449 Error, remote process failed for product instance target
07/29/2007 02:31:50.449 Exit code for passive node: DB2 = 1603
07/29/2007 02:31:50.590 The following exception occurred: No passive nodes were successfully patched Date: 07/29/2007 02:31:50.590 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllinstance.cpp Line: 3422
07/29/2007 02:31:51.449 Watson: Param1 = Unknown
07/29/2007 02:31:51.465 Watson: Param2 = 0x2b01
07/29/2007 02:31:51.465 Watson: Param3 = Unknown
07/29/2007 02:31:51.465 Watson: Param4 = 0x0
07/29/2007 02:31:51.465 Watson: Param5 = instance.cpp@3422
07/29/2007 02:31:51.465 Watson: Param6 = Unknown
07/29/2007 02:31:51.480 Watson: Param7 = SQL9
07/29/2007 02:31:51.480 Watson: Param8 = Hotfix@
07/29/2007 02:31:51.480 Watson: Param9 = x86
07/29/2007 02:31:51.480 Watson: Param10 = 3042
07/29/2007 02:31:51.480 Installed product: SQL9
07/29/2007 02:31:51.480 Installing product: DTS9
07/29/2007 02:31:51.496 Installing instance: Integration Services
07/29/2007 02:31:51.496 Installing target: DB1
07/29/2007 02:31:51.512 Installing file: sqlrun_dts.msp
07/29/2007 02:31:51.512 Copy Engine: Creating MSP install log file at: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixDTS9_Hotfix_KB921896_sqlrun_dts.msp.log
...
I have an xp dev machine i use which has sql server 2005. I skipped installin sp1 on sql server and went to sp2 directly. I tried over and over again but getting following errors. Not sure how to fix it.
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29528
Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Installing Local Groups. The error is: A member could not be added to or removed from the local group because the member does not exist.
----------------------------------------------------------------------------------
Product : Analysis Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixOLAP9_Hotfix_KB921896_sqlrun_as.msp.log
Error Number : 29528
Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Installing Local Groups. The error is: A member could not be added to or removed from the local group because the member does not exist.
----------------------------------------------------------------------------------
Product : Reporting Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRS9_Hotfix_KB921896_sqlrun_rs.msp.log
Error Number : 29528
Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Installing Local Groups. The error is: A member could not be added to or removed from the local group because the member does not exist.
After going into detailed log file i noticed this account its trying to use,
MSI (s) (A8!54) [17:13:45:891]: PROPERTY CHANGE: Adding SQLBROWSERACCOUNT property. Its value is 'PHXNT1ADMINISTRATOR'.
MSI (s) (A8!54) [17:13:45:907]: PROPERTY CHANGE: Adding AGTACCOUNT property. Its value is 'PHXNT1ADMINISTRATOR'.
Restored account SQLBROWSERACCOUNT=PHXNT1ADMINISTRATOR
MSI (s) (A8!54) [17:13:45:907]: PROPERTY CHANGE: Adding SQLACCOUNT property. Its value is 'NT AUTHORITYSYSTEM'.
Restored account AGTACCOUNT=PHXNT1ADMINISTRATOR
MSI (s) (A8!84) [17:13:48:109]: PROPERTY CHANGE: Adding Rollback_sqlGroupMember.D20239D7_E87C_40C9_9837_E70B8D4882C2 property. Its value is '100Installing Local Groups50000SQLServer2005SQLBrowserUser$PHOENIXDEV2PHXNT1ADMINISTRATOR'.
MSI (s) (A8!84) [17:13:48:343]: PROPERTY CHANGE: Adding Do_sqlGroupMember.D20239D7_E87C_40C9_9837_E70B8D4882C2 property. Its value is '110Installing Local Groups50000SQLServer2005SQLBrowserUser$PHOENIXDEV2PHXNT1ADMINISTRATOR'.
my domain was upgraded from nt to 2003 long time ago from phxnt1 to phxad1 which i dont know why it still try's to use the old account. The old domain is still online would this cause this problem not sure.