February 23, 2013 at 5:09 pm
Ok, so we are about 5 hours in to installing SQL 2012 dev edition. We get right on to the installation page and it starts to install
Install_sql_dq_common_Cpu64_Action. It appears to be loading, well the green bar refreshes but there is never any real movement.
This is on a brand new machine. We have had the reported issue of persisting files. we have 8 Gig of RAM so should be OK.
Any suggestions?
Thanks
February 24, 2013 at 1:46 am
As an update things appear to be getting a bit better
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068578302
Start time: 2013-02-24 08:30:20
End time: 2013-02-24 08:39:28
Requested action: Repair
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for DQ: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
Next step for AS: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: E5530
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
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
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services 1033 Enterprise Evaluation Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER SQL Server Replication 1033 Enterprise Evaluation Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Data Quality Services 1033 Enterprise Evaluation Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSAS11.MSSQLSERVER Analysis Services 1033 Enterprise Evaluation Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSRS11.MSSQLSERVER Reporting Services - Native 1033 Enterprise Evaluation Edition 11.0.2100.60 No
SQL Server 2012 Management Tools - Basic 1033 Enterprise Evaluation Edition 11.0.2100.60 No
SQL Server 2012 Management Tools - Complete 1033 Enterprise Evaluation Edition 11.0.2100.60 No
SQL Server 2012 Client Tools Connectivity 1033 Enterprise Evaluation Edition 11.0.2100.60 No
SQL Server 2012 Client Tools Backwards Compatibility 1033 Enterprise Evaluation Edition 11.0.2100.60 No
SQL Server 2012 Client Tools SDK 1033 Enterprise Evaluation Edition 11.0.2100.60 No
SQL Server 2012 Integration Services 1033 Enterprise Evaluation Edition 11.0.2100.60 No
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: D:\x64\setup Installation edition: Evaluation
User Input Settings:
ACTION: Repair
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASCONFIGDIR: Config
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130224_082320\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
ENU: true
FAILOVERCLUSTERGROUP: <empty>
FAILOVERCLUSTERNETWORKNAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
QUIET: false
QUIETSIMPLE: false
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: <empty>
UIMODE: Normal
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130224_082320\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
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, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84B40002
Error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
Feature: Data Quality Services
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, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84B40002
Error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
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, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84B40002
Error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
Feature: Master Data Services
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Reporting Services - Native
Status: Passed
Feature: Analysis 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, and then try the setup process again.
Component name: SQL Server Analysis Services
Component error code: 0x84B40002
Error description: The SQL Server feature 'Analysis_Server_Full' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20130224_082320\SystemConfigurationCheck_Report.htm
February 24, 2013 at 2:32 am
2013-02-24 09:23:31.46 Server Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Feb 10 2012 19:39:15
Copyright (c) Microsoft Corporation
Enterprise Evaluation Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2013-02-24 09:23:31.47 Server (c) Microsoft Corporation.
2013-02-24 09:23:31.47 Server All rights reserved.
2013-02-24 09:23:31.47 Server Server process ID is 16804.
2013-02-24 09:23:31.47 Server System Manufacturer: 'Dell Inc.', System Model: 'Latitude E5530 non-vPro'.
2013-02-24 09:23:31.47 Server Authentication mode is WINDOWS-ONLY.
2013-02-24 09:23:31.47 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2013-02-24 09:23:31.47 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2013-02-24 09:23:31.47 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2013-02-24 09:23:31.47 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2013-02-24 09:23:31.60 Server SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2013-02-24 09:23:31.60 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-02-24 09:23:31.60 Server Detected 8065 MB of RAM. This is an informational message; no user action is required.
2013-02-24 09:23:31.60 Server Using conventional memory in the memory manager.
2013-02-24 09:23:31.73 Server This instance of SQL Server last reported using a process ID of 18272 at 24/02/2013 09:23:30 (local) 24/02/2013 09:23:30 (UTC). This is an informational message only; no user action is required.
2013-02-24 09:23:31.73 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2013-02-24 09:23:31.74 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2013-02-24 09:23:31.77 Server Software Usage Metrics is disabled.
2013-02-24 09:23:31.77 spid3s Starting up database 'master'.
2013-02-24 09:23:31.80 spid3s 2 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2013-02-24 09:23:31.80 spid3s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2013-02-24 09:23:31.85 Server CLR version v4.0.30319 loaded.
2013-02-24 09:23:31.91 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2013-02-24 09:23:31.92 spid3s Resource governor reconfiguration succeeded.
2013-02-24 09:23:31.92 spid3s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2013-02-24 09:23:31.92 spid3s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2013-02-24 09:23:31.94 spid3s SQL Trace ID 1 was started by login "sa".
2013-02-24 09:23:31.95 spid3s Server name is 'E5530'. This is an informational message only. No user action is required.
2013-02-24 09:23:32.05 spid13s A self-generated certificate was successfully loaded for encryption.
2013-02-24 09:23:32.05 spid13s Error: 26023, Severity: 16, State: 1.
2013-02-24 09:23:32.05 spid13s Server TCP provider failed to listen on [ 'any' <ipv6> 1433]. Tcp port is already in use.
2013-02-24 09:23:32.05 spid13s Error: 17182, Severity: 16, State: 1.
2013-02-24 09:23:32.05 spid13s TDSSNIClient initialization failed with error 0x271d, status code 0xa. Reason: Unable to initialize the TCP/IP listener. An attempt was made to access a socket in a way forbidden by its access permissions.
2013-02-24 09:23:32.05 spid13s Error: 17182, Severity: 16, State: 1.
2013-02-24 09:23:32.05 spid13s TDSSNIClient initialization failed with error 0x271d, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. An attempt was made to access a socket in a way forbidden by its access permissions.
2013-02-24 09:23:32.05 spid13s Error: 17826, Severity: 18, State: 3.
2013-02-24 09:23:32.05 spid13s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2013-02-24 09:23:32.05 spid13s Error: 17120, Severity: 16, State: 1.
2013-02-24 09:23:32.05 spid13s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
2013-02-24 09:23:32.11 spid14s A new instance of the full-text filter daemon host process has been successfully started.
February 25, 2013 at 2:07 pm
Very interesting.
Did you install that on a corporate-specific OS instance/deployment? If so, and if you have an MSDN license, you could try to create a development machine/VM with absolutely standard (default) OS options, NOT on your domain (perhaps not on any network at all), if it's on the network apply all Windows patches, then make a backup of the VM, and then try installing SQL2012 Developer. If it fails, you've got a really interesting MS ticket. If it succeeds, restore the backup, then add your antivirus, take another backup, and try installing SQL2012 Developer again. If that works, restore the backup, join the machine to the domain, reboot a couple times, and try installing SQL2012 Developer again.
The idea is to keep getting closer and closer to your failing machine's configuration, so that you'll eventually have a backup where the install works, and a setup where it fails, and you'll know what you did between when it worked and when it failed.
February 25, 2013 at 5:16 pm
Not on a corporate machine. I have a clean windows 8 laptop. I have had several attempts at this and we still can't seem to move forward.
Think there is an issue with the top ip ports ? Also it seems to be the database components that are the real issue.
Thanks
E
Had considered hyper V but though - it can't be that difficult surely it will work first time.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply