I recently installed SQL 2005. During the setup, I didn't get the option that makes me add the licensing module I'm using. I don't want to be slapped in the wrist by microsoft. After setup, how can I check the licensing used?
James
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Thanks in advance.
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Thanks in advance.
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Thanks in advance.
Im about to upgrade all our SQL 2000 Servers to 2005
In your setups do you install the anlaysis services, reporting services on separate servers rather than all on the same server.
Currently we have separate servers for web IIS and was wondering if to install on three different servers
I am trying get a database setup in my new install of VS 2005. I have a project on one PC where I just have VS2005 installed and i am able create a website, go to the APP_DATA folder and add a database. On another PC I have VS 2005 installed and then I installed SQL server 2005. Now I fail to connect to ??? when I try and enter the sercuity page of webconfig or try to add a database when I open the APP_DATA folder. There have been many things done on this PC between the install of the two mentioned packages and trying this database creation. However, I feel that something related to the install of SQL Server 2005 after VS 2005 has done something unexpected. Or, I need to manage something between the SQL Express version that got loaded with VS 2005 and the subsequent install of SQL Server. I just don't know what to look for at this point.
View 1 Replies View RelatedI have a SQL 2k5 log shipping setup and all copy jobs as well as restore jobs are running properly but the LS_Alert job that the wizard auto creates fails every two minutes has anyone experienced this before. After going through the wizard it creates a LS_Alert job and schedules it every two minutes and it fails constantly.
Thanks!
kdubb
I'm a Network Administrator that has to do everything from desktop to server, to routing, and DBA so I need a bit of advice. Stretched thin for time and knowledge in the SQL area and trying to do the best I can.
I currently have a MS SQL 2000 database that is 60GB in size for MS Dynamics 8.0 and one that is 2GB that I want to move to a new server.
I've setup and tested it and it all works, now I'm looking for some Best Practices information for best performance. Currently doing about 3,000 transactions a day.
Server is HP ML350-G5 2 Xeon Dual Core 2.0GHz CPUs w/16GB RAM w/external drive bays running 72GB 15K SAS drives with SMART ARRAY P800.
OS is Windows Server 2003 Enterprise w/SP2 - MS SQL 2005 Standard
I have the following drive configurations setup.
C:(RAID1+0)OS - SQL 2005
D:(RAID1+0)Dynamics Application Shared dictionary files for clients
G:(RAID0)BACKUPS (see note below about TEMPDB) I also have a 25GB swap file on this drive maybe better to put in on the D: volume if I put TEMPDB here
H:(RAID1+0)LOGS (2 user db logs and the tempdb log)
I:(RAID1+0)DATA (2 user db - [model, msdb, master]
Recently found that my G: drive (RAID0) only has space for 2 backups (poor space planning on my part) before I need to move the files. Normally I backup the DB with BackupExec 10.1d just fine in about 2 hours over the wire at night since no one is in the DB at night.
Was wondering if putting my TEMPDB there on (RAID0) would be advisable or not. In SQL 2005 it gets rebuilt each time SQL is restarted so it would seem that ensuring it's on a RAID1 or RAID1+0 might not be as necessary as say the DATA files.
Then if I really wanted to I could actually do backups on the I:DATA drive at night and then use TAPE to back that up, and use an automated script to move them off to offline storage once the TAPE backup is done.
For the [model, msdb, master] should they need to be on the I:DATA drive or just leave them on C:OS ? Not sure how much they're actually used.
Also doing some brief testing the Microsoft Dynamics was much slower on the new Server than it was on the original. Odd to me since the new Server is like a McLaren F1 racing a Ford Pinto. The old server is running a single P4 CPU and 6GB RAM
I've set MS SQL 2005 to use 12GB of RAM on the new server so as to leave 4GB for other Server tasks.
I ran the Maintenance Wizard and had it do checks and defrag and index rebuild etc... so not really sure why the speed would be noticeably slower. One thing I did notice is that once a screen query was ran then the next time it was a bit faster but overall I was expecting to see the screens fly by on this new hardware and SQL 2005 but it doesn't really do that.
I've read some of the white papers etc for tuning, but wow I just don't have unlimited hours to do all this analysis, there seem to be hundreds of pages to read on that type of stuff.
Thanks in advance for the advice.
Hello I have installed Visual Web Developer 2005 Express, as well as Visual studio 2005 Standard edtion. I installed SQL 2005 express edition after installing Visual Web developer 2005 Express Edition! at least I thought I did. I most recently tried to install the SP1 of SQL 2005 express edi... and I seem to have gotten a failure to install message with (sa) in the message(I remember it from the first install but it had gone away on 2nd attempt). I have a two part question (1 Does VWD 2005 Express Edition have SQL 2005 Express Edi... included within it can this be causing the failure and, (2 how can I resolve this problem.
Thank You,
DKB
OK we currently have a single SQL 2000 Server for our DW with a DR SQL 2000 Server. We are wanting to create a setup where we have a Failover Cluster of SQL 2005 here at the main office with a DR SQL 2005 system at our DR site. My question is... How would you all do the failover and stuff? How many servers would I need and what would be the job/role for each server. Some things to take note we are implimenting a SAN in our network and we are also implimenting a Virtual Server system on our network. To my understanding you do not really wish to run SQL Servers on a Virtual machine if possible. So I am already planning on making the SQL Servers Physical systems. We are also planning on putting the DB's on the SAN and have the SAN replicate all the data to DR. So... How would you all invision things to be setup? Is there any good documentation I can read about this type of setup. Thank you in advance for all the advice you can provide.
Thanks,
Billy S.
So, here's my problem..
I've been working on getting SQL 2k5 installed for a few days now. It's been the single most trying installation I've ever attempted. Absolutely riddled with problems.. I've had to do integrate SP2 and XP and reinstall my OS... I've literally lost 15-20 hours of my life to this.
So here's my newest problem.
I've new to the techie world so try and make sense of this. Thanks.
Error: Action "InvokeSqlSetupDllAction" threw an exception during execution.
Unable to load setup helper module : 87
Message displayed to user
Failed to load SqlSpars.dll
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_DSLPTP05_.NET Framework 2.0.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0008.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_DSLPTP05_.NET Framework 2.0 LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0008.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_DSLPTP05_.NET Framework Upgrade Advisor.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0008.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_DSLPTP05_.NET Framework Upgrade Advisor LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0008.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_DSLPTP05_.NET Framework Windows Installer.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0008.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0008_DSLPTP05_.NET Framework Windows Installer LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0008.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2006/4/29 16:4:46
Message pump returning: 87
Dears,
i have a problem when i setup workstation componant in sql 2005 it fail when the setup remove the backup file in the end of setup and give me this
if anyone no what id the problem solve it to me
thanks
... Dear All,
I am trying to install the professional edition of SQL Server 2005 on a new PC with xp pro. I have tried several times with several options but the installation is stalled with the error message that "The drop location is missing file(s) that allow setup to determine how a multi instance product should be installed. Setup cannot continue, please repair the drop and try again."
Does anyone know what the probelm is and how to fix this?
Thanks!
I'm trying to setup a SQL 2005 SP2 Mirror in between two mashines with no witness server.
I have successfully established the following:
1. Backup The Database on Principal Server: OK!
2. Copy the backup over to the mirror server: OK!
3. Restore the Database on Mirror Server: OK!
4. Establish Endpoint on Principal Server: Encyrption Disabled OK! TCP - PORT 5022
4.1 Test Script: Checks fine (values match)
SELECT e.name, e.protocol_desc, e.type_desc, e.role_desc, e.state_desc,
t.port, e.is_encryption_enabled, e.encryption_algorithm_desc,
e.connection_auth_desc
FROM sys.database_mirroring_endpoints e JOIN sys.tcp_endpoints t
ON e.endpoint_id = t.endpoint_id
5. Establish Endpoint on Mirror Server: Encyrption Disabled OK! TCP - PORT 5022
5.1 Test Script: Checks fine (values match) (same script as above)
6. Specify Principal server from Mirror server: OK! Connecting with IP
7. Specify Mirror server from Principal server: OK! Connecting with IP
8. View Mirror Information:
8.1 Test Script: Shows everything in NULL
SELECT mirroring_state_desc, mirroring_partner_name, mirroring_witness_name, mirroring_witness_state_desc, mirroring_role_desc, mirroring_safety_level_desc
FROM sys.database_mirroring
Mirror endpoints are still in red even though they initialized correctly.
Mirror monitor shows no mirrors are up.
SQL Logs shows: The Database Mirroring protocal transport is now listening for connections.
Any help would be appreciated.
I have downloaded SQL server 2005 dev edition from Microsoft download using MSDN licence. I selected SQL Server Studio, Integration Services, Reporting Services and Notification Services to install.
Native client, Backward Compatibility, Setup Support files, VSS writer, online help are getting install but MSXML, SQL Server Studio, Integration Services, Reporting Services and Notification Services are failed. Same setup is running fine in other system.
Error : SQLSetup0013_BTG356299_Core.log
----------------------
Microsoft SQL Server 2005 Setup beginning at Tue Jan 08 14:02:14 2008
Process ID : 2196
C:SoftMSDNSQL 2005 DevSQL Server x86Toolssetup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2008/0/8 14:2:14
Complete: LoadResourcesAction at: 2008/0/8 14:2:14, returned true
Running: ParseBootstrapOptionsAction at: 2008/0/8 14:2:14
Loaded DLL:C:SoftMSDNSQL 2005 DevSQL Server x86Toolsxmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2008/0/8 14:2:14, returned true
Running: ValidateWinNTAction at: 2008/0/8 14:2:14
Complete: ValidateWinNTAction at: 2008/0/8 14:2:14, returned true
Running: ValidateMinOSAction at: 2008/0/8 14:2:14
Complete: ValidateMinOSAction at: 2008/0/8 14:2:14, returned true
Running: PerformSCCAction at: 2008/0/8 14:2:14
Complete: PerformSCCAction at: 2008/0/8 14:2:14, returned true
Running: ActivateLoggingAction at: 2008/0/8 14:2:14
Complete: ActivateLoggingAction at: 2008/0/8 14:2:14, returned true
Running: DetectPatchedBootstrapAction at: 2008/0/8 14:2:14
Complete: DetectPatchedBootstrapAction at: 2008/0/8 14:2:14, returned true
Running: LaunchPatchedBootstrapAction at: 2008/0/8 14:2:14
Error: Action "LaunchPatchedBootstrapAction" threw an exception during execution. Error information reported during run:
"c:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 1602
Aborting queue processing as nested installer has completed
Message pump returning: 1602
----------------------
*******************************************
Setup Consistency Check Report for Machine: BTG356299
*******************************************
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
Article: Edition Upgrade Check, Result: Warning
Description: There can be a product on higher SP level. Action: If you are attempting to upgrade an existing instance of Microsoft SQL Server to another Edition by installing the RTM version of the new Edition, you need to pass "SKUUPGRADE=1" to setup.exe on the command line.
<Func Name='PerformDetections'>
0
<EndFunc Name='PerformDetections' Return='0' GetLastError='0'>
<Func Name='DisplaySCCWizard'>
CSetupBootstrapWizard returned 1
<EndFunc Name='DisplaySCCWizard' Return='0' GetLastError='183'>
Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.3042.0
<EndFunc Name='DwLaunchMsiExec' Return='1602' GetLastError='0'>
Complete: InvokeSqlSetupDllAction at: 2008/0/8 14:4:23, returned false
Error: Action "InvokeSqlSetupDllAction" failed during execution.
Action "AnalyzeInstallStage" will be skipped due to the following restrictions:
Condition "Action: InvokeSqlSetupDllAction has finished and passed." returned false.
Action "PrepareForChainingStage" will be skipped due to the following restrictions:
Condition "Action: InvokeSqlSetupDllAction has finished and passed." returned false.
Action "SequenceChainingActionsStage" will be skipped due to the following restrictions:
Condition "Action: InvokeSqlSetupDllAction has finished and passed." returned false.
Action "InstallChainedPackagesStage" will be skipped due to the following restrictions:
Condition "Action: InvokeSqlSetupDllAction has finished and passed." returned false.
Error: Action "ExposeVistaClusteredResources" failed during execution. Error information reported during run:
Action: "ExposeVistaClusteredResources" will be marked as failed due to the following condition:
Condition "The Clustered SQL Server instance that hosts is installed." returned false.
Running: ReportChainingResults at: 2008/0/8 14:4:23
Error: Action "ReportChainingResults" threw an exception during execution.
DwLaunchMsiExec() returned : 1602
Error Code: 0x80070642 (1602)
Windows Error Text: User cancelled installation.
Source File Name: sqlchainingsqlchainingactions.cpp
Compiler Timestamp: Thu Nov 16 20:31:57 2006
Function Name: sqls::ReportChainingResults:erform
Source Line Number: 3416
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "watsonFailedActionErrorCode" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupStateScope.watsonFailedActionErrorCode
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
Failed to create CAB file due to datastore exception
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "watsonFailedActionErrorCode" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupStateScope.watsonFailedActionErrorCode
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
Message pump returning: 1602
----------------------
Please help,
I just recently installed SQL Server 2005. I have a question about "SQL Server Management Studio".
I want my machine to act as the db server, so I can learn the basics of SQL Server 2005. Once I open
"SQL Server Management Studio" and attempt to connect to a database engine, I get the following error
Cannot connect to database engine....
I don't see any services running in the windows services console, I used to
work with SQL Server v7 awhile back and I remember within the left frame of "SQL Server Management Studio"
window, in the Registered Servers frame that the "Database Engine" icon usually had a green right arrow in it
when it was running correctly. Right now I have this "Database Engine" icon but there is a white circle with
no right green arrow signifying that it is running....
Thanks in advance for your help,
Wes
I am trying to create a new transactional publication between two Sql 2005 servers. This is my first attempt with replication in 2005, so i have obviously missed something in the setup. Each time i try to create the new puplication i receive the following error.
Any help is greatly appreciated
TITLE: New Publication Wizard
------------------------------
SQL Server could not configure 'DTS-70P40LT2Y0A' as a Distributor.
------------------------------
ADDITIONAL INFORMATION:
Property LoginSecure cannot be changed or read after a connection string has been set. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
BUTTONS:
OK
------------------------------
Hi Room,
I am new to SQL reporting 2005 and wanted to setup SQL 2005 reporting on stand along server 2003 box.
SQL Server 2005 server and reporting services were installed.
Can anyone provide me some hints how to setup the sql 2005 reports.?
Any articles or links.?
Thanks for the help.
TJ
Below is the error message receive when installing SQL 2005 (x64) enterprise edition.
Failed to install and configure assemblies c:Program Files (x86)Microsoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: The transaction has aborted
Has someone seen this before? Any pointer is appreciated. Thanks.
The SQL Server System Configuration Checker Cannot be executed due to WMI configuration on the machine djones-xp Error: 2147749907 (0x80041013).
I am trying to install SQL2k5 on several developers workstations when I receive this error. I have successfully installed on a server and on my workstation...
Thanks DeWayne
Hi all,
I'm new in this forum and id'like to post a strange error i can't solve by myself.
On a Win2003Server setted as a Stand Alone Server (without Active Directory) i installed my SQL SEERVER 2005 Workgroup edition with Management Studio and ODBC: Everything fine. a software house installed a IRP based on SQL Server: everything fine too.
They asked me to buil Dctive Directory on server. I should uninstall SQL Server, build up the AD domain and then reinstall SQL Server and from SQL Management Studio reconnect all the db.
Ok with uninstall operations, ok with AD setup but when i tryed to setup Sql Server 2005 it starts fine the DB engine but during management component setup i receive this error:
Tipo evento:Errore
Origine evento:MsiInstaller
Categoria evento:Nessuno
ID evento:11334
Data:20/04/2007
Ora:10.35.06
Utente:SERENAadministrator
Computer:SERVER
Descrizione:
Prodotto: Strumenti di Microsoft SQL Server 2005 -- Errore 1334. Impossibile installare il file "MS.AS.Oneclickcube.Resources.dll.53FCAAEE_2BA6_4556_896D_38710359E752". Impossibile trovare il file nel file CAB "Sql.cab". Questo può indicare un errore di rete, un errore di lettura dal CD-ROM o un problema con questo pacchetto.
Per ulteriori informazioni, consultare la Guida in linea e supporto tecnico all'indirizzo http://go.microsoft.com/fwlink/events.asp.
Dati:
0000: 7b 36 41 44 31 32 42 45 {6AD12BE
0008: 35 2d 38 39 30 33 2d 34 5-8903-4
0010: 31 34 39 2d 41 32 44 42 149-A2DB
0018: 2d 30 46 41 32 39 31 31 -0FA2911
0020: 37 46 33 34 41 7d 7F34A}
sorry for Italian... hopes you can understand...
ideas? i notice that the IRP programmers setted up Visual Stuio 8 components on Server and on Analisys Components thers a OneClicCube.dll component...
On my CD there are no SQL.CAB archive...
no ideas at all..
Thanks a lot.
GAB
I just set it up on my laptop, its the express edition.
During setup I specified both auth (windows and login) and wrote down the username and password. I can connect through Management Studio with windows auth but not with the login.
I want to find the username and password. What do I need to do?
Thanks
<<cross posted from microsoft.public.sqlserver.server>>Environment: Windows 2003 Standard Edition SP1, SQL 2005 EE RTM (bothservers)I am getting the following messages when I run this query:select * from LINKEDSERVER.databasename.dbo.tablenameOLE DB provider "SQLNCLI" for linked server "LINKEDSERVER" returnedmessage "An error has occurred while establishing a connection to theserver. When connecting to SQL Server 2005, this failure may be causedby the fact that under the default settings SQL Server does not allowremote connections.".Msg 782, Level 16, State 1, Line 0SQL Network Interfaces: No credentials are available in the securitypackageOLE DB provider "SQLNCLI" for linked server "LINKEDSERVER" returnedmessage "Client unable to establish connection".Msg 782, Level 16, State 1, Line 0SQL Network Interfaces: No credentials are available in the securitypackageLINKEDSERVER is set up as a SQL Server linked server., with no loginmapping, and connections will be made using the login's currentsecurity context.Both servers allow local and remote connections via TCP/IP, and NamedPipes is disabled on both servers. Both servers are trusted fordelegation, and the service accounts for the MSSQLSERVER service onboth servers are also trusted for delegation.We are auditing successful and failed logins, and are not seeing anyactivity on the linked server.Any help would be appreciated.Randy
View 3 Replies View RelatedHello,(sorry for my English...)Could you help me please with installing SQL Servera 2005 ExpressEdition. I downloaded files:SQLEXPR.EXE - Microsoft SQL Server 2005 Express EditionSSEUtilSetup.EXE - SQL Server Express UtilitySqlServer2K5_BOL_Dec2005.msi - Books Online December 2005and I tried to run them sequentially. After installing SQLEXPR.EXEI had impression that I have little icons in Start menu (comparing tomy SQL Server 2000); I have a submenu:Microsoft SQL Server 2005 / Configuration ToolsSQL Server Configuration ManagerSQL Server Error and Usage ReportingSQL Server Surface Area ConfigurationI would like to have sth like Enterprise Manager (to see Northwinddatabase) and Query Analyzer (to query Northwind).So I decided to run SQLEXPR.EXE again: I see a report:System Configuration Check- WMI Service Requirement (Success)Messages* WMI Service Requirement* Check Passed- MSXML Requirement (Success)Messages* MSXML Requirement* Check Passed- Operating System Minimum Level Requirement (Success)Messages* Operating System Minimum Level Requirement* Check Passed- Operating System Service Pack Level Requirement. (Success)Messages* Operating System Service Pack Level Requirement.* Check Passed- SQL Server Edition Operating System Compatibility (Success)Messages* SQL Server Edition Operating System Compatibility* Check Passed- Minimum Hardware Requirement (Success)Messages* Minimum Hardware Requirement* Check Passed- Pending Reboot Requirement (Success)Messages* Pending Reboot Requirement* Check Passed- Default Installation Path Permission Requirement (Success)Messages* Default Installation Path Permission Requirement* Check Passed- Internet Explorer Requirement (Success)Messages* Internet Explorer Requirement* Check Passed- COM Plus Catalog Requirement (Success)Messages* COM Plus Catalog Requirement* Check Passed- ASP.Net Version Registration Requirement (Success)Messages* ASP.Net Version Registration Requirement* Check Passed- Minimum MDAC Version Requirement (Success)Messages* Minimum MDAC Version Requirement* Check Passed....and screen Feature Selection where I see Client Components notchecked. I decided to mark these components:Client Components "Will be installed on local hard drive"Connectivitiy Compenents "Will be installed on local hard drive"Software Development Kit "Will be installed on local hard drive"(I have free disk space); then I pressed "Next":Named instance: SQLExpressand "Next" again: on screen Existing compenents I see popup with amessage:"None of selected features can be installed or upgraded. Setup cannotproceed since no effective change is being made to the machine. (...)"but I had marked Client Components!Could you explain me please what I am doing wrong?Thank you very much for your help!(MP)
View 2 Replies View RelatedI am trying to install the client tools on an XP machine.
I already had to run the .NET 2.0 repair to get past an earlier problem. 3 components fail, the first one being VS.
Here are the highlights of the summary.txt file. What can I do to resolve this? TIA!
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
--------------------------------------------------------------------------------
Product : Visual Studio Integrated Development Environment 2005
Error : Error 1935.An error occurred during the installation of assembly 'Microsoft.VisualStudio.CommonIDE,Version="8.0.0.0",FileVersion="8.0.50727.42",PublicKeyToken="b03f5f7f11d50a3a",Culture="neutral",ProcessorArchitecture="MSIL"'. Please refer to Help and Support for more information. HRESULT: 0x80070020.
--------------------------------------------------------------------------------
Product : Microsoft Visual Studio 2005 Premier Partner Edition - ENU
Product Version : 8.0.50727.42
Install : Failed
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_MACHINENAME_PPESku_1.log
Last Action : InstallFinalize
Error String :An error occurred during the installation of assembly 'Microsoft.VisualStudio.CommonIDE,Version="8.0.0.0",FileVersion="8.0.50727.42",PublicKeyToken="b03f5f7f11d50a3a",Culture="neutral",ProcessorArchitecture="MSIL"'. Please refer to Help and Support for more information. HRESULT: 0x80070020. assembly interface: IAssemblyCacheItem, function: Commit, component: {B05F61DB-39B8-4D38-A520-B5956C81BB01}
Error Number : 1935
--------------------------------------------------------------------------------
Product : SQL Server Books Online
Error : An error occurred during the installation of assembly 'Microsoft.VisualStudio.CommonIDE,Version="8.0.0.0",PublicKeyToken="b03f5f7f11d50a3a",Culture="neutral",FileVersion="8.0.50727.42",ProcessorArchitecture="MSIL"'. Please refer to Help and Support for more information. HRESULT: 0x80070020.
--------------------------------------------------------------------------------
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Failed
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_MACHINENAME_BOL_1.log
Last Action : InstallFinalize
Error String : An error occurred during the installation of assembly 'Microsoft.VisualStudio.CommonIDE,Version="8.0.0.0",PublicKeyToken="b03f5f7f11d50a3a",Culture="neutral",FileVersion="8.0.50727.42",ProcessorArchitecture="MSIL"'. Please refer to Help and Support for more information. HRESULT: 0x80070020. assembly interface: IAssemblyCacheItem, function: Commit, component: {B05F61DB-39B8-4D38-A520-B5956C81BB01}
Error Number : 1935
--------------------------------------------------------------------------------
Hi,
I am trying to install SQL server 2005 developer edition on Win XP SP2.
I am getting error during Database Services install throwing a log (part of it)
Property(S): FTERegRudeInstName.68C6D15C_77E0_11D5_8528_00C04F68155C = MSSQL.1
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
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): FTEServiceName.68C6D15C_77E0_11D5_8528_00C04F68155C = msftesql
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryManager = Reports
Property(S): RSVirtualDirectoryServer = ReportServer
Property(S): SqlActionManaged = 3
Property(S): SqlStateManaged = 2
Property(S): SOURCEDIR = D:Setup
Property(S): SourcedirProduct = {2373A92B-1C1C-4E71-B494-5CA97F96AA19}
Property(S): InstallNgenTicks = 20000
Property(S): SQLBROWSERSCMACCOUNT = CORPNBDQT5O
Property(S): AGTSCMACCOUNT = CORPNBDQT5O
Property(S): SQLSCMACCOUNT = CORPNBDQT5O
Property(S): DebugClsid.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = {7E6E77F5-0576-4DAF-A405-B9184C5DD85A}
Property(S): ProductToBeRegistered = 1
MSI (s) (AC:94) [11:53:33:621]: Note: 1: 1708
MSI (s) (AC:94) [11:53:33:621]: Product: Microsoft SQL Server 2005 -- Installation failed.
Could somebody help, please?
Amol
904-987-7972
am trying to install sql 2005 with cluster option in win 2003 R2
servers
and keep getting sql database setup failed error.Summary log show that
it failed with error number 67.
It doesn't even create a SQLSetup0004_M2MTPONE_SQL.log file. core log
shows
Complete: DetectLocalBootstrapAction at: 2006/5/1 18:15:31, returned
true
Running: LaunchLocalBootstrapAction at: 2006/5/1 18:15:31
Error: Action "LaunchLocalBootstrapAction" threw an exception during
execution. Error information reported during run:
"C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe"
finished and returned: 67
Aborting queue processing as nested installer has completed
Message pump returning: 67
We have two machines in running enterprises version of R2 in a cluster.
I tried running the setup from both machines and got the same error.
I am trying to find a solution for more than week but no luck. Any
help is appreciated.
thanks - Kailash
Part of Summary log:
--------------------------------------------------------------------------------
Machine : M2MTPONE
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup
BootstrapLOGFilesSQLSetup0004_M2MTPONE_BackwardsCompat_1.log
--------------------------------------------------------------------------------
Machine : NEWTPNT1
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : \M2MTPONEC$Program FilesMicrosoft SQL
Server90Setup BootstrapLOGFilesSQLSetup0004_NEWTPNT1_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : M2MTPONE
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup
BootstrapLOGFilesSQLSetup0004_M2MTPONE_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : M2MTPONE
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Error Number : 67
--------------------------------------------------------------------------------
Machine : NEWTPNT1
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Error Number : 67
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log
file in %ProgramFiles%Microsoft SQL Server90Setup
BootstrapLOGSummary.txt.
Time : Thu Jun 01 18:18:54 2006
hi,
Whenever i tried to install Sql Server 2005, the installation fails giving errors for
event logs and error logs
[microsoft][SQL Native Client][SQL Server]. The server could not load DCOM...
In the log file,
Property(S): Ver.7354AFCB_913B_4E9F_B76C_2376101FDE0C = c:Program FilesMicrosoft SQL Server90
Property(S): SqlTools.7354AFCB_913B_4E9F_B76C_2376101FDE0C = c:Program FilesMicrosoft SQL Server90Tools
Property(S): checksum.7354AFCB_913B_4E9F_B76C_2376101FDE0C = **********
Property(S): SqlInstance.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): InstanceRegKey.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = Microsoft SQL ServerMSSQL.1
Property(S): InstanceName.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = SQLEXPRESS
Property(S): PackagecodeChanging = 1
Property(S): SqlInstance.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceInstall.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
Property(S): SqlInstanceInstallDel.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
Property(S): ProductState = -1
Property(S): TRANSFORMS = qlRun01.mst;:InstID01.mst;:InstName01.mst
Property(S): PackageCode = {A81ED606-6AF4-48DA-A5D9-1AFCC4767FEE}
Property(S): SqlInstance.81902028_4743_45C1_9C8C_17223CBC7128 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.81902028_4743_45C1_9C8C_17223CBC7128 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.81902028_4743_45C1_9C8C_17223CBC7128 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstance.D5FA3BDB_C132_4ACB_9BCE_75B981C3A65B = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.D5FA3BDB_C132_4ACB_9BCE_75B981C3A65B = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.D5FA3BDB_C132_4ACB_9BCE_75B981C3A65B = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): MsiLogFileLocation = C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_SHITAL-PC_SQL.log
Property(S): Shared.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90Shared
Property(S): Ver.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlToolsBinRes.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90SharedResources
Property(S): SqlToolsBinRes1033.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90SharedResources1033
Property(S): SqlInstance.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstanceBinRes.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources
Property(S): SqlInstanceBinRes1033.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033
Property(S): SqlInstanceJet.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstanceOther.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstance.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstanceBinRes.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources
Property(S): SqlInstanceBinRes1033.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033
Property(S): sqlevn70.rll.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033sqlevn70.rll
Property(S): Shared.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90Shared
Property(S): Ver.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlSharedRes.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90SharedResources
Property(S): SqlSharedRes1033.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90SharedResources1033
Property(S): SqlVerComBin.FB04F6FB_D3EA_4FB5_B80C_362DD852A799 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.FB04F6FB_D3EA_4FB5_B80C_362DD852A799 = c:Program FilesMicrosoft SQL Server90
Property(S): InstanceName.FB04F6FB_D3EA_4FB5_B80C_362DD852A799 = SQLEXPRESS
Property(S): SqlInstance.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): InstanceName.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = SQLEXPRESS
Property(S): DataInstance.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): Data.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL Server
Property(S): DataInstanceData.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData
Property(S): DataInstanceBackup.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBackup
Property(S): DataInstanceLog.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOG
Property(S): DataInstanceTemplate.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLTemplate Data
Property(S): DataInstanceTxt.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): AdministratorsGroupQuoted = BUILTINAdministrators
Property(S): LocalSystemAccountQuoted = NT AUTHORITYSYSTEM
Property(S): QuotedServiceGroupSQL.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = SHITAL-PCSQLServer2005MSSQLUser$SHITAL-PC$SQLEXPRESS
Property(S): AdministratorsGroup = BUILTINAdministrators
Property(S): UsersGroupQuoted = BUILTINUsers
Property(S): UsersGroup = BUILTINUsers
Property(S): InstanceRegKey.BA9A7592_6647_4283_9B99_2885BD96A224 = Microsoft SQL ServerMSSQL.1
Property(S): DataInstance.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): Data.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL Server
Property(S): DataInstanceData.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData
Property(S): DataInstanceTemplate.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLTemplate Data
Property(S): DataInstanceTxt.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): ModuleID_SYSDB2 = 75D79626_87FB_4E9A_B07F_87DAE18D0F36
Property(S): SqlInstance.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): Data.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL Server
Property(S): DataInstance.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): DataInstanceRepldata.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
epldata
Property(S): DataInstanceTxt.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlVerComBin.779ED4A9_FDA8_4DBD_8D11_1C6CD6EE5AC7 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.779ED4A9_FDA8_4DBD_8D11_1C6CD6EE5AC7 = c:Program FilesMicrosoft SQL Server90
Property(S): TempFolder = c:UsersshitalAppDataLocalTemp
Property(S): DataInstance.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): Data.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL Server
Property(S): SqlTarget.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstance.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlInstanceBin.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): DataInstanceTxt.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): WORKINGDIRECTORY.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLREPLDATA
Property(S): InstanceRegKey.2F9C839A_286D_4B39_BD89_4DF4067604DF = Microsoft SQL ServerMSSQL.1
Property(S): SqlVerComBin.727FAD0C_033D_4A8B_8329_145D3EEA67B7 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.727FAD0C_033D_4A8B_8329_145D3EEA67B7 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBin.13676F0C_8438_4754_8C60_7ED008CBAB8D = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.13676F0C_8438_4754_8C60_7ED008CBAB8D = c:Program FilesMicrosoft SQL Server90
Property(S): MSVSPrivateAssembliesEN.13676F0C_8438_4754_8C60_7ED008CBAB8D = c:Program FilesMicrosoft SQL Server90COMen
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): WindowsFolder = c:Windows
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): 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): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer$SQLEXPRESS
Property(S): SqlActionManaged = 3
Property(S): SqlNamedInstance = 1
Property(S): SqlStateManaged = 2
Property(S): RSVirtualDirectoryManager = Reports$SQLEXPRESS
Property(S): SOURCEDIR = c:2aae5517aa4b91d8f50a9cSetup
Property(S): SourcedirProduct = {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
Property(S): InstallNgenTicks = 110000
Property(S): SQLBROWSERSCMACCOUNT = NT AUTHORITYNetworkService
Property(S): SQLSCMACCOUNT = NT AUTHORITYNetworkService
Property(S): DebugClsid.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = {0D7C3EF4-D4A8-4796-9452-44FC73491B48}
Property(S): ProductToBeRegistered = 1
MSI (s) (24:44) [12:45:07:442]: Note: 1: 1708
MSI (s) (24:44) [12:45:07:442]: Product: Microsoft SQL Server 2005 Express Edition -- Installation failed.
MSI (s) (24:44) [12:45:07:443]: Windows Installer installed the product. Product Name: Microsoft SQL Server 2005 Express Edition. Product Version: 9.2.3042.00. Product Language: 1033. Installation success or error status: 1603.
MSI (s) (24:44) [12:45:07:457]: Cleaning up uninstalled install packages, if any exist
MSI (s) (24:44) [12:45:07:457]: MainEngineThread is returning 1603
MSI (s) (24:BC) [12:45:07:458]: Destroying RemoteAPI object.
MSI (s) (24:74) [12:45:07:459]: Custom Action Manager thread ending.
MSI (s) (24:BC) [12:45:07:460]: RESTART MANAGER: Session closed.
MSI (s) (24:BC) [12:45:07:460]: No System Restore sequence number for this installation.
=== Logging stopped: 11/6/2007 12:45:07 ===
MSI (c) (F0:98) [12:45:07:514]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (F0:98) [12:45:07:516]: MainEngineThread is returning 1603
=== Verbose logging stopped: 11/6/2007 12:45:07 ===
Can anyone provide me solution?
Hi,
Trying to install 64-bit SQL Server 2005 RTM on Windows 2003 x64 Server with SP 1. The Reporting services option is not enabled in the installation steps. The installation process gets completed without any errors, but the Reporting Services is not installed.
The server has IIS installed, the .NET framework 2.0 is installed by SQL Server 2005 RTM itself. Am I doing anything wrong.
Can anyone help/suggest ?
Thanks in advance.
Installing SQl2005 into on Win2003 2 node cluster, at the very end of the
setup receive a message 'Remote Setup failed'. Referred to some sql logs
and found this;
Error: Action "LaunchLocalBootstrapAction" threw an exception during
execution. Error information reported during run:
"C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe"
finished and returned: 1603
Aborting queue processing as nested installer has completed
Message pump returning: 1603
I've seen some similar errors on the web and suggestions about the Task
Scheduler being started on both nodes, but I ensured these were both started
before the install. SQL2005 does seem to be ok on the node1 where the
install was made, but fails when trying to failover to node 2.
Any help would be much appreciated here.
Thanks
Darren
"Setup failed" error when the installation auto-setups "Workstation Components, Books Online and Developement Tools" . It showed "MainEngineThread is returning 21 The device is not ready" in the log. Could not find a solution online. So I have to seek help here.
Here is the log:
=== Verbose logging started: 9/14/2007 17:29:16 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe ===
MSI (c) (8C:EC) [17:29:16:421]: Resetting cached policy values
MSI (c) (8C:EC) [17:29:16:421]: Machine policy value 'Debug' is 0
MSI (c) (8C:EC) [17:29:16:421]: ******* RunEngine:
******* Product: G:SQL Server x86ToolsSetupSqlRun_Tools.msi
******* Action:
******* CommandLine: **********
MSI (c) (8C:EC) [17:29:16:421]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (8C:EC) [17:29:16:421]: Grabbed execution mutex.
MSI (c) (8C:EC) [17:29:16:437]: Cloaking enabled.
MSI (c) (8C:EC) [17:29:16:437]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (8C:EC) [17:29:16:437]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (30:78) [17:29:16:437]: Grabbed execution mutex.
MSI (s) (30:FC) [17:29:16:437]: Resetting cached policy values
MSI (s) (30:FC) [17:29:16:437]: Machine policy value 'Debug' is 0
MSI (s) (30:FC) [17:29:16:437]: ******* RunEngine:
******* Product: G:SQL Server x86ToolsSetupSqlRun_Tools.msi
******* Action:
******* CommandLine: **********
MSI (s) (30:FC) [17:29:16:437]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (30:FC) [17:29:16:453]: File will have security applied from OpCode.
MSI (s) (30:FC) [17:30:22:078]: Note: 1: 2382
MSI (s) (30:FC) [17:30:29:890]: MainEngineThread is returning 21
The device is not ready.
MSI (c) (8C:EC) [17:30:29:890]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (8C:EC) [17:30:29:890]: MainEngineThread is returning 21
=== Verbose logging stopped: 9/14/2007 17:30:29 ===
I removed the SQL 2005 Express then started installing the Client Components in 2005 developer version. I tried to install into C drive or another drive but got the same error.
Anyone knows anything about it?
Many thanks.
Hello,
I have been made the point person for our migration to SQL2005. We are a law firm with approximately 750 users. The first SQL environment we will be upgrading is our document management system (DMS). This is an intensive SQL product. After this migration we will more of to our finical system, records system and then all home grown databases.
What we would like to do is consolidate servers and scale out the new SQL environment to a farm. After some initial research it does not look like we will be able to scale out, since the data in the DMS is always changing.
Does anyone have some advice or guidance on what direction we should be looking? I have done tons a online searches and can find out information on everything to do with SQL, except this.
Thanks in advance,
Jeff Carroll
SQLServer 2005 setup failed on Windows 2003 .
Please see the error log.
Thanks
Microsoft SQL Server 2005 Setup beginning at Wed Jan 31 17:15:16 2007
Process ID : 1624
C:dbservicessetup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2007/0/31 17:15:16
Complete: LoadResourcesAction at: 2007/0/31 17:15:16, returned true
Running: ParseBootstrapOptionsAction at: 2007/0/31 17:15:16
Loaded DLL:C:dbservicesxmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2007/0/31 17:15:16, returned true
Running: ValidateWinNTAction at: 2007/0/31 17:15:16
Complete: ValidateWinNTAction at: 2007/0/31 17:15:16, returned true
Running: ValidateMinOSAction at: 2007/0/31 17:15:16
Complete: ValidateMinOSAction at: 2007/0/31 17:15:16, returned true
Running: PerformSCCAction at: 2007/0/31 17:15:16
Complete: PerformSCCAction at: 2007/0/31 17:15:16, returned true
Running: ActivateLoggingAction at: 2007/0/31 17:15:16
Complete: ActivateLoggingAction at: 2007/0/31 17:15:16, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__1624" returned false.
Running: PerformSCCAction2 at: 2007/0/31 17:15:16
Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.2435
Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.2435
Complete: PerformSCCAction2 at: 2007/0/31 17:15:16, returned true
Running: PerformDotNetCheck at: 2007/0/31 17:15:16
Complete: PerformDotNetCheck at: 2007/0/31 17:15:16, returned true
Running: ComponentUpdateAction at: 2007/0/31 17:15:16
Complete: ComponentUpdateAction at: 2007/0/31 17:16:7, returned true
Running: DetectLocalBootstrapAction at: 2007/0/31 17:16:7
Complete: DetectLocalBootstrapAction at: 2007/0/31 17:16:7, returned true
Running: LaunchLocalBootstrapAction at: 2007/0/31 17:16:7
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 1603
Aborting queue processing as nested installer has completed
Message pump returning: 1603