SQL Server Express Fails During Installation

Jun 23, 2007

Installing SQL Server Express on Vista, directly after the "Compatibility Issues" dialogue, I get the error:


SQL Server setup unexpectedly failed. For more information, review the setup summary log file in %Program Files%Microsoft SQL Server90Setup BootstrapLOGSummary.txt

This file mentioned is virtually blank, but the Files subdirectory of LOG contains a setup log which contains:


Microsoft SQL Server 2005 Setup beginning at Sat Jun 23 12:44:49 2007
Process ID : 5068
C:UsersdajaboDesktop8c1e33f5803c0da83setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2007/5/23 12:44:49
Complete: LoadResourcesAction at: 2007/5/23 12:44:49, returned true
Running: ParseBootstrapOptionsAction at: 2007/5/23 12:44:49
Loaded DLL:C:UsersdajaboDesktop8c1e33f5803c0da83xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2007/5/23 12:44:49, returned falseError: 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: 0x80070005 (5)
Windows Error Text: Access is denied.

Source File Name: cryptohelpercryptsameusersamemachine.cpp
Compiler Timestamp: Wed Oct 26 16:37:25 2005
Function Name: sqls::CryptSameUserSameMachine:rotectData
Source Line Number: 50

5
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", "", "5068"} 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: 2007/5/23 12:44:49
Complete: ValidateWinNTAction at: 2007/5/23 12:44:49, returned true
Running: ValidateMinOSAction at: 2007/5/23 12:44:49
Complete: ValidateMinOSAction at: 2007/5/23 12:44:49, returned true
Running: PerformSCCAction at: 2007/5/23 12:44:49
Complete: PerformSCCAction at: 2007/5/23 12:44:49, returned true
Running: ActivateLoggingAction at: 2007/5/23 12:44:49
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"
038DCFACUnable 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.

Can anyone help?

View 9 Replies


ADVERTISEMENT

SQL Server Express Installation Fails On Vista Home Premium

May 8, 2007

I have recently updated from XP to Vista Home Premium. Now when I try to install SQL Serve Express SP2 I get :



"setup has detected problem with .net framework installation
and cannot proceed. Microsoft .net framework 2.0 is either not installed or
is corrupt."



I have tried to run sfc /scannow to make sure my .NET 2.0 was not corrupted and also was running as an administrator but could not get it installed. Anyone has any ideas?

View 1 Replies View Related

Express Installation Fails With Invalid Installation Package

May 3, 2006

I get an error when trying to install the SQL Native Client. It
says it cannot find the installation package and to use a valid copy of
'sqlncli.msi'. I've downloaded the Express setup twice and get
the same error from both of them.



I'm attempting this in a VMWare session setup for Windows 2K, Advanced
Server. I am trying to test my installation and setup
procedures. This is not a production setup, just install testing
and documentation. I have allocated only 272MB to the VMWare
session, which is why the system doesn't meet the recommended settings.



Any help would be greatly appreciated.



Below is the Summary.txt output file.



Microsoft SQL Server 2005 9.00.2047.00

==============================

OS Version : Microsoft Windows 2000 Advanced Server Service Pack 4 (Build 2195)

Time : Wed May 03 09:54:23 2006



CPCWIN2KVM1 : The current system does not meet recommended hardware
requirements for this SQL Server release. For detailed hardware
requirements, see the readme file or SQL Server Books Online.

Machine : CPCWIN2KVM1

Product : Microsoft SQL Server Setup Support Files (English)

Product Version : 9.00.2047.00

Install : Successful

Log File : c:Program
FilesMicrosoft SQL Server90Setup
BootstrapLOGFilesSQLSetup0003_CPCWIN2KVM1_SQLSupport_1.log

--------------------------------------------------------------------------------

Machine : CPCWIN2KVM1

Product : SQL Native Client

Error : An
installation package for the product Microsoft SQL Server Native Client
cannot be found. Try the installation again using a valid copy of the
installation package 'sqlncli.msi'.

--------------------------------------------------------------------------------

Machine : CPCWIN2KVM1

Product : Microsoft SQL Server Native Client

Product Version : 9.00.2047.00

Install : Failed

Log File : c:Program
FilesMicrosoft SQL Server90Setup
BootstrapLOGFilesSQLSetup0003_CPCWIN2KVM1_SQLNCLI_1.log

Last Action : InstallFinalize

Error String : An installation package for the
product Microsoft SQL Server Native Client cannot be found. Try the
installation again using a valid copy of the installation package
'sqlncli.msi'.

Error Number : 1706

--------------------------------------------------------------------------------

Machine : CPCWIN2KVM1

Product : Microsoft SQL Server VSS Writer

Product Version : 9.00.2047.00

Install : Successful

Log File : c:Program
FilesMicrosoft SQL Server90Setup
BootstrapLOGFilesSQLSetup0003_CPCWIN2KVM1_SqlWriter_1.log

--------------------------------------------------------------------------------

Machine : CPCWIN2KVM1

Product : MSXML 6.0 Parser

Product Version : 6.00.3883.8

Install : Successful

Log File : c:Program
FilesMicrosoft SQL Server90Setup
BootstrapLOGFilesSQLSetup0003_CPCWIN2KVM1_MSXML6_1.log

--------------------------------------------------------------------------------

View 4 Replies View Related

SQL Express 2005 Installation Fails On All Of Our PCs

Mar 1, 2007

The installation fails and crashes with "Error 110", while attempting to install the SQL Native Client... then crashes (DrWatson). This happens on every OS and test machines that we have within our company... flavors of W2K and WXP, all with .Net Framework 2.0.

If the SQL Native Client exists, the installation continues without error. If SQLEXPR32.EXE is run directly from the command line, the installation will succeed.

If SQLEXPR32.EXE is called from a Windows Installer Custom Action type 50, it will always fail. This is the method we used to successfully install MSDE previously.

Our command line is:

/qb ADDLOCAL=SQL_Engine,SQL_Data_Files SAPWD=password1 SECURITYMODE=SQL DISABLENETWORKPROTOCOLS=2 INSTANCENAME=Instance SQLBROWSERAUTOSTART=1 SQLAUTOSTART=1 ENABLERANU=0

The problem appears to start with: Error: Action "ComponentUpdateAction" threw an exception during execution.

-----------------------------------------------

SQLSetup0009_Core.log

Microsoft SQL Server 2005 Setup beginning at Thu Mar 01 08:07:09 2007
Process ID : 852
c:57774bfc862c706a2e923076f41d037csetup.exe Version: 2005.90.3042.0
Running: LoadResourcesAction at: 2007/2/1 8:7:9
Complete: LoadResourcesAction at: 2007/2/1 8:7:9, returned true
Running: ParseBootstrapOptionsAction at: 2007/2/1 8:7:9
Loaded DLL:c:57774bfc862c706a2e923076f41d037cxmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2007/2/1 8:7:9, returned true
Running: ValidateWinNTAction at: 2007/2/1 8:7:9
Complete: ValidateWinNTAction at: 2007/2/1 8:7:9, returned true
Running: ValidateMinOSAction at: 2007/2/1 8:7:9
Complete: ValidateMinOSAction at: 2007/2/1 8:7:9, returned true
Running: PerformSCCAction at: 2007/2/1 8:7:9
Complete: PerformSCCAction at: 2007/2/1 8:7:9, returned true
Running: ActivateLoggingAction at: 2007/2/1 8:7:9
Complete: ActivateLoggingAction at: 2007/2/1 8:7:9, 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__852" returned false.
Running: PerformSCCAction2 at: 2007/2/1 8:7:9
Complete: PerformSCCAction2 at: 2007/2/1 8:7:9, returned true
Running: PerformDotNetCheck at: 2007/2/1 8:7:9
Complete: PerformDotNetCheck at: 2007/2/1 8:7:9, returned true
Running: ComponentUpdateAction at: 2007/2/1 8:7:9
Error: Action "ComponentUpdateAction" threw an exception during execution. Error information reported during run:
<Func Name='UpdateComponents'>
SCU_SetupMgr::InitComponents()
<Func Name='SnacComp::Init'>
<Func Name='SnacComp::IsRequired'>
SNAC version installing: 9.00.3042.00
The installed SNAC version is less then the installing version
SCU_SetupMgr::svc() state=SS_INIT_DONE, cancel_state=0, is_done=0, ActionRequired=1, NeedReboot=0, custom_props={AutoStart=true
DotNetPatch=
HandleReboots=false
ModuleDir=c:57774bfc862c706a2e923076f41d037c
QuietMode=false
SNACPatch=
SupportPatch=
Unattended=true
WorkDir=c:57774bfc862c706a2e923076f41d037c
}} {e:sql9_sp2_tsqlsetupsqlcudllscusetupmgr.cpp:506}
SCU_SetupMgr::InstallComponent state=INSTALL, cancel_state=0, is_done=0, ActionRequired=1, NeedReboot=0, custom_props={AutoStart=true
DotNetPatch=
HandleReboots=false
ModuleDir=c:57774bfc862c706a2e923076f41d037c
QuietMode=false
SNACPatch=
SupportPatch=
Unattended=true
WorkDir=c:57774bfc862c706a2e923076f41d037c
}} {e:sql9_sp2_tsqlsetupsqlcudllscusetupmgr.cpp:384}
SCU_SetupMgr::InstallComponent state=INSTALL, cancel_state=0, is_done=0, ActionRequired=1, NeedReboot=0, custom_props={AutoStart=true
DotNetPatch=
HandleReboots=false
ModuleDir=c:57774bfc862c706a2e923076f41d037c
QuietMode=false
SNACPatch=
SupportPatch=
Unattended=true
WorkDir=c:57774bfc862c706a2e923076f41d037c
}} {e:sql9_sp2_tsqlsetupsqlcudllscusetupmgr.cpp:384}
SCU_SetupMgr::InstallComponent state=INSTALL, cancel_state=0, is_done=0, ActionRequired=1, NeedReboot=0, custom_props={AutoStart=true
DotNetPatch=
HandleReboots=false
ModuleDir=c:57774bfc862c706a2e923076f41d037c
QuietMode=false
SNACPatch=
SupportPatch=
Unattended=true
WorkDir=c:57774bfc862c706a2e923076f41d037c
}} {e:sql9_sp2_tsqlsetupsqlcudllscusetupmgr.cpp:384}
SCU_SetupMgr::InstallComponent state=INSTALL, cancel_state=0, is_done=0, ActionRequired=1, NeedReboot=0, custom_props={AutoStart=true
DotNetPatch=
HandleReboots=false
ModuleDir=c:57774bfc862c706a2e923076f41d037c
QuietMode=false
SNACPatch=
SupportPatch=
Unattended=true
WorkDir=c:57774bfc862c706a2e923076f41d037c
}} {e:sql9_sp2_tsqlsetupsqlcudllscusetupmgr.cpp:384}
<Func Name='SnacComp::InstallImp'>
Failed to install SNAC
Failed to install SNAC : (110) {e:sql9_sp2_tsqlsetupsqlcudllsnaccomp.cpp:251}
SCU_SetupMgr::svc() caught exception: Failed to install SNAC : (110) {e:sql9_sp2_tsqlsetupsqlcudllsnaccomp.cpp:251}. SetupMgr: state=ERROR, cancel_state=0, is_done=0, ActionRequired=1, NeedReboot=0, custom_props={AutoStart=true
DotNetPatch=
HandleReboots=false
ModuleDir=c:57774bfc862c706a2e923076f41d037c
QuietMode=false
SNACPatch=
SupportPatch=
Unattended=true
WorkDir=c:57774bfc862c706a2e923076f41d037c
}} {e:sql9_sp2_tsqlsetupsqlcudllscusetupmgr.cpp:520}
ScuProgressDlg::SetupFinished()
ScuProgressDlg::DialogProc() installation done... waiting for setup mgr
<EndFunc Name='UpdateComponents' Return='1603' GetLastError='87'>
Component update returned a fatal error : 110
Error Code: 0x8007006e (110)
Windows Error Text: The system cannot open the device or file specified.

