How To Get The Default SA Account Password And How To Change It In Sql 2000 Personal Edition ?

May 9, 2005

hi, all:

         I installed a Sql 2000 Personal Edition in my Laptop,now I want to change my Sql 2000 sa account password.

         but I can not find where I can get the default password for sa account and how to change it .

 

         thanks

View 1 Replies


ADVERTISEMENT

Upgrade SQL 2000 Personal Edition To SQL 2000 Standard Edition

Apr 22, 2008

I am getting the following warning on a Live SQL 2000 system:
This SQL Server has been optimized for 8 concurrent queries. This limit has been exceeded by 1 queries and performance may be adversely affected.
Reading about this error I realised that, by mistake, the version installed is a personal edition instead of the standard edition.
I am thinking to backup the databases, uninstall SQL 2000 Personal edition, install Standard edition and restore the databases back.
OR, disconnect the databases, uninstall the current version, install the standard version and re-connect the databases.
I haven't found within Microsoft any advice how to upgrade the personal version to the standard edition.
Because it is a live system, I would not like to mess the system up. Can you please advice?
Many thanks

View 5 Replies View Related

Default Password For Sa Account

Oct 25, 2004

Hai,

While installing SQL Server 2000 on my Windows 2000 Advanced Server, i choose Windows Authentication mode, so i was not able to enter a password for sa account. And after installation, in Enterprise Manager i could still see sa account under logins but the account has a password.

So my question is what is the default password for sa account when we choose Windows Authentication mode and is it possible to change the mode from windows Authentication to Mixed Authentication mode after installation, with out re-installaing SQL Server 2000.

Thank you in advance
With regards
Sudar

View 8 Replies View Related

SQL Server 2000 Personal Edition

Feb 6, 2008

One of my clients has an application that only requires €œSQL Server 2000 Personal Edition€? (the new versions of SQL are not supported). Tried going to Microsoft€™s download center to get €œSQL Server 2000 Personal Edition€?, but all I found were the service packs. I also talked to the client about getting an updated version of the application he is using, but it is not cost effective. Does anyone know where I can get/buy a copy of €œSQL Server 2000 Personal Edition€?? Thanks for your help and time.

View 1 Replies View Related

SQL Server 2000 Personal Edition

Nov 20, 2007

Hi,
May i know whether SQL Server 2000 Personal Edition is a freeware?
If i install it with the Analysis Services, will it still be considered as freeware?
Thank you.

Regards,
Chong

View 1 Replies View Related

Networking With Personal Edition Sql Server 2000

Apr 26, 2002

I am using the personal edition of sql server 2000 and i have a number of databases stored on the harddrive, how would i set up a connection with other PC's to be able to view/modify/delete the data through an access 2000 front end. The other PC's will not have SQL server on them but will have Access 2000, they will need to go via the network which is non-microsoft compliant.

Thank you very much for you help it would be very much appreciated.

Britta

View 1 Replies View Related

Sys Admin Account Password Change

Jun 20, 2000

If someone can tell if it is wise change the SA account password after all of your databases have been set up using NT Authentication for login. Also, by using the sa password at login are you providing more security and and who should have access to that password (Your developers or your Administrators?)

Thanks

View 3 Replies View Related

Service Account Password Change - Help!

Dec 3, 1999

Ugh! Someone changed the password of our SQL Server service account. It is called syssql, and it is used by the MSSQLServer and SQL Executive services to log in at startup. After the password was changed, we noticed that replication wasn’t running, and since I know that replication uses the Executive service, I restarted that service using the new password. That worked to get replication working again, and since the boxes were production machines I didn’t restart the MSSQLServer service with the new password yet. Now, our syssql account keeps on locking up every so often, and scheduled tasks that use xp_sendmail stopped working, and alerts stopped sending. Is this happening because of the MSSQLServer service still being logged in with the old password? I suspect that the SQL Mail logs in through the MSSQLServer service, which is still using the old password, and the login failures are causing the syssql account to lock. Any other ideas???

Cindy Rutherfurd
cindy.rutherfurd@zcsterling.com

View 2 Replies View Related

How To Change The User Account And Password

May 23, 2008

HI,

I m swagatika and working on a s/w company.I am facing some problem in MS SqlServer2005.

my problem is:-

i installed sql server2005 completely .At the install time , i set the username='xyz' and password=blank (windows authentication mode).

Now i want to change my user account to 'sa' and password to blank.

After installation,how to change the user account and password.

Please can anybody help me ?

View 3 Replies View Related

Installing SQL Server 2000 Personal Edition On Windows XP SP1

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

Has Sql Server 2000 Personal Edition Any User Limits?

Jan 7, 2008


I have installed Sql Server 2000 Personal Edition (Version: 8.00.2039 SP4 Personal Edition), it runs over Windows XP.
Has Sql Server 2000 Personal Edition any user limits?
Thanks for reply
Ariel

View 6 Replies View Related

Sql Server Services Account Password Change.

Sep 21, 2000

A former Network Manager setup the Sql Server Services NT Domain account. I need the password to set it up on our MS Exchange server, should I change the password or create a new domain account.
How can I find out if there is no other applications using the service account in our domain, since the new Network manager doesn't know the password.
What happens if I change the password.

View 2 Replies View Related

How Do I Change The Password Of A DB Account Using Management Studio Express??

Apr 22, 2008

I can get to the DB and find the user account, but I see nowhere to change the password? My app requires a password that meets Windows Security requirements and the one that was initially created is not long enough.....

View 1 Replies View Related

Change Password On Sql 2000?

Apr 4, 2008

I am trying to change password, using the code below.. The code below is in a stored proc and I am passing these parameters from a web application.....
 sp_password [ [ @old = ] 'old_password' , ]     { [ @new =] 'new_password' }     [ , [ @loginame = ] 'login' ]
 
sp_password 'cust1','cust2','cust1'
Server: Msg 15210, Level 16, State 1, Procedure sp_password, Line 20Only members of the sysadmin role can use the loginame option. The password was not changed.
I made my user part of the db_securityadmin role, but that does not help...
How can I give the above mentioned permissions, so that when user cust1 logs on then he can chnage his own password from the web application as long he has given his old password correctly?
 

View 3 Replies View Related

SQL 2000 Password Change Form...?!?

Jul 23, 2007

I am looking to create an ASP w/ functionality to change user's SQL password.  Many do not have access to EM or Query Analyzer and need a website to visit.  Has any had expirience w/ this prior?

View 19 Replies View Related

Microsoft SQL Server 2000 Can't Stand Up After Change Administrator Password?!?!

Jul 20, 2005

HI!I have a little problem:I have change the administrator password (Windows 2003 Server) which MSSQL 2000 use to login.And now the SQL server can't stand up.What should I do?thx!gicio--Posted via http://dbforums.com

View 1 Replies View Related

SQL 2000 Edition Change

Apr 21, 2006

I accidently installed SQL 2000 Enterprise Edition instead of the Standard Edition. If I uninstall Enterpise and then install Standard, can I restore the system databases, ie master, model, msdb? Are they compatible?

View 4 Replies View Related

Personal Edition?

Jul 10, 2006

What are the main differences with personal edition compared to standard edition?

Will be grateful for answers!

Regards,
Marius

View 1 Replies View Related

SQL Server Personal Edition

Mar 31, 2004

Does anyone have any pointers on where I can find out exactly what we're allowed to do with this product? For example, we sell systems based on Microsoft Small Business Server 2000, which includes SQL Server standard edition. If I want to have, say, a branch system which replicates data to the main SBS system, but run it on XP Pro and use a couple of PCs for workstations, can I use SQL PE, or do I have to use SBS on the branch as well? What about if I have two branches? Or five? Does the fact that we're using SBS make any difference? At the moment, where possible, our branch in that scenario might use the MSDE, but that is limited to a 2Gb database which isn't always useful.

