Upgrade Windows 2008 R2 Standard to 2008 R2 Enterprise fails

Hi,
I am trying to perform an in place upgrade from Windows Server 2008 R2 Standard to Enterprise. I want to setup some things with failover clustering. The install goes all the way to the last step where it is transferring files and then it hangs. This server
is in my home and I don't have a plethora of servers to play with so I need to upgrade. This server is an HP ProLiant ML330 G6. My other server is a DL385G2 running 2008 R2 Enterprise. They are different because I was scouring eBay and pounced when a deal
came up. :-)
This server is a DC and it is running:
DHCP
DNS
Exchange 2010
MS Forefront Security
Print Server
DFS Namespace
DFSR (I have a second server that it replicates with)
All HP services (But I disable them for the upgrade)
I suspect that it is failing on a print driver but I am not sure. I disabled all non-MS services from boot. I also added the system environment variable with the iphlp dll. (can't recall it right at this moment)
The way I have been doing this is to power off the server, break the RAID 1 O/S mirror by removing 1 of the drives, power up and run the upgrade. If it fails, I power off, insert the drive I removed and pop out the "upgraded" drive. Boot up, pop
in the failed upgrade drive and let it rebuild.
Any thoughts? The last time it failed I let it back out the upgrade and I copied off a bunch of the setup log files before I restored the previous mirrored drive.
I am also contemplating upgrading this server to 2012 R2. Would using my RAID 1 method above work? I don't know if the upgrade will change something with the server's computer account therefore not allowing me to revert to 2008 R2.
Lastly, I know that I shouldn't have all of these services on one server, but this is in my home and not a work environment. It runs fairly flawlessly.

Hi,
In addition to Dave Patrick, what is the error message when you upgrade failed?
Meanwhile, please check this article:
http://blogs.technet.com/b/server_core/archive/2009/10/14/upgrading-windows-server-2008-r2-without-media.aspx
It seems like the server can't be a DC at the time of upgrade. If you demote a DC using dcpromo, you can upgrade, then re-promote it.
Regards.
If you have any feedback on our support, please click
here
Vivian Wang

Similar Messages

I WANT TO UPGRADE WINDOWS SERVER 2008R2 STANDARD EDDITION SP1 TO ENTERPRISE SP1

I HAVE INSTALLED WINDOWS SERVER 2008 SERVICE PACK1 TO ENTERPRISE SERVICE PACK1
C:\Users\Administrator>DISM /online /Get-CurrentEdition
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7600.16385
Current edition is:
Current Edition : ServerStandard
The operation completed successfully.
C:\Users\Administrator>DISM /online /Get-TargetEditions
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7600.16385
Editions that can be upgraded to:
Target Edition : ServerDataCenter
Target Edition : ServerEnterprise
The operation completed successfully.
C:\Users\Administrator>DISM /online /Set-Edition:ServerEnterprise /ProductKey:XXXX-XXXX-XXXX-XXXX-XXXX
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image Version: 6.1.7600.16385
Error: 50
Setting an Edition is not supported with online images.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

“Setting an Edition is not supported with online images” More than likley the reason you are getting this error is because the server you are trying to inplace upgrade has the AD DS Role installed and is acting as a
domain controller. The only way to upgrade this one is to move the FSMO Roles to another server, then DCpromo the server, and make it a member server and then run the command, and then you can go ahead and make the server a Domain Controller once the edition
of Windows has been changed.
http://rickrbyrne.wordpress.com/2011/06/16/in-place-upgrade-from-windows-server-2008-r2-standard-to-enterprise/
UPDATE: One important note, as I'm reminded by Xaegr in the comments, is that
the server can't be a DC at the time of upgrade. If you demote a DC using dcpromo, you can upgrade, then re-promote it (you may need to migrate FSMO roles, etc, in order to succesfully demote.)
http://blogs.technet.com/b/server_core/archive/2009/10/14/upgrading-windows-server-2008-r2-without-media.aspx<o:p></o:p>
http://mariusene.wordpress.com/

Upgrade Windows 2008 R2 sp1 on an Exchange 2010 SP3 server

I have looked high and low for an answer to this question:
1. I have Windows 2008 R2 running Exchange 2010 SP3
2. Can I upgrade Windows 2008 R2 to SP1 with Exchange 2010 SP3 onboard?
3. Are there pre-requisites for doing this?
4. If so, where can I get the documentation?
I have spent hours looking through Google and Technet. Lots of information about compatibility of 2008 R2 and Exchange SP1 and SP2.
Your wisdom and experience would be appreciated. Thank you!!
Charlie

Hi,
"Can I upgrade Windows 2008 R2 to SP1 with Exchange 2010 SP3 onboard?"
Yes, you can.
"Are there pre-requisites for doing this?"
There is no pre-requisites, however, as what Idan Vexler mentioned above, downtime is required.
"If so, where can I get the documentation?"
Here are two related threads for your reference.
http://social.technet.microsoft.com/Forums/en-US/1093a91d-aed8-4c91-b538-ca82f5860523/upgrading-windows-2008-r2-enterprise-to-sp1-on-exchange-2010?forum=exchange2010
http://social.technet.microsoft.com/Forums/exchange/en-US/0a7f29a2-04a5-485f-9b0c-061f89b311a5/installing-windows-2008r2-sp1-on-exchange-server-2010?forum=exchange2010
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

In place upgrade Windows 2008 and SQL 2008

Hi all,
We are planning to upgrade to Windows 2012 and SQL 2012 , can we take this in-place upgrade path in the following order ?
Setup 1 Host with 2 VM's running Windows 2008 R2 on Host and Windows 2008 R2/sqL 2008 on VM's.
1. Host1(running 2 VM's) - In-place upgrade windows 2008 R2 to windows 2012 R2
2. VM1 on host1 - In place upgrade windows 2008 R2 to Windows 2012 R2
3. VM2 on host1 - In place upgrade windows 2008 R2 to Windows 2012 R2 (AD Server)
4. SQL running VM1 - In place upgrade SQL 2008 with DB/reporting services to SQL 2012 DB/reporting services
All Servers ( including Host and VM's) are stand alone in a workgroup setup.( except one VM a stand alone AD server by itself).
Thanks for your help.

Hi,
If you want migrate from windows 2008r2 to windows 2012r2, you must install windows server 2008r2 sp1.
http://technet.microsoft.com/en-us/library/dn303416.aspx
For the host 1 upgrade, please refer to the following:
http://blog.powerbiz.net.au/server-2012/in-place-upgrade-from-windows-server-2008-r2-to-windows-server-2012/
For the SQL in-place upgrade, i think you may need to ask in SQL forums:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlservermigration
Hope this helps.
Regards.
Vivian Wang

Windows 2008 Server Enterprise R2 x64 and Perc 4/dc SCSI driver issue

Hello all, this is the first time posting so please forgive me if this has been posted here before. I did try to search this issue but zero returns.
OK, I have a Dell PowerEdge 2900. I have just put a fresh install of MS Windows 2008 ENT. Server x64. I cannot seem to find a driver for the PERC 4/dc SCSI controller I have installed. I have been told the 2003 x64 driver would work so I attempted to install that driver but was unsuccessful. Then I was told by Dell that the driver should be native to the OS. Is the driver native to 2008 Server (or, supposed to be)? Does anyone have an answer as to where I might retrieve am driver of the controller if not? Anyway, thanks in advance

Hello,
I don't have a PowerEdge 2900, but I do have a PowerEdge 2850. I'm also just a regular bloke like yourself that just happened upon your post and after I figured this driver debacle out I registered to hopefully help.
The good thing is my PERC card is the same in the PE2850 as it is in your PE2900, as I'm utilizing a PERC 4/DC. I've also managed to run into the same issue you ran into(?) trying to load Windows 2008 Server Enterprise R2 (support for 32bit processors have been removed in R2... so no more x86 versions... my poor PE2650s never stood a chance with this OS).
I can tell you officially from my experience/research Windows Server Enterprise R2 does not have support built into it for the PERC 4/DC card.
However, I was able to download the Windows 2003 x64 driver from support.dell.com and make it work after much trial and error with newer releases of the PERC 4/DC driver that were not accepted by 2k8R2.
Here's the link: http://support.dell.com/support/downloads/download.aspx?c=us&cs=RC956904&l=en&s=hied&releaseid=R100373&SystemID=PWE_PNT_P3C_2850&servicetag=FBCLP61&os=WX64&osl=en&deviceid=6396&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=3&libid=35&fileid=129549
File name (incase Dell moves it on you guys) is "perc-w2k3-6.46.3.64-A01.exe", date released 6/9/2005, build version 6.46.3.64, and the Dell revision number is A01.
Even though it states the driver is for the LSI Logic PERC 4e/Si it's sort of a mega pack including many other drivers such as the PERC 4/DC. This was much relief because I was thinking I would need to stick with Windows 2008 until I found this driver for Windows 2008 R2. :)
What I did was:
1) Downloaded the driver and extracted it to a USB drive.
2) Booted-up via the Win2k8R2 CD and when it got to the screen where it asked to install to a partition and didn't show me a partition to install Win2k8R2 to I selected the option to load a driver.
3) From the load driver option I just browsed to the directory where I extracted the files and selected that directory. If the "hide devices that are not compatible" option is selected (normally on by default) it will show you the proper driver.
4) Select the PERC 4/DC driver and then setup your partitions the way you would like them!
From there you should be able to boot into the OS... and really have some fun.
Now you have the power... I guess the choice is yours to R2 or not to R2... that is the real question. :)
Enjoy!
Dave
Thanks and this worked for a Power edge 1800, PERC 4/DC as well. Kukan

