Qustion On Installing SQL Exxpress Edition
Feb 24, 2008
I'm thinking of learning Sql. I have Server management studio: express and I'm trying to install Sql express. I have the some of the things that come in the install program in SQLEXPR ( Sql express), I get to where I get to a few thing to pick the fetures to install and componets to andstall and then I get this error " TITLE: Microsoft SQL Server Setup
------------------------------
None of the selected features can be installed or upgraded. Setup cannot proceed since no effective change is being made to the machine. To continue, click Back and then select features to install. To exit SQL Server Setup, click Cancel.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=SQLSetup90&EvtType=28108
"Can I only have either express or server manegment or is only one of them for programing? I already have the SQL componet from C# express and VWD 2008 express if that helps at all.
View 3 Replies
ADVERTISEMENT
Jan 22, 2008
Hi
-I have istalled sql server 2005 standard edition , I want to install sql server 2005 enterprise edition on the same machine.
Is it possible? I have Microsoft windows server 2003 SP2 and 1GB RAM.
I want to use partition function with the enterprise edition, will the trial version of sql server work for me?
-If I have already created a database and tables using the standard edition, will I be able to access and use the database using the installed trial version or will I have to start a fresh creating a new database?
- Is it possible to access the same database with any of the installed versions?
BTW, I am prety new to sql server and databases , I am trying to learn by myself
Thanks
View 9 Replies
View Related
Dec 21, 2001
Is that OK to run dbreindex every 24 hours on heavily modified/inserted tables?Does that harm anyway?Gurus advice needed!
thanks.
View 1 Replies
View Related
Sep 28, 2007
How am I configuring permission for an SQL database, that user within my program should'nt read private information?
as well how can I protect my database with a UN & PWD to allow access only for authenticated users, not within the program, just the *.mdf file?
View 7 Replies
View Related
Apr 10, 2007
I am a contract software designer, servicing multiple industries and multiple sizes within those industries. I need a way to develop and test on both SQL Server Developer edition, and SQL Server Express. Is it possible to install these two editions side-by-side for the purposes of development?
Do I need to have them installed on separate computers?
View 3 Replies
View Related
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
May 6, 2007
Hi guys,
I'm trying to create a all-in-one installation package for my application which make use of the SQL 2005 Express edition. It seems that there's no way to roll my application MSI installation with the database engine, the only ways around this problem is to use a bootstrap exe to launch the sql setup before or after my main application's MSI. This works fine during installation and I have modified the original .NET framework bootstrapper to do just that.
The problem comes when uninstalling my application. Since the uninstall process is all done through the MSI engine, how would I take the sql instance with me during my application's uninstall? Since the sql engine is also based on MSI technology, I won't be able to do that during the removal step of my application's MSI, right? Any one know any "clean" ways around that? Besides not letting users uninstall my application directly from Add/Remove program and force them to call another exe simular to my installation bootstrap?
I'm considering to use 3rd party tools like InstallShields, but even them are recommending people to stay with the MSI technology which is where the problem is. I'm running out of ideas really fast...
Thanks in advance!
William
View 1 Replies
View Related
Jun 15, 2006
When I try to Install SQL Server expres edition I keep on getting this error: http://www.fambouman.com/SQLError.JPG
I'am running Windows SBS 2003 fully updated via windows update.. When I go to the URL mentioned in the error I get an error and the browser redirects to microsoft search.
Anybody know how I can setup SQL Expres ? I need it for dotnetnuke to run.
Thanks in advance
View 4 Replies
View Related
Dec 1, 2007
I have Windows Vista Home Premium, with Visual Studio 2005 installed, and SQL Server Express Edition installed. What I want to do is upgrade to SQL Server Express Edition SP2. I understand that I can install SP2 on top of SQL Server Express Edition. However, there are just a couple of areas that I'd like assurances on (have never used SQL Server):
1. Since all my work with SQL Server Express Edition SP2 will be done via the Visual Studio 2005 IDE, does that mean that I don't need to download and install SQL Server Management Studio Express? The Management Studio seems to be more for a standalone development environment. I just want to make sure about this.
2. Also, the information on the information page about Windows Vista issues with User Account Control is not specific to SQL Express Edition SP2. There's a lot of generic and, quite frankly, very abstract information that is hard to understand. For now I'm just planning to install SQL Server and leave it at that, unconfigured, in whatever state the install leaves it at. I am hoping against hope that I will be able to familiarize myself with SQL Server via the Microsoft Visual C# 2005 Step-by-Step book, which is why I'm upgrading to SQL Server Express Edition SP2 in the first place. I'll glean what I can about configuration in the SQL Server Express Edition SP2 docs, but what are the chances that I'll find anything that is specific to using the database soley with Visual Studio 2005? Perhaps I'll be pleasantly surprised. About the User Account control issues, are there are any articles that specifically discuss User Account control issues that are associated with SQL Server Express Edition SP2?
Sorry about the windage. I'm a little cranky after spending about 2 hours clicking from one link to another.
Ed
View 1 Replies
View Related
Dec 3, 2006
I have Visual Web Developer 2005 Express edition and I wanted to install SQL Server 2005 Express edition.From this page, I have downloaded and installed 'Microsoft SQL
Server 2005 Express Edition' and 'Microsoft SQL
Server 2005 Express Edition with Advanced Services http://msdn.microsoft.com/vstudio/express/sql/download/After the installation, how should I access the SQL Server 2005 Express edition?Because the only thing listed in 'Start > All Programs > SQL Server 2005' is 'Configuration Tools'I was hoping that when I install SQL Server 2005 express edition, I would get all the menu that I get by installing SQL Server 2000.So after installing SQL Server 2005 Express edition, what should I be expection? Thanks
View 4 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
Jul 22, 2007
Dear all,
This is the first time using this forum, I hope I can get some help.
I have started studying SLQ Server 2000 at home as I have a Video Tutorial but I thought I need to install SLQ Server 2000 to follow the training. I have been trying to instal SLQ Server 2000 Enterprise Edition on both Windows XP Pro Pack2 and Windows 2000 but I get this message saying "Microsoft SQL server 2000 enterprise edition server component is not supported on this operating system only client component will be available for installation "
I do not know anything about SQL and I thought I must have been doing something wrong otherwise it would not give me the same warning on both operating systems.
I do not know what is it I do wrong and I would appreciate your help and assistance.
Thank you
View 2 Replies
View Related
Dec 15, 2006
Hi,
Having read a lot about SQL Server 2005 CE, I decided, after seing that it was finally available, to start its installation.
1- I downloaded and installed SQL Server 2005 Compact Edition from following link:
http://www.microsoft.com/downloads/details.aspx?FamilyId=85E0C3CE-3FA1-453A-8CE9-AF6CA20946C3&displaylang=en
2- Also I downloaded and installed SQL Server 2005 Compact Edition books online from following link:
http://www.microsoft.com/downloads/details.aspx?FamilyId=E6BC81E8-175B-46EA-86A0-C9DACAA84C85&displaylang=en
==> Is there anything else missing if I intend to use it for development with Visual Studio 2005 (VC++)?
==> What is "Microsoft SQL Server 2005 Compact Edition Developer SDK" compared to the one "SQL Server 2005 Compact Edition" I installed? Should I install it?
ref: (http://www.microsoft.com/downloads/details.aspx?FamilyId=E9AA3F8D-363D-49F3-AE89-64E1D149E09B&displaylang=en)
3- There is also a link, which btw doesn't work at all, that should allow me to download following item:
"Microsoft SQL Server 2005 Compact Edition Tools of VS 2005 sp1"
==> Not being able to have any infos about it, what is the use of it? Should I install it in my environment? If so, any working link where I can download it from?
4- I finally noted, while browsing through SQL Server 2005 CE books online, the following note:
The following programming models are supported by SQL Server Compact Edition:
ADO .NET, accessible by using C# or Microsoft Visual Basic
OLE DB, accessible by using Visual C++ option from within Visual Studio 2005
==> How come that CE is not accessible using ADO.NET model when using VC++?
Thanks in advance,
Stéphane
View 9 Replies
View Related
Nov 21, 2006
I am having issues installing SQL 2005 DEV ED. on Vista RTM. During the install of the Native Client I recieve the following error which seems to mees up the rest of the intall package.
An installation package for the product Microsoft SQL Server Native client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'.
I downloaded vista and sql 2005 developer edition and both are burned to a DVD.
View 5 Replies
View Related
Mar 28, 2007
I have a PDA application that manage a database.
My application uses Sql server 2005 Mobile edition and I want to change to
Sql server 2005 Compact edition.
I have an application that automatically upgrade new version of my software at users (customers sites) It is shipped on a memrory card (SD Card).
I want in my upgrade tool to install Sql server 2005 Compact edition so I do it by running the two cab files :
sqlce30.repl.wce5.armv4i.CAB and sqlce30.wce5.armv4i.CAB
It works ok but I want also to uninstall Sql server 2005 Mobile edition and I do not find out how to do it automatically, First I do not know how to find out if Sql server 2005 Mobile edition is installd and if so how to uninstall it.
I want to do it all automatcally in my upgrade utility because my customers do not know to do it manually by theself.
Second I want to know if I have to use the Sql server 2005 Compact edition Uprade tool to upgrade my clients old databases because the now application works ok without Upgrading the database.
Thanks
Ofer Ebert
View 7 Replies
View Related
Feb 14, 2007
Hi
I have installed SQL Server Express 2005 on my machine.
I want to install SQL Server Standard Edition 2005 on my machine to check new services it has.
Can these 2 Editions coexist with each other, or any troubles you think might encounter?
Thanks
View 5 Replies
View Related
Dec 3, 2007
I have downloaded a free set of SQL Server 2005 Express edition. This set up has been installed successfully on my machine but it is showing me following links.
SQL Server Instance=SQLExpress
User Id=sa
Password=admin12
Start ---> Microsoft Sql Server 2005 --->Configuration Tools ------->SQL Server Configuration Manager
--------->SQL Server Eroor and Usage Reporting
----------->SQL Server Surface Area Configuration
But I don't find any option to start SQL Server 2005 express edition. Please help me out how to start SQL Server 2005 express edition?
View 5 Replies
View Related
Apr 12, 2005
My Problems & Situation:Hi! I am a ASP.NET starter. My platform is WinXP Home Edition and I haven't installed any version of SQL server before.I download different version of MSDE and extracted in my C drive separately, including: 1. Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Release A 2. Microsoft SQL Server 2000 Service Pack 3a (contained MSDE 2000) 3. MSDE 2000 for Developers Using Visual Studio .NETsince all of the above versions have the same problem when I try to install it.
The problem is that when I double click each of the setup.exe, it will show a pop up error:[A strong SA password is requires for security reasons. Please use SAPWD switch to supply the same. Refer to readme for more details. Setup will now exit.]
Then I found a solution from Microsoft, it told me that: 1. Run the setup in the command prompt 2. Locate in the extracted path 3. type --> "Setup.exe /qb+ INSTANCENAME=NetSDK DISABLENETWORKPROTOCOLS=1 SAPWD=<pwd>"
p.s. I have changed the <pwd> to 123abc
However....another Error Occur:1st pop up --> [Unable to determine system default collation.]2nd pop up --> [Microsoft SQL Server Desktop Engine Setup failed.]
My Question:1. Why the error still occour when I type that command to setup? (Solution from Microsoft)2. How can I fix it and complete the installation?3. How many users(maximum) can be created in a MSDE database?
Greateful if anyone can give me hand.
View 3 Replies
View Related
Apr 18, 2008
Would there be any issues with installing an MSSQL 2000 32 bit instance onto a windows 2003 64 bit server?
View 5 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
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
Apr 30, 2007
Dear Sir
How could I install the Microsoft SQL Server 2005 Enterprise edition on Microsoft windows Vista any edition?
I'd be thankful if you could tell me how to do that.
Best Regards.
View 1 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
Apr 4, 2007
I am trying to install sql server 2005 express edition.But i get an error stating that
sql server setup unexpectedly failed. For more information review the detup summary log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGsummary.txt
Summary.txt looks like this.It has only these 3 lines of information nothing else other this, which i have seen in many posts.
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)
Time : Tue Apr 03 22:36:33 2007
I am using windows xp. Probably many of you might have had this problem.Could anyone please provide me with some help.Thanks in advance.
View 3 Replies
View Related
Apr 3, 2007
So after getting no resolution to my previous problems installing SQL Express SP2 after having applied SP2 to the Developer SKU and needing Express for demo purposes (at a conference amusingly held at an MS regional office) I decided to start again.
After some struggles I uninstalled SQL Server (it crashed during uninstall, and I had to manually remove all the registry entries and clean up the directories).
Sql Express SP2 installed fine, but now developer edition refuses to install; more specifically the Management Tools and documentation portion. Absolutely stunning.
I found one problem in that the install would not proceed (installing the engine) because a more recent version of SQLXML was installed, which I got past by uninstalling the SQLXML installation Express had put onto the machine.
However now I am stuck without any management tools whatsoever (although books on-line installed).
Is it so hard to install two Microsoft products side by side? I am tearing my hair out here and utterly sick of this, especially as last time I tried to log a support call with the Express issue MS support refused to take it (despite having incident calls to burn)
Machine : PUCK
Product : Workstation Components, Books Online and Development Tools
Error : There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.
--------------------------------------------------------------------------------
<EndFunc Name='Set_CommitFlag' Return='0' GetLastError='0'>
PerfTime Stop: Set_CommitFlag : Tue Apr 03 13:22:47 2007
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (60:E8) [13:22:47:609]: Note: 1: 1722 2: SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A 3: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe 4: /setup
MSI (s) (60:E8) [13:22:47:640]: Transforming table Error.
MSI (s) (60:E8) [13:22:47:656]: Transforming table Error.
MSI (s) (60:E8) [13:22:47:656]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (60:E8) [13:22:47:656]: Transforming table Error.
MSI (s) (60:E8) [13:22:47:656]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (60:E8) [13:22:47:656]: Transforming table Error.
MSI (s) (60:E8) [13:22:47:656]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (60:E8) [13:22:52:203]: Transforming table Error.
MSI (s) (60:E8) [13:22:52:203]: Transforming table Error.
MSI (s) (60:E8) [13:22:52:203]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (60:E8) [13:22:52:203]: Transforming table Error.
MSI (s) (60:E8) [13:22:52:203]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (60:E8) [13:22:52:203]: Transforming table Error.
MSI (s) (60:E8) [13:22:52:203]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (60:E8) [13:22:52:203]: Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
The problem seems to be in setting up the workbench. Could this be because I already have Visual Studio SP1 installed?
View 1 Replies
View Related
May 23, 2007
When i install sql server 2000 i have a message
" Microsoft SQL Server 2000 Standard Edition Server Component is not supported on this operating system only client components will be available for installation"
Hence I cannot install properly. I installed only the client componets. Thereafter when I went through Enterprise Manager and tried to establish a connection, I failed. It said server does not exist.
What to do now?
I found out that if one has sql server 2000 standard editon the prerequisties are
Microsoft Windows NT Server 4.0 with Service Pack 5 or later, Windows NT Server 4.0 Enterprise Edition with Service Pack 5 or later, Windows 2000 Server, Windows 2000 Advanced Server, or Windows 2000 Datacenter Server.
I have windows xp professional version on which i am installing sql server standard edition.
Which of the above exists in my OS. Or which should I download.
Thanks
View 1 Replies
View Related
Sep 13, 2006
hi,
I have SQL Server Express edition installed on my PC , but now I need to use SQL Server reporting service, there is SP1 for express edition contains reporting service with express edition. Here..
http://msdn.microsoft.com/vstudio/express/sql/download/
Do I need to download 213 MB SQL Server 2005 Express Edition Toolkit SP1 ?
or there is any other method to use reporting services ?
Thanks
View 1 Replies
View Related
Dec 20, 2005
I encountered an error when attempting to install Visual Basic Express Edition RTM. During the setup, I selected MSDN Express Edition and SQL Server 2005 Express Edition. Specifically, the SQL Server 2005 EE part of the installation failed. Here's the error I received:
Visual Basic 2005 Express Edition Setup
Error occurred during setup
Visual Basic 2005 Express Edition has been successfully installed.
The following component failed to install:
Microsoft SQL Server 2005 Express Edition x86
I had not installed any betas on this particular PC; however, I had already installed Visual Studio 2005 Pro and SQL Server 2005 Developer Edition.
(I selected SQL Server EE during the VBEE install because the VBEE readme said that the VSEE Editions (except for VWD) only work with SQL Server EE--so I figured I had to install SQL Server EE if I wanted to do any database work with VBEE. Is that the case?)
The following two log files were the only ones containing any error messages. How should I proceed?
C:Program Filesmicrosoft sql server90setup bootstraplogfilesSQLSetup0003_US05046_Core.log:
Microsoft SQL Server 2005 Setup beginning at Mon Dec 19 14:40:32 2005
Process ID : 5824
c:211395ac6e4ed715363fsetup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2005/11/19 14:40:31
Complete: LoadResourcesAction at: 2005/11/19 14:40:31, returned true
Running: ParseBootstrapOptionsAction at: 2005/11/19 14:40:31
Loaded DLL:c:211395ac6e4ed715363fxmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2005/11/19 14:40:32, returned true
Running: ValidateWinNTAction at: 2005/11/19 14:40:32
Complete: ValidateWinNTAction at: 2005/11/19 14:40:32, returned true
Running: ValidateMinOSAction at: 2005/11/19 14:40:32
Complete: ValidateMinOSAction at: 2005/11/19 14:40:32, returned true
Running: PerformSCCAction at: 2005/11/19 14:40:32
Complete: PerformSCCAction at: 2005/11/19 14:40:32, returned true
Running: ActivateLoggingAction at: 2005/11/19 14:40:32
Complete: ActivateLoggingAction at: 2005/11/19 14:40:32, returned true
Running: DetectPatchedBootstrapAction at: 2005/11/19 14:40:32
Complete: DetectPatchedBootstrapAction at: 2005/11/19 14:40:32, returned true
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__5824" returned false.
Running: PerformSCCAction2 at: 2005/11/19 14:40:32
Loaded DLL:C:WINNTsystem32msi.dll Version:3.1.4000.2435
Loaded DLL:C:WINNTsystem32msi.dll Version:3.1.4000.2435
Complete: PerformSCCAction2 at: 2005/11/19 14:40:33, returned true
Running: PerformDotNetCheck at: 2005/11/19 14:40:33
Complete: PerformDotNetCheck at: 2005/11/19 14:40:33, returned true
Running: ComponentUpdateAction at: 2005/11/19 14:40:33
Complete: ComponentUpdateAction at: 2005/11/19 14:41:6, returned true
Running: DetectLocalBootstrapAction at: 2005/11/19 14:41:6
Complete: DetectLocalBootstrapAction at: 2005/11/19 14:41:6, returned true
Running: LaunchLocalBootstrapAction at: 2005/11/19 14:41:6
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"c:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 1706
Aborting queue processing as nested installer has completed
Message pump returning: 1706
C:Program Filesmicrosoft sql server90setup bootstraplogfilesSQLSetup0003_US05046_Core(Local).log:
Microsoft SQL Server 2005 Setup beginning at Mon Dec 19 14:41:10 2005
Process ID : 5476
c:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2005/11/19 14:41:9
Complete: LoadResourcesAction at: 2005/11/19 14:41:9, returned true
Running: ParseBootstrapOptionsAction at: 2005/11/19 14:41:9
Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapxmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2005/11/19 14:41:9, returned true
Running: ValidateWinNTAction at: 2005/11/19 14:41:9
Complete: ValidateWinNTAction at: 2005/11/19 14:41:9, returned true
Running: ValidateMinOSAction at: 2005/11/19 14:41:9
Complete: ValidateMinOSAction at: 2005/11/19 14:41:9, returned true
Running: PerformSCCAction at: 2005/11/19 14:41:9
Complete: PerformSCCAction at: 2005/11/19 14:41:9, returned true
Running: ActivateLoggingAction at: 2005/11/19 14:41:9
Complete: ActivateLoggingAction at: 2005/11/19 14:41:10, returned true
Running: DetectPatchedBootstrapAction at: 2005/11/19 14:41:10
Complete: DetectPatchedBootstrapAction at: 2005/11/19 14:41:10, returned true
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__5476" returned false.
Action "BeginBootstrapLogicStage" will be skipped due to the following restrictions:
Condition "Setup is running locally." returned true.
Running: PerformDotNetCheck2 at: 2005/11/19 14:41:10
Complete: PerformDotNetCheck2 at: 2005/11/19 14:41:12, returned true
Running: InvokeSqlSetupDllAction at: 2005/11/19 14:41:12
Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlspars.dll Version:2005.90.1399.0
<Func Name='DwLaunchMsiExec'>
Examining 'sqlspars' globals to initialize 'SetupStateScope'
Opening 'MachineConfigScope' for [US05046]
Trying to find Product Code from command line or passed transform
If possible, determine install id and type
Trying to find Instance Name from command line.
No Instance Name provided on the command line
If possible, determine action
Machine = US05046, Article = WMIServiceWin32OSWorking, Result = 0 (0x0)
Machine = US05046, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0)
Machine = US05046, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0)
Machine = US05046, Article = WMIServiceReadRegWorking, Result = 0 (0x0)
Machine = US05046, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0)
Machine = US05046, Article = WMIServiceCIMDataWorking, Result = 0 (0x0)
Machine = US05046, Article = XMLDomDocument, Result = 0 (0x0)
Machine = US05046, Article = Processor, Result = 0 (0x0)
Machine = US05046, Article = PhysicalMemory, Result = 0 (0x0)
Machine = US05046, Article = DiskFreeSpace, Result = 0 (0x0)
Machine = US05046, Article = OSVersion, Result = 0 (0x0)
Machine = US05046, Article = OSServicePack, Result = 0 (0x0)
Machine = US05046, Article = OSType, Result = 0 (0x0)
Machine = US05046, Article = AdminShare, Result = 0 (0x0)
Machine = US05046, Article = PendingReboot, Result = 0 (0x0)
Machine = US05046, Article = IEVersion, Result = 0 (0x0)
Machine = US05046, Article = DriveWriteAccess, Result = 0 (0x0)
Machine = US05046, Article = COMPlus, Result = 0 (0x0)
Machine = US05046, Article = ASPNETVersionRegistration, Result = 0 (0x0)
*******************************************
Setup Consistency Check Report for Machine: US05046
*******************************************
Article: WMI Service Requirement, Result: CheckPassed
Article: MSXML Requirement, Result: CheckPassed
Article: Operating System Minimum Level Requirement, Result: CheckPassed
Article: Operating System Service Pack Level Requirement, Result: CheckPassed
Article: SQL Compatibility With Operating System, Result: CheckPassed
Article: Minimum Hardware Requirement, Result: CheckPassed
Article: Pending Reboot Requirement, Result: CheckPassed
Article: Default Installation Path Permission Requirement, Result: CheckPassed
Article: Internet Explorer Requirement, Result: CheckPassed
Article: Check COM+ Catalogue, Result: CheckPassed
Article: ASP.Net Registration Requirement, Result: CheckPassed
<Func Name='PerformDetections'>
0
<EndFunc Name='PerformDetections' Return='0' GetLastError='0'>
Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.1399.0
<EndFunc Name='DwLaunchMsiExec' Return='0' GetLastError='0'>
Complete: InvokeSqlSetupDllAction at: 2005/11/19 14:42:59, returned true
Running: SetPackageInstallStateAction at: 2005/11/19 14:42:59
Complete: SetPackageInstallStateAction at: 2005/11/19 14:43:1, returned true
Running: DeterminePackageTransformsAction at: 2005/11/19 14:43:1
Complete: DeterminePackageTransformsAction at: 2005/11/19 14:43:5, returned true
Running: ValidateSetupPropertiesAction at: 2005/11/19 14:43:5
Complete: ValidateSetupPropertiesAction at: 2005/11/19 14:43:5, returned true
Running: OpenPipeAction at: 2005/11/19 14:43:5
Complete: OpenPipeAction at: 2005/11/19 14:43:5, returned false
Error: Action "OpenPipeAction" failed during execution.
Running: CreatePipeAction at: 2005/11/19 14:43:5
Complete: CreatePipeAction at: 2005/11/19 14:43:5, returned false
Error: Action "CreatePipeAction" failed during execution.
Action "RunRemoteSetupAction" will be skipped due to the following restrictions:
Condition "Action: CreatePipeAction has finished and passed." returned false.
Running: PopulateMutatorDbAction at: 2005/11/19 14:43:5
Complete: PopulateMutatorDbAction at: 2005/11/19 14:43:5, returned true
Running: GenerateRequestsAction at: 2005/11/19 14:43:5
SQL_Engine = 3
SQL_Data_Files = 3
SQL_Replication = 3
SQL_FullText = -1
SQL_SharedTools = 3
SQL_BC_DEP = -1
Analysis_Server = -1
AnalysisDataFiles = -1
AnalysisSharedTools = -1
RS_Server = -1
RS_Web_Interface = -1
RS_SharedTools = -1
Notification_Services = -1
NS_Engine = -1
NS_Client = -1
SQL_DTS = -1
Client_Components = 3
Connectivity = 3
SQL_Tools90 = -1
SQL_WarehouseDevWorkbench = -1
SDK = 3
SQLXML = -1
Tools_Legacy = -1
TOOLS_BC_DEP = -1
SQL_Documentation = -1
SQL_BooksOnline = -1
SQL_DatabaseSamples = -1
SQL_AdventureWorksSamples = -1
SQL_AdventureWorksDWSamples = -1
SQL_AdventureWorksASSamples = -1
SQL_Samples = -1
Complete: GenerateRequestsAction at: 2005/11/19 14:43:11, returned true
Running: CreateProgressWindowAction at: 2005/11/19 14:43:11
Complete: CreateProgressWindowAction at: 2005/11/19 14:43:12, returned false
Error: Action "CreateProgressWindowAction" failed during execution.
Running: ScheduleActionAction at: 2005/11/19 14:43:12
Complete: ScheduleActionAction at: 2005/11/19 14:43:13, returned true
Skipped: InstallASAction.11
Skipped: Action "InstallASAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.18
Skipped: Action "InstallASAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.22
Skipped: Action "InstallASAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.9
Skipped: Action "InstallASAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "as", install will be skipped as a result.
Skipped: InstallDTSAction
Skipped: Action "InstallDTSAction" was not run. Information reported during analysis:
No install request found for package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.11
Skipped: Action "InstallDTSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.12
Skipped: Action "InstallDTSAction.12" was not run. Information reported during analysis:
No install request found for package: "sqlncli", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.18
Skipped: Action "InstallDTSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.22
Skipped: Action "InstallDTSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.9
Skipped: Action "InstallDTSAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "dts", install will be skipped as a result.
Skipped: InstallNSAction
Skipped: Action "InstallNSAction" was not run. Information reported during analysis:
No install request found for package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.11
Skipped: Action "InstallNSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.12
Skipped: Action "InstallNSAction.12" was not run. Information reported during analysis:
No install request found for package: "sqlncli", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.18
Skipped: Action "InstallNSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.22
Skipped: Action "InstallNSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.9
Skipped: Action "InstallNSAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "ns", install will be skipped as a result.
Skipped: InstallRSAction.11
Skipped: Action "InstallRSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "rs", install will be skipped as a result.
Skipped: InstallRSAction.18
Skipped: Action "InstallRSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "rs", install will be skipped as a result.
Skipped: InstallRSAction.22
Skipped: Action "InstallRSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "rs", install will be skipped as a result.
Running: InstallSqlAction.11 at: 2005/11/19 14:43:14
Installing: sqlsupport on target: US05046
Complete: InstallSqlAction.11 at: 2005/11/19 14:43:26, returned true
Running: InstallSqlAction.12 at: 2005/11/19 14:43:26
Installing: sqlncli on target: US05046
Complete: InstallSqlAction.12 at: 2005/11/19 14:43:40, returned true
Skipped: InstallSqlAction.18
Skipped: Action "InstallSqlAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "sql", install will be skipped as a result.
Running: InstallSqlAction.21 at: 2005/11/19 14:43:40
Installing: sqlwriter on target: US05046
Failed to install package
Fatal error during installation.
Setting package return code to: 1706
Complete: InstallSqlAction.21 at: 2005/11/19 14:43:50, returned false
Error: Action "InstallSqlAction.21" failed during execution. Error information reported during run:
Target collection includes the local machine.
Invoking installPackage() on local machine.
Skipped: InstallSqlAction.22
Skipped: Action "InstallSqlAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "sql", install will be skipped as a result.
Running: InstallSqlAction.9 at: 2005/11/19 14:43:50
Installing: msxml6 on target: US05046
Complete: InstallSqlAction.9 at: 2005/11/19 14:43:54, returned true
Running: InstallToolsAction.11 at: 2005/11/19 14:43:54
Installing: sqlsupport on target: US05046
Complete: InstallToolsAction.11 at: 2005/11/19 14:44:2, returned true
Running: InstallToolsAction.12 at: 2005/11/19 14:44:2
Installing: sqlncli on target: US05046
Complete: InstallToolsAction.12 at: 2005/11/19 14:44:11, returned true
Skipped: InstallToolsAction.13
Skipped: Action "InstallToolsAction.13" was not run. Information reported during analysis:
No install request found for package: "PPESku", referred by package: "tools", install will be skipped as a result.
Skipped: InstallToolsAction.18
Skipped: Action "InstallToolsAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "tools", install will be skipped as a result.
Skipped: InstallToolsAction.20
Skipped: Action "InstallToolsAction.20" was not run. Information reported during analysis:
No install request found for package: "BOL", referred by package: "tools", install will be skipped as a result.
Skipped: InstallToolsAction.22
Skipped: Action "InstallToolsAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "tools", install will be skipped as a result.
Running: InstallToolsAction.9 at: 2005/11/19 14:44:11
Installing: msxml6 on target: US05046
Complete: InstallToolsAction.9 at: 2005/11/19 14:44:15, returned true
Action "InstallSqlAction" will return false due to the following preconditions:
Condition "Action: InstallSqlAction.21 has finished and failed." returned true.
Installation of package: "sql" failed due to a precondition.
Step "InstallSqlAction" was not able to run.
Skipped: InstallNSAction.10
Skipped: Action "InstallNSAction.10" was not run. Information reported during analysis:
No install request found for package: "sqlxml4", referred by package: "ns", install will be skipped as a result.
Running: InstallToolsAction at: 2005/11/19 14:44:15
Installing: tools on target: US05046
Complete: InstallToolsAction at: 2005/11/19 14:44:26, returned true
Skipped: InstallToolsAction.10
Skipped: Action "InstallToolsAction.10" was not run. Information reported during analysis:
No install request found for package: "sqlxml4", referred by package: "tools", install will be skipped as a result.
Skipped: RepairForBackwardsCompatRedistAction
Skipped: Action "RepairForBackwardsCompatRedistAction" was not run. Information reported during analysis:
Action: "RepairForBackwardsCompatRedistAction" will be skipped due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Error: Action "UninstallForMSDE2000Action" failed during execution. Error information reported during run:
Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchMSDE2000" failed due to a precondition.
Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run:
Action: "UninstallForSQLAction" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchLibertySql" failed due to a precondition.
Skipped: InstallASAction
Skipped: Action "InstallASAction" was not run. Information reported during analysis:
No install request found for package: "as", install will be skipped as a result.
Skipped: InstallRSAction
Skipped: Action "InstallRSAction" was not run. Information reported during analysis:
No install request found for package: "rs", install will be skipped as a result.
Skipped: UninstallForRS2000Action
Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis:
Action: "UninstallForRS2000Action" will be skipped due to the following condition:
Condition "Action: InstallRSAction was skipped." returned true.
Running: ReportChainingResults at: 2005/11/19 14:44:27
Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 1706
Error Code: 0x800706aa (1706)
Windows Error Text: The endpoint format is invalid.
Source File Name: sqlchainingsqlchainingactions.cpp
Compiler Timestamp: Thu Sep 1 22:23:05 2005
Function Name: sqls::ReportChainingResults::perform
Source Line Number: 3097
---- Context -----------------------------------------------
sqls::HostSetupPackageInstallerSynch::postCommit
sqls::HighlyAvailablePackage::preInstall
sqls::HighlyAvailablePackage::manageVsResources
ce: 29539
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_US05046_.NET Framework 2.0.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0003.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2005/11/19 14:44:52
Message pump returning: 1706
View 2 Replies
View Related
Nov 15, 2005
I've installed VS2005 Standard Edition onto a machine running XP Home
View 11 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
Jun 1, 2007
I am dealing with the same issue posted in this other thread that seems to have died with no solution found:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1131407&SiteID=17
Almost as soon as I start to install SQL 2005 on my Windows XP Pro Version 2002 Service Pack 2 machine at work it pops up a dialog with one of the following 2 error messages (they alternate randomly):
The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine PCF092191 Error:2147500034 (0x80004002).
The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine PCF092191 Error:2147749907 (0x80041013).
After clicking OK the installation just closes.
I also discovered when I load wmimgmt.msc and click Properties on the WMI Control, I get the following errors on the General tab, AND it does not allow me to click on any other tabs:
Failed to initialize all required WMI classes.
Win32_Processor: <Null>: No such interface supported
Win32_WMISetting: Successful
Security information: Successful
Win32_OperatingSystem: <Null>: No such interface supported
I have been searching online for days and tried doing virtually everything I found that I could understand and nothing works. Reinstalling WMI off the XP CD doesn't work, rebuilding the WMI repository doesn't work, registering all the WMI DLLs and MOF files doesn't work, running all the various scripts to fix WMI that are posted all over online doesn't work.
I downloaded the Microsoft WMI Diagnostics tool and ran it. It printed a ton of errors in a 466-line report that I can't make head or tail of. 6 here, 33 there, 27 over there...almost too many to count. The suggestions it gives to fix them range from vague and incomplete to incomprehensible. I'll paste those error results into a followup post.
I installed the WMI Tools package and can't figure out what to do with any of the tools at all. The only thing I noticed is that when examining a section under Win32_Processor, most entries for various properties are marked <empty>, while I have seen people discussing what I think are those same properties online and talking about seeing stuff typed into theirs (such as the HostingModel having LocalServiceHost typed in and ImpersonationLevel having 1 typed in). But there are so many properties and I'm not sure what should be typed into all of them or if I'm even looking in the right place.
I've seen some suggestions in WMI documentation that not all WMI errors may be related to WMI itself at all, which I think might be the case here, but I don't know. Some material said DCOM may be the problem, but I didn't have much luck figuring out how to fix that either. From the WMI Diagnostics it looks like there may be multiple errors of different kinds, but if it's that bad, I don't know how my computer's been working at all.
I've been using this computer for 9 months and had no major problems with it, although I did have a problem installing Microsoft Windows Genuine Advantage Notification, for which Microsoft sent me a script that fixed it. One other person here at work is suffering from this same WMI error, but most people have been able to install SQL 2005 here with no problem.
My boss does not want me to just do a full XP reinstall. He wants me to identify the specific problem and fix it. If this was my home computer I wouldn't spend so much time banging my head over this incomprehensible problem. But a full reinstall is not really an option for me in this case, unless maybe Microsoft says that's the only way to fix it.
I am available to deal with this issue during 9 to 5 eastern time Monday to Friday.
Thanks in advance for any help...
Eric
View 3 Replies
View Related
