CSDiscovery Log

     Hi
See the following in the CSDiscovery log
log4j:WARN No appenders could be found for logger (com.cisco.nm.csdiscovery.CSDiscoveryManager).
log4j:WARN Please initialize the log4j system properly.
Is this a problem as I am trying to get to the bottom of an issue with Phones numbers.
Thanks

Short answer :This is "normal".
Unfortunately many ciscoworks logs are swapped with errors and warnings when everything is just fine.
It is not a cisco or ciscoworks problem but it is rather "normal" for a lot of these java apps out there. A lot of developers nowadays are more then happy if their shit compiles in their IDE. Fixing the mess is too expensive.
On top of that a lot of the log messages written into the log are just meant to fill logfiles (because the spec said so) rather then provide clues as to what is not working. (Yeah, maybe if you know where in the source code this message was sent, it could help you)
I assume cisco outsources the development and that hurts quality. I really feel some parts are designed by someone that understands what he is trying to do, other parts are designed by someone who has no clue, build according to the spec, minimal implementation. Whether that "saves money" in the long run remains to be seen. 
Cheers,
Michel

Similar Messages

  • CiscoWorks log overflooded

    Hi all
    I have two logs which are overflooded. Can anyone tell me what these records indicate, and what to do?
    In dmgtDbg.log these INFO records come again and again:
    [Tue Nov 04 07:05:31 W. Europe Standard Time 2008][dmgrDbg]##### INFO ##### re-evaluate DbgLevel=0x0
    [Tue Nov 04 07:05:37 W. Europe Standard Time 2008][dmgrDbg][dmgrDbg] getenv(PX_DBG)=NULL
    [Tue Nov 04 07:05:37 W. Europe Standard Time 2008][dmgrDbg][dmgrDbg] getenv(PX_MY_DEBUG)=NULL
    [Tue Nov 04 07:05:37 W. Europe Standard Time 2008][dmgrDbg][dmgrDbg] getenv(PX_MY_TRACE)=NULL
    [Tue Nov 04 07:05:37 W. Europe Standard Time 2008][dmgrDbg][dmgrDbg] getenv(PX_DBG_LEVEL)=NULL
    The CSDiscovery.log is growing very fast (maybe this is normal?)with records like this:
    070027 GeneralSystemAGI@45: [EvalTask-DiscoveryThreadPool-19/10.200.2.15]GeneralSystemAGI: eval() >>>
    070027 GeneralSystemAGI@63: [EvalTask-DiscoveryThreadPool-19/10.200.2.15]GeneralSystemAGI: eval() <<<
    070027 GeneralIpAddrAGI@42: [EvalTask-DiscoveryThreadPool-19/10.200.2.15]GeneralIpAddrAGI: eval() >>>
    I regularly run the logbackup.pl that emptys the log. But the recomended filesize of 1024KBytes is soon reaced again.

    The messages in dmgtDbg.log are typical. You will just need to rotate this file when it gets too big. The log file size recommendations are on the low side, so I wouldn't worry about those.
    As for the CSDiscovery.log, go to Common Services > Server > Admin > CS Log Configurations, and make sure CS Discovery debugging is disabled.

  • LMS 3.2 CSDiscovery stalled

    I am using LMS 3.2 and Device Discovery never finishes. It discoevers the majority of devices and then hangs. The only way to stop it is to run pdterm CSDiscovery from the server command line. I used to have exactly this problem under LMS 3.1 and was advised it was a bug and 3.2 would fix it. Discovery has run ok under 3.2 for 6 months but is no longer working.

    Update - Discovery is working when limited to very small subnets. For any number of devices over approx 100 it stalls.
    I have turned on debugging for CSDiscovery and am seeing a java OutOfMemory error - see below extract from csdiscovery.log
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : java.lang.OutOfMemoryError: Java heap space
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:144)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at java.io.OutputStreamWriter.write(OutputStreamWriter.java:204)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at java.io.Writer.write(Writer.java:126)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at org.apache.log4j.helpers.QuietWriter.write(QuietWriter.java:39)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:292)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at org.apache.log4j.WriterAppender.append(WriterAppender.java:150)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:57)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at org.apache.log4j.Category.callAppenders(Category.java:187)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at org.apache.log4j.Category.forcedLog(Category.java:372)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at org.apache.log4j.Category.fatal(Category.java:346)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at com.cisco.nm.csdiscovery.adaptor.CSDiscoveryAdaptor.updateOGSGroup(CSDiscoveryAdaptor.java:2054)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at com.cisco.nm.csdiscovery.adaptor.CSDiscoveryAdaptor.updateDevices(CSDiscoveryAdaptor.java:1666)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at com.cisco.nm.csdiscovery.adaptor.CSDiscoveryAdaptor.addDevices(CSDiscoveryAdaptor.java:1637)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at com.cisco.nm.csdiscovery.adaptor.CSDiscoveryAdaptor.putAllProcessed(CSDiscoveryAdaptor.java:759)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at com.cisco.nm.discovery.framework.DiscoveryController.updateProcessedNodes(DiscoveryController.java:688)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at com.cisco.nm.discovery.framework.DiscoveryController.finishDiscovery(DiscoveryController.java:637)
    [Jul 14  22:26:03] INFO  [LoggingOutputStream : Thread-2 flush]  : at com.cisco.nm.discovery.framework.DiscoveryController.run(DiscoveryController.java:1304)
    Can I increase the heap size? Where do I go to adjust?

  • Some Devices are not showing up at all in the Discovery reports

    Hi all,
    The first time I ran the CS device discovery I got 50 reachable devices. I scheduled the Device Discovery to be run every week. I added more subnets to the discovery but unfortunately the last discovery shows only 31 devices from the first discovered devices (50). I checked the DCR and there is only 44 devices out of the 50!
    My question is:
    Should not the scheduled Device Discovery discovers all devices -the previously discovered ones and the new ones-?
    Why the rest of the devices are not showing up at all in the discovery reports (neither reachable nor unreachable) although all of them are pingable and responding to the snmpwalk tool from the CWLMS server.
    Your kindly respond is highly appreciated.
    Thanks in advance.

    I ran the discovery again with the same settings after enabling debugging and I checked the following log files:
    1. in the ngdiscovery.log I found a lot of errors all about Duplicate IpAddress example:
    ERROR  [DeviceManager : EvalTask-DiscoveryThreadPool-06 addNewDevice]  : Duplicate IpAddress (127.0.0.51) found in addNewDevice().Device 1 ip = 10.8.113.29 , id1 = 127.0.0.51*F1COR.xyz.com*.1.3.6.1.4.1.9.1.283, Device 2 ip = 10.8.113.106 , id2 = 127.0.0.51*LCD.xyz.com*.1.3.6.1.4.1.9.1.283
    ERROR  [DeviceManager : EvalTask-DiscoveryThreadPool-08 updateDevice]  : Duplicate IpAddress (127.0.0.51) found in updateDevice().Device 1 ip = 10.8.113.93 , id1 = 127.0.0.51*UDS.xyz.com*.1.3.6.1.4.1.9.1.283, Device 2 ip = 10.8.113.73 , id2 = 127.0.0.51*F2COR.xyz.com*.1.3.6.1.4.1.9.1.283
    ERROR  [DeviceManager : EvalTask-DiscoveryThreadPool-09 addNewDevice]  : Duplicate IpAddress (10.8.113.42) found in addNewDevice().Device 1 ip = 10.8.113.42 , id1 = null, Device 2 ip = 10.8.113.86 , id2 = 10.8.118.251*OPS.xyz.sa*.1.3.6.1.4.1.9.1.501
    2. in the CSDiscovery.log:
    Error while changing the permission of the file C:\PROGRA~1\CSCOpx\objects\csdiscovery\1348\DiscoveryStatusObj
    I checked the file and the casusers has a Modify permission
    My Question is:
    1. what is the meaning of those output exactly?
    2. If CWLMS found duplicatedd IP address how it works in terms of (ignoring, updating existing devices, Adding the new devices, ... etc)
    Many thanks for your help.

  • LMS 3.2 discovery process runs for ever

    Dear friends,
    I am having a problem with discovery on Ciscoworks LMS 3.2. The discovery process runs eternally and does not discover any devices.
    Here are the individual device versions:
    Name   Version   Size   Status   Expiration Date 
    1. CM 5.2 300 Purchased Never
    2. DFM 3.2 300 Purchased Never
    3. HUM 1.0 100 Evaluation Sun Jul 26 12:18:01 GMT+03:00 2009
    4. IPM 4.2 300 Purchased Never
    5. RME 4.3 300 Purchased Never
    6. VNM 1.0 Unlimited Purchased Never
    Please find enclosed the csdiscovery.log which indicates the following error
    1000 [main] DEBUG com.cisco.nm.csdiscovery.CSDiscoveryManager  - FATAL: Exception occured in the start discovery Exception occured during start of discovery in CS.
    Reason : failed to initialize DiscoveryController
    I am also enclosing the CSDiscovery-config.xml under the config directory and the specific job as well.
    ngdiscovery.log shows 0 bytes. I am not sure if it is to be populated only when we initiate some debugging?
    Thanks a lot
    Gautam

    It seems you're missing some critical files.  Under NMSROOT/conf/csdiscovery, you should have the following zip files:
    SharedDiscoveryAUS.zipSharedDiscoveryCluster.zipSharedDiscoveryGeneral.zipSharedDiscoveryIGX.zip
    The casusers group should have full control on all four files.  If these files really are missing, you will need to contact TAC to get new ones, or you will need to reinstall Common Services.

  • Logfile Recommended size over error - LMS 3.1

    Log file
    Directory
    File Size (KBytes)
    Recommended Size Limit (KBytes)
    File System Utilization%
    jrm.log
    C:\PROGRA~1\CSCOpx\log
    107084
    1024
    Less than 1%
    stdout.log.*
    C:\PROGRA~1\CSCOpx\mdc\tomcat\logs
    57591
    102400
    Less than 1%
    dbbackup.log
    C:\PROGRA~1\CSCOpx\log
    11772
    1024
    Less than 1%
    psu.log.*
    C:\PROGRA~1\CSCOpx\log
    4832
    1024
    Less than 1%
    restorebackup.log.*
    C:\PROGRA~1\CSCOpx\log
    3075
    51200
    Less than 1%
    I have already configured recommended file size - file rotations in my LMS. still i keep getting this errors. Can you help me getting out of these RED alarms !!

    C:\Program Files\CSCOpx\bin>perl "c:\Program Files\CSCOpx\bin\logrot.pl" -v
    Tue Dec  1 19:53:50 2009: INFO: Read variable backup_dir --> D:\Log\
    Tue Dec  1 19:53:50 2009: INFO: Read variable delay --> 60
    Tue Dec  1 19:53:50 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\dbbackup.log, B
    ackup File = D:\Log\\dbbackup.log
    Tue Dec  1 19:53:50 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
    stat.exe to obtain logfile size.
    Tue Dec  1 19:53:50 2009: INFO: Rolling logfile archive.
    Tue Dec  1 19:53:50 2009: INFO: Archiving C:\PROGRA~1\CSCOpx\log\dbbackup.log to
    D:\Log\\dbbackup.log.0.
            1 file(s) copied.
    Tue Dec  1 19:53:51 2009: INFO: Rotating C:\PROGRA~1\CSCOpx\log\dbbackup.log.
    Tue Dec  1 19:53:51 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\jrm.log, Backup
    File = D:\Log\\jrm.log
    Tue Dec  1 19:53:51 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
    stat.exe to obtain logfile size.
    Tue Dec  1 19:53:51 2009: INFO: Rolling logfile archive.
    Tue Dec  1 19:53:51 2009: INFO: Archiving C:\PROGRA~1\CSCOpx\log\jrm.log to D:\L
    og\\jrm.log.0.
            1 file(s) copied.
    Tue Dec  1 19:54:01 2009: INFO: Compressing D:\Log\\jrm.log.0 using gzip -f
    Tue Dec  1 19:54:08 2009: INFO: Rotating C:\PROGRA~1\CSCOpx\log\jrm.log.
    Tue Dec  1 19:54:08 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\EDS.log, Backup
    File = D:\Log\\EDS.log
    Tue Dec  1 19:54:08 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
    stat.exe to obtain logfile size.
    Tue Dec  1 19:54:08 2009: INFO: Not archiving C:\PROGRA~1\CSCOpx\log\EDS.log bec
    ause it is not big enough.
    file size = 2745636, conf size = 19118080
    Tue Dec  1 19:54:08 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\CSPortal.log, B
    ackup File = D:\Log\\CSPortal.log
    Tue Dec  1 19:54:08 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
    stat.exe to obtain logfile size.
    Tue Dec  1 19:54:08 2009: INFO: Not archiving C:\PROGRA~1\CSCOpx\log\CSPortal.lo
    g because it is not big enough.
    file size = 132588, conf size = 1048576
    Tue Dec  1 19:54:08 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\EDS-GCF.log, Ba
    ckup File = D:\Log\\EDS-GCF.log
    Tue Dec  1 19:54:08 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
    stat.exe to obtain logfile size.
    Tue Dec  1 19:54:08 2009: INFO: Not archiving C:\PROGRA~1\CSCOpx\log\EDS-GCF.log
    because it is not big enough.
    file size = 26184, conf size = 1048576
    Tue Dec  1 19:54:08 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\psu.log, Backup
    File = D:\Log\\psu.log
    Tue Dec  1 19:54:08 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
    stat.exe to obtain logfile size.
    Tue Dec  1 19:54:08 2009: INFO: Not archiving C:\PROGRA~1\CSCOpx\log\psu.log bec
    ause it is not big enough.
    file size = 894079, conf size = 7122944
    Tue Dec  1 19:54:08 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\mdc\tomcat\logs\std
    out.log, Backup File = D:\Log\\stdout.log
    Tue Dec  1 19:54:08 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
    stat.exe to obtain logfile size.
    Tue Dec  1 19:54:08 2009: INFO: Not archiving C:\PROGRA~1\CSCOpx\mdc\tomcat\logs
    \stdout.log because it is not big enough.
    file size = 56244907, conf size = 111889408
    Tue Dec  1 19:54:08 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\CSDiscovery.log
    , Backup File = D:\Log\\CSDiscovery.log
    Tue Dec  1 19:54:08 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
    stat.exe to obtain logfile size.
    Tue Dec  1 19:54:08 2009: INFO: Not archiving C:\PROGRA~1\CSCOpx\log\CSDiscovery
    .log because it is not big enough.
    file size = 1084297, conf size = 1084416
    Tue Dec  1 19:54:08 2009: INFO: Logfile = C:\PROGRA~1\CSCOpx\log\CSDeviceSelecto
    r.log, Backup File = D:\Log\\CSDeviceSelector.log
    Tue Dec  1 19:54:08 2009: INFO: Attempting to use C:\PROGRA~1\CSCOpx\bin\logrot_
    stat.exe to obtain logfile size.
    Tue Dec  1 19:54:08 2009: INFO: Not archiving C:\PROGRA~1\CSCOpx\log\CSDeviceSel
    ector.log because it is not big enough.
    file size = 99013, conf size = 1326080
    C:\Program Files\CSCOpx\bin>

  • SAP message Log

    Does SAP maintain log of all the messages displayed on screen using MESSAGE statement?
    We are investigating a problem and want to see the messages displayed by SAP during the time when problem occured.

    We have custom development for picking and confirmation. Last week we found that in some deliveries there is difference in delivered quantity and packed quantity.
    Custom development is calling sap-standard FMs. Problem occurs randomly, roughly 10 deliveries in a week has this problem.
    We are still trying to investigate the reason that is causing the problem.
    Custom program does display the message to user if FM raise any message. We asked user of they are getting any message while picking, and if they are ignoring it.
    They just confirmed that they are getting message 'Packing Not Possible Since there is no Quantity to be Packed' and they did ignored this.

  • Botão de 'exibir logs' não aparece - NF 3.10

    Pessoal, boa tarde!
    Preciso de uma ajuda de vocês...
    Estamos na fase de validação de um projeto de NFe 3.10, e o abap já realizou toda a aplicação de notas necessárias.
    O problema é que o cliente percebeu que uma funcionalidade de "exibir logs" foi desativada logo após a aplicação dessas notas!
    Antes quando ele fazia a J1B1N por exemplo, aparecia conforme as imagens abaixo:
    E pelo que eles perceberam, agora esse botão e esses logs não aparecem mais.
    Alguém sabe dizer porque ? Alguém já passou por isso ?
    Muito obrigado,
    Luis.

    Boa Tarde Luis
    Já tentou verificar se o controle de tela não foi alterado?
    Pois houveram alterações nos controles de tela da 2.00 para a 3.10.
    Verifique se os campos continuam como obrigatórios nos controles de tela.
    Abraço
    Giovani

  • Error Log during logon of RAR 5.3 Portal - please help

    Hi Experts,
    We are unable to login into the CC portal [GRC RAR 5.3]. The login screen is appearing again and again without logging into the CC portal
    Below is the log file which we are getting and we understand that the product is not responding properly to the application
    Can somebody please help us in resolving this at the earliest
    Thanks in Advance
    Best Regagards,
    Srihari.K
    Date : 12/05/2008
    Time : 2:38:16:008
    Message : Exception of type com.sap.sql.log.OpenSQLException caught: Cannot assign NULL to host variable 1. setNull() can only be used in INSERT and UPDATE statements. The statement is "SELECT MIN("YEARMONTH") "YEARMONTH",MIN("VIOLTYPE") "VIOLTYPE",MIN("VSYSKEY") "VSYSKEY",MIN("ANLTYPE") "ANLTYPE",MIN("USERGROUP") "USERGROUP",SUM("TOTCOUNT") "TOTCOUNT",SUM("RISKLOW") "RISKLOW",SUM("RISKMED") "RISKMED",SUM("RISKHIGH") "RISKHIGH",SUM("RISKCRT") "RISKCRT",SUM("URNONE") "URNONE",SUM("URLOW") "URLOW",SUM("URMED") "URMED",SUM("URHIGH") "URHIGH",SUM("URCRT") "URCRT",SUM("URMIT") "URMIT",MAX("TOTCRTCD") "TOTCRTCD",SUM("CRTCD") "CRTCD",MAX("TOTCRROLE") "TOTCRROLE",SUM("CRROLE") "CRROLE",SUM("TOTUSER") "TOTUSER",MIN("RUNDATE") "RUNDATE" FROM "VIRSA_CC_MGMTTOT" WHERE "YEARMONTH" = ? AND "VIOLTYPE" = ? AND "VSYSKEY" LIKE ? AND "ANLTYPE" = ? AND "USERGROUP" LIKE ?"..
    [EXCEPTION]
    com.sap.sql.log.OpenSQLException: Cannot assign NULL to host variable 1. setNull() can only be used in INSERT and UPDATE statements. The statement is "SELECT MIN("YEARMONTH") "YEARMONTH",MIN("VIOLTYPE") "VIOLTYPE",MIN("VSYSKEY") "VSYSKEY",MIN("ANLTYPE") "ANLTYPE",MIN("USERGROUP") "USERGROUP",SUM("TOTCOUNT") "TOTCOUNT",SUM("RISKLOW") "RISKLOW",SUM("RISKMED") "RISKMED",SUM("RISKHIGH") "RISKHIGH",SUM("RISKCRT") "RISKCRT",SUM("URNONE") "URNONE",SUM("URLOW") "URLOW",SUM("URMED") "URMED",SUM("URHIGH") "URHIGH",SUM("URCRT") "URCRT",SUM("URMIT") "URMIT",MAX("TOTCRTCD") "TOTCRTCD",SUM("CRTCD") "CRTCD",MAX("TOTCRROLE") "TOTCRROLE",SUM("CRROLE") "CRROLE",SUM("TOTUSER") "TOTUSER",MIN("RUNDATE") "RUNDATE" FROM "VIRSA_CC_MGMTTOT" WHERE "YEARMONTH" = ? AND "VIOLTYPE" = ? AND "VSYSKEY" LIKE ? AND "ANLTYPE" = ? AND "USERGROUP" LIKE ?".
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)
         at com.sap.sql.jdbc.common.CommonPreparedStatement.setNull(CommonPreparedStatement.java:303)
         at com.sap.sql.jdbc.common.CommonPreparedStatement.setString(CommonPreparedStatement.java:509)
         at com.sap.sql.sqlj.runtime.profile.ref.RTStatementJDBCPrepared.setString(RTStatementJDBCPrepared.java:359)
         at com.virsa.cc.xsys.mgmreport.dao.sqlj.MGMTotalDAO.getResult(MGMTotalDAO.sqlj:63)
         at com.virsa.cc.ui.RARiskVGraph.refreshData(RARiskVGraph.java:476)
         at com.virsa.cc.ui.RARiskVGraph.wdDoInit(RARiskVGraph.java:130)
         at com.virsa.cc.ui.wdp.InternalRARiskVGraph.wdDoInit(InternalRARiskVGraph.java:191)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Severity : Error
    Category : /System/Database/sql/jdbc/common
    Location : com.sap.sql.jdbc.common.CommonPreparedStatement
    Application : sap.com/tcwddispwda
    Thread : SAPEngine_Application_Thread[impl:3]_32
    Datasource : 1666450:/apps/usr/sap/HLG/JC00/j2ee/cluster/server0/log/defaultTrace.trc
    Message ID : 0003BAF96A51006E0000001F0000265200045D4A46588084
    Source Name : com.sap.sql.jdbc.common.CommonPreparedStatement
    Argument Objs : com.sap.sql.log.OpenSQLException,Cannot assign NULL to host variable 1. setNull() can only be used in INSERT and UPDATE statements. The statement is "SELECT MIN("YEARMONTH") "YEARMONTH",MIN("VIOLTYPE") "VIOLTYPE",MIN("VSYSKEY") "VSYSKEY",MIN("ANLTYPE") "ANLTYPE",MIN("USERGROUP") "USERGROUP",SUM("TOTCOUNT") "TOTCOUNT",SUM("RISKLOW") "RISKLOW",SUM("RISKMED") "RISKMED",SUM("RISKHIGH") "RISKHIGH",SUM("RISKCRT") "RISKCRT",SUM("URNONE") "URNONE",SUM("URLOW") "URLOW",SUM("URMED") "URMED",SUM("URHIGH") "URHIGH",SUM("URCRT") "URCRT",SUM("URMIT") "URMIT",MAX("TOTCRTCD") "TOTCRTCD",SUM("CRTCD") "CRTCD",MAX("TOTCRROLE") "TOTCRROLE",SUM("CRROLE") "CRROLE",SUM("TOTUSER") "TOTUSER",MIN("RUNDATE") "RUNDATE" FROM "VIRSA_CC_MGMTTOT" WHERE "YEARMONTH" = ? AND "VIOLTYPE" = ? AND "VSYSKEY" LIKE ? AND "ANLTYPE" = ? AND "USERGROUP" LIKE ?".,com.sap.sql.log.OpenSQLException: Cannot assign NULL to host variable 1. setNull() can only be used in INSERT and UPDATE statements. The statement is "SELECT MIN("YEARMONTH") "YEARMONTH",MIN("VIOLTYPE") "VIOLTYPE",MIN("VSYSKEY") "VSYSKEY",MIN("ANLTYPE") "ANLTYPE",MIN("USERGROUP") "USERGROUP",SUM("TOTCOUNT") "TOTCOUNT",SUM("RISKLOW") "RISKLOW",SUM("RISKMED") "RISKMED",SUM("RISKHIGH") "RISKHIGH",SUM("RISKCRT") "RISKCRT",SUM("URNONE") "URNONE",SUM("URLOW") "URLOW",SUM("URMED") "URMED",SUM("URHIGH") "URHIGH",SUM("URCRT") "URCRT",SUM("URMIT") "URMIT",MAX("TOTCRTCD") "TOTCRTCD",SUM("CRTCD") "CRTCD",MAX("TOTCRROLE") "TOTCRROLE",SUM("CRROLE") "CRROLE",SUM("TOTUSER") "TOTUSER",MIN("RUNDATE") "RUNDATE" FROM "VIRSA_CC_MGMTTOT" WHERE "YEARMONTH" = ? AND "VIOLTYPE" = ? AND "VSYSKEY" LIKE ? AND "ANLTYPE" = ? AND "USERGROUP" LIKE ?".
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)
         at com.sap.sql.jdbc.common.CommonPreparedStatement.setNull(CommonPreparedStatement.java:303)
         at com.sap.sql.jdbc.common.CommonPreparedStatement.setString(CommonPreparedStatement.java:509)
         at com.sap.sql.sqlj.runtime.profile.ref.RTStatementJDBCPrepared.setString(RTStatementJDBCPrepared.java:359)
         at com.virsa.cc.xsys.mgmreport.dao.sqlj.MGMTotalDAO.getResult(MGMTotalDAO.sqlj:63)
         at com.virsa.cc.ui.RARiskVGraph.refreshData(RARiskVGraph.java:476)
         at com.virsa.cc.ui.RARiskVGraph.wdDoInit(RARiskVGraph.java:130)
         at com.virsa.cc.ui.wdp.InternalRARiskVGraph.wdDoInit(InternalRARiskVGraph.java:191)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Arguments : com.sap.sql.log.OpenSQLException,Cannot assign NULL to host variable 1. setNull() can only be used in INSERT and UPDATE statements. The statement is "SELECT MIN("YEARMONTH") "YEARMONTH",MIN("VIOLTYPE") "VIOLTYPE",MIN("VSYSKEY") "VSYSKEY",MIN("ANLTYPE") "ANLTYPE",MIN("USERGROUP") "USERGROUP",SUM("TOTCOUNT") "TOTCOUNT",SUM("RISKLOW") "RISKLOW",SUM("RISKMED") "RISKMED",SUM("RISKHIGH") "RISKHIGH",SUM("RISKCRT") "RISKCRT",SUM("URNONE") "URNONE",SUM("URLOW") "URLOW",SUM("URMED") "URMED",SUM("URHIGH") "URHIGH",SUM("URCRT") "URCRT",SUM("URMIT") "URMIT",MAX("TOTCRTCD") "TOTCRTCD",SUM("CRTCD") "CRTCD",MAX("TOTCRROLE") "TOTCRROLE",SUM("CRROLE") "CRROLE",SUM("TOTUSER") "TOTUSER",MIN("RUNDATE") "RUNDATE" FROM "VIRSA_CC_MGMTTOT" WHERE "YEARMONTH" = ? AND "VIOLTYPE" = ? AND "VSYSKEY" LIKE ? AND "ANLTYPE" = ? AND "USERGROUP" LIKE ?".,com.sap.sql.log.OpenSQLException: Cannot assign NULL to host variable 1. setNull() can only be used in INSERT and UPDATE statements. The statement is "SELECT MIN("YEARMONTH") "YEARMONTH",MIN("VIOLTYPE") "VIOLTYPE",MIN("VSYSKEY") "VSYSKEY",MIN("ANLTYPE") "ANLTYPE",MIN("USERGROUP") "USERGROUP",SUM("TOTCOUNT") "TOTCOUNT",SUM("RISKLOW") "RISKLOW",SUM("RISKMED") "RISKMED",SUM("RISKHIGH") "RISKHIGH",SUM("RISKCRT") "RISKCRT",SUM("URNONE") "URNONE",SUM("URLOW") "URLOW",SUM("URMED") "URMED",SUM("URHIGH") "URHIGH",SUM("URCRT") "URCRT",SUM("URMIT") "URMIT",MAX("TOTCRTCD") "TOTCRTCD",SUM("CRTCD") "CRTCD",MAX("TOTCRROLE") "TOTCRROLE",SUM("CRROLE") "CRROLE",SUM("TOTUSER") "TOTUSER",MIN("RUNDATE") "RUNDATE" FROM "VIRSA_CC_MGMTTOT" WHERE "YEARMONTH" = ? AND "VIOLTYPE" = ? AND "VSYSKEY" LIKE ? AND "ANLTYPE" = ? AND "USERGROUP" LIKE ?".
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
         at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)
         at com.sap.sql.jdbc.common.CommonPreparedStatement.setNull(CommonPreparedStatement.java:303)
         at com.sap.sql.jdbc.common.CommonPreparedStatement.setString(CommonPreparedStatement.java:509)
         at com.sap.sql.sqlj.runtime.profile.ref.RTStatementJDBCPrepared.setString(RTStatementJDBCPrepared.java:359)
         at com.virsa.cc.xsys.mgmreport.dao.sqlj.MGMTotalDAO.getResult(MGMTotalDAO.sqlj:63)
         at com.virsa.cc.ui.RARiskVGraph.refreshData(RARiskVGraph.java:476)
         at com.virsa.cc.ui.RARiskVGraph.wdDoInit(RARiskVGraph.java:130)
         at com.virsa.cc.ui.wdp.InternalRARiskVGraph.wdDoInit(InternalRARiskVGraph.java:191)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Dsr Component : n/a
    Dsr Transaction : d2d9c100c2b811dd9eb60003baf96a51
    Dsr User :
    Indent : 0
    Level : 0
    Message Code : com.sap.sql_0019
    Message Type : 1
    Relatives : /System/Database/sql/jdbc/common
    Resource Bundlename :
    Session : 92
    Source : com.sap.sql.jdbc.common.CommonPreparedStatement
    ThreadObject : SAPEngine_Application_Thread[impl:3]_32
    Transaction :
    User : ac_admin

    Hi,
    The shear length  of your post is frightening - this would keep many potential replies away !!
    What i woudl recommend is --> Open an OSS messgae ! This would resolve your problem !!
    Thanks

  • NoClassDefFoundError: com/sap/sql/log/OpenSQLException

    I have developed a Java project. It consists of 2 SQLJ files and then a Java class. When I try to execute the Java program, I get a Java error:
    java.lang.NoClassDefFoundError: com/sap/sql/log/OpenSQLException
         at com.mbb.crrs.business.report.dao.ReportDAO.<init>(ReportDAO.sqlj:23)
         at com.mbb.crrs.business.report.dao.Test.main(Test.java:24)
    Exception in thread "main"
    I notice a similar problem on message: Re: Which jar to include com.sap.sql.log.OpenSQLException
    Is that something that I need to maintain for it to work? Thank you.

    Hi,
    the problem one year ago was that the SQLException class was not available through remote access. I don't know if that might have been changed meanwhile in the latest release.
    I implemented a simple work around: I caught every SQL-exception in the method where it was thrown, wrapped the exception message and any nested exception in a self written exception and threw this new exception. That worked fine.
    Regards, Astrid

  • SPAU error reading log file

    Hi All,
    We have an R/3 4.0B landscape and are working on some changes.  I want to see if any SAP delivered objects have been modified in the past, but whenever I run SPAU or SPDD, I get an error message
    "Error Reading File D:\usr\sap\put\log\umodstat.log"  "Message Number 0U 503".
    I can read a text file in the same directory through AL11, so I'm reasonably sure it's not an OS permission problem.
    Any ideas?
    Thanks,
    Alan

    Hi All,
    I had same issue trying to edit sat.trc file, I fixed this problem by manual editing sat.trc file and modified the following line:
    <!FORMATTER[com.sap.tc.logging.perf.PerfFormatter]/>
    change to:
    <!FORMATTER[com.sap.tc.logging.ListFormatter]/>
    after changes you will able to open file with Visaul Admin Log Viewer or standalone logviewer.
    Hope it helps.
    Regards

  • BRF+ Message Log & "Rule as Expression"

    Hi colleagues,
    I am quite new to BRFplus and have two questions:
    1) I would like to use a message log action in order to indicate errors. I tried to follow https://wiki.wdf.sap.corp/wiki/display/FDT/Message+Log   with method SET_APPLICATION_LOG_OBJECT, but I can't find the class this method belogns to. I also tried modelling a rule & action message log with help of the UI. My question is how can I log messages and where can I find them after the function is beeing processed?
    2) In every guide I can read something about rule expressions and even how to create them (e.g. http://help.sap.com/saphelp_nw70ehp1/helpdata/en/cc/85414842c8470bb19b53038c4b5259/frameset.htm), but in the workbench there is no possibilty of creating rules as expressions but only rules and rulesets (the rule is not part of the "Expression" node).
    I hope somebody knows what I mean
    Thanks a lot & kind regards,
    Ilijana

    Thanks a lot for your response!
    Could you tell me why using rules and rulesets is not recommended for 7.01 ? This could be interesting for my bachelor thesis.
    Thanks & Kind Regards,
    Ilijana

  • CK40N : no message log update after =cksu

    Hi costing experts,
    In the costing run statistics there are errors for the marking step, which I correct by entering =cksu according to SAP note 542790.
    However, the message log for the marking step is not updated. It is hard to find which are the remaining messages in the overall message log, because there are some 400 messages in total and only 50 are still relevant according to the refreshed statistics.
    Does anyone have any idea's about what can be done to update the message log?
    Thanks,
    Caroline.

    I got below error in the ST22 dump....
    "Database error text........: "ORA-00060: deadlock detected while waiting for
    resource"
    Internal call code.........: "[RSQL/INSR//BIC/FZXX_C02 ]"
    I was searching for OSS notes associated with following keywords and note able to find any notes related my support pack level we are in SP13 (SAPKW70013)
    "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB" "WRITE_ICFACT"
    Any help will be greatly appreciated...
    Thanks,
    Raman

  • How to pop up a system message for a specific user when She/He log on SAP

    Hi Friends,
    As we know SM02 setting will pop up a system message to all users in specific client in a specific period when the user log on SAP system; and we can do the same thing via using function module SM02_ADD_MESSAGE.
    But now we want to pop up a message to a specific user ID when somebody log on SAP via this ID, instead of all user IDs in the client. Please do we have any similar traction / function module / class method to to do this job??
    Thanks in advance.
    Joe

    Below code can be used to send a pop up message to all users who are logged on to the
    system.
    DATA: MESSAGE(128) VALUE 'Test message'.
    DATA: OPCODE TYPE X VALUE 2.
    DATA: BEGIN OF USR_TABL OCCURS 10.
    INCLUDE STRUCTURE UINFO.
    DATA: END OF USR_TABL.
    CALL 'ThUsrInfo' ID 'OPCODE' FIELD OPCODE
    ID 'TAB' FIELD USR_TABL-SYS.
    LOOP AT USR_TABL.
    CALL FUNCTION 'TH_POPUP'
    EXPORTING
    CLIENT = SY-MANDT
    USER = USR_TABL-BNAME
    MESSAGE = MESSAGE
    EXCEPTIONS
    USER_NOT_FOUND = 1.
    ENDLOOP.
    In the above code just pass the desired user ID instead of All user ID's
    Edited by: harsh bhalla on Mar 26, 2009 2:14 PM

  • How to log in to Service Desk to create sample message to SAP?

    Dear all,
    How to log in to Service Desk under my Solution Manager server to create sample message to SAP under Component: SV-SMG-SUP?
    Regards
    GN

    Hi GN,
    You have different options to create messages in test component SV-SMG-SUP-TST:
    1. if you are on 7.1 you can create message using CRM_UI
    2. If you are using lower vrsion then either you can create message using Workcenter or using transaction NOTIF_CREATE or using menu --> Help --> Create support message.
    Thanks
    Regards,
    Vikram

Maybe you are looking for