Blog Archive

Error FAQs

Q: How do I fix error 53: File not Found?
A: This error can occur when the default Internet Browser is set up incorrectly. In order for EditScript MT to run smoothly Internet Explorer should be set as the default internet browser.

Q: How do I fix error 429?
A: When using Microsoft Office it must be installed as a complete install. Choosing not to install as a complete install may cause specific components needed by EditScript to not be installed as needed.

Q: How do I fix error 430?
A: This problem occurs due to an issue with EditScript 6 and 8 co-existing on the same computer. There are 2 known fixes for this problem.

  1. Find and install EditScript 8.0.48 or higher which fixes this issue. You will have to check with a support representative to see if the institution you are working with is capable of running this version of EditScript (servlet build must be 8.0.46 or higher).

  1. If the institution you are logging into is not capable of running EditScript 8.0.48 or higher you can try the following:
a)       Download the installers for EditScript 6 and 8 to your desktop (via the customer center at
b)       When you need to switch between version 6 and 8 run the corresponding installer for that version
c)       The installer should notify you that this version of EditScript already exists. Choose the "repair" option to fix EditScript
d)       Repeat steps B and C whenever you need to switch between versions.

Q: How do I fix error 462: Remote server machine does not exist or unavailable?
A: This error occurs because EditScript can't talk to the Institution to connect. When this occurs, the best thing to do is to try re-installing EditScript by following the instructions on page 9.

Q: How do I fix error 1155?
A: This error can occur upon installation of EditScript. This error indicates that there is a problem with the “Windows Installer”. It is recommended that you remove and re-install the Windows Installer by:
  1. Going to Start -> Control Panel -> Add or Remove Programs
  2. Remove the “Windows Installer”
  3. Download the latest Windows Installer by searching Microsoft’s website
  4. Run the “Windows Installer”

Q: How do I fix Error 2738: Could not access VBScript run time for custom action?
A: This should only occur on Vista computers. This error message indicates that the VBScript engine is not currently registered on the machine where the install/uninstall is taking place.

The VBScript engine can be quickly registered by following these steps:
1. Run Command Prompt as administrator
         1.1 Start Menu -> All Programs -> Accessories
         1.2 Right click on Command Prompt and select Run as administrator
2. Type cd %windir%\system32 into the Command Prompt and hit Enter
3. Type regsvr32 vbscript.dll into the Command Prompt and hit Enter
Q: The EditScript logo shows but EditScript never starts, how do I fix this?
A: If EditScript logo box appears but EditScript won't start, there could be an issue with the Windows DEP (Data Execution Prevention) setting. This can be fixed by:

  1. Right click on My Computer
  2. Select Properties
  3. Click on the Advanced tab
  4. Go to Settings under the Performance Section
  5. Click on the Data Execution Prevention tab
  6. Select the first radio button: "Turn on DEP for essential Windows Programs and Services only"

Q: I am getting an Automation error with EditScript, how can I fix this?
A: Automation errors are often Microsoft Word related. Error 429: ActiveX component can't create object is an example of this. First, make sure you are running EditScript 8.0.57 or higher. If you still encounter problems afterward it is recommended that you try a "Detect and Repair" in Microsoft Word. There are instructions on page 10 of this document on how to do this.
Q: I am running Vista and am having problems inserting Templates, how can I fix this?
A: Internet Explorer 8 is not yet supported with EditScript, you may experience errors with templates if you are using Internet Explorer 8. Otherwise, please install the Microsoft fix located at
Q: What does it mean if I get communication errors?
A: Please refer to the Connection Problems and Communications Errors section in this document on page 16.

Q: How do I fix a "Value cannot be null, Parameter value:ptr" error?
A: This error should only occur on Vista 64 bit Operating Systems. Currently, Vista 64-bit edition is not supported by EditScript version 8 or version 9. Vista 32-bit edition is the only Vista version that currently works with EditScript.

Q: How do I fix the "Microsoft Word was unable to load a custom eScription addin" Macro Security problem?
A: In Word 2003 this is often fixed with a "Detect and Repair" of Microsoft Word (Page 10).
In Word 2007, there is an option for that is set to disabled by default which needs to be enabled:

  1. Click on the Office Icon in the top left corner
  2. go to Word Options -> Trust Center -> Trust Center Settings -> Addin
  3. Make sure the “Disable all application Add-ins” option is unchecked

Additional Information

This may have been caused because your Macro Security Level is set to 'Very High'. In order for EditScript MT to function with your Macro Security Level set to 'Very High', you must add the EditScript MT installation directory to the list of Trusted Locations within Microsoft Word.

Current Workaround:
The available workaround continues to be that users should set Word macro security to Low.  For instructions on manually setting the macro security level in Microsoft Word, please visit one of the following links that are applicable to the Word version running on the EditScript machine.  Please note that before following the steps outlined in the links below, all instances of Word or applications that use Word (such as EditScript MT and Microsoft Outlook) must be closed.

Further Actions:
We are currently rebuilding the newest versions of EditScript MT 8 and EditScript MT 9 with updated certificate files which will subsequently allow users to set their macro security level back to higher levels if installed.  We hope to have these installers deployed by 5/28.  We are also continuing to investigate other options and will provide ongoing communication as we have it.

