Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You receive an error message when you use the Script Editor in an Office 2003 program


View products that this article applies to.

Thank you for your help!

Microsoft thanks you for taking the time to send us information about the program error that you just experienced. After investigating error reports provided by users like you, our engineers devised a work around for this problem. This article contains information that may help you to avoid this problem in the future.

Error signature

This article describes a program error that can have the following error signatures:
   Application name  Application version  Module name  Module version  Offset
   ----------------------------------------------------------------------------

   Mse7.exe          11.0.5510.0          Msenv.dll    7.0.9064.9606   0018d883

   Mse7.exe          10.0.2529.0          Msenv.dll    7.0.9064.9136   0018d4e4

Additionally, other offsets are possible.

↑ Back to the top


Symptoms

When you try to use the Microsoft Script Editor (MSE) in one of the programs that are listed in the "Applies To" section (on the Tools menu, point to Macro, and then click Microsoft Script Editor), you may receive an error message that is similar to the following, where Program name is one of the programs that is listed in the "Applies To" section:.
Microsoft Program name has encountered a problem and needs to close. We are sorry for the inconvenience.
Please tell Microsoft about this problem.
We have created an error report that you can send to help us improve Program name. We will treat this report as confidential and anonymous.
To see what data this error report contains, click here.
Note To view the details of the error signature, click the link in the following text:
To see what data this error report contains, click here.

↑ Back to the top


Cause

This problem may occur if a file in the following folder is damaged or is corrupted:
drive:\Documents and Settings\username\Application Data\Microsoft\Mse

↑ Back to the top


Workaround

To work around this problem, use Microsoft Windows Explorer to locate and then delete the following folder:
C:\Documents and Settings\username\Application Data\Microsoft\Mse
After you delete this folder, the folder and the files are re-created the next time that you access the Script Editor.

If you do not see the Application Data folder, your operating system is likely hiding hidden files and folders. Hiding hidden files and folders is the default setting in the operating system. To display hidden files and folders, follow these steps:
  1. In the Explorer window, click Folder Options on the Tools menu.
  2. In the Folder Options dialog box, click the View tab.
  3. On the View tab in the Advanced Settings list, locate Hidden files and folders.
  4. Under the Hidden files and folders section, click to select the Show hidden files and folders check box, and then click OK.

Note If this workaround does not resolve your issue, your issue may have a different cause and may require additional steps to resolve.

For more information and additional steps to take to resolve this issue, click the following article number to view the article in the Microsoft Knowledge Base:
898789� The Script Editor unexpectedly quits when you use the Script Editor for the first time in an Office program

↑ Back to the top


More information

The Office Error Reporting dialog box appears when an error occurs that causes a fatal event in the program. The dialog box includes a button to send the information about the fatal event to Microsoft. Microsoft gathers information about these types of events in a database to try to identify the cause. For more information about the Microsoft Data Collection Policy, visit the following Microsoft Web site: For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
283768� Description of the end user privacy policy in application error reporting when you are using Office

289508� How to view error signatures if an Office program experiences a serious error and quits

↑ Back to the top


Keywords: KB840184, kberrmsg, kbscript, kbmacro, kbtshoot

↑ Back to the top

Article Info
Article ID : 840184
Revision : 14
Created on : 3/26/2007
Published on : 3/26/2007
Exists online : False
Views : 368