Job SEND_SYSTEM_RELATIONSHIP_TO_SUPPORT aborts

Hi all,
for some reason the Job SEND_SYSTEM_RELATIONSHIP_TO_SUPPORT (Step: AI_SC_SEND_SYSTEM_RELATIONSHIP) aborts at every execution.
The Job Log looks like:
- Job started
- Step 001 started (Program AI_SC_SEND_SYSTEM_RELATIONSHIP, Variant , Username xyz)
- SLM set as administrating Solution-Manager-System
- Following Errormessages returned from SAP Support Portal:
- Job aborted after System-Exception ERROR_MESSAGE
Does anyone know what could be the reason?
Regards,
Benjamin Ziegler

Hi Afi,
I have deleted the job and recreated it manually; now it runs fine!
Thanks for the quick help?
I only don't understand the note you are referring to; are you sure it's the right note number?
Best regards,
Koen

Similar Messages

We are running 3 batches parallel(a.ksh,b.ksh,c.ksh parallel ) .if a.ksh will complete then d.ksh will start('d' start when 'a' will terminate successfully) and we have to handle error for all jobs ( if some job got aborted during runtime) ?

we are running 3 batches parallel(a.ksh,b.ksh,c.ksh parallel ) .if a.ksh will complete then d.ksh will start('d' start when 'a' will terminate successfully) and we have to handle error for all jobs ( if some job got aborted during runtime) ?

Moderator Action:
You already asked this question, two days earlier.
https://forums.oracle.com/thread/2585158
Stay with your original post. Deliberate multiple posting is the same as spamming the forums.
This new post is locked.

Business Objects R3 Adapter v1.74 causing jobs to abort

I've already filed a case with tech support, but I was wondering if anyone has experienced this problem with the Business Objects R3 Adapter version 1.63-1.74 where the Tidal job gets launched and then almost instantaneously gets aborted. And if there are subsequent Tidal jobs dependent on that aborted job, then those jobs will never get run (stuck on Waiting on Dependencies...) until the job status gets manually set from Aborted to Completed Normally*
The pattern is random, and the BO reports are being generated, it's just the Tidal job status returns Aborted when the external id cannot be found. Any suggestions?
Thanks,
Derrick

I've already filed a case with tech support, but I was wondering if anyone has experienced this problem with the Business Objects R3 Adapter version 1.63-1.74 where the Tidal job gets launched and then almost instantaneously gets aborted. And if there are subsequent Tidal jobs dependent on that aborted job, then those jobs will never get run (stuck on Waiting on Dependencies...) until the job status gets manually set from Aborted to Completed Normally*
The pattern is random, and the BO reports are being generated, it's just the Tidal job status returns Aborted when the external id cannot be found. Any suggestions?
Thanks,
Derrick

How to send mail after job abort

Hi,
how can I send an email when a job is aborted? Or is there a system event if a job aborts?
Thanks for your help
Lutz

You might want to look into ABAP. Basically a generic job that would get called, to send email, whenever a certain job "aborts", but then you'd also need a wrapper job for detecting the bad return code. help.sap.com has some info on that (using events to trigger jobs), like this:
http://help.sap.com/saphelp_47x200/helpdata/en/fa/096f33543b11d1898e0000e8322d00/frameset.htm
or this (the full-control method)
http://help.sap.com/saphelp_47x200/helpdata/en/fa/096f33543b11d1898e0000e8322d00/frameset.htm
CCMS can also monitor job status too, as the other poster said,
http://help.sap.com/saphelp_47x200/helpdata/en/fa/096f33543b11d1898e0000e8322d00/frameset.htm
however it's very limited. Especially if you want to use logic for the alerts (ie only certain jobs should alert upon failure, certain times of day, recipients, etc). It's all possible with CCMS, I've seen it done before using scripts that read CCMS external alerting but it's probably easier just adding event triggers to your critical jobs.

Contact sheet print job aborted in snow leopard

Recently upgraded to snow leopard. When printing a large contact sheet of over 50 raw files the print job is aborted. Printing to a HP Z3100. Nailed it down to amount of data 50 pics at 20mb each seems to be limit. No problem under Leopard. I can convert the files to Jpg and print 80 of them, file size is 1/3. Anyone run into this issue?

Hmm.. Can't say as I've seen that, and I've printed more than 120 photos 12+meg at a time (including some 80meg tif files). Don't know what it might be... how's your scratch space, or the space on your main disk?
Cheers!

Printing Problem - Incomplete multiple page print job - until paper runs out

I'm on Mac OS 10.9.3 printing to a Samsung CLX-6250FX. This is a network printer used by all the Apple/Window computers in this office.
I am having terrible problems recently with printing multiple page documents - excel, word, email, pdf etc. I am spending a fortune in paper and printer cartridges.
The print job does not complete and the last page printed, the following message prints:
ERROR: syntaxerror
OFFENDING COMMAND: true cvt Tfpgm nglyf ' ^ head
STACK:
-mark-
/sfnts
Then the same printer job restarts and fails at the same point until the printer tray runs out of paper (unless the print job is aborted and/or the printer is turned off and turned on again)!!
The specific error message displayed by the printer software is either "Remote host did not accept data file (32)" or "Remote host did not accept data file (105)".
I haven't seen any pattern whatsoever in terms of application used.
I have deleted the printer and reloaded the driver from the disk supplied with the printer. I have checked to see that I am running the most recent driver.
I've already reset the printing system, but that didn't fix it.
I have seen this problem on various support communities pages, but for different printers.
I have yet to see a solution - Any other recommendations please?

The error message you see printed is a Postscript error. With your printer, postscript (normal output type from applications) is converted to the printer's page description language before being sent to the printer. So, I believe the problem is in some part of the driver software.
For first step, I would try restarting from the Recovery partition and repair the hard drive using Disk Utility. You can repair permission, too. This is trying to correct a corrupted file.
http://support.apple.com/kb/ht4718
(just read the first paragraph)
If that doesn't fix it, I would try downloading and installing the latest driver for the printer.
Come back for more if that still doesn't work.

Reg: Function Module thats used to check the status of JOBS and mail it

Hi Experts,
Is there any Standard Function module thats going to find the status of the jobs and mail this status to specied email ID in .xls format. While checking status function module should give whether job is - Aborted, Successful, Running, Waiting, Locked, Error, Warning, Starting Date, Ending Date of the Job.
Please help me,

Hello Nagaraj,
You can find out the status of a job with the SHOW_JOBSTATE function module. You provide this function module with a job name and job number. It returns one of the six possible statuses of the job:
ABORTED TYPE C,
FINISHED TYPE C,
PRELIMINARY TYPE C,
READY TYPE C,
RUNNING TYPE C,
SCHEDULED TYPE C.
Following is the link for the same:
http://help.sap.com/saphelp_sm32/helpdata/en/fa/096e10543b11d1898e0000e8322d00/content.htm
Warm Regards,
Riki Dash

Cancelling PeopleSoft job if running longer than max time

We have some PeopleSoft jobs that we want Tidal to automatically cancel if they are still running after 2 hours, then automatically set the job to Completed Normally so the next job in the jobstream will start running. We tried using a Job Event triggered by "Job running longer than its maximum time", with Selected Action = "Set To Completed Normally". The problem is that it sets the job to completed normally on Tidal, but the job continues to run on PeopleSoft. In other words, it's not cancelling the job.
Next, we changed the Selected Action to "Cancel/Abort". This worked in terms of cancelling the job on PeopleSoft, but we can't figure out how to automatically set the job to Completed Normally on Tidal after the job is cancelled. There is an Event Trigger for "Operator cancelled the job", but apparently the event isn't triggered if Tidal cancels the job. We also tried using Event Trigger = "Job completed", but that didn't work either since apparently Tidal doesn't consider a job in Aborted status as completed.
Anyone have any other ideas on how to automatically cancel a PeopleSoft job and then automatically set the Tidal job to Completed Normally? Thanks.

Hello Richard,
I would use the sacmd (windows) or the tesmcmd(Unix) to interact with the given job so to set it to whatever status you want ;
- You have to first let the event Cancel/Abort it if running longer than expected by using the built in function (Cancel)
- Then using the same event you need to trigger another job action that has the above tesmcmd command to set the job to Normally completed; for this you may need to create a new job that calls the tesmcmd/sacmd and then use jobset command.
now you need to create a job action that triggers that job which will allow you to override the command parameters especially the RunID of your failed job.. hope i was able to get it right unless if you already figured that out.
-rami

Job Schedule Sun thru Thurs only via TVARV using variant

Can someone tell me how to use TVARV to setup my job to run only on Sunday thru Thursday using my variant?

Hi,
Please check the below links.
http://help.sap.com/saphelp_nw04/helpdata/en/c0/9803aae58611d194cc00a0c94260a5/content.htm
Some sample code from seachsap site.
Have you ever wondered where your TVARV variables are being used in your batch jobs? How do you know if they change, and the impact it may have on your interfaces? The program below will provide a listing for you.
The program uses Job Count (job id) as the key versus Job Name as job names can be redundant. The code was written in R/3 v.4.6C, but should work in 3.x versions as well.
Code
PROGRAM: ZCAUS_EXTRACT_REPORT_VARIABLES
AUTHOR: DYLAN HACK
CREATE DATE: 10/09/2002
PURPOSE: This program was developed to extract all jobs based on the
         "Job Status" selection criteria and find the relevant TVARV
         variable entries. Then the report can be downloaded and
         sorted on selection variables. Ultimate purpose is to know
         what jobs are affected by the individual TVARV variables.
         If a job exists but does not have a corresponding entry/use
         of a TVARV variable, it will not get listed.
JOB STATUS LEGEND:
R: job step running.
Y: job step ready (eligible to run, waiting for a work process).
P: job step scheduled.
S: job step released (eligible to run when the start condition of the
   job is fulfilled).
A: job step aborted.
F: job step successfully finished.
Z: system upgrade in progress, only upgrade-related jobs are allowed
   to run. Jobs and job steps with this status are ignored by the
   scheduler.
X: unknown status detected.
REPORT ZCAUS_EXTRACT_REPORT_VARIABLES .
tables: tbtcp, tbtco.
data: var like RSVARVAR occurs 0 with header line,
      begin of report_tmp occurs 0,
        jobname   like tbtcp-jobname,
        jobcount like tbtcp-jobcount,
        stepcount type tbtcp-stepcount,
        progname type syrepid,
        variant   type syslset,
      end of report_tmp,
      report like report_tmp occurs 0 with header line,
      begin of listing occurs 0,
        jobname type tbtcp-jobname,
        jobcount like tbtcp-jobcount,
        stepcount type tbtcp-stepcount,
        progname type syrepid,
        variant   type syslset,
        variable type rsvarvar-variable,
      end of listing.
selection-screen begin of block a1 with frame title text-001.
selection-screen begin of block b1 with frame.
select-options: s_status for tbtco-status.
selection-screen end of block b1.
selection-screen begin of block b2 with frame.
selection-screen comment /5(75) com1.
selection-screen comment /5(75) com2.
selection-screen comment /5(75) com3.
selection-screen comment /5(75) com4.
selection-screen comment /5(75) com5.
selection-screen comment /5(75) com6.
selection-screen comment /5(75) com7.
selection-screen comment /5(75) com8.
selection-screen end of block b2.
selection-screen end of block a1.
initialization.
move:
'R: Job Running' to com1,
'Y: Job Ready (Eligible to run, waiting for process)' to com2,
'P: Job Scheduled' to com3,
'S: Job Released (Eligible to run when start condition is trigerred)'
to
com4,
'A: Job Aborted' to com5,
'F: Job Successfully Finished' to com6,
'Z: Upgrade in process, job being ignored' to com7,
'X: Unknown Status Detected' to com8.
start-of-selection.
get all jobs in released status
select jobcount from tbtco into report_tmp-jobcount
    where status in s_status.
    append report_tmp.
endselect.
get all related variants for those jobs that meet the where clause.
loop at report_tmp.
    select jobname jobcount stepcount progname variant
    into corresponding fields of report
    from tbtcp where jobcount = report_tmp-jobcount and
                     variant not like '&%' and
                     variant <> space.
    append report.
    endselect.
endloop.
sort and delete duplicates (if any)
sort report by jobname jobcount stepcount progname variant.
delete adjacent duplicates from report comparing all fields.
get TVARV selection variables
loop at report.
clear var. refresh var.
call FUNCTION 'RS_VARIANT_VARIABLES'
    EXPORTING
       PROGRAM = report-progname
       VARIANT = report-variant
    TABLES
     VAR = var
    EXCEPTIONS
        VARINT_NOT_EXISTENT.
move the data to a listing table
if var-variable <> space.
   loop at var.
    move: report-jobname   to listing-jobname,
          report-jobcount to listing-jobcount,
          report-stepcount to listing-stepcount,
          report-progname to listing-progname,
          report-variant   to listing-variant,
          var-variable     to listing-variable.
    append listing.
   endloop.
endif.
endloop.
sort and delete dups from listing
sort listing by jobname jobcount stepcount progname variant variable.
delete adjacent duplicates from listing comparing all fields.
data: count type i. loop at listing. count = count + 1. endloop.
write out the listing
write: 'Count', count. skip.
write: 2   'Job Name',
       36 'Job #',
       48 'Step',
       54 'Program name',
       95 'Variant',
       110 'Variable'.
loop at listing.
    write: / listing-jobname,
             listing-jobcount,
             listing-stepcount,
             listing-progname,
             listing-variant,
             listing-variable.
