Module 'net_rim_b​b_qm_platf​orm' not found on Bold 9900

I purchased a backgammon game from App World and after playing it just once I now get the following message when I try to open the game "Error starting backgammon: Module 'net_rim_bb_qm_platform' not found". I contacted the game developer who told me it had nothing to do with them and that I had to deal with RIM.  I have tried uninstalling and re-installing the game and still get the same message.  I haven't been able to find any info anywhere so if anyone can help that would be greatly appreciated.
Thanks.

Normally a battery pull will correct this issue so I'm going to recommend you remove your battery while your phone is powered on then replace it a few seconds later.
Let us know if that helps you.  
- If my response has helped you, please click "Options" beside my post and mark it as solved. Clicking the "thumbs up" icon near the bottom of my response would also be appreciated.

Similar Messages

  • Error initializing ejb-module; Exception javac.exe not found under

    Dear all,
    I got followings error after i had tried to doing some lab.I had checked the folder "C:\Program Files\Oracle\jre\1.3.1" exists but missed but missing javac.exe. Could anyone can advice me what is going wrong?
    04/04/14 16:44:20 Auto-deploying - web/WEB-INF/classes (No previous deployment found)...
    04/04/14 16:44:20 Error instantiating application 'lab04' at file:/C:/share/oc4j
    /labs/lab04/: Error initializing ejb-module; Exception javac.exe not found under
    C:\Program Files\Oracle\jre\1.3.1, please use a valid jdk or specify the locati
    on of your java compiler in server.xml using the <java-compiler .../> tag
    Thanks in advance!
    Best Regards,
    Chris CHIU

    Dear Chris,
    The answer lies in the error message you got, namely:
    please use a valid jdkAccording to your post, you don't have a JDK, you only have a JRE. The javac compiler is part of the JDK, it is not part of the JRE.
    You can download the JDK from the J2SE Download Web page. Look for the Download J2SE SDK link -- do not choose the Download J2SE JRE link!
    Good Luck,
    Avi.

  • Connector Error: u2018Function module u201C/CRYSTAL/GET_OSQL_OBJECT_LISTu201D not found

    Hello experts,
    I have installed Crystal Reports 2008 (not BO Edge) and BusinessObjects Integration Kit for SAP on my laptop and I try to connect my crystal reports to the SAP ECC 6.0 data source. After establishing a connection I can see the following groups in the Available Data Sources: CL [Data Clusters], DD [Data Dictionary] and FN [ABAP Function modules]. However when I try to open them, I get messages:
    - Database Connector Error: u2018Function module u201C/CRYSTAL/GET_OSQL_OBJECT_LISTu201D not found.u2019
    - Database Connector Error: u2018RFC_INVALID_HANDLEu2019
    Could you please give some advice, what is missing?
    Best regards,
    Marcin

    Hi Ingo,
    The Installation Guide u201CBusiness Objects Integration Kit for SAP u2013 Installation and Configurationu201D (created on 01.10.2008, where you are the author) that is listed on the integration kit download page:
    https://www.sdn.sap.com/irj/boc/index?rid=/webcontent/uuid/806c9894-42a5-2b10-648a-d900489b76da [original link is broken]
    refers to BusinessObjects Enterprise / SAP NetWeaver BI combination.
    As I am interested in the Crystal Reports 2008 / mySAP ERP combination I searched for further documents and could find the following, where the ABAP transports are described:
    u201EBusiness Objects XI Integration for SAP Solutions Installation Guideu201D issued on 03.06.2008
    and
    u201EBusiness Objects XI Integration for SAP Solutions Installation and Administration Guideu201D issued on 02.12.2008.
    Is one of these documents the u201Einstallation guide for the SAP Integration Kitu201D that you mentioned? If not, could you please send the link to the installation guide you mean, where the ABAP transports for Crystal Reports 2008 / mySAP ERP combination are described? That would be very helpful.
    Marcin

  • Xorg: module "glx" and commands not found???

    Hello, all.
    I'm fairly new to Linux but I'm not a total noob. I have FC6 on my laptop and am currently trying to get a GUI working for Arch on my desktop.
    I pacman-ed hwd, and ran it to create a Xorg.conf, and upon running it I get the following errors:
    (EE) Failed to load module "glx" (module does not exist, 0)
    /etc/X11/xinit/xinitrc: line 28: twm: command not found
    /etc/X11/xinit/xinitrc: line 29: xclock: command not found
    /etc/X11/xinit/xinitrc: line 30: xterm: command not found
    /etc/X11/xinit/xinitrc: line 31: xterm: command not found
    /etc/X11/xinit/xinitrc: line 32: exec: xterm: not found
    waiting for X server to shut down FreeFontPath: FPE "/usr/share/fonts/misc:unscaled" refcount is 2, should be 1; fixing.
    The last comment it makes I know isn't critical, so I'm not worried about that. But I need help with the "glx" part and the commands not found.
    Thanks in advance.

    Did you installed libgl-dri? If not install it, and it will fix glx problems.
    For the command not found, you need to create a ~/.xinitrc file. Before, you'll need to install the WM/DE that you want to use.
    There is a sample file in the wiki: http://wiki.archlinux.org/index.php/Sta … ents_HOWTO

  • Error in Dialog Module  - INCLUDE report "%_HR9066" not found

    Hi,
    After upgrade from 4.6B to ECC 6.0.When i display/create/change Custom Infotype 9072  in transaction PA30. i encounter a dump stating
    INCLUDE report "%_HR9066" not found. It occurs when the program goes for CALL DIALOG... in the SAP standard program.
    Do advice on how to resolve this issue

    Hi Chayan,
    9066 is the custom infotype .
    After upgrading check for the following things which are related to infotype :
    1) Go to se51 and check for Program MP906600 and screen 2000 exist .If not there is a problem in calling the screen
    2)Go to se11 and check whether the table PA9066 and structure P9066 exist
    3)Check whether the infotype is assigned to the Infotypes in spro .(Optional)
    If everthing is suceessful , the infotype exist in the system . If not one of the objects might miss from the above list .
    Regards,
    Gajalkshmi

  • CDMC - Function Modules not Found

    Hi,
    Initially the Solution manager ST level is 23 and CDMC clearning analysis worked will with ERP satellite system.
    Later, Solution manager has upgraded with 24 and not able to actiavate the statistics and unable to perform clearning analysis.
    Below are 2 known errors(there could be more),
    Function Modules "CNV_CDMC_CC_GET_COMPS_OF_SYS" and "CNVCDMC_OBJECT_EXISTENCE_CHECK" not found.
    Did any face this similar issues ?
    Do we need to consider any component upgrade at Satellite systems  with respect these upgrades in solution manager ?
    Note: 3 of components are upgraded in solution manager which are ST , ST-A/PI and ST-SER...
    Regards,

    Hello,
    If you are on ST-PI SP03 this note is needed in all the participating systems of your CDMC project
    1509340 - Collective Note with all corrections for CDMC (ST-PI SP03)
    Also pleae review SAP Note 1348772 -  CDMC Corrections - Composite SAP NotePlease look under Solution for Support Package 03 relevant Notes:
    This will ensure that your system works without errors!
    Regards,
    Paul

  • I have lightroom 5.7 and a macbook pro 10.9.5.  Occasionally when I am editing a photo in the develop module, I suddenly get a "file not found" message and the editing ceases to work.  There is no "exclamation" icon below the histogram box in the Library

    I have lightroom 5.7 and a macbook pro 10.9.5.  Occasionally when I am editing a photo in the develop module, I suddenly get a "file not found" message and the editing ceases to work.  There is no "exclamation" icon below the histogram box in the Library module or on the photo in grid view, and the histogram is gone.  What is going on? Trying to find it using the "find missing photos" in the library menu does nothing.

  • G_G_IDOC_REC_ZZINCOT function module not found in ECC 5.0

    i am getting the dump.
    the fuction module is not presend in ECC 5.0
    Runtime Errors         CALL_FUNCTION_NOT_FOUND                                                     
    Exceptn                CX_SY_DYN_CALL_ILLEGAL_FUNC                                                 
    Date and Time          04/05/2007 07:13:25                                                         
    ShrtText                                                                               
    Function module "G_G_IDOC_REC_ZZINCOT" not found.                                             
    What happened?                                                                               
    The function module "G_G_IDOC_REC_ZZINCOT" was called, but cannot be                          
        found in the Function Library.                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLGUIF" had to be terminated because one of the                   
        statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                         
    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                                                                               
    An exception occurred. This exception is dealt with in more detail below                      
        . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC',                
         was neither                                                                               
    caught nor passed along using a RAISING clause, in the procedure                              
         "IDOC_INPUT_GLROLL" "(FUNCTION)"                                                             
    Since the caller of the procedure could not have expected this exception                      
         to occur, the running program was terminated.                                                
        The reason for the exception is:                                                              
        The program "SAPLGUIF" contains a CALL FUNCTION statement. The name                           
        of the function module to be called is "G_G_IDOC_REC_ZZINCOT".                                                                               
    No function module exists with the name "G_G_IDOC_REC_ZZINCOT".                               
        All function modules are stored in the Function Library (SE37).                                                                               
    Possible reasons:                                                                               
    a) Wrong name specified. Particular attention should be paid                                  
           to upper/lower case and underscores ("_")                                                  
        b) Transport error                                                                               
    c) If an enqueue/dequeue module has been used, the lock object                                
           may not have been activated (ABAP Dictionary)                                              
           may not have been activated (ABAP Dictionary).                                             
    How to correct the error                                                                               
    Check the last transports to the R/3 System.                                                  
        Is the program "SAPLGUIF" currently being changed?                                            
        If an enqueue/dequeue module is involved, is the activation                                   
        of the lock object missing in the ABAP/4 Dictionary?                                                                               
    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:                                                                               
    "CALL_FUNCTION_NOT_FOUND" CX_SY_DYN_CALL_ILLEGAL_FUNCC                                        
        "SAPLGUIF" or "LGUIFU05"                                                                      
        "IDOC_INPUT_GLROLL"                                                                               
    Function modules with names similar to "G_G_IDOC_REC_ZZINCOT":                                                                               
    G_G_IDOC_REC_COFIT                                                                               
    G_G_IDOC_REC_FILCT                                                                               
    G_G_IDOC_REC_ECMCT                                                                               
    G_G_IDOC_REC_GLPCT                                                                               
    G_G_IDOC_REC_GLT0                                                                               
    G_G_IDOC_REC_SECURE                                                                               
    G_POSTING_ZZINCOT                                                                               
    G_G_IDOC_SEND_COFIT                                                                               
    G_G_IDOC_SEND_ECMCT                                                                               
    G_G_IDOC_SEND_SECURE                                                                               
    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.                                               
        The exception must either be prevented, caught within the procedure                           
         "IDOC_INPUT_GLROLL"                                                                               
    "(FUNCTION)", or declared in the procedure's RAISING clause.                                  
        To prevent the exception, note the following:                                                 
    System environment                                                                               
    SAP Release.............. "640"                                                                               
    Application server....... "d48ix100"                                                          
        Network address.......... "151.162.153.62"                                                    
        Operating system......... "AIX"                                                               
        Release.................. "5.3"                                                               
        Hardware type............ "00C65EFD4C00"                                                      
        Character length......... 8 Bits                                                              
        Pointer length........... 64 Bits                                                             
        Work process number...... 2                                                                   
        Short dump setting....... "full"                                                                               
    Database server.......... "d48ix100"                                                          
        Database type............ "ORACLE"                                                            
        Database name............ "D48"                                                               
        Database owner........... "SAPR3"                                                                               
    Character set............ "en_US.ISO8859-1"                                                                               
    SAP kernel............... "640"                                                               
        Created on............... "Nov 5 2006 20:46:58"                                               
        Created in............... "AIX 1 5 00538A4A4C00"                                              
        Database version......... "OCI_920 "                                                                               
    Patch level.............. "156"                                                               
        Patch text............... " "                                                                               
    Supported environment....                                                                     
        Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE                        
         10.2.0.."                                                                               
    SAP database version..... "640"                                                               
        Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"                                                                               
    Memory usage.............                                                                     
        Roll..................... 16128                                                               
        EM....................... 8379856                                                             
        Heap..................... 0                                                                   
        Page..................... 16384                                                               
        MM Used.................. 2530176                                                             
        MM Free.................. 1657232                                                             
        SAP Release.............. "640"                                                                               
    User and Transaction                                                                               
    Client.............. 010                                                                      
        User................ "OS0730"                                                                 
        Language key........ "E"                                                                      
        Transaction......... "YICUPLD "                                                               
        Program............. "SAPLGUIF"                                                               
        Screen.............. "SAPMSSY0 1000"                                                          
        Screen line......... 6                                                                        
    Information on where terminated                                                                   
        The termination occurred in the ABAP program "SAPLGUIF" in "IDOC_INPUT_GLROLL".               
        The main program was "Y21091IRECON ".                                                                               
    The termination occurred in line 65 of the source code of the (Include)                       
         program "LGUIFU05"                                                                               
    of the source code of program "LGUIFU05" (when calling the editor 650).                       
        Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_FUNC"                 
         occurred in the                                                                               
    procedure "IDOC_INPUT_GLROLL" "(FUNCTION)" but was not handled locally, not                   
         declared in the                                                                               
    RAISING clause of the procedure.                                                              
        The procedure is in the program "SAPLGUIF ". Its source code starts in line 5                 
        of the (Include) program "LGUIF$05 ".                                                         
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    35                                                                               
    36 *Prüfen, ob Customizing richtig eingestellt ist                                             
       37     CHECK EXIT IS INITIAL.                                                                  
       38     PERFORM CHECK_CUSTOMIZING USING IDOC_NUMBER.                                            
       39                                                                               
    40 *Für Einzelposten neue Belegnummern vergeben                                                
       41     CHECK EXIT IS INITIAL.                                                                  
       42     PERFORM NEW_DOCUMENT_NUMBER USING IDOC_NUMBER                                           
       43                                       IDOC_CONTRL-MESTYP.                                   
       44                                                                               
    45 *Füllen der Segmentdaten                                                                    
       46     CHECK EXIT IS INITIAL.                                                                  
       47     CLEAR IDOC_SEGMENT. REFRESH IDOC_SEGMENT.                                               
       48                                                                               
    49     LOOP AT IDOC_DATA WHERE DOCNUM EQ IDOC_NUMBER.                                          
       50       IDOC_SEGMENT = IDOC_DATA.                                                             
       51       APPEND IDOC_SEGMENT.                                                                  
       52     ENDLOOP.                                                                               
    53                                                                               
    54 *Name des zu rufenden Funktionsbausteines ermitteln                                         
       55     ROL_FUNCNAME = 'G_G_IDOC_REC_$'.                                                        
       56     PERFORM BUILD_ROL_FUNCNAME USING IDOC_NUMBER ROL_FUNCNAME.                              
       57                                                                               
    58 *Funktionsbaustein zum Empfangen des IDOC's aufrufen                                        
       59 *Wenn Sender 4.0 System -> Nimm' TAB30, sonst altes TAB                                     
       60     IF NOT E1GLTTF-TAB30 IS INITIAL.                                                        
       61       L_TAB30 = E1GLTTF-TAB30.                                                              
       62     ELSE.                                                                               
    63       L_TAB30 = E1GLTTF-TAB.                                                                
       64     ENDIF.                                                                               
    >>>>>     CALL FUNCTION ROL_FUNCNAME                                                              
       66          EXPORTING                                                                          
       67               MESTYP             = IDOC_CONTRL-MESTYP                                       
       68               DOCNUM             = IDOC_NUMBER                                              
       69               TAB                = L_TAB30                                                  
       70          TABLES                                                                               
    71               IDOC_SEGMENT       = IDOC_SEGMENT                                             
       72               IDOC_STATUS        = IDOC_STATUS                                              
       73               RETURN_VARIABLES   = RETURN_VARIABLES.                                        
       74                                                                               
    75   ENDLOOP.                                                                               
    76                                                                               
    77 *Keine IDOC's empfangen                                                                     
       78   IF SY-SUBRC NE 0.                                                                         
       79     RAISE WF_ERROR_PROCESS.                                                                 
       80   ELSE.                                                                               
    81 *Prüfen, ob Fehler bei der Verarbeitung der IDOCs aufgetreten sind                          
       82     LOOP AT IDOC_STATUS WHERE MSGTY = 'A'                                                   
       83                            OR MSGTY = 'E'.                                                  
       84       EXIT.                                                                               
    Contents of system fields                                                                         
    Name     Val.                                                                               
    SY-SUBRC 0                                                                               
    SY-INDEX 0                                                                               
    SY-TABIX 2                                                                               
    SY-DBCNT 1                                                                               
    SY-FDPOS 0                                                                               
    SY-LSIND 0                                                                               
    SY-PAGNO 0                                                                               
    SY-LINNO 1                                                                               
    SY-COLNO 1                                                                               
    SY-PFKEY                                                                           &

    I think that the FM is a customized one. Correct me if I am wrong. It is quite possible that certain FM's might have been missed out while the new system is built. Here I am assuming that the you are doing an upgrade.
    If whatever, I've mentioned above is correct, you can copy the FM and its other components from the old system into the new one, to rectify the error

  • Function module "GM_DOCUMENT_REVERSE" not found.  after Patch Update

    Hi Abapers/Basis
    After patch update i am not able to do FBCJ reversal entry getting below error message.
    Runtime Errors         CALL_FUNCTION_NOT_FOUND
    Exception              CX_SY_DYN_CALL_ILLEGAL_FUNC
    Date and Time          25.05.2011 14:43:26
    Short text
         Function module "GM_DOCUMENT_REVERSE" not found.
    What happened?
         The function module "GM_DOCUMENT_REVERSE" is called,
         but cannot be found in the library.
         Error in the ABAP Application Program
         The current ABAP program "SAPLRWCL" 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.
         Using Transaction ST22 for ABAP Dump Analysis, you can look
         at and manage termination messages, and you can also
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
         not caught in
        procedure "CALL_DISPATCHER_STORNO_R" "(FORM)", 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:
        The program "SAPLRWCL" contains the CALL FUNCTION statement.
        The name of the function module to be called is "GM_DOCUMENT_REVERSE".
        No function module exists with the name "GM_DOCUMENT_REVERSE".
        All function modules are listed in the Function Library (SE37).
        Possible reasons:
        a) Wrong name specified. Pay particular attention to
           upper/lower case and underscores ("_").
           or
        b) Transport error
        c) In the case of an enqueue/dequeue module,
           the lock object may not have been activated
           (ABAP/4 Dictionary).
    How to correct the error
        Check the last transports to the SAP System.
        Is the program "SAPLRWCL" currently being changed?
        If an enqueue/dequeue module is involved, is the activation
        of the lock object missing in the ABAP/4 Dictionary?
        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:
        "CALL_FUNCTION_NOT_FOUND" "CX_SY_DYN_CALL_ILLEGAL_FUNC"
        "SAPLRWCL" or "LRWCLF10"
        "CALL_DISPATCHER_STORNO_R"
        Function modules with names similar to "GM_DOCUMENT_REVERSE":
        GM_DOCUMENT_CLOSE
        GM_DOCUMENT_RECORD
        GM_DOCUMENT_DELETE
        GM_DOCUMENT_POST
        GM_DOCUMENT_CHECK
        G_DOCUMENT_RECORD
        GJ_DOCUMENT_RECORD
        GM_DOCUMENT_PROJECT
        GET_DOCUMENTS
        GM_DOCUMENT_DISPLAY
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
    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".
    Moderator message: please don't just dump your dumps, search for SAP notes or open a call with SAP instead.
    Edited by: Thomas Zloch on May 25, 2011 2:16 PM

    Hi Karthik,
    Thank you for ur reply.
    I did not implement any user exit/ badi. Dump is saying that my smarform function module does not exist in the se37 library.
    I have excuted my form through se38, that time is working fine. When i tried through output type it is going to dump.
    Regards,
    Kusuma.

  • Compilation error - FPGA NI PXI-7951R board - ERROR: Xst: 2472 - Top module Puma15Top was not found.

    I'm trying to compile a "user CLIP socket" for the NI PXI board - 7951R which has a Virtex-5 LX30 FPGA from Xilinx, but I got the bellow message from NI Compiler, this message is in error report Xilinx.log.
    It says that module Puma15Top was not found.
    But this module is a NI property and is automatically compiled by NI Compiler.
    The compiler automatically generates these files (Puma15Top...) that are passed to the compiler of Xilinx. The Puma15Top files are in the path, i.e: C: \ NIFPGA \ compilation \ Told_F_I_CC5DC260 \ source_files.
    This folder name is automatically generated by labview (Told_F_I_CC5DC260) for each different project or compilation.
    So I have no way to configure in CLIP files where it'll be Puma15Top, once the path is automatically generated during compilation by Labview.
    Does anyone have any idea how to solve this problem? Or have you experienced some like this?
    Following error log:
    ### XstSynthesis ###
    Puma15Top
    Reading design: Puma15Top.prj
    =========================================================================
    *                          HDL Compilation                              *
    =========================================================================
    Compiling vhdl file "C:/NIFPGA/jobs/Cm9xA8x_LaF6U1d/CLUC001_Conf.vhd" in Library work.
    Entity <CLUC001_Conf> compiled.
    Entity <CLUC001_Conf> (Architecture <behavioral>) compiled.
    Compiling vhdl file "C:/NIFPGA/jobs/Cm9xA8x_LaF6U1d/CLUC001_CLIP.vhd" in Library work.
    Entity <CLUC001_CLIP> compiled.
    Entity <CLUC001_CLIP> (Architecture <rtl>) compiled.
    Entity <CLUC001_CLIP> (Architecture <behavioral>) compiled.
    ERROR:Xst:2472 - Top module <Puma15Top> was not found.
    ERROR:Xst:2469 - Please specify the correct library via the -work_lib switch.
    -->
    Total memory usage is 149596 kilobytes
    Number of errors   :    2 (   0 filtered)
    Number of warnings :    0 (   0 filtered)
    Number of infos    :    0 (   0 filtered)
    Process "Synthesis" failed
    Thanks in advanced!

    Hi Guilherme,
    Thanks your suggestion, I upgraded NI-RIO to 13.1.1 version but the problem persists, as shown below:
    Project: T_old.lvproj
    Target: F (RIO0, PXI-7951R)
    Build Specification: I_2
    Top level VI: I.vi
    Compiling on local compile server
    Compilation Tool: Xilinx 11.5
    Start Time: 2/9/2014 18:03:51
    Run when loaded to Fpga: FALSE
    JobId: z8Cq8B4
    Working Directory: C:\NIFPGA\compilation\Told_F_I2_F3177096
    Compilation failed due to a Xilinx error.
    Details:
    ERROR:Xst:2472 - Top module <Puma15Top> was not found.
    ERROR:Xst:2469 - Please specify the correct library via the -work_lib switch.
    -->
    Total memory usage is 149596 kilobytes
    Number of errors   :    2 (   0 filtered)
    Number of warnings :    0 (   0 filtered)
    Number of infos    :    0 (   0 filtered)
    Process "Synthesis" failed
    Start Time: 18:03:51
    End Time: 18:05:19
    Total Time: 00:01:27,414
     Best,
    JEMP

  • "Module not found" in Apple Mail

    Hi all,
    Many times when I edit a new message in Apple Mail, images do not appear after I drag them to the new email. Instead, a sentence appears. My System is in Spanish language and I haven't had the chance to see it in English but it is something like "Module not found".
    This message, instead of attached images, appears randomly so it's very difficult for me to say why is this happening. It happens in some emails I receive so I have to ask them to send them over again. In some emails received with this problem, the images appear time after if I check them back again.
    I deleted and added again my email accounts, but this didn't help. I use MobileMe and Gmail.
    If someone in this forum can help me or has got a clue about this, is very frustrating as I'm a graphic designer and there are attached images in almost every email I send or receive.
    Thanks a lot!

    Hola Carola! 
    That's what I'm talking about! I work as a Graphic Designer and it's quite absurd how I can not appreciate the images my clients send me to show changes or reviews inside the email's body.. it's not just sending but reading the images the issue remains.
    You like me (as many) don´t have enought time to reset or re-install the entire operative system (where the Apple mail is packaged) to fix such a basic problem.
    Apple had closed other discussions like this one with no response.
    -La verdad no entiendo que exista este detalle tan básico para un ordenador hecho para el sector creativo-
    Estoy creando un hashtag en twitter #modulenotfound a ver si consigo algo por ahi.. Saludos desde Madrid

  • Warning: /lib/modules/3.14.17-1-lts/modules.devname not found

    I am trying to use linux-lts but get this error, I'm using rEFInd. I am able to boot the standard arch kernel, but when selecting the other entry in refind I just get the error.
    Warning: /lib/modules/3.14.17-1-lts/modules.devname not found - ignoring
    The file does exist though.

    I sorted it, though not exactly as I want it. I had to change the initrd line in /boot/refind_linux.conf to be initramfs-linux-lts.img, I had previously copied the boot line and created a new one with that initrd line, but that didn't work. As I have things now I can only boot the lts kernel, if I want to change to the other I need to manually change that line before rebooting.

  • Error: "FATAL: Module oracleasm not found" in Red Hat 6

    Hi all:
       OS.....: Red Hat 6.5 (64 bits)
       I am preparing to install an 12c RAC in a Red Hat 6.5. While configuring the ASMLib, i got the following error while executing "/usr/sbin/oracleasm init":
          May  2 18:23:20 oraprd01 modprobe: FATAL: Module oracleasm not found.
       I configure the Oracle YUM Repository and installed the "kmod-oracleasm" package. And in the link (Oracle ASMLib Downloads for Red Hat Enterprise Linux Server 6) i got the "oracleasmlib" and "oracleasm-support" packages, as you can see below:
          [root@oraprd01 binarios]# rpm -qa | grep -i oracleasm
          kmod-oracleasm-2.0.8-4.el6_6.x86_64
          oracleasm-support-2.1.8-1.el6.x86_64
          oracleasmlib-2.0.4-1.el6.x86_64
       My kernel is:
          Linux oraprd01 2.6.32-431.el6.x86_64 #1 SMP Sun Nov 10 22:19:54 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
       My Red Hat version is:
          [root@oraprd01 binarios]# cat /etc/redhat-release
          Red Hat Enterprise Linux Server release 6.5 (Santiago)
       Why am i getting the above error while trying to init the oracleasm module? What am i doing wrong?
       Thanks in advance.

    Problem solved.
       I installed an older version of the kmod-oracleasm (kmod-oracleasm-2.0.6.rh1-3.el6_5.x86_64) downloaded from Red-Hat Customer Portal. Now the ASM module is loaded.

  • Error Function module " " not found in Smartforms

    Hi all,
    Please help me out….
    I created the form using the smartforms, check it and activated it. I can see the unique function module is assigned to the form. I wrote the ABAP program and use function module ‘SSF_FUNCTION_MODULE_NAME’and also define data types.
    when I called the function module fm_name for passing values and tables from program to smartform. This is working perfectly in development server but in production it giving error like Function module " " not found.
    Below I m pasting my code.
    *& Report  ZCASHJOURNAL                                                *
    REPORT  zcashjournal                            .
    TABLES: bseg.
    DATA: FM_NAME TYPE rs38l_fnam.
    DATA:BEGIN OF it_bseg OCCURS 0.
            INCLUDE STRUCTURE bseg.
    DATA:END OF it_bseg.
    DATA:BEGIN OF it_bseg1 OCCURS 0.
            INCLUDE STRUCTURE bseg.
    DATA:END OF it_bseg1.
    DATA: gv_amt_in_words TYPE spell,
          gv_word TYPE spell-word,
          gv_decword TYPE spell-decword.
    DATA:BEGIN OF gt_bkpf OCCURS 0.
            INCLUDE STRUCTURE bkpf.
    DATA:END OF gt_bkpf.
    DATA:bktxt TYPE bktxt.
    DATA:waers TYPE waers.
    DATA:belnr TYPE belnr_d.
    DATA:werks TYPE bukrs.
    DATA:desc  TYPE butxt.
    DATA:awkey TYPE awkey.
    DATA:docno TYPE matnr.
    DATA:cajo  TYPE awkey.
    DATA:desc1 TYPE butxt.
    DATA:dmbtr TYPE dmbtr.
    SELECTION-SCREEN BEGIN OF BLOCK b2.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT (15) FOR FIELD s_belnr.
    SELECTION-SCREEN POSITION 28 .
      PARAMETERS : s_belnr TYPE bseg-belnr .
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
      SELECTION-SCREEN COMMENT (15) FOR FIELD s_werks.
        SELECTION-SCREEN POSITION 28 .
          PARAMETERS: s_werks TYPE werks.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN END OF BLOCK b2.
    SELECT * FROM bkpf
               INTO CORRESPONDING FIELDS OF TABLE gt_bkpf
              WHERE belnr LIKE s_belnr
              AND   bukrs LIKE s_werks.
    IF NOT gt_bkpf[] IS INITIAL.
      SELECT * FROM bseg
          INTO CORRESPONDING FIELDS OF TABLE it_bseg
          FOR ALL ENTRIES IN gt_bkpf
          WHERE bukrs EQ gt_bkpf-bukrs
          AND   belnr EQ gt_bkpf-belnr
          AND   shkzg EQ 'S'.
    ENDIF.
    LOOP AT gt_bkpf.
      bktxt = gt_bkpf-bktxt.
      waers = gt_bkpf-waers.
      belnr = gt_bkpf-belnr.
      werks = gt_bkpf-bukrs.
      awkey = gt_bkpf-awkey.
      docno = awkey+0(10).
      cajo = awkey+10(4).
    ENDLOOP.
    LOOP AT it_bseg.
      dmbtr = it_bseg-dmbtr.
    ENDLOOP.
    IF s_werks EQ '65'.
      desc = 'JCBML - Heavy Equipments'.
    ENDIF.
    IF cajo EQ '0001'.
      desc1 = 'PETTY CASH PLANT II'.
    ENDIF.
    CALL FUNCTION 'SPELL_AMOUNT'
      EXPORTING
        amount    = dmbtr
        currency  = waers
        filler    = space
        language  = sy-langu
      IMPORTING
        in_words  = gv_amt_in_words
      EXCEPTIONS
        not_found = 1
        too_large = 2
        OTHERS    = 3.
    IF sy-subrc EQ 0.
      MOVE : gv_amt_in_words-word TO gv_word,
             gv_amt_in_words-decword TO gv_decword.
    ENDIF.
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
      EXPORTING
        formname                 = 'ZCASHRECPT'
    IMPORTING
       FM_NAME                  = FM_NAME
    EXCEPTIONS
       NO_FORM                  = 1
       NO_FUNCTION_MODULE       = 2
       OTHERS                   = 3
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    *CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
            EXPORTING  formname           = 'ZCASHRECPT'
                    variant            = ' '
                    direct_call        = ' '
            IMPORTING  fm_name            = lf_fm_name
            EXCEPTIONS no_form            = 1
                       no_function_module = 2.
    *v_vbeln = S_VBELN-low.
    CALL FUNCTION FM_NAME
      EXPORTING
        bktxt            = bktxt
        waers            = waers
        belnr            = belnr
        werks            = werks
        desc             = desc
        docno            = docno
        cajo             = cajo
        desc1            = desc1
        dmbtr            = dmbtr
        gv_word          = gv_word
      TABLES
        T_ZDEB           = it_bseg
      EXCEPTIONS
        formatting_error = 1
        internal_error   = 2
        send_error       = 3
        user_canceled    = 4
        OTHERS           = 5.
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.

    Hi Rakesh,
    Check two things
    1. Program tranpsorted to production without any error in request log.
    2. Smartform tranpsorted to production without any error in request log and without renaming / misspelling it.
    CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
    EXPORTING
    formname = 'ZCASHRECPT'
    IMPORTING
    FM_NAME = FM_NAME
    EXCEPTIONS
    NO_FORM = 1
    NO_FUNCTION_MODULE = 2
    OTHERS = 3
    IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    Also try to uncomment the Message id part and it will show some meaningful message.
    And to check whether actaually fucntion module is generated or not goto smartforms ->Smartform name -> Display -> Environment->Fucntion module name . if this is blank try to retransport smartform.
    Hope that helps.
    Regards
    Kapadia
    ***Assigning points is the way to say thanks in SDN.***

  • Pls help  in WEBDYNPRO  Function Module 'RFC_START_PROGRAM' not found error

    Dear Friends,
    While i am calling one function module in webdynpro the follwing erroe is coming.
    Error:-
    Function Module 'RFC_START_PROGRAM' not found error
    Code:-
    CALL FUNCTION 'ZUPDATE' DESTINATION 'PCNCLNT300'
        EXPORTING
          im_material = item_matnr
          im_vornr    = item_vornr
          im_sheet    = item_sheet
      IMPORTING
          value = ZMESSAGE .

    Hi,
    try declarig variable of type rfc_dest
    data: lv_dest type rfc_dest.
    call....
    destination lv_dest
    offcourse make sure your rfc destination has that name in sm59
    and you have the corect authorizations to your user in the remote system
    Are you btw sure that there is no screen action called inside
    the function module? popup or something? because you cannot
    call functions that have screen interaction like in sapgui
    grtz,
    Koen

Maybe you are looking for