Source File Name: sqlncli.msi
Compiler Timestamp: Thu Oct 5 12:22:33 2006
Function Name: Unknown
Source Line Number: 1583

Class not registered.



--------------------------------------------

SQLSetup0009_SNAC.log

=== Verbose logging started: 3/1/2007 8:07:10 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:WINDOWSsystem32msiexec.exe ===
MSI (c) (FC:C8) [08:07:10:062]: Resetting cached policy values
MSI (c) (FC:C8) [08:07:10:062]: Machine policy value 'Debug' is 0
MSI (c) (FC:C8) [08:07:10:062]: ******* RunEngine:
******* Product: c:57774bfc862c706a2e923076f41d037csetupsqlncli.msi
******* Action:
******* CommandLine: **********
MSI (c) (FC:C8) [08:07:10:062]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (FC:C8) [08:07:10:062]: Grabbed execution mutex.
MSI (c) (FC:C8) [08:07:10:109]: Cloaking enabled.
MSI (c) (FC:C8) [08:07:10:109]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (FC:C8) [08:07:10:125]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (30:5C) [08:07:10:140]: Grabbed execution mutex.
MSI (s) (30:B0) [08:07:10:140]: Resetting cached policy values
MSI (s) (30:B0) [08:07:10:140]: Machine policy value 'Debug' is 0
MSI (s) (30:B0) [08:07:10:140]: ******* RunEngine:
******* Product: c:57774bfc862c706a2e923076f41d037csetupsqlncli.msi
******* Action:
******* CommandLine: **********
MSI (s) (30:B0) [08:07:10:156]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (30:B0) [08:07:10:171]: Note: 1: 1309 2: 5 3: C:57774bfc862c706a2e923076f41d037csetupsqlncli.msi
MSI (s) (30:B0) [08:07:10:171]: MainEngineThread is returning 110
The system cannot open the device or file specified.
MSI (c) (FC:C8) [08:07:10:171]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (FC:C8) [08:07:10:171]: MainEngineThread is returning 110
=== Verbose logging stopped: 3/1/2007 8:07:10 ===

View 12 Replies View Related

SQL Express Installation Fails During Setup, Vista Permission Problem?

Feb 7, 2008



I'll install SQL Server Express SP2 on Vista during my Setup.
But the setup beaks with error 110.
In other articles it sounds like an folder access problem.
On a Custom Action Type 210 i start a application which execute the sqlexpress.exe.
I tried some other codes to impersonate or noImersonate but without success.

But i can not use the unpacked files because size is to large(170MB)

An good Idea would be unpack the setup files during setup to an custom folder with right permissions.
But I dont know how unpack files without GUI (SQLEXPRESS x always show the GUI).

Any Idea???????????

Here are the corresponding logfiles:


------------------------------------------------------------------------------------------------
Core.log

...
Unattended=true
WorkDir=e:a3d45fa9ced92ee76a8e8275
}} {e:sql9_sp2_tsqlsetupsqlcudllscusetupmgr.cpp:384}
SCU_SetupMgr::InstallComponent state=INSTALL, cancel_state=0, is_done=0, ActionRequired=1, NeedReboot=0, custom_props={AutoStart=true
DotNetPatch=
HandleReboots=false
ModuleDir=e:a3d45fa9ced92ee76a8e8275
QuietMode=true
SNACPatch=
SupportPatch=
Unattended=true
WorkDir=e:a3d45fa9ced92ee76a8e8275
}} {e:sql9_sp2_tsqlsetupsqlcudllscusetupmgr.cpp:384}
<Func Name='SnacComp::InstallImp'>
Failed to install SNAC
Failed to install SNAC : (110) {e:sql9_sp2_tsqlsetupsqlcudllsnaccomp.cpp:251}
SCU_SetupMgr:vc() caught exception: Failed to install SNAC : (110) {e:sql9_sp2_tsqlsetupsqlcudllsnaccomp.cpp:251}. SetupMgr: state=ERROR, cancel_state=0, is_done=0, ActionRequired=1, NeedReboot=0, custom_props={AutoStart=true
DotNetPatch=
HandleReboots=false
ModuleDir=e:a3d45fa9ced92ee76a8e8275
QuietMode=true
SNACPatch=
SupportPatch=
Unattended=true
WorkDir=e:a3d45fa9ced92ee76a8e8275
}} {e:sql9_sp2_tsqlsetupsqlcudllscusetupmgr.cpp:520}
<EndFunc Name='UpdateComponents' Return='1603' GetLastError='0'>
Component update returned a fatal error : 110
Error Code: 0x8007006e (110)
Windows Error Text: Das System kann das angegebene Gerät oder die angegebene Datei nicht öffnen.

Source File Name: sqlncli.msi
Compiler Timestamp: Thu Oct 5 12:22:33 2006
Function Name: Unknown
Source Line Number: 1583

Error: Failed to add file :"E:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEVELOPMENT-PC_.NET Framework 2.0.log" to cab file : "E:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2008/1/7 8:3:25
Failed to launch Watson with error code : 123
Message pump returning: 110


-----------------------------------------------------------------------------------------------------------------------------------------------


SNAC.log

=== Verbose logging started: 07.02.2008 08:03:24 Build type: SHIP UNICODE 4.00.6000.00 Calling process: E:Windowssystem32msiexec.exe ===
MSI (c) (ACC) [08:03:24:840]: Resetting cached policy values
MSI (c) (ACC) [08:03:24:840]: Machine policy value 'Debug' is 0
MSI (c) (ACC) [08:03:24:840]: ******* RunEngine:
******* Product: e:a3d45fa9ced92ee76a8e8275setupsqlncli.msi
******* Action:
******* CommandLine: **********
MSI (c) (ACC) [08:03:24:840]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (ACC) [08:03:24:840]: Grabbed execution mutex.
MSI (c) (ACC) [08:03:24:871]: Cloaking enabled.
MSI (c) (ACC) [08:03:24:871]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (ACC) [08:03:24:903]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (E4:98) [08:03:24:918]: Grabbed execution mutex.
MSI (s) (E4:5C) [08:03:24:918]: Resetting cached policy values
MSI (s) (E4:5C) [08:03:24:918]: Machine policy value 'Debug' is 0
MSI (s) (E4:5C) [08:03:24:918]: ******* RunEngine:
******* Product: e:a3d45fa9ced92ee76a8e8275setupsqlncli.msi
******* Action:
******* CommandLine: **********
MSI (s) (E4:5C) [08:03:24:918]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (E4:5C) [08:03:24:934]: SRSetRestorePoint skipped for this transaction.
MSI (s) (E4:5C) [08:03:24:934]: Note: 1: 1402 2: HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionPoliciesExplorer 3: 2
MSI (s) (E4:5C) [08:03:24:934]: Note: 1: 1309 2: 5 3: e:a3d45fa9ced92ee76a8e8275setupsqlncli.msi
MSI (s) (E4:5C) [08:03:24:949]: MainEngineThread is returning 110
MSI (s) (E4:98) [08:03:24:949]: No System Restore sequence number for this installation.
Das System kann das angegebene Gerät oder die angegebene Datei nicht öffnen.
MSI (c) (ACC) [08:03:24:949]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (ACC) [08:03:24:949]: MainEngineThread is returning 110
=== Verbose logging stopped: 07.02.2008 08:03:24 ===


