Re: Information store seems to hang

With Windows 2003 (and more than 1GB RAM), you are supposed to to /3GB
/USERVA=3030, but ExBPA should have identified that, and if that was causing
problems, you would have definitely seen virtual memory warnings/errors in
your App log. Still, it won't hurt to put it in. There's a great KB
article on Exchange 2003 memory optimization, but again, if there were
problems with this, you should have at the very least gotten an event logged
stating something like the virtual memory is not optimized, or something
like that.
http://support.microsoft.com/default.aspx?kbid=815372&product=exch2003

Do you not have Exchange set to autodiscover GC's right now? When you bump
diagnostics logging on DSAccess, it will log an event showing which GC's it
has discovered.

Do you have Active Directory Sites and subnets set up? Those are really
needed in order for DSAccess to discover properly...

Running netmon from all 3 makes sense as well.

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Janelle" <Janelle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2C80DE3B-F72B-4364-9DFE-E9B4281AAC63@xxxxxxxxxxxxxxxx
Well I got another response back from microsoft and basically they give me
the impression that they think that the active directory is not configured
correctly and that is causing my exchange issues.
They want me to set the USERVA first of all even though I set the /3GB and
heapdecommitfreeblockthreshold
Delete a guid in the dacl in the exchange domain servers group.
Investigate occurrance of Event ID 8026 which I can't find any of.
I have run netmon from the exchange server but they want me to run it from
the Exchange, client and GC when the problems are occurring.
Set the DS access tab to automatically discover the GC's
I have sent so much any ideas where else to look? And what do you think of
their approach
Thanks
Janelle



"Ben Winzenz [Exchange MVP]" wrote:

I'm sure it's possible it's an issue with the mailbox store...

I haven't seen this problem before though. I would recommend at least
trying to move 1 affected user and see if that resolves the issue.

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Janelle" <Janelle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E2495A7D-1C90-4073-81EE-B5309A8D3355@xxxxxxxxxxxxxxxx
I could but I need to get a accurate count on who is affected first. Is
this
a unique issue or have you heard of something similar?
Thanks
Janelle

"Ben Winzenz [Exchange MVP]" wrote:

Diagnostics logging is on the properties of the server in ESM.

Can you move affected users to a different mailbox store and see if
that
resolves the issue?

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Janelle" <Janelle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:64633DEB-5BEB-4043-A2AB-0F7CECD65F25@xxxxxxxxxxxxxxxx
I really don't think that the upgrades will hurt, and I also agree
that
they
won't resolve my performance issues either.
The only performance issues that I hear of are the ones at my site,
I
really
don't hear anything from the other sites saying they are having
trouble
connecting to the exchange server,but that could mean they just
don't
tell
me.
It usually happens on a regular basis to one of our laptop user who
takes
his machine home every night. Also the ones I know for sure
about,within
the
last weeks issues, were users whose mailboxes all resided in the
same
information store as the systems mailbox and the system attendant.

In regards to the diagnostics I could try to bump them up, where do
I
do
that at?
ExBPA and ExPTA run almost daily with the latest versions I run MPS
reports,
netmon, perfwiz and anything microsoft suggested. I have sent all
that
information to microsoft and as I said in the previous message what
issues
they tended to focus on.
Well let me know what you think
Janelle

"Ben Winzenz [Exchange MVP]" wrote:

I don't see any problems with upgrading, but I seriously doubt it
will
address any of the issues you are having here.

Out of curiousity, is it ALL users that are affected, or just some?
Are
these users in your local office, or a remote location?

Can you bump up diagnostics logging on Exchange? I'd bump up all
of
the
categories listed under MSExchangeAL. I'd also look at bumping up
logging
under MSExchangeDSAccess, and MSExchangeSA. Doing so will log a
LOT
of
additional information, but hopefully some of it will be helpful.

You might also want to try running Microsoft's Performance and
Troubleshooting Analyzer. It's another analyzer like BPA that just
came
out
not too long ago.
http://www.microsoft.com/downloads/details.aspx?FamilyID=4BDC1D6B-DE34-4F1C-AEBA-FED1256CAF9A&displaylang=en

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Janelle" <Janelle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C96D20B4-A457-4993-84B9-54CA770D1D2A@xxxxxxxxxxxxxxxx
Ben,
I read you info and just to let you know I am in Lafayette
indiana
near
your
old stomping grounds. But anyway I got a response from Microsoft
that
deals
more with Event ID's 8270, 8548, 8026, the fact that I ran netmon
only
from
the exchange server, the latency issues between our UK site.
These
seem
to
be
all architectural issues of my Active directory and am not
convinced
those
are really that significant to the issue. So my next step is to
upgrade
to
win 2003 SP1 and Exchange 2003 SP2. Do you see any problems with
that
or
see
anyway that might eliminate my current issues? Any other
suggestion
you
have
will be much appreciated.

"Ben Winzenz [Exchange MVP]" wrote:

Just renaming a store shouldn't do anything. You are just
renaming
the
Display name.

