Will Work For Help SQL 2k5 SP1 Installation Issue (log Attached)

May 24, 2006

The upgrade to SQL 2k5 SP1 fails to upgraede the Database Services. Attached is the log. Will work for help.



05/24/2006 16:19:47.500 ================================================================================
05/24/2006 16:19:47.500 Hotfix package launched
05/24/2006 16:19:53.687 Product discovery successfully completed during the install process for MSSQLSERVER
05/24/2006 16:19:53.687 SP Level check successfully completed during the install process for MSSQLSERVER
05/24/2006 16:19:53.687 Product language check successfully completed during the install process for MSSQLSERVER
05/24/2006 16:19:53.687 Product version check successfully completed during the install process for MSSQLSERVER
05/24/2006 16:19:53.687 Command-line instance name check completed during the install process
05/24/2006 16:19:53.687 Baseline build check completed during the install process
05/24/2006 17:08:03.187 Attempting to install instance: MSSQLSERVER
05/24/2006 17:08:03.281 Attempting to install target: TERRANCE
05/24/2006 17:08:03.375 Attempting to stop service: SQLSERVERAGENT
05/24/2006 17:08:11.093 Successfully stopped service: SQLSERVERAGENT
05/24/2006 17:08:11.109 Attempting to stop service: MSSQLServer
05/24/2006 17:08:18.625 Successfully stopped service: MSSQLServer
05/24/2006 17:08:19.031 Attempting to check for locked files: sqlrun_sql.msp
05/24/2006 17:08:21.390 Attempting to check for locked files: \TERRANCEe$6d48928b5baeb824319ba523e3fdHotFixSQLFilessqlrun_sql.msp
05/24/2006 17:08:21.406 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.out
05/24/2006 17:09:22.343 MSP returned 1602: The user cancels installation.
05/24/2006 17:09:22.375 Successfully checked file: \TERRANCEe$6d48928b5baeb824319ba523e3fdHotFixSQLFilessqlrun_sql.msp
05/24/2006 17:09:22.468 Successfully opened registry key: SystemCurrentControlSetControlSession Manager
05/24/2006 17:09:22.468 Failed to read registry key: PendingFileRenameOperations
05/24/2006 17:09:22.484 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll
05/24/2006 17:09:22.484 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll
05/24/2006 17:09:22.484 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll
05/24/2006 17:09:22.484 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
ls400.dll
05/24/2006 17:09:22.484 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
lhtml.dll
05/24/2006 17:09:22.500 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsir5jp.dll
05/24/2006 17:09:22.500 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftesql.exe
05/24/2006 17:09:22.500 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftepxy.dll
05/24/2006 17:09:22.500 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftefd.exe
05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsfte.dll
05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnLangWrbk.dll
05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnkorwbrkr.dll
05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinninfosoft.dll
05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERefFTERef.dll
05/24/2006 17:09:22.515 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnCHTBRKR.DLL
05/24/2006 17:09:22.531 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnChsBrkr.dll
05/24/2006 17:09:22.531 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMResources1033REPLRES.rll
05/24/2006 17:09:22.531 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
eplrec.dll
05/24/2006 17:09:22.531 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
plisapi.dll
05/24/2006 17:09:22.531 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:WINDOWSassemblyGAC_32Microsoft.SqlServer.Replication9.0.242.0__89845dcd8080cc91Repl.dll
05/24/2006 17:09:22.531 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DataStorage9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataStorage.dll
05/24/2006 17:09:22.531 Failed to read version information for the following file: C:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources10332005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
plhtfin.sql
05/24/2006 17:09:22.531 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
C:Program FilesMicrosoft SQL Server90COMqrdrsvc.exe
05/24/2006 17:09:22.546 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMsnapshot.exe
05/24/2006 17:09:22.546 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
eplmerg.exe
05/24/2006 17:09:22.546 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90COM ablediff.exe
05/24/2006 17:09:22.546 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMDISTRIB.exe
05/24/2006 17:09:22.609 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnDatabaseMail90.exe
05/24/2006 17:09:22.609 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources30822005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources2052sqlevn70.rll
05/24/2006 17:09:22.609 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10422005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1041sqlevn70.rll
05/24/2006 17:09:22.609 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10402005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1036sqlevn70.rll
05/24/2006 17:09:22.625 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10332005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1031sqlevn70.rll
05/24/2006 17:09:22.625 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10282005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033XPStar90.RLL
05/24/2006 17:09:22.625 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
05/24/2006 17:09:22.625 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
05/24/2006 17:09:22.625 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
05/24/2006 17:09:22.625 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn6.6.3.5
C:Program FilesMicrosoft SQL Server90Sharedmsxmlsql.dll
05/24/2006 17:09:22.640 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2.0.3609.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlrw.dll
05/24/2006 17:09:22.640 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
05/24/2006 17:09:22.640 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
05/24/2006 17:09:22.640 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
05/24/2006 17:09:22.640 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLBOOT.dll
05/24/2006 17:09:22.640 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxplog70.dll
05/24/2006 17:09:22.640 Failed to read version information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnatchp~1.dll
05/24/2006 17:09:22.640 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
05/24/2006 17:09:22.656 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
05/24/2006 17:09:22.671 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
05/24/2006 17:09:22.687 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
05/24/2006 17:09:22.703 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
05/24/2006 17:09:22.703 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
05/24/2006 17:09:22.718 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
05/24/2006 17:09:22.718 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90SharedResources10339.0.2047.0
C:Program FilesMicrosoft SQL Server90Sharedmsmdrdir.dll
05/24/2006 17:09:22.734 Failed to read version information for the following file: C:Program FilesCommon FilesSystemole db2.0.3609.0
C:Program FilesCommon FilesSystemole dbxmlrw.dll
05/24/2006 17:09:22.750 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
05/24/2006 17:09:22.750 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
05/24/2006 17:09:22.765 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
05/24/2006 17:09:22.781 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
05/24/2006 17:09:22.781 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
05/24/2006 17:09:22.796 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
05/24/2006 17:09:22.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
05/24/2006 17:09:22.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
05/24/2006 17:09:22.828 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
05/24/2006 17:09:22.859 Failed to read version information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90enMicrosoft.AnalysisServices.AdomdClient.xml
05/24/2006 17:09:22.875 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90Microsoft.AnalysisServices.AdomdClient.dll
05/24/2006 17:09:22.875 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll
05/24/2006 17:09:22.875 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033
E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033sqlcm.xml
05/24/2006 17:09:22.890 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
05/24/2006 17:09:22.890 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
05/24/2006 17:09:22.906 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
05/24/2006 17:09:22.906 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
05/24/2006 17:09:22.921 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
05/24/2006 17:09:22.937 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
05/24/2006 17:09:22.953 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
05/24/2006 17:09:22.953 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
05/24/2006 17:09:22.968 Failed to read associated hotfix build information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
05/24/2006 17:09:22.968 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinnResources10332005.90.2047.0
E:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL
05/24/2006 17:09:22.984 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinn2.0.3609.0
E:Program FilesMicrosoft SQL Server90ToolsBinnSQLdiag.exe
05/24/2006 17:09:22.984 Failed to read version information for the following file: E:Program FilesMicrosoft SQL Server90ToolsBinn2005.90.2047.0
C:Program FilesMicrosoft SQL Server90Sharedsqlsvc~1.dll
05/24/2006 17:09:22.984 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
05/24/2006 17:09:23.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
05/24/2006 17:09:23.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
05/24/2006 17:09:23.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
05/24/2006 17:09:23.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
05/24/2006 17:09:23.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
05/24/2006 17:09:23.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
05/24/2006 17:09:23.031 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared2005.90.2047.0
C:Program FilesMicrosoft SQL Server90Sharedsqlsqm.exe
05/24/2006 17:09:23.031 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared9.0.2047.0
C:Program FilesMicrosoft SQL Server90Shareddbghelp.dll
05/24/2006 17:09:23.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Rmo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Rmo.dll
05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.DLL
05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.DataWarehouse.Interfaces9.0.242.0__89845dcd8080cc91Microsoft.DataWarehouse.Interfaces.DLL
05/24/2006 17:09:23.046 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.RegSvrEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.RegSvrEnum.dll
05/24/2006 17:09:23.062 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
05/24/2006 17:09:23.062 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
05/24/2006 17:09:23.062 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
05/24/2006 17:09:23.062 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ServiceBrokerEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ServiceBrokerEnum.dll
05/24/2006 17:09:23.062 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.WmiEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WmiEnum.dll
05/24/2006 17:09:23.078 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SqlEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SqlEnum.dll
05/24/2006 17:09:23.078 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SmoEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SmoEnum.dll
05/24/2006 17:09:23.078 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Smo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Smo.dll
05/24/2006 17:09:23.078 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlSAC.exe
05/24/2006 17:09:23.078 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedMicrosoft.SqlSac.Public.dll
05/24/2006 17:09:57.218 Attempting to install file: sqlrun_sql.msp
05/24/2006 17:09:57.609 Attempting to install file: \TERRANCEe$6d48928b5baeb824319ba523e3fdHotFixSQLFilessqlrun_sql.msp
05/24/2006 17:09:57.609 Creating MSP install log file at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.log
05/24/2006 17:09:57.609 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
05/24/2006 17:09:57.609 Failed to read registry key: Debug
05/24/2006 17:15:25.375 MSP returned 1603: A fatal error occurred during installation.
05/24/2006 17:15:25.390 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
05/24/2006 17:15:25.406 Failed to read registry key: Debug
05/24/2006 17:15:25.593 Unable to install MSP file: \TERRANCEe$6d48928b5baeb824319ba523e3fdHotFixSQLFilessqlrun_sql.msp
05/24/2006 17:15:25.593 The following exception occurred: Unable to install Windows Installer MSP file Date: 05/24/2006 17:15:25.593 File: depotsqlvaultsetupmainsetupsqlsesqlsedllcopyengine.cpp Line: 856
05/24/2006 17:15:25.937
05/24/2006 17:15:25.937 Product Status Summary:
05/24/2006 17:15:25.937 Product: SQL Server Native Client
05/24/2006 17:15:25.953 SQL Server Native Client (RTM ) - Success
05/24/2006 17:15:25.953
05/24/2006 17:15:25.953 Product: Setup Support Files
05/24/2006 17:15:25.953 Setup Support Files (RTM ) - Success
05/24/2006 17:15:25.953
05/24/2006 17:15:25.953 Product: Database Services
05/24/2006 17:15:25.953 Database Services (RTM 1399 ENU) - Failure
05/24/2006 17:15:25.953 Details: Unable to install Windows Installer MSP file
05/24/2006 17:15:25.953 Analysis Services (SP1 2047 ENU) - Not Applied
05/24/2006 17:15:25.953 Reporting Services (SP1 2047 ENU) - Not Applied
05/24/2006 17:15:25.953
05/24/2006 17:15:25.953 Product: Notification Services
05/24/2006 17:15:25.953 Notification Services (SP1 2047 ENU) - Not Applied
05/24/2006 17:15:25.953
05/24/2006 17:15:25.953 Product: Integration Services
05/24/2006 17:15:25.953 Integration Services (SP1 2047 ENU) - Not Applied
05/24/2006 17:15:25.968
05/24/2006 17:15:25.968 Product: Client Components
05/24/2006 17:15:25.968 Client Components (SP1 2047 ENU) - Not Applied
05/24/2006 17:15:25.968
05/24/2006 17:15:25.968 Product: MSXML 6.0 Parser
05/24/2006 17:15:25.968 MSXML 6.0 Parser (RTM ) - Not Applied
05/24/2006 17:15:25.968
05/24/2006 17:15:25.968 Product: SQLXML4
05/24/2006 17:15:25.968 SQLXML4 (RTM ) - Not Applied
05/24/2006 17:15:25.968
05/24/2006 17:15:25.968 Product: Backward Compatibility
05/24/2006 17:15:25.968 Backward Compatibility (RTM ) - Not Applied
05/24/2006 17:15:25.968
05/24/2006 17:15:25.968 Product: Microsoft SQL Server VSS Writer
05/24/2006 17:15:25.968 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/24/2006 17:15:25.984