Your thoughts would be most welcome. The Microsoft web site doesn't specifically say what we can and cannot do here, or if it does I haven't found it yet. We're in the UK, if that affects licensing information.

View 3 Replies View Related

How To Change The Default Backup Data Directory In SQL Server 2000?

Dec 29, 2006

Hi,

I had SQL Server 2000 installed like below:

Installation Directory = C:Program FilesMicrosoft SQL Server

Default data directory = D:

Default log directory = D:

I found out that the data is stored in D:Program FilesMicrosoft SQL ServerMSSQLdata and backup is done in D:Program FilesMicrosoft SQL ServerMSSQLackup

However, Microsoft says we should never put the ..ackup and ..data folders in the same partition.

My question is: How can I move the path of the backup directory?

I checked the registy but this is what I found:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSSQLServerMSSQLServer

..BackupDirectory=C:Program FilesMicrosoft SQL ServerMSSQLackup (<-- note it is pointing to C: not D:)

..DefaultData=D:

Can somebody help please?

View 3 Replies View Related

Installing Personal Edition On NT4 Wkstn

Jul 23, 2002

The rap from Microsoft is that "SQL Server 2000 Personal Edition is not a separate product but rather a client component of SQL Server 2000 (included as part of the Enterprise and Standard Editions) that is designed to bring SQL Server 2000 functionality to non-server hardware, including workstations and laptops."

I have a copy of SQL2K Standard, but when I try to install it on a workstation it tells me it'll install client tools only. I've searched Microsoft and don't see any downloads for SQL2K PE.

I need the server component on an NT4 Workstation; what's the trick in getting PE installed on an NT4 Workstation?

Al

View 1 Replies View Related

Personal Edition Then Move To Enterprise

Jul 23, 2005

Hello,Could i start work with personal edition then move all data toenterprise edition ? i've to design and code on workgroup environmentthen implement to windows server 2003. Do i just cut & paste data ?TIAPong

View 1 Replies View Related

Change Sql Server 2000 Enterprise To Standard Edition

Sep 6, 2007

Hi,
One of our main servers running on SQL Server 2000 Enterprise edition which has transactional replications on it which replicates to other servers running on the SQL Server 2000 Enterprise edition as well.

Due to Hardware problems the server is being migrated to a new machine but the client has installed SQL Server 2000 standard edition on the new machine.


We will be using a two processor cpu with 4GB RAM and we are also not planning about clustering. Is there any problem if i migrate the server in Standard Edition will the replications work properly between Standard and Enterprise editions.

What other complications can be there if i switch over to standard edition from enterprise edition

Thanks in ADVANCE

Jacx

View 1 Replies View Related

Update SQL Personal Edition Service Pack 3

Dec 7, 2004

Please do not tell me to go to the MS site coz I did not see any helpful step by step how to install this service pack to my SQL Personal Edition. So please anyone, SQL Guru, post here how to install the SP3 for PERSONAL EDITION - not the DESKTOP Engine. Thank you so much...

View 3 Replies View Related

SQL Server Personal Edition Error 1069

Apr 1, 2004

I have just installed the personal edition on a win xp pro PC, the installation seemed to work ok but when I try to start SQL in the Service Manager I get the following error:

"service did not start due to login failure - error 1069"

I have already got the Enterprise Edition installed on a win 2000 server which has been working nicely and used the same settings on the new xp PC, could this be the problem. I installed it using the domain user accout and SQL server authentication.

Anyone know how I can fix this?

Thanks

View 1 Replies View Related

SA Account (DBA System Account) Granting Priveleges But SQL Server 2000 Not Applying Them

Dec 4, 2006