Issue in Upgrading Windows 2008 R2 Standard server to Windows 2012 Standard Srever

Hi
We have a Windows Server 2008 R2 stadard running... (came with the server).
To use 64GB, we have just purchased a licence key (retail) and downloaded ISO (Evaluation version) to upgrade.
Then I got this error message saying that
"Windows Server 2008 R2 Standard cannot be upgraded to Windows Server 2012 Standard Evaluation (Server with a GUI). You can choose to install a new copy of Windows Server 2012 Standard Evaluation (Server with a GUI) instead, but this is different from
an upgrade, and does not keep your files, settings, and programs."
Well, fresh installation is not an option for me. no way..
I read somewhere that it is because I am trying to upgrade from licenced 2008 R2 standard to evaluation 2012 standard. Then I saw a screenshot where you supply a licence key after selecting an edition to choose..
I don't get that screen sinceit is the evaluation version.
Well, I am supposed to upgrade the system before the end of the new year... now I am in a panic.. - - ;;
Can anyone help me with this please???

Hi,
Thank you for posting in Windows Server Forum.
Agree with words of “Dave & Tim” and based on my research, we need to perform a clean installation of Windows Server 2012 Evaluation Versions instead upgrading.
However, if we have licensed Windows Server 2012, we can upgrade to Windows Server 2012 by referring to the Upgrading previous retail versions of Windows Server to Windows Server 2012 part of
Evaluation Versions and Upgrade Options for Windows Server 2012.
Hope it helps!
Regards.

