Fresh install of Server 2012 R2 causes inaccessible boot device on first Reboot

Hello Everyone,
Doing a fresh install of Windows Server 2012 R2 on a SuperMicro X9DRT-HF+ motherboard based server. The server is using iSCSI boot, setup detects the iSCSI disk and copies its files, finishes the "Getting files ready for installation" "Installing
Updates" phase, reboots, takes a while and eventually gives a Blue screen with Inaccessible Boot Device error. I have tried some changing options in the BIOS, I've had Nimble (storage array) support on the phone and they confirmed the setup is correct
but for some reason after the first reboot Windows can no longer find its install files and gives a BSOD.
Additional Information:
Server: SuperMicro X9DRT-HF+ (no internal disk)
Storage: iSCSI disk provided from Nimble CS220 Array
Windows 2008 R2 Server installation will proceed without any problems.
I checked the \Windows\Panther\Setupact.log / CBS.log file and there doesn't seem to be anything indicating a problem.
I have googled a number of times to find solutions but most articles reference a similar problem after installing a particular KB (which shouldn't be the case here). Need some help :)

Hey Tim,
Thanks for your reply, since the start of this post I have also installed MDT to try a different approach to installing the OS. Using MDT I have injected the Intel I350 driver into the installation so it should be restarting with the driver loaded.
The odd thing is that when the server reboots the Windows startup screen loads for about 4 minutes before it gives the INACCESSIBLE_BOOT_DEVICE error. This would indicate to me that it sees the disk and tries to boot from it but then something goes wrong.
Other than the \Windows\Panther location is there another place I should be looking for log files during this part of the Windows install? I have reviewed all the locations listed under the TechNet library article "hh824819" (I can't post
a link to the article but a google search brings it up) but I can't seem to find a log of when the server crashes what it is doing at that point.

Similar Messages

Fresh install Windows Server 2012 R2 cannot RDP

I did a fresh install of WS 2012 R2. I enabled remote access as normal leaving network authentication on. I am unable to rdp to an administrator desktop. I then enabled pinging of the new server to make sure I can see the server. I am able to ping the server
from the WS I wish to RDP from and to ping the WS from the server.
I have installed a lot of servers and never had an issue with this.
Anything new in R2 which I'm missing?

Figured it out! Trying to RDP from outside domain, R2 has this rule disabled in Firewall.
Fixed

Password Complexity problems on fresh install of Server 2012 R2, This has not been answered before....

Hello all,
I have a problem that I can't find the solution to. I have found others with the same problem but the answers provided to them were not the exact situation I am in currently. Please read all the text and see if you can answer this...
I downloaded a copy of Windows Server 2012 R2. I am installing it on a stand alone PRE OWNED server which is a Dell R900 quad quad core server with 16gb ram and 500gb drive. The drive has been initialized and configured perfectly and windows server has been
loaded.
Upon the start of it, the screen appears that tells you to change your password for the admin account. Upon putting ANY (and I do mean ANY) password in there regardless of the complexity, the machine comes back with ..." The password you typed does
not meet the password complexity requirements set by the administrator for your network or group. Get the requirements from your administrator, and then type a new password."
I have tried new drives with no luck, I have tried everything that one can try on this (except the right thing of course). My guess is that the machine retained some crazy complex password file and stored it in an EEprom on board. If this was a factory fresh
machine, I would guess that this wouldn't be an issue as there was no file created yet that the machine is running it's scripted denial from. So... Does anyone have the exact method for eradicating this file or changing the domain controller or file that
controls this complexity problem WITHOUT HAVING TO LOG INTO THE MACHINE since as I said, you can't log into it. I even tried to go in through Linux to find the password in the SAM and since it's a new copy of windows, and there is no passwords in there, it
couldn't find the file since the admin acct wasn't set up yet (but that domain controller is working it's butt off and keeping me out I tell ya! lol)
Any help would be appreciated more than you know! ...Scott

Hello Phillip,
Thanks for the reply! Yes, the drive was put in the machine with no other drives (500gb SAS) and installed/initialized without incident. The DVD was put in the DVD drive and the OS was installed on the machine. As the machine starts up again after
install (reboots) the text comes up that says that you have to change the password on the administrator account due to this being the first install of the OS. I put in a password, and then put it in again, then get the statement about the password being entered
doesn't meet the complexity level set on the domain controller and to contact the admin of the network. I then looked up what that was referring to and used a series of passwords that should have worked as they matched the exact complexity that windows stated
in their tech knowledge base. Such as ... P@ssw0rd and another like Pass\/\/0rd!! as well as quite a few others with various names and symbols. Each time meeting or exceeding the 8 chars with upper and lower case with symbols
present. Each and every time that complexity statement in yellow comes up.
I tried changing and initializing 2 more disks and downloading another copy of windows server 2012 R2 and tried it all again. Still the exact same thing. I have never seen anything like this before. I have installed windows server 2003 and 2008 in the past
many times without errors like this but this one really has me beat as to what is wrong.
I read a tidbit on a way to go to DOS and take some files from the DVD and copy them to certain locations on the drive the OS is installed on. That is supposed to write over the files that provide the complexity issues but where ever I saw it, they didn't
go into detail as to what exactly to do. I know others have had the same problem in the past but every answer I can see either doesn't address the question or provides the wrong answer altogether.
That's why I am posting here in a last ditch effort to save this project since the same exact problem is happening when I tried to install windows server 2008 R2 as well. I thought I may be able to just go with 2008 and get that running without the issue
but when I wipe the drives completely, and reinstall onto the drive the 2008 version, the exact same thing comes up.
If you have a solution, I would love to hear it! Thanks again...Scott

Unable to install SQL Server 2012 Developer

I have a problem with installing SQL Server 2012 (no matter which edition I choose). Installation usually runs well, but near the end shows up an error:
TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
The following error has occurred:
Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%25400x4BDAF9BA%25401306%254026
BUTTONS:
OK
The help link points to not-existing article on MSDN page. After I click OK button, the installation reaches it's end and shows up another, which tells, that Database Engine Services, Reporting Services - Native, Data Quality Services, Full-Text and Semantic
Extractions for Search and SQL Server Replication failed to install.
After that I am able to start, for example SQL Management Studio, but cannot connect to database. Also services of SQL Server (Server, Server Agent, Full-text Filter, Reporting Services) are stopped and I am not able to start them manually (any try throws an
error: "The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details").
I tried complete reinstalling of SQL Server, cleaning registry entries, different editions of that software - none method helped. Also, I tried the .iso images of installation media on other computers - it worked well and installed without any errors. My OS
is Windows 8.1 x64.

Hello,
Please uninstall SQL server completely from add remove program.Make sure you uninstall it completely
Now right click on Setup.exe file which is there in SQL Server installable and select run as administrator to start installation.
On page where you are asked to provide startup account for SQL Server service select NT Authority\System or Local System account.
This issue is basically after installation SQL Server is not able to bring online database services using account which you selected .Local system account will allow it to come online
After installation change startup account to domain account with least privilege
Hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Unable to install SQL Server 2012 Standard: Error code 0x851A0019

Hi All,
I am trying to install sql server 2012 standard edition on windows server 2008R2 but at the end of the installation it is giving me the following error message:
"The following error has occurred:
Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes."
And in the log file I got the following error message:
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: 0x851A0019
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
(I have posted part of the log file)
Need your help to resolve this issue.
Thanks,
MKNayeem

Hi,
Thanks for your reply.
I have already followed that article. I have changed the user to local account user, but it did not work.
Like you said the sql server is installed, but it is not starting the services. Following is the error log file message:
2015-03-16 10:12:15.27 Server Microsoft SQL Server 2012 - 11.0.2100.60 (X64)
Feb 10 2012 19:39:15
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
2015-03-16 10:12:15.27 Server (c) Microsoft Corporation.
2015-03-16 10:12:15.27 Server All rights reserved.
2015-03-16 10:12:15.29 Server Server process ID is 5724.
2015-03-16 10:12:15.29 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2015-03-16 10:12:15.29 Server Authentication mode is MIXED.
2015-03-16 10:12:15.29 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\Log\ERRORLOG'.
2015-03-16 10:12:15.29 Server The service account is 'NT Service\MSSQL$BNG1SECISO'. This is an informational message; no user action is required.
2015-03-16 10:12:15.29 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\DATA\mastlog.ldf
2015-03-16 10:12:15.29 Server Command Line Startup Parameters:
-s "BNG1SECISO"
2015-03-16 10:12:15.57 Server SQL Server detected 2 sockets with 1 cores per socket and 1 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-03-16 10:12:15.57 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-03-16 10:12:15.57 Server Detected 16383 MB of RAM. This is an informational message; no user action is required.
2015-03-16 10:12:15.57 Server Using conventional memory in the memory manager.
2015-03-16 10:12:15.67 Server This instance of SQL Server last reported using a process ID of 2452 at 16-03-2015 07:03:13 (local) 16-03-2015 01:33:13 (UTC). This is an informational message only; no user action is required.
2015-03-16 10:12:15.67 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2015-03-16 10:12:15.69 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.
2015-03-16 10:12:15.69 Server Software Usage Metrics is disabled.
2015-03-16 10:12:15.70 spid6s Starting up database 'master'.
2015-03-16 10:12:15.78 Server CLR version v4.0.30319 loaded.
2015-03-16 10:12:15.82 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-03-16 10:12:17.36 spid6s Error: 824, Severity: 24, State: 2.
2015-03-16 10:12:17.36 spid6s SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:377; actual 261:2228225). It occurred during a read of page (1:377) in database ID 1 at offset 0x000000002f2000 in
file 'C:\Program Files\Microsoft SQL Server\MSSQL11.BNG1SECISO\MSSQL\DATA\master.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and
must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Thanks
MKNayeem

Unable to install SQL Server 2012 on my Surface 3 computerr w/Windows 8.1 as the OS

Another user,
Cheer08, has replied to a thread you have subscribed to in the
SQL Server Express Forum.
Here are the error messages:
Error 2
Error 1
Hello,
This error is related to Microsoft Visual C++ 2005. Could you try to download and install Microsoft Visual C++ 2005 with service pack 1 (SP1) included:
http://www.microsoft.com/en-us/download/details.aspx?id=5638 (x86 or 32-bit)
http://www.microsoft.com/en-us/download/details.aspx?id=18471
(x64 or 64-bit)
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Thread Title Unable to install SQL Server 2012 on my Surface 3 computerr w/Windows 8.1 as the OS.
Started by: FenixRising
Reply:
Fenix, this is SQL Server forum. Regarding the Visual C++ 2005 SP1 Redistributable setup issue, you need to post question in
visual studio forum to get better help.
After installing Visual C++ 2005 SP1 Redistributable successfully,are you able to install SQL Server? If not, share us SQL Server setup logs. This link
https://msdn.microsoft.com/en-us/library/ms143702(v=sql.110).aspx will help you View and Read SQL Server Setup Log Files
Im going to run it now. Get back to you.

Hi,
    I am unable to install SQL Server 2012. I have the install log, but I don't can't read them.
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2053898239
Start time:                    2015-02-08 23:03:01
End time:                      2015-02-08 23:07:31
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, and then try the setup process again.
Next step for SSMS:            Use the following information to resolve the error, and then try the setup process again.
Next step for RS:              Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
Next step for FullText:        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.
Machine Properties:
Machine name:                  RLC_WORK
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 Configured
SQL Server 2012
Client Tools Connectivity                1033
11.2.5058.0     No         Yes
SQL Server 2012
Client Tools Backwards Compatibility     1033
11.2.5058.0     No         Yes
SQL Server 2012
Client Tools SDK                         1033
11.2.5058.0     No         Yes
SQL Server 2012
SQL Server Data Tools                    1033                 Express Edition
11.2.5058.0     No         Yes
SQL Server 2012
LocalDB                                  1033
Express Edition      11.0.2100.60    No         Yes
Package properties:
Description:                   Microsoft SQL Server 2012
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
Installation location:         C:\76766b629842c4dc54646a47c04202\x64\setup\
Installation edition:          Express
Slipstream:                    True
SP Level                       2
Product Update Status:
Success: KB 2958429
Product Updates Selected for Installation:
Title:                         Service Pack 2
Knowledge Based Article:       KB 2958429
Version:                       11.2.5058.0
Architecture:                  x64
Language:                      1033
Update Source:                 Slipstream
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:
CTLRSTARTUPTYPE:               0
CTLRSVCACCOUNT:                <empty>
CTLRSVCPASSWORD:               <empty>
CTLRUSERS:                     <empty>
ENABLERANU:                    true
ENU:                           true
ERRORREPORTING:                true
FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, RS, SSMS, ADV_SSMS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SQLEXPRESS
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:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    SQLEXPRESS
INSTANCENAME:                  SQLEXPRESS
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$SQLEXPRESS
RSSVCPASSWORD:                 <empty>
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         <empty>
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
SQLSVCPASSWORD:                <empty>
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           RLC_WORK\Robert
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  true
TCPENABLED:                    0
UIMODE:                        AutoAdvance
UpdateEnabled:                 true
UpdateSource:                  Slipstream
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150208_230228\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, and then try the setup process again.
Component name:                Microsoft .NET Framework 3.5
Component error code:          0x85940001
Error description:             Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
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, and then try the setup process again.
Component name:                Microsoft .NET Framework 3.5
Component error code:          0x85940001
Error description:             Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
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, and then try the setup process again.
Component name:                Microsoft .NET Framework 3.5
Component error code:          0x85940001
Error description:             Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
Feature:                       Database Engine 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:                Microsoft .NET Framework 3.5
Component error code:          0x85940001
Error description:             Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
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, and then try the setup process again.
Component name:                Microsoft .NET Framework 3.5
Component error code:          0x85940001
Error description:             Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
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:                Microsoft .NET Framework 3.5
Component error code:          0x85940001
Error description:             Error while enabling Windows feature : NetFx3, Error Code : -2146498270 , Please try enabling Windows feature : NetFx3 from Windows management tools and then run
setup again. For more information on how to enable Windows features , see http://go.microsoft.com/fwlink/?linkid=227143
Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.5058.0&EvtType=0x681D636F%401428%401&EvtType=0x681D636F%401428%401
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150208_230228\SystemConfigurationCheck_Report.htm
Fenix

Unable to install SQL Server 2012 along with BIDS & VS 2012 on Windows 7

Unable to install SQL Server 2012 along with BIDS & VS 2012 on Windows 7 professional.
I get the below error
Could not find vsjitdebugger.exe
Blogs say anti-virus is stopping but I dont have one on the system.
Note: I had used SQL 2008 on the system previously and has a refresh i have deleted all the software to speed up the system.
Now i could not install both the software.
Can I get some help regarding this?

Hi Nandu,
As your description, you come across an error(vsjitdebugger.exe cannot be found). Please confirm if the error occurs during the installation of SQL Server 2012. If so, please help post SQL Server setup logs. By default, SQL Server setup log file locates
in C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log.
Base on my research, this error could be caused by that the previous uninstallation is improper and vsjitdebugger.exe file could be mistakenly deleted.
To troubleshoot the issue, you could start your computer into Safe Mode and fix your problem with one of the following methods. For more information, please refer to the article:
http://www.fixerrorkit.com/fix-error/fix-vsjitdebugger.exe-error.html.
1. You could execute the sfc /scannow command following steps below.
a. Press "Windows+R", type in cmd and then right click "Run as administrator"
b. Type in sfc /scannow (There's a space between sfc and /scannow) into the dialog and hit Enter key and click ok.
c. Wait until the System File Checker finishes the check.
2. You could use a Windows repair installation, also known as a Startup Repair to repair your Windows system files.
3. You could install the latest Windows updates to fix vsjitdebugger.exe error. Microsoft often releases new service packs and system patches to replace or update some DLL files of Windows system.
4. You could use third-party tool such as Automatic Error Fix Tool to fix your vsjitdebugger.exe error. However, Microsoft cannot make any representations regarding the quality, safety, or suitability of any third-party software or information found there.
In addition, if you are unable to install Visual Studio, I suggest you post your question in Visual Studio Setup and Installation forum at
https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=vssetup . It is appropriate and more experts will assist you.
Regards,
Michelle Li

I get one or the other error when i install SQL server 2012 SP1 in my Lab server

I get multiple errors when i install SQL server 2012 SP1 In my lab server.
Not sure why i keep getting different errors all the time when i install SQL server 2012 & 2012 SP1.
Below are error codes, screen shots and also a log of the error.
1. Eror code 0X84B40000
Also dint understand any thing from this article related to the above error
http://social.technet.microsoft.com/Forums/sqlserver/en-US/5b6cc928-0db8-4fe4-a5d3-21672225f0ca/i-get-error-code-0x84b40000-when-trying-to-install-sql-server-mgmt-studio-to-an-existing-sql?forum=sqlexpress
2. Eror code 0x851A001A
Can any one plz help as i always get one or the other error.
====================================
Screen shot:
Please note the below screen shot has given the error code 0x851A001A which is same in case of failure of all the other features which have failed during this installation. Hence i have uploaded only one screen shot.
2. Log file content.
=================================
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2014-05-04 21:15:35
End time: 2014-05-04 21:51:45
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
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: SERVER1
Machine processor count: 2
OS version: Windows Server 2008 R2
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
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER SQL Server Replication 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Data Quality Services 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSAS11.MSSQLSERVER Analysis Services 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSRS11.MSSQLSERVER Reporting Services - Native 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Management Tools - Basic
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Management Tools - Complete
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Client Tools Connectivity
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Client Tools Backwards Compatibility
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Client Tools SDK
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Integration Services
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Reporting Services - SharePoint
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: F:\x64\setup\
Installation edition: Enterprise
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: ms\sql
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
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\20140504_204851\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, RS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SCOM
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: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SCOM
INSTANCENAME: SCOM
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SCOM
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: ms\sql
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: MS\Gautam, MS\SCOM Users
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\ConfigurationFile.ini
Detailed results:
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 Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\SystemConfigurationCheck_Report.htm

Sorry about the error in the path, but you find the files that's the main thing.
Indeed it is a certificate problem:
2014-05-04 21:47:43.56 spid12s Error: 17190, Severity: 16, State: 1.
2014-05-04 21:47:43.56 spid12s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2014-05-04 21:47:43.56 spid12s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2014-05-04 21:47:43.57 spid12s Error: 17826, Severity: 18, State: 3.
2014-05-04 21:47:43.57 spid12s 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.
2014-05-04 21:47:43.57 spid12s Error: 17120, Severity: 16, State: 1.
2014-05-04 21:47:43.57 spid12s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
I've recall that I've tried to help people with this error before, but I'm sure they were able to sort it out.
Anyway, this blog post,
http://blogs.msdn.com/b/sqljourney/archive/2012/10/09/sql-2008-service-fails-to-come-online-with-a-valid-certificate-could-not-be-found-and-it-is-not-possible-to-create-a-self-signed-certificate.aspx
suggests the issue is a corrupted user profile, and you should try to use a different service account.
This blog also seems to have a simple solution, but I cannot vouch for that it will work:
http://www.beejblog.com/2012/02/sql-server-solved-unable-to-initialize.html
Erland Sommarskog, SQL Server MVP, [email protected]

Errro while installing sql server 2012 express edition on Windows 8 -64 version

Hi,
Im trying to install sql server 2012 express edition on windows 8 machine(64 bit),however im getting same error every time.
The following error has occurred:
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337
i've googled and checked all prerequisite which is already installed.so not finding the reason behind this error.
it would be great if any one can help on resolving this error.
Thanks in advance
Regards
Ritesh

Hi ,
Thanks for help. here is the log summary text
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2068051679
Start time:                    2014-02-05 12:30:44
End time:                      2014-02-05 12:36:21
Requested action:              Install
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 Replication:     Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name:                  IDEA-PC
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 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services
1033                 Developer Edition    10.50.1600.1    No
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         SQL Server Replication
1033                 Developer Edition    10.50.1600.1    No
SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text and Semantic Extractions for Search 1033
Developer Edition    10.50.1600.1    No
SQL Server 2008 R2
Management Tools - Basic                 1033                 Developer Edition
10.50.1600.1    No
SQL Server 2008 R2
Management Tools - Complete              1033                 Developer Edition    10.50.1600.1
No
SQL Server 2008 R2
Client Tools Connectivity                1033                 Developer Edition    10.50.1600.1
No
SQL Server 2008 R2
Client Tools Backwards Compatibility     1033                 Developer Edition    10.50.1600.1    No
SQL Server 2008 R2
Client Tools SDK                         1033
Developer Edition    10.50.1600.1    No
SQL Server 2008 R2
Integration Services                     1033                 Developer Edition
10.50.1600.1    No
Package properties:
Description:                   Microsoft SQL Server 2012 Service Pack 1
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
SPLevel:                       0
Installation location:         c:\b33170cf028067db5b8335d2\x64\setup\
Installation edition:          Express
Product Update Status:
None discovered.
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:
CTLRSTARTUPTYPE:               0
CTLRSVCACCOUNT:                <empty>
CTLRSVCPASSWORD:               <empty>
CTLRUSERS:                     <empty>
ENABLERANU:                    true
ENU:                           true
ERRORREPORTING:                false
FEATURES:                      SQLENGINE, REPLICATION, SNAC_SDK
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  <empty>
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:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    SQLFASHION
INSTANCENAME:                  SQLFASHION
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:                  <empty>
RSSVCPASSWORD:                 <empty>
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  Latin1_General_CI_AI
SQLSVCACCOUNT:                 NT Service\MSSQL$SQLFASHION
SQLSVCPASSWORD:                <empty>
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           idea-pc\lenovo
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  false
TCPENABLED:                    0
UIMODE:                        AutoAdvance
UpdateEnabled:                 true
UpdateSource:                  MU
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine 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 Common Files
Component error code:          2337
Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\sql_common_core_Cpu64_1.log
Error description:             The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337.
Error help link:
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 Common Files
Component error code:          2337
Component log file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140205_122837\sql_common_core_Cpu64_1.log
Error description:             The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337.
Error help link:
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\20140205_122837\SystemConfigurationCheck_Report.htm

Installing Windows Server 2012 in Order to Use SharePoint Server and Develop in VS2012

Hi.
I need to install SharePoint Server so that I can work with SP Designer and have full options for development using VS2012. Apparently, I also need to Install Windows Server 2012. I would like to install and configure WS2012 in a virtual environment
using the Hyper-V tools that come with Windows 8 Pro. I'm a newbie when it comes to WS2012, and want to make sure I don't end up reformatting my Windows 8 hard drive or causing a similar event that would put me in a rubber room.
I downloaded the WS2012 image file, but am unsure how to proceed. Can anyone give me some help as to how to get started?
Thanks.
Bugless

Hi,
If you have enabled the Hyper-V role on Windows 8 then you can create Windows Server 2012 VM's. As Server 2012 has the Hyper-V tools build in by default there is no need to install them.
So enable the Hyper-V role on Windows, Create a new VM in Hyper-V management console and connect the cd/dvd drive in the VM properties to the Windows Server 2012 setup ISO file. Start the VM and the Server 2012 setup. (during creating a VM you can also
connect the cd/dvd drive to an ISO file)
You might want to give to the Server 2012 VM 2 vCPU's and 2GB+ memory for performance. Also have a look the memory specs for VS2012 to see how much memory you should give to the VM.
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer
MCSE:Server Infrastructure, MCSE:Desktop Infrastructure, MCSA Server 2012, Citrix CCIA & CCEE, Cisco CCNA, VMware VCP 3/4/5 Blog: http://www.citrix-guru.com and http://www.rds-support.eu Twitter: @dnyvandam

Unable to Install Windows Server 2012 R2; system aborts and reboots after first blue Windows logo appears

System: Dell PowerEdge sc1420 with dual xeon and Adaptec 2420SA SATA RAID (supported by OS); 10 GB memory (2x4, rank 2, organization x4, in DIMM1 & DIMM2; 2x1, registered, organization x8, in DIMM3 & DIMM4)
This computer is currently running Windows Server 2008 R2 Enterprise which was installed with no problems.
Objective: clean install of Windows Server 2012 R2 Standard on an otherwise unused RAID array disk set.
All attempts to boot from DVD result in loading of files (grey progress bar on bottom of screen), brief dark screen, then black screen with a blue windows logo for about 2 seconds and then a flash of about 10 lines of error notifications on a black screen
for about 1/4 second (unreadable), and then a reboot of the computer.
Coreinfo.exe confirms that cpus DO support NX and PAE; do NOT support VMX (virtual machine enhancements).
Attempts to run memtest.exe from boot disk tool-menu startup result in an error message that the memtest.exe file is corrupt.
Running memtest.exe from Windows 2008 R2 install disk results in all memory tests passed!
Attempted booting with multiple DVD's (some +R, some -R, all verified) burned from .iso. These DVD's were used successfully to install Windows Server 2012 R2 on an HP Pavilion. Also changed DVD drives just to rule out DVD hardware.
Running CHKDSK from Windows 2012 R2 on HP Pavilion shows no problems; running CHKDSK from Windows 2008 R2 on the Dell system on the same disks shows some problems. Running checkdisk on the Windows 2008 R2 install disk from the Windows 2008 R2 installed
system shows no problems. All disks burned and verified on same system.
Also attempted to boot from USB thumbdrive with copy of DVD on it. Same results: system loads files then reboots at first Windows logo. So that would rule out disk quality issues per se??
Started to try an upgrade rather clean install to see if any errors were announced. None were announced as the system went through much of the process. I aborted somewhere along the way before committing to the upgrade because 1) the most likely
outcome was it would not boot after install (I don't really need the practice in restoring); and 2) even if it did reboot, having a system that can't be repaired by booting the install disk is pointless.
All disks and raid arrays are recognized and usable by RAID controller card and by Windows Server 2008 R2. Disks are within spec for use with Adaptec 2420SA (1TB @ 300).
Is VMX (aka VT-x) actaully required for ANY install even though Hyper-V is not intended to be used? If so, it is too bad that the Microsoft system requirements (
http://technet.microsoft.com/en-us/library/dn303418.aspx ) don't make that clear. And lack of VMX support really doesn't explain the memtest.exe "corruption" issue.
Or is it maybe something unique about the files on 2012 R2 disk (or disk image on USB) that are causing some problem with the chipset processing? But why?
My vote would be for the latter of the issues, but I have no clue why or if it is remediable. Suggestions?

So here is what I think is the final understanding of this problem:
First, one additional piece of important information: The computer successfully moves into and through the Windows Boot Loader phase and succeeding phase ONLY for Windows 8.1 32-bit, but NOT for Windows 8.1 64-bit nor for Windows
Server 2012 R2 (only 64-bit).
The Windows Boot Manager phase (which precedes the Windows Boot Loader phase) is either 32-bit or 64-bit (64 –bit for this case) and is loaded by the 16-bit stub program (Bootmgr) which starts in real mode.
Windows Boot Loader of course runs in either 32-bit or 64-bit (64 –bit for this case) according to the product being installed.
By inference, the essential problem is occurring in conjunction with the loading of a WIM file to start the Windows Boot Manager.
The boot manager starts ok and generally shows its essential screens (Windows Boot Manager; Advanced Boot Options) or proceeds to load files for transition into Windows startup in the succeeding Windows Boot Loader phase (that doesn’t “boot” but rather
loads the system). This is best confirmed by the announced corruption of the memtest.exe file when selecting Windows Memory Diagnostic from the Windows Boot Manager Screen.
If allowed to continue loading files to pass control to the Windows Boot Manager, the type of abort and resulting immediate restart that occurs is that which you would associate with unhandled cpu exceptions (invalid instruction, memory out of range,
wild interrupt, etc.) that most of us have not commonly seen for 20 years (since beginning to use well behave OS’s from Windows NT 3.1 and on).
So, the problem obviously is due to a failure to properly mount the WIM file and/or properly access it (probably the latter) when running in 64-bit protected mode.
This is independent of the hardware on which the install disk is actually mounted (DVD or USB-flash), so it is NOT a hardware problem
per se.
Since the WIM is mounted early in the process, Boot Manager may well have loaded it using BIOS routines to access the physical device on which it resides rather than loading 32-bit or 64-bit drivers of its own.
Hence, if the BIOS does not “mount” the WIM in a way that is later fully compatible with access from the 64-bit systems being loaded, it could cause apparent file corruption.
If it is only partially incompatible some functionality may appear quite usable (like loading files) until later detected.
This is vague on my part, because the exact nature of the incompatibility cannot be readily determined from the information available.
But the consequence is the same: the system cannot boot from the install disk, either for initial installation or repairs.
Incidental conclusion: The 64-bit boot manager code for Windows Server 2008 does not exhibit this faulty behavior, but the 64-bit code for Windows Server 2012 does.
So the problem is not inherent with loading 64-bit server OS’s.
Expectations: If the system were to be upgraded using the features of the install disk while running an installed OS, say Windows Server 2008 R2, it might well succeed and yield a fully functional system upgraded to Windows Server 2012
R2 (because the installed operating system is started from discrete files, not from a WIM file).
However, in order to perform a disaster recovery using Windows resources (such as image backups from Windows Server Backup), one would have to presumably boot from a Windows Server 2012 64-bit install disk or Windows Server USB recovery drive.
Of course we know that the Windows Server install disk will not boot and we can be fairly sure that the problem will migrate to any Windows Server USB recovery drive that is created.
My inspection of a Windows 7 System Repair CD shows that is based exclusively on boot.wim, not discrete files!
Of course a generated image for a WIM for Windows 2012 USB recovery drive
might not have the flaw that drives this behavior, but it probably would.
Problem conclusion: A BIOS upgrade would be required for compatibility with Windows Server 2014 clean installation
and any maintenance; and none is available from the OEM.
Problem not resolved, but understood for future reference.
Thanks to Tim whose comments helped me focus my thinking.

RDL Reports are not working after installing SQL Server 2012 Service Pack 2 in the SharePoint integration Mode

I am using Reporting Service Integration mode with SharePoint. SSRS is installed on separated machine of SharePoint stacks in Integration Mode. Everything was working properly and I could create/edit/modify RDL reports(parameters, Datasource, Subscription)
inside SharePoint and Document Libraries.
But after installing SQL Server 2012 Service Pack 2, on opening RDL reports inside SharePoint I receive this error message.
The permissions granted to user 'i:0#.f|membership|username' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user 'i:0#.f|membership|username' are insufficient for performing this operation
I should mention that SSRS is installed in the SharePoint integration Mode and there is no SSRS management console.

Hi Hedayat-Abedijoo,
According to your description, you are using Reporting Services in SharePoint Integrated mode, and everything worked fine before you install SQL Server 2012 Service Pack 2. After the package is installed, when you open RDL reports, the error occurred: The
permissions granted to user 'i:0#.f|membership|username' are insufficient for performing this operation.
According to my search, there may be two reasons for the problem:
This is caused when the application pool account that runs the SharePoint Web application you are on in IIS and the application pool account that SharePoint believes is running the site differ. This happens if the application pool account is changed directly
in IIS instead of through SharePoint (using the approved method).
This error can be caused when Kerberos authentication has been set up correctly and delegation in a double hop scenario will succeed, but Reporting Services integration has been set up for Trusted Account rather than Windows Authentication. This causes
SharePoint to continue to impersonate the logged-on user when contacting Reporting Services; when Reporting Services compares the application pool account to the user account making the request, they are not equal.
In this case, we can solve the problem by changing the application pool account in IIS back to the previous account and set AuthenticationTypes to RSWindowsNTLM only. For detail information, please refer to 8.3 “The permissions granted to user 'Domain\User'
are insufficient for performing this operation” in the document:http://msdn.microsoft.com/en-us/library/ee384252(SQL.100).aspx
If you have any questions, please feel free to let me know.
Thanks,
Wendy Fu

Error while installing SQL Server 2012 X64 SP2,

Error while installing SQL Server 2012 X64 SP2,
When I installed the SQL Server 2012 X64 SP1, I got the attached error.
What might be the issue here?
Thank you
Best
Jamal

Hello,
Are you trying to install SQL Server on a compressed or encrypted drive? SQL Server won’t install on a drive/folder with these attributes.
Are you trying to install SQL Server on a ReFS file system? It is not supported on SQL Server 2012.
Disable any security/antivirus software and download the media again. Mount the media (.ISO file) and try to install again.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Failed to install windows server 2012 in virtual machine hosted in window 8.1

I installed Hyper-V in windows 8.1, then when I tried to install windows server 2012 R2 or windows server 2008 R2 in virtual machine, I got the following error:
the following is my virtual machine setting:
is there anyone an help to resolve it? thank you very much.

Hi,
Good to hear that you have solved this issue. Thanks for sharing as it would be helpful to anyone who encounters similar issues.
Best regards,
Susie

Unable to install sql server 2012

I am trying to install sql server 2012. I need it to run a trial version of Xactimate. I get the following error during the installation process on the SQL Server Installation Center box : The feature you are trying to use is on a network resource that
is unavailable. Click ok to try again, or enter an alternate path to a folder containing the installation package 'sqlbrowser.msi' in the box below.
Use source: c:\9bc690235b2703df7a6704fa\1033_ENU_LP\x86\setup\

Hello,
Based on the following Xactware support document from two years ago (2012), Xactimate supports SQL Server 2005 and SQL Server 2008.
The document does not say Xactimate supports SQL Server 2012.
http://www.xactware.com/pdf/27/xactimate-27.5-network-install-guide.pdf
As mentioned on page #3 of the installation guide (above link), “If you do not already have SQL Server Express installed on your server,
you can use the version of SQL Server Express that is available on your Xactimate Version 27 DVD. Xactware recommends you use the Xactimate Setup—Network batch file. When you use this batch file, the Xactware instance is automatically created, the network
protocols are enabled, and the correct user name and password is set.”
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Fresh install of Server 2012 R2 causes inaccessible boot device on first Reboot

Similar Messages

Maybe you are looking for