MSDE Setup Failed
Jul 31, 2004was installing MSDE for use with Web matrix
thot had done all correctly ie the setup.exe sapwd=xxxxx securitymode=sql from the command prompt
was told that setup has failed
where is the problem
ADVERTISEMENT
MSDE Setup Question
Dec 12, 2004Hello:
I had partitioned my harddrive to have both XP PRO and Red Hat. Got fed up with all that and so used Partition Magic 8.0 to repartition the drive to be one 16 Gig drive. I still have over 8 Gig left on it even after installing VS .NET on it.
I have successfully installed Visual Studio .NET Pro 2003 on it and I can now write programs in VB and see it on my intranet at c:/wwwroot/.
I am now trying to install MSDE 2000 for Developers Using VS .NET. I have downloaded the file from Microsoft and then when I go to install it on my hard drive it tells me it cannot; I have to free up 92.44 Megs for it to be able to extract it to my c drive.
I am a newbee and any help will be GREATLY appreciated!!
MSDE Setup Problem
Mar 1, 2005i got prob running setup in MSDE ,
there r options to set in setup.ini to enable setting the parameter in MSDE after installed
but it cant run
i use
[Options}
SAPWD=123
after install the sapassword still null,seems like no effect
i've try running from prompt setup.exe /SAPWD 123 too
MSDE Setup -- Where's The Server?
Mar 12, 2004I am using VB.net to build ASP.net pages. I finally decided it was time to start using SQL server based code. So, I installed MSDE....or so I thought.
I have the server Icon in the bottom systray and it's green and seems to be running.
I have been able to use Microsoft Access' Database Upgrade Wizard to create BB.adp file.
An in VB.net I see a master.dbo connection in Server Explorer.
But I can't figure out how to access the database via the SQL server. When I right click on Server Explorer....the Create a New SQL database menu item is greyed out.
My concern is that my installation is not complete and/or I don't know how to locate and verify the server.
Any help would be appreciated. Thanks
Setup On Localhost MSDE Permissions
Nov 20, 2003I'm trying to setup the ASP.Net forum on my local XP Pro PC and am having problems with MSDE security. I had an old version of MSDE on the PC and uninstalled it and downloaded/setup the version on the download page with the forum.
Looking at the MSDE readme I did the Windows Authentication mode instead of the mised mode - was that wrong?
When setup tries to setup the DB I get the log entry:
Determined SQL Server version (8.00.194).
[Fail] Could not add ASPNET user to SQL Server.
SQL Server does not exist or access denied.
The server is up and running and I have already used another tool to setup its DB so the server is up an running and functioning fine.
I have search around on the net about MSDE persmissions but the hits have not been helpful - they usually refer to client tools not provided with MSDE. Even if I could find instructions on setting up a user the ASPForumSetup doesn't say what user name or permissons are needed.
I can't find any spot in the XP Pro environment to setup access permissions to MSDE - is finding that the key? My login is a member of the Administrators group.
Help!
Overcoming MSDE Setup Problems
Nov 5, 2004Here is my experience with installing MSDE.
I'm leaning C# and ASP.NET at the same time using the book "Microsoft ASP.NET Programming with Microsoft Visual C# .NET Step by Step". In Appendix C, P 577, it says to locate setup.exe under …Microsoft Visual Studio .NETSetupMSDE and "run setup.exe to install MSDE."
This was my first mistake, because there are more recent versions available with security patches (for the slammer virus). I have been unable to successfully update the old version. The install program for MSDE has got to be a hackers delight because only a hacker can make it work. I decided to uninstall the old version of MSDE 2000 and install the latest download from the MSDN website. The new version would get most of the files installed and then rollback the install, removing all the files. When I tried to reinstall the old version, it did the same thing. At least the new version requires a password parameter for the sa user. The bad news is that the new password is ignored. Since I already installed the first version with a blank sa password by running setup.exe with no parameters the password will remain blank until I change it using the user friendly osql command line utility. More about osql later…
Here is how I solved the rollback problem:
I first (after many hours trying to modify the registry to clean up the mess Windows uninstaller left there) used the command line switch /L*V <your logfile name> to get a verbose log file. I noticed a property listed called "Disablerollback" this was set to 0. So, I ran setup on the command line as below (all one line):
>setup DisableRollback=1 /L*V "C:Program FilesMicrosoft Visual Studio .NETSetupMSDEsetupbat.log" SAPWD="ignored password"
The setup still failed, but its tracks were preserved for XP to complain about on system restart.
I then restarted the system and logged in. XP threw an error dialog box with the message "Your server installation is either corrupt or has been tampered with (unknown package ID)…" I clicked OK and waited a few extra minutes for XP to finish logging me in.
After logging in, I closed the Service Manger from the taskbar notification area. I then deleted the folders 80, and MSSQL (name of default instance) from the target install directory. Finally, I ran setup.exe again as shown:
>setup /L*V "C:Program FilesMicrosoft Visual Studio .NETSetupMSDEsetupgood.log" SAPWD="ignored password"
This time, after restarting, my old MSDE worked. This approach seems to only work with the first old version of MSDE that was shipped with Visual Studio .NET. I still have yet to figure out how to upgrade and get MSDE to work again.
Once you get MSDE to work, here are some tips on how to administer it using the osql command tool.
To change the sa password do the following (use null for a blank password):
>osql -U sa
Password:
1> sp-password @old=null, @new='newpassword', @loginame='sa'
2> go
Password has been changed
3> quit
On page 113 of the authors' first attempt with the book "Microsoft ASP.NET Programming…", the hacks wrote:
Set up the SQL Server session state database by running the InstallSQLState.sql batch (located in …) against the SQL Server you plan to use. (For more information about running batch statements, check with your database administrator or the SQL Server Books Online.)
Here is how to do it with osql:
> osql -S MSSQLSERVER -U sa -i InstallSQLState.sql
For less characters than it took to write the last parenthetical sentence, they could have just given the same example I supplied here.
If you want a graphical interface to administer you MSDE server, try downloading the small package for "Microsoft SQL Web Data Administrator" from Microsoft's website. This even comes with a modern installer. Here are some tips on how to connect to your locally installed MSDE using this utility:
The main dialog just requires that you click the start button. A login page comes up. To log in as sa, do the following:
? Click the "SQL Login" radio button.
? Under "Please enter a SQL Server name:" fill in the following text boxes:
? Username: sa
? Password: [your password | leave blank if no password is set]
? Server: (local)
This should get you to the server tools page. Click "Security", then Logins. Now, on the Logins page, you can add new users. If you install MSDE for mixed mode, you can add "Windows Integrated" user accounts. This best since you won't have to put passwords in your code to allow database access to these users. To add a user, click on "Create New Login". Set Authentication Method to "Windows Integrated" in the combo box. For Login Name you need to use the form <computername><username> . For example, "MSSQLServerDan".
If you did like I did, and installed MSDE in SQL login mode only, you can do the following registry hack to change it to mixed authentication mode:
1. Locate either of the following subkeys (depending on whether you installed MSDE as the default MSDE instance or as a named instance:
HKEY_LOCAL_MACHINESoftwareMicrosoftMSSqlserverMSSqlServer
-or-
HKEY_LOCAL_MACHINESoftwareMicrosoftMicrosoft SQL Server<Instance Name>MSSQLServer
2. In the right-pane, double-click the LoginMode subkey.
3. In the DWORD Editor dialog box, set the value of this subkey to 1. Make sure that the Hex option is selected, and then click OK.
4. Restart the MSSQLSERVER and the SQLSERVERAgent services for this change to take effect.
Try this link for more details:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q322336
Trying To Setup MSDE 2000 Release A
Dec 12, 2004Hello:
I have extracted the files from the Microsoft download and am all ready to run SETUP for the MSDE 2000 release A for Visual Studio .NET 2003 Pro.
Is there anything I need to know about or run or configure for it all to work?? I am a newbee and I am the only user on my XP Pro machine under Administrator.
Thank you in advance for any pointers.
Want To Avoid Reboot After MSDE Setup
Jun 5, 2007Hello,
OS: Windows XP Embedded
MSDE: 2000 SP3 to SP4
I want to avoid reboot after upgrading MSDE from SP3 to SP4.
setup.exe seems to no option to avoid reboot.
The resason to avoid reboot is continue to do some process after upgrade MSDE.
Regards,
Get Local Machine Name In MSDE Setup .bat File
Nov 5, 2003I have the following command in a .bat file
osql -E -S localhost sp_grantlogin 'GREGASPNET'"
What I would like to do is replace GREG with the name of the local computer this .bat file is being run on.
Is there any string for this... i.e [LOCALMACHINE]ASPNET or something like that?
Greg
Creating Custom Tables During MSDE Setup!
Nov 13, 2004Hi folks, i need ur guidance.
I have a few DDL and DML scripts which i want to be automatically applied during MSDE setup; or an .MDF file be attached automatically. Please suggest an easier way!
Howdy!
How To Setup Email Notification For Msde 2000?
Apr 14, 2006is it possible? Thanks.
View 1 Replies View RelatedCorrect Syntax For Query Using Osql.exe In MSDE Setup
Nov 10, 2003I have the following .bat file that I call to register users to my MSDE instance...
echo osql -E -S %COMPUTERNAME%OfficiumInstance -Q "sp_grantlogin '" + %COMPUTERNAME% + "ASPNET'"
echo osql -E -S %COMPUTERNAME%OfficiumInstance -d Officium -Q "sp_grantdbaccess '" + %COMPUTERNAME% + "ASPNET'"
echo osql -E -S %COMPUTERNAME%OfficiumInstance -d Officium -Q "sp_addrolemember 'db_owner', '" + %COMPUTERNAME% + "ASPNET'"
My question is how do I correctly append %COMPUTERNAME% as a string to
I have tried using + signs...
"sp_grantlogin '" + %COMPUTERNAME% + "ASPNET'"
But that doesn't work.
I have looked for .bat file tutorials on the web but can't find the correct way to do this.
Greg
Setup Failed!
Jun 10, 2004I am getting the below error message while trying to install sql 2000 on win2k sp3 server.
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=AFSIESBAK;UID=sa;PWD=;database=mast er
Specified driver could not be loaded due to system error 126 (sql server).
driver={sql server};server=AFSIESBAK;UID=sa;PWD=;database=mast er
Specified driver could not be loaded due to system error 126 (sql server).
driver={sql server};server=AFSIESBAK;UID=sa;PWD=;database=mast er
Specified driver could not be loaded due to system error 126 (sql server).
SQL Server configuration failed.
################################################## #############################
12:09:16 Process Exit Code: (-1)
12:09:28 Setup failed to configure the server. Refer to the server error logs and C:WINNTsqlstp.log for more information.
12:09:28 Action CleanUpInstall:
12:09:28 C:DOCUME~1ADMINA~1LOCALS~1TempSqlSetupBinsc m.exe -Silent 1 -Action 4 -Service SQLSERVERAGENT
12:09:28 Process Exit Code: (1060) The specified service does not exist as an installed service.
12:09:28 C:DOCUME~1ADMINA~1LOCALS~1TempSqlSetupBinsc m.exe -Silent 1 -Action 4 -Service MSSQLSERVER
12:09:28 Process Exit Code: (0)
12:09:28 StatsGenerate returned: 2
12:09:28 StatsGenerate (0x0,0x1,0xf00,0x300,1033,303,0x0,0x1,0,0,0
12:09:28 StatsGenerate -1,adminafs-ies)
12:09:28 Installation Failed.
SQL Server 7 Setup Failed
Apr 9, 2004Please suggest what I can do .
I had SQL Server 7.0 ( NT 4) installed on my desktop . I have not used it for a while and lately found that there is a problem to start service. So , I decided to reinstall it.
As a result of installation I got the message : "Setup Failed to configure the server"
The log does not tell to much besides repreating the same message , that setup failed.
What could be a problem ? How I can fix it.
Thank you.
Sql 2005 SP1 Setup Failed
Apr 20, 2006Hello 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
SQL 2008 Setup Failed
Feb 6, 2008Dears,
i have fail in sql 2005 setup it stop at install workstation componant step when it remove the backup file and apeare this message :
"there is aproblem with this windows installer pachage.A problem run as part of the setup did finish as expected.
Contact support personnel or package vendor"
and i try to unistall it and reinstall but it fail too
i romve all regitary key before reistalle.
note : my operating system is windows vista business edition and i work in vs 2008
thanks,
SQL 2005 Dev Setup Failed
Jan 8, 2008
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,
Failed Install Of MSDE
May 27, 2004Hi, folks.
I have been trying to install sql2kdesksp3 and am running into some problems. The initial install seems to go okay, even up to the point of issuing the Setup sapwd=password command-line command. However, when I try to install sql2kasp3 or sql2ksp3, a message appears saying that SQL 2000 is not installed.
I am on a XPPro SP1 desktop, with IIS 5.1 and .NET 1.1 Framework installed. Can anybody point me in the right direction to get MSDE installed?
TIA,
Bob
Setup Failed To Configure The Server
Jul 21, 2005Hi
I am trying to install SQL server 7 on XP. I did not install any prerequisite such as service pack 4. During the installation process, I received a error message that says:
'Setup fail to configure the server. Refer to server errorlog and cnfigsvr.out for more information. '
In Errorlog file, the last part of it says:
.
.
.
SQL server's unicode collation is:
'English' (ID =1033) Comparison style =196609
SQL server's non-unicode sort order is:
'no case_iso'(ID=52)
SQL servers non-Unicode character setn is 'iso_1(ID=1)
Warning:
Override, autoexec procedures skipped.
Closing file c:MSSQL7DATAmodel.mdf
Closing file c:mssql7datamodelling.ldf
SQL server is terminating due to 'stop' request from service Control Manager.
In cnfgsvr.out
.
.
.
[Microsoft][ODBC SQL Server Driver][SQL Server] Successfully attached database 'Northwind'
Disconnecting from Server...
Stopping Server ......
Starting Server ......
An error occured while attempting to start the service (1460)
SQL server configuration failed.
Please, help me on how to complete the installation.
Or
Is it because of the service pack 4 that I didn't install that is causing the problem.
Setup Failed - No Package &&<sqlncli.msi&&>
Nov 10, 2005I tried to install a sql 2005 desktop engine. This fails with the error: An installaton package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package €˜sqlncli.msi€™ I used a fresh, new download SQLEXPR.EXE. What shall I do?
SQL Server Setup Unexpectedly Failed
Jun 19, 2006Hi,
I am having the same problem as Cherley Vasconcelos mentioned.
I checked for the 2 below mentioned Registery entries as suggested and they are present.
System:
HKEY_USERSS-1-5-18SoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell Folders
User:
HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell Folders
AppData entry is present under the above registry entries with the value of "%USERPROFILE%Application Data
But the problem still exists.
Please Help,
Thanks in advance,
Sonia
The log file is as follows
========================
Microsoft SQL Server 2005 Setup beginning at Mon Jun 19 10:43:41 2006
Process ID : 3476
c:c8e46d550eeabd55d7setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/5/19 10:43:40
Complete: LoadResourcesAction at: 2006/5/19 10:43:40, returned true
Running: ParseBootstrapOptionsAction at: 2006/5/19 10:43:40
Loaded DLL:c:c8e46d550eeabd55d7xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/5/19 10:43:41, returned false
Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run:
Could not parse command line due to datastore exception.
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Wed Oct 26 16:38:20 2005
Function Name: writeEncryptedString
Source Line Number: 124
----------------------------------------------------------
writeEncryptedString() failed
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Wed Oct 26 16:38:20 2005
Function Name: writeEncryptedString
Source Line Number: 123
----------------------------------------------------------
Error Code: -2146893813
Windows Error Text: Key not valid for use in specified state.
Source File Name: cryptohelpercryptsameusersamemachine.cpp
Compiler Timestamp: Wed Oct 26 16:37:25 2005
Function Name: sqls::CryptSameUserSameMachine::ProtectData
Source Line Number: 50
2148073483
Could not skip Component update due to datastore exception.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:20 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "3476"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Running: ValidateWinNTAction at: 2006/5/19 10:43:41
Complete: ValidateWinNTAction at: 2006/5/19 10:43:41, returned true
Running: ValidateMinOSAction at: 2006/5/19 10:43:41
Complete: ValidateMinOSAction at: 2006/5/19 10:43:41, returned true
Running: PerformSCCAction at: 2006/5/19 10:43:41
Complete: PerformSCCAction at: 2006/5/19 10:43:41, returned true
Running: ActivateLoggingAction at: 2006/5/19 10:43:41
Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run:
Datastore exception while trying to write logging properties.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:20 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupStateScope.primaryLogFiles
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
00F8CFC0Unable to proceed with setup, there was a command line parsing error. : 2
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
Class not registered.
Failed to create CAB file due to datastore exception
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:20 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "3476"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupBootstrapOptionsScope.HostSetup
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Message pump returning: 2
Sql Server 2005 Setup Failed
Nov 6, 2007hi,
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?
SQL Server Setup Unexpectedly Failed
Nov 20, 2007While trying to download SQL Server 2005 Express SP2 I receive the following error message: 'SQL server Setup Unexpectedly dailed. For more information review the Setup memory log file in %Program Files%Microsoft SQL Server90Setup BootstrapLOGSummary.txt'.
That log file simply contains the text:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
In the Files folder under log, a text file has been created with the following data:
Microsoft SQL Server 2005 Setup beginning at Mon Nov 19 20:30:29 2007
Process ID : 4648
c:fc359db69b5e5a0ff927be3c2esetup.exe Version: 2005.90.3042.0
Running: LoadResourcesAction at: 2007/10/19 20:30:28
Complete: LoadResourcesAction at: 2007/10/19 20:30:28, returned true
Running: ParseBootstrapOptionsAction at: 2007/10/19 20:30:28
Loaded DLL:c:fc359db69b5e5a0ff927be3c2exmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2007/10/19 20:30:29, returned false
Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run:
Could not parse command line due to datastore exception.
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Wed Jun 14 16:30:14 2006
Function Name: writeEncryptedString
Source Line Number: 124
----------------------------------------------------------
writeEncryptedString() failed
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Wed Jun 14 16:30:14 2006
Function Name: writeEncryptedString
Source Line Number: 123
----------------------------------------------------------
Error Code: -2146893813
Windows Error Text: Key not valid for use in specified state.
Source File Name: cryptohelpercryptsameusersamemachine.cpp
Compiler Timestamp: Wed Jun 14 16:28:04 2006
Function Name: sqls::CryptSameUserSameMachine:rotectData
Source Line Number: 50
2148073483
Could not skip Component update 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 "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "4648"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Running: ValidateWinNTAction at: 2007/10/19 20:30:29
Complete: ValidateWinNTAction at: 2007/10/19 20:30:29, returned true
Running: ValidateMinOSAction at: 2007/10/19 20:30:29
Complete: ValidateMinOSAction at: 2007/10/19 20:30:29, returned true
Running: PerformSCCAction at: 2007/10/19 20:30:29
Complete: PerformSCCAction at: 2007/10/19 20:30:29, returned true
Running: ActivateLoggingAction at: 2007/10/19 20:30:29
Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run:
Datastore exception while trying to write logging properties.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupStateScope.primaryLogFiles
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
00DFCFC0Unable to proceed with setup, there was a command line parsing error. : 2
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
Class not registered.
Can anyone give me some advice on what I need to correct in order to be able to install SQl server Express? Thanks very much in advance.
SQL Server Express SP1 Setup Failed
Dec 6, 2006One of my customers is trying to setup SQL Server 2005 Express SP1 on his Windows XP Home SP2 machine.
Setup failed with the following in the Summary.txt file:
-------
Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)
Time : Mon Dec 04 23:59:22 2006
D86VH461 : Unknown article Result.
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Mon Dec 04 23:59:23 2006
---------
What is this D86VH461 error code? I seached the Internet and could not find any information on it.
Thanks,
Herbert
SQL Server Setup Unexpectedly Failed (again)
Jun 14, 2006I´m running WinXP SP2 with 1GB RAM, dotNET 2.0. and a previous install of SQL Server 2000. I have tried to install SQL Server 2005 Express and it fails early in the installation: "SQL Server Setup unexpectedly failed. For more information, review the Setup summary log file...". The log file is: (!)
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Wed Jun 14 10:27:51 2006
I have tried named instances, reinstall SQL Server 2000, search readme, kb, forums about the problem....nothing
Help, please.
SQLServer 2005 Setup Failed
Jan 31, 2007SQLServer 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
Log File - Failed MSDE SP4 Installation
May 15, 2006Hi,
I tried installing MSDE SP4 on a windows 2000 Server.
Unable to deploy..getting error "The instance name specified is invalid"
Then tried installing with the following;
setup /upgradesp sqlrun DISABLENETWORKPROTOCOLS=0 /L*v C:MSDELog.log
The log files indicates;
1] SOFTWAREMicrosoftMicrosoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is C:DOCUME~1 hp-mgbLOCALS~1Temp{E09B48B5-E141-427A-AB0C-D3605127224A}
Loading extended custom action library C:DOCUME~1 hp-mgbLOCALS~1Temp{E09B48B5-E141-427A-AB0C-D3605127224A}sqlcax.dll
SOFTWAREMicrosoftMicrosoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Attempting to change the service (MSSQLSERVER) path to : C:mssql7Binnsqlservr.exe -sMSSQLSERVER
MSI (s) (F8:30) [14:32:27:328]: Executing op: ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (F8:30) [14:32:27:328]: Executing op: CustomActionSchedule(Action=InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=1025,Source=BinaryData,Target=InstallPerfMon,)
MSI (s) (F8:D4) [14:32:27:328]: Invoking remote custom action. DLL: C:WINNTInstallerMSI313.tmp, Entrypoint: InstallPerfMon
SOFTWAREMicrosoftMicrosoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is C:DOCUME~1 hp-mgbLOCALS~1Temp{E09B48B5-E141-427A-AB0C-D3605127224A}
Loading extended custom action library C:DOCUME~1 hp-mgbLOCALS~1Temp{E09B48B5-E141-427A-AB0C-D3605127224A}sqlcax.dll
SOFTWAREMicrosoftMicrosoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallPerfMon
Registering performance counters from sqlctr.ini
PerfmonLoad routine returned error code 267
Action ended 14:32:27: InstallFinalize. Return value 3.
2] MSI (s) (F8:30) [14:32:38:656]: Executing op: ActionStart(Name=RollbackDeferProperties.2D02443E_7002_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (F8:30) [14:32:38:656]: Executing op: CustomActionRollback(Action=RollbackDeferProperties.2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=1281,Source=BinaryData,Target=DeferProperties,)
MSI (s) (F8:68) [14:32:38:656]: Invoking remote custom action. DLL: C:WINNTInstallerMSI316.tmp, Entrypoint: DeferProperties
SOFTWAREMicrosoftMicrosoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Start custom action DeferProperties
Defer Properties returns: 0
MSI (s) (F8:30) [14:32:38:796]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (F8:30) [14:32:38:796]: Error in rollback skipped.Return: 5
MSI (s) (F8:30) [14:32:38:796]: Unlocking Server
MSI (s) (F8:30) [14:32:38:812]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Action ended 14:32:38: INSTALL. Return value 3.
3] Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): SqlFeature = SqlRun
Property(S): SOURCEDIR = C:Documents and Settings hp-mgbDesktopMSDE Patchpatch filesMSDESetup
Property(S): SourcedirProduct = {E09B48B5-E141-427A-AB0C-D3605127224A}
MSI (s) (F8:30) [14:32:38:984]: MainEngineThread is returning 1603
MSI (s) (F8:2C) [14:32:39:000]: Destroying RemoteAPI object.
MSI (s) (F8:68) [14:32:39:000]: Custom Action Manager thread ending.
MSI (c) (24:FC) [14:32:39:046]: Back from server. Return value: 1603
MSI (c) (24:FC) [14:32:39:046]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
Action ended 14:32:39: INSTALL. Return value 3.
and finally
MSI (c) (24:FC) [14:32:39:078]: Note: 1: 1729
MSI (c) (24:FC) [14:32:39:078]: Product: Microsoft SQL Server Desktop Engine -- Configuration failed.
MSI (c) (24:FC) [14:32:39:078]: Grabbed execution mutex.
MSI (c) (24:FC) [14:32:39:078]: Cleaning up uninstalled install packages, if any exist
MSI (c) (24:FC) [14:32:39:078]: MainEngineThread is returning 1603
Please suggest me whats wrong with the installation.
Regards,
Parveen
Setup Failed For Error Logs And Cnfgsvr.out
Feb 22, 2001I am trying to install the SQL7 server, at the end of the installation before
rebooting the server I got the following error:
"Setup failed to configure the server. Refer to the server error logs and cnfgsvr.out for more information". I have not seen that error before. I cannot install the SQL7 because I always get the same message. Your help would be very appreciate helping me to solve this problem.
Thanks.
MS DTC Setup Failed To Populate The Shared Cluster
Mar 10, 2004I appologize if I am posting this msg twice (newby), but I am getting this error msg in the app log.
MS DTC setup failed to populate the shared cluster
registry. The DTC resource will not be able to come
online.Error Specifics:
d:srv03rtmcomcomplusdtcsharedmtxclumtxcluse
tuphelper
.cpp:120, CmdLine: "C:WINDOWScluster
esrcmon.exe" -e
1208 -m 1212 -p 2132, Pid: 3636
Have anybody seen this msg and any ideas on what to do in this situation? Your timely assistance is much appreciated. Thanks,
SQL Server Service Failed To Start During Setup!
Aug 30, 2006I had a strange experience with MS SQL Server 2005 Express Edition installation, I am running a P4 3G Processor, 1 GB of RAM, Windows XP SP2, 300 GB HDD (SATA if it matters at all :) ) And using Visual Studio Pro 2005.
I have managed to install the SQL Express with no hassle at all, then had to format my HDD, and start from scratch, to make a new home for my VS 2005 Pro (The 300 GB HDD) And managed to install the SQL Express as part of the VS 2005 without any problems, after using it for 3 months now, I've started a new project in VS 2005, and tried to add a new SQL DB, but it had failed for several times.
I€™ve decided that the files got corrupted for some reason and tried to reinstall the MS SQL 2005 using the original SQL Express installation file I've used before, but without joy.
I thought that it is conflicting with some new MS Update patch and downloaded the latest SQL Express advanced installation, but that did not fix the problem either.
The message I'm getting every time I attempt the installation is" SQL Server service failed to start" with all the bla bla about the online books and whatever useless stuff to learn how to start the service manually.
I have uninstalled the whole thing, including VS 2005, .NET Framework, and any registry trace of the SQL Server installation, but again all in vain.
Finally, some smart wizard suggested in one of the threads that if your computer is not part of a domain, you should run the SQL service as a local service, using the advanced option during the first step of the setup.
And guess what! It worked!!!!
My Question is why did it work during the first two installations, without me fiddling with the advanced installation feature?
My computer was and still is, not part of any domain, my hardware did not change at all, and I had the installation failing with or without any software installed!
Setup And Upgrade :: Cluster Installation Failed
Oct 8, 2010when i install sql server 2005 in cluster. I have error at Setup process screen --> the selected components are being configured.all the components are failed.I am using domain account with administrator account privilege on both server.OS : windows server 2008 on virtual machine..when i install sql server agent is enable to select during setup..
View 12 Replies View RelatedSQL Server Setup Failed To Retrieve The SSL Certificate Name
Sep 19, 2005When I try to install SQL 2005 Developer September CTP on Windows XP Professional it returns an error "SQL Server Setup failed to
View 21 Replies View RelatedHow To Fix ASPNET Login Failed Problem With MSDE
Jul 9, 2002I've searched all over the web trying to find a goddamn fix for this problem and no one has it right or they have the commands misspelled (!!!), so in spite of all those idiots, in spite of the makers of the Web Matrix guided tour for not pointing out this problem, and in spite of Microsoft who has not posted a solution themselves, here it goes:
* !! Change MYCOMPUTER below to the appropriate name of your computer !!
* Open a command prompt
* Type: C:
* Type: cd "C:Program FilesMicrosoft SQL Server80ToolsBinn" (or the exact location of the file "osql.exe" if different)
* Copy/paste the following commands
osql -E -S localhost -Q "sp_grantlogin 'MYCOMPUTERASPNET'"
osql -E -S localhost -d Orders -Q "sp_grantdbaccess 'MYCOMPUTERASPNET'"
osql -E -S localhost -d Orders -Q "sp_addrolemember 'db_owner', 'MYCOMPUTERASPNET'"