View 12 Replies


ADVERTISEMENT

SQL 2000 Installation Problems On XP- Just Wont Work!

Jun 1, 2004

Ive got some problems that are causing me a major headache. I am running windows XP Pro and i have the SQL Server 2000 Enterprise Edition Evaluation cd but when i auto-run to install it the installation wizard just wont come up.
If i try to run it a second time it says another instance of setup is already running, but nothing ever happens. Can anybody tell me why this is?? My work has been stalled for days trying to figure this out. Thanks.

View 1 Replies View Related

Out Of The Box Installation Doesn't Work, Runs Me In Circles...

Dec 20, 2007

A fresh install on Windows Server 2003 of SQL Server 2005 & Reporting Services...

In Reporting Services Configuration Manager...

Under Web Service Identity I have a red X (bad)...

ASP.NET Service Account is grey, can't enter anything there. Isn't is always ASP.NET?

Says: Specify the application pool in which to run the Report Server Web Service.

So I set this to the default app pool for both Report Server and Report Manager. I get an error "There was an error setting the identity for the report service. Click tell me more, get:

ReportServicesConfigUI.WMIProvider.WMIProviderException: A virtual directory must first be created before performing this operation.

at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)

Okay no problem... Goto the Report Service Virtual Directory task. I have Name and WebSite. Can't enter anything in either text box. Click NEW only choice is Report Server, Default web site. Say OK, it tells me that the virtual directory already exists. Fine, click Apply Default Settings. I get:

System.Runtime.InteropServices.COMException (0x80004005)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ResetVirtualDirectoryMappings()

And the HELP button is disabled, GREAT!!

Again, this is a FRESH install on a NEW Server, FRESH O/S, FRESH SQL Server.

So I'm caught in a "Catch-22" I can't set the Web Service Identity because it doesn't think I have a virtual directory, but I can't create the virtual directory because it crashes. First time in a long time a Microsoft Product didn't work in default installation mode -- and made me look real silly after telling the client how simple and easy SQL Server Reporting services were to use and now can't make it run at all.

*Help* I'm sure the answer is an easy one.

View 5 Replies View Related

SQL Server 2005 Installation Vista (+SP2), No Services, Doesnt Work

Nov 16, 2007



While installing SQL Server 2005 Enterprise Edition on Windows Vista Ultimate
the setup alerts me "there are known compatibility problems, please
install SP2 after this". So ok, all went nice and installed without error.
IIS 7 installed fully, so all green in setup display.
(But after installation i do not see any service which begins with SQL***...)
At the end, the setup wanted to start the administration Tool.
Ok, but my name was not listed, so i could not add me to the permitted users.
I can not use any tool, because i have no rights.

Some Ideas?

Microsoft SQL Server Management Studio 9.00.3042.00
Microsoft Analysis Services-Clienttools 2005.090.3042.00
Microsoft Data Access Components (MDAC) 6.0.6000.16386 (vista_rtm.061101-2205)
Microsoft MSXML 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 7.0.6000.16546
Microsoft .NET Framework 2.0.50727.312
Betriebssystem 6.0.6000


