Job in background is getting cancelled

Hi Abapers,
I have created the program to display data. It works fine when I execute it from SE38.
But when I execute the same program in background, It gets cancelled.
Can any one give me the reason & what can we do for this?
Thanks,
Hemal Shah

Hi Hemanl ,
  Since you are executing the program ins background i assume that it is not an interactive ALV , so i would suggest you not to use a container on the screen and use the default screen provided by sap.
Here is the steps you need to folllow
1. Delete the Screen you created to display the ALV.
2. As the screen in deleted so no custom container is required , hence remove the code to create the custom container .
3: When you create grid object give the parent i.e. the parameter I_PARENT the value
    CL_GUI_CONTAINER=>SCREEN0 ,
Rest of the coding with the gird as the original one .
Make these changes and execute your program and see,
Regards
Arun

Similar Messages

  • EMIGALL Distributed Import Job for BP is getting cancelled in background

    Hi,
    When I'm restarting Distributed import and it's getting cancelled after some time with system error as "internal lock table overflow".
    I checked SM12 (while job was running) it's  showing 14,000 - 15,000 locks on table BUT000, even though EMIGALL is not updating that table as it's rerun of the old job. (Old job been cancelled due to network issue.).
    Can anybody please help me to understand why it's happening?
    Thanks in advance,
    Sagar

    Hi Sagar,
    I think I can explain what happened in your system:
    During data migration the application encountered many errors and does not release the locks immediately. Remember: it is not the slave jobs that creates locks but the called application (through the service functio module). If the application enncounters an error (also when the business object cannot be locked due to a lock table overflow) it returns the error and the load program writes it to the error log. The saved error message is not always directly related to the lock table overflow situation. Often it is saying: object already locked by user xxx).
    The master jobs uses also locks to block the configuration of its profile against concurrent access (exclusive access). If a user blocks the profile temporarily during an update of the profile, the master job waits until the update operation finishes. This last usually only very few ms. If the master encounteres a 'lock table overflow' situation it cancels - as designed be the developer.
    The simple solution is that you should avoid a lock table overflow situation and/or that the lock table must not be too small.
    Sagar,  I might also be that you find also the error 'lock table overflow' in the system log. Please check.
    Kind regards,
    Fritz

  • Job SM:EXEC SERVICES  gets cancelled with  SYNTAX_ERROR

    Hi,
         The job which refreshes Service sessions (for Early Watch Alerts) in SolMan 4. gets cancelled with the message:
    Syntax error in program "RDSVASAEA_ROOT_____________050 ".
    I performed a syntax check on the program in the ABAP Editor and it gives the following result :
    Field "BDLDLTRHOSTS001030" is unknown. It is neither in one of the
    specified tables nor defined by a "DATA" statement. "DATA" statement.
    Can you let me know, how to solve this problem.
    My system is SolMan 4.0 SP 15 on Win 2003 with Oracle 10.2.
    ST-SER and ST-ICO are with the latest support pkg level,
    Regards,
    Anil.

    These steps can be done easier as of Support Package Stack 15:
    >
    Amit Devale wrote:
    > Step 1:
    > Run report BDL_DELETE_ALL_TABLES via SE38 to delete all entries
    > in the service definition tables
    >
    > Step 2:
    > Execute a 'Refresh service definitions' task session in transaction
    > SDCCN ->Task ->Create ->'Refresh service definitions'
    >
    > Step 3:
    > Execute in transaction SE37 the function module "BDL_GENERATE_LOGFUNC
    > _INCLUDES" and enter the value "ALL" in the 'OPTION' field.
    Hi Amit,
    Support Package Stack 15 of SAP Solution Manager does contain an update of SDCCN (shipped within ST-PI 2005_1_700 SP06.
    [SAP Note 727998|www.service.sap.com/sap/support/notes/727998]
    This offers an easy way to update the service definitions and to generate the logfunc Includes.
    Step 0: Ensure that optimizer statistics exist for table D010INC.
    Step 1-3 :You can use functionality in SDCCN to execute these steps.
    Perform:
    - Path: SDCCN -> Utilities -> Maintain Service Definitions
    - Select 'Delete and Replace Service Definitions -> Confirm this selection
    - Confirm that you want to delete the definitions
    - Confirm that a new task 'Service Definition  Refresh' was created
      (Take a note of the task id -> Review the log for this task id when it is completed)
    You should not not see any errors for either the update of a Service Definitions table or the generation of any re-import include.
    Best regards,
    Ruediger
    P.S.: Great, that you start to share your rich experience here in SDN.

  • Job getting cancelled

    Hi All,,
    We have a job" UPC_BUNDLE_EXECUTE" which is getting cancelled everyday
    here ar
    Job started
    Step 001 started (program UPC_BUNDLE_EXECUTE, variant &0000000000000, user ID )
    Global planning sequence was terminated with errors
    Job cancelled after system exception ERROR_MESSAGE

    Hi,
    I have already checked... but no dumps exits..
    but this job is getting cancelled daily...
    can anybody throw a light on this...
    appreciate your guidance
    Regds

  • Report program when run in background job getting cancelled immediately

    Hi
    When i run a program in foreground i am able to see the output. But when run in background not able to run the job successfully. The job is getting cancelled immediately.
    I am using the below function module for output display. Should i need to pass any parameters in the below function module so that i can run the program in background  successfully.
      CALL METHOD DETAIL_GRID->SET_TABLE_FOR_FIRST_DISPLAY     
          EXPORTING                                            
            IS_LAYOUT         = IS_LAYOUT                    
            I_SAVE            = 'A'                        
            IS_VARIANT        = GS_VARIANT                   
          CHANGING                                           
            IT_FIELDCATALOG   = IT_FIELDCATALOG               
            IT_OUTTAB         = BLOCKED_STOCK_TAB_ALV[].     
    Please suggest.
    Thanks and regards
    Rajani Yeluri

    Hi Rajani.
      ALV require the DRYPOR(screen) for display but incase you run in back ground which have to write to spool but in spool we can only write in format of LIST REPORT not inter-active report like ALV. That why
    system cancelled your process immediately.
    Hope it helps.
    Sayan.

  • Background job getting CANCELLED

    hello,
    i have  a background job scheduled for a report program.it is getting cancelled and giving the following error:
    "TABLE_ILLEGAL_STATEMENT"
    You attempted to change, delete or create a line in the       
    internal table "???", but no valid cursor exists              
    for the table.                                                
    Possible reasons:                                             
    1. The relevent ABAP/4 statement does not include the addition
       "...INDEX...", although the statement is not               
       inside a "LOOP...ENDLOOP" loop processing this table.      
    2. The relevent ABAP/4 statement was called from within a     
       "LOOP...ENDLOOP" loop after a DELETE "???".                                                                               
    what could be the reason?

    it is also giving following error message:
    Caution: Program has changed
    Caution: At time of termination,  Active source code no longer available  and after above two statements its giving sign "?" before every statement in below manner:
    024300 ?     lit_ekpo_dummy1[] = it_ekpo[].                     
    024310 ?     DELETE lit_ekpo_dummy1 WHERE ebeln NE tab1-ebeln.  
    024320 ?     DESCRIBE TABLE lit_ekpo_dummy1 LINES count01.      
    024330 ?                                                        
    024340 ?     REFRESH lit_ematn_dummy[].                         
    024350 ?     lit_ematn_dummy[] = lit_ematn[].

  • Job getting cancelled in background scheduling

    Hi,
        I have written a report  in the SAP HR system and it is to be scheduled in background. This program transfers the PERNRs from HR system to CRM system as partners in BUT000.The report works perfectly fine if it is run in foreground. When I run it in background the job gets cancelled and I get the job log having a message that it could not ascertain code page and the system exception ERROR_MESSAGE is raised. If anybody has any clues regarding this problem please help me.
    Thanks & Regards,
    Rahul.

    Hi,
    I Guess you are using container controllers in the Report, and all container contols requires help from Sap Gui for execution. I guess that is the reason it is failing in background . Please check on that aspect as well.
    Hope this helps..

  • Background job BI_ODSA_ASD is getting cancelled, set privilege at db level

    Hi,
    Background job BI_ODSA_ASD is getting cancelled,
    i have increased the tablespace, still no luck,
    last time i faced the same problem at that time , i gave some permission at oracle level which worked fine, i dont not remember now,
    it was something like GRANT PRIVILEGE SAPSYS SAPCON...... (not sure)
    if anyone knows please let me know.
    Regards,
    SM

    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_SDB_ORA_PROGRAM_ERROR
    Date and Time          20.09.2007 15:46:44
    Short text
    An exception occurred that was not caught.
    What happened?
    The exception 'CX_SDB_ORA_PROGRAM_ERROR' was raised, but it was not caught
    anywhere along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CL_SDB_ORA_UPDATE_STATS=======CP' has to be
    terminated.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_SDB_ORA_PROGRAM_ERROR', was not
    caught and
    therefore caused a runtime error.
    The reason for the exception is:
    ـbernehmen
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_SQL_EXCEPTION", which was raised in the program
    "CL_SQL_STATEMENT==============CP",
    specifically in line 31 of the (include) program
    "CL_SQL_STATEMENT==============CM002".
    The cause of the exception was:
    ORA-20000: Insufficient privileges
    ORA-06512: at "SYS.DBMS_STATS", line
    2150
    ORA-06512: at "SYS.DBMS_STATS", line 14112
    ORA-06512: at line 1
    How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "UNCAUGHT_EXCEPTION" "CX_SDB_ORA_PROGRAM_ERROR"
    "CL_SDB_ORA_UPDATE_STATS=======CP" or "CL_SDB_ORA_UPDATE_STATS=======CM00I"
    "UPDATE_STATS"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.

  • Background Jobs getting Cancelled

    Hi SRM Gurus
    we are working on SRM  4.0  and follow a classic scenarios.
    We have schedulled following background jobs
    1 BBP_GET_STATUS_2
    2 CLEAN_REQREQ_UP
    3 SMWP_BATCH
    Which were running successfully however from yesterday this all jobs are showing status cancelled.
    Can any one throw some light as to why this jobs are getting cancelled or how to check the reaons for the cancelling of jobs.
    regards,
    Nimish Sheth

    Hi Nimish,
    for how long where they running ?
    They might be cancelled because of time out (ex: R/3 system not available temporary).
    Do you have traces in SM21 in the same time fence ?
    Rgds
    Christophe

  • Background Job get Cancelled when executing the report. Reason?

    Hi All,
    I have scheduled a Back ground Job and executed Immediately.
    when checking transacion SM37 the job get canceled.
    How to find out the problem for the Job Cancellation.
    Regards,
    Viji

    hi
    After scheduling back ground job ( give a time laps of 2 min )
    then go to sm37 ( at this moment , the job is not yet started) .
    select ur job in sm 37 and when job starts processing , type JDBG as the command and press enter.
    Now it will go to the debugging screen, where u will find system program . Now set a break point at the stements used in ur program from the debugging screen itself.( menu - breakpoint- breakpoint at - statement ) and press F8 .
    Now you can start debug ur code.
    Revrt back if any issues.
    Regards,
    Naveen

  • Standard Background Job getting cancelled

    Hello Guru ,
    In my BI dev server one standard event periodic job is geting cancelled due to following reason
    Job Name : AP_CCMS_MONI_BATCH_STARTUP_DP
    Program:  RSAL_BATCH_TOOL_STARTUPDISP
    cancelled error
    No alerts in configuration range
    Internal error:
    Job cancelled after system exception ERROR_MESSAGE
    can anybody help me in this regards
    Regards
    Deepak

    Run the job once again and lets see what happens... sometimes system cancels the job....check in ST22 if there is short dump.
    Thanks....
    Shambhu

  • RDDGENOL job getting cancelled with huge number of ABAP dumps

    Hi,
    In our Production system, we had applied Kernel upto patch level 263 and while
    applying SPAM 30 for release 640 it failed. We tried applying Basis patch 15 still
    it did not went through.
    Since then we are getting around 1500-2500 dumps daily. The job RDDGENOLis getting cancelled and the dumps RAISE_EXCEPTION and SYNTAX_ERROR is displayed in ST22. Today, there were around 2500 dumps in the system.
    When I now run the Database <-> ABAP Dictionary consistency check in
    DB02, I see number of errors for missing objects in the database. There
    are around of dozens of Primary Indexes, secondary Indexes, Tables,
    Views listed in the result:
    Objects Missing in database No.
    =========================== ===
    Primary indexes 6
    Secondary indexes 14
    Tables 37
    Views 26
    When I try to create each of them using SE16 or using SQL utility on OS
    level, it gives an SQL system error. We are also getting thousands of
    dumps each day (attached alongwith this message). Also I see the CPF327E error
    in the OS Level Joblog.
    Also we cannot transport any requests. There is some problem with or
    due to the conversions. Is it a problem with Kernel, ABAP dictionary or
    database.
    Following is the extract of the dumps due to DDIC in 000:
    ============================================================
    Runtime Error          SYNTAX_ERROR
    Date and Time         
    ShrtText
    Syntax error in program "CL_WB_CROSSREFERENCE==========CP ".
    What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLSEWB" had to be terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    In program "CL_WB_CROSSREFERENCE==========CP ", the following syntax error
    occurred
    in the Include "CL_WB_CROSSREFERENCE==========CM00D " in line 8:
    |    "The type "KEYWORD_TAB" is unknown." 
    ============================================================
    ============================================================
    Runtime Error          RAISE_EXCEPTION
    Date and Time         
    ShrtText
    Exception condition "DESTINATION_NOT_OPEN" raised.
    What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    A RAISE statement in the program "SAPLCRFC" raised the exception
    condition "DESTINATION_NOT_OPEN".
    Since the exception was not intercepted by a superior program
    in the hierarchy, processing was terminated.
    Short description of exception condition:
    Specified destination is not open.
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
    How to correct the error
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "RAISE_EXCEPTION" C
    "SAPLCRFC" or "LCRFCU20"
    "RFC_CONNECTION_CLOSE"
    or
    "SAPLCRFC" "DESTINATION_NOT_OPEN"
    or
    "RADBAT01 " "DESTINATION_NOT_OPEN"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    System environment
    SAP Release.............. "640"
    Application server....... "TXTPDSAP"
    Network address.......... "172.16.0.140"
    Operating system......... "OS400"
    Release.................. "5.3"
    Hardware type............ "0065000655EC"
    Character length......... 8 Bits
    Pointer length........... 64 Bits
    Work process number...... 35
    Short dump setting....... "full"
    Database server.......... "TXTPDSAP"
    Database type............ "DB400"
    Database name............ "TXT"
    Database owner........... "R3TXTDATA"
    Character set............ "en_US.ISO8859-1"
    SAP kernel............... "640"
    Created on............... "Dec 11 2008 23:06:45"
    Created in............... "AIX 1 5 00538A4A4C00 (IBM iSeries with OS400)"
    Database version......... "DB4_52"
    Patch level.............. "263"
    Patch text............... " "
    Supported environment....
    Database................. "V5R2, V5R3, V5R4, V6R1"
    SAP database version..... "640"
    Operating system......... "OS400 2 5, OS400 3 5, OS400 4 5, OS400 1 6"
    Memory usage.............
    Roll..................... 696832
    EM....................... 16759712
    Heap..................... 0
    Page..................... 32768
    MM Used.................. 1383120
    MM Free.................. 3483600
    SAP Release.............. "640"
    User and Transaction
    Client.............. 000
    User................ "DDIC"
    Language key........ "E"
    Transaction......... " "
    Program............. "SAPLCRFC"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    The termination occurred in the ABAP program "SAPLCRFC" in
    "RFC_CONNECTION_CLOSE".
    The main program was "RADBAT01 ".
    The termination occurred in line 22 of the source code of the (Include)
    program "LCRFCU20"
    of the source code of program "LCRFCU20" (when calling the editor 220).
    The program "SAPLCRFC" was started as a background job.
    Job name........ "RDDGEN0L"
    Job initiator... "DDIC"
    |    Job number...... 00032101    
    ============================================================
    Kindly let me know the immediate fix. Thanks!
    Regards,
    Nick

    Hi Nick,
    I would say, you are having a slight missperception of this forum ... it should not replace your basis ressources in your company.
    What you are doing is pretty complex (and the mixtrure of SPAM Update AND Basis SP seems to be wrong to me) and therefore, it will not be possible, to help you, just based on such a short dump.
    Sorry,
    Volker Gueldenpfennig, consolut international ag
    http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

  • Job getting cancelled with Tbale_illegal_statement dump

    hello,
    Hi Experts,
    i have a background job scheduled for a standard transaction SARA .it is getting cancelled and giving the following error:
    "TABLE_ILLEGAL_STATEMENT"
    Information on where terminated
    The termination occurred in the ABAP program "SAPLCKMLLAARCH" in
    "CKMLLA_INIT_READ".
    The main program was "RKSARCDL ".
    The termination occurred in line 253 of the source code of the (Include)
    program "LCKMLLAARCHF01"
    of the source code of program "LCKMLLAARCHF01" (when calling the editor 2530).
    The program "SAPLCKMLLAARCH" was started as a background job.
    The line it is giving Dump Is >       INSERT handle_tab.
    I have tried to debug the transaction but the execution is not ata all going to the program
    SAPLCKMLLAARCH where it is giving dump.Propably because that program is running in Background.
    So please let me know how I can fix this issue..Please

    Hi Prashanth,
    Were you able to resolve the issue ? Because, i am also facing the same problem, when I am triggering the Delete step for CO_CCMAST archiving object.
    Regards,
    Shail.

  • Reg:SAP_REORG_UPDATERECORDS job getting cancelled

    Hi Experts,
    I have a standard background job,SAP_REORG_UPDATERECORDS getting cancelled regularly in one of our production boxes.
    It runs only for a few seconds and then gets cancelled.
    The job log is.....
    "Job started
    Step 001 started (program RSM13002, variant SAP&001, user ID <XXXXXX>)
    Reorganization of update date not allowed in batch
    Job cancelled"
    I have searched for notes,but could not able to get the right solution
    kindly,help me resolve the issue
    Thnaks in advance
    Rgds-
    Venu

    Hello Venu,
    This job is no more needed as per recommenation from SAP
    Please go through the following notes:16083 and 67014 it shows that job is no more needed.This is the note of SAP about this job:
    "The standard job SAP_REORG_UPDATERECORDS that was contained in some delivered versions must no longer be executed (see Note 67014). In its new version, the underlying ABAP Program RSM13002 is programmed so that it terminates when running in a job (that is, in the background). Therefore, the job SAP_REORG_UPDATERECORDS always terminates in this case. In any case, the job SAP_REORG_UPDATERECORDS should be deleted from the pool of standard jobs, if it is still there: sm36 -> 'Standard jobs' -> 'Delete standard jobs'. In addition, released jobs that may exist and contain report RSM13002 should be deleted. You can find and delete these jobs using sm37."
    Rohit

  • Background landscape fetch getting cancelled in solman

    Dear All,
    I m getting Abap dump in Solution Manager .One of my Background process is getting cancelled Job 'Landscape Fetch' .
    I m pasting the dump here.
    Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
    xception              CX_SY_REF_IS_INITIAL
    ate and Time          07.06.2010 13:00:37
    Short text
    Access via 'NULL' object reference not possible.
    What happened?
        Error in the ABAP Application Program
        The current ABAP program "SAPLSMSY_ACTUALIZE_DATA" had to be terminated because
         it has
        come across a statement that unfortunately cannot be executed.
    What can you do?
        Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
        administrator.
      The exception must either be prevented, caught within proedure
    "SMSYAD_GET_DATA_FROM_LCR" "(FUNCTION)", or its possible occurrence must be
    declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
        Using Transaction ST22 for ABAP Dump Analysis, you can look
        at and manage termination messages, and you can also
        keep them for a long time.
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
         caught in
        procedure "SMSYAD_GET_DATA_FROM_LCR" "(FUNCTION)", nor was it propagated by a
         RAISING clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        You attempted to use a 'NULL' object reference (points to 'nothing')
        access a component (variable: "ACCESSOR").
        An object reference must point to an object (an instance of a class)
        before it can be used to access components.
        Either the reference was never set or it was set to 'NULL' using the
        CLEAR statement.
    How to correct the error
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL"
        "SAPLSMSY_ACTUALIZE_DATA" or "LSMSY_ACTUALIZE_DATAU14"
        "SMSYAD_GET_DATA_FROM_LCR"
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
        1. The description of the current problem (short dump)
           To save the description, choose "System->List->Save->Local File
        (Unconverted)".
        2. Corresponding system log
           Display the system log by calling transaction SM21.
           Restrict the time interval to 10 minutes before and five minutes
        after the short dump. Then choose "System->List->Save->Local File
        (Unconverted)".
        3. If the problem occurs in a problem of your own or a modified SAP
        program: The source code of the program
           In the editor, choose "Utilities->More
        Utilities->Upload/Download->Download".
        4. Details about the conditions under which the error occurred
    The exception must either be prevented, caught within proedure
    "SMSYAD_GET_DATA_FROM_LCR" "(FUNCTION)", or its possible occurrence must be
    declared in the
    RAISING clause of the procedure.
    I refer the following note number and implimented that 1042815.But its not working.
    I refer this follwing thread Re: Solution Manager 4.0  Re-Configuration
    Kindly suggest me how to resolve this.
    Regards
    Ashok

    Hello Ashok singh
    I think that this note below will help you to solve this issue. There's a PDF attached in this note that will help you to check this issue step by step. I believe that this issue is being caused by a problem with SLD.
      Number              768452
      Short text          Troubleshooting SLDCHECK - Releases 640, 70X

Maybe you are looking for

  • Third Party Plug Issue

    Questions about a few plugs. Downloaded the free version of digi's bomb factory BF76 (formerly UA1176) but not sure if it's compatible with L8 even though it's an RTAS plug. It self-installed but isn't showing up on the channel strip even after reboo

  • How to do changes in Z"ME2M"  (Copied report of ME2M)

    Hi Friends, The standard transaction ME2M gives the PO documents with the details of GRN & GRIR quantities to be delivered and quanities to be invoiced and the report output is based on the document date My Requirement is: I have to add a "Posting da

  • Labels in jdk1.4

    Hi, I just started using jdk1.4 and all the labels that used to have this java light purple color are now black. Is this a bug in jdk1.4 or do you have to manualy configure the labels in jdk1.4.

  • CDATA error.  Is it me or Sun?

    I have a sample xml below and Sun's java source code. When use jdk1.3.1 or 1.4 and jaxp as the parser, I got error when turn on validation. Also, the CDATA section does not show properly when turn of validation (only show: Diagram:). Why "Text" still

  • How can I archive my books on my iPhone to cloud?

    How can I archive my iBooks to cloud to achieve more space for other iBooks.