Broadcast_status.
	Device_status.

Broadcast_Status

BcoComp generates a Broadcast_Status alarm, when it encounters an error while it is generating the job or placing it in the active folder of the device.

An alarm is raised with one of the following error messages.

Note: The message depends on the situation.

Problem in Opening GenFld.

Problem in Opening the CAF File XX.

Device Not selected in Function Block by user.

Problem in Opening CMA.sta (Common Memory Area) File)

Device XX Not Available (Problem in getting Device handler).

Problem with the Spooler of device XX.

Problem in creating Page in Spooler of device XX.

Problem in posting the Data to device XX.

Failed to retrieve Device Information.

Problem in creating MemoryMapFile.

Failed to retrieve Device Information.

Problem in creating MapView for MemoryMapFile.

Unable to retrieve job information from the device.

Problem in getting Device handle.

Problem is setting the Job Priority.

Problem in creating Directory for spooling files in Device XX.

Problem in saving the data in spool Directory.

Problem in Creating AccessToken for CMA.

Fetch & Merge Failed

Device XX is down.

Problem with External Source (Solve API).

Problem with External Source (Tracker API).

Problem with External Source (Extended Tracker API).

Data Fetch Failed on WYSIWYG Broadcast.

The print job was aborted.

Problem in Opening the CWF File XX.

WYSIWYG Form has no Objects.

Problem loading the WYSIWYG Form.

Invalid WYSIWYG form, may be an ASCII form or any Text File rename to WYSIWYG.

Solve 'XX' used in form 'XX' returned multiple values.

The print job was aborted for an unspecified reason.

The print job was aborted because the user clicked the Cancel button in the dialog box that displays the status of the print job.

The print job was aborted because the user canceled it through the operating system shell.

The system is out of disk space, so no further printer data can be spooled.

The system is out of memory, so no further printer data can be spooled.

Data is not available for some of the Generic Fileds.

Device_Status

BcoComp generates a Device_Status alarm, when it encounters an error on the device or job that is sent to the device.

An alarm is raised with one of the following error messages.

Note: The message depends on the situation.

Device XX is paused.

Device XX is in an error state.

Device XX is deleting a print job.

Paper Jam in the Device XX.

Device XX is out of paper.

Device XX is in a manual feed state.

Device XX has a paper problem.

Device XX is offline.

Device XX is in an active input/output state.

Device XX is busy.

Device XX is printing.

Device XX's output bin is full.

Device XX is not available for printing.

Device XX is waiting.

Device XX is processing a print job.

Device XX is initializing.

Device XX is warming up.

Device XX is low on toner.

Device XX is out of toner.

Device XX cannot print the current page.

Device XX has an error. User intervention needed.

Device XX has run out of memory.

Device XX door is open.

Device XX status is unknown.

Device XX is in power save mode.

 

Job on device JJ is paused.

An error with the job in device JJ.

Job is being deleted on device JJ.

Job is spooling on device JJ.

Job is printing on device JJ.

Device JJ is offline.

Device JJ is out of paper.

Job has printed on device JJ.

Job has been deleted from device JJ.

The driver cannot print the job on device JJ.

Device JJ has an error. User intervention needed.

Job on device JJ has been restarted.

Job is sent to the device JJ.

More information

Broadcast troubleshooting.

---