endloop.
Thanks,
Ramakrishna

Can't clear a .ppt print job on an OfficeJet Pro L7680, attached to a Lenovo PC w Win7 32-bit

I was printing a .ppt print job that aborted and didn't complete. I tried to delete the print job. I tried to reset the printer. I turned the printer off/on. I took the printer offline/online. The print job won't clear and although I can submit new print jobs, the printer can't print anything else (because of the .ppt job that can't be cleared). I was using the HP Solutions Center (HP print utility on my laptop)) and Windows print tools. Any thoughts on what I can do to clear this print job?

Delete the printer in Control Panel as it appears it is hung up (if there is more than one instance of it, delete them all).
Next, re-add the printer in this manner:
1. Make sure the printer is turned on and connected to your network. Verify that you can access the printer's internal web page by browsing to its IP address before continuing.
2. Click >> Start >> Control panel >> Devices & Printers.
3. Click the Add a printer
4. Select Local printer
5. Select Create a new port and select Standard TCP/IP Port and click Next button.
6. Under Device type, select TCP/IP Device. Under Hostname or IP address, enter the printer's IP address. Click Next.
7. Select Hewlett-Packard from the list of manufacturers and select and select your printer model. Click Next.
If your printer model was not listed, then select Have Disk, browse the HP CD that came with your printer and select the first file that starts with hp and ends with inf. Click Open then OK. Select your printer model. Click Next.
8. If you are asked, use the currently installed driver.
9. It will ask for the Printer name -- enter a new name or use the existing one. This will be the name of the printer that you select from other applications.
10. You may be asked to share the printer. Choose NO.
11. The Print Test Page box appears. Go ahead and print it.
12. Click Finish.
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

Changes to write optimized DSO containing huge amount of data

Hi Experts,
We have appended two new fields in DSO containg huge amount of data. (new IO are amount and currency)
We are able to make the changes in Development (with DSO containing data). But when we tried to
tranport the changes to our QA system, the transport hangs. The transport triggers a job which
filled-up the logs so we need to kill the job which aborts the transport.
Does anyone of you had the same experience. Do we need to empty the DSO so we can transport
successfully? We really don't want to empty the DSO's as it will take time to load?
Any help?
Thank you very muhc for your help.
Best regards,
Rose

emptying the dso should not be necessary, not for a normal dso and not for a write optimized DSO.
What are the things in the logs; sort of conversions for all the records?
Marco

HP Laserjet P4014 Stopped – 'Filter' failed

I’ve seen discussion of this for other printers and versions of OS X. Has anyone seen this on 10.9.5 and, better still, solved it?
If I try to print to a networked HP Laserjet P4014, the print queue gives up with the message
Stopped – ‘Filter’ failed
Things I have tried so far:
downloading new HP driver software
resetting the printing system
changing the computer network name
rebooting
The only effect of all this so far is having to put back the printer’s network name and password.
At best, I get 1 page printed, followed by a Postscript error.
The only workaround so far: print to PDF and print the PDF from a Linux machine.

As far as I can tell the critical thing is an RPC error. I trimmed quite a lot – I am not sure how informative this all is. I meantime also sent a tcpdump and sysdiagnose output to Apple via bug reporter so let’s see if they come up with something.
D [15/Oct/2014:11:39:44 +0200] [Job 21] 3 filters for job:
D [15/Oct/2014:11:39:44 +0200] [Job 21] cgpdftops (application/pdf to application/postscript, cost 25)
D [15/Oct/2014:11:39:44 +0200] [Job 21] pstops (application/postscript to application/vnd.cups-postscript, cost 66)
D [15/Oct/2014:11:39:44 +0200] [Job 21] /Library/Printers/hp/filter/hpPostProcessing.bundle/Contents/MacOS/hpPostProces sing (application/vnd.cups-postscript to printer/StaffMinor, cost 0)
D [15/Oct/2014:11:39:44 +0200] [Job 21] argv[6]="/private/var/spool/cups/d00021-001"
D [15/Oct/2014:11:39:44 +0200] [Job 21] envp[12]="SOFTWARE=CUPS/1.7.2"
D [15/Oct/2014:11:39:44 +0200] [Job 21] Looking up "print.ict.ru.ac.za"...
D [15/Oct/2014:11:39:44 +0200] [Job 21] STATE: -connecting-to-device
D [15/Oct/2014:11:39:44 +0200] [Job 21] Connected to printer...
D [15/Oct/2014:11:39:44 +0200] [Job 21] Set job-printer-state-message to "Connected to printer...", current level=INFO
D [15/Oct/2014:11:39:44 +0200] [Job 21] job id is 30...
D [15/Oct/2014:11:39:44 +0200] [Job 21] Sending print data...
D [15/Oct/2014:11:39:44 +0200] [Job 21] Set job-printer-state-message to "Sending print data...", current level=INFO
D [15/Oct/2014:11:39:44 +0200] [Job 21] cgpdftops - using PPD file "/private/etc/cups/ppd/StaffMinor.ppd"...
D [15/Oct/2014:11:39:44 +0200] [Job 21] PS Matching Mode = AP_ApplicationColorMatching
D [15/Oct/2014:11:39:44 +0200] [Job 21] cgpdftops - languageLevel = 3, mediaBox.size.width = 595, mediaBox.size.height = 842
D [15/Oct/2014:11:39:44 +0200] [Job 21] cgpdftops - documentMediaBox.size.width = 595, documentMediaBox.size.height = 842
D [15/Oct/2014:11:39:44 +0200] [Job 21] Page = 595x842; 12,12 to 583,830
D [15/Oct/2014:11:39:44 +0200] [Job 21] slow_collate=0, slow_duplex=0, slow_order=0
D [15/Oct/2014:11:39:44 +0200] [Job 21] Before copy_comments - %!PS-Adobe-3.0
D [15/Oct/2014:11:39:44 +0200] [Job 21] %!PS-Adobe-3.0
D [15/Oct/2014:11:39:44 +0200] [Job 21] PID 38050 (/usr/libexec/cups/filter/cgpdftops) exited with no errors.
D [15/Oct/2014:11:39:44 +0200] [Job 21] Wrote 4 pages...
D [15/Oct/2014:11:39:44 +0200] [Job 21] Calling processor PageCounting before line %%Page: 4 4
D [15/Oct/2014:11:39:44 +0200] [Job 21] PID 38051 (/usr/libexec/cups/filter/pstops) exited with no errors.
D [15/Oct/2014:11:39:44 +0200] [Job 21] Calling processor PageScanning before line %%Trailer
D [15/Oct/2014:11:39:44 +0200] [Job 21] Final number of pages = 4
D [15/Oct/2014:11:39:44 +0200] [Job 21] Pages per copy = 4
D [15/Oct/2014:11:39:44 +0200] [Job 21] Allowing document iterator to handle job termination...
D [15/Oct/2014:11:39:44 +0200] [Job 21] Pre-processing tasks
D [15/Oct/2014:11:39:44 +0200] [Job 21] Current page number is 4
D [15/Oct/2014:11:39:44 +0200] [Job 21] Calling processor PageAccounting after line %%Page: 4 4
D [15/Oct/2014:11:39:44 +0200] [Job 21] PAGE: 4 1
D [15/Oct/2014:11:39:44 +0200] [Job 21] rpc_write_printer: RPC error 0x16c9a036
D [15/Oct/2014:11:39:44 +0200] [Job 21] RpcWritePrinter error -1!
D [15/Oct/2014:11:39:44 +0200] [Job 21] Cleaning up printer-state-reasons...
D [15/Oct/2014:11:39:44 +0200] [Job 21] STATE: -apple-job-blocked,job-completed-successfully,job-canceled-at-device,processing -to-stop-point,apple-job-error,offline-report,media-needed-warning,paused-report ,job-completed-successfully,job-printing,apple-job-restart,job-incoming,apple-jo b-intervention,apple-printer-busy,door-open-warning,apple-printer-errorstate,app le-printer-warming-up,apple-printer-active,apple-printer-manual-feed,apple-print er-unavailable,marker-supply-empty-report,offline-report,output-area-full-report ,interpreter-resource-unavailable-warning,apple-printer-page-punt,media-jam-warn ing,media-empty-warning,media-jam-warning,paused-report,apple-printer-deleting,a pple-printer-lowpower,apple-printer-printing,apple-printer-processing,offline-re port,apple-printer-unknown,toner-low-report,apple-printer-intervention,apple-pri nter-waiting,apple-printer-warming-up
D [15/Oct/2014:11:39:44 +0200] [Job 21] Aborting print job
D [15/Oct/2014:11:39:44 +0200] [Job 21] rpc_abort_printer: RPC error 0x16c9a060
D [15/Oct/2014:11:39:44 +0200] [Job 21] rpc_close_printer: RPC error 0x16c9a060
D [15/Oct/2014:11:39:44 +0200] [Job 21] Ready to print.
D [15/Oct/2014:11:39:44 +0200] [Job 21] Set job-printer-state-message to "Ready to print.", current level=INFO
D [15/Oct/2014:11:39:44 +0200] [Job 21] smb backend (PID=38058) exited with no errors
D [15/Oct/2014:11:39:44 +0200] [Job 21] smb backend will exit with status 0
D [15/Oct/2014:11:39:44 +0200] [Job 21] PID 38052 (/Library/Printers/hp/filter/hpPostProcessing.bundle/Contents/MacOS/hpPostProce ssing) stopped with status 1.
D [15/Oct/2014:11:39:44 +0200] [Job 21] Hint: Try setting the LogLevel to "debug" to find out more.
D [15/Oct/2014:11:39:44 +0200] [Job 21] End of messages
D [15/Oct/2014:11:39:44 +0200] [Job 21] printer-state=3(idle)
D [15/Oct/2014:11:39:44 +0200] [Job 21] printer-state-message="Filter failed"
D [15/Oct/2014:11:39:44 +0200] [Job 21] printer-state-reasons=none
E [15/Oct/2014:11:44:45 +0200] [Job 21] Stopping unresponsive job.

