System.exit(0)   error in program.

Any help appreciated. Let me first put my code here:
Converts money using CurrencyConverter, there's another class I haven't posted here!! (which calculates conversion)
import java.util.* ;
public class CurrencyConverterTester
  public static void main(String[] args)
    Scanner in = new Scanner(System.in) ;
    System.out.println("How many euros is one dollar?") ;
    String input = in.nextLine() ;
    double rate = Double.parseDouble(input) ;
    CurrencyConverter myconverter = new CurrencyConverter(rate);
    System.out.println("Dollar value (Q to quit)") ;
    input = in.nextLine() ;
    while (true) {
      if (input == "Q"){
        System.exit(0);
        break;}
      else {
      System.out.println(input + " dollar = " +  myconverter.convert(Double.parseDouble(input)) + " euros");
      input = in.nextLine();
      continue;}   
}The issue is that the program won't terminate when I enter Q as my input?? I'm guessing it might have something to do my conversion from string to double in the 'else' statement, but not sure. Also, if you can suggest a more simpler method for the last 'while' statement, that would be helpful as well. Thanks. (noob to java)

paulcw wrote:
Curse Gosling for making + syntactic sugar for string append, but not overloading any other operators.@Paul
What did you expect from a duck ;-)
Seriously, yep, maybe it would have been better for noobs if the syntax of Java Strings was consistent with other kinds of Object... or maybe it would have been better if == was compiler-magiced into stringA.equals(stringB)... and the left and right shift operators have promise, and of course that way lies MADNESS, as witnessed in C++ ;-)
@OP... You are (IMHO) using the break, continue and especially System.exit() inappropriately... see my comments in your code...
    System.out.println("Dollar value (Q to quit)") ;
    input = in.nextLine() ;
    // while-true-loops are a "fairly usual" way of doing this kind of stuff,
    // but that doesn't make them "the preferred option". Typically you would
    // explore more "vanilla approaches" (which don't rely on the break and
    // continue statements)... leaping straight to the "tricky approach" means
    // you haven't (most often out of sheer laziness) thought it through... and
    // ALL good computer programs are thoroughly thought through (yep, try
    // saying that three times fast, especially after three beers).
    while (true) {
      // You don't compare Strings using ==
      if ( "Q".equalsIgnoreCase(input) ) {
        // Either of the following statements will do the job. The call to exit
        // will exit the JVM, therfore the break statement cannot be reached,
        // so it is superflous, so it's presence is just a bit confusing. Having
        // said that, "real programmers" don't use System.exe routinely, only in
        // the case of an emergency, such as handling a fatal-error, such as an
        // out-of-memory condition... an even then it's usually indicative of a
        // poor "system design", because it terminates the JVM which is running
        // this program without giving anything else in the program a chance to
        // clean-up after itself... like ask the user if they want to save there
        // work, or whatever.
        // I would use break (if anything) instead of System.exit
        // ... and if I wrote the Java tutorials, exit wouldn't be mentioned at
        // all until both "normal" flow control, and exception handling had both
        // been thoroughly covered.
        System.exit(0);
        break;
      } else {
        // I would break this line up, probably into three lines, simply becuase
        // it's syntatically "a long line".
        // Also the name "myconverter" doesn't tell what the class is/does.
        // IMHO, currencyConverter would be a better (more meaningful) name.
        // HERE'S HOW I WOULD WRITE IT
        // double dollars = Double.parseDouble(input);
        // double euros = currencyConverter.convert(dollars);
        // System.out.println(input + " dollar = " + euros + " euros");
        System.out.println(input + " dollar = " +  myconverter.convert(Double.parseDouble(input)) + " euros");
        input = in.nextLine();
        // This continue statement is superflous. continue says "go back to the
        // top of loop, reevaluate the loop-condition (true in this case) and
        // (if the condition is still true) "Play it again Sam".
        // ... which is exactly what will happen without this continue statement
        // and hence (IMHO) your code is easier to follow without it, simply
        // because another programmer may waste there time trying to figure out
        // WHY that continue statement is present.
        continue;
    }*ALSO:* The format of that code totally sucks. Braces all over the place; improper indentation. No wonder you're struggling to read your own code. Please read and abide the [The Java Code Conventions|http://java.sun.com/docs/codeconv/] (at least until you have the requisite experience to formulate credible and compelling arguments as to why your "style" is superior to the standard, and that's no small ask). Yes this is *important*... trust me on this (for now)... especially if you are going to ask for help on the forums... You're effectively wasting our time asking us to decipher your code because you are too lasy to format it correctly... and I for one find that "self entitled" attitude ugly, and offensive... Help us help you... you know?
