Re: Cluster service, network name takes long time to start/fail

Check the event logs to see if the resource is failing before starting.
Otherwise, check the cluster.log for hints. Cluster logs are located in
c:\windows\cluster\cluster.log.

Regards,
John

"Björn" <Bjrn@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9A07F30F-8179-4D6A-B72C-B48347495BBB@xxxxxxxxxxxxxxxx
> Hi
>
> we have a new Cluster for Exchagne and it works fine but..
> the Resourse Network Name takes about 2 min to start/"restart".
> and i am realy new to cluster, were do i start looking for errors.
> Network IP startes in about 5 sec.
> and all the outher resoures starts fine.


.

Relevant Pages

  • Re: Cluster Failover history
    ... Assuming 2003 cluster, you can look at the event logs on the cluster nodes. ... 1069 - Generic error, means cluster resource failed. ... notification when a failover occurs. ...
    (microsoft.public.windows.server.clustering)
  • Re: Improper share removal
    ... If a user attempts to remove a shar via explorer and they have the ... The cluster service will ... Assuming that you have the default values set, this resource would ... John ...
    (microsoft.public.windows.server.clustering)
  • Re: Share goes away when failover happens
    ... > Here's the article Toby was referring to: ... >> have access to my cluster at the moment). ... You need to create a resource ...
    (microsoft.public.windows.server.clustering)
  • RE: SQL Server Cluster and MSDTC
    ... Microsoft only supports running MSDTC on cluster nodes as a clustered ... Using MSDTC as a non-clustered resource on a Windows cluster is ... DD - SQL server 2005 ...
    (microsoft.public.sqlserver.clustering)
  • Re: Fulltext failure on a 2 node cluster
    ... No cluster resource for that cluster has shown as failed. ... There are NO error messages in SQL Server or the event log. ... Server full-text search resource online: ...
    (microsoft.public.sqlserver.clustering)