Problem Install SQL Server Desktop Engine
Feb 27, 2004
I'm in the process of attempting to install Microsoft SQL Server Desktop Engine on my computer in support of an email program call Mailloop6. I've tried going through their tech support but they haven't been able to figure it out.
I'm running Windows XP with SP1 upgrade on a DSL connection.
When I installed the program the first time, I got the following error:
"Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information."
The program obviously wouldn't install. I contacted the vendor and they sent a version with a batch file. Same result. I removed all the appropriate registry entries between installs and removed all the data files as well.
I've tried installing the program using the free MDSE download from the MS site with the following result:
"A Strong SA password is required for security reasons. Please use SAPWD switch to supply the same. Refer to readme for more details. Setup will now exit."
Here's the error log that I got after attempting to install:
2004-02-25 19:31:42.55 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2004-02-25 19:31:42.55 server Copyright (C) 1988-2002 Microsoft Corporation.
2004-02-25 19:31:42.55 server All rights reserved.
2004-02-25 19:31:42.55 server Server Process ID is 3404.
2004-02-25 19:31:42.55 server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL$MAILLOOP6LOGERRORLOG'.
2004-02-25 19:31:42.56 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-02-25 19:31:42.60 server SQL Server configured for thread mode processing.
2004-02-25 19:31:42.60 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-02-25 19:31:42.63 spid3 Warning ******************
2004-02-25 19:31:42.63 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
2004-02-25 19:31:42.63 spid3 Starting up database 'master'.
2004-02-25 19:31:42.91 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-02-25 19:31:42.94 spid5 Starting up database 'model'.
2004-02-25 19:31:43.24 server SQL server listening on 152.163.0.0: 4113.
2004-02-25 19:31:43.24 server SQL server listening on 172.16.1.33: 4113.
2004-02-25 19:31:43.24 server SQL server listening on 127.0.0.1: 4113.
2004-02-25 19:31:43.25 spid3 Server name is 'MONSTERMAILLOOP6'.
2004-02-25 19:31:43.25 spid3 Skipping startup of clean database id 5
2004-02-25 19:31:43.25 spid3 Skipping startup of clean database id 6
2004-02-25 19:31:43.25 spid3 Starting up database 'msdb'.
2004-02-25 19:31:43.56 spid5 Clearing tempdb database.
2004-02-25 19:31:44.13 spid5 Starting up database 'tempdb'.
2004-02-25 19:31:44.17 spid3 Recovery complete.
2004-02-25 19:31:44.17 spid3 SQL global counter collection task is created.
2004-02-25 19:31:44.19 spid3 Warning: override, autoexec procedures skipped.
2004-02-25 19:31:47.75 server SQL server listening on TCP, Shared Memory, Named Pipes.
2004-02-25 19:31:47.75 server SQL Server is ready for client connections
2004-02-25 19:31:57.97 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.
Any thoughts on this would be very much appreciated!
View 2 Replies
ADVERTISEMENT
Aug 18, 2007
My coworker tried install SQL server 2005 on a server. The server already has a desktop engine running as "MSSQLServer". Because the new sql server 2005 need running as a default instance. So he still using "MSSQLServer" as the instance name.
After installation, the service's running file seems still point to the old location. When view the properties on Management studio, it still report as "desk top engine" and the version is 8.xx..xxxx.
My question is,
1. What has been done during the installation? Is current desktop engine was upgraded?
2. In current situation, what can we do to install the SQL server 2005 as a default instance. Is there way to rename the desktop engine to a named instance?
Thanks
View 4 Replies
View Related
Feb 28, 2003
I have a few questions about the SQL Server Desktop Engine (MSDE), sorry there are so many ..
1. Which software products does this come with ?
2. If I create a SQL Server Database and want to distribute it to clients, how do I actually do it with MDSE ?
3. If I need to "upgrade" my database at some point in the future (that may contain data at a client site) how would I go about getting all the data out - would I need to write an external app ?
4. What are it's pros and cons when compared to installing full SQL Server on a client site ?
5. I've heard that the preformance of an MSDE Database degrades severely after more than 5 concurrent connections, is this just due to the performance of the product or is it something to do with the licencing model ?
6. Is it possible to write applications in, say VB, to alter the database once it has been installed on client site e.g. modify/create tables, indexes, stored procedures ?
Thanks for any help in advance ..
Scott..
View 2 Replies
View Related
Jan 21, 2004
Can someone advise me if this is basically SQL server 2000 and will work effectively to simulate sql server on a stand alone development machine ? Is this what its meant for?
I'm just not clear on this, here is the link:
http://www.microsoft.com/downloads/details.aspx?FamilyID=413744d1-a0bc-479f-bafa-e4b278eb9147&DisplayLang=en
Thanks in advance for any advice.
View 2 Replies
View Related
Jan 23, 2004
Hello,
I'm trying to install Microsoft SQL Server Desktop Engine (MDSE) and it said that I require a SA Password. I can't figure out how to do this.
Can anybody help?
Thanks,
Shenra
View 1 Replies
View Related
Jan 29, 2004
Trying to install Microsoft SQL Server 2000 Desktop Engine on my laptop. I downloaded the software and opened it to a folder on the C drive. Then from the command prompt I entered this:
C:msderela>setup sapwd = hillary instancename=mjh targetdir=c:mike
The program starts to install and seems to get near to the end of instal and then the progress bar starts going backwards and nothing gets installed....any ideas of what I'm doing wrong....I really don't know anything about this at all.
Thanks
View 14 Replies
View Related
Apr 11, 2004
i have got to connect to sql server desktop engine over internet with the following connection string
conString = "Provider=SQLOLEDB.1;Persist Security Info=True;Initial Catalog=" & dbName & ";Network Address=" & IPAddress & ";Data Source=" & DataSource & " ;User ID=" & UserId & " ; Password=" & Password
Plz also inform me about the restriction imposed in connectivity by any of the window operating system such as that win 98 wont work or work!
There is no firewall involved. The two computers are in the same room and connected directly to the internet.
Even the ping is not going to either computer.
So what could be the possible problem and the solution.
need urgent
View 1 Replies
View Related
May 4, 2008
Did a SQL Server Desktop Engine 2000 (MSDE) having SQL Agent module?
View 2 Replies
View Related
Dec 31, 2007
Hi,
what is the distribution fee for SQL Server 2005 Desktop Engine distribution? Where can I find this information? I don't need it for development only for distribution.
Thanks,
LearningWPFnDotNet
View 7 Replies
View Related
Jul 27, 2006
I have SQL Server 2000 installed on my laptop and am trying to install an instance of MSDE. I keep getting the error message: "The installation of SQL Server 2000 Desktop Engine has failed. Please see the Getting Started manual for further instructions."
I have done this installation before on other machines. Something must be corrupt on my machine (?). The error message is not very enlightening. Any ideas?
View 6 Replies
View Related
Aug 3, 2006
I have got SQL Server Desktop Engine running with 2 database and I need
to install the evaluation version of SQL Server 2005 instead. A
straight upgrade does not seem to be possible. Does someone know if
backing up the databases, uninstalling the desktop engine, installing
SQL Server 2005 and then importing/restoring the databases would be an
option to look into?
View 1 Replies
View Related
Nov 30, 2005
Dear friends,
View 3 Replies
View Related
Sep 25, 2007
Hi
i'm chanaka my problem is i had a wsus 2.0 version server, last week my server disk was full, finaly i was move the Wsus data to new disk.with all the contens. when i try to move the datbase it's give the error.
when i open the wsus admin console it's give the error message. and it's add the event log error also. this thing is giving to me big problems.
Connection to database failed. Reason=Unknown error.. Connection string: Data Source=EMAIL-FILTERWSUS;Initial Catalog=SUSDB;Connection Timeout=60;Application Name=WSUS SQL Connection;Trusted_Connection=Yes;Pooling='true'; Max Pool Size = 100
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
if u can give me help. . please if u can give me help.
Best Regards,
shadow
Aucsna
View 1 Replies
View Related
May 16, 2008
During installation of MSDE the installation hangs at "please wait while Windows configures microsoft sql server desktop engine" I always end up killing the installation process. I am trying to install Windows XPe dev kit and this is the step I am getting stuck on. If I try to skip this step and setup the database the setup obviously tells me that i dont have sql 200 or MSDE installed.
The KB article http://support.microsoft.com/kb/811479 describes the syptoms perfectly, but fast user switching isnt even enabled for this machine and is not the source of the problem.
View 8 Replies
View Related
Nov 20, 2006
hi dear developers;
i just finished my program and i am making a setup for it but the db is MSSQL SERVER 2005. the home users how will they use sql server 2005? is there any thing like sql server 2000 desktop engine? something like that... shortly the user don't have to know sql server and settings of it so how will we do it???
thank you very much...
View 5 Replies
View Related
Sep 21, 2004
How do I add login user ASPNET to my SQL 2000 Desktop Engine Server?. I can not find the "Server Manager" in the Start - Programs. Is there any other way to get around adding ASPNET login to the SQL server so I can test my VB program. I got the error: Login failed for user 'com_nameASPNET'.
View 1 Replies
View Related
Feb 6, 2007
I am currently running Windows XP Professional Service Pack2. It already has MSDE & SQL Server 2000 installed (although I just uninstalled MSDE in the vain hope that it might present the installer with a more straightforward upgrade).
I have tried installing with the default instance & a new instance (I don't really care - I just need to install the darn thing). I just want the basic database & Books On-line, nothing fancy.
Here is the Summary log, for what it's worth:
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Tue Feb 06 16:45:14 2007
Machine : ANTHONYY1
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft SQL Server Native Client
Product Version : 9.00.2047.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_OWC11_1.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_BackwardsCompat_1.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : MSXML 6.0 Parser (KB927977)
Product Version : 6.00.3890.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLSupport_2.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft SQL Server Native Client
Product Version : 9.00.2047.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_SQLNCLI_2.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_OWC11_2.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_BOL_1.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_BackwardsCompat_2.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : MSXML 6.0 Parser (KB927977)
Product Version : 6.00.3890.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0011_ANTHONYY1_MSXML6_2.log
--------------------------------------------------------------------------------
Machine : ANTHONYY1
Product : SQLXML4
Error : Setup is preparing to continue with the installation.
--------------------------------------------------------------------------------
Here is the SQLSetup0011_ANTHONYY1_Core(Local).log
Microsoft SQL Server 2005 Setup beginning at Tue Feb 06 16:45:14 2007
Process ID : 2560
C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2007/1/6 16:45:14
Complete: LoadResourcesAction at: 2007/1/6 16:45:14, returned true
Running: ParseBootstrapOptionsAction at: 2007/1/6 16:45:14
Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapxmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2007/1/6 16:45:14, returned true
Running: ValidateWinNTAction at: 2007/1/6 16:45:14
Complete: ValidateWinNTAction at: 2007/1/6 16:45:14, returned true
Running: ValidateMinOSAction at: 2007/1/6 16:45:14
Complete: ValidateMinOSAction at: 2007/1/6 16:45:14, returned true
Running: PerformSCCAction at: 2007/1/6 16:45:14
Complete: PerformSCCAction at: 2007/1/6 16:45:14, returned true
Running: ActivateLoggingAction at: 2007/1/6 16:45:14
Complete: ActivateLoggingAction at: 2007/1/6 16:45:14, returned true
Running: DetectPatchedBootstrapAction at: 2007/1/6 16:45:14
Complete: DetectPatchedBootstrapAction at: 2007/1/6 16:45:14, returned true
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__2560" returned false.
Action "BeginBootstrapLogicStage" will be skipped due to the following restrictions:
Condition "Setup is running locally." returned true.
Running: PerformDotNetCheck2 at: 2007/1/6 16:45:14
Complete: PerformDotNetCheck2 at: 2007/1/6 16:45:14, returned true
Running: InvokeSqlSetupDllAction at: 2007/1/6 16:45:14
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 [ANTHONYY1]
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 = ANTHONYY1, Article = WMIServiceWin32OSWorking, Result = 0 (0x0)
Machine = ANTHONYY1, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0)
Machine = ANTHONYY1, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0)
Machine = ANTHONYY1, Article = WMIServiceReadRegWorking, Result = 0 (0x0)
Machine = ANTHONYY1, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0)
Machine = ANTHONYY1, Article = WMIServiceCIMDataWorking, Result = 0 (0x0)
Machine = ANTHONYY1, Article = XMLDomDocument, Result = 0 (0x0)
Machine = ANTHONYY1, Article = Processor, Result = 0 (0x0)
Machine = ANTHONYY1, Article = PhysicalMemory, Result = 0 (0x0)
Machine = ANTHONYY1, Article = DiskFreeSpace, Result = 0 (0x0)
Machine = ANTHONYY1, Article = OSVersion, Result = 0 (0x0)
Machine = ANTHONYY1, Article = OSServicePack, Result = 0 (0x0)
Machine = ANTHONYY1, Article = OSType, Result = 0 (0x0)
Machine = ANTHONYY1, Article = iisDep, Result = 0 (0x0)
Machine = ANTHONYY1, Article = AdminShare, Result = 0 (0x0)
Machine = ANTHONYY1, Article = PendingReboot, Result = 70011 (0x1117b)
Machine = ANTHONYY1, Article = PerfMon, Result = 0 (0x0)
Machine = ANTHONYY1, Article = IEVersion, Result = 0 (0x0)
Machine = ANTHONYY1, Article = DriveWriteAccess, Result = 0 (0x0)
Machine = ANTHONYY1, Article = COMPlus, Result = 0 (0x0)
Machine = ANTHONYY1, Article = ASPNETVersionRegistration, Result = 0 (0x0)
Machine = ANTHONYY1, Article = MDAC25Version, Result = 0 (0x0)
*******************************************
Setup Consistency Check Report for Machine: ANTHONYY1
*******************************************
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: IIS Feature Requirement, Result: CheckPassed
Article: Pending Reboot Requirement, Result: CheckPassed
Article: Performance Monitor Counter Requirement, Result: CheckPassed
Article: Default Installation Path Permission Requirement, Result: CheckPassed
Article: Internet Explorer Requirement, Result: CheckPassed
Article: Check COM+ Catalogue, Result: CheckPassed
Article: ASP.Net Registration Requirement, Result: CheckPassed
Article: Minimum MDAC Version Requirement, Result: CheckPassed
<Func Name='PerformDetections'>
0
<EndFunc Name='PerformDetections' Return='0' GetLastError='0'>
<Func Name='DisplaySCCWizard'>
CSetupBootstrapWizard returned 1
<EndFunc Name='DisplaySCCWizard' Return='0' GetLastError='183'>
Failed to find help file for LCID :2057
Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.1399.0
<EndFunc Name='DwLaunchMsiExec' Return='0' GetLastError='0'>
Complete: InvokeSqlSetupDllAction at: 2007/1/6 16:49:35, returned true
Running: SetPackageInstallStateAction at: 2007/1/6 16:49:35
Complete: SetPackageInstallStateAction at: 2007/1/6 16:49:36, returned true
Running: DeterminePackageTransformsAction at: 2007/1/6 16:49:36
Complete: DeterminePackageTransformsAction at: 2007/1/6 16:49:47, returned true
Running: ValidateSetupPropertiesAction at: 2007/1/6 16:49:47
Complete: ValidateSetupPropertiesAction at: 2007/1/6 16:49:47, returned true
Running: OpenPipeAction at: 2007/1/6 16:49:47
Complete: OpenPipeAction at: 2007/1/6 16:49:47, returned false
Error: Action "OpenPipeAction" failed during execution.
Running: CreatePipeAction at: 2007/1/6 16:49:47
Complete: CreatePipeAction at: 2007/1/6 16:49:47, returned false
Error: Action "CreatePipeAction" failed during execution.
Action "RunRemoteSetupAction" will be skipped due to the following restrictions:
Condition "Action: CreatePipeAction has finished and passed." returned false.
Running: PopulateMutatorDbAction at: 2007/1/6 16:49:47
Complete: PopulateMutatorDbAction at: 2007/1/6 16:49:47, returned true
Running: GenerateRequestsAction at: 2007/1/6 16:49:47
SQL_Engine = 3
SQL_Data_Files = 3
SQL_Replication = 3
SQL_FullText = 3
SQL_SharedTools = 3
SQL_BC_DEP = 3
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 = 3
SQL_WarehouseDevWorkbench = 3
SDK = 3
SQLXML = 3
Tools_Legacy = 3
TOOLS_BC_DEP = 3
SQL_Documentation = 3
SQL_BooksOnline = 3
SQL_DatabaseSamples = -1
SQL_AdventureWorksSamples = -1
SQL_AdventureWorksDWSamples = -1
SQL_AdventureWorksASSamples = -1
SQL_Samples = -1
Complete: GenerateRequestsAction at: 2007/1/6 16:49:48, returned true
Running: CreateProgressWindowAction at: 2007/1/6 16:49:48
Complete: CreateProgressWindowAction at: 2007/1/6 16:49:48, returned true
Running: ScheduleActionAction at: 2007/1/6 16:49:48
Complete: ScheduleActionAction at: 2007/1/6 16:49:48, returned true
Skipped: InstallASAction.11
Skipped: Action "InstallASAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.18
Skipped: Action "InstallASAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.22
Skipped: Action "InstallASAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.9
Skipped: Action "InstallASAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "as", install will be skipped as a result.
Skipped: InstallDTSAction
Skipped: Action "InstallDTSAction" was not run. Information reported during analysis:
No install request found for package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.11
Skipped: Action "InstallDTSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.12
Skipped: Action "InstallDTSAction.12" was not run. Information reported during analysis:
No install request found for package: "sqlncli", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.18
Skipped: Action "InstallDTSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.22
Skipped: Action "InstallDTSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.9
Skipped: Action "InstallDTSAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "dts", install will be skipped as a result.
Skipped: InstallNSAction
Skipped: Action "InstallNSAction" was not run. Information reported during analysis:
No install request found for package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.11
Skipped: Action "InstallNSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.12
Skipped: Action "InstallNSAction.12" was not run. Information reported during analysis:
No install request found for package: "sqlncli", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.18
Skipped: Action "InstallNSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.22
Skipped: Action "InstallNSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.9
Skipped: Action "InstallNSAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "ns", install will be skipped as a result.
Skipped: InstallRSAction.11
Skipped: Action "InstallRSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "rs", install will be skipped as a result.
Skipped: InstallRSAction.18
Skipped: Action "InstallRSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "rs", install will be skipped as a result.
Skipped: InstallRSAction.22
Skipped: Action "InstallRSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "rs", install will be skipped as a result.
Running: InstallSqlAction.11 at: 2007/1/6 16:49:48
Installing: sqlsupport on target: ANTHONYY1
Complete: InstallSqlAction.11 at: 2007/1/6 16:49:51, returned true
Running: InstallSqlAction.12 at: 2007/1/6 16:49:51
Installing: sqlncli on target: ANTHONYY1
Complete: InstallSqlAction.12 at: 2007/1/6 16:49:55, returned true
Running: InstallSqlAction.18 at: 2007/1/6 16:49:55
Installing: owc11 on target: ANTHONYY1
Complete: InstallSqlAction.18 at: 2007/1/6 16:49:56, returned true
Running: InstallSqlAction.21 at: 2007/1/6 16:49:56
Installing: sqlwriter on target: ANTHONYY1
Complete: InstallSqlAction.21 at: 2007/1/6 16:49:58, returned true
Running: InstallSqlAction.22 at: 2007/1/6 16:49:58
Installing: bcRedist on target: ANTHONYY1
Complete: InstallSqlAction.22 at: 2007/1/6 16:50:0, returned true
Running: InstallSqlAction.9 at: 2007/1/6 16:50:0
Installing: msxml6 on target: ANTHONYY1
Complete: InstallSqlAction.9 at: 2007/1/6 16:50:2, returned true
Running: InstallToolsAction.11 at: 2007/1/6 16:50:2
Installing: sqlsupport on target: ANTHONYY1
Complete: InstallToolsAction.11 at: 2007/1/6 16:50:5, returned true
Running: InstallToolsAction.12 at: 2007/1/6 16:50:5
Installing: sqlncli on target: ANTHONYY1
Complete: InstallToolsAction.12 at: 2007/1/6 16:50:8, 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.
Running: InstallToolsAction.18 at: 2007/1/6 16:50:8
Installing: owc11 on target: ANTHONYY1
Complete: InstallToolsAction.18 at: 2007/1/6 16:50:10, returned true
Running: InstallToolsAction.20 at: 2007/1/6 16:50:10
Installing: BOL on target: ANTHONYY1
Complete: InstallToolsAction.20 at: 2007/1/6 16:52:2, returned true
Running: InstallToolsAction.22 at: 2007/1/6 16:52:2
Installing: bcRedist on target: ANTHONYY1
Complete: InstallToolsAction.22 at: 2007/1/6 16:52:4, returned true
Running: InstallToolsAction.9 at: 2007/1/6 16:52:4
Installing: msxml6 on target: ANTHONYY1
Complete: InstallToolsAction.9 at: 2007/1/6 16:52:6, returned true
Skipped: InstallNSAction.10
Skipped: Action "InstallNSAction.10" was not run. Information reported during analysis:
No install request found for package: "sqlxml4", referred by package: "ns", install will be skipped as a result.
Running: InstallSqlAction at: 2007/1/6 16:52:7
Installing: sql on target: ANTHONYY1
Error: MsiOpenDatabase failed with 110
Failed to install package
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
Error: MsiOpenDatabase failed with 110 for MSI D:ServersSetupSqlRun_SQL.msi
Setting package return code to: 1620
Complete: InstallSqlAction at: 2007/1/6 16:52:27, returned false
Error: Action "InstallSqlAction" failed during execution. Error information reported during run:
Target collection includes the local machine.
Invoking installPackage() on local machine.
Running: InstallToolsAction.10 at: 2007/1/6 16:52:27
Installing: sqlxml4 on target: ANTHONYY1
Error Code: 0x8007006e (110)
Windows Error Text: The system cannot open the device or file specified.
Source File Name: sqlchainingminorbuildactionbehavior.cpp
Compiler Timestamp: Mon Jun 13 14:30:04 2005
Function Name: sqls::MinorBuildActionBehavior::modifyRequest
Source Line Number: 65
---- Context -----------------------------------------------
sqls::InstallPackageAction::perform
Complete: InstallToolsAction.10 at: 2007/1/6 16:55:59, returned false
Error: Action "InstallToolsAction.10" failed during execution. Error information reported during run:
Target collection includes the local machine.
Invoking installPackage() on local machine.
Action "InstallToolsAction" will return false due to the following preconditions:
Condition "Action: InstallToolsAction.10 has finished and failed." returned true.
Installation of package: "tools" failed due to a precondition.
Step "InstallToolsAction" was not able to run.
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: RepairForBackwardsCompatRedistAction
Skipped: Action "RepairForBackwardsCompatRedistAction" was not run. Information reported during analysis:
Action: "RepairForBackwardsCompatRedistAction" will be skipped due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Error: Action "UninstallForMSDE2000Action" failed during execution. Error information reported during run:
Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchMSDE2000" failed due to a precondition.
Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run:
Action: "UninstallForSQLAction" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchLibertySql" failed due to a precondition.
Skipped: UninstallForRS2000Action
Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis:
Action: "UninstallForRS2000Action" will be skipped due to the following condition:
Condition "Action: InstallRSAction was skipped." returned true.
Running: ReportChainingResults at: 2007/1/6 16:55:59
Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 1620
Error Code: 0x80070654 (1620)
Windows Error Text: This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
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
led due to cancel code received from cancel source: 29539
...and here is the SQLSetup0011_ANTHONYY1_SQL.log:
=== Verbose logging started: 06/02/2007 16:52:14 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe ===
MSI (c) (00:54) [16:52:14:284]: Resetting cached policy values
MSI (c) (00:54) [16:52:14:284]: Machine policy value 'Debug' is 0
MSI (c) (00:54) [16:52:14:284]: ******* RunEngine:
******* Product: D:ServersSetupSqlRun_SQL.msi
******* Action:
******* CommandLine: **********
MSI (c) (00:54) [16:52:14:284]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (00:54) [16:52:14:284]: Grabbed execution mutex.
MSI (c) (00:54) [16:52:14:299]: Cloaking enabled.
MSI (c) (00:54) [16:52:14:299]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (00:54) [16:52:14:299]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (A4:98) [16:52:14:299]: Grabbed execution mutex.
MSI (s) (A4:00) [16:52:14:299]: Resetting cached policy values
MSI (s) (A4:00) [16:52:14:299]: Machine policy value 'Debug' is 0
MSI (s) (A4:00) [16:52:14:299]: ******* RunEngine:
******* Product: D:ServersSetupSqlRun_SQL.msi
******* Action:
******* CommandLine: **********
MSI (s) (A4:00) [16:52:21:080]: Note: 1: 2203 2: D:ServersSetupSqlRun_SQL.msi 3: -2147024873
MSI (s) (A4:00) [16:52:21:080]: MainEngineThread is returning 1620
MSI (c) (00:54) [16:52:21:080]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (00:54) [16:52:21:080]: MainEngineThread is returning 1620
=== Verbose logging stopped: 06/02/2007 16:52:21 ===
I suppose an error dialog (or log message) that actually told you what is wrong and then what to do is too much to ask for. (Or an installer than just copied all the files into place). :(
View 4 Replies
View Related
Apr 17, 2007
Hello.
Has anyone attempted and successfully installed SQL Server 2000 SP4
via remote desktop on the cluster.
The reason I am asking is that SP4 readme file has this:
"...
4.3 Systems Management Server Distributed Installation
You cannot install Database Components SP4 from a remote location.
..."
Currently SQL Server has SP3a installed.
Thank you in advance.
View 2 Replies
View Related
Aug 21, 2007
I have installed Visual Studio 2005 Prof Edition on a Vista machine and SQL Server 2005 Developer Edition on a Windows 2000 server. They will be used as a development environment for us. As we need to management the SQL Server 2005, we would like to install the 2005 Developer SSMS on the Vista machine such that we can manage the SQL Server 2005 developer instance installed on that Win2k machine. However, the system does not allow us to do it. We have the express edition autoamtically installed while we installed the Vistual Studio. Is there any workaround that i can still install the 2005 developer SSMS without uninstall the sql server 2005 Xpress version? Or, I have to uninstall the Xpress version before i can install the 2005 developer's SSMS? Please help!
View 11 Replies
View Related
Feb 17, 2004
My objective is to use Enterprise Manager to move (copy) my SQL db from the server to my windows desktop computer.
I downloaded MSDE and am having trouble installing it, no doubt because I do not understand the documentaion (ReadMeMSDE2000A.htm).
When I try to run setup, I get that message that says:
"A strong SA password is required for security reasons. Please use SAPWD switch to supply the same."
Considering my purpose, do I need a "strong" SA password? If not, how do I get around it? If yes, how do I set it up?
I am a Mac user so I have poor windows skills, please make it as painless as possible for me, thanks!
Ron
View 3 Replies
View Related
Feb 16, 2006
venu writes "Hi,
Am very new to MS SQL adminstration
Can anybody help me out how to work on Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Release A just for the practice.
The activity which am going to workout on MSDE is below.
How to install SQL(on XP)
How the layout will be(like if i insall MSDE what are all Application will be and how they depends on each other)
How to create/delete tables if so, how can we do it either by GUI or CUI
just i need a clarifications reg same
Thank you,
venu"
View 1 Replies
View Related
Feb 28, 2003
I was looking at the registry key value "ConcurrentLimit" in
"HKEY_LOCAL_MACHINE'SOFTWAREMicrosoftMicrosoft SQL Server80MSSQLLicenseInfoMSSQL8.00"
and wondering if this the concurrency control of SQL Server. Can someone please verify??
One of our SQL Production Server I inherited was installed with this version by mistake. The value for this key was set to 2. Does this mean it only allows 2 concurrent access to the SQL Server??
Thanks...byyu :)
View 4 Replies
View Related
Feb 19, 2005
Dear all,
This week I was told to setup MSDE Desktop Engine on my pc bcz my Access back end db is getting bigger in size. And as a little advance step, I decided to put my Access back end on SQL server.
To be frank, I have no experience with SQL server but after reading the instructions, I have installed MSDE (latest version) on my pc successfully. A small icon of SQL server appeared nearby clock icon of my pc showing the SQL server is running on ASHFAQUEPC.
I shifted a Trial db onto this server in following way.
Considering the opened Trial db would be my BE, from the Tools---Database Utility---Upsize wizard, I followed below steps according to Upsize wizard.
1.I selected ‘Local’ server and check marked to ’Use Trusted Connection’.
2.And then I selected some tables to export
3.Kept all default attributes of db as it is
4.Selected ‘Let the wizard decide’ under data option to include.
5.At the next step ‘What application change do you want to make?
a.Create a new Access client/Server application.
b.Link SQL Server tables to existing application.
c.No application changes. (I selected this option)
Then it showed me the report of my db description of changes that were made after deploying it. The report I did not print bcz it was a trial db with one table (2 fields) and a simple query.
My idea was to connect my Trial BE with another one of another Access mdb file so FE would be Access and BE would be from MSDE.
1.Now I don’t know how to link my BE to my FE?
2.From where I can directly see my BE? Because SQL Server Service Manager does
not have any menu?
3.Where I was wrong in following steps?
Guidance in this regards is highly appreciated.
With kind regards,
Ashfaque
View 1 Replies
View Related
Mar 15, 2004
i installed the MSDE2000A on server and i tried to connect from client machine through vb Application using connection string. Server anad client are in LAN. but Some systems able to connect and some systems are unable to connect.
i am getting the error:
"SqlServer does not exist or access denied "
for non connected machines.
the server is listening from these machines. but not connecting to MSDE.
can anyone give me solution what may be the cause.
View 6 Replies
View Related
Jul 23, 2005
Hi there,I sincerely hope that someone out there can help. I have twoinstances of the SQL 2000 Desktop Engine running. One is on my localmachine for development and the other is on another machine on ournetwork which is the production environment. I have built an Access2003 front end application which connects to this database. Thisworks fine locally, as you would expect. I successfully installed thedatabase on the production machine and am able to connect to it viaAccess 2003 (using the Data Link Properties window) and from thirdparty database manager software (similar to Enterprise Manager). I amnot able to to connect to the database via my application.I am using the "sa" account with a strong password. This is myconnection string:strConnection = "Provider=sqloledb;DataSource=server02;UserId=sa;Password=strong;Initial Catalog=Test"The error I'm getting is:"Connection cannot be used to perform this operation. It is eitherclosed or invalid in this context."The connection string is the only thing that changes in my code when Iswitch from my local to my production database. Is there some reasonthat I can't use the "sa" account in this fashion that I'm not awareof? I'd rather not use integrated security for simplicity's sake asthis is a small, internal application. Also, I would have thoughtthat if that was the issue, I couldn't use "sa" at all, even locally.I'm going to post to the Access group as well but thought someone heremight have some advice to offer as well.Thanks,Barb
View 2 Replies
View Related
Nov 16, 2005
Hi, I've just tried to install SQL Server 2005 Standard and I'm getting an error that I can't find any information on. In the log, I find Error 29503. A message after it indicates that it couldn't start the server.
View 11 Replies
View Related
Nov 16, 2006
Hi Folks,
I am unable to install SQL 2005 Express on my XP desktop. I receive following error:
SQL Server 2005 setup has detected incompatible components from beta versions of Visual Studio .............
- I have uninstalled and reinstalled the Visual Studio 2005 Express many times
- I do not see any version of SQL installed on my machine from Add/Remove Program
- I checked the running processes and there is no instance of SQL running
I do not know where this incompatible version of SQL is on my machine. I am getting ready to format my machine but I want to see if someone can help me install 2005 express without having to format my PC.
Thanks in advance!
- Aaron
View 1 Replies
View Related
May 16, 2007
Please Help!!!.
I Installed everything but database Engine...
Error Log:
Property(S): SqlVerComBin.8E491190_3328_49D2_9FFE_2D036D847DE2 = C:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.8E491190_3328_49D2_9FFE_2D036D847DE2 = C:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBin.EB8FB35E_3FC3_41F6_9721_7400C2070A66 = C:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.EB8FB35E_3FC3_41F6_9721_7400C2070A66 = C:Program FilesMicrosoft SQL Server90
Property(S): SqlTarget.EB8FB35E_3FC3_41F6_9721_7400C2070A66 = C:Program FilesMicrosoft SQL Server
Property(S): SqlInstance.EB8FB35E_3FC3_41F6_9721_7400C2070A66 = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQL
Property(S): SqlInstanceBin.EB8FB35E_3FC3_41F6_9721_7400C2070A66 = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLBinn
Property(S): sqlreps_dll.EB8FB35E_3FC3_41F6_9721_7400C2070A66 = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLBinnsqlrepss90.dll
Property(S): SqlInstance.E4D6F7B0_3639_4517_9BA2_30823DE19CEB = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQL
Property(S): SqlTarget.E4D6F7B0_3639_4517_9BA2_30823DE19CEB = C:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceInstall.E4D6F7B0_3639_4517_9BA2_30823DE19CEB = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLInstall
Property(S): CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = C:Program FilesCommon Files
Property(S): MSShared.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = C:Program FilesCommon FilesMicrosoft Shared
Property(S): DatabaseRepl.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = C:Program FilesCommon FilesMicrosoft SharedDatabase Replication
Property(S): DatabaseReplRes.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = C:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources
Property(S): DatabaseReplRes1033.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = C:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources1033
Property(S): WindowsFolder = C:WINNT
Property(S): Gac.A6DEDA64_4924_4EA9_84E5_DC507BA0794B = C:Program FilesMicrosoft SQL Server90GAC
Property(S): Ver.A6DEDA64_4924_4EA9_84E5_DC507BA0794B = C:Program FilesMicrosoft SQL Server90
Property(S): Gac.4845A713_8D8A_4100_8CAA_164C5AC9E452 = C:Program FilesMicrosoft SQL Server90GAC
Property(S): Ver.4845A713_8D8A_4100_8CAA_164C5AC9E452 = C:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBin.8B75390F_DF2F_4C2C_92F5_9B83F3B36340 = C:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.8B75390F_DF2F_4C2C_92F5_9B83F3B36340 = C:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBin.889BED4C_E3F4_4943_956C_6FFD882F721F = C:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.889BED4C_E3F4_4943_956C_6FFD882F721F = C:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBin.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBinRes.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:Program FilesMicrosoft SQL Server90COMResources
Property(S): SqlVerComBinRes1033.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:Program FilesMicrosoft SQL Server90COMResources1033
Property(S): SqlInstance.7827AB3E_7041_406A_9591_4DB66042927F = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQL
Property(S): SqlTarget.7827AB3E_7041_406A_9591_4DB66042927F = C:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.7827AB3E_7041_406A_9591_4DB66042927F = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLBinn
Property(S): Data.7827AB3E_7041_406A_9591_4DB66042927F = C:Program FilesMicrosoft SQL Server
Property(S): DataInstance.7827AB3E_7041_406A_9591_4DB66042927F = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQL
Property(S): FTDataDir.7827AB3E_7041_406A_9591_4DB66042927F = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLFTData
Property(S): DataInstanceTxt.7827AB3E_7041_406A_9591_4DB66042927F = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQL
Property(S): DataInstanceFTData.7827AB3E_7041_406A_9591_4DB66042927F = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLFTData
Property(S): ModuleID_FTSSV = 68C6D15C_77E0_11D5_8528_00C04F68155C
Property(S): SqlFullTextDefaultPath = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLFTData
Property(S): FTERefPath.68C6D15C_77E0_11D5_8528_00C04F68155C = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLFTData
Property(S): QuotedServiceGroupFTS.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = B0019B91BCDB3SQLServer2005MSFTEUser$B0019B91BCDB3$SQL2005PDI1
Property(S): FTEInstName.68C6D15C_77E0_11D5_8528_00C04F68155C = SQL2005PDI1
Property(S): FTERudeInstName.68C6D15C_77E0_11D5_8528_00C04F68155C = MSSQL.3
Property(S): FTERegRoot.68C6D15C_77E0_11D5_8528_00C04F68155C = SOFTWAREMicrosoftMicrosoft SQL ServerMSSQL.3MSSearch
Property(S): FTEInstanceSubDir.68C6D15C_77E0_11D5_8528_00C04F68155C = MSSQL.3MSSQL
Property(S): FTEStartupType = 0
Property(S): FTEStatus = 3
Property(S): InstanceRegKey.7827AB3E_7041_406A_9591_4DB66042927F = Microsoft SQL ServerMSSQL.3
Property(S): InstanceName.7827AB3E_7041_406A_9591_4DB66042927F = SQL2005PDI1
Property(S): SqlVerComFT.BB43EC2E_1D73_400F_AE2F_F370407BC222 = C:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.BB43EC2E_1D73_400F_AE2F_F370407BC222 = C:Program FilesMicrosoft SQL Server90
Property(S): FTESqlInstanceBin.68C6D15C_77E0_11D5_8528_00C04F68155C = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLBinn
Property(S): FTESqlInstance.68C6D15C_77E0_11D5_8528_00C04F68155C = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQL
Property(S): FTESqlInstanceBinRef.68C6D15C_77E0_11D5_8528_00C04F68155C = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLBinnFTERef
Property(S): FTESqlInstanceDotNumber.68C6D15C_77E0_11D5_8528_00C04F68155C = C:Program FilesMicrosoft SQL ServerMSSQL.1
Property(S): SqlVer.68C6D15C_77E0_11D5_8528_00C04F68155C = C:Program FilesMicrosoft SQL Server90
Property(S): FTESharedCompRoot.68C6D15C_77E0_11D5_8528_00C04F68155C = C:Program FilesMicrosoft SQL Server90
Property(S): Sql.68C6D15C_77E0_11D5_8528_00C04F68155C = C:Program FilesMicrosoft SQL Server
Property(S): SqlTarget.68C6D15C_77E0_11D5_8528_00C04F68155C = C:Program FilesMicrosoft SQL Server
Property(S): ProgramFilesFolder.68C6D15C_77E0_11D5_8528_00C04F68155C = C:Program Files
Property(S): CAFTERemovePerfCounters.68C6D15C_77E0_11D5_8528_00C04F68155C = $SQL2005PDI1
Property(S): CAFTEUninstallFTERef.68C6D15C_77E0_11D5_8528_00C04F68155C = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLBinnFTERef|C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLFTData
Property(S): CAFTEUpgradeFTERefFiles.68C6D15C_77E0_11D5_8528_00C04F68155C = SQLServer$SQL2005PDI1:C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLBinnFTERef
Property(S): CAFTEUpgradeFTERefFilesRollBack.68C6D15C_77E0_11D5_8528_00C04F68155C = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLBinnFTERef
Property(S): CAFTEInstallFTERef.68C6D15C_77E0_11D5_8528_00C04F68155C = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLBinnFTERef|C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLFTData
Property(S): CAFTEAddCertificate.68C6D15C_77E0_11D5_8528_00C04F68155C = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLBinn
Property(S): CAFTEInstallPerfCounters.68C6D15C_77E0_11D5_8528_00C04F68155C = C:Program FilesMicrosoft SQL ServerMSSQL.3MSSQLBinnSQL2005PDI1
Property(S): CASetLaunchPermissions.68C6D15C_77E0_11D5_8528_00C04F68155C = {68C6D318-77E0-11D5-8528-00C04F68155C}:NT AUTHORITYSYSTEM
Property(S): FTERegInstName.68C6D15C_77E0_11D5_8528_00C04F68155C = SQL2005PDI1
Property(S): FTERegRudeInstName.68C6D15C_77E0_11D5_8528_00C04F68155C = MSSQL.3
Property(S): FTEUPGRADE.68C6D15C_77E0_11D5_8528_00C04F68155C = 0
Property(S): FTEUpgrade30.68C6D15C_77E0_11D5_8528_00C04F68155C = 0
Property(S): FTEUpgradeMSSearchApp.68C6D15C_77E0_11D5_8528_00C04F68155C = SQLServer$SQL2005PDI1
Property(S): FTEUpgradeMSSearchStandalone.68C6D15C_77E0_11D5_8528_00C04F68155C = 0
Property(S): CostingComplete = 1
Property(S): FTEInstID.68C6D15C_77E0_11D5_8528_00C04F68155C = 1
Property(S): FTEAppID.68C6D15C_77E0_11D5_8528_00C04F68155C = {68C6D318-77E0-11D5-8528-00C04F68155C}
Property(S): FTEAdminCLSID.68C6D15C_77E0_11D5_8528_00C04F68155C = {68C6D37C-77E0-11D5-8528-00C04F68155C}
Property(S): FTEIFTEAdmin.68C6D15C_77E0_11D5_8528_00C04F68155C = {64f6bd6f-cc0d-11d6-9a15-505054503030}
Property(S): FTEMSFTEPXY.68C6D15C_77E0_11D5_8528_00C04F68155C = {64f6bdd4-cc0d-11d6-9a15-505054503030}
Property(S): FTEDollarInstName.68C6D15C_77E0_11D5_8528_00C04F68155C = $SQL2005PDI1
Property(S): FTEServiceName.68C6D15C_77E0_11D5_8528_00C04F68155C = msftesql$SQL2005PDI1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer$SQL2005PDI1
Property(S): SqlStateManaged = 2
Property(S): SqlActionManaged = 3
Property(S): SqlNamedInstance = 1
Property(S): RSVirtualDirectoryManager = Reports$SQL2005PDI1
Property(S): SOURCEDIR = S:PDIPDI ToolsSQL 2005 DeveloperCD1Setup
Property(S): SourcedirProduct = {2373A92B-1C1C-4E71-B494-5CA97F96AA19}
Property(S): InstallNgenTicks = 20000
Property(S): DebugClsid.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = {BF3C1964-6601-4DBB-A782-1848FD4A2109}
Property(S): SQLBROWSERACCOUNT = CORPNBDG3C3
Property(S): ProductToBeRegistered = 1
MSI (s) (F8:64) [14:22:43:217]: Note: 1: 1708
MSI (s) (F8:64) [14:22:43:217]: Product: Microsoft SQL Server 2005 -- Installation failed.
MSI (s) (F8:64) [14:22:43:233]: Cleaning up uninstalled install packages, if any exist
MSI (s) (F8:64) [14:22:43:233]: MainEngineThread is returning 1603
MSI (s) (F8:48) [14:22:43:342]: Destroying RemoteAPI object.
MSI (s) (F8:C0) [14:22:43:342]: Custom Action Manager thread ending.
=== Logging stopped: 5/16/2007 14:22:43 ===
MSI (c) (7C:84) [14:22:43:342]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (7C:84) [14:22:43:342]: MainEngineThread is returning 1603
=== Verbose logging stopped: 5/16/2007 14:22:43 ===
View 4 Replies
View Related
Apr 13, 2004
Help,
the installation process stops almost immediately telling me I need a superduper secure password thingy but when I try the command prompts suggested they don't work... I'm on XP home.
View 11 Replies
View Related
Jul 23, 2007
Hello,
I have downloaded he trial Edition of SQL2005 Enterprise Edition. The data base engine does not install. Since I have previously installed Visual Studio 2008 which has VS 2005 components I uninstalled the SQL 2005 (which only has the configuration tool.
I also uninstalled he SQL Express and Compact Editions. When I tried to install SQL 2005 Enterprise once again the Data Base Engine did not nstall. I do get a warning that IIS is running in 32 bit mode in the pre-setup list,(I am running W2K3 R2 x64). I do not know what tro do I am downloading the trial software again. I need to have the data base engine and management studio. I am baffled as to why it doesn't install the Dtat Base Engine. In my add and remove programs there is no instance of SQL installed. Can anyone help? Thank you in advance. Joe
View 1 Replies
View Related
Feb 24, 2007
1. Today I've installed webmatrix and MSDE200A and followed this instruction"Select 'SQL2kdesksp3.exe' and save it to your computer.Double-click on the SQL2kdesksp3.exe you downloaded.Once you have run the self extracting exe (SQL2kdesksp3.exe), go to a command prompt.Start > Run > cmdNavigate to the directory you expanded the self extracting exe to and change to the MSDE subdirectory.The default is C:sql2ksp3Type Setup SAPWD=(Some password) SecurityMode=SQLExample:c:sql2ksp3> Setup SAPWD=password SecurityMode=SQLAfter that gets done running, MSDE is installed.Start servicesTo get the SQL Server running and the SQL Agent we need start the services.right click My Computer > manage > servicesDouble click the following and set to Automatic.MSSQLSERVERSQLSERVERAGENTMake sure both are on automatic." then I restarted my comp. I've tried to connect to database but it did not work.I need the reply ASAP!!!! 2.What are the different among MSDE200A.exe, sql2ksp3.exe, and sql2kdesksp3.exe ?
View 1 Replies
View Related
Dec 7, 1999
Is it necessary to have a MS Loopback Adaptor to install SQL Server desptop edition at my home ? ( Otherwise i am unable to connect to the server from the EM )
Thanks,
Deepak.
View 1 Replies
View Related
Dec 19, 2003
hi, can I use sql server desktop edition to deploy my web application and at the same time I am not violating license agreement with Ms.
thanks
Al
View 1 Replies
View Related