Exchange Emails - Pending
-
What I meant to say, is I went through the list in that link you sent. But Exchange 2013 all start with 15.x
-
@BBigford said:
@brianlittlejohn The build is 516.32, how do you decipher your service pack from that?
You are on the RTM version. There is a SP and several CU updates since then.
-
@brianlittlejohn said:
@BBigford said:
@brianlittlejohn The build is 516.32, how do you decipher your service pack from that?
You are on the RTM version. There is a SP and several CU updates since then.
How were you able to find out it is RTM?
On another note. I removed every user but me and the secretary... Meeting notice delivered just fine. Which means there is a problematic user, even though I checked each one and they are all current employees and accounts are all fine.
-
@BBigford
Last Line in 2013 TableRelease to Manufacturing (RTM) version of Exchange Server 2013
December 3, 2012
15.00.0516.032 -
@brianlittlejohn said:
@BBigford
Last Line in 2013 TableRelease to Manufacturing (RTM) version of Exchange Server 2013
December 3, 2012
15.00.0516.032
Oh, I overlooked the last of the numbers. My fault. I was only looking at the first of them. -
@BBigford said:
@brianlittlejohn said:
@BBigford said:
@brianlittlejohn The build is 516.32, how do you decipher your service pack from that?
You are on the RTM version. There is a SP and several CU updates since then.
How were you able to find out it is RTM?
On another note. I removed every user but me and the secretary... Meeting notice delivered just fine. Which means there is a problematic user, even though I checked each one and they are all current employees and accounts are all fine.
How many users were in it? It does seem like one of your user mailbox's may be causing your issue.
-
@brianlittlejohn said:
@BBigford said:
@brianlittlejohn said:
@BBigford said:
@brianlittlejohn The build is 516.32, how do you decipher your service pack from that?
You are on the RTM version. There is a SP and several CU updates since then.
How were you able to find out it is RTM?
On another note. I removed every user but me and the secretary... Meeting notice delivered just fine. Which means there is a problematic user, even though I checked each one and they are all current employees and accounts are all fine.
How many users were in it? It does seem like one of your user mailbox's may be causing your issue.
Does anyone have a full mailbox that can't accept any new messages?
-
@brianlittlejohn said:
@BBigford said:
@brianlittlejohn said:
@BBigford said:
@brianlittlejohn The build is 516.32, how do you decipher your service pack from that?
You are on the RTM version. There is a SP and several CU updates since then.
How were you able to find out it is RTM?
On another note. I removed every user but me and the secretary... Meeting notice delivered just fine. Which means there is a problematic user, even though I checked each one and they are all current employees and accounts are all fine.
How many users were in it? It does seem like one of your user mailbox's may be causing your issue.
64 from the start. I broke them out in blocks of 16. The last group she tried is having the problem. Checking on mail box sizes.
-
That would be REALLY stupid if one mailbox being too full caused the whole distro to fail. That person should simply not be able to receive email...
-
I just checked all the remaining mailboxes, none are close to full.
-
@BBigford said:
I just checked all the remaining mailboxes, none are close to full.
Guess now you can start removing folks from that group until you find the culprit.
-
EDIT: never mind, my reply was for Exchange 2010
-
Did you narrow it down to a single user?
Maybe a corrupt mailbox?
-
FYI, I seem to have to run a calendar repair on my physician's calendars at least yearly if not more often. Their calendars are changing constantly, I mean like dozens of times a day. The biggest issues we have are when an appointment is moved from one time to another time or day (something else that happens all the time).
We found that completely deleting the old appointment and creating a brand new one on the new time/date completely solves that specific problem - sadly our turn over is high and the new staff aren't told this until there is a problem.