As far as if it was deleted, as long as the System Mailbox and
System
Attendant mailbox exist, it should be fine. The System
Attendant
mailbox
normally gets automatically re-created when the System Attendant
service
is
restarted if it is deleted for some reason.

See
http://blogs.technet.com/evand/archive/2004/12/21/329172.aspx
and
http://blogs.technet.com/evand/archive/2004/12/17/323636.aspx

for more information on the Sys Att mailbox and System mailbox.

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Janelle" <Janelle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0FE9658D-5EAC-4A6E-8439-33BB081C23E4@xxxxxxxxxxxxxxxx
We do not have any other exchange server in the mix at this
time,
but
one
or
two of our other sites were migrated from other exchange
servers,
to
the
current one.
Now the person who set up the exchange server either deleted
or
renamed
the
original default mailbox store(where the systems attendant and
system
mailbox
reside) which is created when you install exchange located
under
the
first
routing group.He did this because he was not able to create
enough
more
than
4 information stores in the first routing group. Not sure if
that
would
affect anything, I'm not sure so I thought I would mentioned
it
to
see
if
that sheds any light on my situation
Thanks
Janelle

"Ben Winzenz [Exchange MVP]" wrote:

Hmmm - if none of your stores appear to be dismounted, then
it's
likely
it
is caused by something else. The other events you posted all
seem
related
to the Address List.

Does
http://support.microsoft.com/default.aspx?scid=kb;en-us;321102
apply?
Do you have multiple servers, and specifically, any old 5.5
servers
still
in
the mix?
http://support.microsoft.com/default.aspx?scid=kb;en-us;329685
perhaps?

Also, check out
http://www.microsoft.com/technet/prodtechnol/exchange/guides/StrPermwE2k3/2934133f-e3af-46a5-9369-1ece5843ff58.mspx
and
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=6.5.6940.0&EvtID=9175&EvtSrc=MSExchangeSA&LCID=1033

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Janelle" <Janelle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:AA5DB38A-FCCB-413A-93A0-226C067AF7A3@xxxxxxxxxxxxxxxx
Why and how would a mailbox store become dismounted on its
own?
And
when I
look at the stores none of them appear to be dismounted.
But
restarting
the
system attendant, information store and the MTA stacks
makes
everything
work
again and the 9175 goes away.
I entered my case with microsoft as critical when I opened
it,
I'm
not
sure
that I can escalate it further than critical but I have
contacted
them
and
expressed my concern.
Yes the 8270 is from the MSExchangeAL

"Ben Winzenz [Exchange MVP]" wrote:

9175 events are benign and can be ignored. You'll see
those
every
time a
mailbox store is dismounted.

If you have an open PSS support case, and they aren't
making
any
headway,
you need to call back in and get it escalated. Having a
support
issue
open
for 2 weeks without any progress isn't normal.

What are the sources of the other events? 8270 -is that
from
the
MSExchangeAL?

8315 error -
http://support.microsoft.com/default.aspx?scid=kb;en-us;254030

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"Janelle" <Janelle@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:1EF8BE82-9A06-4251-82F6-F0EAA95F8F86@xxxxxxxxxxxxxxxx
and I have Exchange server 2003 SP1 on a Windows 2003
server
no
SP.
I
get
alot of event id's 9175 having to do with the system
attendant.
Event
ID


.

Relevant Pages

  • Re: Information store seems to hang
    ... information store as the systems mailbox and the system attendant. ... Can you bump up diagnostics logging on Exchange? ... As far as if it was deleted, as long as the System Mailbox and System ... Now the person who set up the exchange server either deleted or renamed ...
    (microsoft.public.exchange.admin)
  • 262892 XADM: Moving the Exchange 2000 System Attendant Mailbox
    ... Microsoft Exchange Server 2003 Enterprise Edition ... The System Attendant mailbox on an Exchange server is used ... You may not need to move the System Attendant mailbox to ...
    (microsoft.public.de.german.exchange2000.general)
  • Re: Issue using Exchange 2003 cross-administrative group mailbox move in mixed mode
    ... the object was re-created in the source site from looking at the perspective ... > delivering to the wrong mailbox. ... > Microsoft Exchange Support ... >> some servers I have had no issues doing this but on a couple of servers I ...
    (microsoft.public.exchange2000.active.directory.integration)
  • Re: I couldnt start up Exchange System Attendant
    ... DNS are installed on two domain servers and all virtual servers dns point to these two domain servers. ... I checked both exchange servers belong to Exchange Domain Servers Group. ... Exchange System Attendant couldn't start up and error message is: ...
    (microsoft.public.exchange.admin)
  • RE: Event 2061 LDAP search call failed
    ... is mailbox enabled and missing the LegacyExchangeDN attribute. ... Use Outlook or Exmerge tool to export mailbox to PST file. ... right-click the problematic user and then click Exchange tasks. ... Exchange 2003 server to make it re-detect these servers. ...
    (microsoft.public.exchange.connectivity)