The Script Editor unexpectedly quits when you use the Script Editor for the first time in an Office program (898789)


The information in this article applies to:

  • Microsoft Office Professional Edition 2003
  • Microsoft Office Access 2003
  • Microsoft Office Excel 2003
  • Microsoft Office FrontPage 2003
  • Microsoft Office InfoPath 2003
  • Microsoft Office OneNote 2003
  • Microsoft Office Outlook 2003
  • Microsoft Office Outlook 2003 with Business Contact Manager
  • Microsoft Office PowerPoint 2003
  • Microsoft Office Publisher 2003
  • Microsoft Office Publisher 2003 with Digital Image Pro
  • Microsoft Office Word 2003
  • Microsoft Office XP Developer
  • Microsoft Office XP Professional
  • Microsoft Office XP Small Business
  • Microsoft Office XP Standard
  • Microsoft Office XP Students and Teachers
  • Microsoft Access 2002
  • Microsoft Excel 2002
  • Microsoft FrontPage 2002
  • Microsoft Outlook 2002
  • Microsoft PowerPoint 2002
  • Microsoft Publisher 2002
  • Microsoft Word 2002
  • Microsoft Office Basic Edition 2003
  • Microsoft Office Small Business Edition 2003
  • Microsoft Office Standard Edition 2003
  • Microsoft Office Students and Teachers Edition 2003

Thank you for your help!

We thank you for taking the time to send us information about the program error that you just experienced. After investigating error reports that are provided by users like you, our engineers devised a workaround for this problem. This article contains information that may help you 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           ntdll.dll     5.1.2600.1217    00007bd2
 mse7.exe           11.0.5510.0           ntdll.dll     5.1.2600.1106    000016c5
 mse7.exe           11.0.5510.0           ntdll.dll     5.1.2600.2180    000105f8
 mse7.exe           11.0.5510.0           ntdll.dll     5.0.2195.6899    0004c128
 mse7.exe           11.0.5510.0           ntdll.dll     5.0.2195.6899    0004c128
 mse7.exe           11.0.5510.0           ntdll.dll     5.1.2600.2180    000105f8
 mse7.exe           11.0.5510.0           ntdll.dll     5.1.2600.2180    000105f8
 mse7.exe           11.0.5510.0           ntdll.dll     5.2.3790.0       7300
 mse7.exe           10.0.2529.0           ntdll.dll     5.1.2600.1217    00007bd2
 mse7.exe           10.0.2529.0           ntdll.dll     5.1.2600.0       0000171c
 mse7.exe           10.0.2529.0           ntdll.dll     5.1.2600.114     00007b58
 mse7.exe           10.0.2529.0           ntdll.dll     5.0.2195.6899    0004c128
 mse7.exe           10.0.2529.0           ntdll.dll     5.0.2195.2779    0004b144
 mse7.exe           10.0.2529.0           ntdll.dll     5.1.2600.1106    000016c5
 mse7.exe           10.0.2529.0           ntdll.dll     5.0.2163.1       000497a0
 mse7.exe           10.0.2529.0           ntdll.dll     5.0.2195.1600    0004a08a
 mse7.exe           10.0.2529.0           ntdll.dll     5.1.2600.1177    00007bd2
 mse7.exe           10.0.2529.0           ntdll.dll     5.1.2600.2055    11274
 mse7.exe           10.0.2529.0           ntdll.dll     4.0.1381.298     000046db

Additionally, other offsets are possible.

SYMPTOMS

When you use the Microsoft Script Editor for the first time in one of the programs that are listed in the "Applies to" section, the Script Editor unexpectedly quits. Additionally, you receive an error message that is similar to the following error message:
Microsoft Script Editor 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 Script Editor. 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.

CAUSE

This problem may occur if you install a Microsoft Office program in a location that is different from a separate installation of the same version of Office. Therefore, the following conditions are true:
  • The computer has two or more copies of the same version of the Script Editor.
  • The computer has two or more copies of the Msenv.dll file.
Depending on which Office program that you use the Script Editor in first, only one of the Msenv.dll files is registered. When you try to use a second copy of the Script Editor, two Msenv.dll files load into memory. Therefore, a conflict occurs. Additionally, the Script Editor unexpectedly quits.

WORKAROUND

To work around this problem, repair the Office installation.

To repair Microsoft Office 2003, follow these steps:
  1. Quit all Office programs.
  2. Click Start, click Run, type appwiz.cpl, and then click OK.
  3. In the Currently installed programs list, click Microsoft Office 2003, and then click Change.
  4. On the Maintenance Mode Options page, click Reinstall or Repair, and then click Next.
  5. On the Reinstall or Repair Office page, click Detect and Repair errors in my Office installation.
  6. Click to select the Restore my Start Menu Shortcuts check box, and then click Install.
  7. If you are prompted to restart the computer to finish the installation, click Yes.
To repair Microsoft Office XP, follow these steps:
  1. Quit all Office programs.
  2. Click Start, click Run, type appwiz.cpl, and then click OK.
  3. In the Currently installed programs list, click Microsoft Office XP, and then click Change.
  4. Click Repair Office, and then click Next.
  5. Click Detect and Repair errors in my Office installation, and then click Install.
  6. Click OK when you receive the message that Setup successfully repaired the Office installation.
  7. Click Close.

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:

http://oca.microsoft.com/en/dcp20.asp

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

Modification Type:MinorLast Reviewed:9/13/2006
Keywords:kbScript kberrmsg kbBug KB898789 kbAudITPRO kbAudEndUser
©2004 Microsoft Corporation. All rights reserved.