Knowledge Base

"Access Violation" Error Message When You Quit Phone Dialer

Article ID: 237185

Article Last Modified on 11/1/2006

APPLIES TO

Microsoft Windows NT Server 4.0, Terminal Server Edition
Microsoft Windows NT Workstation 4.0 Developer Edition
Microsoft Windows NT Server 4.0 Standard Edition
Microsoft Windows NT Server 4.0 Enterprise Edition
Microsoft BackOffice Small Business Server 4.5
Microsoft BackOffice Server 4.0
Microsoft BackOffice Server 4.5

This article was previously published under Q237185

SYMPTOMS

When you quit Phone Dialer, you may receive an "Access violation" error message, and an entry similar to the following example may be written to the Event Viewer Application log:

The application, exe\dialer.dbg, generated an application error.
The error occurred on date @ time
The exception generated was c0000005 at address 31313131.

CAUSE

The Phone Dialer cleanup routine does not properly remove the entries from memory if the Dialer.ini file is modified so that the [Last Dialed Numbers] section contains an entry with between 128 and 256 characters.

RESOLUTION

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/windows/servicepacks/ -or-

152734how 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:

http://support.microsoft.com/directory/overview.asp

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:

152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.

This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.

Keywords: kbhotfixserver kbqfe kbbug kberrmsg kbfix kbqfe KB237185

Microsoft KB Archive/237185

Contents