Troubleshoot File Drop Integration

For information about how to configure a File Drop integration, see File Drop Integration. For information about managing access to integrations, see Controlling Access in Spectrum.

Important! Whenever you add a new device, data service, integration, or facility, you must ensure that the service is activated on all Spectrum Application Servers on which it should be available to run and started on at least one. In an environment with only one Spectrum Application Server, these types of services are automatically activated and started when they are created. For more information, see High Availability with Distributed Services.

Important! In an environment with distributed services, to permit a user to perform administrative tasks related to services you must assign Read and Write permissions for Servers. These permissions must be assigned for each server in Access Control . Examples of administrative tasks related to services include creating a data service, a device connection, an integration, or a facility. Core services can only be configured by the SuperAdmin or SystemAdmin user.

Tip: You can check the version of Loftware Spectrum and obtain information about its components, the Spectrum Application Server, and your Spectrum license (including the integrations allowed) by clicking Help Help > About.

Symptom	Resolution
No print job files are printing	You must determine whether the issue is due to the integration, the process and business rule, or the device and device driver. One of the following approaches may resolve the issue: Verify that the integration is running by checking for the presence of the Stop Integration button in the File Drop integration. If it is not running, click Start Integration. Verify that the Scan Folder exists and is accessible. If Spectrum has been able to access the Scan Folder, it contains three subfolders (error, processed, and processing). If they are deleted, they are automatically re-created. If the preceding approaches do not resolve the issue, see the resolutions listed in the following row.
One or more print job files are not printing	One of the following approaches may resolve the issue: Verify that the job file has one of the file extensions specified in the File Drop integration. Ensure that the Polling Interval is not excessively long. 1000ms is equivalent to 1 second. 999,999,999ms is equivalent to 11.5 days. If FIFO is selected, check whether a file of a recognized file type is in the Scan Folder and is locked. (A file may be locked if it is open for editing.) If so, either unlock the file, remove the file, or clear the FIFO check box. Click Status and search for job files that were submitted but not printed. For detailed information about a job, double-click the job record. Also, with the job record selected, click the Information title bar at the bottom of the right column to expand the Information pane and display more details about the job. To obtain information to help diagnose the issue, select Archive Original Job File and Archive XML and then resubmit the job. If the Archive Original Job File and Archive XML options are selected, the job file should appear in the Scan Folder and then move to one of its subfolders. Scan Folder: If the job is in this folder, it has not yet been processed. Ensure that files in this folder are not locked. Files should not be edited in this folder. processing: If the job is in this subfolder, Spectrum has begun to process it. Ensure that files in this folder are not opened for editing or locked for any other reason. processed: If the job is in this subfolder, it has been completed successfully. error: If the job is in this subfolder, Spectrum attempted to process it but encountered a problem. The .err file associated with the job may provide information about the problem. If it indicates that the job file was not parsed correctly and if the Validate XML check box is cleared, select Validate XML and submit the print request again. Tip: A .err file is created in the error subfolder only if the error occurs before processing begins. Otherwise, the error is listed in Status instead. Note: After you have resolved the issue, it is recommended that you clear Archive Original Job File and Archive XML so that you do not accumulate unnecessary archive files. Selecting these options generates the files in the processed folder.
Print jobs are not being routed to the expected device	Review the Device Name field. To route all print jobs to the same device, enter a device name in this field. To allow print jobs to be routed to the device specified within the print job, leave this field blank.
Code 10008 under Job Error	If you clicked Status, double-clicked a job record, and Code 10008 was displayed, then the Run As user account for the integration may not have the necessary object access permissions Permissions in Spectrum associated with a specific object or with a folder that control what actions can be performed on that object or on objects within that folder. Each object has default permissions that can be overridden by exceptions for a specific group or user. A user must have both a role-based permission and the corresponding object access permission to perform an action on an object. for an object used by the job. For more information, see Configuring a Run As User for Integrations.
Code 10016 under Process Errors	If you clicked Status, double-clicked a job record, clicked a row in the Process Errors table, and Code 10016 was displayed, then the job file may include an incorrect path. Correct the path and copy the job file to the Scan Folder again.
Performance when using File Drop integration is too slow	Any of the following configuration changes may improve performance. Ensure that the Archive Original Job File and Archive XML check boxes are cleared. Evaluate whether the Polling Interval is appropriate. 1000ms is equivalent to 1 second. 999,999,999ms is equivalent to 11.5 days. Clear the FIFO check box. Clear the Validate XML check box. If you do not need to restrict print jobs to a particular device, clear the Device Name field.