Regards Sven

View 1 Replies View Related

SQL Express Fails On Setup Support Files Installation On Vista

Mar 13, 2007

Hi
We have a problem installing SQL Express Edition SP1 on Vista. The installation stops during installation of setup support files with the following message:

Errors occurred during the installation:Error 2 installing Microsoft SQL Server 2005 Setup Support Files. See log file for more detailed information.Det går inte att hitta filen. (translated: File not found)
The log file points to the support.log file with the following content:

=== Verbose logging started: 2007-03-13 17:34:23 Build type: SHIP UNICODE 4.00.6000.00 Calling process: C:cd nät40..SQLEXPRSetup.exe ===MSI (c) (C4:F4) [17:34:23:450]: Resetting cached policy valuesMSI (c) (C4:F4) [17:34:23:450]: Machine policy value 'Debug' is 0MSI (c) (C4:F4) [17:34:23:450]: ******* RunEngine: ******* Product: C:cd nät40..SQLEXPRSetupSqlSupport.msi ******* Action: ******* CommandLine: **********MSI (c) (C4:F4) [17:34:23:450]: Client-side and UI is none or basic: Running entire install on the server.MSI (c) (C4:F4) [17:34:23:450]: Grabbed execution mutex.MSI (c) (C4:F4) [17:34:23:591]: Cloaking enabled.MSI (c) (C4:F4) [17:34:23:591]: Attempting to enable all disabled privileges before calling Install on ServerMSI (c) (C4:F4) [17:34:23:607]: Incrementing counter to disable shutdown. Counter after increment: 0MSI (s) (00:10) [17:34:23:622]: Grabbed execution mutex.MSI (s) (00:1C) [17:34:23:622]: Resetting cached policy valuesMSI (s) (00:1C) [17:34:23:622]: Machine policy value 'Debug' is 0MSI (s) (00:1C) [17:34:23:622]: ******* RunEngine: ******* Product: C:cd nät40..SQLEXPRSetupSqlSupport.msi ******* Action: ******* CommandLine: **********MSI (s) (00:1C) [17:34:23:622]: Machine policy value 'DisableUserInstalls' is 0MSI (s) (00:1C) [17:34:23:669]: SRSetRestorePoint skipped for this transaction.MSI (s) (00:1C) [17:34:23:669]: Note: 1: 1402 2: HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionPoliciesExplorer 3: 2 MSI (s) (00:1C) [17:34:23:669]: Note: 1: 1324 2: .. 3: 1 MSI (s) (00:1C) [17:34:23:669]: MainEngineThread is returning 2MSI (s) (00:10) [17:34:23:669]: No System Restore sequence number for this installation.MSI (c) (C4:F4) [17:34:23:669]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1MSI (c) (C4:F4) [17:34:23:669]: MainEngineThread is returning 2=== Verbose logging stopped: 2007-03-13 17:34:23 ===
The funny thing here is that it works fine when the installer is run from a network share, ie \testserversetupsetup.exe but when the same folder is burned to a CD or copied to a local folder it fails. I have verified that the folders are identical.

I'm not sure what info is required to pinpoint the problem but here are some log files and a screen shot of the message.

Any help or pointers would be greatly appreciated.

Regards,
Martin

View 5 Replies View Related

SQL Tools :: SSDT For VS2012 Installation Fails With (Same Architecture Installation) Error

Mar 9, 2013

The 6:th of march Sql server data tools for Visual Studio 2012 was released.

[URL]

I seem to be unable to install this using the link provided on the blog page. I'm getting a "Same architecture installation" error. Running on the machine is Visual Studio 2012 Premium & Sql Server 2012 (64bit).

why I'm getting this installation error.

View 14 Replies View Related

SQL Server 2005 Installation Fails

Nov 23, 2006

I am running Windows XP SP2. The installation fails with

SQL Server coul not connect to the database service for server configuration.

[SQL Native Client]Unable to complete login process due to delay in opening server conection.



Please help in getting this working, I have not been able to find anything by googling thus far.

Regards

Harald Hedlund

View 1 Replies View Related

MSDE Installation Fails Due To Detection Of Previous Installation

Jul 23, 2005

Please help,I am trying to install MSDE 2000 so that Backup exec will run on thisserver. I have gotten so far as to find an entry in my SQLSTP.TXT filethat says that c:mssql7 was detected so the install fails.Now, to start with there is no directory called C:mssql7 on thisserver. I have gone through all MS articles on manual removal of SQLserver and instances. I have searched the registry for mssql7 andremoved any keys that matched, as per MS article I have searched onSQLBOOT.dll and it is not present anywhere on my system and I still getthe same results.2:07:44 Begin Action: Detection12:07:44 SQL Server version already installed: 7.00.62312:07:44 Previous Install SQL Path: C:MSSQL712:07:44 Previous Install SQL Data Path: C:MSSQL712:07:44 End Action Detection12:07:44 Begin Action: ODBCLocked12:07:44 End Action ODBCLocked12:07:44 GetDefinition returned: 112:07:44 Previous SQL Server ProductType: MSDE [0x4]12:07:44 This combination of Package and Operating System allows a fullproduct install.can anyone think of anything here..what else could be causing the server to think there is a previousversion of SQL 7 on this box!!!?

View 1 Replies View Related

SQL Server 2000 Service Pack 3a Installation Fails

Jul 23, 2005

I have an installation of SQL Server 2000. Both MBSA and @@versionshow this to be the gold release. When I install Service Pack 3a, itshows no error. But after restart of the server, it's still unpatched,by both MBSA and @@version.Any idea what may be going on here?

View 3 Replies View Related

Installation Of SQL Server 2005 + RS Fails On A Vista 64 Bits

Feb 27, 2007

Hello,

I'm trying to install a version of SQL server 2005 with reporting services on a vista 64 bits.

I've a licence for SQL server 2005 standard edition in French, my vista is in French, and I'm using visual studio standard edition in English to develop. I would like to develop reports using SQL server to include these reports in my applications developped with Visual Studio.

Wich version of SQL server should I install ? I've tryed to install SQL server express 2005 with advanced feature SP2 (english version) and then later the standard edition (French version) (each time uninstalling all SQL server components between tries), but I got problems with reporting services each time.

I got first a warming saying than reporting services is 32 bits and IIS is 64 bits, I so allowed IIS to run 32 bits ASP .Net, but after that, I now get a problem of .Net registration in IIS as warming message on the line concerning Reporting services during the install of SQL Server, and it doesn't even offer to install RS on the next window.

I reinstalled the DotnetFX64 to be sure, but still get the same message. If I look in the IIS the application pools are looking me to be normal, with the ASPNET 32 bit code allowed.

View 11 Replies View Related

SQL Server 2005 Database Installation Fails To Install

May 9, 2007

Hi,

I have been trying to install SQL Server 2005 developer version on my second laptop IBM Thinkpad Windows XP PRO, for the first time. All other components installed successfully except the database. I 've tried selecting the named instance and default instance it didn't make any difference. I have a Admin role on the laptop and as a service id I selected my user id. password and domain. I am running the setup behind my company's firewall.

The error in the log is :



Doing Action: Do_UpdateETWMOFWithGUID
PerfTime Start: Do_UpdateETWMOFWithGUID : Wed May 09 11:07:46 2007
<Func Name='Do_UpdateETWMOFWithGUID'>
Calling installSqlEvent Trance
The arguments that are passed to InstallSqlEventTrace are InstanceName: SQLSERVER2005 , ProductCodeL: {2373A92B-1C1C-4E71-B494-5CA97F96AA19} , BinPath: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
INFO: Checking installed version
INFO: Writing MOF file
ERROR: Unable to open registry key: HRESULT = 0x80070005, Key = SYSTEMCurrentControlSetControlWMISecurity

The value returned is -2147024891
<EndFunc Name='Do_UpdateETWMOFWithGUID' Return='1603' GetLastError='0'>
PerfTime Stop: Do_UpdateETWMOFWithGUID : Wed May 09 11:07:46 2007
Gathering darwin properties for failure handling.
Error Code: 1603

MSI (s) (88!E0) [11:09:48:898]: Product: Microsoft SQL Server 2005 -- Error 29528. The setup has encountered an unexpected error while Updating Installed Files. The error is: Fatal error during installation.


Error 29528. The setup has encountered an unexpected error while Updating Installed Files. The error is: Fatal error during installation.


I have tried to attach the log but I think it is too big. I cannot post this message.