Domain Controller upgrade windows 2008 r2 to windows 2012

I currently have 3 windows 2008 r2 domain controllers. 1 physical and 2 virtual. I am looking to see what the best upgrade path would be. the physical is the primary and has dhcp and dns services
Stonecold31666

See this,
http://social.technet.microsoft.com/wiki/contents/articles/16797.upgrade-to-active-directory-2012.aspx
Regards
Biswajit Biswas
My
Blogs|TechnetWiki
Ninja
Best regards Biswajit Biswas Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. MCP 2003,MCSA 2003, MCSA:M 2003, CCNA, MCTS, Enterprise Admin

In-place upgrade Windows 2008 to 2008R2 and effects on SharePoint

I have a SharePoint farm, with a WFE running on Windows 2008 64 bit. THe APP and SQL server both use 2008R2. It's a complicated setup, with many custom applications. Rather than a fresh install, we would prefer to maintain our current applications and configuration.
Can I perform an in-place 2008R2 upgrade? Will it affect SharePoint? The Farm?
Backup strategies?
Thanks,
Scott

Hi Scott,
Operating System in place upgrade is NOT supported with SharePoint 2010. It is recommended that building a new Win2008 R2 and restoring a backup of your SharePoint 2010.
For more information, you can have a look at the blogs:
https://social.technet.microsoft.com/Forums/en-US/8c638ca6-0edf-4d5d-a443-3841cb64f673/inplace-upgrade-from-windows-2008-to-2008-r2-breaks-sharepoint-2010?forum=sharepointadminprevious
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Simple external job works in windows 7 enterprise but not windows 2008 R2 enterprise.

SQL*Plus: Release 11.2.0.1.0
widows 7 sp1 and 2008 sp1 enterprise
The job runs without error on two windows 7 environments but the job fails on windows 2008 with:
error 255
"EXTERNAL_LOG_ID="job_89424_68834",
ORA-27369: job of type EXECUTABLE failed with exit code: The extended attributes are inconsistent.
I know it's not the credential as I can replace it with another undefined user and it will tell me that username and/or password is not valid.
I create a specific directory with the user in question and verified I can read/write to it.
without any job arguments to cmd.exe I still get the error.
the joe can run the cmd.exe without issue.
Is there some slight difference in windows 7 and 2008 server (security?) that would account for this?
user joe is a member of the local administrators and ora_dba groups on all servers
job and credential defined as follows:
BEGIN
    sys.dbms_scheduler.create_credential(
        username => 'joe',
        password => joespassword,
    database_role => NULL,
    windows_domain => NULL,
    comments => NULL,
    credential_name => '"DBREP"."joe"'
END;
BEGIN
    SYS.DBMS_SCHEDULER.CREATE_JOB (
            job_name => '"BLAH"."test"',
            job_type => 'EXECUTABLE',
            job_action => 'C:\Windows\System32\cmd.exe',
            number_of_arguments => 0,
            start_date => NULL,
            repeat_interval => NULL,
            end_date => NULL,
            job_class => '"SYS"."DEFAULT_JOB_CLASS"',
            enabled => FALSE,
            auto_drop => FALSE,
            comments => '',
            credential_name => '"BLAH"."joe"',
            destination_name => NULL);
        SYS.DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(
             job_name => '"BLAH"."test"',
             argument_position => 1,
             argument_value => '/c');
    SYS.DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(
             job_name => '"BLAH"."test"',
             argument_position => 2,
             argument_value => 'dir');
    SYS.DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(
             job_name => '"BLAH"."test"',
             argument_position => 3,
             argument_value => 'c:\temp');
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE(
             name => '"BLAH"."test"',
             attribute => 'logging_level', value => DBMS_SCHEDULER.LOGGING_FULL);
    SYS.DBMS_SCHEDULER.enable(
             name => '"BLAH"."test"');
END;

Hi Andy,
It seems you're hitting the unpublished bug 12886827. The fix for this bug is included in 11.2.0.3 patch bundle 1.
Since your version is 11.2.0.1, you'll need to upgrade, which is not a bad thing anyway because 11.2.0.1 has many bugs.

Windows 2008 R2 backup fails with event 521 error code 2155348001

Windows Server 2008 R2 SP1. Hyper-V role installed.
OS on drive C. All VMs stored on Drive D.
I am attempting to run a Bare Metal backup of the host system to a network share.
Drive D is not included in the backup job. I am getting the following error:
Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          1/10/2014 11:28:52 PM
Event ID:      521
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      SHAQTUS.scdl.local
Description:
The backup operation that started at '‎2014‎-‎01‎-‎11T04:08:50.683000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348001'. Please review the event
details for a solution, and then rerun the backup operation once the issue is resolved.
Reviewing event details, as suggested, does not offer any solution.
I have tried the suggested solutions in other similar threads of increasing the timeout value with the registry entry.
This does not work.
I have not tried reregistering the VSS writers manually, as the only links I have found are for server 2003/2008 (not R2) and explicitly state that they won’t work on higher versions of the OS, since they now utilize manifests and the manual procedure could
cause problems for those servers. Haven't found similar procedures for 2008 R2.
I have been able to narrow this down a bit.
A Windows 2008 R2 SP1 server with Hyper-V installed – backup to a network share is successful;
Install the DPM 2012 agent – same backup fails with the 2155348001 error.
We use DPM 2012 to backup VMs, but DPM cannot perform a bare metal backup/restore of server and the 2012 version no longer has the DPMSRT feature.
I prefer to run Bare Metal Backup to a file server share.
Stuck on this one.
Rick

Hi,
The issue is related to DPM, I would suggest you ask for help from DPM forums:
http://social.technet.microsoft.com/Forums/en-US/home?forum=dataprotectionmanager
Regards,
Mandy
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.

Windows 2008 failover clustering fails with Event ID 1205 1069 1558

I have a two nodes Windows 2008 and SQL 2008 cluster running in active\passive. I was restarting
my nodes after applying windows update then I received the following error message below within Failover Cluster Manager. I get errors with Event ID 1205 1069 1558 this happens every month .. Could someone help me on to find the root cause for
this issue how to check if it is an issue with network or Quorum drive ?

First, take a look at the 1069 event. This should point out which resource is failing.
Then, open a command prompt and run the command: cluster log /g
This will generate a cluster.log file that you can use to further troubleshoot this issue. The log file will be located in the C:\Windows\Cluster\Reports folder.
The cluster.log will be based on GMT time, so you may need to translate this to the local time zone in order to find the events you are looking for. Look for ERR or WARN messages and these should hopefully give you more insight as to why the resource is
failing.
Hope this helps.
Visit my blog about multi-site clustering

Windows 2008 R2 install fails on ProLiant MicroServer G7 N40L

The system has 4 x 2.5SATA drives. I have tried RAID10 and RAID1. Used a 500GB partition for the Windows install. Every time the install gets all the way to the end of the initial install after it completes copying the Windows files and it about to reboot when I get:
Windows could not prepare the computer to boot in the next phase of the installation. To install Windows, restart the installation.
This has happened 3 separate times all at the same place. What am I missing here? Is there some incompatability issue with Windows 2008 R2? The system has 2GB of RAM. I can't tell what kind of memory it is (ECC, non-ECC, etc.)
Thanks, Michael

Hi, Michael:
You may also want to post your question on the HP Business Support Forum -- Proliant Servers section.
http://h30499.www3.hp.com/t5/ProLiant/ct-p/proliant

Error on setup failover cluster with Windows 2008 R2 enterprise and SQL Server 2008 R2 (also with SP1)

Hi!
The setup process fails with this error:
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
I have found some hints by google, but nothing really helpfull.
Has anyone had a simular problem when installing SQL server 2008 R2?
All posts I found are about sql server 2008 (no R2!).
The cluster itself is working (storage, network, msdtc, quorum...).
Any hints?
Andreas
Here is the complete log:
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2067791871
Exit facility code:            1216
Exit error code:               1
Exit message:                  Failed: see details below
Start time:                    2012-04-06 11:23:57
End time:                      2012-04-06 12:01:21
Requested action:              InstallFailoverCluster
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0x625969A3%400x294A9FD9
Cluster properties:
Machine name: OC-SQLCL02ND01
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Machine name: OC-SQLCL02ND02
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Machine Properties:
Machine name:                  OC-SQLCL02ND01
Machine processor count:       32
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:                  Yes
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
Installation location:         G:\x64\setup\
Installation edition:          STANDARD
Slipstream:                    True
SP Level                       1
User Input Settings:
ACTION:                        InstallFailoverCluster
AGTDOMAINGROUP:                <empty>
AGTSVCACCOUNT:                 MANAGEMENT\sqladmin
AGTSVCPASSWORD:                *****
ASBACKUPDIR:                   S:\OLAP\Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   S:\OLAP\Config
ASDATADIR:                     S:\OLAP\Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      S:\OLAP\Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  MANAGEMENT\sqladmin
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            MANAGEMENT\administrator
ASTEMPDIR:                     S:\OLAP\Temp
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\ConfigurationFile.ini
CUSOURCE:
ENU:                           True
ERRORREPORTING:                False
FAILOVERCLUSTERDISKS:          Cluster Disk 3,Cluster Disk 4,Cluster Disk 5
FAILOVERCLUSTERGROUP:          SQL Server (MSSQLSERVER)
FAILOVERCLUSTERIPADDRESSES:    IPv4;172.29.2.122;Cluster Network 2;255.255.255.0,IPv4;172.29.3.122;Cluster Network 3;255.255.255.0
FAILOVERCLUSTERNETWORKNAME:    CLUSTER02
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SSMS,ADV_SSMS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD:                 *****
HELP:                          False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             S:\
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    MSSQLSERVER
INSTANCENAME:                  MSSQLSERVER
ISSVCACCOUNT:                  NT AUTHORITY\SYSTEM
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
PASSPHRASE:                    *****
PCUSOURCE:                     d:\install\mssql\sp1
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
RSINSTALLMODE:                 FilesOnlyMode
RSSVCACCOUNT:                  MANAGEMENT\sqladmin
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLDOMAINGROUP:                <empty>
SQLSVCACCOUNT:                 MANAGEMENT\sqladmin
SQLSVCPASSWORD:                *****
SQLSYSADMINACCOUNTS:           MANAGEMENT\administrator
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               L:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQLUSERDBDIR:                  T:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQLUSERDBLOGDIR:               L:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQMREPORTING:                  False
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       Analysis Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Reporting Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Integration Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Connectivity
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Complete
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Business Intelligence Development Studio
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\SystemConfigurationCheck_Report.htm

Hi Andreas Plachy,
Please make sure that the Virtual Server Name ‘CLUSTER02’ is unique on the network. In addition, are there any resources named ‘SQL Server’ on the Windows cluster? If that is the case, you may need to rename the related resources to avoid conflicting with
SQL Server, and try again.
Stephanie Lv
TechNet Community Support

Windows 2008 R2 IPSEC fails if NAT involved

I'm deploying a project that includes an IPSEC Tunnel between Windows servers, through a NAT Firewall. When both servers were windows 2003, this worked fine. We have had to migrate to Win2k8R2, and now the tunnel is established, but no traffic flows through
the tunnel.
The tunnel has been tested in both Windows Firewall with Advanced Security, and Legacy "Policy Agent" configuration with the same result.
Originally we were Win2k3 to Win2k3 and it worked:
|Win2k3 PRIVATEIP|-------|NATFW|-----------|Win2K3 PUBLICIP|
Then we had to switch one server to Win2k8R2:
|Win2k3 PRIVATEIP|-------|NATFW|-----------|Win2K8R2 PUBLICIP|
NATFW is mapping the yellow server to a blue IP address. It is a 1:1 mapping, NAT not PAT! Our tunnel establishes, but no traffic will flow. In our testing, we have the following results:
Yellow......Blue........Subnets...........Outcome
=================================================
2k8R2.......2k8R2.......same..............OK
2k3..........2k8R2.......same..............OK
2k3..........2k3..........same..............OK
2k8R2.......2k8R2.......routed,no.NAT....OK
2k3..........2k8R2.......routed,no.NAT.....OK
2k3..........2k3..........routed,no.NAT.....OK
2k8R2.......2k8R2.......routed,NAT........Fail.(quick/main.mode.established,.no.traffic)
2k3..........2k8R2.......routed,NAT........Fail.(quick/main.mode.established,.no.traffic)
2k3..........2k3..........routed,NAT........OK
any thoughts.

Hi I have exactly the same issue.
2k8R2.......2k8R2.......routed,no.NAT....OK
2k8R2.......2k8R2.......routed,NAT........Fail.(quick/main.mode.established,.no.traffic)
Did you find any solution for this?
It is recommended to install ISA server to manage NAT and IPSEC. But I don't want to do this for some reasons.

Windows 2008 R2 Firewall Fails to start

Ran into a problem where the Windows firewall Service fails to start after a reboot. The error is as follows:
The Windows Firewall service terminated with service-specific error This operation returned because the timeout period expired.
This has happened on a couple of servers (1 application server and 1 Print Server). The problem is intermittent, i.e out of 10 reboots it might occur 3 times. Manually starting the service works fine and the service starts with no errors.
I suspect a dependencies issue but I have kind of hit a brick wall and was hoping someone might have an idea what else to look at. Again, manually starting the service has never generated any error of any kind, and the service has always started.
Thanks in advance for any thoughts or suggestions.

Hi Dave K,
Thanks for posting here.
Could you please post the full information of the only event here ? include the event ID, key words ..etc.
Actually if you can confirm that all other dependencies services of main firewall service "Windows Firewall" (MPSSVC) were started up and running property , you may
try to set the “startup type” option to “automatic (delayed start)” and reboot to see if this issue will reproduce.
Meanwhile, other methods for troubleshooting firewall startup issues could be found form the article below:
http://blogs.technet.com/b/wsnetdoc/archive/2011/06/29/cool-set-of-topics-on-the-windows-firewall-service-by-david-pracht.aspx
Regards,
Tiger Li
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact
[email protected]
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Upgrade Windows 2008 R2 Standard to 2008 R2 Enterprise fails

Similar Messages

Maybe you are looking for