DFS-R folder resources Failed in Failover Cluster on Server 2008 R2

Maybe a week ago, 7 of our DFS-R Folder failover cluster resources lost their configuration data. In the resource list, they just show up as "()".
I've seen suggestions online that disabling the replicated folder will remove it from the Failover Cluster, and then re-enabling it will automatically add it back to the cluster. So, I've disabled it via the Connections tab, and that does nothing. The other
option is to disable it under the Memberships tab...but that has consequences, and I would rather not do that if it isn't necessary.
I'm also now seeing event ID 5012's popping up in the DFS Replication logs every hour or so.
The DFS Replication service failed to communicate with partner etc etc. The partner did not recognize the connection or the
replication group configuration.
Error: 9026 (The connection is invalid)
Now, "dfsrdiag pollad /verbose" or "dfsrdiag pollad /mem:<dc name>" both come back as successful. And a DFS Diagnostic Report brings back nothing apparently relevant to this issue, other than one error concerning the same event
ID 5012's.
Also, I've verified that it's not a DNS issue, pinging the home office DFS server from the site server resolves correctly, and vice versa. And the windows firewall is disabled on both servers. It's POSSIBLE that there is a network issue. Replication works
fine between the site server and the 2nd cluster server service, just not between the site server and the 1st cluster server service. However, via netstat I see active connections between the site server and the cluster server, as well as the active cluster
host (although, just a single connection to the clustered DFS server, but ~6 to the cluster host itself).
So, I'm completely at a loss here. Any recommendations?

Hi,
This error usually occurs when one partner attempts to establish an RPC connection with another member, but is unable to.
You could refer to the thread below to troubleshoot the issue:
DFSR Event ID 5012 when other DFS folder working
https://social.technet.microsoft.com/Forums/en-US/9748cb08-858d-454e-93cd-233c98cb2ee8/dfsr-event-id-5012-when-other-dfs-folder-working?forum=winserverfiles
Best Regards,
Mandy
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]

Similar Messages

  • Migrating single file server to failover cluster file server

    Hi,
    Currently we have one file server which is our Domain controller also. File Server data stored in SAN storage lun. Users home folders also resides at file server.Now we want to create 2 node failover cluster file server.
    Questions:
    1)Can we assign same storage lun to failover cluster?
    2)Do we need to assign all permissions and storage quota again?
    What is the best option to achieve this goal.                                                                            

    Hi,
    if you attach the same LUN to the failover cluster the NTFS permission (security tab) are retained because they are stored in the LUN itself
    Share permission are lost because they are stored in the registry of the file server. If you have few share with a simple share permission structure, simply recreate them in the cluster. If you have a lot of shares and complex permission tree, you have to
    export registry hives related to lanmanserver\shares

  • Windows 2012 Failover Cluster - File server role (vCO)

    Hi, 
    I wonder if anybody can shed some light on a query i have.
    A windows 2012 failover cluster will be built in AD domain example.uk.  Cluster File server roles will be created and will reside in this domain also.
    We also have a requirement to run a cluster file server role in the child domain off secure.example.uk.  Is this possible? or do the file server roles and related vCO's have to reside in the same domain as the cluster (CNO).
    I know the CNO can be used to create the VCO but could a prestage a VCO in the child domain of secure.example.uk.
    Mark

    Hi Mark,
    By default CNO will create 
    VCO automatically in default domain computer OU, we generally use the
    KISS principle to place the CNO and VCO to the same OU, and as far as I know there no known design document indicate the VCO can be placed in different domain, therefore I suggest you place the CNO and V CO at same OU.
    More information:
    When Creating a New Resource or Role in Windows Server 2012 R2 Failover Cluster, the Network Name Fails to Come Online or Failed to Create Associated Computer Object in Domain
    http://blogs.technet.com/b/askpfeplat/archive/2014/11/17/when-creating-a-new-resource-or-role-in-windows-server-2012-r2-failover-cluster-the-network-name-fails-to-come-online-or-failed-to-create-associated-computer-object-in-domain.aspx
    CNO Blog Series: Increasing Awareness around the Cluster Name Object (CNO)
    http://blogs.technet.com/b/askcore/archive/2012/09/25/cno-blog-series-increasing-awareness-around-the-cluster-name-object-cno.aspx
    How to Create a Cluster in a Restrictive Active Directory Environment
    http://blogs.msdn.com/b/clustering/archive/2012/03/30/10289577.aspx
    Prestage Cluster Computer Objects in Active Directory Domain Services
    https://technet.microsoft.com/en-us/library/dn466519.aspx
    I’m glad to be of help to you!
    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 Support, contact [email protected]

  • 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

  • Failover cluster File Server role best practices

    We recently implemented a Hyper-V Server Core 2012 R2 cluster with the sole purpose to run our server environment.  I started with our file servers and decided to create multiple file servers and put them in a cluster for high
    availability.  So now I have a cluster of VMs, which I have now learned is called a guest cluster, and I added the File Server role to this cluster.  It then struck me that I could have just as easily created the File Server role under my Hyper-V
    Server cluster and removed this extra virtual layer.  
    I'm reaching out to this community to see if there are any best practices on using the File Server role.  Are there any benefits to having a guest cluster provide file shares? Or am I making things overly complicated for no reason?
    Just to be clear, I'm just trying to make a simple Windows file server with folder shares that have security enabled on them for users to access internally. I'm using Hyper-V Core server 2012 R2 on my physical servers and right now I have Windows
    Server Standard 2012 R2 on the VMs in the guest cluster.
    Thanks for any information you can provide.

    Hi,
    Generally with Hyper-V VMs available, we will install all roles into virtual machines as that will be easy for management purpose.
    In your situation the host system is a server core, so it seems that manage file shares with a GUI is much better.
    I cannot find an article specifically regarding "best practices of setting up failover cluster". Here are 2 articles regarding build guest cluster (you have already done) and steps to create a file server cluster. 
    Hyper-V Guest Clustering Step-by-Step Guide
    http://blogs.technet.com/b/mghazai/archive/2009/12/12/hyper-v-guest-clustering-step-by-step-guide.aspx
    Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster
    https://technet.microsoft.com/en-us/library/cc731844(v=ws.10).aspx
    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Failover Cluster on Server 2012 R2

    Hi
    I`m trying to deploy a Failover Cluster with two servers, both Virtual machines on Vmware, OS- server 2012 r2.
    Both servers can see all disks from storage.
    For some reason, I keep getting these messages(for all disks) when I run "Validate Configuration" before creating the cluster:
    1. Persistent Reservation Registration key 0x1000100b2 for Test Disk X reservation holder node "Servername" was not removed by the call to REGISTER using RESERVATION KEY 0x1000100b2 and SERVICE ACTION RESERVATION KEY 0x1000100c2.
    2. Test DiskX does not support SCSI-3 Persistent Reservations commands needed by clustered storage pools that use the Storage Spaces subsystem. Some storage devices require specific firmware versions or
    settings to function properly with failover clusters. Contact your storage administrator or storage vendor for help with configuring the storage to function properly with failover clusters that use Storage Spaces.
    all other steps come sout with no errors.
    I have already deployed another cluster, the same way, and didn`t get any of those messages..
    Can anyone give me a hand here?
    Thank you!
    I

    Hi Moriyas,
    The VMware has some specific supported scenario when we use failover cluster, please refer the following VMware KB to realize the detail requirement on your current platform.
    Microsoft Clustering on VMware vSphere: Guidelines for supported configurations (1037959)
    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1037959
    Microsoft Cluster Service (MSCS) support on ESXi/ESX (1004617)
    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004617
    I’m glad to be of help to you!
    *** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these
    sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use
    of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
    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 Support, contact [email protected]

  • List Services Information" fails during cluster validation Server 2008 R2

    Server 2008 r2 ent
    An error occurred while executing the test. There was an error getting information about the running services on the nodes. There was an error retrieving information about the Services from node 'XXXXX.XXXXX.COM'. Object reference not set to an instance
    of an object.

    Hi,
    Please offer more detail information about the error content, from your current information it hardly to say why it occur, base on my experience it may cause by the different version server edition, such as the different update or different hot fix installed
    on some server, please confirm the cluster nodes have the same server edition and update.
    The related KB:
    Understanding Requirements for Failover Clusters
    http://technet.microsoft.com/en-us/library/cc771404.aspx
    Hope this helps.
    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.

  • Failed SQL express install on Server 2008 Standard

    I am attempting to install Visual Web Developer 2008 Express Edition on a Server 2008 Standard SP2, which all ready includes SQL Server 2008. The installer includes SQL Server Express, which is failing without any error codes. 
    Visual Web Developer only partly installs. The tools folder has a shortcut to Remote Debugger, as the only component to succeed. It seems this is the newest version of Visual Studio compatible with Server 2008 Standard.
    My real goal is to create an empty Win Forms site bound to its existing SQL Server 2008 and then drop my completed development site pages into the production server. I need a successful complete install.
    Thanks,
    Kurt

    Hello,
    Based on your description, you had install SQL Server 2008 Standard edition, and you try to install the Visual Web Developer 2008 Express Edition SP1 with SQL Server 2008 Express, but SQL Server install failed with this error message: "A component could not
    be downloaded".
    When install SQL Server express, it will download files from website, please verify the issue is not caused by the network issue.
    You can try to review the SQL Server Setup log for more details. The dafult path is:
    C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\LOG\.
    You can also try to download the SQL Server 2008 express from the following link and install separately.
    http://www.microsoft.com/en-in/download/details.aspx?id=1695
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

  • Windows Search Service failing to install on Windows Server 2008 R2 Terminal Server

    Hi,
    I am unable to install the Windows Search Service on a Server 2008 R2 Terminal Server. I want to install this to enable indexing options within Outlook 2013 for all users.
    Server Manager > Add Roles > File Services > Select only Windows Search Service > Install.
    The error I receive: "Attempt to configure Windows Search Service failed with error code 0x80070057. The parameter is incorrect."
    Thanks,
    Bjorn

    Hi,
    I did the test and could install the Windows Search Service without problem.
    Which role did you installed on the terminal server?
    Did you try to install it on another windows server?
    Regards.
    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 Support, contact [email protected]

  • Login fails when connecting to SQL Server 2008

    There were 3 databases and a report server database on sql server 2008 r2. All were renamed.  Now, when trying to connect to sql server I am getting a login failed error for default database. I'm guessing because the default db name was changed. How
    can I fix this so that I can connect to the db server\instance?
    Thanks

    Hi ,
    According to your description, I do a test in SQL Server 2008R2. If you use windows system admin account to log in the instance via Windows authentication, even if you change all use database name, you can still log in successfully. However, if you create
    a SQL Server login name to connect to instance via SQL Server authentication, when you change the default database name, it will
     occur the error which just like at follows .
    //Cannot open user default database. Login failed.
    Login failed for user '***'. (.Net SqlClient Data Provider), Error Number: 4064//
    I recommend you change the default database any existing database on your server like master via clicking on Option , or you can run following statement for username
     to replace your original database name with master.
    ALTER LOGIN [login name] WITH DEFAULT_DATABASE = master
     GO
    Thanks,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • SAP-R/3 resource fails in CRM cluster instalation.

    Hi.
    We just install CRM 4.0 in a cluster, and everything was working perfectly, but at the moment that we increased the value for parameter PHYS_MEMSIZE, the SAP-R/3 resource did not work anymore.
    At this moment we already check several notes and also we replaced some dll in the kernel, c:windowssystem32 and c:windowsSapCluster, but this resource still failed.
    Does somebody know how to solve this issue?
    Thanks
    Jorge Ramírez C.

    This issue was already solved.
    The problem was at the moment that we import profile, this action cut a line of the profile file.
    we had to use variables into the profile file in order to have a shorter line.
    It was really curious, because if we tried to start the SAP instance without cluster service it worked perfectly.
    Anyway now everything is working very well, thank you so much for your time.
    Jorge Ramírez Carrasco.

  • User profiles service services failed the logon on windows server 2008 R2

    Please help!
    I have try the steps from http://support.microsoft.com/kb/947215
    Method 3
    -Delete user folder on c:\users >>> the folder is deleted. no file left.
    -Delete user profile list registry 
    Still could not logon and it shows the error only for that user. Other users or new user are fine. 
    The step that I did not do is RESTART a server. because this is production server.
    Please help if there is any solution to fix this.

    Hi,
    Is the group policy Do not logon users with temporary profiles configured?
    If yes, please disable it, then run gpupdate /force on problematic machine and test if the issue persists.
    Best Regards,
    Amy

  • I Am Getting Failed Notifications When Installing SQL SERVER 2008 can any one suggest me Wt can i do

    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Exit code (Decimal):           -2068643839
      Exit facility code:            1203
      Exit error code:               1
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Start time:                    2014-03-07 08:24:10
      End time:                      2014-03-07 09:07:13
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\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.0.1600.22%26EvtType%3d0xC71AA851%400x73BA6908
    Machine Properties:
      Machine name:                  HOME
      Machine processor count:       1
      OS version:                    Windows XP
      OS service pack:               Service Pack 3
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
    Package properties:
      Description:                   SQL Server Database Services 2008
      SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
      ProductName:                   SQL2008
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         E:\Projects\Sqlserver2008\x86\setup\
      Installation edition:          ENTERPRISE
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            HOME\Administrator
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\ConfigurationFile.ini
      ENABLERANU:                    False
      ERRORREPORTING:                False
      FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
      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\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      MEDIASOURCE:                   E:\Projects\Sqlserver2008\
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           HOME\Administrator
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    1
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0xB8A6B4FA
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
      MSI error description:         
      Configuration status:          Failed: see details below
      Configuration error code:      0xEEBAE95A
      Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0xB8A6B4FA
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
      MSI error description:         
      Configuration status:          Failed: see details below
      Configuration error code:      0xEEBAE95A
      Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0xB8A6B4FA
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
      MSI error description:         
      Configuration status:          Failed: see details below
      Configuration error code:      0xEEBAE95A
      Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
      Feature:                       Analysis Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0xB8A6B4FA
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_as_Cpu32_1.log
      MSI error description:         
      Configuration status:          Failed: see details below
      Configuration error code:      0xEEBAE95A
      Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
      Feature:                       Reporting Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                0xB8A6B4FA
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_as_Cpu32_1.log
      MSI error description:         
      MSI status:                    Failed: see details below
      MSI error code:                0xB8A6B4FA
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
      MSI error description:         
      Configuration status:          Failed: see details below
      Configuration error code:      0xEEBAE95A
      Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
      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:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools SDK
      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
      Feature:                       SQL Server Books Online
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Microsoft Sync Framework
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\SystemConfigurationCheck_Report.htm

    Hello,
    Please check below link
    http://support.microsoft.com/kb/955403/en-gb
    SQL Server enterprise edition is not supported on Windows XP.You can install but its not supported by Microsoft.
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Setting Expiration period for Maintenance Plan Backups fails to work in sql server 2008

    I have created a Maintenance Plan to do a nightly full backup and set the backup
    set to expire after 4 days in sql server 2008 R2.
    Weeks later, old backups are sitting on the hard drive.Please do the needful.

    I have created a Maintenance Plan to do a nightly full backup and set the backup
    set to expire after 4 days in sql server 2008 R2.
    Weeks later, old backups are sitting on the hard drive.Please do the needful.
     Can any one please explain what is the use of BACKUP Expiration ??? 
     I created a backup with expiration date but still am using the same backup file to restore databases?? Then what is the use of Expiration date?

  • Replication solution for MSCS Failover Cluster?

    That is definitely the plan, just a matter of finding the best software solution to achieve that. I imagine StarWind free version is an option...

    I am setting up a multi-site windows failover cluster (windows server 2008 r2), to be used for a print services cluster. My sites are connected via mlps network, but I've run into a bit of a snag: I need to have shared storage (cluster disk), and since it is across multiple sites, it is going to have to be 2 volumes that have replication between them that complies with MSCS (removing options like vmware replication and MS DFS).  Each location has SAN storage, but are from different providers and cannot replicate between each other on that level, so I am looking for a (free or low-cost) software solution that I can put inside a VM at each location to serve as my cluster disk.
    Any suggestions are greatly appreciated, thanks.
    This topic first appeared in the Spiceworks Community

Maybe you are looking for