Hi,I am trying to setup IMAP4 on Exchange 2003 that is active/passsive cluster. I have set the IMAP4 service to manual on each of my servers. I have setup an IMAP server resource in Cluster Admin. I can bring the resource online in Cluster Admin but when I go ESM to stop the IMAP4 virtual server it tells me "Add a clusterresource for this virtual server in order to start, stop, or pause it". I am also getting a couple of errors in the event viewer: Event Type:ErrorEvent Source:ClusSvcEvent Category:Failover Mgr Event ID:1069Date:11/26/2007Time:11:49:53 AMUser:N/AComputer:PAC-EXCH-01Description:Cluster resource 'Exchange IMAP4 Server Instance' in Resource Group 'Exchange' failed. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type:ErrorEvent Source:MSExchangeClusterEvent Category:Services Event ID:1005Date:11/26/2007Time:11:49:53 AMUser:N/AComputer:PAC-EXCH-01Description:Exchange IMAP4 Server Instance: The IsAlive check for this resource failed. For more information, click http://www.microsoft.com/contentredirect.asp.Data:0000: 26 04 00 00 &... Does anyone have any ideas on what I need to do to fix this? Thanks. Michael

I've run into this before. Try starting IMAP on the active node withservices(i know your not supposed to, but it worked for me), then bring it online with cluster admin.

Thanks for the suggestion. I tried what you suggested but I am still having the same issue. The system event viewer is still telling me "Cluster resource 'Exchange IMAP4 Server Instance' in Resource Group 'Exchange' failed." I configured everything per what I read on the Technet website but I am still at a loss as why this is happening. Michael

What do you have in cluster.log ?

In the log it shows that its waiting for the IMAP4SVC to start, then it shows that it is waiting for service 'IMAP4SVC' to reach one of these states: stopped; running; paused, then it shows that the current state it running. Is there anything specific I should be looking for?

It should give you a few lines about why a resource woudl fail to come online, usually offers much more granular detail than event viewer.

I don't see anything that looks like an error really. I do see this though, DwGetIsAliveMaxRetries: IsAliveMaxRetries not set, using default value: 4

that shouldn't be an issue, but if the resource is failing to come online, the word 'fail' should be all over cluster.log maybe its over-written itself. Try bringing it online again and re-check the log file.