Re: Exchange 2003 Cluster Problem

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi Rodney.
Hope you are Fine.I want to know what is the possibility and risk involved
in rebuilding the Node 1.Can i reinstall the exchange 2003 on Node1 without
reinstalling the Operating System.Is there any documentation how to rebuild
the Node 1 in Exchange 2003 Cluster.
Thanks and Regards
Fasahat.



"Rodney R. Fournier [MVP]" wrote:

> %systemroot%\Cluster for the Cluster.log file. It should provide clues as to
> what is wrong. Next, if this is truly urgent, call PSS.
>
> Cheers,
>
> Rod
>
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
>
> "Fasahat" <Fasahat@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:2F853379-B1DE-44D9-9D70-2CB6D4AF54BB@xxxxxxxxxxxxxxxx
> > Hi Rodney
> > I have not changed anything on Node1.There are no service packs installed
> > for WIndows 2003 Server.Exchange 2003 has Service pack installed.Both the
> > Nodes were working fine.This issue suddenly came up.I cannot see any
> > errors
> > in the Event Log.Where can i check the Cluster Logs.
> > I can ping the Heartbeat connection between the two nodes.
> > Only thing is once i failback to Node 1,Users cannot open thier
> > Outlook,neither can i ping to Exchange MSDTC Virtual IP or the Name.
> > I know it is not a good idea to shut down Node1 but that is the only
> > option
> > left till i find a solution.I haven,t turned on the Firewall.
> > I have two groups in the cluster
> > Windows cluster grouip
> > Exchange group having the resources fro Exchange 2003 Server.
> > The Network stack has two connections
> > Private and Public
> > I can ping to the Private IP of Node 2 from Node 1
> > I can ping to the Public IP of Node 2 from Node 1.
> > Both the Nodes are pointing to internal DNS.
> > I don,t why it is happening.
> > need help urgently
> > Regards
> > Fasahat
> >
> >
> > "Rodney R. Fournier [MVP]" wrote:
> >
> >> So what has changed on Node1? Did you install SP1 and turn on the
> >> firewall?
> >> Was it patched? Did it ever work? What do the Cluster.log and Event logs
> >> tell you?
> >>
> >> Shutting down the node is probably not the best idea. How many Groups do
> >> you
> >> have in your cluster? What service pack(s) are you running for the OS and
> >> Exchange? What does the network stack look like on Node1? I simply need
> >> more
> >> information.
> >>
> >> Cheers,
> >>
> >> Rod
> >>
> >> MVP - Windows Server - Clustering
> >> http://www.nw-america.com - Clustering Website
> >> http://www.msmvps.com/clustering - Blog
> >> http://www.clusterhelp.com - Cluster Training
> >>
> >>
> >> "Fasahat" <Fasahat@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:AACA2B39-36CD-4C78-B493-3EA3C27E7BBD@xxxxxxxxxxxxxxxx
> >> > Hi Friends
> >> > I have an Exchange 2003 Cluster configured on Windows 2003 Server
> >> > Opearting
> >> > System.My exchange was working fine before two days.I suddenly got a
> >> > problem.Users cannot access the Exchange Cluster if the exchange
> >> > resourecs
> >> > are on Node1.i cannot ping to the Exchange cluster Virtual name neither
> >> > the
> >> > exchange MSTDC IP Address.I can ping the windows Cluster.The Cluster
> >> > failover
> >> > and failback is working.There are no errors in theEvent Log.
> >> > Once i failover to NODE 2 users can access the exchange cluster and
> >> > send
> >> > and
> >> > recieve mails.i can ping the exchange virtula IP Address.
> >> > If i failback to NODE1 the problem arises.
> >> > I have shut down the Node 1 and all the resources are on NODE2.
> >> > I tried to search Microsoft knowledge base,couldnt find the right
> >> > solution.
> >> > PLease Advice.
> >> > Regards
> >> > fasahat
> >> > --
> >> >
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: Exchange 2007 SP1 Standard Edition - SCR on a Windows 2003 Clu
    ... Mailbox roles and manually start Exchange ... services in case a windows cluster fail-over occurs (Windows cluster active ... active node as an SCR source and the passive node as an SCR target? ... the windows cluster so that they don't have to change Exchange server IP/name ...
    (microsoft.public.exchange.setup)
  • Re: Exch 2003 SP2 - applied on one node, but cant move resources
    ... resources to Node2, the failover did not complete because 'system attendant' ... Virtual Exchange server and failover occurred normally again upon taking ... cluster resources oline. ...
    (microsoft.public.exchange.admin)
  • Exchange 2007 cluster install - interesting note on an SCC installation
    ... I got my client/hub server setup just fine, and then when I went to my ... the install was going smoothly but then I noticed in the cluster ... I was using during the Exchange install was 10.40.32.170. ...
    (microsoft.public.exchange.setup)
  • Re: Comparaison on Exchange 2003 Clustering and Exchange 2007 SP1 SCR
    ... In terms of Exchange 2007 cluster solutions, CCR will typically always be preferred over SCC. ... If you need a zero data loss solution, then your choice would be to use SCC and third-party replication. ... The goal is to have DB, Server and site resiliency...They have under 1000 users, running single Exchange 2003 Server. ... The equivalent of Exchange Server 2003's clustering model is Exchange Server 2007's Single Copy Cluster. ...
    (microsoft.public.exchange.design)
  • Exchange 2003 Setup Error: 0xC1037989
    ... We finally managed to get the Exchange Server 2003 setup ... the DTC resource for the cluster during setup. ... I m Exchange 2003 on Windows ...
    (microsoft.public.exchange.setup)