Please let me know another way to send the log file.



Any help is appreciated.

View 1 Replies View Related

SQL Server 2000 Installation Fails On Windows XP With Service Pack 2

Nov 29, 2005

Hi,
i tried to install SQL Server 2000 Developer and MSDE the whole day on my Windows XP SP2.
MDAC is the latest, that come with WinXP SP2 (2.81). The installation fails at the end after 100% complete.

It says:
Translated: "the setup programm starts the server and installs the configuration you chose..."
("das setup-programm startet den server und installiert die von ihnen gewählte konfiguration...")

then it takes some time and the failure appears, saying:
"the setup programm could not configure the server. you can find more
information in the server-failure-log files and in
"C:windowssqlstp.log."

sqlstp.log last couple of lines:
22:42:10 C:WINDOWSTEMPSqlSetupBinscm.exe  -Silent 1 -Action 4 -Service MSSQLSERVER
22:42:10 Process Exit Code: (0)
22:42:10 StatsGenerate returned: 2
22:42:10 StatsGenerate (0x80000000,0x1,0xf000000,0x200,1031,303,0x0,0x1,0,0,0
22:42:10 StatsGenerate -1,toebens)
22:42:10 Installation Failed.



I already read several knowledge base articles on this... removed keys in the registry...and so on...nothing worked :(

this **** makes me angry. please help me.
thanks
 

View 5 Replies View Related

SQL Server 2005 Server Installation Fails

Oct 8, 2007

Downloaded and installed Visual Studio 2008 Express Editions Beta 2 applications in order:


Visual Basic 2005 Express Edition

Visual C# Express Edition

Visual C++ Express Edition

SQL Server 2005 Express Edition (Advanced)
All went well untill the SQL Server installation. Get an error message stating:


"An installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'."

The "Setup Progress" dialog box displays a "Setup failed." error beside "SQL Native Client" and "SQL Server Database Services" and then closes generating the "Send Error Report" dialog box. A log file is generated but can't find anything meaningful regarding the problem.

HELP!

View 1 Replies View Related

Installation Of SQL Server 2005 Post-SP1 Hotfix 918222 (Build 2153) Fails At Copyengine.cpp Line: 689

Feb 5, 2007

I believe that I mistakenly attempted to apply the Analysis Services component of this update before applying the SQL Server component. The update now fails continuously with the following message:

02/05/2007 17:58:24.990 ================================================================================
02/05/2007 17:58:25.021 Hotfix package launched
02/05/2007 17:58:27.615 Product discovery successfully completed during the install process for MSSQLSERVER
02/05/2007 17:58:27.630 SP Level check successfully completed during the install process for MSSQLSERVER
02/05/2007 17:58:27.646 Product language check successfully completed during the install process for MSSQLSERVER
02/05/2007 17:58:27.661 Product version check successfully completed during the install process for MSSQLSERVER
02/05/2007 17:58:27.677 Command-line instance name check completed during the install process
02/05/2007 17:58:27.693 Baseline build check completed during the install process
02/05/2007 17:58:34.864 Attempting to install instance: MSSQLSERVER
02/05/2007 17:58:34.974 Attempting to install target: CHARLIDEVSRV
02/05/2007 17:58:35.005 Attempting to check for locked files: sqlrun_sql.msp
02/05/2007 17:58:35.052 Attempting to check for locked files: \CHARLIDEVSRVf$44923e05996203228c1608bea1hotfixsqlFilessqlrun_sql.msp
02/05/2007 17:58:35.067 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB918222_sqlrun_sql.msp.out
02/05/2007 18:01:52.978 MSP returned 1635: This patch package could not be opened. Verify that the patch package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer patch package.
02/05/2007 18:01:53.009 Unable to check MSP file: \CHARLIDEVSRVf$44923e05996203228c1608bea1hotfixsqlFilessqlrun_sql.msp
02/05/2007 18:01:53.025 The following exception occurred: Unable to install Windows Installer MSP file Date: 02/05/2007 18:01:53.025 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 689
02/05/2007 18:01:53.212 Failed to install instance: MSSQLSERVER
02/05/2007 18:01:53.259
02/05/2007 18:01:53.259 Product Status Summary:
02/05/2007 18:01:53.290 Product: SQL Server Database Services 2005
02/05/2007 18:01:53.306 MSSQLSERVER - Failure
02/05/2007 18:01:53.321


The update fails although I have cleaned the registry of any reference to it. Another article indicated that the hotfix may delete registry keys required, for instance, to operated SSIS if applied in the wrong order. Here, it appears to be preventing the hotfix from being reapplied. I have ensured that all necessary permissions are available and the services are running in domain user accounts with the necessary rights. I'm the administrator on the machine.

Is there a way to get this hotfix applied without having to completely rip and rebuild my server instance?

View 4 Replies View Related

SQL SERVER Express Installation

Apr 10, 2006

Hi, I am planning to install Sql server Express version on my machine. I already have Vs.NET 2005 Professional and SQL server 2000 installed and was wondering that if the installation of sql server expresss edition will cause any problems? If not then I can proceed  with the installation!

View 1 Replies View Related

Sql Server Express Installation

Nov 19, 2007



Sql server express edition 2005 Installation fails!
Its says processor not supported.
I got HP Laptop and intel T750 2.2 GHz processor.
Please help me to install it

View 3 Replies View Related

Installation SQL Server Express

Mar 6, 2008

Hi
I have SQL Server 2005 and VS 2005 sp1 installed in my machine, however, i need SQL Server 2005 Management Studio and some of the key features in it.

What is the correct proccess to 'upgrade' my system without alter the programs referred?

Thank u for your help.

N. O.

View 1 Replies View Related

SQL Server Express SP2 MU Installation

May 26, 2007

Does anyone know of a way to let end-users install SP2 from Microsoft Update without giving them "God" rights? Please tell me I've just overlooked something and that there's a simple way to do this.



To make a long story short, I have big clients & small clients. The big ones use enterprise and have DBA's who know what they're doing. These guys can do whatever they want & they know enough to not mess things up. They've been running SP2 for months now.



The small ones use express. They have wannabe hardware techs who show up at the office periodically and tinker. I've dealt with too many techs who think that knowing how to swap a motherboard makes them fully qualified to "tweak" SQL Server. One even dropped & redefined an identity because he wanted to allow duplicates. (In case you're wondering, he thought that grouping related records by duplicating the ID would be more efficient than our existing "over-complicated" grouping because the server would automatically sort by the ID.) Anyway, to protect the little guys, I had to restrict their rights. All they can do as administrator is backup the data.



One more thing, due to industry regulations some of the of the data is encrypted before being stored. I can't let them accidently edit records through SQL manager either.



Thanks in advance for any help you can provide.

View 6 Replies View Related

Can Not Connect To SQL Server Express After Installation

Jan 13, 2008

 Hi everyone I have some problems with SQL server. I just installed the SQL Server 2005 express edition on my computer. And after installation, i cannot connect to it. I don't have any firewalls on my computer, and in the installation I have chosen to be able to log in with both (windows authentification or sql authentification). Both authentifications doesn't work when I tried to log in The following is the error I get :"Cannot connect to localhost. An error has occurred while establishing a connection to the server. When connecting to SQL server 2005, this failure may be caused byt he fact that under the default settings SQL server does not allow remote connections."Can somebody please help me ?
 

View 3 Replies View Related

SQL Server Express Installation Issues

Apr 22, 2006

I have an issue with installation of Microsoft SQL Server Express Edition on my machine . I am using the following environmentAMD Athlon 2800+ 64 bit processor512 Mb RAMWindows XP Professional Edition.Visual Studio 2005 Professional Edition.The installation simply errors out at startup. Can somebody help me out to fix the problem?

View 1 Replies View Related

Sql Server Express Installation Problem

Dec 21, 2006

when i install sql server 2005 express, it runs till configuration check. After saying configuration check all ok, it says the error message "Microsoft SQL Server Setup Error writing to file: Access is denied." ". Verify that you have access to that directory". The temp files are getting extrated to "d:" which has full file permission. please let me know what is happening.

View 1 Replies View Related

Sql Server Express 2005| Installation

Oct 29, 2006

Dear Sir/madam

While installing sql server express 2005 get an error message install latest version using sqlnci.msi . Please let me know from where i can find or download sqlnci.msi



This error comes while installing native client option

With regards



Anil







View 1 Replies View Related

??? SQL Server Express SP2 Installation Dies ???

Jun 6, 2007

Hello all,



I'm trying to install "SQL Server 2005 Express Edition SP2".



I downloaded "SQLEXPR32.EXE" (38,220,656 bytes) from the Microsoft site.



At the beginning of the setup the installation program scans my system -- no problems or warnings. Everything looks fine.



During installation I uncheck, "Hide advanced configuration options" simply because I want to change the default instance name. I make no other changes to the default installation.



The installation starts up but when it tries to install the "SQL Native Client" I get the following error dialog message:



"An installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'."



That's an odd message to receive since I am *not* even trying to install the SQL Native Client.



Does anyone have an idea of what might be causing this to happen. I've install SSE many times in the past with no problems.



Thanks



View 1 Replies View Related

How To Set And Use SQL Server Express 2005 After Installation?

Feb 27, 2007