Q: How can I fix the “No Database URL is specified in the EditScript MT Options file” error?
A: This error occurs when a needed setting is missing from this localOptions.xml file in the EditScript Directory. The localOptions.xml file should have an entry like:

            <name>Login Location</name>
            <value>mhhs</value>             <-institution name here is probably missing

This has been documented in development case 18738 and it is best to contact eScription support to fix the issue.

Q: How do I fix a “Winword has terminated unexpectedly” error?
A: It is recommended that you upgrade to the latest version of EditScript first. This alone can resolve the error sometimes. If you continue to have issues after re-installing EditScript, please try a "Detect and Repair" in Microsoft Word. There are instructions on page 10 of this document on how to do this.

Q: How do I fix a "No Database URL Specified…" error?
A: This is a problem with a specific file called localOptions.xml that controls login information to EditScript. Please report this problem to eScription Support so Support may manually fix the problem on your computer.

Other FAQs

Q: How do I determine which version of EditScript I am running?
Version 6

  1. Select eScription from the Menu Bar at the top
  2. Select About EditScript from the drop-down menu
  3. A new window should pop up showing you what version you are running

Version 8 & 9

  1. Go to the eScription Menu Bar on the right and select Help from the drop down menu
  2. Select About EditScript MT
  3. A new window should pop up showing you what version you are running

Q: I have problems with my contact files and/or CC list, how can I fix this?
A: The easiest thing to try to fix this problem is to delete the contact files and then restart EditScript MT. To do this, try the following:

Version 6

  1. Navigate to C:\Program Files\eScription\EditScript
  2. Locate all files with the prefix "Contact" and delete them
  3. Log back into EditScript MT and allow the program to re-download the contact files

Version 8 & 9

  1. Navigate to C:\Documents and Settings\<user name>\Application Data\eScription\EditScriptMT
  2. Locate all files with the prefix "Contact" and delete them
  3. Log back into EditScript MT and allow the program to re-download the contact files

Q: Where do I find necessary Microsoft Office & Microsoft Word Updates?
A: Microsoft Windows Updates and Microsoft Office Updates can be found at

Q: How do you remove eScription Dictionaries?
A: The eScription Dictionaries are located in the following path by default: C:\Program Files\eScription\EditScript\
The filenames for the dictionaries are as follows: escription0.dic, escription1.dic, escription2.dic, escription3.dic, escription4.dic
To disable the installed eScription dictionaries please remove all five eScription dictionary (.dic) files from the installed directory. Be aware, when upgrading to newer versions of EditScript-MT the dictionaries are automatically re-installed.

Q: Why is EditScript MT slow or unresponsive?
A: Your computer may not meet the minimum requirements for EditScript. Please check the specifications listed on page 2 of this document. You can also check the Windows Task Manager to determine if there are other programs that might be slowing down your computer:
  1. Press control-alt-delete once
  2. Select Task Manager
  3. Click on the Processes tab
  4. Click on the CPU column header to sort by processor usage
Only the System Idle Process should have a number in the CPU column higher than 50. If other programs have consistently high numbers, it could indicate that that process is causing the problems.

Q: My Red Box cursor isn't showing up, what can I do to fix this?
A: For Windows XP try changing the display theme on your computer by doing the following:

  1. Right-click on the desktop
  2. Click on Properties
  3. Click on the Themes tab
  4. Select either the Windows XP or Windows XP modified theme

Q: How can I get my templates to open up in EditScript and not in a separate Word window?
A: Please refer to the "Adjusting .doc file extensions for Template Issues" section on page 21.

Q: Exactly what versions of Word are supported with EditScript?
A: The versions are as follows:

2007 Office products (versions 8 and 9 only)
  • Office Basic
  • Office Standard
  • Office Home and Student
  • Office Small Business
  • Office Professional
  • Office Professional Plus
  • Office Enterprise
  • Office Ultimate

2003 Office products
  • Office Basic
  • Office Home and Student
  • Office Standard
  • Office Small Business
  • Office Professional
  • Office Professional Enterprise

Q: EditScript is “shadowing” text and the screen is “super-imposing” itself. How can I fix this?
A: This is most likely because the default background color is set to a color other than white. Please follow the below steps to ensure your color settings are correct:

In Windows XP

  1. Go to the Start Menu, and then to Control Panel
  2. Click on Display and another window should pop up.
  3. Click on the Appearance tab
  4. Click on Advanced and a new window should pop up
  5. Click on the Item drop down box and navigate to Window at the bottom
  6. With Window selected, make sure the Color1 box is set to white (top left)

In Windows Vista

  1. Right Click anywhere on the Desktop
  2. Click on Windows Color and then Appearance. This will bring up a new window.
  3. Click on Advanced in the lower right
  4. On the drop down list under Item please choose Desktop.
  5. On the drop down list of Color 1: select White

Q: My Word Toolbars aren’t working with EditScript, how can I fix this?
A: This is probably due to a Global Word Template file called “Normal.Dot” becoming corrupted. In order to fix this you will want to:

  1. Close out all Word Documents
  2. Press CTRL+ALT+DELETE and go to Task Manager
  3. Make sure that “WINWORD.EXE” isn’t running in the Processes Tab
  4. Navigate to C:\Documents and Settings\user name\Application Data\Microsoft\Templates and rename the “” file
  5. Open Word and this should create a new “”

The downside to this method is that all shortcuts and text autocorrect entries are still in the old corrupted “”.