HP Officejet Pro 8500 : Use scanner without print heads/cartridges

Hello.
I have a HP Officejet Pro 8500 (CB023A) that I bought specifically because of the automatic duplex scanner. Buying a scanner with automatic duplex instead of this multifunction printer was out of the question because the cheapest one costed over ten times more than this multifunction printer (and they still do).
I can no longer afford to keep buying print heads and cartridges just to use the scanner, as this multifunction uses ink for scanning!!! But that is beside the point.
I have read in other posts about taping sensors but I was thinking about going a little further and completely remove the printing part of the multifunction. Anyone knows if I can just disconnect the printing part from the circuit board? Or will I have to fiddle with software? Maybe some hidden option in the "Mfg Commands" (accessible by pressing * and # with the printer on) or some other hidden feature?
Considering that this multifunction takes way too long to boot because of all the print head checking/cleaning/etc, with a little luck, without the printing part the boot time will decrease to almost nothing .
Before I start disassembling I would appreciate some advice, specially if someone else has already tried it.
Thank you in advance.

Hello kamath27. Thank you for your reply.
I apologize for not replying sooner but I wanted to try and disassemble the multifunction before replying instead of just replying with an acknowledge.
Also, sorry for such a long post but I wanted to be as detailed as possible.
However, before describing what I did and found, I want to clarify something.
With the multifunction in the same condition it came from the factory, if I remove one print cartridge, or one is empty, the multifunction stops on boot with a message requesting to change the cartridge before continuing and there is no way to bypass it. When this message shows, pressing any button on the multifunction or the screen yields no result (there is no OK button displayed on the multifunction screen). It was always like this and firmware updates never solved it.
And going to the printer control panel on the connected computer says that the printer is offline even if it is connected through USB and is displayed in device manager as a connected USB device. This is the reason why I had spent so much money buying ink that I do not use. I never print anything on this multifunction. All prints that the multifunction ever performed were a dozen or so of maintenance align and test pages.
Now for what I did. I disassembled the multifunction just enough to take out the main circuit board, the wireless board, the buzzer and the door sensors. I set up the printer half and the scanner half side-by-side with the main circuit board in the middle, reconnected everything and turned it on in order to test if anything stopped working during disassembly. Everything was OK and the multifunction worked as normal (printed a test page and scanned it to the computer).
Next, while facing the main board the same way it would be faced while mounted in the multifunction, I started disconnecting the connectors (except the ones that belong to the scanner half) one by one from left to right in the following fashion: With the multifunction OFF, I disconnected one connector, turned the multifunction on, waited for any message or the main screen, tried to print a test page and then scan it, and finally disconnected the multifunction, reconnected the connector and moved on to the next one.
The results were:
- disconnected the tray feeding sensor -> Allows to boot with a paper jam message that can be bypassed with an OK on the screen. Can not print because of the alleged paper jam but can scan.
- disconnected the pump -> Allows to boot but a message keeps popping about pump motor stalled. Can be bypassed with an OK but pops right back and all jobs get aborted. Can not print or scan.
- disconnected the printer motor -> Oddly, no messages. Allows to boot and scan but not print. This was strange because when trying to print there is no message in the printer and the software on the PC only said the printer was busy. I would think the printer would eventually display a message saying the print carriage was jammed or something but nothing happened after 10 minutes. I might test again later as one test may be interfering with the next.
- disconnected the print cartridge door sensor -> Stops on boot with a message to close the door. Does not allow to print or scan.
- disconnected the print cartridges connector -> Stops on boot with message to replace cartridges. Does not allow to print or scan.
- disconnected the print heads connector -> On boot briefly displays a screen with the image of the power button and the code "C00E0060" below. Then the screen turns white and all buttons on the multifunction start blinking. It is as described here but resetting the multifunction, reconnecting the connector and turning it on took it back to operational condition.
- disconnected everything except for the scanner connectors and the tray and door sensors - Gives the exact same behaviour as the previous test (code "C00E0060").
So, from the tests it seems that I can not use the scanner if anything from the printer half is disconnected. Any ideas on how to circumvent this, if possible?
Thank you.

How To Setup a Network Printer

I have a network printer server which connected a Canon PIXMA iP2200 linkjet. The printer works well under windows with http protocol. When I try to setup this printer under Arch, I installed CUPS, ghostscript and gsfonts via pacman and I installed iP2200 filter from aur. I managed to added the printer from the CUPS local web interface and printed a test page successfully, but I can't print any other documents, What's wrong with it?

Well I am trying to paste a piece of Error log here:
E [18/Jan/2010:09:17:48 +0800] Unable to set ACLs on root certificate "/var/run/cups/certs/0" - Operation not supported
E [18/Jan/2010:09:19:36 +0800] Returning IPP client-error-document-format-not-supported for Send-Document (ipp://localhost:631/printers/ip1600) from localhost
E [18/Jan/2010:09:38:01 +0800] [Job 8] 打印文件不被接受 (server-error-device-error)！
E [18/Jan/2010:09:38:01 +0800] [Job 8] Job aborted due to backend errors; please consult the error_log file for details.
D [18/Jan/2010:09:38:01 +0800] [Job 8] The following messages were recorded from 09时37分53秒 to 09时38分01秒
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 5227 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 5227 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 1158 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 1158 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 6322 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 6322 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 5220 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 5220 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 6745 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 6745 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 5256 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 5256 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 9 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 9 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 5184 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 5184 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 7154 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 7154 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 5430 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 5430 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 1898 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 1898 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 1357 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 1357 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 5252 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 5252 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 7500 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 7500 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 4661 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 4661 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 6359 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 6359 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 4808 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 4808 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 4860 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 4860 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 4594 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 4594 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 1089 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 1089 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 7329 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 7329 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 2755 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 2755 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 5412 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 5412 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 1241 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 1241 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 5334 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 5334 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 7777 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 7777 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 5959 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 5959 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 5126 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 5126 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 5473 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 5473 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 5153 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 5153 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 5140 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 5140 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8192 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 7498 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 7498 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 8 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 8 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Read 14 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Wrote 14 bytes of print data...
D [18/Jan/2010:09:38:01 +0800] [Job 8] 1 files to send in job...
D [18/Jan/2010:09:38:01 +0800] [Job 8] STATE: +connecting-to-device
D [18/Jan/2010:09:38:01 +0800] [Job 8] Connecting to 192.168.1.1:631
D [18/Jan/2010:09:38:01 +0800] [Job 8] 正在连接到打印机…
D [18/Jan/2010:09:38:01 +0800] [Job 8] STATE: -connecting-to-device
D [18/Jan/2010:09:38:01 +0800] [Job 8] 已连接到打印机…
D [18/Jan/2010:09:38:01 +0800] [Job 8] Connected to 192.168.1.1:631 (IPv4)...
D [18/Jan/2010:09:38:01 +0800] [Job 8] Getting supported attributes...
D [18/Jan/2010:09:38:01 +0800] [Job 8] document-format-supported (1 values)
D [18/Jan/2010:09:38:01 +0800] [Job 8] [0] = "application/octet-stream"
D [18/Jan/2010:09:38:01 +0800] [Job 8] printer-uri = "http://192.168.1.1:631/printers/iP1600"
D [18/Jan/2010:09:38:01 +0800] [Job 8] requesting-user-name = "ashes"
D [18/Jan/2010:09:38:01 +0800] [Job 8] job-name = "/tmp/org.chromium.0ZlxDm"
D [18/Jan/2010:09:38:01 +0800] [Job 8] Set job-printer-state-message to "打印文件不被接受 (server-error-device-error)！", current level=ERROR
D [18/Jan/2010:09:38:01 +0800] [Job 8] ATTR: auth-info-required=none
D [18/Jan/2010:09:38:01 +0800] [Job 8] Backend returned status 1 (failed)
D [18/Jan/2010:09:38:01 +0800] [Job 8] End of messages
D [18/Jan/2010:09:38:01 +0800] [Job 8] printer-state=3(idle)
D [18/Jan/2010:09:38:01 +0800] [Job 8] printer-state-message="打印文件不被接受 (server-error-device-error)！"
D [18/Jan/2010:09:38:01 +0800] [Job 8] printer-state-reasons=none
E [18/Jan/2010:09:50:43 +0800] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/ReadMe.htm"!
E [18/Jan/2010:09:51:02 +0800] [cups-driverd] Bad driver information file "/usr/share/cups/model/foomatic-db-ppds/Kyocera/ReadMe.htm"!
E [18/Jan/2010:09:55:25 +0800] [cups-driverd] Unable to open driver directory "/usr/lib/cups/driver": No such file or directory
E [18/Jan/2010:09:55:39 +0800] [cups-driverd] Unable to open driver directory "/usr/lib/cups/driver": No such file or directory
E [18/Jan/2010:09:55:45 +0800] [cups-driverd] Unable to open driver directory "/usr/lib/cups/driver": No such file or directory
E [18/Jan/2010:09:55:47 +0800] [cups-driverd] Unable to open driver directory "/usr/lib/cups/driver": No such file or directory
E [18/Jan/2010:09:55:51 +0800] [cups-driverd] Unable to open driver directory "/usr/lib/cups/driver": No such file or directory
E [18/Jan/2010:09:55:56 +0800] [cups-driverd] Unable to open driver directory "/usr/lib/cups/driver": No such file or directory
E [18/Jan/2010:10:26:20 +0800] [Job 9] Aborting job because it has no files.
E [20/Jan/2010:00:19:51 +0800] Unable to set ACLs on root certificate "/var/run/cups/certs/0" - Operation not supported
E [21/Jan/2010:22:15:17 +0800] Unable to set ACLs on root certificate "/var/run/cups/certs/0" - Operation not supported
Anyone could give me some advice?
Last edited by ashesxera (2010-01-21 14:22:13)

The error 600 occurred in the current database connection "LCA".

Hi All,
User is executing job /SAPAPO/TS_REALIGN_COPY in background, as soon as the job is released its failing with runtime error:
I check the Note 1126394 but not relevant.
Runtime Errors         DBIF_DSQL2_SQL_ERROR
Exception              CX_SY_NATIVE_SQL_ERROR
Date and Time          18.08.2011 00:03:39
Short text
     An SQL error occurred when executing Native SQL.
What happened?
     The error 600 occurred in the current database connection "LCA".
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
How to correct the error
    Database error text........: "POS(1) Work rolled back: BAD_ALLOCATION in
     SAPTS_COPY_DA"
    Database error code........: 600
    Triggering SQL statement...: "EXECUTE PROCEDURE SAPTS_COPY_DATA"
    Internal call code.........: "[DBDS/NEW DSQL]"
    Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
    "/SAPAPO/SAPLOM_TIMESERIES" or "/SAPAPO/LOM_TIMESERIESU20"
    "/SAPAPO/OM_TS_DATA_COPY"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
Information on where terminated
    Termination occurred in the ABAP program "/SAPAPO/SAPLOM_TIMESERIES" - in
     "/SAPAPO/OM_TS_DATA_COPY".
    The main program was "/SAPAPO/TS_RLG_COPY_SINGLE ".
    In the source code you have the termination point in line 57
    of the (Include) program "/SAPAPO/LOM_TIMESERIESU20".
    The program "/SAPAPO/SAPLOM_TIMESERIES" was started as a background job.
    Job Name....... "/SAPAPO/TS_REALIGN_COPY"
    Job Initiator.. "CIBERNLAPO2"
    Job Number..... 00015100
    The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred
     in
    procedure "/SAPAPO/OM_TS_DATA_COPY" "(FUNCTION)", but it was neither handled
     locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "/SAPAPO/SAPLOM_TIMESERIES "; its source code
     begins in line
    1 of the (Include program "/SAPAPO/LOM_TIMESERIESU20 ".
Kindly suggest any notes or is any setting needs to be modified.
Regards,
Kaasi

Hello Ada,
the job was aborted due:
Database error text........: "POS(1) Work rolled back: BAD_ALLOCATION in
     SAPTS_COPY_DA"
    Database error code........: 600
    Triggering SQL statement...: "EXECUTE PROCEDURE SAPTS_COPY_DATA"
    Internal call code.........: "[DBDS/NEW DSQL]"
    Please check the entries in the system log (Transaction SM21).
From the posted dump.
Was it lack of OMS heap memory, memory leaking, program error or huge data selection for application run it's not clear. It will be best for SAP customer to create the SAP message and get SAP support when application canceled due Database error BAD_ALLOCATION in LCA routine.
Regards, Natalia Khlopina

Job SEND_SYSTEM_RELATIONSHIP_TO_SUPPORT aborts

Similar Messages

Maybe you are looking for