Fpcopara job log - error in smartform

Hello,
I am running Fpcopara tcode for a mass printing.
After the job finishes, when I look in joblog I can see the error message no 6323: Error in smartform ....
Any ideas on how to debug the job, because fpcopara is running in background and DBUG seems not to work...
Thank you

Hi
Check this report RSNAST00 and debug the code
I think you have not maintained the print parameters in your driver program
please check the same
for reference check the driver program RLB_INVOICE
and this perform
determine print data
  PERFORM set_print_data_to_read USING    lf_formname
                                 CHANGING ls_print_data_to_read
                                 cf_retcode.
Regards
Shiva

Similar Messages

  • Unable to delete job logs - Error : file is corrupted or unreadable

    Hi,
    We are running SolMan on Windows 2003 and there are some very old job logs (dated 2009) in "F:\usr\sap\sid\SYS\global\000JOBLG\" which we are unable to remove.
    The error is "The file or directory is corrupted or unreadable".  Because of this, Data Protector backup always has errors.
    I have run "RSBTCDEL2" but these logs were not removed.
    Is there a way to remove these stubborn old job logs?
    Thanks in advance

    >
    Sisab Nimda wrote:
    > Hi,
    >
    > We are running SolMan on Windows 2003 and there are some very old job logs (dated 2009) in "F:\usr\sap\sid\SYS\global\000JOBLG\" which we are unable to remove.
    >
    > The error is "The file or directory is corrupted or unreadable".  Because of this, Data Protector backup always has errors.
    >
    > I have run "RSBTCDEL2" but these logs were not removed.
    >
    > Is there a way to remove these stubborn old job logs?
    >
    > Thanks in advance
    Hi Sisab,
    Best is to determine whether you actually have the jobs from 2009 ( completed / Cancelled ones ) in your Solution manager system. If they donot exist in the job tables ( normally can be seen using transaction SM37 and a date range ), just go ahead and delete the joblogs from the OS level from 2009.
    Regards
    Amit

  • Display error message in batch job log

    Hello
    I have a batch job running and I have an error coming during some validation logic.
    The problem is I need to continue the batch job when this error message comes and it should not cancel the batch job as it is doing currently but display that error message in batch job log, there are more similar error messages coming in job log and job gets finished, but when my error message comes job gets cancelled.
    I cannot give it as info message as it will give wrong idea about message type.
    Is there any FM by which we can add message in job log?

    Sanjeev I have done that but problem is I do not want to give that as Information message but Error message only and continue processing.
    If you see in screenshot 3rd message is given by me as information and you can see error messages also 6th and 7th and job continued till it is finished
    Basically I want that 'I' to be displayed as 'E'.
    Display error message in batch job log 

  • How to display custom error message in Job log for batch processing

    Hi All,
    I am rexecuting one R/3 report in batch mode and i want to display all the custom error i have handled in job log when its executed from SM36,SM37. The custom error are like 'Delovery/Shipmet doe not exits' or others which we can display in online mode like message e100(ZFI) or any other way and accordingly we can handle the program control like come out of the program ro leave to transaction'Zxxx' or anything. But i want my program to be executed completely and accumulate all the error in job log of batch processing.
    Can anyone tell me how can i do so...
    Thanks,
    Amrita

    Hi,
    Thats what i have done from the begining. I have written message like this:
    Message i100(ZFI).
    I was hoping to see this message in the log. But i cant see. Can you help me pleae...

  • Error in Source system (Job is not going in to job log of CRM system)

    Hi,
    We replicated datasources from CRM server in BI 7 server and they get replicated and are in Active version
    All transactiond atasources which are 7.0 version are executing successfully, but the Datasources which are in 3.5 version i.e. Datasource for master data infoobject gives error while executing infopackage.
    The error message is as follows:
    "Diagnosis
         In the source system, there is no transfer structure available for
         InfoSource 0CRM_MKTMETA_ATTR .
    System Response
         The data transfer is terminated.
    Procedure
         In the Administrator Workbench, regenerate from this source system the
         transfer structure for InfoSource 0CRM_MKTMETA_ATTR ."
    Also while executing the infopackage the job log in source system is not able to create the corresponding job.
    Following action are already been taken:
    1. Datasource replication
    2. Confirmed that the Transfer Structure are avialable and are in ACTIVE state.

    Hi
    It seems some changes are taken place at Source System for the Mast.Data DS. Try to Recheck the Same at Source System -- Activate/Retranport the same.
    BI side.
    RSA13Source System Your DS-- Replicate the Data Source -- Try to Run RS_TRANSTRUC_ACTIVATE_ALL(SE38) / Activate Transfer Rules Manually -- Then Full/Re Init -- Delta Uploads
    Hope it helps and clear

  • Error reading job logs of Apps server from Central Instance

    Dear Gurus,
    We have newly installed system with one CI ( cluster environment) and 2 application Instances.
    Systems are recently installed by other team. I am looking into support part after handover.
    We have noticed below error while reading failed background job logs from our CI. If suppose any job is failing, we can read respective job log from that application instance but it throws error while reading job log from CI to either of application instance.
    I checked /sapmnt/SID/global is shared among all 3 servers and i am successfully able to "Touch a" from applications instances.
    Even though i have given "777" permissions to all folders like  /sapmnt/SID , /sapmnt/SID/global , /sapmnt/SID/global/400JOB*
    I am not able to read job log from CI , for same failed job I can read job log from respective application instance.
    Error log :
    Error reading job log JOBLGX00080700X39290
    Message no. BT167
    Diagnosis
    The background processing system was unable to read the job log named in the message.
    This message suggests that there is a problem with the TEMSE storage system of the SAP system.  The TEMSE storage system is a repository for temporary objects, such as job logs and spool requests. Job logs are always stored in the TEMSE as operating system files.
    This error occurs if the TEMSE system is not able to find or access the file that contains the text of the job log that you requested. Possible causes for the loss or unavailability of the job log include the following:
    Someone deleted the required TEMSE file (from the operating system, not from within the SAP system).
    A CRON (or equivalent scheduler) job has deleted the TEMSE file.
    The file system in which the TEMSE stores its files is not mounted or is not accessible (NFS problem, disk failure, or similar problem).
    The TEMSE reorganize or consistency check functions were used within the SAP system and deleted the job log.
    SM21 logs :
    Error 2 for write/read access to a file. File = /usr/sap/SID/SYS/global
    BP_JOBLOG_SHOW: Failed to display jobs. Reason:
    > Error reading job log JOBLGX00080700X39290
    Strange this is I can check failed job log on one application instance frfom other application instance but not from CI.
    Kindly throw some lights where to check.
    Regards,

    Hi Shravan,
    I guess it is related to permission to /sapmnt/SID/global folder. Please ensure owner is sidadm:sapsys in all the systems viz CI, App servers etc.
    Check the mounting options are correctly set with read/write mode.
    Hope this helps.
    Regards,
    Deepak Kori

  • Error in creating the payment document; read job log

    Hi All,
    Recently we are upgraded to EHP4 pack. While running the payment proposal for the vendor I am getting the error 007 "Error in creating the payment document;read job log" Details of job log is as follows
    >            Due date determination additional log
    > Document 1100001518 line item 001 via ILS          694.00-
    > Terms of payment: 05/23/2011   60  0.000 %    0  0.000 %    0
    >  01 days grace period is being considered
    >  Maximum cash discount should always be taken
    >   Payment must take place before 07/23/2011; next payment on 07/27/2011
    > Item is due with 0.000 % cash discount
    Internal error: doc.balance not zero / comp.code SNXL vendor 1009530510 customer
    Balances:        2,052.00- ILS /        2,052.00- ILS
    >
    >            Posting documents additional log
    >  Currencies in line 1: ILS / ILS  Currencies in line 2: USD / ___
    > Document  company code SNXL currency ILS payment method T
    >  LIt PK Acct         RA            Amount            Tax
    >
    >  001 38 2001520500               3,420.00              0.00
    >                                  1,002.02              0.00
    >  002 50 0032118400               1,026.00              0.00
    >                                    297.21              0.00
    >  003 25 2001520500              72,645.00              0.00
    >                                 20,879.23              0.00
    >  004 50 0032118400              21,793.50              0.00
    >                                  6,312.93              0.00
    >  005 50 0010009101              48,457.50              0.00
    >                                 14,036.70              0.00
    >  006 40 0096100000                   0.00              0.00
    >                                    769.63              0.00
    >
    Information re. vendor 1009530510 / paying company code SNXL ...
    I have checked the configuration of FBZP The configuration settings is correct. Can you please help to solve this problem
    Regards
    Girish

    Hi Girish,
    You should be having error FZ326.
    Please kindly refer to the following link in order to solve the issue:
    http://wiki.sdn.sap.com/wiki/display/ERPFI/PaymentProgram-ErrorMessageFZ326
    or
    http://wiki.sdn.sap.com/wiki/x/jY3YCw
    Apply all notes that are relevant to your support packaged.
    Kind Regards,
    Fernando Evangelista

  • F110 Error 007 - Error in creating the payment document; read job log

    We have created a new SAP instance (vers 4.7) and testing if its working.
    The above error occurs at the payment proposal stage for payment methed C (Cheque), but is OK for E (BACS).
    I have been back through the config a couple of times checking FBZP and OBA7, and I can see anything obviously wrong.
    The job log says........
    10.03.2010 16:27:24 Job started -
                                                                       00           516          S    
    10.03.2010 16:27:24 Step 001 started (program SAPF110S, variant &0000000000007, user ID BPGB) -
         00           550          S    
    10.03.2010 16:27:24 Log for proposal run for payment on 10.03.2010, identification GB4  -
               FZ           402          S    
    10.03.2010 16:27:25                                                                              -
      ZT           004          S    
    10.03.2010 16:27:25 Information re. vendor 500007 / paying company code PS10 ...  -
                     FZ           305          S    
    10.03.2010 16:27:25 ... payment not possible because of reported error  -
                               FZ           311          S    
    10.03.2010 16:27:25 End of log  -
                                                                       FZ           398          S    
    10.03.2010 16:27:25 Job finished  -
                                                                     00           517          S    
    What appears to be the offending line in the log (Error ZT004) is blank, so gives me no clues as to the problem.  I'm at a loss what to check net, and I'm hoping somebody can help me.
    Any advise welcome.
    Thanks
    Graham

    Thanks Ji, that gives me a much better log to look through.
    I've been doing a lot more testing as a result, but ultimately still come up blank.  Heres why I am....
    1.  I have 2 payment methods...
    C-Cheque
    E=BACS
    2. I pay 2 types of vendors...
    Eternal (i.e. Invoices)
    Internal (i.e. Employees expenses)
    3. The payment proposal step is working fine for external suppliers on both payment methods, but fails for internal on both methods.
    4. I am using the same payment terms on everything (Immediate payment no discount)
    5.The only difference in the logs is (i.e. the line below does not appear on the external supplier logs).....
    Cash discount base amount not set!                                                              FZ           753
    6. The accounting documents look as I expect (External have an amount in the Cash Discount base, internal do not), this is how our current system behaves where we do not have any issues, and I cannot see any differences in the vendor document between the 2 systems
    7. Incase I have missed something that is the real cause of the problem, here is the full log.
    If you have any ideas what the problem still is, advice would be gratefully received, as I am pulling what little hair I have left out.
    Full log......
    Job started                                                                                00           516
    Step 001 started (program SAPF110S, variant &0000000000018, user ID BPGB)                          00           550
    Log for proposal run for payment on 10.03.2010, identification GB6                                 FZ           402
    >                                                                                FZ           693
    > Additional log for vendor 500008 company code PS10                                               FZ           691
    >                                                                                FZ           693
    >            Due date determination additional log                                                 FZ           799
    > Document 2100000002 line item 001 via GBP           53.04-                                       FZ           700
    > Terms of payment: 10.03.2010    0  0.000 %    0  0.000 %    0                                    FZ           701
    >  00 days grace period is being considered                                                        FZ           726
    >  Cash discount base amount not set!                                                              FZ           753
    >   Payment must take place before 10.03.2010; next payment on 12.03.2010                          FZ           728
    > Item is due with 0.000 % cash discount                                                           FZ           721
    >                                                                                FZ           693
    >            Payment method selection additional log                                               FZ           699
    > Payment method selection for items due now to the amount of GBP           53.04-                 FZ           601
    > Payment method "E" is being checked                                                              FZ           603
    > Bank details are being checked                                                                   FZ           640
    >    Customer/vendor bank details are being read                                                   FZ           644
    > Country GB / Bank number 404731 / Account 12457852 ...                                           FZ           645
    >     Customer/vendor bank details are being checked                                               FZ           665
    >   System reads house banks and checks if they are allowed                                        FZ           668
    > Our bank 1000 is being checked                                                                   FZ           648
    > For currency GBP and 001 days 9999,999,999.00 are planned                                        FZ           658
    > Available amount is enough, 9999,999,999.00 GBP still available,           53.04  necessary      FZ           657
    >   House bank is selected ...                                                                     FZ           673
    > Our bank details 1000 GBBK1 are being used                                                       FZ           641
    > Bank details of the partner with ctry GB bk no. 404731 acct 12457852 are being used              FZ           642
    > Payment method "E" is permitted                                                                  FZ           609
                                                                                    ZT           004
    Information re. vendor 500008 / paying company code PS10 ...                                       FZ           305
    ... payment not possible because of reported error                                                 FZ           311
    End of log                                                                                FZ           398
    Job finished                                                                                00           517
    Edited by: gbrandreth on Mar 11, 2010 11:35 AM

  • F110 " Error in creating the payment document; read job log"

    Hi all,
    when i execute payment in Tcode F110, getting message " Error in creating the payment document; read job log".
    Log for payment run for payment on 30.07.2009, identification TEST1
    Error in the recovery of constants
    Information re. vendor 1000040256 / paying company code BG10 ...
    ... payment not possible because of reported error
    Because of it, the payment file is also not generated.
    The status says " Payment run has been carried out".
    But when the open items are cleared.
    What could be the reason for this error message?
    Regards,
    Vidya

    Hi,
    As the document is in the cleared status, you can try finding out with which run date and run id the documents got cleared. Go to Transaction code SE12 and give the following details - Company code, vendor code and the payment documents (clearing document for the invoice) or you can also give the invoice document numbers and fiscal year.
    The output will tell you which payment run id and run date was used to process the payment.
    Hope this will help you understand what has happened.
    Thanks and Regards,
    Anit
    Edited by: Anit Mangat on Jul 30, 2009 4:38 PM

  • Distribute System  - Error when run tcode DB13 - Job Log - Cancel

    i have two server and I installed SAP ERP 6.0 (Application ABAP) on two server base on Distribute System model
    Server A : I installed Global Host Preparation and Central Instance
    Server B : I installed Database Instance
    On server A, I exported /sapmnt, /usr/sap
    On server B, I mounted /samnt, /usr/sap from Server A
    Process Installation -> OK
    and finally , I logged in SAP through server A -> OK
    But when i run tcode DB13 to run Action Pad : Cleanup Logs, Check and Update Optimize Statistic ....etc -> Cancel
    -> with error in tab Job Log below
    20.01.2010     14:37:07     Job started
    20.01.2010     14:37:07     Step 001 started (program RSDBAJOB, variant &0000000000041, user ID BASIS)
    20.01.2010     14:37:07     No application server found on database host - rsh/gateway will be used
    20.01.2010     14:37:07     Execute logical command BRCONNECT On host sapree2
    20.01.2010     14:37:07     Parameters: -u / -jid CLNUP20100120143706 -c -f cleanup
    20.01.2010     14:37:29     SXPG_STEP_XPG_START: is_local_host: rc = 403
    20.01.2010     14:37:29     SXPG_STEP_XPG_START: host = sapree2
    20.01.2010     14:37:29     SXPG_STEP_XPG_START: is_local_r3_host: rc = 802
    20.01.2010     14:37:29     SXPG_STEP_XPG_START: RFC_TCPIP_CONNECTION_OPEN: rc = 1003
    20.01.2010     14:37:29     SXPG_STEP_COMMAND_START: SXPG_STEP_XPG_START returned: 1.003
    20.01.2010     14:37:29     SXPG_COMMAND_EXECUTE(LONG)
    20.01.2010     14:37:29     <timestamp> = 20100120143729
    20.01.2010     14:37:29     COMMANDNAME = BRCONNECT
    20.01.2010     14:37:29     ADDITIONAL_PARAMETERS = -u / -jid CLNUP20100120143706 -c -f cleanup
    20.01.2010     14:37:29     LONG_PARAMS
    20.01.2010     14:37:29     OPERATINGSYSTEM = ANYOS
    20.01.2010     14:37:29     TARGETSYSTEM = sapree2
    20.01.2010     14:37:29     DESTINATION
    20.01.2010     14:37:29     SY-SUBRC = 1003
    20.01.2010     14:37:29     SXPG_COMMAND_EXECUTE failed for BRCONNECT - Reason: program_start_error: For More Information, See SYS
    20.01.2010     14:37:29     Job cancelled after system exception ERROR_MESSAGE
    and then , I checked tcode SM59 -> TCP/IP Connection -> SAPXPG_DBDEST_SAPREE2 -> Test Connection -> not OK with error
    Logon     Connection Error
    Error Details     Error when opening an RFC connection
    Error Details     ERROR: timeout during allocate
    Error Details     LOCATION: SAP-Gateway on host sapree1.reecorp.com / sapgw00
    Error Details     DETAIL: no connect of TP sapxpg from host sapree2.reecorp.com after 20 sec
    Error Details     COMPONENT: SAP-Gateway
    Error Details     COUNTER: 22
    Error Details     MODULE: gwr3cpic.c
    Error Details     LINE: 1973
    Error Details     RETURN CODE: 242
    Error Details     SUBRC: 0
    Error Details     RELEASE: 701
    Error Details     TIME: Wed Jan 20 14:42:39 2010
    Error Details     VERSION: 2
    thanks for your advice

    Hi,
    For installation you can refer the standalone gateway installation guide available under http://service.sap.com/instguides
    For operating the standalone gateway you can use the below link
    http://help.sap.com/saphelp_nw04/helpdata/en/bb/9f13194b9b11d189750000e8322d00/content.htm
    Cheers.....,
    Raghu

  • Submit Back ground job with error log

    Hi Gurus
    Can anyone help with Back ground job with error log. i want put all the error logs in to 1 internal table and submit the back ground .how can i do that .please help me

    Hi reddy ,
    i am not experienced this in real scenarion .. even though i would like to give my idea
    Put your logic inside the FM and execute in in background task mode on your action button .
    call function 'Function module name' in background task
    exporting
       parameter =
    importing
       ret =
    refer the below link for more detail on executing FM as  background task
    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/8f/53b67ad30be445b0ccc968d69bc6ff/frameset.htm
    Regards
    Chinnaiya P

  • Logging errors from job's program

    Hello,
    I want to log error returned from the job's program and I wonder whether it is possible at all.
    What I have done is:
    1) write a procedure
    2) create a program executing this procedure
    3) create a job running this program
    From time to time this procedure returns error (it does some operation on objects and sometimes some of them are invalid). Normally, this error causes job to finish it's action (job failure as well). I needed this job to proceed so I added a clause 'exception when others then null'. Now it works, but it's a temporary solution because I need to capture this error and log it, so that it is available for further investigation.
    I searched through oracle doc and it seems the only choice is to create my own table or file and log the results into it.
    Does any of you know any other way? For example to log it in somehow into system tables (like dba_scheduler_job_run_details).
    Thanks in advance,
    Aliq

    Hi Dharmesh,
    Thanks for responding.
    This is a large deployment involving hundreds of applications and servers. My responsibility is to come up with development guidelines for applications hosted on TS. I have gone through the guidelines
    posted by Microsoft @
    http://msdn.microsoft.com/en-us/library/aa383490(v=vs.85).aspx. But it didn't cover the topic on logging.
    Do you know whether Microsoft has published any other document on this topic.
    Thanks,
    Raj

  • Background Job Log - Interface error

    Hi,
    I am using a program in back ground which will transfer the data from one FTP server to another FTP server, the program is scheduled in back ground, the Job appears in green means sucessful but
    in Job log I get the following log, (an if there are 10 file to be sent, 8 files moves but 2 files fails).
    ftp> Interactive mode Off .#                                                   
    ftp> prompt                                                                    
    ftp> open primary-proxy                                                        
    Invalid command.#                                                              
    Invalid command.#                                                              
    ftp> sk74n2w9                                                                  
    Not connected.#                                                                
    ftp> ascii                                                                     
    Not connected.#                                                                
    Not connected.#                                                                
    ftp> close                                                                     
    quit Transfer Complete                                                         
    > ftp: connect :Connection refused                                             
    D:\usr\sap\PRD\D00\work>endlocal 
    Please give your valuable imputs.
    Regards,
    Prabhu

    Hi all,
    Please give some inputs on the above question. and any clarifications pls let me know.
    Regards,
    Prabhu
    Edited by: prabhu jayaraman on Dec 9, 2008 7:06 AM

  • NW Log Error

    Hello,
    We are on MII 12.1.7 build 47
    I am getting below errors in NW logs (Default trace view) not sure what is it that causing these errors but I am afraid these errors might impact us sooner or later..
    Any suggestions/recommendations will be of great help!!
    com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server <http://gpiptcxmdev01:50000/uddi/api/publish/> returned message <Unauthorized>.
    [EXCEPTION]
    com.sap.esi.esp.lib.mm.config.exceptions.SRTechnicalExceptioncom.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server <http://gpiptcxmdev01:50000/uddi/api/publish/> returned message <Unauthorized>.
    at com.sap.engine.services.webservices.tools.wsil.SOACentralSRPublisherImpl.saveClassificationSystem(SOACentralSRPublisherImpl.java:1296)
    at com.sap.esi.esp.service.server.mass.PublishRulesHandler.publishServiceDefinitions(PublishRulesHandler.java:484)
    at com.sap.esi.esp.service.server.mass.PublishRulesHandler.process(PublishRulesHandler.java:448)
    at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.process(SOATimeoutListenerImpl.java:385)
    at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.run(SOATimeoutListenerImpl.java:222)
    at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.timeout(SOATimeoutListenerImpl.java:126)
    at com.sap.esi.esp.service.server.SOATimeoutListenerImpl.timeout(SOATimeoutListenerImpl.java:95)
    at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:71)
    at com.sap.engine.frame.core.thread.Task.run(Task.java:73)
    at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
    at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)
    Caused by: com.sap.esi.uddi.sr.api.ws.ServicesRegistrySipublishClassificationSystemsFault123: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server <http://gpiptcxmdev01:50000/uddi/api/publish/> returned message <Unauthorized>.
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.JAXWSUtil.deserializeException(JAXWSUtil.java:402)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.JAXWSUtil.processFault(JAXWSUtil.java:372)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1115)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:779)
    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:746)
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:167)
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:120)
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:83)
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:64)
    at $Proxy477.publishClassificationSystems(Unknown Source)
    at com.sap.esi.uddi.sr.api.ws.ejb.ServicesRegistryProxyFacade.publishClassificationSystems(ServicesRegistryProxyFacade.java:333)
    at sun.reflect.GeneratedMethodAccessor553.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
    at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
    at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
    Regards,
    Adarsh

    Hi Mike,
    Thanks for your response.
    What roles are assigned to the user that is triggering these error messages?
    This is our new development server and we have migrated stuff from 11.5 to 12.1 and there are only 8 users on this system and all of them are super admins but of those I am the only one using the system currently and I am not sure it is being generated by any of our 8 users because the interesting point is this error generates on every 49th minute of hour (for eg, 10:49, 11:49, 12:49 and so on) and along with I see two more errors "SR Log error" occurring on same time.
    These are the only three errors I see repeating every hour and no other errors.
    What version of the JRE is running on the machine accessing MII?
    On client machines we have JRE 1.5 update 22 and on server we have JRE 1.5 update 21
    What process is being performed at the time of the error messages?
    No background jobs are scheduled and even if I don't run any programs still I can see this error on every hour
    Regards,
    Adarsh

  • External Operation Job Log

    Hello all,
    I can't seem to find additional information on this. I have written an exteranl operation in c# and I can run it from the portal without any issue. I know that standard error is supposed to be captured in the job log, however I can't seem to figure out how to write to standard error from a c# console application. Console.error doesn't seem to cut it.
    I am using ALUI 6.0 sp1, but I dont' think this has changed much over the years. Has anybody written a c# external operation and been able to write to the job log?
    Thanks,
    Berney

    You could just make it write to stdout and then redirect stdout to stderr like this: "dir 1>&2". I put that in a bat file in the scripts directory and then made the bat an external operation. It wrote to the job logs like this:
    Mar 3, 2009 11:40:55 AM- Starting to run operations (1 total) for job 'stdout dir test ext op Job'. Will stop on errors.
    Mar 3, 2009 11:40:55 AM- *** Job Operation #1 of 1: ExternalOperation [Run as owner 'Administrator']
    Mar 3, 2009 11:40:55 AM- Java Version: 1.5.0_12 from BEA Systems, Inc.
    Mar 3, 2009 11:40:55 AM- OS x86 Windows 2003 5.2 as SYSTEM
    Mar 3, 2009 11:40:55 AM- External Operation Agent for stdout dir test External Operation is starting...
    Mar 3, 2009 11:40:55 AM- Original Script is: "test.bat"
    Mar 3, 2009 11:40:55 AM- Scripts home is: E:\bea\alui\ptportal\10.3.0\scripts
    Mar 3, 2009 11:40:55 AM- Appending E:\bea\alui\ptportal\10.3.0\scripts to test.bat.
    Mar 3, 2009 11:40:55 AM- Full Path to script is: E:\bea\alui\ptportal\10.3.0\scripts\test.bat.
    Mar 3, 2009 11:40:55 AM- Operation has timeout of 0 ms.
    Mar 3, 2009 11:40:55 AM- stdout>
    Mar 3, 2009 11:40:55 AM- stdout>E:\bea\alui\ptportal\10.3.0\scripts>dir 1>&2
    Mar 3, 2009 11:40:55 AM- stderr> Volume in drive E is New Volume
    Mar 3, 2009 11:40:55 AM- stderr> Volume Serial Number is 4CFC-EB07
    Mar 3, 2009 11:40:55 AM- stderr>
    Mar 3, 2009 11:40:55 AM- stderr> Directory of E:\bea\alui\ptportal\10.3.0\scripts
    Mar 3, 2009 11:40:55 AM- stderr>
    Mar 3, 2009 11:40:55 AM- stderr>03/03/2009 11:37 AM <DIR> .
    Mar 3, 2009 11:40:55 AM- stderr>03/03/2009 11:37 AM <DIR> ..
    Mar 3, 2009 11:40:55 AM- stderr>12/18/2008 07:59 AM 5,049 AnalyticsRunJobs.bat
    Mar 3, 2009 11:40:55 AM- stderr>10/08/2008 01:35 PM 2,034 BulkSubscriber.bat
    Mar 3, 2009 11:40:55 AM- stderr>10/08/2008 01:35 PM 3,577 SavedSearchMailer.bat
    Mar 3, 2009 11:40:55 AM- Total Memory = 33554432 bytes, Free Memory = 9573312 bytes, Used Memory = 23981120 bytes.
    Mar 3, 2009 11:40:55 AM- stderr>03/03/2009 11:37 AM 8 test.bat
    Mar 3, 2009 11:40:55 AM- stderr> 4 File(s) 10,668 bytes
    Mar 3, 2009 11:40:55 AM- stderr> 2 Dir(s) 17,469,964,288 bytes free
    Mar 3, 2009 11:40:55 AM- *** Job Operation #1 completed: Process completed successfully; Command line: ""test.bat"".(282609)
    Mar 3, 2009 11:40:55 AM- Done with job operations.
    I don't think much has changed with this in the portal 6.x world, but it looks like stderr is definitely captured in wci 10.3. If there's a problem with an older version, start a support ticket to investigate a possible bug.

Maybe you are looking for