And BTW.... Here's how I would actually do it.... no funky while-true, break, or continue... just a plain-ole'-while-woop....
package forums;
import java.util.Scanner;
public class KRC
  private static final Scanner SCANNER = new Scanner(System.in);
  public static void main(String[] args) {
    try {
      String input = null;
      while ( !"Q".equalsIgnoreCase(input=enterDollarAmount()) ) {
        System.out.println(input + " dollars is " +  Double.parseDouble(input) + " euros.");
        System.out.println();
    } catch (Exception e) {
      e.printStackTrace();
  private static String enterDollarAmount() {
    System.out.print("Please enter an amount in dollars : ");
    return SCANNER.nextLine();
}Edited by: corlettk on 25/10/2009 10:21 ~~ Distant Monarching Forum Markup!

Similar Messages

  • Getting an exit value from a program called thru a shell script

    how do i get the correct exit value always from a program called thru a shell script
    the getExitValue of the process works fine someitmes but not always ...
    Ex: write a pgm which sleeps for 5 secs & returns with exit(100).try to invoke this thru a script & try to run this script from Runtime.getRuntime.exec(..)
    ...the exit value is not same as 100.(it works if the sleep is not given though !!)
    can nebody help??

    ive done that ...see the sample code for ex..
    public void execute()
                   try{
                             Process program=Runtime.getRuntime().exec(cmd);
                             printOutput(program.getInputStream());
                             try
                                  program.waitFor();
                             catch(InterruptedException e)
                                  System.out.println("Command Interrupted: " + e);
              System.out.println("Error status : "+program.exitValue());
                        catch(SecurityException e)
                             System.out.println("Error executing program "+e);
                        catch(IOException e)
                             System.out.println("Error executing program "+e);
    ....

  • Capture System.exit

    Hello
    I am writing a program where I need to use utilities from a separate jar file. The only public entry point is that jar file's main method and it ends with System.exit
    Is there a way to capture the System.exit call so my program doesn't terminate?
    If so, can I capture the return value?
    Using Runtime.exec() is not preferred as it limits the number of command line parameters supplied to the called program.
    I'd appreciate any suggestions on how do do this or sugggestions on where to look for further information.
    aqd

    how could you expect me to use JAVA command without compiling it with Javac??
    I complied the java code using javac and then called(executed ) it using the Java..
    I am using JNI_Create/JavaVM() to create a JVM from CPP file. that works fine. Now, my issue is that I want to capture a couple of exit codes that are returned from the System.exit() of the java code.
    now, guys.. is there any way to capture that exit codes returning by Ssytem.exit() in or using JNI ??
    if yes, please help me with the code snippets.
    Thanks,
    Soujanya.R

  • Error Specify a value for variable-Abort System error in program SAPLRRK0 a

    Dear Experts,
    Could anyone help me to fix this issue?
    I have an Customer exit variable in my query to calulate the first week of the prior year value as per the system calendar. when i execute the query, I am receiving the following error messaged and i am throwing out from the BW server.
    The error message is
    Error Specify a value for variable ZR00**
    Abort System error in program SAPLRRK0 and form APPEND_KHANDLE_1-01-
    Many thanks in advance.
    Regards.
    Krishna.

    Hi Kishor,
    try runnig the same query in RSRT, with execute and debug option.
    Also check in query designer for its correctness.
    Hope this helps...
    Regards,
    umesh

  • The ABAP call stack was: SYSTEM-EXIT of program BBPGLOBAL

    Hi
    We are using SRM 5.0. We are facing a strange problem. We are able to see the initial screen of SRM EBP in the browser. But once the user name and password are provided the system goes for a dump with the following error:
    The following error text was processed in the system SS0 : System error
    The error occurred on the application server <Server Name> and in the work process 0 .
    The termination type was: ABORT_MESSAGE_STATE
    The ABAP call stack was: SYSTEM-EXIT of program BBPGLOBAL
    <b>SM21 Log:</b>
    Short Text
         Transaction Canceled &9&9&5 ( &a &b &c &d &e &f &g &h &i )
         The transaction has been terminated.  This may be caused by a
         termination message from the application (MESSAGE Axxx) or by an error
         detected by the SAP System due to which it makes no sense to proceed
         with the transaction.  The actual reason for the termination is
         indicated by the T100 message and the parameters.
    Transaction Canceled ITS_P 001 ( )
    Message Id: ITS_P
    Message No: 001
    I just checked these threads but did not help much,
    RABAX_STATE  error after loggin into BBPSTART service in SRM 4.
    ITS_TEMPLATE_NOT_FOUND error
    Besides I tried this note: 790727 as well, still I get the same error.
    Any help would be highly appreciated.
    Thanks in advance
    Kathirvel Balakrishnan

    Hi
    <u>Please do the following steps.</u>
    <b>When you are using the Internal ITS,you need not run the report W3_PUBLISH_SERVICES.(only SIAC_PUBLISH_ALL_INT )
    ALso pls check the foll:
    -->activate the services through SICF tcode.
    > Go to SICF transaction and activate the whole tree under the node Default host>sap>bc>gui>sap>its.
    >Also maintain the settings in SE80>utilities>settings>internet transaction server-->test service/Publish. (BBPSTART , BBPGLOBAL etc)
    Table TWPURLSVR should have entries for the / SRM server line as well as gui and web server.
    Could you please review again the following steps ?
    Did you check that ICM was working correctly (Transaction -  SMICM) ?
    1-Activate the necessary ICF services
    With transaction SICF and locate the
    services by path
    /sap/public/bc/its/mimes
    /sap/bc/gui/sap/its/webgui
    2- Publish the IAC Services
    With Transaction SE80 locate from
    the menu Utilities -> Settings ->
    Internet Transaction Server (Tab) ->
    Publish (Tab) and set “On Selected
    Site” = INTERNAL.
    3- Locate the Internet Services SYSTEM and WEBGUI.
    Publish these services with the Context
    Menu -> Publish -> Complete Service
    4- Browse to http://<server>:<icmport>/sap/bc/gui/
    sap/its/webgui/! and login to the
    webgui.</b>
    Hope this will help.
    Please reward suitable points.
    Regards
    - Atul

  • System error in program SAPLRRSV & Form RRSV_CHAVL_TO_VALUE_CONVERT

    Hi,
    While running a Bw Report I'm getting the following error:
    System error in program SAPLRRSV & Form RRSV_CHAVL_TO_VALUE_CONVERT
    When checking the report found that one of the Characteristic of the report is in incorrect Internal format. As a result it shows inconsistency when checking the values of the charactersitic for conversion exit.
    Tried correctin this error by doing a correct error but it didnt work.
    When checked the SID table the characteristics had some invalid records which are not maintained in the Master Data table.
    How to correct this error?
    -Thanks
    Sree

    Hi Sree,
    We're having the same problem. I'd like to know how to solve it. Could you please tell me how to do it?
    Thanks.
    Best regards,
    Julian.

  • Error on System.exit(0)

    Hi everybody.
    I'm running an application with JFrames. And everything works fine. But when i'm trying to close the main JFrame and reach the method System.exit(0); i get the next windows error.
    instruction on "0x77a7bb99" references to memory on "0x1c553ce0". Memory can't read.
    Do you know why i get this kind of error.
    I'm using java 1.4.1_01.
    Thank u for your time :)

    If i upgrade to 1.5 i don't see de Error dialog. But i get an EXCEPTION_ACCESS_VIOLATION:
    # An unexpected error has been detected by HotSpot Virtual Machine:
    # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x77a7bb99, pid=2184, tid=2848
    # Java VM: Java HotSpot(TM) Client VM (1.5.0_02-b09 mixed mode, sharing)
    # Problematic frame:
    # C [ole32.dll+0x2bb99]
    --------------- T H R E A D ---------------
    Current thread (0x00ac70a8): VMThread [id=2848]
    siginfo: ExceptionCode=0xc0000005, reading address 0x0c6c3d80
    Registers:
    EAX=0x0c6c3d80, EBX=0x0be13714, ECX=0x0be137b8, EDX=0x80000001
    ESP=0x02cafc28, EBP=0x02cafc6c, ESI=0x00000000, EDI=0x0be01568
    EIP=0x77a7bb99, EFLAGS=0x00010246
    Top of Stack: (sp=0x02cafc28)
    0x02cafc28: 0c6c3d80 00000001 0be13714 00000000
    0x02cafc38: 00000000 0be079e8 0009c320 00000001
    0x02cafc48: 0be00ec0 00000000 0009c320 0be05680
    0x02cafc58: 00000001 00000001 0009c320 00000001
    0x02cafc68: 0000000a 02cafc94 77ab2524 0be13714
    0x02cafc78: 0be13710 0be13794 00000000 00000000
    0x02cafc88: 00000000 00000001 0be14010 02cafcb4
    0x02cafc98: 77ab0550 00000002 0be137b8 0be13710
    Instructions: (pc=0x77a7bb99)
    0x77a7bb89: 47 14 50 8b 08 ff 51 08 83 67 14 00 8b 47 18 50
    0x77a7bb99: 8b 08 ff 51 10 f6 47 04 08 75 14 8b 4b 68 85 c9
    Stack: [0x02c70000,0x02cb0000), sp=0x02cafc28, free space=255k
    Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
    C [ole32.dll+0x2bb99]
    C [ole32.dll+0x62524]
    C [ole32.dll+0x60550]
    C [ole32.dll+0x604ad]
    C [dpDevClt.dll+0x3044]
    C [ntdll.dll+0x30e7]
    C [ntdll.dll+0xee02]
    C [KERNEL32.DLL+0x269c3]
    C [MSVCRT.dll+0x7cd8]
    V [jvm.dll+0x117825]
    V [jvm.dll+0x1179c5]
    V [jvm.dll+0x11775a]
    C [MSVCRT.dll+0x85bc]
    C [KERNEL32.DLL+0xb388]
    VM_Operation (0x0cbaf70c): exit, mode: safepoint, requested by thread 0x030a7e30
    --------------- P R O C E S S ---------------
    Java Threads: ( => current thread )
    0x030c0468 JavaThread "RMI ConnectionExpiration-[IP:1099]" daemon [_thread_blocked, id=2716]
    0x030742b0 JavaThread "TimerQueue" daemon [_thread_blocked, id=2820]
    0x00286d68 JavaThread "DestroyJavaVM" [_thread_blocked, id=2764]
    0x030a7e30 JavaThread "AWT-EventQueue-0" [_thread_blocked, id=1772]
    0x0306c008 JavaThread "AWT-Shutdown" [_thread_blocked, id=2108]
    0x02e4df58 JavaThread "Thread-2" [_thread_in_native, id=2468]
    0x03021b70 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=2412]
    0x00acdd60 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=2636]
    0x00acc910 JavaThread "CompilerThread0" daemon [_thread_blocked, id=2704]
    0x00ac8d90 JavaThread "Finalizer" daemon [_thread_blocked, id=2856]
    0x00a99dc0 JavaThread "Reference Handler" daemon [_thread_blocked, id=2772]
    Other Threads:
    =>0x00ac70a8 VMThread [id=2848]
    VM state:at safepoint (shutting down)
    VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
    [0x00286300/0x00000b18] Threads_lock - owner thread: 0x00ac70a8
    Heap
    def new generation total 576K, used 359K [0x22af0000, 0x22b90000, 0x22fd0000)
    eden space 512K, 57% used [0x22af0000, 0x22b39c08, 0x22b70000)
    from space 64K, 100% used [0x22b70000, 0x22b80000, 0x22b80000)
    to space 64K, 0% used [0x22b80000, 0x22b80000, 0x22b90000)
    tenured generation total 1408K, used 955K [0x22fd0000, 0x23130000, 0x26af0000)
    the space 1408K, 67% used [0x22fd0000, 0x230beea8, 0x230bf000, 0x23130000)
    compacting perm gen total 8192K, used 3377K [0x26af0000, 0x272f0000, 0x2aaf0000)
    the space 8192K, 41% used [0x26af0000, 0x26e3c510, 0x26e3c600, 0x272f0000)
    ro space 8192K, 66% used [0x2aaf0000, 0x2b0488a8, 0x2b048a00, 0x2b2f0000)
    rw space 12288K, 46% used [0x2b2f0000, 0x2b884818, 0x2b884a00, 0x2bef0000)
    Dynamic libraries:
    0x00400000 - 0x0040c000      C:\Archivos de programa\Java\jdk1.5.0_02\bin\java.exe
    0x78460000 - 0x784e3000      C:\WINNT\system32\ntdll.dll
    0x78ff0000 - 0x79052000      C:\WINNT\system32\ADVAPI32.dll
    0x79450000 - 0x7950d000      C:\WINNT\system32\KERNEL32.DLL
    0x77120000 - 0x77191000      C:\WINNT\system32\RPCRT4.DLL
    0x78000000 - 0x78045000      C:\WINNT\system32\MSVCRT.dll
    0x6d6b0000 - 0x6d835000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\client\jvm.dll
    0x77e10000 - 0x77e6f000      C:\WINNT\system32\USER32.dll
    0x77f40000 - 0x77f7b000      C:\WINNT\system32\GDI32.dll
    0x77550000 - 0x77581000      C:\WINNT\system32\WINMM.dll
    0x6d2f0000 - 0x6d2f8000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\hpi.dll
    0x68f70000 - 0x68f7b000      C:\WINNT\system32\PSAPI.DLL
    0x6d680000 - 0x6d68c000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\verify.dll
    0x6d370000 - 0x6d38d000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\java.dll
    0x6d6a0000 - 0x6d6af000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\zip.dll
    0x6d070000 - 0x6d1d6000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\awt.dll
    0x77800000 - 0x7781e000      C:\WINNT\system32\WINSPOOL.DRV
    0x79520000 - 0x79530000      C:\WINNT\system32\MPR.DLL
    0x75e30000 - 0x75e4a000      C:\WINNT\system32\IMM32.dll
    0x77a50000 - 0x77b3f000      C:\WINNT\system32\ole32.dll
    0x727a0000 - 0x727e6000      C:\WINNT\system32\ddraw.dll
    0x72840000 - 0x72846000      C:\WINNT\system32\DCIMAN32.dll
    0x72c90000 - 0x72d24000      C:\WINNT\system32\D3DIM700.DLL
    0x77590000 - 0x777db000      C:\WINNT\system32\shell32.dll
    0x70bd0000 - 0x70c35000      C:\WINNT\system32\SHLWAPI.dll
    0x71710000 - 0x71794000      C:\WINNT\system32\COMCTL32.dll
    0x6d2b0000 - 0x6d2ed000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\fontmanager.dll
    0x6d530000 - 0x6d543000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\net.dll
    0x74fe0000 - 0x74ff4000      C:\WINNT\system32\WS2_32.dll
    0x74fd0000 - 0x74fd8000      C:\WINNT\system32\WS2HELP.DLL
    0x6d550000 - 0x6d559000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\nio.dll
    0x10000000 - 0x10011000      C:\mobileclient\bin\oljdbc40.dll
    0x03540000 - 0x035cc000      C:\mobileclient\bin\olobj40.dll
    0x035d0000 - 0x035de000      C:\mobileclient\bin\olaes.dll
    0x035e0000 - 0x0360c000      C:\mobileclient\bin\olStdDll.dll
    0x75000000 - 0x75009000      C:\WINNT\system32\WSOCK32.dll
    0x70200000 - 0x70296000      C:\WINNT\system32\WININET.dll
    0x79640000 - 0x796c7000      C:\WINNT\system32\CRYPT32.dll
    0x77410000 - 0x77420000      C:\WINNT\system32\MSASN1.DLL
    0x779b0000 - 0x77a4b000      C:\WINNT\system32\OLEAUT32.dll
    0x780c0000 - 0x78121000      C:\WINNT\system32\MSVCP60.dll
    0x0ba30000 - 0x0ba3b000      C:\mobileclient\bin\olil125x.dll
    0x0ba40000 - 0x0ba68000      C:\mobileclient\bin\olod2040.dll
    0x0ba70000 - 0x0baeb000      C:\mobileclient\bin\olsql40.dll
    0x0bb30000 - 0x0bb48000      C:\WINNT\system32\VFJavaW42.dll
    0x0bb50000 - 0x0bbc0000      C:\WINNT\system32\VFinger.dll
    0x75120000 - 0x7516f000      C:\WINNT\system32\NETAPI32.dll
    0x790d0000 - 0x790df000      C:\WINNT\system32\Secur32.dll
    0x77bf0000 - 0x77c01000      C:\WINNT\system32\NTDSAPI.dll
    0x77980000 - 0x779a4000      C:\WINNT\system32\DNSAPI.DLL
    0x77950000 - 0x7797b000      C:\WINNT\system32\WLDAP32.DLL
    0x75170000 - 0x75176000      C:\WINNT\system32\NETRAP.dll
    0x75100000 - 0x7510f000      C:\WINNT\system32\SAMLIB.dll
    0x65440000 - 0x65447000      C:\WINNT\system32\wtsapi32.dll
    0x664d0000 - 0x664da000      C:\WINNT\system32\UTILDLL.dll
    0x77510000 - 0x77532000      C:\WINNT\system32\TAPI32.dll
    0x783c0000 - 0x78451000      C:\WINNT\system32\SETUPAPI.dll
    0x78df0000 - 0x78e52000      C:\WINNT\system32\USERENV.DLL
    0x655e0000 - 0x655ed000      C:\WINNT\system32\WINSTA.dll
    0x68950000 - 0x6895b000      C:\WINNT\system32\REGAPI.dll
    0x77300000 - 0x77317000      C:\WINNT\system32\MPRAPI.dll
    0x77390000 - 0x773bf000      C:\WINNT\system32\ACTIVEDS.DLL
    0x77360000 - 0x77383000      C:\WINNT\system32\ADSLDPC.DLL
    0x77830000 - 0x7783e000      C:\WINNT\system32\RTUTILS.DLL
    0x0bc70000 - 0x0bc84000      C:\WINNT\system32\SMJavaW.dll
    0x0bc90000 - 0x0bca3000      C:\WINNT\system32\ssl.DLL
    0x0bcd0000 - 0x0bce7000      C:\WINNT\system32\sslBiometrika.dll
    0x0bd00000 - 0x0bd1e000      C:\WINNT\system32\fx3scan.dll
    0x0bd30000 - 0x0bd91000      C:\WINNT\system32\fx3.dll
    0x77820000 - 0x77827000      C:\WINNT\system32\VERSION.dll
    0x75980000 - 0x75986000      C:\WINNT\system32\LZ32.DLL
    0x0beb0000 - 0x0bec9000      C:\WINNT\system32\sslFile.dll
    0x76b10000 - 0x76b4e000      C:\WINNT\system32\comdlg32.dll
    0x0bee0000 - 0x0bef7000      C:\WINNT\system32\sslST.dll
    0x0bf10000 - 0x0bf5d000      C:\WINNT\system32\tci.dll
    0x0bf70000 - 0x0bf89000      C:\WINNT\system32\sslUareU.dll
    0x0bfa0000 - 0x0bfba000      C:\WINNT\system32\dpFpFns.dll
    0x0bfc0000 - 0x0bfca000      C:\WINNT\system32\dpDevDat.dll
    0x0bfd0000 - 0x0bff3000      C:\WINNT\system32\dpDevClt.dll
    0x0c000000 - 0x0c071000      C:\WINNT\system32\dpFtrEx.dll
    0x0c080000 - 0x0c0db000      C:\WINNT\system32\dpMatch.dll
    0x0c560000 - 0x0c5f0000      C:\WINNT\system32\CLBCATQ.DLL
    0x0c680000 - 0x0c6be000      C:\Archivos de programa\DigitalPersona\Bin\DPPS.dll
    0x7ca00000 - 0x7ca23000      C:\WINNT\system32\rsabase.dll
    0x0c6d0000 - 0x0c6f3000      C:\WINNT\system32\rsaenh.dll
    0x0c700000 - 0x0c904000      C:\WINNT\system32\msi.dll
    0x74f80000 - 0x74f9e000      C:\WINNT\system32\msafd.dll
    0x74fc0000 - 0x74fc7000      C:\WINNT\System32\wshtcpip.dll
    0x77840000 - 0x7784c000      C:\WINNT\System32\rnr20.dll
    0x77320000 - 0x77333000      C:\WINNT\system32\iphlpapi.dll
    0x77500000 - 0x77505000      C:\WINNT\system32\ICMP.DLL
    0x774c0000 - 0x774f3000      C:\WINNT\system32\RASAPI32.DLL
    0x774a0000 - 0x774b1000      C:\WINNT\system32\RASMAN.DLL
    0x77340000 - 0x77359000      C:\WINNT\system32\DHCPCSVC.DLL
    0x777e0000 - 0x777e8000      C:\WINNT\System32\winrnr.dll
    0x777f0000 - 0x777f5000      C:\WINNT\system32\rasadhlp.dll
    0x6d660000 - 0x6d666000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\rmi.dll
    VM Arguments:
    java_command:
    Environment Variables:
    CLASSPATH=C:\mobileclient\bin\msync.jar;C:\codigos\almacen\classes;C:\mobileclient\bin\olite40.jar;C:\mobileclient\bin\webtogo.jar
    PATH=c:\j2sdk1.4.1_01\bin\;;C:\mobileclient\bin;C:\oracle\ora92\bin;C:\Archivos de programa\Oracle\jre\1.3.1\bin;C:\Archivos de programa\Oracle\jre\1.1.8\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\Archivos de programa\Symantec\pcAnywhere\;c:\winnt;c:\winnt\respair;c:\grupotelnet\classes;c:\grupotelnet;c:\GrupoTelnet\comandera;c:\GrupoTelnet\comandera\config;c:\j2sdk1.4._01\bin;C:\WINNT\system32;c:\grupotelnet\classes;c:\GrupoTelnet;C:\mobileclient\bin
    USERNAME=Administrador
    OS=Windows_NT
    PROCESSOR_IDENTIFIER=x86 Family 15 Model 1 Stepping 3, GenuineIntel
    --------------- S Y S T E M ---------------
    OS: Windows 2000 Build 2195 Service Pack 4
    CPU:total 1 family 15, cmov, cx8, fxsr, mmx, sse, sse2, ht
    Memory: 4k page, physical 515568k(63456k free), swap 876852k(302676k free)
    vm_info: Java HotSpot(TM) Client VM (1.5.0_02-b09) for windows-x86, built on Mar 4 2005 01:53:53 by "java_re" with MS VC++ 6.0

  • Program exits with the System.exit(3) exit code, help?

    When I ran my program(a simulation for a wind powered vehicle), it suddenly ends with no apparent reason, and returns System.exit(3) exit code.
    I have no Idea what this exit code means, and thus am stuck in the debugging...
    Help is greatly appreciated

    No error messages?
    If not, then you need to search for all instances of
    catch (WhateverException var) {}and replace them with
    catch (WhateverException var) {
      var.printStackTrace();
    }

  • SYNTAX_ERROR unable to log in to SAP system Syntax error in program "SAPMSE

    hi SAP Experts,
    I have applied Basis patch 12 and I scheduled the background.  Backgroud job was terminated. System became slow. Then I stopped the server and restarted.  Now, I am unable to log in to SAP GUI by entering Username and Password and getting syntax error.
    Syntax error in program "SAPMSEM1".
    What happened?
    Error in the ABAP Application Program
    The current ABAP program '????????????????????????????"
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occured in program "SAPMSEM1" in include
    "CL_SALV_FORM_ELEMET==========CU" in
    line 13:
    "the type "IF_SALV_FORM_CONFIG" is unknown."
    The include has been created and last changed by:
    Created by: "SAP "
    Last Changed by: "SAP "
    I am unable to access any transction code.
    Please help me..
    Thanks in advance...
    Raju

    hi,
    Thanks for your response.
    i haven't take any back up.  can u pls tell me step by step procedure to implement the SP with TP.
    your answer will be helpful..
    Regards
    Raju

  • Unable to login in the system ---- Syntex Error is Program SAPLSFES

    Hi,
    We have Sol_Man 7(N/W 700) in Win2003 and MSSQL 2005.
    During Support pack SAPKB70014 application in our Soloution Manager, I have continued all the step in Dialog but today it shows a message that "Inform SAP system for tp termination".The SP application was running for almost 12-14hrs.
    Then I restart my SAP system.Now when I opening SAP GUI
    Message is comming
    ABAP Runtime Error   Error Code <no erorr name or code was mentioned >
    In bottom of the page messege is comming
    " Syntex Error is Program SAPLSFES "
    Login name & password not asking.
    I also found in the Slog that
    "WARNING:       Background job RDDIMPDP could not be started or terminated abnormally."
    In SAPIB70014
    2EETW000 sap_dext called with msgnr "1":
    2EETW000 -
    db call info -
    2EETW000 function:   db_xrtab
    2EETW000 fcode:      RT_MI_LOAD
    2EETW000 tabname:    SPROXHDR                     
    2EETW000 len (char): 1740
    2EETW000 key:        CLASCX_SERVICES_REGISTRY_SIPUBLIS8 CLASCX_SERVICES_REGISTRY_SIPUBLIS82F7E61BA8717B7CD295188A843F6CB8E97F12D39
    2EETW000 retcode:    1
    2EETW125 SQL error "1105" during "" access: "[1105] Could not allocate space for object 'dbo.SPROXHDR'.'SPROXHDR~HAS' in database 'SM1' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup."
    I also checked and found that TRBAT table contains only header information where as TRJOB table is empty.
    Also found tp.exe in Task Manager.
    I have already created a message with SAP.
    Please guide me in this regard.
    Regards,
    Partha

    WARNING: Background job RDDIMPDP could not be started or terminated abnormally."
    login into Client 000 and schedule the background job again.
    Could not allocate space for object 'dbo.SPROXHDR'.'SPROXHDR~HAS' in database 'SM1' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup."
    Check the database space also. i think there is some space problem also, you need to add some space or need to add datafile.
    Regards,
    Subhash

  • SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

    Hello,
    We are doing an installation of SAP NW 7.01 SR1 on V6R1.
    <br>
    We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
    <br>
    We are again getting error in following steps:
    <br>
    sapinst.log
    <br>
    <br>WARNING 2009-09-30 23:25:28.477
    Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
    IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
    J9VM - 20090309_31291_BHdSMr
    JIT  - 20090210_1447ifx1_r8
    GC   - 200902_24)
    I<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
    <br>Loading of 'SAPNTAB' import package: OK
    <br>Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
    Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
    Loading of 'DOKCLU' import package: OK
    Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
    Loading of 'SAPAPPL1' import package: OK
    Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
    Loading of 'DD03L' import package: OK
    Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
    Loading of 'SCPRSVALS' import package: OK
    Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
    Loading of 'SAPSDIC' import package: OK
    Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
    Loading of 'SCPRVALS' import package: OK
    Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
    Loading of 'SAPSSRC' import package: OK
    Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
    Loading of 'FUPARAREF' import package: OK
    Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
    Loading of 'TODIR' import package: OK
    Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
    Loading of 'SEOSUBCODF' import package: OK
    Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
    Loading of 'E071K' import package: OK
    Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
    Loading of 'SAPPOOL' import package: OK
    Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
    Loading of 'SAPSPROT' import package: OK
    Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
    Loading of 'SAPSDOCU' import package: OK
    Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
    Loading of 'SAPCLUST' import package: OK
    Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
    Loading of 'SAPSLOAD' import package: OK
    Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
    Loading of 'SAPSLEXC' import package: OK
    Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
    Loading of 'SAPUSER' import package: OK
    Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
    Loading of 'SAPDDIM' import package: OK
    Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
    Loading of 'SAPDFACT' import package: OK
    Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
    Loading of 'SAPDODS' import package: OK
    Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
    Loading of 'SAPUSER1' import package: OK
    Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
    Loading of 'SAP0000' import package: OK
    Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
    Loading of 'SAPAPPL0' import package: OK
    Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
    Loading of 'SAPSSEXC' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
    <br>
    WARNING[E] 2009-09-30 23:25:28.524
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
    <br>
    ERROR 2009-09-30 23:25:28.914
    FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    <br>
    <br>import_monitor.log.
    <br>****************************************************************************************************************************************************
    <br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is successfully completed.
    <br>
    WARNING: 2009-09-30 23:31:31
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2009-09-30 23:31:31
    1 error(s) during processing of packages.
    INFO: 2009-09-30 23:31:31
    Import Monitor is stopped.
    <br>*************************************************************************************************************************************************
    <br>SAPAPPL02.LOG
    <br>**************************************************************************************************************************************************
    <br>TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) INFO: TVV1 created #20091001110304
    <br>
    (DB) INFO: TVV1 deleted/truncated #20091001110304
    <br>
    (IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
    <br>
    (DB) ERROR: DDL statement failed<br>
    (ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
    DbSlExecute: rc = 99<br>
      (SQL error -539)<br>
      error message returned by DbSl:
    Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
    Your inputs will help a lot.
    Regards,
    Prasad

    Hello,
    We are doing an installation of SAP NW 7.01 SR1 on V6R1.
    <br>
    We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
    <br>
    We are again getting error in following steps:
    <br>
    sapinst.log
    <br>
    <br>WARNING 2009-09-30 23:25:28.477
    Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
    IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
    J9VM - 20090309_31291_BHdSMr
    JIT  - 20090210_1447ifx1_r8
    GC   - 200902_24)
    I<br>mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
    <br>Loading of 'SAPNTAB' import package: OK
    <br>Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
    Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28.<br>
    Loading of 'DOKCLU' import package: OK
    Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28.<br>
    Loading of 'SAPAPPL1' import package: OK
    Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28.<br>
    Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28.<br>
    Loading of 'SAPAPPL2' import package: ERROR
    Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28.<br>
    Loading of 'DD03L' import package: OK
    Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.<br>
    Loading of 'SCPRSVALS' import package: OK
    Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28.<br>
    Loading of 'SAPSDIC' import package: OK
    Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28.<br>
    Loading of 'SCPRVALS' import package: OK
    Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28.<br>
    Loading of 'SAPSSRC' import package: OK
    Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28.<br>
    Loading of 'FUPARAREF' import package: OK
    Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28.<br>
    Loading of 'TODIR' import package: OK
    Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28.<br>
    Loading of 'SEOSUBCODF' import package: OK
    Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28.<br>
    Loading of 'E071K' import package: OK
    Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28.<br>
    Loading of 'SAPPOOL' import package: OK
    Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28.<br>
    Loading of 'SAPSPROT' import package: OK
    Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28.<br>
    Loading of 'SAPSDOCU' import package: OK
    Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28.<br>
    Loading of 'SAPCLUST' import package: OK
    Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28.<br>
    Loading of 'SAPSLOAD' import package: OK
    Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28.<br>
    Loading of 'SAPSLEXC' import package: OK
    Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28.<br>
    Loading of 'SAPUSER' import package: OK
    Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28.<br>
    Loading of 'SAPDDIM' import package: OK
    Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28.<br>
    Loading of 'SAPDFACT' import package: OK
    Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28.<br>
    Loading of 'SAPDODS' import package: OK
    Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28.<br>
    Loading of 'SAPUSER1' import package: OK
    Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28.<br>
    Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28.<br>
    Loading of 'SAP0000' import package: OK
    Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28.<br>
    Loading of 'SAPAPPL0' import package: OK
    Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28.<br>
    Loading of 'SAPSSEXC' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.<br>
    <br>
    WARNING[E] 2009-09-30 23:25:28.524
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
    <br>
    ERROR 2009-09-30 23:25:28.914
    FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    <br>
    <br>import_monitor.log.
    <br>****************************************************************************************************************************************************
    <br>INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPAPPL0' import package is successfully completed.
    <br>
    INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPSSEXC' import package is successfully completed.
    <br>
    WARNING: 2009-09-30 23:31:31
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2009-09-30 23:31:31
    1 error(s) during processing of packages.
    INFO: 2009-09-30 23:31:31
    Import Monitor is stopped.
    <br>*************************************************************************************************************************************************
    <br>SAPAPPL02.LOG
    <br>**************************************************************************************************************************************************
    <br>TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) INFO: TVV1 created #20091001110304
    <br>
    (DB) INFO: TVV1 deleted/truncated #20091001110304
    <br>
    (IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
    <br>
    (DB) ERROR: DDL statement failed<br>
    (ALTER TABLE "TVV1" DROP PRIMARY KEY )<br>
    DbSlExecute: rc = 99<br>
      (SQL error -539)<br>
      error message returned by DbSl:
    Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
    Your inputs will help a lot.
    Regards,
    Prasad

  • PE 11 new install on WinXP system - Debug event error, can't open program

    Hi everyone,
    I searched the community for similar errors and followed a couple of troubleshooting steps suggested for older versions of PE, but they didn't work. I just installed Premiere Element 11 on my Windows XP office desktop (also installed PS Elements 11, which works without a problem.) Install went well and I rebooted the system as prompted. Every time I attempt to open Premiere however (I am not attempting to load any video files, I just want to open the program to start a new project), I get the splash screen at first, but after a few seconds of "Loading" and/or "Initializing" a bunch of parameters, the program hangs and following screen pops up:
    "Premiere Element Debug Event"
    Premiere Element has encountered an error.
    [..\..\Src\Core\Preferences.ccp-338]
    Continue
    When I click on "Continue" the following window pops up:
    "Microsoft Visual C++ Runtime Library"
    Runtime Error!
    Program: ..e\Adobe Premiere Elements 11\Adobe Premiere Elements.exe
    The application has requested the Runtime to terminate in an unusual way.
    Please contact the application's support team for more information.
    OK
    So, here I am support team... Need more information, lol. I will also add that clicking the OK after the second window pops up often doesn't close the Premiere splash window still visible in the background, I have to CTRL-ALT-DEL and kill it manually by ending the process in Task Manager.
    I installed the same program - same s/n - on my home computer as well, with no issues (that's a much newer, and much faster, Windows 8.1 system however.) I think you are entitled to install 2 copies though, right? So this wouldn't be related to too many attempts to register the same software?
    Thanks for any help.

    umbertob
    Wea re not Adobe. We are Premiere Elements users who visit here under our own free will (unscheduled) to help other Premiere Elements users with their Premiere Elements workflows.
    Please detail the resources of your Windows XP computer. What edition is it...professional, home premium, or other? You realize come April 2014 Microsoft will discontinue support for Windows XP. Apparently you can continue to use it, but Microsoft points to security risks in that state.
    a. how much installed RAM, how much available
    b. how much free hard drive space
    c. is the video card/graphics card used by the computer up to date according to the web site of the manufacturer of the video card/graphics card.
    Did you install the program to the computer default location according to the installation process?
    Please review and then we can discuss the details.
    Thank you.
    ATR

  • Abort system error in program CL_RSDM_READ_MASTER_DATA and form_sidval_dire

    HI All,
    The following error is thrown when I execute the query.
    abort system error in program CL_RSDM_READ_MASTER_DATA and form_sidval_direct_
    However, earlier today, I ran this query successfully several times.This Query is on a multiprovider.
    Appreciate your help in advance.
    Regards,
    Harika

    Dear Harika,
    Try to repair at RSRV and check.
    Check: Re: SID error for characteristic
    Srini

  • BW-WebI Report: MDDataSetBW.GetCellData.  System error in program

    Hi,
    I'm trying to run a WebIntelligence Report connected with BW Query but return error before showing the results.
    The error is:
    Error in MDDataSetBW.GetCellData.  System error in program CL_RSDRC_MULTIPROV and form SETRESOLVE-01- (consid.TxtDescrit.). (WIS 10901)
    My query in BO contain 8 dimensions and 2 measures.
    Someone has been there?
    Tks!
    Edited by: Peeter Cassiano Antunes Bonomo on Sep 6, 2011 7:33 PM

    Ingo,
    running the query in RSRT with the same elements works perfectly.The results are displayed.
    But tested the MDX query in the transaction MDXTest and entered in the ABAP Debugger, press F8 and the following message appeared:
    "The current application triggered a termination with a short dump".
    "The current application program detected a situation which really should not occur. Therefore, a termination with a short dump was triggered on purpose by the key word MESSAGE (type x)."
    "Short text of error message:
    System error in program SAPLRRK0 and form CHECK_KHANDLE (consid.TxtDescrit)."
    Does that help?
    Tks,
    Edited by: Peeter Cassiano Antunes Bonomo on Sep 9, 2011 3:18 PM

  • !!System error in program SAPLRS_EXCEPTION and form RS_EXCEPTION_TO_MESSAGE

    Hi Gurus,
    Mater data text loading from a DSO to a InfoObject has failed in the process Chain at DTP step while trying to extract Data packet 2 from the DSO.
    In the log i am getting following error message:
    "System error in program SAPLRS_EXCEPTION and form RS_EXCEPTION_TO_MESSAGE (see long text)
    Message no. BRAIN299".
    Please help urgent.
    FYI.....
    we have recently done upgrade from BI/ABAP SP11 to SP15 and the latest Java SP || 14 (both included in SPS 14).
    Points will surely be awarded.
    Thanks,
    Anurag

    Hello Anurag,
    Could you solve this problem? If so, please share the solution with me. I'm getting the same error while loading data using DTPs.
    Regards,
    Neha

Maybe you are looking for