I have never used SQL Server, except that I did use MS Access, so after I downloading and installing the SQL Server Express 2005 ... I really do not know how to make it works!

1. Let say I would like to create a table at my local computer (1st) as a Server, how I do it (configuration)?

2. Then I have a second PC, as a client how I link to that table?

Might be they are 2 silly questions, but I would like to try out the new SQL Server Express and compare what are the better features with MS Access!

Thanks to any help

View 1 Replies View Related

SQL Server Express Installation Issue

Nov 10, 2006

I am trying (unsuccessfully!) to install at a client site.

They're running W2K SP4 which has never had any instance of SQL of any flavour installed.

The install seems to be failing at the same place each time. I have tried complete uninstalls of SQL and associated components but to no avail.

Here is the contents of Summary.txt:


Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows 2000 Service Pack 4 (Build 2195)
Time : Fri Nov 10 10:13:13 2006

Machine : ALC
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.1.2047.00
Install : Failed
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_ALC_WI.log
Error Number : 1603
--------------------------------------------------------------------------------

SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.


Time : Fri Nov 10 10:24:18 2006


List of log files:
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_ALC_Core(Local).log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_ALC_Datastore.xml
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_ALC_.NET Framework 2.0.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_ALC_SNAC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_ALC_Core.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_ALC_Support.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_ALC_SCC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_ALC_WI.log


And then part of the WI.log which is where it appears to be failing...

=== Logging started: 10/11/2006 10:15:01 ===
MSI (c) (5C:FC) [10:15:01:699]: Note: 1: 2205 2: 3: PatchPackage
MSI (c) (5C:FC) [10:15:01:699]: Machine policy value 'DisableRollback' is 0
MSI (c) (5C:FC) [10:15:01:699]: User policy value 'DisableRollback' is 0
MSI (c) (5C:FC) [10:15:01:699]: PROPERTY CHANGE: Adding UILevel property. Its value is '5'.
MSI (c) (5C:FC) [10:15:01:699]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
MSI (c) (5C:FC) [10:15:01:699]: Doing action: INSTALL
Action 10:15:01: INSTALL.
Action start 10:15:01: INSTALL.
MSI (c) (5C:FC) [10:15:01:699]: UI Sequence table 'InstallUISequence' is present and populated.
MSI (c) (5C:FC) [10:15:01:699]: Running UISequence
MSI (c) (5C:FC) [10:15:01:699]: PROPERTY CHANGE: Adding EXECUTEACTION property. Its value is 'INSTALL'.
MSI (c) (5C:FC) [10:15:01:699]: Doing action: CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128
Action 10:15:01: CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128.
Action start 10:15:01: CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128.
MSI (c) (5C:FC) [10:15:01:699]: PROPERTY CHANGE: Adding CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 property. Its value is 'C:Program FilesCommon Files'.
Action ended 10:15:01: CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128. Return value 1.
MSI (c) (5C:FC) [10:15:01:699]: Doing action: SystemFolder.7188DA12_A95E_46B7_8623_9D93B5260E2A
Action 10:15:01: SystemFolder.7188DA12_A95E_46B7_8623_9D93B5260E2A.
Action start 10:15:01: SystemFolder.7188DA12_A95E_46B7_8623_9D93B5260E2A.
MSI (c) (5C:FC) [10:15:01:699]: PROPERTY CHANGE: Adding SystemFolder.7188DA12_A95E_46B7_8623_9D93B5260E2A property. Its value is 'C:WINNTsystem32'.
Action ended 10:15:01: SystemFolder.7188DA12_A95E_46B7_8623_9D93B5260E2A. Return value 1.
MSI (c) (5C:FC) [10:15:01:715]: Doing action: CommonFilesFolder.808C44A0_9EC0_4446_A4CB_3E51F5C5D59F
Action 10:15:01: CommonFilesFolder.808C44A0_9EC0_4446_A4CB_3E51F5C5D59F.
Action start 10:15:01: CommonFilesFolder.808C44A0_9EC0_4446_A4CB_3E51F5C5D59F.
MSI (c) (5C:FC) [10:15:01:715]: PROPERTY CHANGE: Adding CommonFilesFolder.808C44A0_9EC0_4446_A4CB_3E51F5C5D59F property. Its value is 'C:Program FilesCommon Files'.
Action ended 10:15:01: CommonFilesFolder.808C44A0_9EC0_4446_A4CB_3E51F5C5D59F. Return value 1.
MSI (c) (5C:FC) [10:15:01:715]: Doing action: SystemFolder.60A85CA1_D9D8_43FA_9DD5_574BEF970F9F
Action 10:15:01: SystemFolder.60A85CA1_D9D8_43FA_9DD5_574BEF970F9F.
Action start 10:15:01: SystemFolder.60A85CA1_D9D8_43FA_9DD5_574BEF970F9F.
MSI (c) (5C:FC) [10:15:01:715]: PROPERTY CHANGE: Adding SystemFolder.60A85CA1_D9D8_43FA_9DD5_574BEF970F9F property. Its value is 'C:WINNTsystem32'.
Action ended 10:15:01: SystemFolder.60A85CA1_D9D8_43FA_9DD5_574BEF970F9F. Return value 1.
MSI (c) (5C:FC) [10:15:01:715]: Doing action: WindowsFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E
Action 10:15:01: WindowsFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E.
Action start 10:15:01: WindowsFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:715]: PROPERTY CHANGE: Adding WindowsFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNT'.
Action ended 10:15:01: WindowsFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:715]: Doing action: SystemFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E
Action 10:15:01: SystemFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E.
Action start 10:15:01: SystemFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:715]: PROPERTY CHANGE: Adding SystemFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNTsystem32'.
Action ended 10:15:01: SystemFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:715]: Doing action: WindowsFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E
Action 10:15:01: WindowsFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E.
Action start 10:15:01: WindowsFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:715]: PROPERTY CHANGE: Adding WindowsFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNT'.
Action ended 10:15:01: WindowsFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:715]: Doing action: SystemFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E
Action 10:15:01: SystemFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E.
Action start 10:15:01: SystemFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:715]: PROPERTY CHANGE: Adding SystemFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNTsystem32'.
Action ended 10:15:01: SystemFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:715]: Doing action: WindowsFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Action 10:15:01: WindowsFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E.
Action start 10:15:01: WindowsFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:715]: PROPERTY CHANGE: Adding WindowsFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNT'.
Action ended 10:15:01: WindowsFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:715]: Doing action: SystemFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Action 10:15:01: SystemFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E.
Action start 10:15:01: SystemFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:715]: PROPERTY CHANGE: Adding SystemFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNTsystem32'.
Action ended 10:15:01: SystemFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:715]: Doing action: WindowsFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E
Action 10:15:01: WindowsFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E.
Action start 10:15:01: WindowsFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:715]: PROPERTY CHANGE: Adding WindowsFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNT'.
Action ended 10:15:01: WindowsFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:715]: Doing action: SystemFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E
Action 10:15:01: SystemFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E.
Action start 10:15:01: SystemFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:715]: PROPERTY CHANGE: Adding SystemFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNTsystem32'.
Action ended 10:15:01: SystemFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:715]: Doing action: WindowsFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E
Action 10:15:01: WindowsFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E.
Action start 10:15:01: WindowsFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:731]: PROPERTY CHANGE: Adding WindowsFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNT'.
Action ended 10:15:01: WindowsFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:731]: Doing action: SystemFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E
Action 10:15:01: SystemFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E.
Action start 10:15:01: SystemFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:731]: PROPERTY CHANGE: Adding SystemFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNTsystem32'.
Action ended 10:15:01: SystemFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:731]: Doing action: WindowsFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E
Action 10:15:01: WindowsFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E.
Action start 10:15:01: WindowsFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:731]: PROPERTY CHANGE: Adding WindowsFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNT'.
Action ended 10:15:01: WindowsFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:731]: Doing action: SystemFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E
Action 10:15:01: SystemFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E.
Action start 10:15:01: SystemFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:731]: PROPERTY CHANGE: Adding SystemFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNTsystem32'.
Action ended 10:15:01: SystemFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:731]: Doing action: WindowsFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Action 10:15:01: WindowsFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E.
Action start 10:15:01: WindowsFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:731]: PROPERTY CHANGE: Adding WindowsFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNT'.
Action ended 10:15:01: WindowsFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:731]: Doing action: SystemFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Action 10:15:01: SystemFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E.
Action start 10:15:01: SystemFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:731]: PROPERTY CHANGE: Adding SystemFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNTsystem32'.
Action ended 10:15:01: SystemFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:731]: Doing action: WindowsFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
Action 10:15:01: WindowsFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E.
Action start 10:15:01: WindowsFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:731]: PROPERTY CHANGE: Adding WindowsFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNT'.
Action ended 10:15:01: WindowsFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:731]: Doing action: SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
Action 10:15:01: SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E.
Action start 10:15:01: SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E.
MSI (c) (5C:FC) [10:15:01:731]: PROPERTY CHANGE: Adding SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E property. Its value is 'C:WINNTsystem32'.
Action ended 10:15:01: SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E. Return value 1.
MSI (c) (5C:FC) [10:15:01:731]: Doing action: ProgramMenuFolder.ConfigurationTools1033
Action 10:15:01: ProgramMenuFolder.ConfigurationTools1033.
Action start 10:15:01: ProgramMenuFolder.ConfigurationTools1033.
MSI (c) (5C:FC) [10:15:01:731]: PROPERTY CHANGE: Adding ProgramMenuFolder.ConfigurationTools1033 property. Its value is 'C:Documents and SettingsAll UsersStart MenuPrograms'.
Action ended 10:15:01: ProgramMenuFolder.ConfigurationTools1033. Return value 1.
MSI (c) (5C:FC) [10:15:01:731]: Doing action: ProgramFilesFolder.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action 10:15:01: ProgramFilesFolder.D20239D7_E87C_40C9_9837_E70B8D4882C2.
Action start 10:15:01: ProgramFilesFolder.D20239D7_E87C_40C9_9837_E70B8D4882C2.
MSI (c) (5C:FC) [10:15:01:731]: PROPERTY CHANGE: Adding ProgramFilesFolder.D20239D7_E87C_40C9_9837_E70B8D4882C2 property. Its value is 'C:Program Files'.
Action ended 10:15:01: ProgramFilesFolder.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 1.
MSI (c) (5C:FC) [10:15:01:731]: Skipping action: SetMDACSxS (condition is false)
MSI (c) (5C:FC) [10:15:01:731]: Doing action: InitDlg
Action 10:15:01: InitDlg.
Action start 10:15:01: InitDlg.
Info 2898.The installer has encountered an unexpected error. The error code is 2898. For DlgTextStyle textstyle, the system created a 'Tahoma' font, in 0 character set.
Info 2898.The installer has encountered an unexpected error. The error code is 2898. For ButtonTextStyle textstyle, the system created a 'Tahoma' font, in 0 character set.
Info 2898.The installer has encountered an unexpected error. The error code is 2898. For Tahoma8 textstyle, the system created a 'Tahoma' font, in 0 character set.
Info 2898.The installer has encountered an unexpected error. The error code is 2898. For DlgTextStyleB textstyle, the system created a 'Tahoma' font, in 0 character set.
Info 2898.The installer has encountered an unexpected error. The error code is 2898. For DlgTitleStyleB textstyle, the system created a 'Tahoma' font, in 0 character set.
Action 10:15:01: InitDlg. Dialog created
Action ended 10:15:01: InitDlg. Return value 1.
MSI (c) (5C:FC) [10:15:01:746]: Doing action: SetInstanceName
Action 10:15:01: SetInstanceName.
Action start 10:15:01: SetInstanceName.
MSI (c) (5C:FC) [10:15:01:746]: PROPERTY CHANGE: Adding SqlInstanceName property. Its value is 'SQLExpress'.
Action ended 10:15:01: SetInstanceName. Return value 1.
MSI (c) (5C:FC) [10:15:01:746]: Doing action: SetInitStatus
Action 10:15:01: SetInitStatus.
Action start 10:15:01: SetInitStatus.
MSI (c) (5C:FC) [10:15:01:746]: PROPERTY CHANGE: Adding InitStatus property. Its value is '0'.
Action ended 10:15:01: SetInitStatus. Return value 1.
MSI (c) (5C:FC) [10:15:01:746]: Doing action: SetUpgradeUser
Action 10:15:01: SetUpgradeUser.
Action start 10:15:01: SetUpgradeUser.
Action ended 10:15:01: SetUpgradeUser. Return value 1.
MSI (c) (5C:FC) [10:15:01:746]: Doing action: UnsetErrorReportingUI
Action 10:15:01: UnsetErrorReportingUI.
Action start 10:15:01: UnsetErrorReportingUI.
Action ended 10:15:01: UnsetErrorReportingUI. Return value 1.
MSI (c) (5C:FC) [10:15:01:762]: Skipping action: SetCluster (condition is false)
MSI (c) (5C:FC) [10:15:01:762]: Doing action: UnsetSqmReportingUI
Action 10:15:01: UnsetSqmReportingUI.
Action start 10:15:01: UnsetSqmReportingUI.
Action ended 10:15:01: UnsetSqmReportingUI. Return value 1.
MSI (c) (5C:FC) [10:15:01:762]: Doing action: SetClusterSec
Action 10:15:01: SetClusterSec.
Action start 10:15:01: SetClusterSec.
Action ended 10:15:01: SetClusterSec. Return value 1.
MSI (c) (5C:FC) [10:15:01:762]: Doing action: SetEnableRanuUI
Action 10:15:01: SetEnableRanuUI.
Action start 10:15:01: SetEnableRanuUI.
Action ended 10:15:01: SetEnableRanuUI. Return value 1.
MSI (c) (5C:FC) [10:15:01:762]: Doing action: SetUpgradePwd
Action 10:15:01: SetUpgradePwd.
Action start 10:15:01: SetUpgradePwd.
Action ended 10:15:01: SetUpgradePwd. Return value 1.
MSI (c) (5C:FC) [10:15:01:762]: Skipping action: UnsetEnableRanuUI (condition is false)
MSI (c) (5C:FC) [10:15:01:762]: Skipping action: ErrorDisableNetworkProtocols (condition is false)
MSI (c) (5C:FC) [10:15:01:762]: Skipping action: SetSharedVolumePath (condition is false)
MSI (c) (5C:FC) [10:15:01:762]: Skipping action: UnsetINSTALLSQLDATADIR (condition is false)
MSI (c) (5C:FC) [10:15:01:762]: Doing action: LaunchConditions
Action 10:15:01: LaunchConditions. Evaluating launch conditions
Action start 10:15:01: LaunchConditions.
MSI (c) (5C:FC) [10:15:01:762]: Note: 1: 2205 2: 3: LaunchCondition
MSI (c) (5C:FC) [10:15:01:762]: Note: 1: 2228 2: 3: LaunchCondition 4: SELECT `Condition`, `Description` FROM `LaunchCondition`
Action ended 10:15:01: LaunchConditions. Return value 0.
MSI (c) (5C:FC) [10:15:01:762]: Skipping action: SetSqlDisableNetworkProtocols.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 (condition is false)
MSI (c) (5C:FC) [10:15:01:762]: Doing action: StreamSupportFiles.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action 10:15:01: StreamSupportFiles.D20239D7_E87C_40C9_9837_E70B8D4882C2. Extracting custom action file from stream
Action start 10:15:01: StreamSupportFiles.D20239D7_E87C_40C9_9837_E70B8D4882C2.
MSI (c) (5C:18) [10:15:01:762]: Invoking remote custom action. DLL: C:DOCUME~1ADMINI~1.MSJLOCALS~1Temp1MSI19.tmp, Entrypoint: StreamSupportFiles
MSI (c) (5C:80) [10:15:01:778]: Cloaking enabled.
MSI (c) (5C:80) [10:15:01:778]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (5C:80) [10:15:01:778]: Connected to service for CA interface.
Action ended 10:15:02: StreamSupportFiles.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
MSI (c) (5C:FC) [10:15:02:137]: Skipping action: FatalError (condition is false)
Action ended 10:15:02: INSTALL. Return value 3.
MSI (c) (5C:8C) [10:24:17:387]: Destroying RemoteAPI object.
MSI (c) (5C:80) [10:24:17:387]: Custom Action Manager thread ending.



