Microsoft KB Archive/170255

From BetaArchive Wiki

Article ID: 170255

Article Last Modified on 5/2/2006


  • Microsoft Visual InterDev 1.0 Standard Edition

This article was previously published under Q170255


When you try to open any Active Server Pages (ASP) files in Visual InterDev you get the following error message:

Application error instruction at 0x5166344D referenced memory at 0x00000004. The memory could not be read.

This message is followed by the following:

Unhandeled exception in msdev.exe devhtmx.pkg 0xc0000005: Access Violation.


This problem is caused by an entry in the registry that is left over from the beta of Visual InterDev (Named Visual Studio).

The Readme.txt file that is included with Visual InterDev details the steps necessary to remove the beta, and all of its associated registry entries. This particular error will not occur if the registry keys in the Readme.txt file were removed.


WARNING: The following steps include editing your registry with Registry Editor. Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

This error can be fixed by doing the following:

  1. Ensure that Visual InterDev is not running.
  2. Launch a registry editor such as RegEdit.exe.
  3. Delete the key:

  4. Launch Visual InterDev and open any ASP file. The error should not occur.


Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Note that since there are apparently beta components and/or registry entries on the affected machine, it is recommended that you read the Readme.txt file for the full instructions on removing the beta to minimize conflicts with Visual InterDev


For the latest Knowledge Base articles and other support information on Visual InterDev and Active Server Pages, see the following page on the Microsoft Technical Support site:

Additional query words: crash GPF UAE 0x5166344D 0x00000004

Keywords: kberrmsg kbregistry kbreadme kbprb KB170255