Troubleshooting Automation of Microsoft Office Products


Many Users have the need to Automate using Microsoft Office Products. This Article will outline some troubleshooting steps when trying to automate these Jobs within JAMS. While this Article will speak about Excel, it can be applied to other Microsoft Office Products with minimal tweaks.



The Job executes but never finishes in JAMS.


When creating an Excel Job in JAMS, it may be necessary to run these Jobs in Interactive Mode. Many times when these Excel Jobs run they open Interactive Windows on the Server where they are executing.




Create a New Interactive Execution Method in JAMS

  1. Click on the Execution Method shortcut in the Configuration section.
  2. Select Add in the ribbon bar to open the Execution Method Definition Wizard.
  3. Select Next and give the Execution Method a name. For example, if the original Execution Method was Command, we might call this new Execution Method Command_Interactive.
  4. Select Next and choose Command as the Base Execution Method.
  5. Select Next and then check the Edit the Execution Method Definition after adding option. Then click Finish.
  6. When the Properties box opens, select the Source tab and check the Interactive option.
  7. Save and Close the Execution Method. It may be necessary to Refresh Execution Method view(s) to see the new Execution Method.
  8. Set the newly created Execution Method on your Interactive Microsoft Office Job(s). You can use the newly created Execution Method in the Job Creation Wizard when creating new Jobs, or set the Execution Method on any existing Job. To edit the Execution Method of an existing Job, open the Job Definition Properties and select the new Execution Method in the Job's Source Options.


Return to Top


Ensure Interactive Services Detection is Started

Now that the interactive Execution Method has been created and set on the Job, we need to ensure that the Interactive Services Detection service is turned on.

  1. Open Windows Services on the server where the Job needs to run. If this is a remote server, RDP into the server.
  2. Find the Interactive Services Detection service. If this service is not running, start the service.
  3. Users with Microsoft SQL 2012 will now see an error message. Users who do not experience this error may skip to step 9. This error appears because the Service is disabled by default in Microsoft Server 2012. We will resolve this error in the next steps. 
  4. To resolve the error, open Regedit.
  5. Navigate to
  6. Change the value of NoInteractiveServices from 1 to 0.
  7. Reboot the Server.
  8. Repeat steps 1 and 2.
  9. The Job can now be executed in JAMS. If the Job does not complete, it may require user input. Go to the server the Job is executing on and view the toolbar. If you see the Interactive Detection Service blinking, click on it and select View Message. This will allow you to see if the program may be prompting for any user input.


Return to Top


Resolve Jobs that fail with a Permissions or File not Found Error

If the Job runs but fails with a permissions error or cannot find a file, it may be necessary to modify the DCOM permissions on the server where the Job is executing.

  1. On the server where the Job is executing, open a Run box and type in dcomcnfg.exe to open Component Services.
  2. Navigate to DCOM Config, located at Component Services>Computers>My Computer>DCOM Config.
  3. In the middle pane, right-click Microsoft Excel Application and select Properties to open the Microsoft Excel Application Properties window.
  4. On the Identity tab, select This User, then enter the information for the JAMS User that is executing the JAMS Job.
  5. Navigate to the Security tab. Note there are three permissions sections: Launch and Activation Permissions, Access Permissions, and Configuration Permissions.
  6. For each of the three permissions sections, select Customize and then Edit to open the Permission Properties. Give the JAMS user that is executing the Job Full Permissions in each section.
    NOTE: If the JAMS user is a local administrator on the server where the Job is executing, this step is not necessary.
  7. The Job should now complete successfully.


Return to Top


Have more questions? Submit a request