Unable to boot Windows Server 2012 after adding features (AD, DNS, DHCP)

Hi,
I'm installing a VM server 2012 and it installs without any problems. Able to boot it and login, I change the name of the server and restart it. Still no problem.
Now when I want to add some features, Active Directory, DHCP and DNS, promoting to Domain Controller. Create a new forest and so on. When this is configured and installed the server wants to restart. It restarts but boots into a loop and ends up in System
Recovery/Troublshoot. I have tried repairing the boot with bcdedit in cmd-prompt but not able to fix it. Same Issue in VMware and hyper-v manager on different hosts. Im thinking that the image is at fault, but its strange that everything works at the beginning.
Am I missing something? The image I'm using is from MSDN, Server 2012 debug checked with updates. I'll try another image today, but why shouldnt that one work?

Hi Presaro,
I’m glad to hear that everything is OK. Thank you for posting here.
Best Regards,
Tina

Similar Messages

Unable to login Windows Server 2012 after making local policy changes

Experts, we have modified the local policy setting on the windows server 2012 and badly it was domain controller now none of the users are able to login to the server. After entering the user name and password it will launch till welcome screen then it errors
out saying user name or password incorrect. below are the steps which we followed
1. Policy setting is located in Computer Configuration\Security Settings\Local Policies\Security Options \Network security: Configure encryption types allowed for Kerberos values change from Not Configured to DES_CBC_MD5
2. changed user attribute msDS-SupprtdEncryptionTypes to 2 , this account we were used for kerberos authentication.
3. Logged off from the server and then server doesn't allow any user to login.
regards,
Jakk

Have you tried connecting to the server from a 2nd DC? Have you tried installing the RSAT tools on a domain member server and modify the offending policy ?
last choice would be restart the DC into safe mode.

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.

Unable to install Device CALs on Windows Server 2012 after OS Reinstall

Due to a hardware fault we had to reinstall Windows Server 2012. I have activated the Terminal Services licensing Server but I am unable to install Device CALs that we have purchased.
The error is as follows:
"Remote Desktop Services Licensing is unable to process your request. Make sure you provided correct information. If the problem persists, try other methods of activation. Error code is 800"
I tried contacting technical support over phone - they are also unable to resolve the issue.

Hi, thanks for response.
I contacted Clearing House over phone and provided them with all the details regarding authorization
number(s), license number(s) et al. However they also mentioned that there is some technical error from their "tool" and directed me to Technet Forum.
I shall try the Hotfix

Unable to activate windows server 2012 (0x80072F8F)

I seem to be unable to activate my Windows Server 2012 Essentials. All I recieve is the following message:
Windows couldn´t be activated
Go to Control Panel to learn about other ways to activate
Error code: 0x80072F8F
Error description: A security error occurred
This is a presisting problem and I can´t find any other way to activate in the control panel, what to do?

I'd double check that the date / time are correct.
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Windows server 2012 as primary DC and DNS server and windows server 2003 as secondary DC and DNS

Migration from windows server 2003 AD DC and DNS server to windows server 2012 R2,
Cannot I set up Windows server 2012 R2 as primary DC and DNS , windows server 2003 as secondary DC and DNS ? (for backup server when server 2012 fail, user can continue to login and access internet services)

You can mix both as long as your Forest and Domain Functional level are Windows Server 2003. However, I would like to bring your attention to this blog about known problems when mixing DCs with Windows Server 2003 and 2012 R2 OS:
http://blogs.technet.com/b/askds/archive/2014/07/23/it-turns-out-that-weird-things-can-happen-when-you-mix-windows-server-2003-and-windows-server-2012-r2-domain-controllers.aspx
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Unable to Install Windows Server 2012 on Windows Server 2008 R2 SP1 Hyper-V

My attempts to install are failing with a message "Windows cannot install required files. The file may be corrupt or missing....Error code: 0x800705070".
I am posting this on the Wondows 2012 Server forum but I have had exactly the same problem as described below with Windows 2008 R2 SP1.
As the title says this is on a Windows Server 2008 R2 SP1 host with all current updates. I have downloaded the ISO file from a Technet subscription file twice, once by direct download and once by the Akamai downloader. The virtual disk is connected with
the default IDE driver. I mounted both installation images as ISOs, located on a file system on the host server. I have tried installs by deleting the VM and recreating both the VM and a new virtual disk, re-using a previously created virtual disk, and
deleting the partitions in a previously created virtual disk, and executing the format command, and then attempting the install.
I have exactly the same problem trying to create a Windows Server 2008 R2 SP1 VM on the same host OS. With those attempts, I downloaded the Technet subscription iso 4 or 5 times, and burned one to a DVD which I attached to the created VM. Same
error message.
The virtual machines and virtual disks I created and used were all located on an RAID5 array, on a builtin Intel RAID controller using Intel Rapid Storage Technology software version 11.2.0.1066. The host Windows Server 2008 R2 SP1 uses this file system
but the OS is installed on a dedicated drive (C).
I had previously created a guest VM with Windows Server 2008 R2 (several months worth of updates ago) without drama.
I have spent hours reading forums and blog articles on this. A common response is to download the iso another time, and/or burn it to a DVD instead of mounting an iso image. Although I didn't do the later yet with 2012 Server, but I have done these
other steps attempting to install Windows 2008 Server SP1. The install process takes a while (not to mention doing multiple downloads). Given this seems to be a common recommended remedy, and indeed based on posts does seem to eliminate the problem is some
cases, why doesn't somebody change the Microsoft installer program so it does a thorough integrity check at the beginning of the install process?

Jeff,
After the exercise of Windows 2012 Server successfully installing (as I described above) I also successfully installed Windows 2008 R2 on Hyper-V. From my standpoint, I have eliminated the problem (which isn't the same as correcting the problem).
The answer to your specific question regarding Hyper-V support is that the motherboard I am using, an Asus P5Q, is not supported by Windows 2008 R2 because it doesn't use ECC memory, and the vendor doesn't say it supports Windows 2008. But I am sure you
know the motherboard vendors often don't test older motherboards with newer software versions. It appears that in specifying ECC memory Microsoft is trying to protect users of Windows Server from hurting themselves, not saying the software won't run.
Having said that, my suspicion in the beginning was, and still is, that it was some variable(s) left in an unknown state in the Hyper-V environment, which was why after trying to install Windows 2008 R2 several times I tried Windows 2012 which resulted in
the same error, and then encountered the same error trying to install Windows 7 on the same Hyper-V installation. The specific Hyper-V Windows 2008 R2 server had run without any operating problems for months before I started having trouble, and although it
had been quite a while since I had created VMs, that process used to work. The hardware didn't change. What changed was applying updates through Microsoft Update, and a few access control rights I changed, and at least I think, I set back to their original
value.
So in short, no, my hardware isn't supported by Windows 2008 Server. Two, your assertion that you are running the same software configuration that I am is very unlikely to be true. There are an extremely large number of things which are different between
your test system and mine, such as which Windows 2008 components are installed, what updates were installed and in what order they were installed, and what other third party software each of us is running, and between AD, and all the features, a large number
of potential differences in ACLs, options, etc. and I don't for a minute think this particular problem was caused by the underlying hardware.
I do appreciate your taking the time to try to help me, and I hope there is one thing you and I could agree on. Microsoft could pretty easily make it much easier to isolate problems. In this day and age reporting hex error codes (as opposed to doing the
table lookup in the error handling proc), and not providing more diagnostic information seems to me to be almost quaint. And in this case Microsoft can dismiss my problems on the grounds it was all on unsupported hardware. Unfortunately, I think they
are missing an opportunity to make their software better, because in my opinion what I encountered there are a set of conditions which will cause installations to fail that aren't going to get corrected.

Poweredge R730XD - unable to install Windows Server 2012 standard via DVD - limit progress via USB

Hi all,
hoping someone has encountered and sorted this problem. I've had troubles installing W2012 on our newest batch of server - 4x R730XDs. Either by deployment or booting directly by DVD I encounter the following message:
"windows failed to start. A recent hardware or software change might be the cause"
So I wrote the iso for Windows to USB and booted off that which yielded this message:
"We couldn’t create a new partition or locate an existing one. For more information, see the Setup log files."
A colleague recognised the message and directed me these instructions:
Start DISKPART.
TypeLIST DISK and identify your SSD disk number (from 0 to n disks).
Type SELECT DISK whatever disk number you have.
Type CLEAN.
Type CREATE PARTITION PRIMARY.
Type ACTIVE.
Type FORMAT FS=NTFS QUICK.
Type ASSIGN.
Type EXIT twice (one to get out of DiskPart, the other to exit the command line tool).
It didn't work - the next and final message I have is:
"An Operating System wasn't found. Try disconnecting any drives that don't contain an operating system"
As a last resort measure I pulled those disks out but no change to outcome.
I've encountered these issues with 3 out 4 of the servers (I haven't bothered to install the 4th and last).
To summarise the spec of the servers, R730XD - front drives fully populated with 24x 600GB SAS (currently not setup in an array) with additional 2x 300GB in a flex bay at the rear set to RAID1 for OS.
Any suggestions or experiences appreciated.
Kind regards,
KCC

Hi all,
an update of sorts - we were able to progress futher by setting up a the RAID array for the boot drive inside of the Lifecycle controller (that aspect of LC I have avoided using for a few years due to lack of flexibility in creating multiple arrays). Windows then installed as normal via deployment on 2 of 3 servers. the third still exhibits the same issue. We thought to perform a factory reset, if there such a thing, but am struggling to find such an option in the LC.

Unable to add File Server Resource Manager Tools on Windows Server 2012 - Errors on restart and roll back install

Unable to install Windows Server 2012 Feature - [Tools] File Server Resource Manager Tools.
Installs, however when I restart the server error messages appears saying feature unable to install, windows reverting changes.
In the Setup event logs have the following information message "Update FSRM-Infrastructure of package FSRM-All failed to be turned on. Status: 0x800f0922"
Does anyone have any idea's on why this Feature can not be installed ??
Scott

Hi Shaun
Tried both of your suggestions, however neither strategy worked.
Strategy 1
Tried installing via powershell - "install-windowsfeature -name fs-resource-manager -includemanagementtools"
Feature un-installed itself during the restart.
Attempted to use the command "DISM /online /remove-feature /featurename:FSRM-Infrastructure-Services". However
this did work because one the Service was'nt installed or two because there was no command option for "/remove-feature"
PACKAGE SERVICING COMMANDS:
/Add-Package - Adds packages to the image.
/Remove-Package - Removes packages from the image.
/Enable-Feature - Enables a specific feature in the image.
/Disable-Feature - Disables a specific feature in the image.
/Get-Packages - Displays information about all packages in the image.
/Get-PackageInfo - Displays information about a specific package.
/Get-Features - Displays information about all features in a package.
/Get-FeatureInfo - Displays information about a specific feature.
/Cleanup-Image - Performs cleanup and recovery operations on the image.
Strategy 2
Tried installing via powershell, using the following command DISM
/online /enable-feature /featurename:FSRM-Infrastructure-Services, however got the same result, the install backed out during the restart.
All up back to where I started?

Problems PXE booting Gen 2 Virtual Machines after Upgrading to Windows Server 2012 R2

My Current Setup:
I have two virtual machines set up with Hyper V on my Windows Server 2012 Server.
VM1: Configured to boot from an ISO file and runs Clonezilla server.
VM2: Configured to PXE boot using a legacy network adapter, and with a passthrough 250Gb hard disk.
These two VMs are connected to an external Virtual Switch, which allows physical machines to PXE boot to the Clonezilla server.
For the past few months I have been using this setup for two purposes:
1. To clone physical machines to the Clonezilla virtual server (as a backup).
2. To restore those image to the second VM if I find that need to get access to the files on the original image..
This has worked perfectly, except for the fact that the speed of the legacy network adapter on the second VM (which is required to PXE boot) is very slow. But I know this is because of the limitations in how the legacy adapter works...
Now my problem:
I found out that Gen 2 VMs allow you to PXE boot without having use a legacy network adapter, allowing me to image back to the VM faster. So I upgraded the Server to Server 2012 R2 . I then created the same two virtual machines on the R2 server. I can still
PXE boot the Gen 1 VM to the Clonezilla Server but I cannot get the Gen 2 VMs to PXE boot properly. They get an IP address from the Clonezilla Server but then just stop with the following screen. (note: I have disabled the Secure Boot).
Are Gen 2 VMs unable to pull down images from anything other than a WDS Server?

Hi J,
>>Unfortunately WDS is not a solution for us as it is dependent on the PC being part of a domain
If you would like to make the client not join to the domain, please check the box before “Do not join the client to a domain after an installation.” In addition, make sure not to set the client to the domain in the unattend file and do not prestage
the computer in AD. "
It is quoted from following thread :
https://social.technet.microsoft.com/Forums/windowsserver/en-US/1026c3a9-0a10-4a58-a48f-5391659a96c8/wds-set-unattend-file-for-workgroup?forum=winserversetup
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

New Windows Server 2012 install won't boot after installing Hyper-V role.

I have just installed Windows Server 2012 onto a Dell PowerEdge R310. Everything worked okay until I installed the Hyper-V role. After that, when it tries to boot, I get "Your PC ran into a problem and needs to restart. We're just collecting
some error info, and then we'll restart for you. (0% complete)" for a split second, then the system reboots into Automatic Repair mode.
In Automatic Repair mode, my options are Refresh your system (which tells me the drive that Windows is on is locked), Reset your system (which tells me there is no partition), and Automatically Fix your PC (which tells me it can't fix it).
I have updated to the latest version of the BIOS (1.11.0, which Dell states adds Windows Server 2012 support).
I'm at a loss.. I've tried everything I can think of. Has anyone run into this issue and figured out a solution? The only references I can find to this issue talk about Gigabyte motherboards with USB 3.0, but this server pre-dates USB 3.0 by
quite a bit.

Hi,
Not only the BIOS but the iDRAC and storage part also need to ne up date check, have a look at the following list to see what you need for Server 2012:
http://en.community.dell.com/techcenter/os-applications/w/wiki/3868.dell-bios-support-for-windows-server-2012.aspx
If any info was collected during the error then have a look in the event viewer or look for a kernel/memory dump file so you can try to find the issue, in many cases a driver, anti-virus sofware or 3rd part service can cause these kind of issues.
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

My 10.9.0.1 internal mac was ruined after the installation of Windows Server 2012 on boot camp

Hi Everyone. I've been trying to install Windows Server 2012 on my boot camp. Well, soon after the 2012 was installed, my mac os 10.9.0.1 was ruined. When I pressed on the option key while the imac was booting, I can see the icon of "10.9.0.1 recovery". But after I chose it, the apple tried very hard to boot it up with a progress bar below the apple icon. The computer shut down itself after the progress bar reached the end. I've tried boot it up with the installation CD and tried to repair the Macintosh HD in Disk Uitilites but no use. It was said the hard drive cannot be repaired and better be reformat. Currently I can only boot up my mac from my SuperDuper external clone drive. Anyone could give me wise advices to fix this problem please?

The "wise advices" I can offer are:
Read the Boot Camp documentation before trying to reinstall Windows Server. Windows Server is not supported by Boot Camp
Erase and reformat your hard drive. Reinstall OSx then restore your data from your backup.
Use a virtual machine like Parallels, Fusion, or VirtualBox to install Windows Server

Windows could not update the computer's boot configuration Server 2012

I'm trying to install Windows Server 2012 on another partition (V:) that I create directly from Disk Management. After I create it, I do a simple format of the partition.
Next, I try to Install Windows Server 2012, directly on the recent partition, after the setup is completed, Windows Server 2012 boots to the Getting the devices
ready section, but stops and throws me this error.
Windows could not update the computer's boot configuration
After that the computer, restarts and it goes on and on unable to create a multi-boot environment. What's killing me is that I have done this on the past like 10 times and never run to this problem.
I'm running Windows 7 Home Premium on an ASUS K45 64 bit.

Hi,
You can try adding a new boot entry by using bcdedit tool:
Adding Boot Entries
http://msdn.microsoft.com/en-in/library/windows/hardware/ff541231(v=vs.85).aspx
Or you can build a usb-bootable deivce to install the image:
Walkthrough: Create a Bootable Windows PE RAM Disk on a USB Flash Disk
http://technet.microsoft.com/en-us/library/dd744530(v=ws.10).aspx
Hope this helps.

Unable to uninstall sql server 2012 from Windows 7(ultimate) 64-bit SP1 version.

I am trying to install sql sever 2012 on my m/c but it's giving me error after partial installation.
Now I have successfully installed Sql Server 2008 R2 on my machine but when I am trying to uninstall 2012 sql server from my machine its giving an error regarding unsupported OS. However as mentioned earlier I have Windows 2007 Ultimate SP1 (64-bit) installed
on my machine which is included in valid platform for sql server 2012. Also I installed visual studio 2013 on my machine but it existed with error SqlServer\LocalDB not installed.

Hi pritamk,
According to your error message, as other post, you can uninstall SQL Server from command line, inaddition, another workaround is that change the compatibility mode of setup.exe to Vista SP2, then run “Remove” option from the control panel. You can refer
to the following steps.
Browse to your SQL setup bootstrap folder, For SQL Server 2012, this is the path "C:\Program Files \Microsoft SQL Server\110\Setup Bootstrap\SQLServer2012\".
Go to Setup.exe file and right click on Setup.exe. Then go to properties and click on "Compatibility" tab. Under "Compatibility mode", click on Run this program in compatibility mode for "Windows Vista (Service Pack 2)". Then Click on "Apply" then "OK".
After that go to control panel -> Programs and Features -> and remove SQL Server 2012
There is similar issue about uninstalling SQL Server 2012 RC0 from control panel. You can review the following post.
https://connect.microsoft.com/SQLServer/feedback/details/707706/unable-to-uninstall-sql-server-2012-rc0-from-control-panel
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

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 boot Windows Server 2012 after adding features (AD, DNS, DHCP)

Similar Messages

Maybe you are looking for