Problems Installing SQLServer 2000 Developer Edition On Windows XP Pro
Jul 20, 2005
Hello!
When trying to install SqlServer 2000 Developer (as Administrator) on my
Windows XP Professional I get the following message at the point where
the system asks Local Account or Domain account:
The logon account cannot be validated for the SQL server service. Verify
that the user name and password entered are correct. The logon attempt
failed.
Anyone an idea what goes wrong here?
Thanks for your info.
Daniel
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
View 1 Replies
ADVERTISEMENT
Oct 27, 2007
Dear friends...
I am having this problem since I installed the new windows Vista.
I am trying to install the SQL Server 2005 developer edition on Windows Vista, but After installation finish successfuly I open the start menu to surprise that I could not find the Shortcuts to open the SQL Server and create new database and tables etc... I opened the full path of the exe files "C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDE" but there are not any file there, even that I searched for the exe files names but they are not existed. It looks that after instalation complete that the SQL Server is not installed on Windows Vista.
So, my question is: After installing the SQL Server 2005 SP2 for windows Vista, will the problem be solved? Or there is something else to do ON WINDOWS VISTA.
Please, I need the answer for this problem, because I need to work on SQL Server 2005 very hard.
Thanks in advance for your help...
View 11 Replies
View Related
Jul 24, 2007
I cannot find any specific info on the support of SQL server 2005 developer edition on different Windows Vista. Does anyone have any experience? TIA
View 3 Replies
View Related
Jun 14, 2007
Hello
I've installed Windows 2003 SP2 in a stand-alone cluster (will be adding a second node later). I'm now installing SQL Server 2005 Developer Edition 64-bit extended and would like to have the "Create a SQL Server Failover Cluster" box to not be grayed out. Even when I check the "SQL Server Database Services" box, it still has the cluster box grayed out.
Any idea's?
TIA!
View 2 Replies
View Related
Nov 1, 2005
I tried to install this on the same box and I'm not sure how to reply to setup questions since I want to keep my SQL Server 2000 intact.
View 5 Replies
View Related
Feb 12, 2007
Hello, I hope someone knows the answer to this issue. I am trying to install SQL Server 2000 Developer Edition and once I get to the screen that is asking for the SQL Server instance and Login Information I receive the following error when trying to proceed.
(Report Server database is a different version and cannot be used for this installation)
I have installed reporting services 2000 developer edition many times and I have never seen this error.
View 2 Replies
View Related
Jul 20, 2005
I have a need to become familiar with SQL Server 2000 for work.Needless to say I am new to SQL Server any version, but not IT ingeneral. My employer has provided me with the SQL Server 2000Personal disk from the SQL Server 2000 Enterprise kit as this isreported here on the MSDN web site to be the version that is supportedon Windows XP. In fact so many of you kind people confess to havingsucceeded in doing it.I have tried several installs using various custom componentcombinations as well as the default "typical" install.All start of trying to install the MDAC component, then after severalminutes display a dialog with the following text:"The software you are installing has not passed Windows Logo testingto verify its compatibility with Windows XP. The software will not beinstalled. Contact your system administrator"Before anyone asks, yes I am logged on as the administrator of theWindows XP machine.The setup program then displays a dialog with the following text:"Installation of the Microsoft Data Access Components package failed.(-1)"Setup then shuts down and the PC needs to be restarted before the SQLServer setup can be run again.For the techos that might have an insight, I have included detailsfrom the following logs below. SQL.MIF, SQLSTP.LOG, DASETUP.LOGSETUPAPI.LOG.Any ideas will be appreciated. Thank you.Only the log files follow from here.DASETUP.LOG: ****************************************: * Beginning of Install *: ****************************************Starting Install: Current Date/Time (U.S. Local Time): 09/07/2003 :18:25:09Path: C:Windows;C:WindowsSystem32;Localization: Machine Locale set to: English_Australia.1252Command Line Parameters:Suppress Reboot: 0Quiet/Silent Mode: 1Logging Level: 3Windows Directory: C:WindowsProgress: Loading Resource Library.Progress: Parsing INI File.*************************:** Begin INI File Dump **:*************************:Ini Section: General: ProductName = Microsoft Data Access Components 2.6: ProductBuild = 2.60.6526.2: ProductUrl = http://www.microsoft.com/data: ProductVersionKey = SOFTWAREMicrosoftDataAccess: ProductVersionValue = FullInstallVer: InstanceName = MDAC: CheckInUseFiles = 1: EULAFile = MDACEULA.RTF: EULAType = rtf: BackupSize = 10: InstallSize = 20: SupportsTS = 1: SupportsMUI = 0: CheckForDiskSpace = 1: ValidOs = 4294967295Ini Section: Packages: A = SETUP_LIBS: B = C_RUNTIME_LIBS: C = MTX_FILES: D = SETUP_RSP_FILES: E = DASETUP_FILES: F = WDSETUP_DOWNLEVEL: G = WDSETUP_MILLENNIUM: H = WDSETUP_W2K_MIGRATION: I = MDAC_DOWNLEVEL: J = MDAC_MILLENNIUM: K = MDAC_W2K_MIGRATION: L = MSXML_FILES: M = SQLXMLX: N = SQLNET_DOWNLEVEL: O = SQLNET_MILLENNIUM: P = SQLNET_W2K_MIGRATION: Q = SQLODBC_DOWNLEVEL: R = SQLODBC_MILLENNIUM: S = SQLODBC_W2K_MIGRATION: T = SQLOLEDB_DOWNLEVEL: U = SQLOLEDB_MILLENNIUM: V = SQLOLEDB_W2K_MIGRATION: W = JET_FILES: X = NEW_MUI_ENGINE: Y = REG_MDAC_VERSIONIni Section: SETUP_LIBS: Name = Microsoft Setup Libraries: ComponentName = SETUP_LIBS: Dependencies =: InstallType = inf: CabFile = setupapi.cab: InfFile = setupapi.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 1: UseRollback = 0: RebootAfter = 0: ValidOs = 3Ini Section: C_RUNTIME_LIBS: Name = Microsoft C/C++ Runtime Libraries: ComponentName = C_RUNTIME_LIBS: Dependencies =: InstallType = inf: CabFile = msvcrt.cab: InfFile = msvcrt.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 7Ini Section: MTX_FILES: Name = MTX System Files: ComponentName = MTX_FILES: Dependencies =: InstallType = inf: CabFile = mtxfiles.cab: InfFile = mtxfiles.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 7Ini Section: DASETUP_FILES: Name = MDAC Setup Files: ComponentName = DASETUP: Dependencies =: InstallType = inf: CabFile =: InfFile = dasetup.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 4294967295Ini Section: SETUP_RSP_FILES: Name = MDAC Setup Response Files: ComponentName = SETUP_RSP_FILES: Dependencies =: InstallType = inf: CabFile =: InfFile = rspfiles.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 4294967295Ini Section: WDSETUP_DOWNLEVEL: Name = WebData Setup Files: ComponentName = WDSETUP: Dependencies =: InstallType = inf: CabFile = WDSETUP.CAB: InfFile = WDSET_DL.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 7Ini Section: WDSETUP_MILLENNIUM: Name = WebData Setup Files: ComponentName = WDSETUP: Dependencies =: InstallType = inf: CabFile = WDSETUP.CAB: InfFile = WDSETUPM.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 16Ini Section: WDSETUP_W2K_MIGRATION: Name = WebData Setup Files: ComponentName = WDSETUP: Dependencies =: InstallType = xpak: CabFile = WDSETUP.CAB: InfFile = WDSETUP.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 12Ini Section: MDAC_DOWNLEVEL: Name = Microsoft Data Access Components: ComponentName = MDAC_CORE: Dependencies = C_RUNTIME_LIBS,MTX_FILES,WDSETUP: InstallType = inf: CabFile = MDACXPAK.CAB: InfFile = MDACXPDL.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd = %11%odbcconf.exe /S /Lv odbcconf.log /F%11%mdaccore.rsp: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 7Ini Section: MDAC_MILLENNIUM: Name = Microsoft Data Access Components: ComponentName = MDAC_CORE: Dependencies = C_RUNTIME_LIBS,MTX_FILES,WDSETUP: InstallType = inf: CabFile = MDACXPAK.CAB: InfFile = MDACXPKM.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd = %11%odbcconf.exe /S /Lv odbcconf.log /F%11%mdaccore.rsp: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 16Ini Section: MDAC_W2K_MIGRATION: Name = Microsoft Data Access Components: ComponentName = MDAC_CORE: Dependencies = C_RUNTIME_LIBS,MTX_FILES,WDSETUP: InstallType = xpak: CABFile = MDACXPAK.CAB: InfFile = MDACXPAK.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd = %11%odbcconf.exe /S /Lv odbcconf.log /F%11%mdaccore.rsp: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOS = 12Ini Section: MSXML_FILES: Name = Microsoft XML Parser: ComponentName = MSXML: Dependencies =: InstallType = inf: CabFile = MSXML.cab: InfFile = MSXML.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 31Ini Section: SQLXMLX: Name = XML Extensions for Microsoft OLE DB Provider for SQL Server: ComponentName = SQLXMLX: Dependencies = WDSETUP,MDAC_CORE,MSXML: InstallType = inf: CabFile = SQLXMLX.cab: InfFile = SQLXMLX.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 31Ini Section: SQLNET_DOWNLEVEL: Name = Microsoft SQL Server Network Libraries: ComponentName = SQLNET: Dependencies =: InstallType = inf: CabFile = SQLNET.CAB: InfFile = SQLNETDL.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 7Ini Section: SQLNET_MILLENNIUM: Name = Microsoft SQL Server Network Libraries: ComponentName = SQLNET: Dependencies =: InstallType = inf: CabFile = SQLNET.CAB: InfFile = SQLNETM.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 16Ini Section: SQLNET_W2K_MIGRATION: Name = Microsoft SQL Server Network Libraries: ComponentName = SQLNET: Dependencies =: InstallType = xpak: CabFile = SQLNET.CAB: InfFile = SQLNET.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 31Ini Section: SQLOLEDB_DOWNLEVEL: Name = Microsoft SQL Server OLE DB Provider: ComponentName = SQLOLEDB: Dependencies = MDAC_CORE,SQLXMLX,SQLNET: InstallType = inf: CabFile = SQLOLDB.CAB: InfFile = SQLOL_DL.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 7Ini Section: SQLOLEDB_MILLENNIUM: Name = Microsoft SQL Server OLE DB Provider: ComponentName = SQLOLEDB: Dependencies = MDAC_CORE,SQLXMLX,SQLNET: InstallType = inf: CabFile = SQLOLDB.CAB: InfFile = SQLOLDBM.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 16Ini Section: SQLOLEDB_W2K_MIGRATION: Name = Microsoft SQL Server OLE DB Provider: ComponentName = SQLOLEDB: Dependencies = MDAC_CORE,SQLXMLX,SQLNET: InstallType = xpak: CabFile = SQLOLDB.CAB: InfFile = SQLOLDB.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 31Ini Section: SQLODBC_DOWNLEVEL: Name = Microsoft SQL Server ODBC Driver: ComponentName = SQLODBC: Dependencies = WDSETUP,SQLNET: InstallType = inf: CabFile = SQLODBC.CAB: InfFile = SQLOD_DL.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd = %11%odbcconf.exe /S /Lv odbcconf.log /F%11%sqlclnt.rsp: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 7Ini Section: SQLODBC_MILLENNIUM: Name = Microsoft SQL Server ODBC Driver: ComponentName = SQLODBC: Dependencies = WDSETUP,SQLNET: InstallType = inf: CabFile = SQLODBC.CAB: InfFile = SQLODBCM.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd = %11%odbcconf.exe /S /Lv odbcconf.log /F%11%sqlclnt.rsp: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 16Ini Section: SQLODBC_W2K_MIGRATION: Name = Microsoft SQL Server ODBC Driver: ComponentName = SQLODBC: Dependencies = WDSETUP,SQLNET: InstallType = xpak: CabFile = SQLODBC.CAB: InfFile = SQLODBC.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd = %11%odbcconf.exe /S /Lv odbcconf.log /F%11%sqlclnt.rsp: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 31Ini Section: JET_FILES: Name = Jet Expression Service and String Sorting Libraries: ComponentName = JET: Dependencies =: InstallType = inf: CabFile = JETFILES.cab: InfFile = JETFILES.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 7Ini Section: NEW_MUI_ENGINE: Name = Microsoft MUI Setup Engine: ComponentName = NEWMUI: Dependencies =: InstallType = inf: CabFile = NEWMUI.CAB: InfFile = NEWMUI.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 8Ini Section: REG_MDAC_VERSION: Name = Microsoft Data Access Components: ComponentName = REG_MDAC_VERSION: Dependencies = MDAC_CORE,WDSETUP,MSXML,SQLXMLX,SQLNET,SQLOLEDB,SQ LODBC: InstallType = inf: CabFile =: InfFile = noop.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd = %11%odbcconf.exe /S /Lv odbcconf.log /F%11%
edist.rsp: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 31*************************:** End INI File Dump **:*************************:Progress: Loading EULA.Progress: Loading Strings.Debug: Loaded string resource: 13. Characters = 8Windows Version:Major Version: 5Minor Version: 0Windows NT: 1SP Level: 1Terminal Services: 0Progress: Loading Setup Engine Library.Entering function: LoadAdvPack()Parameters:*phInstance = 0x00000000pAdvPackLib = 0x0013EEF0Exiting function: LoadAdvPack()Return value: (BOOL) 1Progress: Loading ODBCConf Library.Entering function: LoadODBCConf()Parameters:*phInstance = 0x00000000pODBCConfLib = 0x0013EEFCExiting function: LoadODBCConf()Return value: (BOOL) 1IE Version:IE 6.00 and greaterVerifying System Language: The system LCID and the LCID of the setupresource DLL do not match.Entering function: BuildJobList()Parameters:pContext = 0x0013EEE4Entering function: CJob::InitializeJobQueues()Parameters:hHive = 0x80000002szRoot = ???????????????spContext = 0x%08XExiting function: CJob::InitializeJobQueues()Return value: (HRESULT) 0x00000000Exiting function: BuildJobList()Return value: (HRESULT) 0x00000000Progress: Creating Setup Wizard.Creating Wizard Page: 0Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 1Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 2Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 3Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 4Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 5Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Debug: Loaded string resource: 10. Characters = 104Creating Wizard Page: 6Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 7Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 8Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 9Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 10Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 11Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 12Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 13Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 14Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard: Microsoft Data Access Components 2.6 SetupProgress: Running in Silent Mode. Suppressing UIChecking for disk space: Drive C: requires 12316672 bytes, there are17936592896 bytes available.Detecting in-use files: Setup is checking for in-use files.Detecting in-use files: Start time: 08:25:12:25Detecting in-use files: Setup has detected a locked file:C:WindowsSystem32odbc32.dllDetecting in-use files: Setup has detected a locked file:C:WindowsSystem32odbcint.dllDetecting in-use files: Finished building filelist. CheckPoint time:08:25:15:259Detecting in-use files: Process requires reboot: winlogon.exe, ProcessID 600 (System Process: 1)Detecting in-use files: Process requires reboot: WINDOWS, Process ID556 (System Process: 1)Detecting in-use files: Process requires reboot: Program Manager,Process ID 556 (System Process: 1)Detecting in-use files: End time: 08:25:15:900Detecting in-use files: Elapsed time: 00:00:03:875Detecting in-use files: In-use file check complete.Progress: Running in Silent Mode. Starting Install...Entering function: InstallPackages()Parameters:hWnd = 0x00000000pContext = 0x0013EEE4hMessageTarget = 0x00000000pParam = 0x00000000bAsync = 0Entering function: InstallPackagesThread()Parameters:pParam = 0x009C29C0Entering function: CJob::InitializeJobQueues()Parameters:hHive = 0x80000002szRoot = ???????????????spContext = 0x%08XExiting function: CJob::InitializeJobQueues()Return value: (HRESULT) 0x00000000Debug: Loaded string resource: 3. Characters = 21Debug: Loaded string resource: 5. Characters = 14Entering function: ExecuteInstall()Parameters:nDirective = 1hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMP
spfiles.infpwcsCabFile = (null)pwcsSection = DefaultInstall.NTpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 4pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000000Debug: Loaded string resource: 3. Characters = 21Debug: Loaded string resource: 5. Characters = 14Entering function: ExecuteInstall()Parameters:nDirective = 1hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPdasetup.infpwcsCabFile = (null)pwcsSection = DefaultInstall.NTpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 4pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000000Debug: Loaded string resource: 3. Characters = 21Debug: Loaded string resource: 5. Characters = 14Entering function: ExecuteInstall()Parameters:nDirective = 4hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPWDSETUP.INFpwcsCabFile = (null)pwcsSection = DefaultInstallpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 4pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x01000003Debug: Loaded string resource: 3. Characters = 21Debug: Loaded string resource: 5. Characters = 14Entering function: ExecuteInstall()Parameters:nDirective = 4hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPMDACXPAK.INFpwcsCabFile = (null)pwcsSection = DefaultInstallpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 36pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000BC2Reboot Required: Job number 4 requires rebootDebug: Loaded string resource: 3. Characters = 21Debug: Loaded string resource: 5. Characters = 14Entering function: ExecuteInstall()Parameters:nDirective = 1hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPMSXML.infpwcsCabFile = (null)pwcsSection = DefaultInstall.NTpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 36pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000000Debug: Loaded string resource: 3. Characters = 21Debug: Loaded string resource: 5. Characters = 14Entering function: ExecuteInstall()Parameters:nDirective = 1hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPSQLXMLX.infpwcsCabFile = (null)pwcsSection = DefaultInstall.NTpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 548pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000000Reboot Required: Job number 6 requires rebootDebug: Loaded string resource: 3. Characters = 21Debug: Loaded string resource: 5. Characters = 14Entering function: ExecuteInstall()Parameters:nDirective = 4hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPSQLNET.INFpwcsCabFile = (null)pwcsSection = DefaultInstallpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 36pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x80004005Debug: Loaded string resource: 4. Characters = 23Debug: Loaded string resource: 6. Characters = 16Entering function: ExecuteInstall()Parameters:nDirective = 5hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPSQLNET.INFpwcsCabFile = (null)pwcsSection = DefaultInstallpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 68pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x80004005Debug: Loaded string resource: 4. Characters = 23Debug: Loaded string resource: 6. Characters = 16Entering function: ExecuteInstall()Parameters:nDirective = 1hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPSQLXMLX.infpwcsCabFile = (null)pwcsSection = DefaultInstall.NTpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 68pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000000Debug: Loaded string resource: 4. Characters = 23Debug: Loaded string resource: 6. Characters = 16Entering function: ExecuteInstall()Parameters:nDirective = 1hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPMSXML.infpwcsCabFile = (null)pwcsSection = DefaultInstall.NTpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 68pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000BC2Reboot Required: Job number 5 requires rebootDebug: Loaded string resource: 4. Characters = 23Debug: Loaded string resource: 6. Characters = 16Entering function: ExecuteInstall()Parameters:nDirective = 5hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPMDACXPAK.INFpwcsCabFile = (null)pwcsSection = DefaultInstallpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 68pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000BC2Reboot Required: Job number 4 requires rebootEntering function: CJob::DestroyJobQueues()Parameters: None.Exiting function: CJob::DestroyJobQueues()Return value: (HRESULT) 0x00000000Exiting function: InstallPackagesThread()Return value: (HRESULT) 0x00000000Exiting function: InstallPackages()Return value: (HRESULT) 0x00000000State after Install:Setup was Successful: 0Setup Requires Reboot: 0Setup Will Reboot the Machine: 0Exiting: Setup is shutting down..Ending Install: Current Date/Time (U.S. Local Time): 09/07/2003 :18:38:30Errors collection: Severity: 100, Type: 2, Code: 0x80004005, Title:(null), Text: Unspecified errorErrors collection: Severity: 100, Type: 2, Code: 0x80004005, Title:(null), Text: Unspecified errorError: The following error was encountered during setup:*** (null):Unspecified error(Severity: 100, Type: 2, Code: 0x80004005)SQL.MIFSTART COMPONENTNAME = "WORKSTATION"START GROUP NAME = "ComponentID"ID = 1CLASS = "DMTF|ComponentID|1.0"START ATTRIBUTENAME = "Manufacturer"ID = 1ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(64)VALUE = "Microsoft"END ATTRIBUTESTART ATTRIBUTENAME = "Product"ID = 2ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(64)VALUE = "Microsoft SQL Server 2000"END ATTRIBUTESTART ATTRIBUTENAME = "Version"ID = 3ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(64)VALUE = "8.00.194"END ATTRIBUTESTART ATTRIBUTENAME = "Locale"ID = 4ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(16)VALUE = ""END ATTRIBUTESTART ATTRIBUTENAME = "Serial Number"ID = 5ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(64)VALUE = ""END ATTRIBUTESTART ATTRIBUTENAME = "Installation"ID = 6ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(64)VALUE = "DateTime"END ATTRIBUTEEND GROUPSTART GROUPNAME = "InstallStatus"ID = 2CLASS = "MICROSOFT|JOBSTATUS|1.0"START ATTRIBUTENAME = "Status"ID = 1ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(32)VALUE = "Failed"END ATTRIBUTESTART ATTRIBUTENAME = "Description"ID = 2ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(128)VALUE = "Installation of the Microsoft Data Access Componentspackage failed. (-1)"END ATTRIBUTEEND GROUPEND COMPONENTSETUPAPI.LOG[2003/09/07 18:25:11 3916.11]#-199 Executing "C:WINDOWSTempIXP000.TMPdasetup.exe" with commandline: /Q:D /N#E077 Could not locate a non-empty section [DefaultInstall] whencalculating disk space in "C:WINDOWSTempIXP000.TMPoop.inf". Error0xe0000102: The required line was not found in the INF.[2003/09/07 18:25:16 3916.1]#-199 Executing "C:WINDOWSTempIXP000.TMPdasetup.exe" with commandline: /Q:D /N#E361 An unsigned or incorrectly signed file"c:windows empixp000.tmp
spfiles.inf" will be installed(Policy=Ignore). Error 1168: Element not found.#-024 Copying file "C:WINDOWSTempIXP000.TMP
spfiles.inf" to"C:Program FilesCommon FilesMicrosoft Shareddasetup
spfiles.inf".#E361 An unsigned or incorrectly signed file"C:WINDOWSTempIXP000.TMP
spfiles.inf" will be installed(Policy=Ignore). Error 1168: Element not found.#-336 Copying file "C:WINDOWSTempIXP000.TMP
edist.rsp" to"C:WindowsSystem32
edist.rsp" via temporary file"C:WindowsSystem32SET14.tmp".#E361 An unsigned or incorrectly signed file"C:WINDOWSTempIXP000.TMP
edist.rsp" will be installed(Policy=Ignore). Error 1168: Element not found.#-336 Copying file "C:WINDOWSTempIXP000.TMPmdaccore.rsp" to"C:WindowsSystem32mdaccore.rsp" via temporary file"C:WindowsSystem32SET17.tmp".#E361 An unsigned or incorrectly signed file"C:WINDOWSTempIXP000.TMPmdaccore.rsp" will be installed(Policy=Ignore). Error 1168: Element not found.#-336 Copying file "C:WINDOWSTempIXP000.TMPsqlclnt.rsp" to"C:WindowsSystem32sqlclnt.rsp" via temporary file"C:WindowsSystem32SET1A.tmp".#E361 An unsigned or incorrectly signed file"C:WINDOWSTempIXP000.TMPsqlclnt.rsp" will be installed(Policy=Ignore). Error 1168: Element not found.[2003/09/07 18:25:19 3916.1]#-199 Executing "C:WINDOWSTempIXP000.TMPdasetup.exe" with commandline: /Q:D /N#E361 An unsigned or incorrectly signed file"c:windows empixp000.tmpdasetup.inf" will be installed(Policy=Ignore). Error 1168: Element not found.#-024 Copying file "C:WINDOWSTempIXP000.TMPdasetup.inf" to"C:Program FilesCommon FilesMicrosoft Shareddasetupdasetup.inf".#E361 An unsigned or incorrectly signed file"C:WINDOWSTempIXP000.TMPdasetup.inf" will be installed(Policy=Ignore). Error 1168: Element not found.#-336 Copying file "C:WINDOWSTempIXP000.TMPdasetup.ini" to"C:Program FilesCommon FilesMicrosoft Shareddasetupdasetup.ini"via temporary file "C:Program FilesCommon FilesMicrosoftShareddasetupSET22.tmp".#E361 An unsigned or incorrectly signed file"C:WINDOWSTempIXP000.TMPdasetup.ini" will be installed(Policy=Ignore). Error 1168: Element not found.[2003/09/07 18:25:21 3916.1]#-199 Executing "C:WINDOWSTempIXP000.TMPdasetup.exe" with commandline: /Q:D /N#-340 Extracted file "ds16gt.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SETF4.tmp" (target is"C:WindowsSystem32ds16gt.dll").#-336 Copying file "C:WindowsSystem32SETF4.tmp" to"C:WindowsSystem32ds16gt.dll" via temporary file"C:WindowsSystem32SETF6.tmp".#W025 A newer file "C:WindowsSystem32ds16gt.dll" was overwritten byan older (signed) file. Version of source file: 3.510.3711.0. Versionof target file: 3.510.3711.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "ds32gt.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SETF7.tmp" (target is"C:WindowsSystem32ds32gt.dll").#-336 Copying file "C:WindowsSystem32SETF7.tmp" to"C:WindowsSystem32ds32gt.dll" via temporary file"C:WindowsSystem32SETF9.tmp".#W025 A newer file "C:WindowsSystem32ds32gt.dll" was overwritten byan older (signed) file. Version of source file: 3.520.6526.0. Versionof target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "msadce.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET106.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadce.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET106.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadce.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET108.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadce.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadcer.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET109.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadcer.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET109.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadcer.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET10B.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadcer.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.70.7713.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadcf.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET10C.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadcf.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET10C.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadcf.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET10E.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadcf.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadcfr.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET10F.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadcfr.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET10F.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadcfr.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET111.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadcfr.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.70.7713.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadco.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET112.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadco.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET112.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadco.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET114.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadco.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadcor.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET115.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadcor.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET115.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadcor.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET117.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadcor.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.70.7713.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadcs.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET118.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadcs.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET118.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadcs.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET11A.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadcs.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadds.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET11B.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadds.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET11B.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadds.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET11D.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadds.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msaddsr.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET11E.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsaddsr.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET11E.tmp" to "C:Program FilesCommonFilesSystemMSADCmsaddsr.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET120.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsaddsr.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.70.7713.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msader15.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET121.tmp" (target is "C:Program FilesCommonFilesSystemADOmsader15.dll").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET121.tmp" to "C:Program FilesCommonFilesSystemADOmsader15.dll" via temporary file "C:ProgramFilesCommon FilesSystemADOSET123.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsader15.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.70.7713.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msado15.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET124.tmp" (target is "C:Program FilesCommonFilesSystemADOmsado15.dll").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET124.tmp" to "C:Program FilesCommonFilesSystemADOmsado15.dll" via temporary file "C:ProgramFilesCommon FilesSystemADOSET126.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsado15.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msado20.tlb" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET127.tmp" (target is "C:Program FilesCommonFilesSystemADOmsado20.tlb").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET127.tmp" to "C:Program FilesCommonFilesSystemADOmsado20.tlb" via temporary file "C:ProgramFilesCommon FilesSystemADOSET129.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsado20.tlb" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msado21.tlb" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET12A.tmp" (target is "C:Program FilesCommonFilesSystemADOmsado21.tlb").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET12A.tmp" to "C:Program FilesCommonFilesSystemADOmsado21.tlb" via temporary file "C:ProgramFilesCommon FilesSystemADOSET12C.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsado21.tlb" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msado25.tlb" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET12D.tmp" (target is "C:Program FilesCommonFilesSystemADOmsado25.tlb").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET12D.tmp" to "C:Program FilesCommonFilesSystemADOmsado25.tlb" via temporary file "C:ProgramFilesCommon FilesSystemADOSET12F.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsado25.tlb" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadomd.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET130.tmp" (target is "C:Program FilesCommonFilesSystemADOmsadomd.dll").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET130.tmp" to "C:Program FilesCommonFilesSystemADOmsadomd.dll" via temporary file "C:ProgramFilesCommon FilesSystemADOSET132.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsadomd.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msador15.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET133.tmp" (target is "C:Program FilesCommonFilesSystemADOmsador15.dll").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET133.tmp" to "C:Program FilesCommonFilesSystemADOmsador15.dll" via temporary file "C:ProgramFilesCommon FilesSystemADOSET135.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsador15.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadox.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET136.tmp" (target is "C:Program FilesCommonFilesSystemADOmsadox.dll").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET136.tmp" to "C:Program FilesCommonFilesSystemADOmsadox.dll" via temporary file "C:ProgramFilesCommon FilesSystemADOSET138.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsadox.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadrh15.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET139.tmp" (target is "C:Program FilesCommonFilesSystemADOmsadrh15.dll").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET139.tmp" to "C:Program FilesCommonFilesSystemADOmsadrh15.dll" via temporary file "C:ProgramFilesCommon FilesSystemADOSET13B.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsadrh15.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "mscpxl32.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET13C.tmp" (target is"C:WindowsSystem32mscpxl32.dll").#-336 Copying file "C:WindowsSystem32SET13C.tmp" to"C:WindowsSystem32mscpxl32.dll" via temporary file"C:WindowsSystem32SET13E.tmp".#W025 A newer file "C:WindowsSystem32mscpxl32.dll" was overwrittenby an older (signed) file. Version of source file: 3.511.3.20. Versionof target file: 3.520.7713.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "msdadc.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET13F.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdadc.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET13F.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdadc.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET141.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdadc.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdaenum.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET142.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdaenum.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET142.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdaenum.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET144.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdaenum.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdaer.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET145.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdaer.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET145.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdaer.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET147.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdaer.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdaora.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET148.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdaora.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET148.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdaora.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET14A.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdaora.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdaosp.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET14B.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdaosp.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET14B.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdaosp.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET14D.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdaosp.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdaprsr.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET14E.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsdaprsr.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET14E.tmp" to "C:Program FilesCommonFilesSystemMSADCmsdaprsr.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET150.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsdaprsr.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.70.7713.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msdaprst.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET151.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsdaprst.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET151.tmp" to "C:Program FilesCommonFilesSystemMSADCmsdaprst.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET153.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsdaprst.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msdaps.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET154.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdaps.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET154.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdaps.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET156.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdaps.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdarem.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET157.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsdarem.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET157.tmp" to "C:Program FilesCommonFilesSystemMSADCmsdarem.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET159.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsdarem.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msdaremr.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET15A.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsdaremr.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET15A.tmp" to "C:Program FilesCommonFilesSystemMSADCmsdaremr.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET15C.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsdaremr.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.70.7713.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msdart.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET15D.tmp" (target is"C:WindowsSystem32msdart.dll").#-336 Copying file "C:WindowsSystem32SET15D.tmp" to"C:WindowsSystem32msdart.dll" via temporary file"C:WindowsSystem32SET15F.tmp".#W025 A newer file "C:WindowsSystem32msdart.dll" was overwritten byan older (signed) file. Version of source file: 2.60.6526.0. Versionof target file: 2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored.The existing target file was signed.#-340 Extracted file "msdasc.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET163.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdasc.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET163.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdasc.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET165.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdasc.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdasql.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET166.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdasql.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET166.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdasql.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET168.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdasql.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdasqlr.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET169.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdasqlr.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET169.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdasqlr.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET16B.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdasqlr.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.70.7713.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdatl3.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET16C.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdatl3.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET16C.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdatl3.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET16E.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdatl3.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdatsrc.tlb" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET16F.tmp" (target is"C:WindowsSystem32msdatsrc.tlb").#-336 Copying file "C:WindowsSystem32SET16F.tmp" to"C:WindowsSystem32msdatsrc.tlb" via temporary file"C:WindowsSystem32SET171.tmp".#W025 A newer file "C:WindowsSystem32msdatsrc.tlb" was overwrittenby an older (signed) file. Version of source file: 9.0.6526.0. Versionof target file: 9.0.9030.0. The SP_COPY_FORCE_NEWER flag was ignored.The existing target file was signed.#-340 Extracted file "msdatt.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET172.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdatt.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET172.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdatt.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET174.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdatt.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdaurl.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET175.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdaurl.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET175.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdaurl.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET177.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdaurl.dll" was overwritten by an older (signed) file. Version ofsource file: 9.1.6526.0. Version of target file: 9.1.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdfmap.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET178.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsdfmap.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET178.tmp" to "C:Program FilesCommonFilesSystemMSADCmsdfmap.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET17A.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsdfmap.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msjro.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET17D.tmp" (target is "C:Program FilesCommonFilesSystemADOmsjro.dll").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET17D.tmp" to "C:Program FilesCommonFilesSystemADOmsjro.dll" via temporary file "C:ProgramFilesCommon FilesSystemADOSET17F.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsjro.dll" was overwritten by an older (signed) file.Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msorcl32.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET183.tmp" (target is"C:WindowsSystem32msorcl32.dll").#-336 Copying file "C:WindowsSystem32SET183.tmp" to"C:WindowsSystem32msorcl32.dll" via temporary file"C:WindowsSystem32SET185.tmp".#W025 A newer file "C:WindowsSystem32msorcl32.dll" was overwrittenby an older (signed) file. Version of source file: 2.573.6526.0.Version of target file: 2.573.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "msxactps.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET186.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsxactps.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET186.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsxactps.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET188.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsxactps.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "odbc16gt.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET199.tmp" (target is"C:WindowsSystem32odbc16gt.dll").#-336 Copying file "C:WindowsSystem32SET199.tmp" to"C:WindowsSystem32odbc16gt.dll" via temporary file"C:WindowsSystem32SET19B.tmp".#W025 A newer file "C:WindowsSystem32odbc16gt.dll" was overwrittenby an older (signed) file. Version of source file: 3.510.3711.0.Version of target file: 3.510.3711.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "odbc32.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET19C.tmp" (target is"C:WindowsSystem32odbc32.dll").#-336 Copying file "C:WindowsSystem32SET19C.tmp" to"C:WindowsSystem32odbc32.dll" via temporary file"C:WindowsSystem32SET19E.tmp".#W025 A newer file "C:WindowsSystem32odbc32.dll" was overwritten byan older (signed) file. Version of source file: 3.520.6526.0. Versionof target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#W190 File "C:WindowsSystem32SET19E.tmp" marked to be moved to"C:WindowsSystem32odbc32.dll" on next reboot.#-340 Extracted file "odbc32gt.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET19F.tmp" (target is"C:WindowsSystem32odbc32gt.dll").#-336 Copying file "C:WindowsSystem32SET19F.tmp" to"C:WindowsSystem32odbc32gt.dll" via temporary file"C:WindowsSystem32SET1A1.tmp".#W025 A newer file "C:WindowsSystem32odbc32gt.dll" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "odbcad32.exe" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET1A2.tmp" (target is"C:WindowsSystem32odbcad32.exe").#-336 Copying file "C:WindowsSystem32SET1A2.tmp" to"C:WindowsSystem32odbcad32.exe" via temporary file"C:WindowsSystem32SET1A4.tmp".#W025 A newer file "C:WindowsSystem32odbcad32.exe" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "odbccp32.cpl" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET1A5.tmp" (target is"C:WindowsSystem32odbccp32.cpl").#-336 Copying file "C:WindowsSystem32SET1A5.tmp" to"C:WindowsSystem32odbccp32.cpl" via temporary file"C:WindowsSystem32SET1A7.tmp".#W025 A newer file "C:WindowsSystem32odbccp32.cpl" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.7713.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "odbccp32.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET1A8.tmp" (target is"C:WindowsSystem32odbccp32.dll").#-336 Copying file "C:WindowsSystem32SET1A8.tmp" to"C:WindowsSystem32odbccp32.dll" via temporary file"C:WindowsSystem32SET1AA.tmp".#W025 A newer file "C:WindowsSystem32odbccp32.dll" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "odbccr32.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET1AB.tmp" (target is"C:WindowsSystem32odbccr32.dll").#-336 Copying file "C:WindowsSystem32SET1AB.tmp" to"C:WindowsSystem32odbccr32.dll" via temporary file"C:WindowsSystem32SET1AD.tmp".#W025 A newer file "C:WindowsSystem32odbccr32.dll" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "odbccu32.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET1AE.tmp" (target is"C:WindowsSystem32odbccu32.dll").#-336 Copying file "C:WindowsSystem32SET1AE.tmp" to"C:WindowsSystem32odbccu32.dll" via temporary file"C:WindowsSystem32SET1B0.tmp".#W025 A newer file "C:WindowsSystem32odbccu32.dll" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "odbcint.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET1B4.tmp" (target is"C:WindowsSystem32odbcint.dll").#-336 Copying file "C:WindowsSystem32SET1B4.tmp" to"C:WindowsSystem32odbcint.dll" via temporary file"C:WindowsSystem32SET1B6.tmp".#W025 A newer file "C:WindowsSystem32odbcint.dll" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.7713.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#W190 File "C:WindowsSystem32SET1B6.tmp" marked to be moved to"C:WindowsSystem32odbcint.dll" on next reboot.#-340 Extracted file "odbctrac.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET1B7.tmp" (target is"C:WindowsSystem32odbctrac.dll").#-336 Copying file "C:WindowsSystem32SET1B7.tmp" to"C:WindowsSystem32odbctrac.dll" via temporary file"C:WindowsSystem32SET1B9.tmp".#W025 A newer file "C:WindowsSystem32odbctrac.dll" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "oledb32.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET1BA.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBoledb32.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET1BA.tmp" to "C:Program FilesCommon FilesSystemOLEDBoledb32.dll" via temporary file
View 2 Replies
View Related
Mar 14, 2007
Hi everyone...
I'm facing a problem while installing the SQL Server 2005 Express on Windows 2000 Pro with SP4.
After finishing the downloading from Microsoft I start the installation and things seems to go ok but during Extracting Files step a message appears "SQL Server Setup unexpectedly failed. For more information, review the setup summary log file in %Program Files%Microsoft SQL Server90Setup BootstrapLOGSummary.txt" and it terminates the installation.
I located the log file and open it but can't understand the problem..I copy the text and paste it here for anyone who can understand it.Please, it is very importand for me to work with SQL Server for my project. Any advice or information or anything else???
Thank you all,
HERE IS THE LOG FILE:
"Microsoft SQL Server 2005 Setup beginning at Wed Mar 14 07:45:33 2007
Process ID : 2684
c:c7720b32114815db82783dd06c2d54b9setup.exe Version: 2005.90.3042.0
Running: LoadResourcesAction at: 2007/2/14 7:45:33
Complete: LoadResourcesAction at: 2007/2/14 7:45:33, returned true
Running: ParseBootstrapOptionsAction at: 2007/2/14 7:45:33
Loaded DLL:c:c7720b32114815db82783dd06c2d54b9xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2007/2/14 7:45:33, 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: Wed Jun 14 16:30:14 2006
Function Name: writeEncryptedString
Source Line Number: 124
----------------------------------------------------------
writeEncryptedString() failed
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Wed Jun 14 16:30:14 2006
Function Name: writeEncryptedString
Source Line Number: 123
----------------------------------------------------------
Error Code: 0x80070002 (2)
Windows Error Text: Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run:
Datastore exception while trying to write logging properties.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupStateScope.primaryLogFiles
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
02B1CFC0Unable to proceed with setup, there was a command line parsing error. : 2
Error Code: 0x80070002 (2)
Windows Error Text:
Class not registered.
Failed to create CAB file due to datastore exception
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "2684"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupBootstrapOptionsScope.HostSetup
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Message pump returning: 2"
View 4 Replies
View Related
Jun 1, 2007
Hi, all -
I'm trying to register a developer's 2000 pc from my 2005 pc.
i'm not sure this is even something possible from Dev Edition to Dev Edition- I can register a 2000 server just fine.
I can ping him. Both our systems have remote access 'on'. His server is (local), i've tried connecting to it by just entering his machine name and by using just the ip address. The error I get is "timeout expired. The timeout elapsed prior to completion of the operation or the server is not responding."
Am I just not registering this properly? I entered just the ip address in the 'server' box. I am connecting as sa with the pw he gave me. When i connect to my server, I use the ip addressinstance. However, I am not sure what to use for the instance when all I see when I look at his machine is (local).
I haven't needed to do this before.
Suggestions?
View 2 Replies
View Related
Dec 21, 2007
Hi
I am interested in taking MCTS exam 70-431 for sql server 2005 implementation and maintainance.
I have been reading the hardware requirements for the instalation of sql server versions and realise that enterprise and developer editions have same minimum requirements for the operation system.
I understand that the Developer Edition includes all the functionality of SQL Server 2005 Enterprise Edition, but it is licensed for use as a development and test system, not as a production server.
Also I undestand that the developer edition supports the Windows XP Home Edition with SP2 or later but the enterprise edition does not support this operating system. The evaluation/trial version is for the enterprise edition. Can I use the developer version of sql server 2005 for my practice exercises instead of using the trial version?
I have all hardware requirements for the trial enterprise version except that I am using Microsoft windows Xp home edition version 2002 with SP2. I am trying to see if I can use the developer version of sql server 2005 as it is cheaper for me to buy this software than buying the new operating system for my computer.
According to the microsoft book for the MCTS exam 70-431 there is a section which states that before you begin you should have Microsoft Windows Server 2003 running on your computer on an NTFS file system
(NTFS) partition. Will I still be ok to use the book and be able to do all the tests in the book if i am using the developer version of sql server 2005 with my Microsoft windows Xp home edition than using the trial version which comes with the book?
Thanks
gifty
View 3 Replies
View Related
May 13, 2007
Can I install SQL Server 2005 Developer Edition on XP Media Center Edition?
Thanks.
View 3 Replies
View Related
Apr 3, 2007
Hi Everyone,
Recently I installed Visual Studio 2005 which also installed SQL Express Edition with it. I then installed SQL Server 2005 Developer Edition and am now able to see two instances SQLEXPRESS and MSSQLERVER.
I do not want to use the Express version anymore, Do I have to have the Express version running or can I have just the Developer Edition ?
Please help, can't find any help on the SQL website!
Thanks
View 4 Replies
View Related
Apr 24, 2008
I am unable to successfully install SQL Server 2005 Developer edition here on a machine at work. Database service and client tools fails to install. I get the message that:"The computer running SQL Server setup does not meet the minimum system requirements for this SQL server release. Microsoft SQL Server is not supported by this operating system."
I am running Win XP pro sp2 with all the latest updates installed. What could be causing this and how do I fix it?
View 5 Replies
View Related
Sep 20, 2007
I tring to install SQL Server 2005 Developer Edition on Windows XP Pro but i not able to to so because of the following errors:-
Action "OpenPipeAction" failed during execution
Action "CreatePipeAction" failed during execution.
MsiOpenDatabase failed with 87
MsiOpenDatabase failed with 87 for MSI
Action "InstallDTSAction.9" failed during execution. Error information reported during run:
Action: "InstallDTSAction.9" will be marked as failed due to the following condition:
Condition "Package "9" either passed when it was last installed, or it has not been executed yet" returned false. Condition context:
Prereq package will be failed due to the previous installation attempt returning: 1605
Can Anyone help me out on this?
Thanks
VG
View 12 Replies
View Related
May 14, 2006
Hi,
I downloaded SQL Server 2005 Developer Edition (x86) via MSDNAA (the package conatins 2 cd images the download program CRC checked them and all. I'm trying to install it on Windows XP prof. sp2).
When I mount the first CD, the installation menu comes up, if from the Install menu I select
"Server components, tools, Books Online, and samples"
an error message pops up saying:
"The application or DLL D:Setupsetupex.dll is not a valid Windows image. Please check this against your installation diskette."
When I press OK, it pops up again, then after clicking on OK one more time the Microsoft SQL Server 2005 Setup window comes up. After accepting the installation conditions and clicking next, it takes me to the "Installing Prerequisites" phrase, where when I press the Install button, it writes:
"Errors occured during the installation:
Error 193 installing .NET Framework 2.0"
Then the installation freezes, and I must press cancel (after that, the installation breaks saying: SQL Server Setup unexpectedly failed...)
If in the installation menu I choose
"
Install SQL Server Upgrade Advisor"
or
"
Run the SQL Native Client Installation Wizard"
a warning pops up saying:
"This installation package could not be opened.
Contact the application vendor to verify that this is a
valid Windows Installer package."
When I press OK, the warning disappeares, nothing happens.
I have .NET Framework 2.0, running VS2005 Prof. with no problem, had MS SQL Server 2005 Express Edition, but uninstalled it (never used), and just installed the latest MSI.
Searched the net for the "error 193" message, but haven't found anything that actually could help my case.
Thank you for your help.
View 7 Replies
View Related
Mar 6, 2007
I get the following error installing SQL Server 2005 Developer Edition
Failed to install and configure assemblies C:Program FilesMicrosoft SQL Server90DTSTasksMicrosoft.SqlServer.MSMQTask.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: You must have administrative credentials to perform this task. Contact your system administrator for assistance.
I am installing on Windows XP with Admin privs.
There is nothing listed in COM+ Services for SQL.
The Distributed Transaction Coordinator service is running.
There is a previous installation of SQL 2000 Developer Edition installed.
I have seen some pretty old posts with the same error.
I was wondering if there was a final resolution, service pack, etc. that solves this problem?
View 3 Replies
View Related
Mar 20, 2007
Hi,
I have a problem installing SQL Server 2005 Developer Edition.
When I start the setup, I get the message:
"SQL Server Setup could not run. Another instance of SQL Server Setup is already running. The running instance must complete before you can run SQL Server Setup again"
I am using Windows XP and have SQL Server 2000 and SQL Server Express 2005 installed.
I shut down both instances before I attempted to do the install but I still get the message.
I checked active tasks but no tasks with SQL* is running.
Please advise.
Thanks
View 4 Replies
View Related
Apr 14, 2006
I downloaded the 2 CD ISO Format from msdn to install SQL Server 2005 English Developer Edition on my XP SP2 box.
I currently have SQL 2000 running. So Sql Server 2005 Dev Edition is to run side by side in a named instance.
From CD1, I launched default.hta and could not install Database Services. The log mentioned could not find a 'valid copy of xxx.msi' where xxx is VSS writer, Database Services or SQL XML4 etc...
I tried 3 times and each time it damaged my SQL2000 beyond repair.
Any suggestions will be much appreciated. Thanks
View 4 Replies
View Related
Aug 26, 2006
I have Visual Studio 2005 Professional on windows xp.
I am getting error installing SQL Server 2005 Developer Edition on windows XP.
My Hardware is P4 1.6 GHz with 256MB RAM (Though BOL says setups shouldnt fail because of this ).
Is there ANY solution for installing SQL Server 2005 Developer Edition on Windows XP.
The error at end I am getting is :
=======================================================================================
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
The feature(s) specified are not valid for this edition of SQL Server.
For help, click:
http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rl
l&EvtID=70031&EvtType=sqlchaining%5csqlchainingactions.cpp%40DeterminePackageTransformsAction%40sqls%3a%3aDete
rminePackageTransformsAction%3a%3aperform%400x1118f
------------------------------
BUTTONS:
OK
------------------------------
=======================================================================================
I can reinstall Visual Studio 2005, if this is the solution? .
Please Help
regards
View 4 Replies
View Related
Aug 22, 2006
I am installing SQL 2005 developer edition on windows 2000. The server met all requirements for the installation. I get an €œUnexpected error occurred€? at the end of the installation right when the SQL engine installation is completed.
Looking at the error logs, on the setup0001 (core) file I get the following error: Has anyone encountered this :
Source File Name: sqlchainingsqlchainingactions.cpp
Compiler Timestamp: Thu Sep 1 22:23:05 2005
Function Name: sqls::ReportChainingResults::perform
Source Line Number: 2992
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 "watsonFailedActionErrorCode" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupStateScope.watsonFailedActionErrorCode
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
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 "watsonFailedActionErrorCode" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupStateScope.watsonFailedActionErrorCode
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
Message pump returning: 1602
View 1 Replies
View Related
Jul 31, 2007
Currently I am just trying to completely remove all Vista Ultimate's knowledge of installed instances of SQLServer 2005 Developer edition.
I cannot do this for some reason. This all began when I tried to install SQLServer 2005 and it installed but I could not connect to it. Now I have two installed instances that I cannot access, after removing all SQL programs from the Programs and Features icon in the control panel.
I tried running "WIndows Installer CleanUp Utility" as I read in a thread on this forum. This did not help. After going thru and removing all SQLServer programs using the "programs and features" icon in control panel... The installation process shows two installed instances of SQLServer 2005.
1) How can I completely erase all Vista Ultimate's knowledge of any SQLServer 2005 install and start over?
I have downloaded SQLServer 2005 SP 2, and run it, but clearly what I should do, and what Microsoft has asked me to do are not working...
2) What should I be doing to install SQLServer 2005 Developer Edition successfully?
I have been a strong supporter of Microsoft, but this is getting me very frustrated.
Please help,
- Chaz
View 3 Replies
View Related
Dec 19, 2007
hello eveyone..i have just downloaded and installed the visaul web developer 2005 express edition and sqlserver 2005 express edition.On top of that i even downloaded and installed the northwind database.But my problem is when i am connecting to the northwind database by clicking toos menu>connect to the database>choose datasource>new connection>..i have provided it with the required information..but as soon as i press "Test Connection" button the following error box displays.. "an error has occured while establishing a connection to the server.when connecting to the sql server2005,this failure may be caused by the fact that under default settings sql server doestnot allow remote connections.(provider:Named piped providers,error:40-couldnot open a connection to sqlserver.)" i have no idea whats is all about..can anyone get me pass this error..
View 2 Replies
View Related
Jul 8, 2007
Hi, I am going to get a new laptop and was wondering in particular which versions of Windows Vista will run SQL Server 2005 Developer Edition. I want to be able to use all the features of SQL Server 2005, so IIS is needed for example ( I will be building end to end BI soutions using SQL Server Management Studio, SSIS, Analysis Services and Reporting Services.
Chris
View 13 Replies
View Related
Apr 17, 2008
Hi,
I have Vista Home premium edition and trying to install SQL Server developer edition 2005 as local administrator. I have already enabled IIS 7 and have Office Ultimate 2007 installed. When I run the set up program, I get a warning titled "Program Compatibility Assistant" that my Operating system may not be compatible with the version of sql server I am installing. It says after setup is complete, I should run SP2 of SQL Server 2005 with 3 buttons as "Check for solutions online", "run this program" and "cancel"...
My question, should I select "run this program" and after the setup completes, download SP2 and apply the patch?
I read some articles in forums that sounds like lot of issues to get sql server working on vista. Can some one direct me to correct options. This is my wife's machine so I dont want to experiment too much and blow her machine away. Please help.
Thanks,
Gaja
View 7 Replies
View Related
Jan 18, 2008
Has microsoft issued an update so I can install SQL 2005 DE on Windows Vista? Thank You!
View 3 Replies
View Related
May 21, 2005
Can you install Sql Server 2000 Developer Edition with MSDE 2000 release A already installed?
View 2 Replies
View Related
Jul 21, 2006
Hello,
Well I have completely reformatted my computer and reinstalled windows XP professional with all the updates, xp service pack 2 and .net framework 1.1. Now when I try to install sql server 2000 developer, I get the following message where it asks Local Account or Domain account (I choose Domain):
The logon account cannot be validated for the SQL server service. Verify that the user name and password entered are correct. The logon attempt failed
I am using the administrators account, I didn't have a password on it so I created one but this makes no difference. I also tried creating a new user account with admin rights but this also fails to solve the problem.
Please can someone help me with this,
pp
View 1 Replies
View Related
Nov 1, 2006
I have a SQL cluster that is using SQL 2000 developer
edition on both nodes - I need to bring these servers into production, the
question is how do I upgrade Developer edition to Enterprise edition?
I have been told it€™s a simple REG change? but can't find it on any forum. Or
do I need to de-install and reinstall the correct version - Any help is appreciated.
Thanks all in advance
View 3 Replies
View Related
May 5, 2004
I am currently using MS Access for my site and am ready to move on.
I have obtained (legally) SQL Server 2000 Developer Edition.
Before I install this on my pc to learn this new tool and begin adjustments to my site, I have an important question, If I can phrase it correctly.
1. Will this set up my pc as a SQL server as well as keep the current configurations?
2. I have some projects I would like to keep using MS Access, how would this effect it?
3. I have never created a database using SQL or MySQL, any suggested tutorial links?
Thanks,
Zath
<has new toys now :) >
View 5 Replies
View Related
Dec 29, 2004
** Error in msgbox : “Setup failed to configure the server. Refer to the server error logs and C:WINDOWSsqlstp.log for more information. �
** Cut From: C:WINDOWSsqlstp.log – ( previous exit codes look OK) ---
(previous text removed) …
21:54:29 C:Program FilesMicrosoft SQL Server80ToolsBinncnfgsvr.exe -F "C:WINDOWSsqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 66364 -U sa -P
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=cn91909-a;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
driver={sql server};server=cn91909-a;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
driver={sql server};server=cn91909-a;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
SQL Server configuration failed.
###############################################################################
21:54:55 Process Exit Code: (-1)
21:57:07 Setup failed to configure the server. Refer to the server error logs and C:WINDOWSsqlstp.log for more information.
21:57:07 Action CleanUpInstall:
21:57:07 C:WINDOWSTEMPSqlSetupBinscm.exe -Silent 1 -Action 4 -Service SQLSERVERAGENT
21:57:07 Process Exit Code: (1060) The specified service does not exist as an installed service.
21:57:07 C:WINDOWSTEMPSqlSetupBinscm.exe -Silent 1 -Action 4 -Service MSSQLSERVER
21:57:07 Process Exit Code: (0)
21:57:07 StatsGenerate returned: 2
21:57:07 StatsGenerate (0x0,0x1,0xf000000,0x200,1033,303,0x0,0x1,0,0,0
21:57:07 StatsGenerate -1,debbie)
21:57:07 Installation Failed.
View 1 Replies
View Related
Jun 17, 2005
I have a windows 2003 server with the latest service pack and patches. This server also acts a domain controller.
View 4 Replies
View Related
Feb 25, 2004
I have been using MSDE and I recently got Microsoft SQL ServerTM 2000 Developer Edition as part of my MAPS pack. Can and should I replace MSDE with Microsoft SQL Server 2000 Developer Edition on my development pc? Thanks in advance for any advice on pros and cons or known issues?
View 4 Replies
View Related
Mar 16, 2007
When come to Create Instances screen and click next it prompt error message
although i had restart my computer.
A previous program Installation created pending file operations on the installation machine. You must restart the computer before running setup.
View 2 Replies
View Related
