Thursday, January 29, 2009

Event ID 929 is logged, and mail is not delivered from one mail server to another mail server in an Exchange 2000 Server organization

http://support.microsoft.com/kb/907969

ADModify

http://www.codeplex.com/admodify

Project DescriptionADModify.NET is a tool primarily utilized by Exchange and Active Directory administrators to facilitate bulk user attribute modifications. See http://blogs.technet.com/exchange/archive/2004/08/04/208045.aspx for launch details

Exchange log disk is full, Prevention and Remedies

Exchange log disk is full, Prevention and Remedies

http://www.msexchange.org/articles/Exchange-log-disk-full.html

Wednesday, January 28, 2009

Overview of the ExchDump tool for Exchange 2000 Server and for Exchange Server 2003

Instead of utilizing LDP to get dump of the policies, you can ran an execdump.exe /server from the /bin directory and it create the fillowing: ExchDump_XXXXXX_XXXXXX XML & HTM for review.

Example:

CN=SMALLBIZ (ldap://CN=SMALLBIZ,CN=Servers,CN=first/ administrative group,CN=Administrative Groups,CN=SBS,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=SBS,DC=local) Class: msExchExchangeServer Schema: LDAP://schema/msExchExchangeServer msExchDataPath : "C:\Program Files\Exchsrvr" serialNumber : "Version 6.5 (Build 7638.2: Service Pack 2)" serverRole : 0 whenChanged : Thursday, 11/06/2008 15:31:57 (GMT) ->Click for more details...

http://support.microsoft.com/kb/839116

Tuesday, January 27, 2009

A message that exceeds the configured size limit is sent to a server that is running Exchange Server 2003

http://support.microsoft.com/kb/894795/

Exparse Cmd Example

I used the following cmd to dump the 10 largest incoming/outgoing messages by bytes to a txt file from a message tracking log file.

C:\Program Files\exparse>cscript exparse.vbs /l:"C:\exparse\logfile.log" /v:2000 /sort:bytes /R:10 /S:10

Note: Command Syntax

Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

Invalid flag .

Parses Exchange Tracking logs.

SYNTAX:
1. ExParse.vbs /V:
/L: or ]
[/R:]
[/S:]
[/G:]
[/P:]
[/SORT:<>]

PARAMETER SPECIFIERS:
/V Valid Versions (55, 2000)
/L Tracking log, or log directory
/R Display the Top X Recipients.
/S Display the Top X Senders.
/p Display the Top X Public folders.
/Sort Sort by # message or message bytes.


NOTE:With extremly large tracking logs it is not recommended to
track senders,recipients, Public folders,and gateways at the same time


EXAMPLE:
1. cscript ExParse.vbs /v:55 /l:c:\20030523.log
Parses the Exchange 55 tracking log in c:\temp.

2. cscript ExParse.vbs /v:55 /l:c:\20030523.log /r:7
Parses the Exchange 55 tracking log in c:\temp, and shows the top seven users

Troubleshooting Version Store issues - JET_errVersionStoreOutOfMemory

http://msexchangeteam.com/archive/2006/04/19/425722.aspx

Note: I had a case were I was getting events 623, 1022, 1025 and the following event ID.


Example of a 623 in the application logs:

Event Type: Error
Event Source: ESE
Event Category: Transaction Manager
Event ID: 623
Date: 1/26/2009
Time: 3:34:46 PM
User: N/A
Computer: Computer
Description:
Information Store (4176) Standard Storage Group X: The version store for this instance (2) has reached its maximum size of 155Mb. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back.
Possible long-running transaction:
SessionId: 0xBD33ACA0
Session-context: 0x00000000
Session-context ThreadId: 0x000015AC
Cleanup: 1
For more information, click http://www.microsoft.com/contentredirect.asp.

Wednesday, January 7, 2009

Instructions for gathering data for Exchange Process Crash using Adplus.vbs on a 32bit server

Before the crash occurs
1) Download and install the Microsoft Debuggers

NOTE: You do not have to install the debug tools on your Exchange server. It can be installed on a workstation then copied to the
the Exchange server.

a. Go to http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
b. Under "Download the Debugging Tools for Windows" select the Current Release version.
c. In the File Download dialog box, Select Save and save file to the local hard drive.
d. Once downloaded, navigate to the folder and double click the executable to install.

2) Run Adplus.vbs on the Exchange server console (not through Terminal Services).
a. Open a command prompt by going to Start, Run and enter the syntax: CMD
b. Navigate to the debuggers folder (Default is c:\Program Files\Debugging Tools For Windows):
c: Enter the syntax:

cscript adplus.vbs -crash -pn -o c:\_DumpFile

example to create a dump file for the Store process:
cscript adplus.vbs -crash -pn Store.exe -o c:\Store_DumpFile

d. Click "OK" to the Adplus Warning stating "An _NT_SYMBOLS_PATH environment variable is not set..."
e. Review the Windows Script Host dialog box stating ADPlus is now running in CRASH mode…” Click OK after reading the dialog box.

At this point, Adplus will attach a debugger to the process and wait for an Access Violation. Once an Access Violation occurs,
the debugger will be invoked and a dump file will be created.
Do NOT manually stop or terminate the process.
The folder c:\Store_DumpFile will be automatically created
The Store dump file will have a .dmp file extension and associated data files will be placed in the folder
An alternate local drive can be used if drive c:\ does not have enough drive space.

3) Compress the files created (use your case number as the filename) and FTP them to Microsoft Support using the agreed transfer method.

4) Please include the following information in a text file:
· What version of NT and Service Pack are you running?
· What Exchange Hotfixes do you have installed?
· A full description of the events leading up to the crash.
· Can you recover the server restarting the service?
· Does this happen only under heavy load?
· Have you temporarily disabled any Antivirus software?

Keywords: ADPLUS, Dump, Crash.