Re: Event ID 1123 and 1122
- From: Jay <Jay@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 26 Nov 2007 08:44:14 -0800
Eric - If you go back a couple of pages to a question I posted titled "Proper
NIC Config?" you'll see that I had the same exact problem. In my case,
hard-coding the NIC speed and duplex (even though it was a nwere 1GB NIC)
eliminated the errors.
"Sabo, Eric" wrote:
Still nothing....
Should I measure the DPC of the NIC?
So from what you are saying I should adjust the settings on the heartbeat
via the command line.
Are there any post sp2 cluster patches that might help?
"Chuck [MSFT]" <ctimon@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eTjBL2DMIHA.5328@xxxxxxxxxxxxxxxxxxxxxxx
You can run SCC and still take advantage of the new settings without suing
a FSW
DPC = Deferred Procedure Call
http://www.microsoft.com/whdc/Driver/tips/DPC_ISR.mspx
--
Chuck Timon, Jr.
Microsoft Corporation
Windows Server 2008 Readiness Team
This posting is provided 'AS IS" with no warranties, and confers no
rights.
"Sabo, Eric" <sabo_e@xxxxxxx> wrote in message
news:eGjMcfBMIHA.4740@xxxxxxxxxxxxxxxxxxxxxxx
Chuck,
I don't think that article applies, we are running SCC.
Clussvc.exe is at 5.2.3790.3959 if this helps at all.
Yes, I have been troubleshooting these events ever since we installed
this cluster.
What do you mean by DPC ?
Thanks for all your help on this issue.
"Chuck [MSFT]" <ctimon@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eoVeA64LIHA.484@xxxxxxxxxxxxxxxxxxxxxxx
The failover only occurs when there is a 'true' failure....so, if you
went through the article how did you investigate the DPC issues? Those
are the trickiest to, first, find, and then address. With a new hot fix
designed specifically for Exchange 2007 CCR, you can actually tune some
parameters now that will help alleviate the 1123 errors =
http://support.microsoft.com/kb/921181/
--
Chuck Timon, Jr.
Microsoft Corporation
Windows Server 2008 Readiness Team
This posting is provided 'AS IS" with no warranties, and confers no
rights.
"Sabo, Eric" <sabo_e@xxxxxxx> wrote in message
news:e$4KWB3LIHA.2208@xxxxxxxxxxxxxxxxxxxxxxx
Chuck,
Any other articles, unfortunately I went through each and every step
describe in the article and still haven't been able to get rid of the
1123 and 1122 events.
I am at a lost on this issue.
So far the cluster resources haven't failed over.
"Chuck [MSFT]" <ctimon@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23LB5zBiLIHA.4228@xxxxxxxxxxxxxxxxxxxxxxx
http://support.microsoft.com/default.aspx?scid=kb;en-us;892422
--
Chuck Timon, Jr.
Microsoft Corporation
Windows Server 2008 Readiness Team
This posting is provided 'AS IS" with no warranties, and confers no
rights.
"Sabo, Eric" <sabo_e@xxxxxxx> wrote in message
news:ui7obxeLIHA.5244@xxxxxxxxxxxxxxxxxxxxxxx
I need some opinions on how to correct getting Event ID 1123 and Event
ID 1122 on all cluster nodes every hour. This is a three node
cluster running Windows 2003 SP2 - Exchange 2007 Update # 4.
I went through all best practices and nothing really stands out as a
misconfiguration on any of the nodes. Installed the latest network
drivers for the network cards.
The cluster hasn't been affected by this yet.
Looking for suggestions on this issue.
Thanks in Advance!
Eric Sabo
- Follow-Ups:
- Re: Event ID 1123 and 1122
- From: Sabo, Eric
- Re: Event ID 1123 and 1122
- References:
- Event ID 1123 and 1122
- From: Sabo, Eric
- Re: Event ID 1123 and 1122
- From: Chuck [MSFT]
- Re: Event ID 1123 and 1122
- From: Sabo, Eric
- Re: Event ID 1123 and 1122
- From: Chuck [MSFT]
- Re: Event ID 1123 and 1122
- From: Sabo, Eric
- Re: Event ID 1123 and 1122
- From: Chuck [MSFT]
- Re: Event ID 1123 and 1122
- From: Sabo, Eric
- Event ID 1123 and 1122
- Prev by Date: Re: Event ID 1123 and 1122
- Next by Date: Re: Event ID 1123 and 1122
- Previous by thread: Re: Event ID 1123 and 1122
- Next by thread: Re: Event ID 1123 and 1122
- Index(es):
Relevant Pages
|