Macro and API Error Messages

14000
"Macro Engine creation failed (ERR=<xxxx>).  Macro support will be disabled for this session."
Explanation: PASSPORT was unable to create the engine required to run .zmc macros.
   
User response: This error generally occurs when the passmac.dll file required to run the macro scripting engine is missing or has not been registered properly on your system.  Follow the steps below to resolve:
  1. Perform a search to make sure the passmac.dll file exists on your system.  This file normally resides in the C:\Program Files\PASSPORT or installed directory.  If it is missing, copy it from a working system, or reinstall PASSPORT PC TO HOST to restore the file.
  2. At the Run command line (from the Start Menu), type the following command:
    regsvr32 "C:\Program Files\PASSPORT\passmac.dll"
    This will register the passmac.dll file with the operating system.
    OR
  3. Reinstall PASSPORT.
14001
"An error occurred on line <LineNumber>, position <ColumnNumber>, of the script. <Details>"
Explanation: A macro scripting error occurred at the specified location.
   
User response:
  1. Use the error message details to determine the reason for the error.
  2. Edit your macro accordingly.
PASSPORT macros use VBScript. More information on VBScript functionality is available through Microsoft's VBScript Reference: http://msdn.microsoft.com/en-us/library/d1wf56tt.aspx
   
14003
"An error occurred reading the macro. Unable to execute."
Explanation: Failed to load the macro file.
   
User response:
  1. Ensure that the macro exists in the selected location. To remap the appropriate function to an existing macro with a valid path, select the appropriate function from the following:
    - Using the Keyboard
    - Using the Toolbar
    - Using the Keypad
    - Using Hotspots
    - Using the Mouse
  2. Ensure that the file is a valid .zmc or .zam PASSPORT macro.
  3. Ensure that you have at least read permissions to the macro.
14004
"Creating the ActiveX Scripting engine failed.  Scripting engine is probably not correctly registered or CLSID incorrect."
Explanation: Failed to create the VBScript Scripting engine.
   
User response:
  1. Ensure that the vbscript.dll file exists in your Windows System32 directory.
  2. Check the version of the vbscript.dll file in your Windows System32 directory to ensure that you are using the most recent version.
  3. After verifying that the vbscript.dll file exists and is up-to-date, ensure that the vbscript.dll file is properly registered. At the Run command line (from the Start Menu), type:

    regsvr32 "C:\Windows\System32\vbscript.dll"

    This will register the vbscript.dll with the operating system.
14005
"ActiveX Scripting engine does not support IActiveScriptParse."
Explanation: You might not have a valid version of Vbscript.dll installed.
   
User response:
  1. Ensure that the vbscript.dll file exists in your Windows System32 directory.
  2. Check the version of the vbscript.dll file in your Windows System32 directory to ensure that you are using the most recent version.
  3. After verifying that the vbscript.dll file exists and is up-to-date, ensure that the vbscript.dll file is properly registered. At the Run command line (from the Start Menu), type:

    regsvr32 "C:\Windows\System32\vbscript.dll"

    This will register the vbscript.dll with the operating system.
14006
"Unable to run macro. Error connecting to the presentation space."
Explanation: Failed to connect to the presentation space of the emulation session.
   
User response:
  1. This error will occur if you are attempting to run a macro before a connection with the host has been successfully established. You can verify an active connection by selecting "Connection Log" from the Communication menu and looking for the text "Connected to <your host ip address:port number>"
  2. This error message can occur when a macro is started when there is an X-condition on the OIA line. To resolve the problem, clear the X-condition before running your macro.  Or, you can add functionality to your macro that checks and clears the OIA line before proceeding with the remainder of the steps in the macro.
14200
"Macro Engine creation failed (ERR=<xxxx>).  Macro support will be disabled for this session."
Explanation: PASSPORT was unable to create the engine required to run .zam macros.
   
User response: This error generally occurs when the passobj.dll, SAS7_000.DLL, or SAS7_CTL.OCX files required to run the macro scripting engine are missing or has not been registered properly on your system.  Follow the steps below to resolve:
  1. Perform a search to make sure these files exist on your system.  They normally reside in the C:\Program Files\PASSPORT or installed directory.  If they are missing, copy them from a working system, or reinstall PASSPORT PC to Host to restore the file.
  2. At the Run command line (from the Start Menu), type:

    regsvr32 "C:\Program Files\PASSPORT\xxxx.xxx"

    where xxxx.xxx is the name of the missing file.

    This will register the file with the operating system.
  3. Repeat this process for each of the 2 files (passobj.dll and SAS7_CTL.OCX).

    OR
  4. Reinstall PASSPORT.
14201
"An error occurred on line <LineNumber>, position <ColumnNumber>, of the script. <Details>"
Explanation: A macro scripting error occurred at the specified location in the .zam macro.
   
User response:
  1. Use the error message details to determine the reason for the error.
  2. Edit your macro accordingly.
PASSPORT .zam macros use SAX Basic Language which is Visual Basic for Applications (VBA) compatible.