Default trace?

Hi Friends,
usr/sap/<sid>/DVEBMGS<nn>/j2ee/cluster/server0/log/archive
In the above folder the default trace files of XI are getting archived, which is  zip format and in hidden mode.These files have occupied huge amount of space.
What is the importance of these files?
Are these files necessary?
Will it cause any problem if we delete these file?
Pls help !!
Regards,
Bharath.

Hai,
Check the below link.....
http://help.sap.com/saphelp_nwce10/helpdata/en/ac/e9d8a51c732e42bd0e7de54b9ff4e2/frameset.htm
You can delete the old archives if you really dont see any issue.
Regards,
Yoganand.V

Similar Messages

  • PI 7.11 - confusing error messages in the Default Trace

    Hello,
    Every day, I see these error messages pop up in the default trace ( all with location System.err ):
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
    at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
    at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977)
    at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
    at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
    at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355)
    at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
    at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:60)
    at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
    at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
    .... and many others.
    It all seems to start with this error:
    java.util.regex.PatternSyntaxException: Unexpected internal error near index 16 number_of_nodes\
    They all appear just once a day and all at the same time.
    I already looked for possible causes or background jobs, but nothing...
    Can anybody give me a suggestion?
    Thanks a lot.

    Hi Kevin,
    indeed....You need to apply the following SAP Notes:
    1749574 - Checking for the latest Configuration Wizard patch
    1927916 - Registration of Mbean:ConfigurationExportKMC DefaultTrace
    Afterwards restart J2EE engine. This helped in my case.
    Best Regards
    Harald

  • Error Logs in the Default Trace

    Hi All,
    Iam getting following eror for every second in the Default Trace log but no users are effected with this log. Can anybody tell me what this error is about .
    Date : 12/20/2006
    Time : 11:18:43:702
    Message : Exception in method: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
    [EXCEPTION]
    com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1093)
         at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1037)
         at java.lang.Thread.run(Thread.java:534)
    Severity : Error
    Category :
    Location : com.sap.ip.collaboration.rtc.class com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.JMSPolling.startRunning()
    Application : sap.com/irj
    Thread : Thread[Thread-37,5,SAPEngine_Application_Thread[impl:3]_Group]
    Datasource : 34368150:/usr/sap/PP1/JC03/j2ee/cluster/server0/log/defaultTrace.trc
    Message ID : 0003BA4DBF04001100003473000012530004250B918DE14E
    Source Name : com.sap.ip.collaboration.rtc
    Argument Objs : com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1093)
         at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1037)
         at java.lang.Thread.run(Thread.java:534)
    Arguments : com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1093)
         at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1037)
         at java.lang.Thread.run(Thread.java:534)
    Dsr Component :
    Dsr Transaction :
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 1
    Relatives :
    Resource Bundlename :
    Session : 0
    Source : com.sap.ip.collaboration.rtc
    ThreadObject : Thread[Thread-37,5,SAPEngine_Application_Thread[impl:3]_Group]
    Transaction :
    User : j2ee_guest
    Thanks,
    Master

    I am having this same issue as well.  I upgraded our BI and BI Portal to SP12.  Everything worked fine.  Then I started the BI integration as outlined in OSS note 917950 -> Setting up BEx Web - Problem analysis.doc and restarted the J2EE engine and now I have this same error in the default trace and I can't log into the visual admin as the j2ee_admin user.  I get "error while connecting".   But I can connect to the visual admin as myself.  If I login to the BI portal as my self and click on user administration I get this error "A required service for the identity management user interface is not available. Contact your system administrator"
    Here's the error as seen in the default trace file that keeps repeating.
    #1.#0003BA21A6F5005C000000590000595B000439DE957600B4#1189528059902#com.sap.ip.collaboration.rtc#sap.com/irj#com.sap.ip.collaboration
    .rtc.class com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.JMSPolling.startRunning()#J2EE_GUEST#0####d71a1250608111dcbcf70
    003ba21a6f5#Thread[Thread-57,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Java###Exception in method: com.sap.engine.se
    rvices.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfa
    ctory/default/QueueConnectionFactory.
    [EXCEPTION]
    #1#com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the wh
    ole lookup name is jmsfactory/default/QueueConnectionFactory.
            at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
            at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
            at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
            at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
            at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
            at javax.naming.InitialContext.lookup(InitialContext.java:347)
            at javax.naming.InitialContext.lookup(InitialContext.java:347)
            at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1238)
            at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1182)
            at java.lang.Thread.run(Thread.java:534)
    Also, at the very beginning of the default trace file I see this error:
    ##0#0#Error##Java###A SecurityException was caught while attempting to retrieve user with Administrator rights in the fallback attem
    pt. The performed attempt was userCtx.getUserInfo(role.getRunAsIdentity(true)) but it ended with the following security exception :
    [EXCEPTION]
    #1#com.sap.security.core.server.userstore.UserstoreException: Could not get user null
    ##0#0#Error##Java###A SecurityException was caught while attempting to retrieve user with Administrator rights in the fallback attem
    pt. The performed attempt was userCtx.getUserInfo(role.getRunAsIdentity(true)) but it ended with the following security exception :
    [EXCEPTION]
    #1#com.sap.security.core.server.userstore.UserstoreException: Could not get user null

  • Deleting default trace file in java

    Hello all,
    Whats the best way to automatically delete default trace file in java instance? I want to delete these files lets say every week or 2 wkkds,Is there any type of configuration that can be done through NWA or OS...? or do i have to write some scripts? Please advice.

    Perfect.
      When set to 10, 0 -->9 are cyclic files. Regarding archiving, yes this is possible. Apart from defaulttrace files you can also archive other java log files (system, network,security etc). The configuration procedure is explained :-
    http://help.sap.com/saphelp_nw04/helpdata/en/48/2edfd5bd3e0d4a81b90325fe195a70/frameset.htm
    Once the 10th trace file(i.e.defaultrace9) is full, all the trace files (from defaulttrace0-defaultrace9) are zipped to a single file. The file compression ratio is extremely good.
    Unfortunately there is no automated mechanism to clear off the archived files. This needs manual intervention(regular cleanup, script etc).
    The archived log files may also be viewed for analysis from NWA.
    While estimating the size for each defaulttrace consider  three factors  i) System load ii) Number of defaulttrace files.
    iii) Retention days(without archiving)
    Ex: System load as observed :
    Say the trace file size is 10MB and 6 trace files get written in 4 hours of peak time and 1 trace files is written for 4 hours during non-peak time .Assuming 8 hours of peak business hours and rest all non-working hours.
    No of files generated is 62 + 14 = 16 files of 10 MB each are generated per week day
    If the defaulttrace file  count is set to 16, you can retain one days' logs . Say you wish to retain the same with less number of files (i.e. 8) you would have to increase the file size to 20 MB. Also will have to look at file system space availability.
                   CAUTION: For a file system occupancy estimate, you will have to also consider as to how many Server nodes are 
                                    configured as each node has its own log area !
    For this you need to observe the pattern as to how many files are being written then estimate the size and count
    cheers !
    PRADi

  • Moving Default Trace File in SQL Server

    How can I move the default trace file in SQL server?
    SQL Server 2012?
    Thanks in advance
    ebro

    Please have a look at these links:
    Change path for default SQL Server trace
    Steps to change the default location of SQL Server /SQL Server Agent - Error log files
    DETERMINING DEFAULT TRACE LOCATION
    Collecting the Information in the Default Trace
    T-SQL Articles
    T-SQL e-book by TechNet Wiki Community
    T-SQL blog

  • Write  logs in different location instead of default trace

    I need to write a logs in different location other than default trace. I don't want to write logs in default trace. what setting i need to do in portal so that i can able to write at other location instead of default trace.

    Hi,
    Check this thread.
    Log for J2EE Web Services?
    Regards,
    Harini S

  • Webdynpro Exception in Default Trace File

    Hello ,
    We are on EP7.0 ECC6.0 ESS1.0 and kepp on getting the following error in the Default Trace file for ESS Travel Webdynpro :
    #1.5^H#00145EC6B0AC001200000072000740EC00045AF21F04ABB9#1225895855827#com.sap.engine.services.servlets_jsp.client.RequestInfo
    Server#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#JSS0WHZ#4383##goxsa664_PP1_7622452
    #JSS0WHZ#36d947e0ab4711ddb54c00145ec6b0ac#SAPEngine_Application_Thread[impl:3]_10##0#0#Error##Plain###application [webdynpro/
    dispatcher] Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.services.
    sal.core.DispatcherException: Wrong Web Dynpro URL: "../WebDynpro/Servlet/<deployableObject>/<application>/xx?..". xx is not
    allowed without exchange key. Retrieved URI path: /sap.com/esstratri/TripForm/~wd_key115_1225895826865/background.gif.
            at com.sap.tc.webdynpro.serverimpl.wdc.adapter.HttpRequestAdapter.checkApplicationUri(HttpRequestAdapter.java:111)
            at com.sap.tc.webdynpro.clientserver.session.RequestManager.checkApplicationUri(RequestManager.java:665)
            at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:141)
            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:387)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
            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(ApplicationSessio
    nMessageListener.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(AccessController.java:215)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    If anybody has encountered such situation ....please let me know.
    Thanks in advance.
    Shikhil

    Hi Shikhil,
    We are running into this exact same issue. Can you please tell me if you were able to resolve this and how it was done?
    Thank you so much,
    -Kevin

  • Time stamp information in default trace file

    How to check the time stamp in defaulttrace.trc or application.trc files for logs in XI server.
    I have seen following timestamp in above mentioned trace  files. But seem to me, during the shutdown time of server, system put the timestamp in trace file.
    ERROR       gateway shutdown
    TIME        Fri Jun 20 11:01:08 2008
    Except for shutdown time, how the system put the timestamp for other activity of system in the default trace and application trace file??
    Sometime, i need to check the timestamp to get some specific information in default trace file for some system activities.
    is timestamp mentioned in coded form as per following log:
    #1.#36CC34C00F02009B000001B400001FF40004510B33EAB6D3#1215008464352#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCDefaultRequestHand
    ler.handleRequest()#J2EE_GUEST#0##XQA#SAPSYS                          #4869A1FC78690A8DE10000000A2C0AC7#SAPEngine_Application_Thread[impl:3]_51##0#0#Error##P
    lain###java.lang.reflect.InvocationTargetException#
    #1.#36CC34C00F02009B000001B500001FF40004510B33EAB76C#1215008464352#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCDefaultRequestHand
    ler.handleRequest()#J2EE_GUEST#0##XQA#SAPSYS                          #4869A1FC78690A8DE10000000A2C0AC7#SAPEngine_Application_Thread[impl:3]_51##0#0#Error##P
    lain###java.lang.reflect.InvocationTargetException
    Thanks
    Amar

    Hi Amarjit
    The timestamp is noted in unix epoch time (java does use this as well). It is this field:
    #1.#36CC34C00F02009B000001B400001FF40004510B33EAB6D3# 1215008464352 #com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCDefaultRequestHand
    ler.handleRequest()#J2EE_GUEST#0##XQA#SAPSYS
    The first 10 digits are seconds since epoch. The last 3 digits are milisecondes. Converted in human readable format: 07/02/2008 16:21:04.352
    [Unix Time|http://en.wikipedia.org/wiki/Unix_time]
    Damn, i remeber having answered this already here in the forums, but i cannot find the thread anymore myself :-(((
    Best regards
    Michael

  • Details missing in default trace file of XI

    Hi Experts,
    I am doing RFC to RFC scenario. I am getting checkered flag in SXMB_MONI. But for some reason i am not getting the details of my scenario in the default trace of XI. I'm not sure if the detiails of scenarios involving RFC's will be updated in the trace files. If yes, please help me in finding the reasons as to why it is not heppening in my case.
    Thanks and Regards,
    Hari.

    Hi,
    Increase your logging/ Tracing levels in the Integration engine configuration to see the synchronous message in the SXMB_MONI.
    1.Execute SXMB_ADM in the ABAP stack of XI
    2.Navigate to Configuration --> Integration Engine Configuration --> Change Specific Configuration Data
    Set the following:
    Category : Runtime
    Parameter : LOGGING_SYNC
    value : 1 (activated)
    Parameter : TRACE_LEVEL 3
    value : 3 (activated)
    For information on how to activate and deactivate traces, see the following SAP Note: 532918    (RFC Trace Generation)
    also go with below links
    Configuring the Trace File
    http://help.sap.com/saphelp_nw04/helpdata/en/3d/93532ad37011d194ba00a0c94260a5/frameset.htm
    Enqueue Trace Analysis
    http://help.sap.com/saphelp_nw04/helpdata/en/3d/93532ad37011d194ba00a0c94260a5/frameset.htm
    Enqueue Trace Records
    http://help.sap.com/saphelp_nw04/helpdata/en/3d/93532ad37011d194ba00a0c94260a5/frameset.htm
    Please let me know if this helps you or do you need any more info.

  • Logging Format like in default trace

    Hi all,
    When using log-viewer service in visual admin I want my logs to be formatted as it is in default trace (defaultTrace.trc)
    The message is separately displayed in its own column whereas location/severity/date etc. is shown in its own column, but not contained in the message itself.
    When I use my own location, destination(file) and formatter(trace) I cannot achieve the same. I get date and time in the right columns, but in the message column I get all the stuff that is in the file: date, severity, location. Let's say its not getting filtered.
    Any idea what's so special about default trace?
    regards
    stefan
    Edited by: Stefan Bungert on Apr 21, 2008 4:16 PM

    Hi,
    I think you change the format as you using TraceFormatter class.
    According to the pattern you give in the constructor your format will change.
    It is that pattern that determines.
    Regards,
    Srinivasan Subbiah

  • Unable to view latest default trace in log viewer

    Hello all,
    We have NW 7.0 J2EE production server. We have a CI and two application servers.
    Our SP level is SP18.
    The DB is oracle and the operating system in RHEL 4.
    I have a problem in viewing the default trace files in log viewer using the visual administrator.
    I am able to view the old default trace but unable to view the latest trace data generated.
    I am facing this problem when i try to view the logs of a particular application server.
    Able to view the latest default trace properly for CI and the other application server. Problem lies only with a single application server.
    I have also check the permissions in OS level for the trace files. Everything looks fine.
    Could some one give me a clue on how to solve this issue.
    Regards,
    Chandru

    Hello Joey,
    The trace file isnt too big....
    We have set the file size as 10 MB.
    We have some 15 to 16 default trace files for each of the server process and we have 3 server process in that application server.
    The ForceSingleTraceFile parameter is set as YES in visual admin.
    So the logs will be displayed in visual admin as a single default trace file.
    Hope I had provided the inputs you have asked...
    Regards,
    Chandru

  • Visual admin error on default trace on server0

    HI,
    We have a recurrent error log which occurs all 5 minutes in the default trace in our Was Java (server0 node).
    ACCESS.ERROR: Authorization check for caller assignment to J2EE security role [SAP-J2EE-Engine : administrators].
    The user that throw this error is PIRWBUSER.
    please, can you help us ?
    Thanks.

    Hi Stephane,
                     The following thread will help to resolve the problem.
    please check it.
    Error in SP13; Authorization check for caller assignment
    Re: Too many exception"ACCESS.ERROR: Authorization check"
    regards
    mahesh.

  • NWA logs and trace does not show the content of Default trace

    Hi All,
    The content which i see in /usr/sap/SID/DV*/j2ee/cluster/server0/log/default trace
    i am unable to see the same in default trace in NWA logs and traces,
    It is a 7.0 system..
    Coudl you please suggest.
    Rgds
    S

    Hello,
    Is it newly built system? Please compare log and trace levels with other java systems in your landscape.
    You can give a try as following..
           1.      Goto NWA and click on Log Configurator service.
           2.      Switch to advanced mode.
           3.      Select the Location tab page.
           4.      Choose the location of default.trc file.
           5.      Save the configuration
           6.      Restart JAVA and see.
    Thanks,
    Siva Kumar
    Edited by: Siva Kumar Arivinti on Jan 12, 2012 3:36 PM

  • Workflow Daemon is stuck in E sourcing CLM and documents are not flowing to approvers.which place should i check for this issue related information i have already checked default traces and Logs

    Hi Guys,
    We have a situation in our landscape where workflow daemon service is stuck  and we have to restart the Esourcing system.
    Could you please help here where should i check the cause of the issue.
    i have already checked the Default traces and Esourcing traces.
    Could you help in identifying the cause.
    Regards
    Tarun

    Hi Tarun,
    Open the Document for e.g. Contract Document, on the Document Tab there is an option for Phase Information open that page this will give you all the information related to the phase and where it is stuck, with which user it is pending etc.
    Now since the workflow is stuck, either you can restart the Demon Registration via background Task Status. or else Cancel the Workflow so it can be restarted. by doing the below steps.
    1) goto Setup
    2) open Workflow Definition Under Workflow.
    3) now choose the phase at which your Workflow is stuck.
    4) open that phase.
    5) under Reports Tab there is option for " Current Workflow Processes"
    6) open the Current Workflow Processes
    7) search the document which is stuck
    8) click on the "X" mark  = Cancel the workflow process option
    9) it will take you to the workflow cancel wizard screen. give the comment why you need to cancel this and click on Finish
    10 ) once the Workflow is canceled the phase will go to the Requester review phase and form here you will have to manully move to the next phase. so the workflow can be restarted. once done refresh it.
    11) before doing this take Approval from the customer.
    If the above does not work and still there is an issue then please check the Pre- Phase script.
    Let me know if this works.
    Thanks
    kanchan

  • Fatal error in Default Trace

    Hi Experts,
    I'm from SAP-XI backround and in one of the scenarios I found below fatal error in one of the default traces
    of our production system.
    Fatal Error :
            Error during initialization: Object not found in lookup of SLDAgentBean.
    Thrown:
    MESSAGE ID: com.sap.aii.rwb.exceptions.rb_AgentException.message2
    com.sap.aii.rwb.exceptions.BuildLandscapeException: Error during initialization: Object not found in lookup of SLDAgentBean.
    at com.sap.aii.rwb.agent.client.EJBAgent.getXIDomain(EJBAgent.java:259)
    at com.sap.aii.rwb.util.web.model.AppMainModel.getSelectedDomain(AppMainModel.java:138)
    at com.sap.aii.rwb.util.web.model.AppMainModel.getSelectedXIComponent(AppMainModel.java:150)
    at com.sap.aii.mdt.web.MonitorDynPage.set
    Can any one please let me know the cause for the error:
    Thanks and regards,
    Prajwal

    Hi Prajwal,
    Check this link this may be useful
    com.sap.aii.rwb.exceptions.BuildLandscapeException
    Regards
    Ramesh

Maybe you are looking for

  • IPhone 5 no longer connecting to home wifi after adding new iPhone 5s

    I just bought my husband a new iPhone 5s and successfully connected it to our home wifi; however, now my iPhone 5 won't connect.  All other home devices will connect without an issue. I've tried Reseting the Network Setting on my iPhone and that does

  • How to unlock disabled ipad

    My daughter put a password on her ipad mini.  She can not remember the password and now it is "disabled" and will not respond.  How do we unlock and reset her device?

  • Volume of Invoices in CRM Billing

    Hi Guys Do you have any idea about the volume of invoices which CRM can handle if we use CRM as billing? In our current scenario we will be generating 1000Invoices per hour.So do you think ECC can handle this amount or CRM billing has the capability

  • Message Mapping delete Field

    Hello, i want to delete a field in the target structure. Like you do it with disable. for example when in the source field the value is empty i want to disable the target field. But when there is a value, i want to map this value into target field. h

  • Edit Window Grayed Out

    When selecting a photo from thumbnails the program highlights the thumbnail, but then when I select the Edit button the photo shows up for a second, then the edit portion of the screen grays out replacing the photo with a framed question mark. The la