VerbalKint04
Technical User
We've already got the two node cluster in place and are using NSI's GeoCluster to help manage the cluster resources.
This past weekend something happened that caused Exchange not to respond to network requests. All of the services were running on the server, but I couldn't get into my mailbox! Obviously this isn't a system that we want to move to until I can figure out what was going on. I'm hoping that someone will be able to help out. Here's the nasty details:
SYMPTOMS:
The exact error (not really an error, but dialog box) was the "Waiting for response" window that comes up when your computer is trying to talk to the Exchange server but it isn't responding to requests right away. The odd thing was, I could see my folder list, and that I did in fact have new messages, but when I tried to view the contents of the folder, nothing was available.
POSSIBLE CAUSES?
One of the arbitration paths has been acting squirly for about a week now, but I would hate to believe that if an arbitration path goes down it would cause the cluster to become unstable (arbitration paths are paths that the cluster uses to verify that if it can't talk with a server, it checks to see if that server is down, or if the cluster is down (which would initiate a failover))
ANOTHER POSSIBLE CAUSE:
Our server that acts as the intermediary between Exchange 5.5 and the AD had all of it's MS Exchange services stopped for some reason. I checked the event logs but was unable to see when the services actually stopped (must have happened before 5/26/2003, or it wasn't logged at all.)
Again, the really odd thing from all of this is that nothing happened this weekend. The problem resolved itself once I rebooted the active node and had the system failover to the passive node, which I then failed back to the other node once it booted up. Exchange works on both servers, but for some reason it just didn't make it through the weekend and I have no errors to go off of!
If anyone has any idea about a possible cause to the situation please let me know.
This past weekend something happened that caused Exchange not to respond to network requests. All of the services were running on the server, but I couldn't get into my mailbox! Obviously this isn't a system that we want to move to until I can figure out what was going on. I'm hoping that someone will be able to help out. Here's the nasty details:
SYMPTOMS:
The exact error (not really an error, but dialog box) was the "Waiting for response" window that comes up when your computer is trying to talk to the Exchange server but it isn't responding to requests right away. The odd thing was, I could see my folder list, and that I did in fact have new messages, but when I tried to view the contents of the folder, nothing was available.
POSSIBLE CAUSES?
One of the arbitration paths has been acting squirly for about a week now, but I would hate to believe that if an arbitration path goes down it would cause the cluster to become unstable (arbitration paths are paths that the cluster uses to verify that if it can't talk with a server, it checks to see if that server is down, or if the cluster is down (which would initiate a failover))
ANOTHER POSSIBLE CAUSE:
Our server that acts as the intermediary between Exchange 5.5 and the AD had all of it's MS Exchange services stopped for some reason. I checked the event logs but was unable to see when the services actually stopped (must have happened before 5/26/2003, or it wasn't logged at all.)
Again, the really odd thing from all of this is that nothing happened this weekend. The problem resolved itself once I rebooted the active node and had the system failover to the passive node, which I then failed back to the other node once it booted up. Exchange works on both servers, but for some reason it just didn't make it through the weekend and I have no errors to go off of!
If anyone has any idea about a possible cause to the situation please let me know.
