| Author |
Message |
Kerrie
Guest
|
 Posted:
Wed Jan 12, 2005 12:33 am Post subject:
Incoming queue full? |
|
|
Hello, I have a small test system with a MOM Server, 2 DCs - one of which
(the one that holds all the FSMOs) also has SMS on it. That particular DC
has started getting errors that its queue is full. I can ping it with no
problems..
The event is 21268.
Anyone encounter this or get past it? |
|
| Back to top |
|
 |
James Morey
Guest
|
| Posted:
Wed Jan 12, 2005 12:51 am Post subject:
Re: Incoming queue full? |
|
|
Kerrie,
You might want to start with the MOM Operator console. Look for the "The
agent incoming queue is full" alert for that computer and select it. In the
middle pane (Results pane) on the bottom there should be a tab called
"Product Knowledge". Select this and you will get some troubleshooting help
for that alert.
let us know if this does not help.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:uNiSXwA%23EHA.2984@TK2MSFTNGP09.phx.gbl...
| Quote: | Hello, I have a small test system with a MOM Server, 2 DCs - one of which
(the one that holds all the FSMOs) also has SMS on it. That particular DC
has started getting errors that its queue is full. I can ping it with no
problems..
The event is 21268.
Anyone encounter this or get past it?
|
|
|
| Back to top |
|
|
Kerrie
Guest
|
| Posted:
Wed Jan 12, 2005 2:23 am Post subject:
Re: Incoming queue full? |
|
|
Hi James,
Actually I did go through the KB prior to posting this message. :)
The Managment Server is up
The network connection is up
The management server is not pegged (performance)
The Management Server is running - no events 21209 or 21285.
Good response time on a ping.
The agent was pushed out - as a MOM 2005 agent. MOM 2000 was not previously
in this environment.
If it can't authenticate, I'm not seeing other evidence of that. No Agent
connection refused messages.
??
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:%23FSoM6A%23EHA.600@TK2MSFTNGP09.phx.gbl...
| Quote: | Kerrie,
You might want to start with the MOM Operator console. Look for the "The
agent incoming queue is full" alert for that computer and select it. In
the middle pane (Results pane) on the bottom there should be a tab called
"Product Knowledge". Select this and you will get some troubleshooting
help for that alert.
let us know if this does not help.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:uNiSXwA%23EHA.2984@TK2MSFTNGP09.phx.gbl...
Hello, I have a small test system with a MOM Server, 2 DCs - one of which
(the one that holds all the FSMOs) also has SMS on it. That particular DC
has started getting errors that its queue is full. I can ping it with no
problems..
The event is 21268.
Anyone encounter this or get past it?
|
|
|
| Back to top |
|
|
James Morey
Guest
|
| Posted:
Wed Jan 12, 2005 2:49 am Post subject:
Re: Incoming queue full? |
|
|
I've seen it a few times here and would really like to know myself. In
general, this alert means that the information is coming in too fast for the
agent to process it and send it up to the Management Server.
What MPs do you have imported and targeted at this agent? Does the agent
machine show any resource shortages?
This is the stumper of the week, I think. I'll look into this one and get
back as soon as I find anything.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:easjetB%23EHA.208@TK2MSFTNGP12.phx.gbl...
| Quote: | Hi James,
Actually I did go through the KB prior to posting this message. :)
The Managment Server is up
The network connection is up
The management server is not pegged (performance)
The Management Server is running - no events 21209 or 21285.
Good response time on a ping.
The agent was pushed out - as a MOM 2005 agent. MOM 2000 was not
previously in this environment.
If it can't authenticate, I'm not seeing other evidence of that. No Agent
connection refused messages.
??
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:%23FSoM6A%23EHA.600@TK2MSFTNGP09.phx.gbl...
Kerrie,
You might want to start with the MOM Operator console. Look for the "The
agent incoming queue is full" alert for that computer and select it. In
the middle pane (Results pane) on the bottom there should be a tab called
"Product Knowledge". Select this and you will get some troubleshooting
help for that alert.
let us know if this does not help.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers
no rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:uNiSXwA%23EHA.2984@TK2MSFTNGP09.phx.gbl...
Hello, I have a small test system with a MOM Server, 2 DCs - one of
which (the one that holds all the FSMOs) also has SMS on it. That
particular DC has started getting errors that its queue is full. I can
ping it with no problems..
The event is 21268.
Anyone encounter this or get past it?
|
|
|
| Back to top |
|
|
Kerrie
Guest
|
| Posted:
Wed Jan 12, 2005 3:21 am Post subject:
Re: Incoming queue full? |
|
|
Environment:
Test system, combination of VPC guests and regular machines. Connected via a
router, private network.
The agent machine is a DC running SMS. And that says a lot. It holds all the
FSMO roles, is a GC, has DNS, SMS primary site server, with SQL 2000, SRS
for the SMS reports so VS.NET, running Windows Server 2003.
The VPC host has only 1 GB RAM, so while the guest is at least the only
guest on this machine, its pretty busy. CPU shows processor hikes, but it is
not paging. It has been spawning all sorts of errors from various MP scripts
not getting a decent response, AD replication occuring slowly ...
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:e8PV78B%23EHA.3840@tk2msftngp13.phx.gbl...
| Quote: | I've seen it a few times here and would really like to know myself. In
general, this alert means that the information is coming in too fast for
the agent to process it and send it up to the Management Server.
What MPs do you have imported and targeted at this agent? Does the agent
machine show any resource shortages?
This is the stumper of the week, I think. I'll look into this one and get
back as soon as I find anything.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:easjetB%23EHA.208@TK2MSFTNGP12.phx.gbl...
Hi James,
Actually I did go through the KB prior to posting this message. :)
The Managment Server is up
The network connection is up
The management server is not pegged (performance)
The Management Server is running - no events 21209 or 21285.
Good response time on a ping.
The agent was pushed out - as a MOM 2005 agent. MOM 2000 was not
previously in this environment.
If it can't authenticate, I'm not seeing other evidence of that. No Agent
connection refused messages.
??
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:%23FSoM6A%23EHA.600@TK2MSFTNGP09.phx.gbl...
Kerrie,
You might want to start with the MOM Operator console. Look for the "The
agent incoming queue is full" alert for that computer and select it. In
the middle pane (Results pane) on the bottom there should be a tab
called "Product Knowledge". Select this and you will get some
troubleshooting help for that alert.
let us know if this does not help.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers
no rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:uNiSXwA%23EHA.2984@TK2MSFTNGP09.phx.gbl...
Hello, I have a small test system with a MOM Server, 2 DCs - one of
which (the one that holds all the FSMOs) also has SMS on it. That
particular DC has started getting errors that its queue is full. I can
ping it with no problems..
The event is 21268.
Anyone encounter this or get past it?
|
|
|
| Back to top |
|
|
James Morey
Guest
|
| Posted:
Wed Jan 12, 2005 5:12 am Post subject:
Re: Incoming queue full? |
|
|
I am tempted to say that, under these circumstances, the poor agent can't
keep up. Did increasing the agent cache seem to help? Or did it just fill up
again?
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:OJTt9NC%23EHA.1564@TK2MSFTNGP09.phx.gbl...
| Quote: | Environment:
Test system, combination of VPC guests and regular machines. Connected via
a router, private network.
The agent machine is a DC running SMS. And that says a lot. It holds all
the FSMO roles, is a GC, has DNS, SMS primary site server, with SQL 2000,
SRS for the SMS reports so VS.NET, running Windows Server 2003.
The VPC host has only 1 GB RAM, so while the guest is at least the only
guest on this machine, its pretty busy. CPU shows processor hikes, but it
is not paging. It has been spawning all sorts of errors from various MP
scripts not getting a decent response, AD replication occuring slowly ...
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:e8PV78B%23EHA.3840@tk2msftngp13.phx.gbl...
I've seen it a few times here and would really like to know myself. In
general, this alert means that the information is coming in too fast for
the agent to process it and send it up to the Management Server.
What MPs do you have imported and targeted at this agent? Does the agent
machine show any resource shortages?
This is the stumper of the week, I think. I'll look into this one and get
back as soon as I find anything.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers
no rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:easjetB%23EHA.208@TK2MSFTNGP12.phx.gbl...
Hi James,
Actually I did go through the KB prior to posting this message. :)
The Managment Server is up
The network connection is up
The management server is not pegged (performance)
The Management Server is running - no events 21209 or 21285.
Good response time on a ping.
The agent was pushed out - as a MOM 2005 agent. MOM 2000 was not
previously in this environment.
If it can't authenticate, I'm not seeing other evidence of that. No
Agent connection refused messages.
??
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:%23FSoM6A%23EHA.600@TK2MSFTNGP09.phx.gbl...
Kerrie,
You might want to start with the MOM Operator console. Look for the
"The agent incoming queue is full" alert for that computer and select
it. In the middle pane (Results pane) on the bottom there should be a
tab called "Product Knowledge". Select this and you will get some
troubleshooting help for that alert.
let us know if this does not help.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers
no rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:uNiSXwA%23EHA.2984@TK2MSFTNGP09.phx.gbl...
Hello, I have a small test system with a MOM Server, 2 DCs - one of
which (the one that holds all the FSMOs) also has SMS on it. That
particular DC has started getting errors that its queue is full. I can
ping it with no problems..
The event is 21268.
Anyone encounter this or get past it?
|
|
|
| Back to top |
|
|
Kerrie
Guest
|
| Posted:
Wed Jan 12, 2005 9:13 am Post subject:
Re: Incoming queue full? |
|
|
Of course it filled up again :)
We are doing some reconfiguration now to separate the DC and SMS to 2
servers- on 2 physical machines. Although the DC didn't do much processing
since it wasn't a very active network (except for all those MP scripts
bombing), we'll see if that makes any difference. If nothing else, it may
reduce memory restraints - although the system was not paging, I suspect
there was such a bottleneck in the processor nothing ever got to memory.
So if one or both of the machines continues to have its queue fill up, that
may not have been the cause. We'll see.
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:u9MlIMD%23EHA.208@TK2MSFTNGP12.phx.gbl...
| Quote: | I am tempted to say that, under these circumstances, the poor agent can't
keep up. Did increasing the agent cache seem to help? Or did it just fill
up again?
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:OJTt9NC%23EHA.1564@TK2MSFTNGP09.phx.gbl...
Environment:
Test system, combination of VPC guests and regular machines. Connected
via a router, private network.
The agent machine is a DC running SMS. And that says a lot. It holds all
the FSMO roles, is a GC, has DNS, SMS primary site server, with SQL 2000,
SRS for the SMS reports so VS.NET, running Windows Server 2003.
The VPC host has only 1 GB RAM, so while the guest is at least the only
guest on this machine, its pretty busy. CPU shows processor hikes, but it
is not paging. It has been spawning all sorts of errors from various MP
scripts not getting a decent response, AD replication occuring slowly ...
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:e8PV78B%23EHA.3840@tk2msftngp13.phx.gbl...
I've seen it a few times here and would really like to know myself. In
general, this alert means that the information is coming in too fast for
the agent to process it and send it up to the Management Server.
What MPs do you have imported and targeted at this agent? Does the agent
machine show any resource shortages?
This is the stumper of the week, I think. I'll look into this one and
get back as soon as I find anything.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers
no rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:easjetB%23EHA.208@TK2MSFTNGP12.phx.gbl...
Hi James,
Actually I did go through the KB prior to posting this message. :)
The Managment Server is up
The network connection is up
The management server is not pegged (performance)
The Management Server is running - no events 21209 or 21285.
Good response time on a ping.
The agent was pushed out - as a MOM 2005 agent. MOM 2000 was not
previously in this environment.
If it can't authenticate, I'm not seeing other evidence of that. No
Agent connection refused messages.
??
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:%23FSoM6A%23EHA.600@TK2MSFTNGP09.phx.gbl...
Kerrie,
You might want to start with the MOM Operator console. Look for the
"The agent incoming queue is full" alert for that computer and select
it. In the middle pane (Results pane) on the bottom there should be a
tab called "Product Knowledge". Select this and you will get some
troubleshooting help for that alert.
let us know if this does not help.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and
confers no rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:uNiSXwA%23EHA.2984@TK2MSFTNGP09.phx.gbl...
Hello, I have a small test system with a MOM Server, 2 DCs - one of
which (the one that holds all the FSMOs) also has SMS on it. That
particular DC has started getting errors that its queue is full. I
can ping it with no problems..
The event is 21268.
Anyone encounter this or get past it?
|
|
|
| Back to top |
|
|
James Morey
Guest
|
| Posted:
Thu Jan 13, 2005 2:19 am Post subject:
Re: Incoming queue full? |
|
|
Well, thank for being a trailblazer on this one. I'm curious about how your
changes will affect the agent queue issue. I'll keep looking into it from my
side.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:ubVqFTF%23EHA.3700@tk2msftngp13.phx.gbl...
| Quote: | Of course it filled up again :)
We are doing some reconfiguration now to separate the DC and SMS to 2
servers- on 2 physical machines. Although the DC didn't do much processing
since it wasn't a very active network (except for all those MP scripts
bombing), we'll see if that makes any difference. If nothing else, it may
reduce memory restraints - although the system was not paging, I suspect
there was such a bottleneck in the processor nothing ever got to memory.
So if one or both of the machines continues to have its queue fill up,
that may not have been the cause. We'll see.
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:u9MlIMD%23EHA.208@TK2MSFTNGP12.phx.gbl...
I am tempted to say that, under these circumstances, the poor agent can't
keep up. Did increasing the agent cache seem to help? Or did it just fill
up again?
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers
no rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:OJTt9NC%23EHA.1564@TK2MSFTNGP09.phx.gbl...
Environment:
Test system, combination of VPC guests and regular machines. Connected
via a router, private network.
The agent machine is a DC running SMS. And that says a lot. It holds all
the FSMO roles, is a GC, has DNS, SMS primary site server, with SQL
2000, SRS for the SMS reports so VS.NET, running Windows Server 2003.
The VPC host has only 1 GB RAM, so while the guest is at least the only
guest on this machine, its pretty busy. CPU shows processor hikes, but
it is not paging. It has been spawning all sorts of errors from various
MP scripts not getting a decent response, AD replication occuring slowly
...
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:e8PV78B%23EHA.3840@tk2msftngp13.phx.gbl...
I've seen it a few times here and would really like to know myself. In
general, this alert means that the information is coming in too fast
for the agent to process it and send it up to the Management Server.
What MPs do you have imported and targeted at this agent? Does the
agent machine show any resource shortages?
This is the stumper of the week, I think. I'll look into this one and
get back as soon as I find anything.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers
no rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:easjetB%23EHA.208@TK2MSFTNGP12.phx.gbl...
Hi James,
Actually I did go through the KB prior to posting this message. :)
The Managment Server is up
The network connection is up
The management server is not pegged (performance)
The Management Server is running - no events 21209 or 21285.
Good response time on a ping.
The agent was pushed out - as a MOM 2005 agent. MOM 2000 was not
previously in this environment.
If it can't authenticate, I'm not seeing other evidence of that. No
Agent connection refused messages.
??
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:%23FSoM6A%23EHA.600@TK2MSFTNGP09.phx.gbl...
Kerrie,
You might want to start with the MOM Operator console. Look for the
"The agent incoming queue is full" alert for that computer and select
it. In the middle pane (Results pane) on the bottom there should be a
tab called "Product Knowledge". Select this and you will get some
troubleshooting help for that alert.
let us know if this does not help.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and
confers no rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:uNiSXwA%23EHA.2984@TK2MSFTNGP09.phx.gbl...
Hello, I have a small test system with a MOM Server, 2 DCs - one of
which (the one that holds all the FSMOs) also has SMS on it. That
particular DC has started getting errors that its queue is full. I
can ping it with no problems..
The event is 21268.
Anyone encounter this or get past it?
|
|
|
| Back to top |
|
|
Kerrie
Guest
|
| Posted:
Thu Jan 13, 2005 10:11 am Post subject:
Re: Incoming queue full? |
|
|
Of course today I got an error that the OUTGOING agent queue was full - this
is a different machine, of course. This is the other DC which has nothing
else going on it ... DNS, AD replication (remember, the very small
environment), and it is a SMS client. This particular machine is normally
very well behaved, doesn't have a whole lot of errors on it or scripts
timing out, etc.
Now as I understand it (based on the KB information associated with the
error) is that the outgoing queue is coming from the managed client to the
Management Server.
That would mean that the incoming queue (the one we started this thread on)
is from the Management Server to the client - so I'm a bit confused as to
how scripts erroring on the client would have caused the incoming queue to
be full (our prior hypothesis); I would have thought that would flood the
outgoing queue instead.
On the (new) SMS Server, I did get a number of errors from the SMS EXECUTIVE
saying it had stopped - although it never showed as stopped on the server
itself. No full queue messages however.
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:%23PFbLQO%23EHA.2700@TK2MSFTNGP14.phx.gbl...
| Quote: | Well, thank for being a trailblazer on this one. I'm curious about how
your changes will affect the agent queue issue. I'll keep looking into it
from my side.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers no
rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:ubVqFTF%23EHA.3700@tk2msftngp13.phx.gbl...
Of course it filled up again :)
We are doing some reconfiguration now to separate the DC and SMS to 2
servers- on 2 physical machines. Although the DC didn't do much
processing since it wasn't a very active network (except for all those MP
scripts bombing), we'll see if that makes any difference. If nothing
else, it may reduce memory restraints - although the system was not
paging, I suspect there was such a bottleneck in the processor nothing
ever got to memory.
So if one or both of the machines continues to have its queue fill up,
that may not have been the cause. We'll see.
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:u9MlIMD%23EHA.208@TK2MSFTNGP12.phx.gbl...
I am tempted to say that, under these circumstances, the poor agent can't
keep up. Did increasing the agent cache seem to help? Or did it just fill
up again?
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and confers
no rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:OJTt9NC%23EHA.1564@TK2MSFTNGP09.phx.gbl...
Environment:
Test system, combination of VPC guests and regular machines. Connected
via a router, private network.
The agent machine is a DC running SMS. And that says a lot. It holds
all the FSMO roles, is a GC, has DNS, SMS primary site server, with SQL
2000, SRS for the SMS reports so VS.NET, running Windows Server 2003.
The VPC host has only 1 GB RAM, so while the guest is at least the only
guest on this machine, its pretty busy. CPU shows processor hikes, but
it is not paging. It has been spawning all sorts of errors from various
MP scripts not getting a decent response, AD replication occuring
slowly ...
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:e8PV78B%23EHA.3840@tk2msftngp13.phx.gbl...
I've seen it a few times here and would really like to know myself. In
general, this alert means that the information is coming in too fast
for the agent to process it and send it up to the Management Server.
What MPs do you have imported and targeted at this agent? Does the
agent machine show any resource shortages?
This is the stumper of the week, I think. I'll look into this one and
get back as soon as I find anything.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and
confers no rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:easjetB%23EHA.208@TK2MSFTNGP12.phx.gbl...
Hi James,
Actually I did go through the KB prior to posting this message. :)
The Managment Server is up
The network connection is up
The management server is not pegged (performance)
The Management Server is running - no events 21209 or 21285.
Good response time on a ping.
The agent was pushed out - as a MOM 2005 agent. MOM 2000 was not
previously in this environment.
If it can't authenticate, I'm not seeing other evidence of that. No
Agent connection refused messages.
??
"James Morey" <jmorey@online.microsoft.com> wrote in message
news:%23FSoM6A%23EHA.600@TK2MSFTNGP09.phx.gbl...
Kerrie,
You might want to start with the MOM Operator console. Look for the
"The agent incoming queue is full" alert for that computer and
select it. In the middle pane (Results pane) on the bottom there
should be a tab called "Product Knowledge". Select this and you will
get some troubleshooting help for that alert.
let us know if this does not help.
--
=====================
NOTE - This posting is provided "AS IS" with no warranties, and
confers no rights.
James Morey | Microsoft | Windows & Enterprise Management Division
=====================
"Kerrie" <kerrieL@comcast.net> wrote in message
news:uNiSXwA%23EHA.2984@TK2MSFTNGP09.phx.gbl...
Hello, I have a small test system with a MOM Server, 2 DCs - one of
which (the one that holds all the FSMOs) also has SMS on it. That
particular DC has started getting errors that its queue is full. I
can ping it with no problems..
The event is 21268.
Anyone encounter this or get past it?
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in