Messaging + cluster + Validation of resource failed

Hello,
I have messaging server 7 configured on 2 servers and there is one server for cluster. so 2 + 1 cluster here.
After manual scwitch to be3 from be1, service is running fine.
However in next step of configuration with cluster it is failing.
I have installed HA agent 7 which comes with comm suite 6 x86,Solaris 10
#scstat -g
-- Resource Groups and Resources --
            Group Name     Resources
Resources: mail1-msg-res  mail1-lh-res mail1-hastp-res
Resources: mail2-msg-res  mail2-lh-res mail2-hastp-res
-- Resource Groups --
            Group Name     Node Name                State          Suspended
     Group: mail1-msg-res  be1                Online         No
     Group: mail1-msg-res  be3                Offline        No
     Group: mail2-msg-res  be2                Online         No
     Group: mail2-msg-res  be3                Offline        No
-- Resources --
            Resource Name  Node Name                State          Status Message
  Resource: mail1-lh-res   be1                Online         Online - LogicalHostname online.
  Resource: mail1-lh-res   be3                Offline        Offline - LogicalHostname offline.
  Resource: mail1-hastp-res be1                Online         Online
  Resource: mail1-hastp-res be3                Offline        Offline
  Resource: mail2-lh-res   be2                Online         Online - LogicalHostname online.
  Resource: mail2-lh-res   be3                Offline        Offline - LogicalHostname offline.
  Resource: mail2-hastp-res be2                Online         Online
  Resource: mail2-hastp-res be3                Offline        Offline
#scrgadm -a -t SUNW.ims
root@e-eihqbe1 # scrgadm -a -j mail1-msg-res -t SUNW.ims -g mail1-msg-res -x IMS_serverroot=/messaging/mail1/bin/ -y Resource_dependencies=mail1-hastp-res,mail1-lh-res
(C189917) VALIDATE on resource mail1-msg-res, resource group mail1-msg-res, exited with non-zero exit status.
(C720144) Validation of resource mail1-msg-res in resource group mail1-msg-res on node be3 failed.What am I missing?
regards,
sumant.

Basically the problem causing the resource creation for the COMMS service to fail (ie, placing the messaging server under cluster control) is that in order to validate the service you have to be able to access the binaries on both system at the same time, like APACHE. So it's either, install binaries locally for both systems or use a global file system. It's not stated, but if you look in the HA configuration in Chapter 3 in Sun Java System Messaging Server 6.3 Administration Guide, the "Two node Symmetric Messaging Server -- Example" has an vfstab listed with the global options set. And if you look at the ZFS example in the 7.0 documentation, they install the binaries on the local file systems.
It appears the rule of thumb is:
Binaries=local or global
Config = failover fs
So what they guy did above-- or from what I can make sense of-- was to make the file system available to both hosts, at the same time. Since I was mucking with ZFS, I just copied everything over to the other host (scp), faked the mount point so the FS was available on both nodes, and then ran the create script. Once I was done, I deleted the copy and switched the resource at will.
Correct me if I'm wrong (chemo brain, and it's been a while) but I think the validate scripts are only used when creating the resource. You don't even need them when you create your own basic GDS service. If I was to create my own Agent, I'd just make sure the validation portion was under the start/stop script. I just might do that...

Similar Messages

  • Cluster Resource Failed in Clustered Role

    Hello All.
    We’re running our VMs on the Cluster of Hyper-V hosts of Windows Server 2012 R2.
    We frequently encounter the following error in the Cluster Events:
    “Cluster resource 'Virtual Machine VM123' of type 'Virtual Machine' in clustered role 'VM123' failed.
    Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart
    it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.”
    VM123 is the hostname of VM. We encounter this error for most of the VMs, however the VMs keep running in the cluster.
    Anybody please guide me what this error mean.
    Please help and advise.
    Regards,
    Hasan Bin Hasib

    Hi Hasan Bin Hasib,
    Since in your description there don’t have others detail clue, in your current information we can get the VM123 resource at failed status, you can first run the cluster validation
    to verify whether your cluster configuration is correct and install the Recommended hotfixes and updates first.
    Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
    https://support.microsoft.com/en-us/kb/2920151?wa=wsignin1.0
    Understanding how Failover Clustering Recovers from Unresponsive Resources
    http://blogs.msdn.com/b/clustering/archive/2013/01/24/10388009.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]

  • Cluster Validation Fails on List iSCSI Host Bus Adapters

    I have an 8 Node SQL Failover Cluster.
    This cluster has been in service for quite some time now, suddenly the Cluster Validation is failing...
    When it gets to the "List iSCSI Host Bus Adapters" (which we do no use on any of these nodes) it fails with the error:
    "An error occurred while executing the test. There was an error getting information about the iSCSI controllers installed on the nodes. There was an error retrieving information about the iSCSI host bus adapters from node 'node1'. Invalid class "
    The test is not performed on any of the other nodes, it just fails.
    This is causing a problem when trying to extend SQL to some of the newer nodes that have been added.
    I have tried evicting and readding nodes, I've tried uninstalling/reinstalling failover clustering, among other things.
    I did notice that on node7, if I attempt validation, and ONLY mention node7, the test will complete on that box only.
    Again, we do not even use iSCSI, this is a Fibre Channel cluster.  It's just the attempt by the validation wizard to list the iSCSI Host Bus Adapters that do not exist, that is failing....
    Any thoughts?  I did see a similar post which mentioned having a problem listing Fibre Channel adapters that sounded like the exact same error, but there was no resolution there either...

    Hi,
    For SQL Server Cluster issues, I suggest discussing them in our SQL Server Disaster Recovery and Availability forum. They are the best resource to troubleshoot SQL Server Cluster issues.
    http://social.msdn.microsoft.com/Forums/en/sqldisasterrecovery/threads
    Tim Quan - MSFT

  • Failed Cluster Validation Wizard - Active Directory

    Hi All,
    I have a problem creating a cluster that has just got me stumped.
    I've created two other clusters at two other sites with exact same hardware and configuration. All worked fine at those location.
    For this third location, the cluster build is not going so well.
    I have 2 x Dell server for a 2 node cluster, and a Dell SAN. There are iSCSI HBAs and switches for iSCSI and a flat network for the LAN and Management on another switch. The heartbeat is connected via a directly connected cable.
    The nodes are running 2012 R2 Core, with latest patches (April 2015).
    Firewall is disabled by Group Policy, both on servers and Domain Controller.
    The Domain Controller at this site is on the local LAN.
    On each future cluster node, the LAN cards can ping the Domain Controller by name and address (using -S to verify the source address). On the DC it can also ping each LAN interface, again both by name and IP. Heartbeat NICs can similarly ping each other.
    Using a Management Server on a remote subnet (Domain Account, local admin of all concerned servers, except the DC, and having read/write on the target OU), the Cluster Validation Wizard fails, on one node only.
    I'm getting an error message on "System Configuration\Validate Active Directory Configuration" of:
    Connectivity to a writable domain controller from node DEN1NTHV02.mycorp.net could not be determined because of this error: Could not get domain controller name from machine DEN1NTHV02.
    Node(s) DEN1NTHV01.mycorp.net can reach a writable domain controller.
    Node(s) DEN1NTHV02.mycorp.net cannot reach a writable domain controller. Please check connectivity of these nodes to the domain controllers.
    The computer accounts are in the same OU, and both are enabled and have no (seeming) other problems.
    So, (1) does anyone have any idea, or (2) where can I find the verbose output text of the failed test?

    Re-check your IP configuration.  Ensure the only NICs with a gateway defined is the primary NIC that will be used for client access.
    "a flat network for the LAN and Management on another switch. The heartbeat is connected via a directly connected cable."
    Just FYI.  Though a cross-over cable between the two nodes works for a two-node cluster, it is not recommended if there is even a chance of the cluster going beyond two nodes.
    Secondly, from your above statement, it sounds like you have the other, non-iSCSI networks plugged into a single switch.  That becomes a single point of failure.
    . : | : . : | : . tim

  • Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason: The handle is invalid.

    I'm stuck here trying to figure this error out.  
    2003 domain, 2012 hyper v core 3 nodes.  (I have two of these hyper V groups, hvclust2012 is the problem group, hvclust2008 is okay)
    In Failover Cluster Manager I see these errors, "Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason:  The handle is invalid."
    I restarted the host node that was listed in having the error then another node starts showing the errors.
    I tried to follow this site:  http://blog.subvertallmedia.com/2012/12/06/repairing-a-failover-cluster-in-windows-server-2012-live-migration-fails-dns-cluster-name-errors/
    Then this error shows up when doing the repair:  there was an error repairing the active directory object for 'Cluster Name'
    I looked at our domain controller and noticed I don't have access to local users and groups.  I can access our other hvclust2008 (both clusters are same version 2012).
    <image here>
    I came upon this thread:  http://social.technet.microsoft.com/Forums/en-US/85fc2ad5-b0c0-41f0-900e-df1db8625445/windows-2012-cluster-resource-name-fails-dns-registration-evt-1196?forum=winserverClustering
    Now, I'm stuck on adding a managed service account (mas).  I'm not sure if I'm way off track to fix this.  Any advice?  Thanks in advance!
    <image here>

    Thanks Elton,
    I restarted 3 hosts after applying the hotfix.  Then I did the steps below and got stuck on step 5.  That is when I get the error (image above).  There
    was an error repairing the active directory object for 'Cluster Name'.  For more data, see 'Information Details'.
    To reset the password on the affected name resource, perform the following steps:
    From Failover Cluster Manager, locate the name resource.
    Right-click on the resource, and click Properties.
    On the Policies tab, select If resource fails, do not restart, and then click OK.
    Right-click on the resource, click More Actions, and then click Simulate Failure.
    When the name resource shows "Failed," right-click on the resource, click More Actions, and then click Repair.
    After the name resource is online, right-click on the resource, and then click Properties.
    On the Policies tab, select If resource fails, attempt restart on current node, and then click OK.
    Thanks

  • Error Message on WLC5508 'Validation of STAT_PAYLOAD failed'

    Hi,
    Upon checking the logs, I'm seeing a lot of these messages;
    *emWeb: Oct 25 14:11:01.345: #LOG-3-Q_IND: spam_lrad.c:10136 Validation of STAT_PAYLOAD failed - AP  00:3a:98:09:4e:d0
    Always the same MAC address, which I assume is a Cisco AP trying to join.
    Anyone know what this means? The output interpreter/message decoder isn't much help.
    5508 Controller running ver 7.3.101.0.
    Cheers,
    Dan

    Also seeing...
    *spamApTask6: Oct 25 14:19:58.547: #LWAPP-3-VALIDATE_ERR: spam_lrad.c:10136 Validation of STAT_PAYLOAD failed - AP  00:3a:98:09:4e:d0
    and
    *Dot1x_NW_MsgTask_0: Oct 25 14:17:01.149: #LOG-3-Q_IND: spam_lrad.c:10136 Validation of STAT_PAYLOAD failed - AP  00:3a:98:09:4e:d0
    All refer to the same MAC above.
    Also I noticed in the traps that the RADIUS server is flipping to the backup every few minutes after the 'live' one doesn't respond in a timely manner....
    Thu Oct 25 14:29:55 2012
    RADIUS server 10.2.100.50:1646 activated on WLAN 2
    33
    Thu Oct 25 14:29:55 2012
    RADIUS server 10.15.5.100:1646 deactivated on WLAN 2
    34
    Thu Oct 25 14:29:55 2012
    RADIUS server 10.15.5.100:1646 failed to respond to request (ID 195) for client 00:21:6a:4c:6a:e0 / user 'KIE\NDaly'
    35
    Thu Oct 25 14:29:47 2012
    RADIUS server 10.15.5.100:1646 activated on WLAN 2
    36
    Thu Oct 25 14:29:47 2012
    RADIUS server 10.2.100.50:1646 deactivated on WLAN 2
    37
    Thu Oct 25 14:29:47 2012
    RADIUS server 10.2.100.50:1646 failed to respond to request (ID 58) for client 00:21:6a:4c:6a:e0 / user 'KIE\NDaly'
    Checking for network issues between the WLC and ACS now....

  • Failing "List Services Information" Cluster validation test

    Hi
    I'm building a 2 node Windows 2008 SP2 Cluster. I've setup the SAN Disks, NIcs etc and am running the cluster validation tests. However this always fails on the "List Services Information" Test with the following error statement:
    "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 '<Server FQDN>'. Object reference not set to an
    instance of an object.
    Note: I replaced the actual server fqdn with <Server FQDN>
    Any help is appreciated.
    Thanks

    Hi,
    I know it is not a SQL cluster but you could still have a try with steps below as a workaround. See:
    http://support.microsoft.com/kb/953748/en-us
    •For an integrated failover Add-Note setup, run the following command on each node that is being added:
    Setup /SkipRules=Cluster_VerifyForErrors /Action=InstallFailoverCluster
    •For an advanced or enterprise installation, run the following command:
    Setup /SkipRules=Cluster_VerifyForErrors /Action=CompleteFailoverCluster
    •If you receive this validation failure when you add a node to an existing failover installation, run the following command on each node that is being added:
    Setup /SkipRules=Cluster_VerifyForErrors /Action=AddNode
    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

  • [svn] 2277: 1) Update the messaging-config. xml under resource and add the cluster definition with shared-backend attribute .

    Revision: 2277
    Author: [email protected]
    Date: 2008-06-27 08:22:18 -0700 (Fri, 27 Jun 2008)
    Log Message:
    1) Update the messaging-config.xml under resource and add the cluster definition with shared-backend attribute. [#blz-197]
    2) Minor update to the session test.
    Ticket Links:
    http://bugs.adobe.com/jira/browse/blz-197
    Modified Paths:
    blazeds/branches/3.0.x/qa/apps/qa-regress/WEB-INF/src/remoting/session/FlexSessionAttribu teListenerTest.java
    blazeds/branches/3.0.x/resources/config/messaging-config.xml

    To use servlets u have indeed to update your web.xml...Well I'm not sure this is relevant to your case anyway.
    You have to add a <servlet> element to this file.
    Something like this:
    <servlet>
    <servlet-name>blabla</servlet-name>
    <servlet-class>blablapackage.Blablaclass</servlet-class>
    <init-param>...</init-param>
    </servlet>
    Now this may not solve your problem. Make sure you refer to your servlets using their full qualified names.btw, just to be sure, what is your definition of "servlet"? (i mean: any java class or only javax.servlet.Servlet)

  • Error when creating a resource : Failed to initialize the DSDL

    Hi,
    I've configured a cluster and trying to configure an Oracle mount point. ,ve already created the listerner and server resources for Oracle but having the following error with mount point creation:
    Command executed: /usr/cluster/bin/clresource create -t SUNW.HAStoragePlus:5
    -g int_group -p
    Resource_project_name=default -p FilesystemMountPoints=/global/data
    oracle_mount_point
    Error message:
    clresource: pegase-par-sun-wfl-int-a - Failed to process the resource
    information.Failed to
    initialize the DSDL.
    clresource: (C189917) VALIDATE on resource oracle_mount_point, resource
    group int_group, exited with
    non-zero exit status.
    clresource: (C720144) Validation of resource oracle_mount_point in resource
    group int_group on node
    pegase-par-sun-wfl-int-a failed.
    clresource: (C891200) Failed to create resource "oracle_mount_point"
    Could you please help me?

    should i have to install a particular library or something like that? DSDL ?
    thanks for your help

  • Cluster network name resource error 1196

    I have a two-node Hyper-V 2012 Core Server cluster. Initially, the cluster was working fine and I was able to do live migrations with no problem. I first realized that something had gone wrong when I was attempting to move a VM's storage to the Cluster Disk.
    When I right click on the VM and select Move > Virtual Machine Storage, the bottom left area of the "move storage" screen says "Loading..." forever and never displays the cluster storage. This happened once before and I was able to correct
    the issue by taking the Server Name resource offline and doing More Actions > Repair. However, if I try a repair now I receive the following error messages:
    "There was an error repairing the active directory object for 'Cluster Name'. Error Code: 0x800713b8. The cluster request is not valid for this object". 
    I have verified that the cluster name Active Directory object (CCSDCluster) still exists and each node as well as itself has full permissions to the object. What I am not certain of is whether the object is still in the same Organizational Unit as it was
    originally. After the failed repair attempt, I am able to bring the Server Name resource back online successfully.
    In addition, I am continually receiving cluster event errors indicating the following:
    "Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason: The handle is invalid. Ensure that the network adapters associated with dependent IP address resources are configured
    with at least one accessible DNS server." 
    Each of the two nodes has multiple NICs configured. One for management, one for guest OSs (Hyper-V virtual switch is configured to use this NIC and not allow management OS access), and two for iSCSI (for redundancy and multi-path). Live migration is set
    to only use the management NICs. The management NIC on both nodes is configured with valid DNS servers. The CCSDCluster DNS entry has full permissions for both nodes and itself.
    Any suggestions on what to try would be greatly appreciated. Thank you!

    Could my issues be related to a problematic network configuration? Please see the ipconfig below from one of my Hyper-V host servers.
    Ethernet adapter Ethernet 8 = iSCSI
    Ethernet adapter Ethernet 6 = iSCSI
    Ethernet adapter Ethernet 2 = Management interface
             10.1.3.19 = Management IP address, 10.1.3.3 = IP address of Cluster Name Object
    Tunnel adapter Local Area Connection *11 = ?? Not sure what this one is
    Windows IP Configuration
       Host Name . . . . . . . . . . . . : CCSDVM01
       Primary Dns Suffix  . . . . . . . : clairton.local
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : clairton.local
    Ethernet adapter Ethernet 9:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter #4
       Physical Address. . . . . . . . . : 28-92-4A-AF-46-34
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    Ethernet adapter Ethernet 8:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter #3
       Physical Address. . . . . . . . . : 28-92-4A-AF-61-68
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 172.16.1.12(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 172.16.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter Ethernet 7:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter #2
       Physical Address. . . . . . . . . : 28-92-4A-AF-61-6C
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    Ethernet adapter Ethernet 6:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter
       Physical Address. . . . . . . . . : 28-92-4A-AF-46-30
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 172.16.1.11(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 172.16.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter Ethernet 3:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #55
       Physical Address. . . . . . . . . : E4-11-5B-B9-3A-9C
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    Ethernet adapter Ethernet 2:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #58
       Physical Address. . . . . . . . . : E4-11-5B-B9-3A-A2
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 10.1.3.19(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       IPv4 Address. . . . . . . . . . . : 10.1.3.3(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.1.3.100
       DNS Servers . . . . . . . . . . . : 10.1.3.10
                                           10.1.3.39
       NetBIOS over Tcpip. . . . . . . . : Enabled
    Tunnel adapter Local Area Connection* 11:
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
       Physical Address. . . . . . . . . : 02-AD-4B-6D-A9-FB
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 169.254.2.92(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.0.0
       Default Gateway . . . . . . . . . :
       NetBIOS over Tcpip. . . . . . . . : Enabled

  • WWW service is not able to start via Microsoft Failover Cluster generic service resource

    Environment
    Cluster Nodes = two
    Cluster Nodes OS = Windows 2008R2
    Application = IIS
    Query
    I created generic service resources of many windows services under Microsoft Failover Cluster and they are failing over successfully but when I create a generic service resource for WWW, then the WWW service is not able to online
    via Microsoft Failover Cluster. It stuck in online pending.
    I have noticed two things.
    1.) If the WWW service is set to manual and started at passive node and I manually restart the Active node then the WWW service successfully switch over to stand by/passive node. but if the WWW service is set to
    manual and not started on stand by/Passive node then the WWW service is not failing over.
    2.) if I kill the WWW service manually (as a test case) on Active Node via this command (taskkill /f /pid XXXX) then the WWW service failed and is not failing
    over to standby/passive node.
    Any comment will be appreciated. Thanks. Zahid Haseeb.

    The problem is resolved. I feel that it will be helpful to other people who may face the same problem which I faced, so I wrote a blog on "How to configure IIS Web Site and Application Pool in Microsoft Failover Cluster" and mentioned almost all activities
    which I have done. Kindly see the resolution under section "Configure some changes in Cluster Configuration" in the below link
    http://zahidhaseeb.wordpress.com/2014/02/12/how-to-configure-iis-web-site-and-application-pool-in-microsoft-failover-cluster/
    Any comment will be appreciated. Thanks. Zahid Haseeb.

  • Cluster Setup Support Rules fails with Warnings

    Hi,
    I'm in the process of installing our ECC production server in a clustered environment on windows server 2008 with SQL server 2008 as our database.
    The MSCS cluster at the OS level has been configured successfully. When I start the SQL server installation as mentioned in the installation guide, the Setup Support Rules fails with following warnings.
    1. The setup support file prompts me to set the MSDTC service as a clustered one but it was not mentioned anywhere in the installation guide that the MSDTC service needs to be clustered. Do I need to cluster that service with seperate network ip address and cluster group ?
    2. The Network binding order issues a warning even though the adapters are set up in the right order as mentioned in the installation guide.
    3. Eventhough there is a internet connectivity available in the server, the "Microsoft .Net Application Security" check issues a warning.
    NB: As per the cluster validation report, the clustering at the OS level seems to be fine.
    Please provide me your valuable suggestions to rectify these warnings. Can I ignore these warnings and proceed with the installation of SQL Server ?
    Regards,
    Varadharajan M

    Hi,
    Microsoft Distributed Transaction Coordinator
    Is is user by older versions of Mssql database.
    From a SAP perspective you don't need this service.
    You can ignore setup request for this service.
    As per the reply, I understand that the MSDTC service is not mandatory to cluster in Windows Server 2008/MS SQL Server 2008. But when i try to install the SQL DB, the Set support rule ends up with warnings saying that the MSDTC service should be clustered. Can I ignore the warnings and proceed with the installation. Can anyone confirm this please ?
    Also please confirm whether we need to have the db cluster group in the DNS before initiating the SQL Server Set up.
    Regards,
    Varadharajan M

  • DAG 2010 Cluster IP address resource 'Cluster IP Address' cannot be brought online because the cluster network replication

    Hello,
    DAG Exchange 2010 SP3 RU6 with MAPI network and Replication network. All works correctly.
    But, when the DAG member restarts , the cluster goes offline and i can't bring it online.
    The message error:
    Cluster IP address resource 'Cluster IP Address' cannot be brought online because the cluster network 'Cluster Network 1' is not configured to allow client access.
    Cluster Network 1 is the replication network and it is normal that allow client access is unchecked
    I already tried to check, apply then uncheck apply. it does anything.
    Could you please help me to figure out the issue ?
    Best regards

    Hi,
    Check below link.
    http://forums.msexchange.org/Cluster_network_name_is_not_online/m_1800552315/tm.htm
    I was able to resolve the issue without taking down any resources.
    First, I noticed that the Failover Cluster Manager "Cluster Name" had the IP address of the replication network only..
    After going back through the guide @
    http://technet.microsoft.com/en-us/library/dd638104.aspx I changed the properties on the NICs for file sharing, etc..I then adjusted windows firewall rules to block traffic from my MAPI network destined for the replication network. 
    I then removed the IP from the replication network on the DAG leaving only the 1 MAPI network IP.
    After an hour or so, I ran Get-DatabaseAvailabilityGroupNetwork and seen that the MAPIAccess property was finally set to true on my MAPI network. I went back to Failover Cluster Manager and my Cluster Core Resource Cluster Name dropped the IP address that was
    associated (IP from the replication network) I added a new IP from my Mapi network range, updated the DAG IP in Exchange and the DNS record for the DAG and my cluster resource came online.

  • [svn:bz-trunk] 9839: Document enforce-endpoint-validation in resources/ config/services-config.xml.

    Revision: 9839
    Author:   [email protected]
    Date:     2009-08-31 11:29:03 -0700 (Mon, 31 Aug 2009)
    Log Message:
    Document enforce-endpoint-validation in resources/config/services-config.xml.
    Modified Paths:
        blazeds/trunk/resources/config/services-config.xml

  • Error Message: The content processing pipeline failed to process the item

    Hi Everyone:
    Our crawl logs yesterday show a ton of errors.  Half of the items being crawled are failing.  We are getting the following message:
    The content processing pipeline failed to process the item. ( There was an internal problem connecting to or querying the database.; ; SearchID = 8869868B-F919-41D1-8FC5-B55585EE479C )
    Does anyone know what the root cause of this issue is?  Our search was working just fine and now this has suddenly occurred.  Can it be due to resources?  Is it because of a change we just made?
    Thank you,
    Jake

    Hi Jake,
    What changes have you made for your SharePoint environment?
    Have you reset search index and started a full crawl if possible?
    Please check the following article about adding the search service account in SharePoint search server local admin, then check results again.
    http://trikks.wordpress.com/2013/03/19/fixing-the-sharepoint-2013-search-error-the-content-processing-pipeline-failed-to-process-the-item/
    Thanks
    Daniel Yang
    TechNet Community Support

Maybe you are looking for