XADM: Wizard Sets Incorrect Concurrent Read Thread Range
Article ID: 152878
Article Last Modified on 10/28/2006
APPLIES TO
- Microsoft Exchange Server 4.0 Standard Edition
This article was previously published under Q152878
SYMPTOMS
When you use the Microsoft Exchange Performance Optimizer, a
signed/unsigned variable problem can cause an underflow in a calculation
under certain circumstances. The maximum number of concurrent read threads
can be set in the range from 0 to 1717986910.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Exchange Server
version 4.0. This problem was corrected in Microsoft Exchange Server 4.0
U.S. Service Pack 2. For information on obtaining the service pack, query
on the following word in the Microsoft Knowledge Base (without the spaces):
Keywords: kbusage KB152878