thanks Frank

View 6 Replies View Related

Business Intelligence Development Studio Installation Doesn't Work

Jan 31, 2007

Hello,

I have just tried to install (among other things) BIDS, and have found it hasn't worked. I tried it once over an old SQL Server 2005 Express Edition installation, and that failed, so I followed the advice of others and removed it. In fact I removed everything I could find to do with SQL Server 2005, and started right from the beginning (restarted after removing everything). My steps were:

1) Install SQL Express with Advanced Services (SQLEXPR_ADV.EXE, 240 MB, downloaded today from http://msdn.microsoft.com/vstudio/express/sql/download/). Choose to install all components, with default options. Restart when complete.

2) Install SQL Express Tools (SQLEXPR_TOOLKIT.EXE, 218 MB, dowloaded today from http://msdn.microsoft.com/vstudio/express/sql/download/). Choose only to install BIDS (one of four components).

When it was all over, I tried to fire up BIDS via the start menu (All Programs / Microsoft SQL Server 2005 / SQL Server Business Intelligence Development Studio), and got an error to say the shortcut to "devenv.exe" couldn't be found. Sure enough, it isn't where it should be - in fact it is not there at all.

As a note, I observed that when I went to install BIDS as per step 2 above, the installer made some claims about it already being installed, and that it would perform an upgrade...??

Something is not right here... By the way, I have installed BIDS on another machine some months ago, with no problems. Probably an older version at the time...

Hope someone can help.

Nick

View 3 Replies View Related

Using Mdf Not Attached To SQL Server

Aug 31, 2006

Hi.  I am using VS 2005 and I want to create a database file (mdf) and have it on my server, but not have it attach to an instance of SQL server.  Is this possible? The hosting I am using only allows for 1 SQL DB, and obviously doesn't allow you to attach instances of a DB.  I would rather go with an mdf file that access, but not sure if this is possible. If anyone knows if it is and how to pull it off it would be GREAT!! 

View 7 Replies View Related

Attached Database

Mar 1, 2006

how can i attached MDF file only without .log and data only

View 6 Replies View Related

Attached In Vb8 Vs Vb6 Incompatability

Oct 10, 2006

I have two programs which access sql server 2005. One was written in vb6 the other in vb8 (aka vb.net 2005).

vb6 works well with this connection string:

Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Database=MyDbName;Data Source=.MyServerInstanceName

vb8 (in vs2005) generated the following connection string which works well in the vb8 application:

Data Source=.MyServerInstanceName;AttachDbFilename='C:MyDbPathMyDbName.mdf';Integrated Security=True

Within their own programs each connection string works well. However, if I use one program and then the other (e.g., vb8 program then vb6), I get an error message:

Unable to open the physical file "C:MyDbPathMyDbName.mdf". Operating system error 32: "32(The process cannot acces the file because it is being used by another process.)".

If I detach the database using SSMS, I can then access it with the other program. Obviously, this is not an ideal situation and not something I would want the end user to have to do.

Also, when using the vb6 connection string, SSMS lists the database in Object Explorer as: MyDbName. When using the vb8, the database is listed as C:MyDbPathMyDbName.mdf. BTW, the database is set for multi-user.

How can I get the two programs to place nice together?

View 12 Replies View Related

Backingng Up A Database That Is Attached

Jan 10, 2006

Hi,
I was trying to figure out how to back up a database that has been attached to the SQL Express instance. I found on the web this tutorial and tried to use it, however it seems like it cannot find the database. The DB is attached by the web application using AttachDbFilename in the connectionstring.
http://www.sqldbatips.com/showarticle.asp?ID=27
Any ideas?
thanks

View 5 Replies View Related

Attached Db Successful In QA But Not Showing In EM

Nov 13, 2001

I used Query Analyser to De-tach a SQL 7 database and that worked fine. The database became 'invisible' in Enterprise Manager and the entry was removed from the sysdatabases in Master. The mdf and ldf file remain in the file system. However, when I ran the sp to Attach the database QA said successful but it does not show in Enterprise Manager or in sysdatabases in Master. I'm going to run through the procedure again and if problems I'll check the logs but has anyone else had difficulty with this. Also with attaching the db to a SQL2000 install I believe the logins on the SQL7 install are not brought over. In my case, the client is using trusted logins with their database application so their is probably not a lot to manually recreate on the SQL 2000 install but doees anyone have nay sample code/script that can give me an idea of what is required in the area of getting logins out of the Master of SQL7 and into SQL2000.

Great forum...

Have a great day,

ChrisE

View 3 Replies View Related

Re-attached DB Lost Users

Aug 10, 2005

If you re-attach a db to a different server, presumably you are shutting out your users (by them not having logins to the new server). If you are moving to a different domain I can only think that having the sa pwd and switching to "Mixed Authentication" would be the only way to get back in to start adding new logins/users, is that correct?

View 2 Replies View Related

List Attached Databases?

Mar 12, 2007

Is there a stored procedure to list attached databases?
You can do this:
use Master
exec sp_helpfile
go

Which shows you the config files for the current DB.
What if you want to do a multiple sp_detach_db? If you could get a list of the attached DB's you could recursilvely or conditioinaly detach.

View 4 Replies View Related

Attached Vs Detached Database

Nov 11, 2007

Hello all,
I'm using SQL 2005 Express edition. I'm currently connecting to the database file directrly (from ASP.NET) and that db file is not attached to the server.
My question is this:
What is the difference ? Will the performance improve if the db is attached and I connect to it throught the server ? I'm really not sure what the difference is.
Thanks

View 5 Replies View Related

List Of Attached Databases

Feb 7, 2006

How can I, programatically, get a list of attached databases? I'm using VB.

View 4 Replies View Related

Getting All Users Attached To A Database

May 25, 2008

Hey!

I need help getting all the users that are "attached" or "allowed" to access a given database and their login information. I do not know if this is even possible but I had tried to do my own research and cant figure it out/find any info on it. Any help is greatly appreciated!

Thank you!
-Teenprogrammer

View 4 Replies View Related

Can You See Auto Attached DB's In Management Studio As Well?

Jul 13, 2006

When you have SQL Server Express installed, and you drop a database in App_Code it will be attached and you can browse it with Server Explorer in Visual Studio. Same when you choose Website -> ASP.NET Configuration, you get a new ASPNETDB database in App_Code and it will be attached.My question: is it normal behaviour that I cannot see these databases in the Object Browser in SQL Server Management Studio?For the record: I also have SQL Server 2005 Dev installed, so the Management Studio I have is not the Express edition.

View 4 Replies View Related

Export To Cvs/excel With Comments Attached

Sep 20, 2006

i'm building a web page to help our support staff run and export their sql queries faster and more easily than going through the sql server manager.  i found an article at codeproject [1] that i was able to customize to be more flexible, but i'm not sure how to get it to export the results of a query along with the comments that preceed the query.

for example, i have the following sql file: -- this query does a certain thing, and the comment can be pretty long at times, depending on how complicated the query is
select * from table where columnid > 100would anyone be able to tell me how to edit Kolluri's export function to allow for a comment section?  alternatively if his way of doing an export is out of date, i'd be interested in a newer way.  most importantly, though, i need to be able to export the comments along with query results.my ultimate goal is to have a drop down list of databases on the server, a list of query files (from a certain consolodated folder) for them to run on the chosen database, a "test query" function, and an export function that exports the comments and results.[1] http://www.codeproject.com/aspnet/ExportClassLibrary.asp 

View 1 Replies View Related

Retrieving Data From An Attached Mdf File

Apr 13, 2007

I attach my SQL Server Express data file to my host. I would like to copy all of my member information back to my local computer. How can I do this? My host won't allow my to physically copy the data file over.  My host is discountasp.net.   Thanks,Jeff

View 1 Replies View Related

Persistent Autoincrementing Value, Not Attached To Row Insertion?

Oct 19, 2004

I need to get a unique value to use for a record *before* the record is added to a table. It doesn't have to be contiguous with existing records, but it must always be unique, has to be persistent over multiple instantiations of an ASP.NET application, and has to work in that sort of a multi-session environment (where other sessions could need additional unique values before the first session gets around to actually adding a record to the table).

I considered generating and using unique CLSIDs for this, but the resulting value also needs to become part of the filename of some files that are being saved to the disk (and those names also saved in the table), and including text CLSIDs along with other filename data would make for some unpleasantly long and difficult to work with filenames.

I also don't think there's a practical way for me to use a trigger associated with an identity column for this, because I need to save files to disk using the unique value before I even know if the record will in fact end up being added to the table, and what's more, the numbers and names of those files will vary in ways that might be difficult to handle in a stored procedure.

What I'm thinking I will have to do is create a separate database table called something like "UniqueIDGen". This table would have a single record in it with a single integer value, initialized to a value of 1. Then, each time an ID is needed, this one record would be locked, read and incremented by 1. The only reason for doing it this way instead of with an application variable, as I see it, is that the values need to be unique and continue incrementing in perpetuity, no matter how many times the ASP.NET application is recycled or the server is rebooted.

But I still have to wonder if there might be a more efficient method provided by SQL Server for this type of unique value generation ... something that is equally as persistent without requiring an entire table with only a single record to be allocated to such a basic task. Does anyone know of a more elegant solution for this?

View 6 Replies View Related

Attached .mdf File Security Settings

Dec 4, 2005

I'm having some problems with SQL Server 2005. I installed the Personal Starter kit but don't have the Express edition installed so I attached the .mdf file to SQL Server 2005. That's ok and I also changed the connection string to integrated security.<add name="Personal" connectionString="Data Source=MyTestServer;Initial Catalog=Personal;Integrated Security=True" providerName="System.Data.SqlClient"/>I tried setting the security settings in the Management studio under Security | Logins | BUILTINAdministrators where I select the User mapping and check the checkbox before the Personal.mdf file. But this doesn't seem to do the trick. How can I set the correct security settings?

View 2 Replies View Related

SQL Server Crashed, DB Files Attached But ..

Dec 29, 2005

Hi, paws.
My server crashed recently, I didn't give to much importance because I knew that having access to the partitions I could recover my DB files and attach my database to my new server, and everything was fine until ... I found that my DTS Packages and Jobs where not in my Attached DB.
Now, where can I find these ?
Can you help a tormented man ?
Thanks in advance.

Francisco J

View 4 Replies View Related

Attached Database Showing Read-only

Feb 27, 2008

I attached my database to SQL 2005 but it's showing up as read-only for some reason. I've attached this before just fine in another instance of the Vista OS. Why would it attach differently this time compared to all other times and show read only?

The .mdb and .ldf files are not read only if you right-click and check out their properties.

View 12 Replies View Related

Attached A .mdb Not Created By My Sql Server 2005

May 21, 2008

I attached .mdf and .ldf from the app_data folder in an asp.net web site. I set the configuration to SSPI. The trouble is, I get this error
requested by the login. The login failed.
Login failed for user 'IN-XYZmattaniah'.


If I create a database and connect to it using SSPI I do not get this error. I assume there is something I am missing.

View 4 Replies View Related

SQL Server DB As Service Or Attached File ?

Apr 2, 2007

Hello,

I was wondering about the principles of SQL Server. In all of my books, they show me to attach the DB, even create the DB through Visual Studio 2005. Which creates a .mdf file and a .ldf file.



Ok, but I cannot open those files through SQL Server Management. The only DB I am able to manage through SQL Server Management is the ones created with it.



So my question is: For a Multi-User type Application, is there a problem to attach a network based file through VS2005, the same way as an access file ?



Again my keyword here is Multi-User. Sorry if this myth be a stupid question but I am used to MSAccess. SQL Server is a lot more complexe and I don't want to start in the wrong direction.



Thank you for your response.

View 5 Replies View Related

Detached Vs Attached Database Files

Nov 11, 2007

Hello all,
I'm using SQL 2005 Express edition. I'm currently connecting to the database file directrly (from ASP.NET) and that db file is not attached to the server.
My question is this:
What is the difference ? Will the performance improve if the db is attached and I connect to it throught the server ? I'm really not sure what the difference is.
Thanks

View 3 Replies View Related

Extracting The Attached File From An Email

Feb 1, 2008

Hi there,

I need to extract a attached file which is sent via email. I believe that I can do this via SSIS... but I would like to know how...
Could you kindly send me any idea about how can I do it?




Thank you, so much.
Luis Antonio

View 15 Replies View Related

Database Snapshot On SAN Attached Disks

Sep 27, 2007

Hi All

I am in process of moving a SQL 2005 solution from a development box that used local storage to UAT environment with SAN attached storage. The solution uses database snapshots

The database files are on the SAN storage but during testing I was unable to create a Database snapshot on the SAN disk. Creating snapshots on the local disk worked fine.

Is their some restriction/problem in using the database snapshot technology with SAN storage?

View 19 Replies View Related

SQL Express Database When Attached: Login Failed

Mar 23, 2007

Hello,
I was using a SQL Express database for some time now with no problems for a NUnit Test project.  No, all of a sudden, I'm getting these problems:
DatabaseProviderTest.TestContainsUser : System.Data.SqlClient.SqlException : Cannot open user default database. Login failed.Login failed for user 'XXXXXX'.
For the SQLEXPRESS database, I checked and I am a user, and I gave myself every permission imaginable.  The default database is master, so I don't know why I am getting this problem?
Any ideas?  Thanks.

View 3 Replies View Related

Ms Sql Mdf Database File Attached Vs Created On Sql Server

May 27, 2007

 Hi allI have a question concerning sql database mdf files. In the old days I would user a ms access database. This file would be stored with the actual web files and would utilise a dsn connection. I have noted when designing with vwd 2005 express it allows you to use 2 methods of creating a mdf database. You can either create it as an attachment mdf or you can create it directly using sql manager. My question is, if you create the mdf database as an attachement file can you store it in the same manner as if you where using a ms access database, meaning can you store it with the web site's files so it uses the file storage allocated size and then create a connection similar to a dsn (but for sql) to the isp's sql engine or does it have to be uploaded to the isp' s sql server.The reason for this question is some of my customers do not want to pay the extra cost to have an sql allocation, however I do not want to go back to using old asp methods to create advanced sites as I prefer using stored procedures. Any help will be appreciated 

View 4 Replies View Related

Dropping An Active Connection On An Attached Database

Jan 9, 2008

Why in the hell doesn't SQL Server provide a facility for dropping anactive connection on an attached database in SQL Server Managementconsole? I can't detach an attached database because apparently thereis an active connection.I know you can use SSEUTIL but it seems like kluge for a poorlythought out function.Crazy

View 2 Replies View Related

Need Advice On Expanding To Direct Attached Storage

Jan 10, 2007

We are currently using an application which uses SQL Server 2005. Both sit on the same box.

This month we're adding another piece of software to our network on a new box which also depends on SQL Server. Since we don't have a directed attached storage device to store (as recommended by Microsoft), we're contemplating installing SQL Server again just for this application. Of course this means that we have to maintain two separate SQL Server databases.

Any thoughts on what we should do?

Thanks

View 1 Replies View Related

SQL Express On Vista Cannot Attach The Database Says It Is Already Attached

Mar 8, 2007

I am supposed to be documenting the SQL Express 2005 SP2 installation and connection to our application on Vista. I have installed and uninstalled the application several times in trying to create the connection and document the process. I thought I was done but now the database will not attach because it thinks the databasse is already attached. The database is not attached. I even uninstalled it again thinking something was left over.

Among the possibilities are that the database we are trying to attach is from SQL Server 2003 on a Server 2003. I tend not to think it is a server issue but have no reason to make that statement.

I tend to think it is a Vista issue because I have encountered and circumvented several. Our applications work fine on the full version of SQL. I can connect my Vista computer to the servers without issue. We have no Vista Servers other than the workstation I am trying to get SQL Express running on.

I am about out of ideas. Any suggestion will be tried at this point. Brian

View 1 Replies View Related

Wich One Is More Efficient ? Datafile Or Attached On Server ?

May 8, 2008

Hello friends !
Wich one is more efficient way to use a sql mdf file in Sqlexpress ?
attaching a mdf file on sqlexpress ( and use initialcatalog in connection string ) or use AttachDbFilename on connection string directly ?
Is there any difference in performance and speed ?
Thanks a lot

View 1 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved