Access Violation in RRAS When Windows Time Service Adjusts System Time

On a system with Routing and Remote Access Service (RRAS), the following symptoms may occur as a result of a negative system time adjustment.

• Mpradmin.exe may display an Integer Overflow exception error message (status code 0xC0000095).
• You may not be able to stop Mprouter.exe and it stops accepting new RRAS connections.

Both symptoms are caused by an arithmetic calculation for call duration that can generate a negative 64-bit result that causes an integer overflow when saved in a 32-bit integer format. This behavior occurs only if the time adjustment is negative and sufficiently large enough to move the system clock back to a time prior to the beginning of any RRAS connection.

Time adjustments are caused in a variety of ways. Manual time correction through the System Time tool in Control Panel is a potential source, as are automatic mechanisms such as the intrinisic OS operations that periodically synchronize the system time to the CMOS clock resource. Domain-based Microsoft network time services can similarly cause this problem. Additionally, third-party programs that synchronize the system clock to a network-accessible reference clock can act to stimulate this problem.

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

• http://www.microsoft.com/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/ (http://www.microsoft.com/Windows/ServicePacks/) -or-
  
  
• 152734  (http://support.microsoft.com/kb/152734/EN-US/ ) how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server version 4.0, Terminal Server Edition Service Pack 6.