Microsoft KB Archive/818794

From BetaArchive Wiki

Article ID: 818794

Article Last Modified on 2/5/2007



APPLIES TO

  • Microsoft Visio 2002 Professional SR-1
  • Microsoft Visio 2002 Standard SR-1



SYMPTOMS

When you move a Dynamic connector shape to a different connection point on a shape in your cross-functional flowchart, you may receive an error message similar to one of the following:

Microsoft Visio C++ Runtime Library

Runtime Error!

Program: Drive:\Program Files\Microsoft Office\Visio10\Visio.exe

abnormal program termination

-or-


The instruction at "0x30b26b70" referenced memory at "0x1a5a01b4". The memory could not be "read".

Click on OK to terminate the program.

When you click OK, Visio stops responding (hangs).

Additionally, when you start Task Manager (press CTRL+ALT+DELETE, and then click Task Manager), and then click the Processes tab, the Visio.exe process may consume up to 100 percent of CPU resources.

CAUSE

This problem may occur if all the following conditions are true:

  • You connect flowchart shapes that are located in bands in your flowchart with a Dynamic connector shape.
  • The Dynamic connector shape is grouped with one or more flowchart shapes.

In this situation, Visio incorrectly process the operation when you move an endpoint of the Dynamic connector shape to a different connection point (blue "X") on a flowchart shape.

RESOLUTION

Service pack information

This problem is corrected in Microsoft Visio 2002 Service Pack 2.

To resolve this problem, obtain the latest service pack for Microsoft Visio 2002. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

867749 How to obtain the latest Visio 2002 service pack


Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visio 2002 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The global version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

   Date         Time   Size    File name
-------------------------------------------------------------------------------
27-Apr-2003  10:09  194,560  Visio2002-kb818794-eng.msp

                

After the hotfix is installed, the global version of this fix will have the file attributes (or later) that are listed in the following table:

Date         Time   Version      Size       File name
-----------------------------------------------------
24-Apr-2003  11:44  10.0.4024.4       586,240  Cross functional.dll

Note Because of file dependencies, this update requires Visio 2002 SR-1.




STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Visio 2002 Service Pack 2.

MORE INFORMATION

For more information about how to create cross-functional flowcharts in Visio 2002, visit the following Microsoft Web site:

Keywords: kbhotfixserver kbqfe kbstoprespond kbtshoot kbfix kbbug KB818794