• Register

SQL Server Video Tutorial Just for $50 

Follow DBATAG

twitter facebook Feed email

Subscribe to Email Newsletters

How to resolve Windows Error 5018 - 0x8007139A - The cluster resource could not be brought online by the resource monitor

0 votes
I am getting Windows Error 5018[0x8007139A]
 
 The Error Message says :
 
The cluster resource could not be brought online by the resource monitor.
 
 
 Any suggestions [ Solution | TIPS ]  to resolve [FIX] this ?
 
  This is Windows Error Code ERROR_RESMON_ONLINE_FAILED  Message
 
 
 Thanks
asked by DBACSE
edited by anonymous

1 Answer

0 votes
Microsoft Exchange 2000 Server and Microsoft Exchange Server 2003 enforce Active/Passive scenarios on Exchange clusters that have more than two nodes. This means that on a four-node Exchange 2000 cluster or a four-node Exchange 2003 cluster, only three Exchange virtual servers can be created, and only one Exchange virtual server can be hosted per node.



For Datacenter clusters, you must update Exchange 2000 to Exchange 2000 Service Pack 1 (SP1) or later before you create the System Attendant resources (this does not apply to Exchange 2003). If an earlier version of Exchange 2000 is installed on a Datacenter cluster, and you try to create System Attendant resources, you may receive the following error message:


An error occurred attempting to add pages from the '{30C5DA98-BA0C-11D2-BC65-00C04FA32177}' extension DLL. Catastrophic failure. Error ID: -2147418113 (8000ffff).



Event Type: Error
Event Source: MSExchangeCluster
Event ID: 2076
Description:<SAResourceName>: Cluster Service failed resource control function
 
For more information, click http://search.support.microsoft.com/search/?adv=1.


Note
Error 5007 = ERROR_RESOURCE_NOT_FOUND
On Exchange 2000 clusters and Exchange 2003 clusters that have more than two nodes, only one Exchange virtual server at a time can come online on each node. In a configuration that has a single passive node (N+1), this means that if two nodes fail, only one Exchange Virtual Server can come online, and the second Exchange Virtual Server cannot come online.

During the failover, you may receive the following error message (where <SA> is the System Attendant resource name:
An error occurred attempting to bring the '<SA>' resource online: The cluster resource could not be brought online by the resource monitor. Error ID: 5018 (0000139a).


The following events are logged in the system event log:
Event ID: 1065
Event Type: Error
Event Source: ClusSvc
Description:
Cluster resource SA failed to come online.

Event ID: 1069
Event Type: Error
Event Source: ClusSvc
Description:
Cluster resource 'SA' failed.

Error 5071 = ERROR_NODE_CANT_HOST_RESOURCE
Error 5018 = ERROR_RESMON_ONLINE_FAILED



By default, all the resources that are in the cluster are configured to permit "possible owner" of all nodes that are in the cluster, and no "preferred owner" values are set. If a failure is experienced, the Exchange 2000 and Exchange 2003 resources may try to come online on a node that is already running an Exchange virtual server. As described earlier in this article, the resources cannot come online.



To work around this issue, make sure that you correctly configure the failover policies on the cluster to target any failure to a passive node.

http://support.microsoft.com/kb/197047  -  Failover/failback policies on Microsoft Cluster Server


Exchange 2000 clusters can host only a single MAPI public folder store across all Exchange virtual servers in the cluster. By default, only the first Exchange virtual server that is created contains a public folder store that is associated with the MAPI public folder hierarchy. When you try to create additional public folder stores in the MAPI hierarchy, you receive the following error:

All the public folder trees already have an associated public store on this server. You will need to create a new public folder tree before creating this new public store.
answered by DESIDBA

Related questions



If this page has HELPED you somehow then do

You can also join me here to get daily SQL Server Tutorial / NEWS

Join me on TWITTER Join me on FACEBOOK Join me on LinkedINGet UPDATES via XML Feed Get Updates via Email