Re: Exchange 2003 logging 12800 errors

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Danny,

Thanks for your update.

I am sorry for the delayed response due to weekend. Please understand that
the newsgroups are staffed weekdays by Microsoft Support professionals to
answer your systems and applications questions. Your understanding is
greatly appreciated!

Because Charles is taking leave I will continue to work with you on the
issue.

For the issue, I suggest you do as following:

1. Re run the monitoring wizard to see how thing goes.
2. Try to do a clean boot:

1) Click Start, click Run, and then in the Open box, type "MSCONFIG"
(without the quotation marks). Click OK.
2) In the System Configuration Utility (MSConfig) window, click to select
the Selective Startup button.
3) Click to clear the check mark from the "Load startup items" below
Selective Startup.
4) Click the Services tab, click to check the "Hide All Microsoft Services"
box, and remove all the check marks from the remained Non-Microsoft
Services. Please note that the Exchange services could be marked as
non-Microsoft. Please do not disable those services.
5) Click OK to close the MSConfig window. Click Yes when you are asked to
restart your computer in order to enable the changes.
6) After restarting, please check whether this issue will reoccur.

3. Have you installed Exchange SP1? If not, you can try to install it from
the following web site:

http://www.microsoft.com/exchange/downloads/2003/sp1.asp
http://www.microsoft.com/downloads/details.aspx?FamilyId=0FE89C95-E767-428C-
8621-6A586C655EE3&displaylang=en

After installing Exchange 2003 SP1, there are a couple of tweaks needed:

1) By default, after running CEICW, the component will set the Default
Domain property on the corresponding IIS sub-directories (under
Authentication -> Access Control) as following:

/Exchange/: \
/Microsoft-Server-ActiveSync/: SBS domain name
/OMA/: SBS domain name

However, Exchange 2003 SP1 replaces the OWA logon screen (Program
Files\Exchsrvr\bin\auth\usa\logon.asp) and it caused OWA now to ask for
domain\username instead of simply just the username. To fix this problem
before SBS SP1 comes out, you can edit the SP1 logon.asp or (which is
recommended) just add the domain name in the Exchange virtual directory,
Directory Security, Authentication and access control, Default Domain.

The same goes to the OWA and Server-ActiveSync sub-sites, we can just set
the "SBS domain name" back. This is considering the fact that some PPC or
mobile phone cannot use the reverse backslash character when inputting
credential.

2) After installing Exchange 2003 SP1 to SBS server, you may notice that
store.exe is consuming more memory than before. It also occurs on normal
Exchange 2K3 server, the only difference is that SBS has the monitoring
component which will send out e-mail notification once the threshold is
reached.

This issue occurs no matter the amount of the memory is below or above 1
GB. In addition, many of the partners has also implemented the suggestions
in the following KB, it makes things better but the store memory usage is
still higher than SP1 was applied:

815372 How to Optimize Memory Usage in Exchange Server 2003
http://support.microsoft.com/?id=815372

Prior to SP1, the database cache bytes are counted as mapped bytes. In SP1,
the database cache is counted under private bytes. Thus, the private bytes
will be considerably higher (about 940 MB higher) for SP1 than before, and
mapped bytes will be correspondingly lower. If people are using private
bytes as the measure of memory, then yes, it changed dramatically between
Ti and Ti SP1. Working set and Virtual Bytes should be mostly unaffected.

Since SBS Monitoring is counting the Private Bytes, it will be 940MB higher
than before. This won't impact the server's normal operation.

Workaround is to add 1000 or above to the counter so that you will not
receive the warning that frequently.

Please check Susan's Website for more detailed information:

http://www.sbslinks.com/exchange.htm

NOTE: This response contains a reference to a third party World Wide Web
site. Microsoft is providing this information as a convenience to you.
Microsoft does not control these sites and has not tested any software or
information found on these sites; therefore, Microsoft cannot make any
representations regarding the quality, safety, or suitability of any
software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make
sure that you completely understand the risk before retrieving any software
from the Internet.

More information:

325044 How to troubleshoot virtual memory fragmentation in Exchange Server
2003 and Exchange 2000 Server
http://support.microsoft.com/default.aspx?scid=kb;EN-US;325044

I am appreciated your time and look forward to hearing form you.

Best regards,

Crina Li (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Danny Liberty" <dliberty@xxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.sbs
| Subject: Re: Exchange 2003 logging 12800 errors
| Date: 15 Jan 2006 07:55:57 -0800
| Organization: http://groups.google.com
| |
| Hi Charles,
|
| Unfortunately the situation is not resolved. I would like to emphasize
| the store.exe process only consumes ~21MB of memory.
| Any other leads?
|
| Thanks,
|
| Danny
|
|

.

Quantcast