If anyone can shed light on this it would be most appreciated.



Andy

View 3 Replies View Related

Get SQL Server Express Installation Path

Mar 26, 2008

Hi, i would like to know if there's a way to know the path where my sql server is located, i need to know this because i've an application (VB .NET) that needs to know this path, any help?

View 1 Replies View Related

Failed SQL Server Express Installation

May 15, 2007

I have tried everything. The installation keeps failing and it seems to be a problem with WMI. Here is my installation summary and the error part of my wmidiag report. Can some one please help.



icrosoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Mon May 14 21:05:07 2007

PROHOMESTEVEMAC : The current system does not meet recommended hardware requirements for this SQL Server release. For detailed hardware requirements, see the readme file or SQL Server Books Online.
Machine : PROHOMESTEVEMAC
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.2047.00
Install : Successful
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : PROHOMESTEVEMAC
Product : Microsoft SQL Server Native Client
Product Version : 9.00.2047.00
Install : Successful
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : PROHOMESTEVEMAC
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.2047.00
Install : Successful
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : PROHOMESTEVEMAC
Product : MSXML 6.0 Parser
Product Version : 6.10.1129.0
Install : Successful
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : PROHOMESTEVEMAC
Product : SQL Server Database Services
Error : SQL Server Setup Failed to compile the Managed Object Format (MOF) file c:Program FilesMicrosoft SQL Server90Sharedsqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
--------------------------------------------------------------------------------
Machine : PROHOMESTEVEMAC
Product : SQL Server Database Services
Error : SQL Server Setup Failed to compile the Managed Object Format (MOF) file c:Program FilesMicrosoft SQL Server90Sharedsqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
--------------------------------------------------------------------------------
Machine : PROHOMESTEVEMAC
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.1.2047.00
Install : Failed
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup Failed to compile the Managed Object Format (MOF) file c:Program FilesMicrosoft SQL Server90Sharedsqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.
Error Number : 29513
--------------------------------------------------------------------------------

SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.


Time : Mon May 14 21:07:30 2007


