Installation Problem: SQL Server Setup Failed To Compile Te Managed Object Format (MOF) File C:program FilesmicrosoftSQL Serv
Aug 2, 2007
When I install the SQL Server 2005 SP2 on my vista laptop, I get the following message: SQL server setup failed to compile te 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...
What did I wrong?
Greets,
Wouter
View 2 Replies
ADVERTISEMENT
Oct 2, 2005
I am trying to install SQL Server 2000 on a Win2K OS machine but Iget this error message:"A previous program installation created pending file operations onthe installation machine. You must restart the computer before runningsetup."I see others have had this problem but have fixed it using the solutionin:http://support.microsoft.com/defaul...kb;en-us;312995I have tried the solution but to no avail. The registry key:HKEY_LOCAL_MACHINESYSTEMCurrentControlSetContro lSessionManagerPendingFileRenameOperations keeps reappearing as soon as Iclose RegEdit.Any ideas?Thanks,lq
View 3 Replies
View Related
May 2, 2006
I'm trying in vain to upgrade sql server 2000 to 2005 with great headache and pain.
I (finally) have removed all Beta, and other incompatible version of .NET, Visual Studio and any other offending components, and made it to the first page of the install shield.
The .NET 2.0 components installed fine - but I get a fatal error trying to install the SQL Server Set Support Files.
I do have a log file - and have tired searching on the various error codes in it, but am coming up blank. Please advise - this is taking forever!
sample of error msgs in log file:
MSI (s) (B0:E0) [12:33:06:613]: Note: 1: 1935 2: 3: 0x8002802F 4: 5: CreateAssemblyNameObject 6: Microsoft.NetEnterpriseServers.ExceptionMessageBox,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"
MSI (s) (B0:E0) [12:33:06:613]: Product: Microsoft SQL Server Setup Support Files (English) -- Error 2908. The installer has encountered an unexpected error. The error code is 2908. Could not register component {1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.
MSI (s) (B0:E0) [12:33:06:613]: Executing op: ComponentRegister(ComponentId={52723CBD-3400-458C-988A-4D012E6CAEDB},KeyPath=<Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0",State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
Error 2908. The installer has encountered an unexpected error. The error code is 2908. Could not register component {1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.
MSI (s) (B0:E0) [12:33:06:629]: MSCOREE not loaded loading copy from system32
MSI (s) (B0:E0) [12:33:06:629]: Assembly Error:Function not defined in specified DLL.
MSI (s) (B0:E0) [12:33:06:629]: Note: 1: 1935 2: {52723CBD-3400-458C-988A-4D012E6CAEDB} 3: 0x8002802F 4: 5: CreateAssemblyNameObject 6: Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"
MSI (s) (B0:E0) [12:33:06:629]: Product: Microsoft SQL Server Setup Support Files (English) -- Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {52723CBD-3400-458C-988A-4D012E6CAEDB}
Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {52723CBD-3400-458C-988A-4D012E6CAEDB}
MSI (s) (B0:E0) [12:33:06:629]: User policy value 'DisableRollback' is 0
MSI (s) (B0:E0) [12:33:06:629]: Machine policy value 'DisableRollback' is 0
Action ended 12:33:06: InstallFinalize. Return value 3.
mandpenny
View 5 Replies
View Related
Aug 30, 2007
Hi
I have SQL Server 2000 (SP4) running on an Windows 2003 SP 1 server. I have started to get the error message "Connection to application object failed - Ensure no program modules have been deleted" when I go into Enterprise Manager.
I have tried reinstalled SQL Server and applied SP4 but to no effect. Can anyone help?
Mark
View 4 Replies
View Related
Oct 8, 2010
when 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 Related
Jul 10, 2007
I have created and deployed my first report. It renders fine for me and the other database admin. When others attempt to view it, we get the error
Query execution failed for data set 'periods'. (rsErrorExecutingCommand), For more information about this error navigate to the report server on the local server machine, or enable remote errors
Initially, We created a local group on the machine that hosts both the database and webserver and added the individuals to that group. Then, within SRS Report manager, we added that group to the Browswer role of the report.
The error message was slightly different, in that it couldn't even open the Datasource.
We then added an individual to the database as dbreader, and got the above message. It apprently is starting to render, and when it encounters the first query (dataset "periods", which populates a drop down list for a parameter), it chokes. BTW, the Periods dataset executes a stored procedure dbo.Period_List that has no parameters. It returns a list of reporting periods.
I could not figure out how to "enable remote errors" or find an error log on the server. The C:Program FilesMicrosoft SQL ServerMSSQL.3Reporting ServicesLogFiles Log files did not appear to record any errors.
Please advise!
View 6 Replies
View Related
Jul 20, 2005
I am looking for the SQL Server 2000 Licensing Setup Utility Programand cannot find it. Everything I read says, goto ControlPanel->Administrative Tools->SQL Server License Utility. When I gothere, I do not see... Any help would be Greatly appreciated!Setup:Win 2000 ServerSQL Server 2000 Standard Edition Svc Pk 3.Thanks.
View 2 Replies
View Related
Oct 23, 2006
Have run about six downlowds and all fail with same problem. The installer seems to be missing a file. all other parts of Viz studio Exp install but NOT the sql server exp.
Am I the only one getting this ? and if so what is the problem?. All other Visual Dev Express parts have instald OK.
Run on XP home SP2. As I posted this I noticed the compiler time stamp is 4 days ahead of real time ???
From the install log:
Complete: ParseBootstrapOptionsAction at: 2006/9/22 15:34:19, 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
View 5 Replies
View Related
Oct 10, 2015
During the installation of Adding node to a SQL Server failover cluster(On passive node) getting error like.. The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.We  run the below commands but didn’t get any resolution & got the same above error .
Â
1<sup>st</sup> Method…
1. Open console command (Run->CMD with administrator privileges).Â
2. net stop winmgmtÂ
3. Rename folder %windir%System32WbemRepository to other one, for backup purposes (for example _Repository).Â
4. net start winmgmt
2<sup>nd</sup>Â Method..
1. Disable and stop the WMI service.
a) Command : - sc config winmgmt start= disabled
b. Command : - Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â net stop winmgmt
2. Run the following commands.
a). Command: Winmgmt /salvagerepository %windir%System32wbem
b). Command: Â Winmgmt /resetrepository %windir%System32wbem
3. Re-enable the WMI service
Command:Â Â Â Â Â Â Â Â Â sc config winmgmt start= autoÂ
Last command to run after above steps
4. Command:Â Â Â Â mofcomp "%programfiles(x86)%Microsoft SQL Server100Sharedsqlmgmproviderxpsp2up.mof"
File not found Error for above command.
View 3 Replies
View Related
May 15, 2006
Hi,
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
View 5 Replies
View Related
Jan 21, 2008
I have a table with 2 row:
CREATE TABLE [dbo].[EABL](
[DSID] [int] IDENTITY(1,1) NOT NULL,
[ABLBELNR] [nvarchar](255) NULL)
If I make a XML formatfile which look like this:
<?xml version="1.0"?>
<BCPFORMAT ...>
<RECORD>
<FIELD ID="1" xsi:type="CharTerm" TERMINATOR=" " MAX_LENGTH="20"/>
</RECORD>
<ROW>
<COLUMN SOURCE="1" NAME="ABLBELNR" xsi:type="SQLNVARCHAR"/>
</ROW>
</BCPFORMAT>
then the import failed with the following error message:
[Microsoft][SQL Native Client]All bound columns are not read-only
If I delete the identity column then the import works correct.
What can I do, so that I can import with the identity column ?
Thanks for you help
Fasse
View 6 Replies
View Related
Nov 17, 2005
This forum is intended for users who are new to SQL Server, and have basic usage questions. If you have setup or installation issues or questions, you should check out the Setup forum.
Thanks
View 11 Replies
View Related
Sep 1, 2004
Hi, i tried to install MS SQL server 2000 in my XP system but during the setup service account installation, i tried to use a domain user account but it cannot validate my user name and password. I used my windows administrator logon account and password. Please help..thank you.
Thanks : :confused:
View 6 Replies
View Related
Oct 17, 2007
Evening,
I am very well versed in the proper way to set up a SQL Server server prior to installation.
In this I mean, the proper process in placing your MDF, LDF and NDF(s) on seperate spindles/discs and also to place TempDB on its own spindle/disc and such.
There are numerous other points to cover in setting up the server based on memory, security, processor and such but I am sure you understand.
What I am looking for is the link(s) to the whitepapers discussing these Best Practices methodologies for pre-installation setup.
I looked on the Best Practices page but did not seem to find a doc that contains all the Best Practices that should be followed, if possible of course, in setting up a server prior to the SQL Server 2005 installation process.
Can anyone please point me to a link(s)/doc(s) that describe what I am looking for.
I need to pass this information down to other members of my team.
Thanks and have a great day!
View 4 Replies
View Related
Dec 26, 2006
I installed SQL Server 2005.
In the add/remove programs are all the programs visible. But when I use "Start -> All programs -> Microsoft SQL Server 2005", there are only 5 configuration tools, no management studio.
What is going wrong?
Where can I find the executable that start up SQL Server 2005?
View 1 Replies
View Related
May 25, 2007
Hi!
I have created a setup in visual studio and set the sql server as a pre-requsites.
now when the setup is run from
setup.exe
it checks whether sql server is installed... if installed then continues otherwise install sql server express edition, now this installation is silent,
I need to set the sa password during installation of sql server . i have no option to set the password during installation, can any one help
View 1 Replies
View Related
Aug 2, 2004
Does anyone know if its possible to configure sql server 2000 so it reads in the date in a different format. Right now, it takes the date in the following format month day year. I want it to take in day month year instead.
I am using asp.net and that is properly configured to give day month year, but then this date is sent to sql server, i get into problems
please help
View 7 Replies
View Related
Apr 9, 2004
Please 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.
View 5 Replies
View Related
Feb 21, 2008
Hi,
I want to build a silent setup/installation of MS-SQL-Server-Express 2005 for installation on customers computers.
I want to integrate it in my own setup/installation routine of my application.
How can I do that?
Where can I get Infos or tutorials? Perhaps here ?
Sorry for my bad english
Regards Tron
View 7 Replies
View Related
Mar 18, 2007
heloo..
if I want to use full text search in my program, can I include Full Text Search service in my program setup silently in the same way as including SQL Express and .Net Framework to the setup project, Or I have to Install MS Sql Server 2005 on my customer computer?
View 1 Replies
View Related
Jul 21, 2005
Hi
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.
View 3 Replies
View Related
Jun 19, 2006
Hi,
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
View 1 Replies
View Related
Nov 6, 2007
hi,
Whenever i tried to install Sql Server 2005, the installation fails giving errors for
event logs and error logs
[microsoft][SQL Native Client][SQL Server]. The server could not load DCOM...
In the log file,
Property(S): Ver.7354AFCB_913B_4E9F_B76C_2376101FDE0C = c:Program FilesMicrosoft SQL Server90
Property(S): SqlTools.7354AFCB_913B_4E9F_B76C_2376101FDE0C = c:Program FilesMicrosoft SQL Server90Tools
Property(S): checksum.7354AFCB_913B_4E9F_B76C_2376101FDE0C = **********
Property(S): SqlInstance.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): InstanceRegKey.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = Microsoft SQL ServerMSSQL.1
Property(S): InstanceName.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = SQLEXPRESS
Property(S): PackagecodeChanging = 1
Property(S): SqlInstance.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceInstall.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
Property(S): SqlInstanceInstallDel.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
Property(S): ProductState = -1
Property(S): TRANSFORMS = qlRun01.mst;:InstID01.mst;:InstName01.mst
Property(S): PackageCode = {A81ED606-6AF4-48DA-A5D9-1AFCC4767FEE}
Property(S): SqlInstance.81902028_4743_45C1_9C8C_17223CBC7128 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.81902028_4743_45C1_9C8C_17223CBC7128 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.81902028_4743_45C1_9C8C_17223CBC7128 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstance.D5FA3BDB_C132_4ACB_9BCE_75B981C3A65B = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.D5FA3BDB_C132_4ACB_9BCE_75B981C3A65B = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.D5FA3BDB_C132_4ACB_9BCE_75B981C3A65B = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): MsiLogFileLocation = C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_SHITAL-PC_SQL.log
Property(S): Shared.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90Shared
Property(S): Ver.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlToolsBinRes.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90SharedResources
Property(S): SqlToolsBinRes1033.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90SharedResources1033
Property(S): SqlInstance.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstanceBinRes.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources
Property(S): SqlInstanceBinRes1033.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033
Property(S): SqlInstanceJet.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstanceOther.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstance.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstanceBinRes.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources
Property(S): SqlInstanceBinRes1033.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033
Property(S): sqlevn70.rll.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033sqlevn70.rll
Property(S): Shared.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90Shared
Property(S): Ver.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlSharedRes.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90SharedResources
Property(S): SqlSharedRes1033.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90SharedResources1033
Property(S): SqlVerComBin.FB04F6FB_D3EA_4FB5_B80C_362DD852A799 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.FB04F6FB_D3EA_4FB5_B80C_362DD852A799 = c:Program FilesMicrosoft SQL Server90
Property(S): InstanceName.FB04F6FB_D3EA_4FB5_B80C_362DD852A799 = SQLEXPRESS
Property(S): SqlInstance.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): InstanceName.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = SQLEXPRESS
Property(S): DataInstance.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): Data.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL Server
Property(S): DataInstanceData.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData
Property(S): DataInstanceBackup.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBackup
Property(S): DataInstanceLog.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOG
Property(S): DataInstanceTemplate.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLTemplate Data
Property(S): DataInstanceTxt.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): AdministratorsGroupQuoted = BUILTINAdministrators
Property(S): LocalSystemAccountQuoted = NT AUTHORITYSYSTEM
Property(S): QuotedServiceGroupSQL.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = SHITAL-PCSQLServer2005MSSQLUser$SHITAL-PC$SQLEXPRESS
Property(S): AdministratorsGroup = BUILTINAdministrators
Property(S): UsersGroupQuoted = BUILTINUsers
Property(S): UsersGroup = BUILTINUsers
Property(S): InstanceRegKey.BA9A7592_6647_4283_9B99_2885BD96A224 = Microsoft SQL ServerMSSQL.1
Property(S): DataInstance.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): Data.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL Server
Property(S): DataInstanceData.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData
Property(S): DataInstanceTemplate.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLTemplate Data
Property(S): DataInstanceTxt.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): ModuleID_SYSDB2 = 75D79626_87FB_4E9A_B07F_87DAE18D0F36
Property(S): SqlInstance.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): Data.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL Server
Property(S): DataInstance.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): DataInstanceRepldata.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
epldata
Property(S): DataInstanceTxt.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlVerComBin.779ED4A9_FDA8_4DBD_8D11_1C6CD6EE5AC7 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.779ED4A9_FDA8_4DBD_8D11_1C6CD6EE5AC7 = c:Program FilesMicrosoft SQL Server90
Property(S): TempFolder = c:UsersshitalAppDataLocalTemp
Property(S): DataInstance.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): Data.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL Server
Property(S): SqlTarget.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstance.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlInstanceBin.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): DataInstanceTxt.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): WORKINGDIRECTORY.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLREPLDATA
Property(S): InstanceRegKey.2F9C839A_286D_4B39_BD89_4DF4067604DF = Microsoft SQL ServerMSSQL.1
Property(S): SqlVerComBin.727FAD0C_033D_4A8B_8329_145D3EEA67B7 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.727FAD0C_033D_4A8B_8329_145D3EEA67B7 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBin.13676F0C_8438_4754_8C60_7ED008CBAB8D = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.13676F0C_8438_4754_8C60_7ED008CBAB8D = c:Program FilesMicrosoft SQL Server90
Property(S): MSVSPrivateAssembliesEN.13676F0C_8438_4754_8C60_7ED008CBAB8D = c:Program FilesMicrosoft SQL Server90COMen
Property(S): SqlVerComBin.8E491190_3328_49D2_9FFE_2D036D847DE2 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.8E491190_3328_49D2_9FFE_2D036D847DE2 = c:Program FilesMicrosoft SQL Server90
Property(S): WindowsFolder = c:Windows
Property(S): CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = c:Program FilesCommon Files
Property(S): MSShared.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = c:Program FilesCommon FilesMicrosoft Shared
Property(S): DatabaseRepl.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = c:Program FilesCommon FilesMicrosoft SharedDatabase Replication
Property(S): DatabaseReplRes.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = c:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources
Property(S): DatabaseReplRes1033.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = c:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources1033
Property(S): SqlVerComBin.8B75390F_DF2F_4C2C_92F5_9B83F3B36340 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.8B75390F_DF2F_4C2C_92F5_9B83F3B36340 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBin.889BED4C_E3F4_4943_956C_6FFD882F721F = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.889BED4C_E3F4_4943_956C_6FFD882F721F = c:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBin.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBinRes.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = c:Program FilesMicrosoft SQL Server90COMResources
Property(S): SqlVerComBinRes1033.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = c:Program FilesMicrosoft SQL Server90COMResources1033
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer$SQLEXPRESS
Property(S): SqlActionManaged = 3
Property(S): SqlNamedInstance = 1
Property(S): SqlStateManaged = 2
Property(S): RSVirtualDirectoryManager = Reports$SQLEXPRESS
Property(S): SOURCEDIR = c:2aae5517aa4b91d8f50a9cSetup
Property(S): SourcedirProduct = {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
Property(S): InstallNgenTicks = 110000
Property(S): SQLBROWSERSCMACCOUNT = NT AUTHORITYNetworkService
Property(S): SQLSCMACCOUNT = NT AUTHORITYNetworkService
Property(S): DebugClsid.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = {0D7C3EF4-D4A8-4796-9452-44FC73491B48}
Property(S): ProductToBeRegistered = 1
MSI (s) (24:44) [12:45:07:442]: Note: 1: 1708
MSI (s) (24:44) [12:45:07:442]: Product: Microsoft SQL Server 2005 Express Edition -- Installation failed.
MSI (s) (24:44) [12:45:07:443]: Windows Installer installed the product. Product Name: Microsoft SQL Server 2005 Express Edition. Product Version: 9.2.3042.00. Product Language: 1033. Installation success or error status: 1603.
MSI (s) (24:44) [12:45:07:457]: Cleaning up uninstalled install packages, if any exist
MSI (s) (24:44) [12:45:07:457]: MainEngineThread is returning 1603
MSI (s) (24:BC) [12:45:07:458]: Destroying RemoteAPI object.
MSI (s) (24:74) [12:45:07:459]: Custom Action Manager thread ending.
MSI (s) (24:BC) [12:45:07:460]: RESTART MANAGER: Session closed.
MSI (s) (24:BC) [12:45:07:460]: No System Restore sequence number for this installation.
=== Logging stopped: 11/6/2007 12:45:07 ===
MSI (c) (F0:98) [12:45:07:514]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (F0:98) [12:45:07:516]: MainEngineThread is returning 1603
=== Verbose logging stopped: 11/6/2007 12:45:07 ===
Can anyone provide me solution?
View 3 Replies
View Related
Nov 20, 2007
While 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.
View 2 Replies
View Related
Dec 6, 2006
One 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
View 7 Replies
View Related
Jun 14, 2006
I´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.
View 10 Replies
View Related
Jan 30, 2008
while installing SQL SERVER 2005 Express edition, I got the error below:
ITEM NAME VALUE
Link ID 20476
PRODUCT Name Microsoft SQL Server
Product Version 9.00.3042.00
Message Source setup.rll
Message ID 29503
EvtType sqlsetuplibservice.cpp@Do_sqlScrip
The installation always goes thru till the last stage of installing Database Service, while on configuring the Database engine, the error mesage will flag that Installation failed, the server could not be started.
following "help" suggestions, i tried to start the server manually thru command prompt but it never recognise the command as an internal command.
a close observation of the C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL file system reveals that the "Binn" and other folders were not there. I was able to notice this when i installed it on my system in the house.
what could be the problem and most importantly, the solution
thank you
View 8 Replies
View Related
Aug 30, 2006
I 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!
View 1 Replies
View Related
Sep 19, 2005
When 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 Related
Feb 23, 2007
SP2 refuses to install for the Database Engine because €œthe previous upgrade did not complete€?, i.e. it detects a suspended installation. The same thing happened to me when I installed SP1. I then remember opening the maintenance dialog and completing the setup, after which SP1 installed just fine.
When I try to do the same thing this time, I€™m presented with the €?complete the suspended installation€? option, which when I run it reports the installation completed successfully. However, in reality the installation still remains in suspended mode for whatever reason. If I reboot and open the maintenance dialog, I€™m still presented with the €?complete the suspended installation€? option. I€™ve even tried to run it more than once, but it doesn€™t help. Needless to say, SP2 still refuses to install.
I don't know why the installation is in a suspended state. I know every part of SP1 installed successfully in the end, and the computer never crashed during the installation. I've been using it every day since then, without any problems. All other parts of SP2 did install successfully.
I created a feedback entry on Microsoft Connect, where you can find the log files created by Windows Installer. The URL is:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=259606
Any ideas what I can do to resolve this problem?
View 1 Replies
View Related
Dec 28, 2006
I received the following error when installing SQL Server 2005:
The setup has encountered an unexpected error while Installing performance counters. The error is: -1073741790
View 2 Replies
View Related
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