I have been running a script in SQL Server 2000 as sa also as a Active Directory user who has administrator rights (I tested both approaches SQL Server then Windows Authentication) in Query Analyser which grants execute rights to the stored procedures within the database instance and Query Analyser does not give any errors when I run the script. I have made sure that each transaction has a go after it. I then return to Enterprise Manager, check the rights (I apply them to roles so that when we create another SQL Server user we just grant him/her rights to the role) and discover that the role has not been granted the rights. I seems to be occurring only with 2 of the procedures. Is there a known bug that might be causing this?

yours sincerely

Craig Hoy

View 9 Replies View Related

SQL 2000 Personal Editon And XP Pro

Feb 12, 2004

I just installed SQL 2000 personal edition on a win xp pro box and now when it boots I get a SQL service manager error that says service manager has generated errors and needs to be closed.

Is there anything particular with XP and SQL 2000 i need to know?

I thought this would be a no brainer as it was with Win2k, but no.

MD, MCSA/MCSE WIN2K

View 2 Replies View Related

Deployment Of SQL 2000 Server Personal

Mar 28, 2008



Hi everyone,

I would like to know how I can deploy Microsoft SQL 2000 Server Personal edition using SMS 2003 Sp2.

When I map a drive and I execute my batch file it install SQL 2000 correctly but when I try to deploy SQL 2000 server personal edition using SMS 2003, It said that I deployed successfully sql 2000 server but when I look into my client computer, it didn't install SQL so this is the problem I have.

anyone can help me?

Best regards

View 1 Replies View Related

Sa Account Password

Aug 10, 1998

Well, I inherited a SQL Server ....sob story.........installer won`t call back.....sob story.....buying books like mad......sob story. Geez, this was a *great* job when I interviewed.....

Regardless, I do not know the password for the sa account on a SQL 6.5 server running on NT4SP3. We are using standard securtiy. Do I have any options?

Hopefully, the technical discussion doesn`t reference rubber garden watering implements. :{)

Thanks,
steve

View 5 Replies View Related

SQL Server 2000 Std Ed/Personal Ed Install Problem

Jul 1, 2004

I already had MSDE installed on my laptop and I was trying to load the Client Tools. I stopped the MSDE service, then tried to install the Client Tools from the SQL Server 2000 Standard Edition (Personal Edition) CD. Near the end of the install, I received an error telling me that the C:Program FilesCommon FilesMicrosoft SharedSQL Debuggingsqldbg.dll file was in use and it would not complete the install.

So, I removed the MSDE thru Add/Remove programs, rebooted, then tried to install SQL Server 2000 Std Ed (Personal Ed) and the Client Tools from the CD. Same error message. I used My Computer to try to go to that folder and see the sqldbg.dll file, but when I try to open the folder it tells me "Access is denied".

Obviously, something is using this file, but I'm not sure where to go from here. Any suggestions?

Thanks,

Chris

View 1 Replies View Related

Problem In Installing SQL Server 2000 Personal

Aug 23, 2007

Hi... I recently reformatted my pc due to a very slow operation. Then I reinstall SQL Server 2000 Personal to my PC running Windows XP OS....As I run the setup, it will display INTERNAL ERROR and won't continue... What seemed to be the problem there? Before I reformatted the PC, it was installed well...

View 6 Replies View Related

Service Account Password

Jan 22, 2002

Folks,

MSSQLServer and SQL Server Agent services under NT are running under a system account under our domain (setup many moons ago) for which we have lost the passsword. Is there any way we can recover these passwords?


Thanks.

Sam

View 1 Replies View Related

The Password Of The Account Must Be Changed

Feb 26, 2007

I am trying to adapt a vb6 application to support sqls 2005 features. I am using SQL Server Authentication and want to support the feature which forces the user to change his password on the next login. Using an SQLOLEDB connection string, on trying to log I get an error saying that the password must be changed - fair enough - but how can I do this? I would have expected to be able to supply both old and new passwords in the connection string, but there does not seem to be any such feature. Am I missing something obvious?

View 8 Replies View Related







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