List of log files:
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_Core(Local).log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_SQLSupport_1.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_SQLNCLI_1.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_SqlWriter_1.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_MSXML6_1.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_SQL.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_Datastore.xml
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_.NET Framework 2.0.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_Support.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_Core.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0027_PROHOMESTEVEMAC_SCC.log





28836 00:40:38 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
28837 00:40:38 (0) ** INFO: WMI ADAP status: .............................................................................................. 2.
28838 00:40:38 (0) ** => The WMI ADAP process is processing a performance library (2).
28839 00:40:38 (0) ** Some WMI performance classes could be missing at the time WMIDiag was executed.
28840 00:40:38 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
28841 00:40:38 (0) ** - ROOT/MICROSOFT/SQLSERVER, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
28842 00:40:38 (0) **
28843 00:40:38 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 1 ERROR(S)!
28844 00:40:38 (0) ** - ROOT/MICROSOFT/SQLSERVER, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
28845 00:40:38 (0) **
28846 00:40:38 (0) ** WMI GET operations: ................................................................................................. OK.
28847 00:40:38 (0) ** WMI MOF representations: ............................................................................................ OK.
28848 00:40:38 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
28849 00:40:38 (2) !! WARNING: WMI ENUMERATION operation errors reported: ................................................................. 1 WARNING(S)!
28850 00:40:38 (0) ** - Root/Default, InstancesOf, 'SystemRestore' did not return any instance while AT LEAST 1 instance is expected.
28851 00:40:38 (0) ** MOF Registration: 'C:WINDOWSSYSTEM32WBEMSR.MOF'
28852 00:40:38 (0) **
28853 00:40:38 (2) !! WARNING: WMI EXECQUERY operation errors reported: ................................................................... 1 WARNING(S)!
28854 00:40:38 (0) ** - Root/Default, 'SELECT * FROM SystemRestore' did not return any instance while AT LEAST 1 instance is expected.
28855 00:40:38 (0) **
28856 00:40:38 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
28857 00:40:38 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
28858 00:40:38 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
28859 00:40:38 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
28860 00:40:38 (0) ** WMI static instances retrieved: ..................................................................................... 988.
28861 00:40:38 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
28862 00:40:38 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 0.
28863 00:40:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
28864 00:40:38 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
28865 00:40:38 (0) ** DCOM: ............................................................................................................. 3024.
28866 00:40:38 (0) ** WINMGMT: .......................................................................................................... 5.
28867 00:40:38 (0) ** WMIADAPTER: ....................................................................................................... 0.
28868 00:40:38 (0) ** => Verify the WMIDiag LOG at line #19321 for more details.
28869 00:40:38 (0) **
28870 00:40:38 (0) ** # of additional Event Log events AFTER WMIDiag execution:
28871 00:40:38 (0) ** DCOM: ............................................................................................................. 0.
28872 00:40:38 (0) ** WINMGMT: .......................................................................................................... 1.
28873 00:40:38 (0) ** WMIADAPTER: ....................................................................................................... 0.
28874 00:40:38 (2) !! WARNING: => Verify the WMIDiag LOG at line #28428 for more details.
28875 00:40:38 (0) **
28876 00:40:38 (0) ** 2 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
28877 00:40:38 (0) ** => This error is typically a WMI error. This WMI error is due to:
28878 00:40:38 (0) ** - a missing WMI class definition or object.
28879 00:40:38 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
28880 00:40:38 (0) ** You can correct the missing class definitions by:
28881 00:40:38 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
28882 00:40:38 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
28883 00:40:38 (0) ** (This list can be built on a similar and working WMI Windows installation)
28884 00:40:38 (0) ** The following command line must be used:
28885 00:40:38 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
28886 00:40:38 (0) ** - a WMI repository corruption.
28887 00:40:38 (0) ** Under Windows XP SP2, you can validate the repository consistency
28888 00:40:38 (0) ** by executing the following command:
28889 00:40:38 (0) ** i.e. 'WMIDiag CheckConsistency'
28890 00:40:38 (0) ** Note: Under Windows XP SP2, when the repository is checked and detected INCONSISTENT,
28891 00:40:38 (0) ** a new repository is automatically re-created based on Auto-Recovery mechanism.
28892 00:40:38 (0) ** Note that some information can be lost during this process (i.e. static data, CIM registration).
28893 00:40:38 (0) ** However, the original repository is located at 'C:WINDOWSSYSTEM32WBEMRepository.001'.
28894 00:40:38 (0) ** The computer must be rebooted for the system to work with the re-created repository.
28895 00:40:38 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
28896 00:40:38 (0) ** otherwise some applications may fail after the reconstruction.
28897 00:40:38 (0) ** This can be achieved with the following command:
28898 00:40:38 (0) ** i.e. 'WMIDiag ShowMOFErrors'
28899 00:40:38 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
28900 00:40:38 (0) ** ALL fixes previously mentioned.
28901 00:40:38 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
28902 00:40:38 (0) **
28903 00:40:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
28904 00:40:38 (0) ** WMI Registry key setup: ............................................................................................. OK.
28905 00:40:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
28906 00:40:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
28907 00:40:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
28908 00:40:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
28909 00:40:38 (0) **
28910 00:40:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
28911 00:40:38 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
28912 00:40:38 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
28913 00:40:38 (0) **
28914 00:40:38 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:DOCUMENTS AND SETTINGSSTEVE HOFERLOCAL SETTINGSTEMPWMIDIAG-V2.0_XP___.CLI.SP2.32_PROHOMESTEVEMAC_2007.05.15_00.37.32.LOG' for details.
28915 00:40:38 (0) **
28916 00:40:38 (0) ** WMIDiag v2.0 ended on Tuesday, May 15, 2007 at 00:40 (W:59 E:6 S:1).

View 1 Replies View Related

SQL Server Express Fails To Install

May 2, 2006

I'm experiencing a problem installing SQL Server Express 2005. I thought I had the same problem as Tom from a recent thread but his error file is quite different from mine. The Visual Basic Express
package properly installed everything except SQL Server. I've run
it many times, but the service fails
to start. I also downloaded the separate installation package for
SQL Server Express and ran it several times, which also failed.
It gets to a point where the services are installed, but when I try to
manually start the SQL service it says that the service started and
then stopped. The event
viewer shows this error:

Product: Microsoft SQL Server 2005 Express Edition -- Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067) The process terminated unexpectedly.

The error log is:

2006-05-02 16:10:58.07 Server Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86)
Apr 14 2006 01:12:25
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

