November 22, 2013 at 7:57 pm
Hi
Very much a newbie, with little experience with SQL.
Had Visual Studio in here, and apparently also SQL 2005, 2008. Tried to install SQL 201RC22, to learn Transact SQL for a class.
Error messages after I spent two days searching for solutions, manually removing all other instances of SQL in the files, registry and Control Panel.
Tried MS "fixes", installing into another local drive (this is not for a network, just to learn), you name it. Two days now.
Latest error messages during and after "successful" install:
____________________
TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
------------------------------
The following error has occurred:
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.
------------------------------
TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
------------------------------
The following error has occurred:
Error call into RS WMI native function to retrieve database scripts. Error code: -2147220975
TRYING TO CONNECT:
Cannot connect to BOB2\SQLEXPRESS2012.
===================================
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (.Net SqlClient Data Provider)
------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
------------------------------
Error Number: -1
Severity: 20
State: 0
------------------------------
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
-------------------------------------------------------
Action required:
Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Feature failure reason:
An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Error details:
§ Error installing SQL Server Common Files
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.
Error code: 0x84BB0001
Visit http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xA60E3551%400xD3BEBD98%401211%401&EvtType=0xA60E3551%400xD3BEBD98%401211%401 to get help on troubleshooting.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068119551
Start time: 2013-11-22 21:16:39
End time: 2013-11-22 21:43:19
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Adv_SSMS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Conn: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for BC: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SSMS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for BIDS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: BOB2
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: F:\SQL 2012 RC2 setup files\x64\setup\
Installation edition: Express
Slipstream: True
SP Level 1
Product Update Status:
User selected not to include product updates.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131122_211208\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, RS, BIDS, CONN, BC, SDK, BOL, SSMS, ADV_SSMS, SNAC_SDK, LOCALDB
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SQL2012
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: f:\Program Files\Microsoft SQL Server\
INSTANCEID: SQL2012
INSTANCENAME: SQL2012
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SQL2012
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQL2012
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: bob2\rzuvich0760
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: false
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131122_211208\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Common Files
Component error code: 0x84BB0001
Error description: 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.
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Common Files
Component error code: 0x84BB0001
Error description: 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.
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Common Files
Component error code: 0x84BB0001
Error description: 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.
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Common Files
Component error code: 0x84BB0001
Error description: 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.
Feature: SQL Server Data Tools
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Common Files
Component error code: 0x84BB0001
Error description: 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.
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Common Files
Component error code: 0x84BB0001
Error description: 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.
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x80131500
Error description: Error call into RS WMI native function to retrieve database scripts. Error code: -2147220975
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x80131500
Error description: Error call into RS WMI native function to retrieve database scripts. Error code: -2147220975
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x80131500
Error description: Error call into RS WMI native function to retrieve database scripts. Error code: -2147220975
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: LocalDB
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131122_211208\SystemConfigurationCheck_Report.htm
TRYING TO CONNECT:
Cannot connect to BOB2\SQLEXPRESS2012.
===================================
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (.Net SqlClient Data Provider)
------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
------------------------------
Error Number: -1
Severity: 20
State: 0
HELLLLLLLLLLLLLLLPPPPPPPPPPPPPP!
Bob.
November 24, 2013 at 4:14 am
Too a newbie, but:
In my experience, there is very little to do, when theese installs first begins to go wrong.
It only gets worse and worse.
The SQL 2012 is better than 2008, but that is the one you have tried with.
Do you have any chance of starting from fresh?
i.e. Format C: and a fresh windows as a start?
Best regards
Edvard Korsbæk
November 24, 2013 at 5:26 am
I can, but was trying to avoid it sincerely. It just makes no sense to me that installing a program on a computer is so difficult and, if anything goes wrong, you have to blow away all of your other data and programs just to re-install it.
I have the ability to back it all up, but we are talking many days job in all, with files, programs, backup, re-installing Windows 7, reinstalling programs.
Because I wanted to put SQL in there and learn it? What other software does such a thing that is not called a VIRUS? And companies use this thing? DO they fire the IT guy when he says the server must be completely redone because an "instance" is in the way? Just makes no sense to me.
Regards,
Bob
November 24, 2013 at 7:20 am
I can, but was trying to avoid it sincerely. It just makes no sense to me that installing a program on a computer is so difficult and, if anything goes wrong, you have to blow away all of your other data and programs just to re-install it.
I have the ability to back it all up, but we are talking many days job in all, with files, programs, backup, re-installing Windows 7, reinstalling programs.
Because I wanted to put SQL in there and learn it? What other software does such a thing that is not called a VIRUS? And companies use this thing? DO they fire the IT guy when he says the server must be completely redone because an "instance" is in the way? Just makes no sense to me.
Regards,
Bob
Bob,
SQL Server is not just a program, or a application. It is a full Server Service. Since you already has two other versions, it would have been simple had you not tried to install the latest version over top, or in the same directory as one of the others. Most likely Express. You can have as many different versions as you like. But, you Must install each on into its own directory, and use a named instance. That is real catch, the named instance part. SQL Server will assign a different port number to each instance name.
There is no "Upgrade" or "update" to SQL Server. They are all their own stand alone version. You cannot attempt to upgrade one with the next version. It does not work that way. And from some of the error messages, you installed the latest over top of what looks like Express edition. You needed to either completely remove Express and use that instance name, or create a new instance name. There can be only one version with the instance name of "default"
And no, DBA's know better, and we do not get fired, because we do not make that kind of mistake. Unless you are a Junior, and then most likely a junior DBA would not be installing SQL Server on a server by themselves. At least not the first few times. Also, we setup a fully automated, "hands-off" install.
You already has a couple versions of SQL Server installed, you could have used that to learn T-SQL language. I would have recommended using SQL 2008 instead of SQL 2005, but you could have used it for what you want to do. You never need the absolute latest version to learn T-SQL.
As stated, the best thing that you can do to ensure that everything will work correctly, is to swipe the drives and start over. You will thank yourself in the long run. Also, if possible, use an actual server operating system, instead of a home user operating system. That is not required, but recommended. I personally have never used a home user operating system.
Plan what you want install, and do exactly that. I always install ALL services, it is easier to turn a service on or off, as opposed to stopping later and having to run the install again, for something that should have been installed the first time.
Andrew SQLDBA
November 24, 2013 at 9:00 am
Actually, I had the other two earlier versions, but different instances for them. When all else failed, I manually removed in the files and registry all of them (or so I thought) for hours doing searching and deleting, so that no more instances or services showed up. This was per instruction from the Microsoft site itself for this purpose.
Each previous version in Windows Explorer had a different directory and instance name. There was even a time from my memory when I could use any of them. I was not at that time trying so much to do SQL, but VB.Net, with SQL as the back end. Rarely did anything with SQL outside of VB, since I did not have to.
While I had earlier versions installed, they were not connecting or working, which is why I figured that I need to just install 2012 into a different directory.
I just want to learn Transact SQL, that is all. I was not planning on doing a complete HD backup, blowing away all of my work and reinstalling Windows, then all of my programs again, then re-installing SQL. Even a friend of mine who has worked with Access, SQL, TSql and VB as the front end for years did not ever encounter this error. He replied to me, "Never heard of that happening.".
I guess that is what I have to do then.
November 24, 2013 at 10:51 am
Robert
But you kept trying to install SQL Server over top of things that were not working correctly any way. I have never had an issue using a .NET front-end with a SQL back-end. They always work.
It is best that you correct all the issues, and a swipe of the drive(s) will be much faster than anything. You mentioned "Windows Explorer". What does that have to do with SQL Server install? If you have more than one version of that, that would tell you a lot right there. That OS and drive layout of files are so very messed up, I would not waste any more time. Just swipe it and start over. I rebuild all of my server about every 6 months. Keeps them running fast and lean. But I do install much on them. It still takes me only about 6 hours to perform a complete rebuild of the OS. I always have more than one drive in the boxes, and I never mix the OS with the Apps. Always place the apps on a separate drive or partition. I always place the databases, logs and Temp database on a separate drive, one for each.
By trying to remove things by hand, there is no telling what you have deleted that other services / apps / OS requires. You best thing is to swipe the drive(s) and begin again. Install only the apps and services that you absolutely need. No need to install 3 or 4 different versions of Microsoft Office, for example. Never install a trial version of any software. That causes nothing but problems and issues.
Andrew SQLDBA
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply