June 5, 2010 at 3:04 pm
On the install phase, I clicked Analysis, Reporting and Integration services including the database engine. I received errors on all 3 services, everything else installed fine. When I go into Reporting Services Configuration Connection and type in the server name "DOND-PC", click Find, I get this error message...."Unable to connect to the Report Server WMI provider - Details: Invalid Namespace". I'm sure I'm going to have questions on the other 2 services that didn't install properly. Is there something I didn't check on the install process? Is the server name the same as my computer name?
Any help is appreciated. Thanks, Don
June 8, 2010 at 11:35 am
If I were you I would investigate the errors that occured during installation before going too much further.
June 8, 2010 at 12:06 pm
Well, that's part of the problem too. None of the services, Report, Integration, Analysis install properly, they all fail. I've tried numerous installs, can get everything else to install fine, but none of the services. The text file that is logged is well "out of my realm" of understanding to be able to figure out what is wrong. There appears to be mentioned a few lines about 2003 MS office web components, but I already have that installed.
Do you know of any "cheat sheet" for getting the services to install properly?
Thanks, Don
June 8, 2010 at 12:48 pm
Generally speaking, the installation wizard is pretty good at telling you what you're missing in the way of software/configurations. The various problems I have encountered during installs have usually fixed by removing & reinstalling. If I were you I would get all available updates before you try and install again.
I would suggest doing a fresh install with just the database engine, troubleshoot that. This will keep the log smaller and make it easier to identify the error, which you can then research. Start with google or make a post here if you are really stuck.
Note that sometimes the error can appear at the end of the log, or sometimes in the middle, depending on the failure. Once you've got that, add the other services one by one in the same fashion.
EDIT: I should add that without the services installed, you don't have a SQL Server installation.
June 8, 2010 at 2:13 pm
The database engine installs just fine, so does everything else, just not the services. I'm thinking the services are not installing due to the UID and PWD, but not sure on that.
Here's the error from MS's website:
Details
Product: SQL Server
ID: 50000
Source: setup.rll
Version: 10.0
Component: SQL Server Native Client
Message: A network error occurred while attempting to read from the file '%.*ls'.
Explanation
An attempt was made to install (or update) SQL Server Native Client on a computer where SQL Server Native Client is already installed, and where the existing installation was from an MSI file that was not named sqlncli.msi.
User Action
To resolve this error, uninstall the existing version of SQL Server Native Client. To prevent this error, do not install SQL Server Native Client from an MSI file that is not named sqlncli.msi.
I am in the process of uninstalling SS 2008, because removing the native client requires me to do so. The MSI file in question is on the CD I would assume, and how does one not use it?
Don
June 8, 2010 at 2:23 pm
i'm a little confused by your reply. You said the services failed to install, however said the database engine installed correctly. I presume when you say 'Services' you mean 'Reporting Services', not the windows services that run the SQL functions.
The error you quoted relates to the native client, which allows connectivity from applications to the database. There are some cases where if it is installed before SQL is, you can get the message you speak of. I believe there are some other applications/windows components that can install the native client. I actually had this problem just the other week. Removing SQL, then removing the native client, resolved that issue.
If this current course of action does not get you up and running, perhaps post a screen shot of the first error screen you come across.
June 8, 2010 at 2:32 pm
Yes I was talking about Reporting, Integration and Analysis Services. Removed SS2008 and then the native client. Attempting another install now.
June 8, 2010 at 2:40 pm
The first error screen is the Service Accounts, this install is Developer Edition on a laptop, for learning purposes only. I am the sole admin.
The Integration Services is using > NT AUTHORITY\NetworkService as the Account Name with no password, should I be using that on all the other accounts as well?
June 8, 2010 at 2:59 pm
For the purposes of your exercise, I think that would be fine. It can be changed later if needed.
In real life situations, this is a pretty important step. Many people create individual local/domain accounts for SQL or part thereof to run under.
June 8, 2010 at 3:27 pm
Well that didn't work. Everything installed except the "Services", they all failed. This is the summary of the text file. I says to go to log files, which I will do.
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068643839
Exit facility code: 1203
Exit error code: 1
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2010-06-08 16:30:35
End time: 2010-06-08 17:06:27
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100608_162758\OWC11_Cpu32_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.0.1600.22
Machine Properties:
Machine name: DOND-PC
Machine processor count: 2
OS version: Windows Vista
OS service pack: Service Pack 2
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 0
Installation location: H:\x86\setup Installation edition: DEVELOPER
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP: <empty>
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: NT AUTHORITY\NetworkService
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: DonD-PC\Donald
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100608_162758\ConfigurationFile.ini
ENABLERANU: False
ERRORREPORTING: False
FEATURES: SQLENGINE,AS,RS,BIDS,IS,BOL,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
MEDIASOURCE: H: NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\NetworkService
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: DonD-PC\Donald
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100608_162758\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Analysis Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xEA235729
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100608_162758\OWC11_Cpu32_1.log
MSI error description:
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xEA235729
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100608_162758\OWC11_Cpu32_1.log
MSI error description:
Configuration status: Passed
Feature: Integration Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xEA235729
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100608_162758\OWC11_Cpu32_1.log
MSI error description:
Configuration status: Passed
Feature: Management Tools - Complete
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Business Intelligence Development Studio
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Books Online
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100608_162758\SystemConfigurationCheck_Report.htm
June 8, 2010 at 3:35 pm
The log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100608_162758\OWC11_Cpu32_1.log
is a very large file, however towards the bottom, I think it's saying the failure is due to Windows Office 2003 Web Components. See following:
MSI (s) (94:A4) [16:59:09:038]: Note: 1: 1729
MSI (s) (94:A4) [16:59:09:038]: Product: Microsoft Office 2003 Web Components -- Configuration failed.
MSI (s) (94:A4) [16:59:09:038]: Windows Installer reconfigured the product. Product Name: Microsoft Office 2003 Web Components. Product Version: 12.0.4518.1014. Product Language: 1033. Reconfiguration success or error status: 1602.
MSI (s) (94:A4) [16:59:09:038]: Deferring clean up of packages/files, if any exist
MSI (s) (94:A4) [16:59:09:038]: MainEngineThread is returning 1602
MSI (s) (94:9C) [16:59:09:038]: RESTART MANAGER: Session closed.
MSI (s) (94:9C) [16:59:09:038]: No System Restore sequence number for this installation.
=== Logging stopped: 6/8/2010 16:59:09 ===
MSI (s) (94:9C) [16:59:09:038]: User policy value 'DisableRollback' is 0
MSI (s) (94:9C) [16:59:09:038]: Machine policy value 'DisableRollback' is 0
MSI (s) (94:9C) [16:59:09:038]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (94:9C) [16:59:09:038]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (94:9C) [16:59:09:038]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (94:9C) [16:59:09:038]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (94:9C) [16:59:09:038]: Restoring environment variables
MSI (s) (94:9C) [16:59:09:038]: Destroying RemoteAPI object.
MSI (s) (94:AC) [16:59:09:038]: Custom Action Manager thread ending.
MSI (c) (20:18) [16:59:09:053]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (20:18) [16:59:09:053]: MainEngineThread is returning 1602
=== Verbose logging stopped: 6/8/2010 16:59:09 ===
Any idea on what it wants????
Thanks, Don
June 8, 2010 at 6:30 pm
I pasted the error message into Google. A person in Australia had the same problem, the fix is to delete MS Office 2003 Web components. After deleting that and restarting the computer, I installed the Services - Reporting, Integration and Analysis, and they installed successfully.
I apreciate everyone's help. Thank You.
Don
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply