Solved

Exchange 2007 Slowness New Install - Troubleshooting Assistant Error

Posted on 2009-06-30
4
1,523 Views
Last Modified: 2012-05-07
Hello all,

We are in the process of migrating from Novell to Microsoft Exchange 2007.  Initially, we installed our Hub Transport Role and our CAS and Mailbox role on a seperate server, both running Win Server 2008 SP1.  After the initial install everything was extremely slow.  The HT has 16GB of memory and the CAS and Mailbox role has 32GB.  

Doing a little bit more investigation I realized that our initial setup of the RAID and placement was not ideal for the CAS and Mailbox server, so we redid the server so we have 6 drives currently, so 3 mirrored RAID, with the OS on one drive, the Database on another and the log file on another.

This helped speed up things tremendously.  However, I am still experiencing sluggishness, specifically when the user initially logs in, which we believe is partially due to our one Active Directory server.   We have two AD servers atm with 10k accounts.  The one server is running 64-bit and the other 32-bit,  We believe that the we are experiencing memory limitations on the 32-bit server, so we intent to upgrade the server to 64-bit.  A couple months back, we also began password synchronization, so various services now look to AD for authenication.  To deal with this, we also intend to build an ADAM server.

With that said, I want to make sure that with the errors that I am seeing that if there is ANYTHING else that I can should be doing to improve performance, that I do so now, before we implement this new system and users complain about slowness or worse...

These are following issues that I get from the Troubleshooting assistant on the HT:
LDAP Health:  Error accessing 'MSExchangeDSAcess Domain Controllers' and/or 'MSExchangeDSAccess Caches' performance counter data Error accessing the 'MSExchangeDSAccess Domain Controllers' performance counters. Unknown error (0xc0000bb8)

Memory and Processor Health
Time Range: One or more virtual memory performance counters are not present in the file C:\Perflogs\dispatch-20090626124349\dispatch-PDH.blg. The following counters are missing: \\dispatch\MSExchangeIS\VM Largest Block Size,\\dispatch\MSExchangeIS\VM Total 16MB Free Blocks,\\dispatch\MSExchangeIS\VM Total Free Blocks,\\dispatch\MSExchangeIS\VM Total Large Free Block Bytes

Queue Health:
One or more performance counters are not present in the file C:\Perflogs\dispatch-20090626124349\dispatch-PDH.blg. The following counters are missing: \\dispatch\Epoxy(IMAP)\Client Out Queue Length,\\dispatch\Epoxy(IMAP)\Store Out Queue Length,\\dispatch\Epoxy(POP3)\Client Out Queue Length,\\dispatch\Epoxy(POP3)\Store Out Queue Length,\\dispatch\MSExchangeIS Public(_Total)\Replication Receive Queue Size,\\dispatch\SMTP Server(_Total)\Categorizer Queue Length,\\dispatch\SMTP Server(_Total)\Remote Queue Length,\\dispatch\SMTP Server(_Total)\Remote Retry Queue Length,\\dispatch\SMTP Server(_Total)\Local Queue Length,\\dispatch\MSExchangeIS\Virus Scan Queue Length,\\dispatch\MSExchangeIS\Virus Scan Files Scanned/sec,\\dispatch\MSExchangeIS\Virus Scan Files Quarantined/sec,\\dispatch\MSExchangeIS\Virus Scan Messages Processed/sec

RPC Performance Counters:
One or more performance counters are not present in the file C:\Perflogs\dispatch-20090626124349\dispatch-PDH.blg. The following counters are missing: \\dispatch\Epoxy(IMAP)\Client Out Queue Length,\\dispatch\Epoxy(IMAP)\Store Out Queue Length,\\dispatch\Epoxy(POP3)\Client Out Queue Length,\\dispatch\Epoxy(POP3)\Store Out Queue Length,\\dispatch\MSExchangeIS Public(_Total)\Replication Receive Queue Size,\\dispatch\SMTP Server(_Total)\Categorizer Queue Length,\\dispatch\SMTP Server(_Total)\Remote Queue Length,\\dispatch\SMTP Server(_Total)\Remote Retry Queue Length,\\dispatch\SMTP Server(_Total)\Local Queue Length,\\dispatch\MSExchangeIS\Virus Scan Queue Length,\\dispatch\MSExchangeIS\Virus Scan Files Scanned/sec,\\dispatch\MSExchangeIS\Virus Scan Files Quarantined/sec,\\dispatch\MSExchangeIS\Virus Scan Messages Processed/sec

Unclassified Items:
Failed to readExMon data from ETL trace file
No user data was found in Exchange Server User Monitor (ExMon) ETL trace file 'C:\Perflogs\dispatch-20090626124349\dispatch-EXMON.etl'. This may be because you are not running this tool on a version of Windows that is the same or more recent than the server on which the trace was collected, or because there was no RPC data in the trace file.

Paged pool memory
The maximum paged pool memory on server dispatch is over the warning threshold of 200 MB. Current value: 202 MB.

On the CAS and Mailbox Server:
Function Call Log:
FCL Function name: HrReadDsvalGuid: Slow calls to the active directory: Long wait time in function call to the directory
FCL function name: HrSearchGuid: Slow calls to the active directory: Long wait time in function call to the directory
FCL function name: JetOpenTable: Slow calls to Jet: Long wait time in function call to Jet

Paged pool memory:
Paged pool memory on server rfd is over the error threshold of 220 MB. Current value: 301 MB.

RPC:
High RPC latency:  The '\MSExchangeIS\RPC Averaged Latency' is higher than the threshold of 0.05 seconds (50 ms). The measured value is 0.056 seconds (55.9649122807018 ms).

Error accessing the 'MSExchangeDSAccess Domain Controllers' performance counters. Unknown error (0xc0000bb8)


The one that preplexed me the most is the page pool memory.
Any input would be greatly appreciated.


0
Comment
Question by:StuGreentree
  • 2
  • 2
4 Comments
 
LVL 65

Accepted Solution

by:
Mestha earned 500 total points
ID: 24746226
Pile of missing counters from perfmon is rare, but non-unusual. I think Microsoft have a KB article on how to reset those.

Are both domain controllers global catalogs? With 10,000 accounts you are pushing them a little bit. I would be looking to add in an additional x64 DC sooner rather than later, and then take the GC role away from the 32 bit machine. GC does the logins. The other FSMO roles could be left on the machine (or moved to it).
Exchange will only talk to one DC at a time, so if it is using the 32 bit DC then you may well be seeing a performance impact there.

Have you run the best practises tool against the system to ensure that nothing is flagged there?

Simon.
0
 

Author Comment

by:StuGreentree
ID: 24762157
Do you happen to know the KB on how to reset those counters?

Both of the domain controllers are global catalog servers.  I move the role solely to the x64 in the interim for the transition of when we make the 32-bit machine a 64-bit one.  I have moved the other FSMO roles as well.  

I have run the ExBPA health check a few times now and currently on the HT I am getting "Firewall is enabled" and oddly enough is it not enabled...  It is also giving me a public folder tree database assignment as not having any public folder store, which is fine because we are not going to be using this feature.  

On the mailbox and CAS server: same public folder database assignment that's it.

Even with changing the GC catalogue role to the x64 bit domain controller, I am still having issues with sloweness in the OWA login.  It takes about 30 seconds after a user enters their username and password before it will login.  Once you are inside owa and even pulling up the page, everything is extremely speedy.  
0
 
LVL 65

Expert Comment

by:Mestha
ID: 24762533
Unless you are exclusively on Outlook 2007, so no Mac clients or older versions of Outlook, you must use public folders.

The tool should have pointed you to Microsoft articles on resetting the counter. Otherwise try this.
http://msexchangetips.blogspot.com/2006/09/exchange-perfmon-exchange-counters.html

After changing the global catalog, did you restart any Exchange services?

Simon.
0
 

Author Comment

by:StuGreentree
ID: 24869145
Turns out the bottleneck was the 32-bit server, I removed it from being a GC and did a reboot.  Since then we have upgraded it to 64-bit and everything is working great now.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
"Migrate" an SMTP relay receive connector to a new server using info from an old server.
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now