2006-05-02 16:10:58.08 Server (c) 2005 Microsoft Corporation.
2006-05-02 16:10:58.08 Server All rights reserved.
2006-05-02 16:10:58.09 Server Server process ID is 816.
2006-05-02 16:10:58.09 Server Logging SQL Server messages in file 'c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'.
2006-05-02 16:10:58.09 Server This instance of SQL Server last reported using a process ID of 2748 at 5/2/2006 4:10:29 PM (local) 5/2/2006 9:10:29 PM (UTC). This is an informational message only; no user action is required.
2006-05-02 16:10:58.15 Server Registry startup parameters:
2006-05-02 16:10:58.15 Server -d c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf
2006-05-02 16:10:58.15 Server -e c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG
2006-05-02 16:10:58.16 Server -l c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf
2006-05-02 16:10:58.28 Server Error: 17311, Severity: 16, State: 1.
2006-05-02 16:10:58.28 Server SQL Server is terminating because of fatal exception c000001d. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
2006-05-02 16:10:58.30 Server Using 'dbghelp.dll' version '4.0.5'
2006-05-02 16:10:58.36 Server **Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
2006-05-02 16:10:58.36 Server ***Stack Dump being sent to c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGSQLDump0005.txt
2006-05-02 16:10:58.36 Server * *******************************************************************************
2006-05-02 16:10:58.36 Server *
2006-05-02 16:10:58.36 Server * BEGIN STACK DUMP:
2006-05-02 16:10:58.36 Server * 05/02/06 16:10:58 spid 0
2006-05-02 16:10:58.36 Server *
2006-05-02 16:10:58.36 Server * ex_handle_except encountered exception C000001D - Server terminating
2006-05-02 16:10:58.36 Server *
2006-05-02 16:10:58.36 Server *
2006-05-02 16:10:58.36 Server * MODULE BASE END SIZE
2006-05-02 16:10:58.36 Server * sqlservr 01000000 02BCEFFF 01bcf000
2006-05-02 16:10:58.36 Server * ntdll 7C900000 7C9AFFFF 000b0000
2006-05-02 16:10:58.36 Server * kernel32 7C800000 7C8F3FFF 000f4000
2006-05-02 16:10:58.36 Server * MSVCR80 78130000 781CAFFF 0009b000
2006-05-02 16:10:58.36 Server * msvcrt 77C10000 77C67FFF 00058000
2006-05-02 16:10:58.37 Server * MSVCP80 7C420000 7C4A6FFF 00087000
2006-05-02 16:10:58.37 Server * ADVAPI32 77DD0000 77E6AFFF 0009b000
2006-05-02 16:10:58.37 Server * RPCRT4 77E70000 77F00FFF 00091000
2006-05-02 16:10:58.37 Server * USER32 77D40000 77DCFFFF 00090000
2006-05-02 16:10:58.37 Server * GDI32 77F10000 77F56FFF 00047000
2006-05-02 16:10:58.37 Server * CRYPT32 77A80000 77B13FFF 00094000
2006-05-02 16:10:58.37 Server * MSASN1 77B20000 77B31FFF 00012000
2006-05-02 16:10:58.37 Server * Secur32 77FE0000 77FF0FFF 00011000
2006-05-02 16:10:58.37 Server * MSWSOCK 71A50000 71A8EFFF 0003f000
2006-05-02 16:10:58.37 Server * WS2_32 71AB0000 71AC6FFF 00017000
2006-05-02 16:10:58.37 Server * WS2HELP 71AA0000 71AA7FFF 00008000
2006-05-02 16:10:58.37 Server * USERENV 769C0000 76A72FFF 000b3000
2006-05-02 16:10:58.37 Server * opends60 333E0000 333E6FFF 00007000
2006-05-02 16:10:58.37 Server * NETAPI32 5B860000 5B8B3FFF 00054000
2006-05-02 16:10:58.37 Server * SHELL32 7C9C0000 7D1D4FFF 00815000
2006-05-02 16:10:58.37 Server * SHLWAPI 77F60000 77FD5FFF 00076000
2006-05-02 16:10:58.37 Server * OCMAPIHK 10000000 1000CFFF 0000d000
2006-05-02 16:10:58.37 Server * comctl32 773D0000 774D1FFF 00102000
2006-05-02 16:10:58.37 Server * comctl32 5D090000 5D126FFF 00097000
2006-05-02 16:10:58.37 Server * psapi 76BF0000 76BFAFFF 0000b000
2006-05-02 16:10:58.37 Server * instapi 48060000 48069FFF 0000a000
2006-05-02 16:10:58.37 Server * sqlevn70 4F610000 4F7A3FFF 00194000
2006-05-02 16:10:58.37 Server * dbghelp 03000000 03112FFF 00113000
2006-05-02 16:10:58.37 Server *
2006-05-02 16:10:58.37 Server * Edi: 0075C528: 000E1068 00000000 00000000 00000000 0075C548 00000000
2006-05-02 16:10:58.37 Server * Esi: 00000000:
2006-05-02 16:10:58.37 Server * Eax: 0075C40C: 000042AC 00000000 00000000 7C81EB33 00000000 0000000C
2006-05-02 16:10:58.37 Server * Ebx: 0000003F:
2006-05-02 16:10:58.38 Server * Ecx: 0075CA7C: 00000000 0001001F 00000000 00000000 00000000 00000000
2006-05-02 16:10:58.38 Server * Edx: 0000003D:
2006-05-02 16:10:58.38 Server * Eip: 7C81EB33: 10C2C95E 0FFF8500 FED0E68E FC558BFF 0F0C5589 7D8B16B7
2006-05-02 16:10:58.38 Server * Ebp: 0075C45C: 0075C4A0 02187744 000042AC 00000000 00000000 00000000
2006-05-02 16:10:58.38 Server * SegCs: 0000001B:
2006-05-02 16:10:58.38 Server * EFlags: 00080246:
2006-05-02 16:10:58.38 Server * Esp: 0075C408: 00000000 000042AC 00000000 00000000 7C81EB33 00000000
2006-05-02 16:10:58.38 Server * SegSs: 00000023:
2006-05-02 16:10:58.38 Server * *******************************************************************************
2006-05-02 16:10:58.38 Server * -------------------------------------------------------------------------------
2006-05-02 16:10:58.38 Server * Short Stack Dump
2006-05-02 16:10:58.50 Server 7C81EB33 Module(kernel32+0001EB33)
2006-05-02 16:10:58.50 Server 02187744 Module(sqlservr+01187744)
2006-05-02 16:10:58.51 Server 0218B600 Module(sqlservr+0118B600)
2006-05-02 16:10:58.51 Server 0218B1AD Module(sqlservr+0118B1AD)
2006-05-02 16:10:58.51 Server 023F4109 Module(sqlservr+013F4109)
2006-05-02 16:10:58.51 Server 7C862CD3 Module(kernel32+00062CD3)
2006-05-02 16:10:58.57 Server 7C83AA6B Module(kernel32+0003AA6B)
2006-05-02 16:10:58.60 Server Stack Signature for the dump is 0xDF483EDE
2006-05-02 16:10:59.33 Server External dump process return code 0x20000001.
External dump process returned no errors.

Any thoughts? Thanks.

View 8 Replies View Related

SQL Server Express Fails To Install

May 5, 2006

I have tried several times to install SSEE and SSEE
with Advanced Services. Each time it fails early in the
installation. I am running XP SP2 with 1GB memory. There
was no previous install of SSEE. The error reads, "SQL Server
Setup unexpectedly fialed. For more information, review the Setup
summary log file...". The log file follows:



Microsoft SQL Server 2005 Setup beginning at Thu May 04 20:58:25 2006

Process ID : 2000

c:a9b2b8f496f31ae4f8a6setup.exe Version: 2005.90.2047.0

Running: LoadResourcesAction at: 2006/4/4 20:58:24

Complete: LoadResourcesAction at: 2006/4/4 20:58:24, returned true

Running: ParseBootstrapOptionsAction at: 2006/4/4 20:58:24

Loaded DLL:c:a9b2b8f496f31ae4f8a6xmlrw.dll Version:2.0.3609.0

Complete: ParseBootstrapOptionsAction at: 2006/4/4 20:58:25, 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", "", "2000"} 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/4/4 20:58:25

Complete: ValidateWinNTAction at: 2006/4/4 20:58:25, returned true

Running: ValidateMinOSAction at: 2006/4/4 20:58:25

Complete: ValidateMinOSAction at: 2006/4/4 20:58:25, returned true

Running: PerformSCCAction at: 2006/4/4 20:58:25

Complete: PerformSCCAction at: 2006/4/4 20:58:25, returned true

Running: ActivateLoggingAction at: 2006/4/4 20:58:25

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"

00DECFC0Unable 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.

View 3 Replies View Related

SQL Server And Express Install Fails

Dec 3, 2007

I have a server version of SQL Server, but I need a local SQL Server Express version as well for dev.

When I install express and the full set of SQL Server management tools, I can see my Express instance in configuration manager, but Management Studio says the instance is broken. I have tried both SA and windows authentication. I turned on all the protocols in both server and client, but no luck.

The error returned is Error 26 Error locating server instance specified, but I am selecting the instance from the dropdown box, so it is not a typo. I have tried quite a few variations with no success.

The install is on XP-pro

Thanks,

Michael

View 4 Replies View Related

SQL Server Express Fails To Install

Jul 28, 2006

Hi, there!

I tried to install SSE 2005 and I got the following message:

SQL Server Setup unexpectedly failed. For more information, review the Setup summary log file in...

The log file has the content below. Can someone help me to fix this problem, please?

I have no idea about what is going on!

Thank you for the help!

Microsoft SQL Server 2005 Setup beginning at Sun Jul 23 12:52:54 2006
Process ID : 2420
c:97830b63babac24aedb48a81be43976asetup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2006/6/23 12:52:53
Complete: LoadResourcesAction at: 2006/6/23 12:52:53, returned true
Running: ParseBootstrapOptionsAction at: 2006/6/23 12:52:53
Loaded DLL:c:97830b63babac24aedb48a81be43976axmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2006/6/23 12:52:54, 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: Fri Jul 29 01:13:55 2005
Function Name: writeEncryptedString
Source Line Number: 124
----------------------------------------------------------
writeEncryptedString() failed
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Fri Jul 29 01:13:55 2005
Function Name: writeEncryptedString
Source Line Number: 123
----------------------------------------------------------
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.

Source File Name: cryptohelpercryptsameusersamemachine.cpp
Compiler Timestamp: Mon Jun 13 14:30:00 2005
Function Name: sqls::CryptSameUserSameMachine::ProtectData
Source Line Number: 50

2
Could not skip Component update due to datastore exception.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "2420"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Running: ValidateWinNTAction at: 2006/6/23 12:52:54
Complete: ValidateWinNTAction at: 2006/6/23 12:52:54, returned true
Running: ValidateMinOSAction at: 2006/6/23 12:52:54
Complete: ValidateMinOSAction at: 2006/6/23 12:52:54, returned true
Running: PerformSCCAction at: 2006/6/23 12:52:54
Complete: PerformSCCAction at: 2006/6/23 12:52:54, returned true
Running: ActivateLoggingAction at: 2006/6/23 12:52:54
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: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupStateScope.primaryLogFiles
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
00E2CFC4Unable 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: Fri Jul 29 01:13:50 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: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "2420"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupBootstrapOptionsScope.HostSetup
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Message pump returning: 2

View 4 Replies View Related

Trouble In Installation Of SQL Server Express Edition SP2

Mar 8, 2007

Hi I have Visual Studio 2005 with SP1 installed, and I want to install the Management Studio. I tried many times installing that and I always got the same problem, which is when I try to create a database in VS I just don’t get trough as I used to. A message appears saying that I’ve to enable some estance. So to resolve the problem I saw if is everything ok with the SQL Server, which seemed to be fine, but I couldn’t start the Report service.
            Now I just formatted the computer and I’m afraid to happen all over again. May be the version with only the Management would be fine, I don’t know if it adds something beside of that.  
 
            Thank you very much.

View 1 Replies View Related







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