Could not find Function DisplayTimerMsgImgPopup in DLL

I just upgraded to TS 4.2.1 from 3.1.  I created a new sequence, in which, I put a message popup.  When I try to run that step, I get the following error: Could not find Function DisplayTimerMsgImgPopup in DLL (or external module) C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 4.2.1\Components\NI\StepTypes\MsgBox\msgbox.dll.  I used Dependency Walker to examine the DLL in that location and that function does not exist.  It seems that since the message popup is a selectable Insert Step type, that function should be part of the base setup distributed in the installation.  Why does the Message Popup try to use that function if it is not included in the DLL?  Any help would be appreciated.
Thanks,
Tracey

It's there in my 4.2 installation. Perhaps you copied your 3.1 steps to the 4.2 folder? What's the size of the dll and date?

Similar Messages

  • Need help in finding the root cause the error 'Could not find function:'

    Hi fokls,
    In my workflow notification , when I click on the notification to process it , it says ' 'Could not find function:' error.
    I found the this message is coming out from the Fnd_new_messages table from the message_name 'FND_FUNCTION_NOT_FOUND'.
    Here are my questions ...
    1. FND_FUNCTION_NOT_FOUND - Is it a oracle Seeded message ?
    2. If so the error I am getting is a oracle product Bug ?
    And In between , I am getting this error for few transaction only. ( out of 100 , i am getting this error at the rate of 5 per 100 ... or less)
    3 .If its a oracle product bug then , how is 95 out of 100 transaction are succssfully wokring ?
    4. If is a custom bug , how it os not though for some other 95 transaction ?
    5. Can I expect it as Data issue ? If so what kind of data issue.
    Folks , any kind of info will be really , realy helpful for me ... please let me know your inputs for me.
    Thansk to all in advance
    Raghu

    In the error message 'Could not find function:' after colon what function name it is giving.
    'FND_FUNCTION_NOT_FOUND' is a seeded message only.
    As you are saying the error was throwing only for 5% or less notifications, is the error throwing for same kind of notifications? I mean the item type and message are same for these erroneous notifications?
    It can be that some function in particular type of workflow is error-ed out does not exists, when responding to those kind of notifications it might be throwing error.
    Please check that.
    Edited by: sarojak on Nov 12, 2010 6:16 AM

  • RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA'

    Hi, All
    the system is PI 7.0 EHP1 oraclei Win2003 server, I configured SLD but I run RZ70, having error "RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA' ". I know there are lot of tread about this error, but none of themsolve my problem. all JCO, RFC connections and SDL DATA supplier(VA) seem OK. error message in SM21 is "Could not send SLD data"
    detail from SM21
    The system could not send the data that has been collected automatical
    for the System Landscape Directory (SLD). Check whether the gateway
    configured in transaction RZ70 has been started and whether the SLD
    bridge has been registered with this gateway.
    You can use transaction SM59 to check this in the sending system for t
    implemented RFC destinations. The RFC destinations have the standard
    names "SLD_UC" for Unicode sending systems and "SLD_NUC" for non-Unico
    sending systems. If a different RFC destination has been entered in
    RZ70, check this destination instead.
    You can use the Gateway Monitor to check the target gateways. In ABAP
    systems, this monitor is started with transaction SMGW, or you can use
    the external SAP program "gwmon". Check whether the specified gateway
    has an active registration.
    OF COURSE I checked  RFC of  SLD_UC and SMGW
    any different ideas
    Regards
    ABH

    Hi
    Please check the following notes are implemented
    Note 906454                           
    Note 907729
    You may be aware but if you are not --->RZ70 creates the required SLD* RFCs during runtime - therefore if you have defined these RFCs manually first using the same namespace you can get RFC conflicts which result in a failed submission    
    Please also check the user in the RFC is known to both systems and has required authorization to write to SLD
    Generally with SLD you have to install or select a suitable gateway to handle incoming data supply traffic
    Also the gateway you are using has be known to SLD and reflected in RZ70 - i.e these defintions have to be the same
    It is also recommended to delete all references to SLD_* RFCs in data supplier and target SLD
    after a failed submission attempt to allow RZ70 to recreate these consistently once the above has been checked
    Best wishes
    Stuart

  • JCO.SERVER could not find the server function

    Hi,
    I am calling "BAPI_COMPANY_GETDETAIL".thuough the zprogram"ZBAPI_COMPANY_GETDETAIL"
    REPORT ZBAPI_COMPANY_GETDETAIL.
    DATA:BEGIN OF ITAB,
    RCOMP LIKE T880-RCOMP,
    END OF ITAB.
    ITAB-RCOMP = 99999.
    CALL FUNCTION 'BAPI_COMPANY_GETDETAIL'
    EXPORTING
    COMPANYID = ITAB.
    IMPORTING
    COMPANY_DETAIL =
    RETURN =
    The Details I Gave......
    In SM59 of R/3:
    PROGRAMID:LCRSAPRFC_PIT
    GATEWAYHOST:PITEST
    GATEWAYSERVICE:sapgw01
    Tested the connection and it is running
    ID:
    In Communication Channel.
    Application server (Gateway):PITEST
    Application server Service (Gateway):
    PROGRAMID:LCRSAPRFC_PIT
    RFC Metadata Repository parameter.
    ip of XI Server
    System No Xi System NO
    username
    pwd
    In SM58 I find the Following error.
    "JCO.SERVER could not find the server function BAPI_COMPANY_GETDETAIL.
    I Tested RFC ADAPTOR in  RWG and it is ok.
    I do not Understand where the problem is.
    Please clarify.
    Thanks,
    Srinivasa

    Thanks for the reply,
    Yes RFC is in the Sender  side.
    I am calling "BAPI_COMPANY_GETDETAIL".thuough the zprogram"ZBAPI_COMPANY_GETDETAIL"
    REPORT ZBAPI_COMPANY_GETDETAIL.
    DATA:BEGIN OF ITAB,
    RCOMP LIKE T880-RCOMP,
    END OF ITAB.
    ITAB-RCOMP = 99999.
    CALL FUNCTION 'BAPI_COMPANY_GETDETAIL'
    EXPORTING
    COMPANYID = ITAB.
    IMPORTING
    COMPANY_DETAIL =
    RETURN =
    The Details I Gave......
    In SM59 of R/3:
    PROGRAMID:LCRSAPRFC_PIT
    GATEWAYHOST:PITEST(XI system name)
    GATEWAYSERVICE:sapgw01
    Tested the connection and it is running
    ID:
    In Communication Channel.
    Application server (Gateway):PITEST(XI system name)
    Application server Service (Gateway):
    PROGRAMID:LCRSAPRFC_PIT
    RFC Metadata Repository parameter.
    ip of XI Server
    System No Xi System NO
    username
    pwd
    In SM58 I find the Following error.
    "JCO.SERVER could not find the server function BAPI_COMPANY_GETDETAIL.
    I Tested RFC ADAPTOR in RWG and it is ok.
    I do not Understand where the problem is.
    These is what I gave,

  • JCO.Server could not find server function 'CONTROL_RECIPE_AVAILABLE'

    Hi Experts,
    I've been trying to read some of the topics in the forums to find answers about the error JCO.Server could not find server function but still haven't resolve the issue.
    Basically, the scenario is from SAP r/3 to PI 7.1 ehp1 (process integration) system.
    All of the aforementioned steps we're done.
    R/3 (SAP) end
    1.) Create RFC destination (T)
    2. ) Indicate the program ID
    3.) Indicate the server/hostname
    4.) Indicate the sap gateway
    Test connection was made and it was successful.
    SAP PI end.
    Integration Directory (Let me skip from the basics and state directly the setup of my senderRFC)
    1.) RFC Comm Channel (set as Sender)
    2.) Indicated the server hostname (sending system), sap gateway and Program ID (basically what was indicated in RFC setup in SAP end)
    3.) RFC Metadata Repository Parameters (In here I used the details of PI environment)..Created user with SAP_ALL profile..I used system without Load Balancing (Parameter, AppServer, SysNo, Logon User, Logon Password, Language and Client)
    I was able to test a message from SAP end but still "JCO.Server could not find server function" was the result upon checking sm58.
    Did I miss something from my setup and config?

    Hi Michal,
    I guess there's a big difference with RFC Server Parameters and with RFC Metadata Repository Parameters.
    Note: Im using PI 7.1 ehp1
    For RFC Server Parameters it includes:
    - Application Server (gateway)*
    - Application Server Service (gateway)*
    - Program ID*
    For RFC Metadata Repository Parameters it includes:
    - Load Balancing or no Load Balancing (choices)..in here my choice is no Load Balancing
    - Application Server*
    - System No*
    - Logon Language*
    - Logon Client*
    - Authentication Mode (Use Log-on Data for SAP System or Secure Network Connection for RFC)
    if Use Log-on Data for SAP System it includes:
    - Logon User*
    - Logon Password*
    If Secure Network Connection for RFC it includes:
    - Quality of Protection
    - SNC Partner Name
    Looked onto your blogs mentioned several times, but no information on RFC Metadata Repository Parameters.

  • Help~~~Could not find Agent_OnLoad function in the agent library

    $ java -agentpath: /home/work/libtest.so SimpleTest
    Error occurred during initialization of VM
    Could not find Agent_OnLoad function in the agent library:
    I'm very sure libtest.so and Agent_OnLoad function are exist.
    thanks
    nowonder

    Yes, this is 32bit version. 64bit looks like this:
    java version "1.5.0_10"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b02)
    Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_10-b02, mixed mode)Bye,
    Tomas Hurka

  • SAP IGS: JCO.Server could not find server function 'PIGFARMDATA'

    dEAR ALL,
    Operating System: aix6.0
    Database: Oracle 11g
    IGS is not getting started.
    SM59--IGS_RFC_DEST--CONNECTION TEST is fine
    sigs-- IGS_RFC_DEST-- Error is generating " JCO.Server could not find server function 'PIGFARMDATA' ".
    Tried starting IGS USING the below command:
    /usr/sap/KBQ/DVEBMGS01/exe/igswd_mt -mode=profile pf=/usr/sap/KBQ/SYS/profile/KBL_DVEBMGS01_<Hostname>
    Startup using profile
    ***LOG Q0I=> NiIBindSocket: bind (67: Address already in use) [nixxi.cpp 3735]
    *** ERROR => NiIBindSocket: SiBind failed for hdl 1/sock 5
        (SI_EPORT_INUSE/67; I4; ST; 0.0.0.0:40180) [nixxi.cpp    3735]
    ***LOG Q0I=> NiIBindSocket: bind (67: Address already in use) [nixxi.cpp 3735]
    *** ERROR => NiIBindSocket: SiBind failed for hdl 2/sock 5
        (SI_EPORT_INUSE/67; I4; ST; 0.0.0.0:40100) [nixxi.cpp    3735]
    ***LOG Q0I=> NiIBindSocket: bind (67: Address already in use) [nixxi.cpp 3735]
    *** ERROR => NiIBindSocket: SiBind failed for hdl 2/sock 5
        (SI_EPORT_INUSE/67; I4; ST; 0.0.0.0:40101) [nixxi.cpp    3735]
    ***LOG Q0I=> NiIBindSocket: bind (67: Address already in use) [nixxi.cpp 3735]
    *** ERROR => NiIBindSocket: SiBind failed for hdl 2/sock 5
        (SI_EPORT_INUSE/67; I4; ST; 0.0.0.0:40102) [nixxi.cpp    3735]
    kbqadm>  sapcontrol -nr 01 -function GetProcessList
    22.07.2014 16:36:48
    GetProcessList
    OK
    name, description, dispstatus, textstatus, starttime, elapsedtime, pid
    msg_server, MessageServer, GREEN, Running, 2014 07 22 16:33:57, 0:02:51, 8847548
    disp+work, Dispatcher, GREEN  Running, Message Server connection ok, Dialog Queue time: 0.00 sec, AS Java: ALL processes running, 2014 07 22 16:33:57, 0:02:51, 12976352
    rslgcoll, Central Syslog Collector, GREEN, Running, 2014 07 22 16:33:58, 0:02:50, 9175214
    rslgsend, Central Syslog Sender, GREEN, Running, 2014 07 22 16:33:58, 0:02:50, 8585278
    DVEBMGS01\exe\ig.sapKBQ_DVEBMGS01, , GRAY, Stopped, , , 13566036
    ps -ef | grep igs--all igs process are running
    HTTP://<HOSTNAME>:40180---sap igs IS RUNNING
    IGS Logs: ( /usr/sap/KBQ/DVEBMGS01/igs/log)
    trace File  pw_sapbwqa_1.trc
    [Portwatcher::Ping] Ping was unsuccessful 3 times
    [Portwatcher::Ping] Reconnect Portwatcher
    Tue Jul 22 16:54:11 2014
    [Portwatcher::Ping] Ping was unsuccessful 1 times
    Tue Jul 22 16:54:41 2014
    [Portwatcher::Ping] Ping was unsuccessful 2 times
    igs vERSION IS Internet Graphics Service 7200.0.7.0
    "mux_sapbwqa.trc---tRACE File
    Tue Jul 22 16:29:13 2014
    *** ERROR => [ListenerRfc::Loop] RfcListenAndDispatch() (IGS.KBQ sapbwqa sapgw01) returned error: RFC_INVALID_HANDLE [listenerrfc_ 1039]
    *** ERROR => [ListenerRfc::OpenRfc] RfcRegisterServer() returned RFC_COMMUNICATION_FAILURE /
    ERROR       partner 'sapbwqa:sapgw01' not reached
    TIME        Tue Jul 22 16:29:13 2014
    RELEASE     720
    COMPONENT   NI (network interface)
    VERSION     40
    RC          -10
    MODULE      nixxi.cpp
    LINE        2896
    DETAIL      NiPConnect: 10.10.90.150:3301
    SYSTEM CALL connect
    ERRNO       79
    ERRNO TEXT  Connection refused
    COUNTER     18
    [listenerrfc_ 948]
    *** ERROR => [ListenerRfc::Loop] OpenRfc() (IGS.KBQ sapbwqa sapgw01) returned RFC_COMMUNICATION_FAILURE
    Still trying... [listenerrfc_ 1007]
    Tue Jul 22 16:30:13 2014
    *** ERROR => [ListenerRfc::Loop] RfcListenAndDispatch() (IGS.KBQ sapbwqa sapgw01) returned error: RFC_INVALID_HANDLE [listenerrfc_ 1039]
    trc file: "mux_sapbwqa.trc", trc level: 1, release: "720"
    Tue Jul 22 16:39:40 2014
    [IgsMux::Initialize] Internet Graphics Service 7200.0.7.1
    [IgsMux::Initialize] Platform: IBM RS/6000 with AIX (rs6000_64)
    [ListenerRfc::ListenerRfc] Constructed for R/3 NA
    [ListenerHttp::ListenerHttp] Constructed for port 40180
    *** ERROR => [ListenerHttp::Loop] NiListen on port 40180 failed [listenerhttp 703]
    [ListenerHttp::~ListenerHttp] Destroyed for port 40180
    [Multiplexer::StartUp]
    *** ERROR => [ServerTcpIp::NiServerLoop] Caught a NetError: [NetError] [NiBufListen failed] [ServerTcpIp::NiServerLoop()] [-4]. [servertcpip_ 254]
    can you please tel the reason why the IGS is not working
    Regards
    gayathri.K

    Hi Gayathri,
    Startup using profile
    ***LOG Q0I=> NiIBindSocket: bind (67: Address already in use) [nixxi.cpp 3735]
    *** ERROR => NiIBindSocket: SiBind failed for hdl 1/sock 5
        (SI_EPORT_INUSE/67; I4; ST; 0.0.0.0:40180) [nixxi.cpp    3735]
    ***LOG Q0I=> NiIBindSocket: bind (67: Address already in use) [nixxi.cpp 3735]
    *** ERROR => NiIBindSocket: SiBind failed for hdl 2/sock 5
        (SI_EPORT_INUSE/67; I4; ST; 0.0.0.0:40100) [nixxi.cpp    3735]
    ***LOG Q0I=> NiIBindSocket: bind (67: Address already in use) [nixxi.cpp 3735]
    *** ERROR => NiIBindSocket: SiBind failed for hdl 2/sock 5
        (SI_EPORT_INUSE/67; I4; ST; 0.0.0.0:40101) [nixxi.cpp    3735]
    ***LOG Q0I=> NiIBindSocket: bind (67: Address already in use) [nixxi.cpp 3735]
    *** ERROR => NiIBindSocket: SiBind failed for hdl 2/sock 5
        (SI_EPORT_INUSE/67; I4; ST; 0.0.0.0:40102) [nixxi.cpp    3735]
    Just check the process which is using the port
    netstat -tupan|grep 40180
    With Regards
    Ashutosh

  • Could not find the entry point in the procedure sqlite3_wal_checkpoint sqlite3.dll dynamic link library., Could not find the entry point in the procedure sqlite3_wal_checkpoint sqlite3.dll dynamic link library.

    Could not find the entry point in the procedure sqlite3_wal_checkpoint sqlite3.dll dynamic link library.

    Could not find the entry point in the procedure sqlite3_wal_checkpoint sqlite3.dll dynamic link library.
    Try uninstalling your MobileMe control panel for Windows.

  • My soundbooth not function withe error code NV_OGL. the stament: "soundbooth could not find any capable playback modules". but pc system is working. Any one can help me?

    Hi, I am SK Chew,My soundbooth is not function after few months not used and with an error code "NV_OGL" and the statement is "soundbooth could not find any capable playback modules". and my pc is working in good condition. any one can help me?

    Quicktime errors http://forums.adobe.com/message/4545437 may help
    Or, not exactly the same, but MAY be related
    ExporterQuickTimeHost QT Version http://forums.adobe.com/thread/1109614

  • Error RFC sender scenario :JCO.Server could not find server function

    Hi ,
    The scenario which am working is as follows:
    I already have a report in R/3 that calls a Bapi which is in CRM system, now I want to make this point-point connection through XI(RFC sender-XI-RFC Reciever) with out changing the report (only changing the RFC destination).
    I have imported the bapi from CRM to XI , changed the rfc destination(to tcp/ip) that existed in R/3 to point to XI(test connection is working fine) and also created the RFC sender adapter .
    Now on executing the report am getting the following error.
    “JCO.Server could not find server function” 
    Please, let me know where I went wrong.
    Should the function module exists on the XI server. If the functional module is not there then I am getting the  error if the function module is there in XI then every thing is working fine.

    Hi Michal ,
    Now my scenario is working . The error <b>"JCO.Server counld not find server function"</b>  got fixed by giving the system details that contain the RFC in the adapter metadata parameters in the channel configuration.
    Thanks & Regards,
    Srikanth.

  • RFC call ended with "Communication Failure" exception (Function call failed; could not find the function

    Hi All,
    I am getting error while executing oDATA service from SAP Netweaver Gateway
    Error details:
    RFC call ended with "Communication Failure" exception (Function call failed; could not find the function
    I am using SAP NG 740
    Project is created in Gateway system using SEGW having Map to Datasource option used.
    in SPRO manage alias, I had seleted Local App option. Screen attached
    I had tried all troubleshooting like delete and add service and alias in "/IWFND_MAINT_SERVICE".
    but still getting same error for all service.
    Kindly advise.
    Regards
    Vivek

    Hello Vivek,
    Service builder would have also generated code for RFC Exception handling to catch exceptions raised when communication fails between your GW and BE for some reasons.
    Handling is done for 1. System Failure 2. Communication Failure & 3. Business Failure;
    Put a BP in your DPC or DP_EXT class where exception code is written to check what exactly is has caused communication failure.
    Check if that RFC is existing in that destination or not.
    For your reference  : Code would be something like this. Put BP here and check the problem.
    * Error and exception handling
    IF lv_subrc <> 0.
    * Execute the RFC exception handling process
       me->/iwbep/if_sb_dpc_comm_services~rfc_exception_handling(
         EXPORTING
           iv_subrc            = lv_subrc
           iv_exp_message_text = lv_exc_msg ).
    ENDIF.
    Go inside this method and check to get info on what has to be done to resolve issue.
    Check carefully what has gone wrong and fix it accordingly.
    No need of adding service & deleting as problem is not because of that.
    Regards,
    Ashwin

  • JCO.Server could not find server function "ZVERIFY_FILE"

    Hi Experts,
    I am facing one problem, i have created on TCP/IP connection with connection type T and given it some Program Id.
    I have register this Program id On SRM server.
    Now from this server i want to call one JAVA file, for that purpose i have installed JCO on the server.
    My server file looks like,
    import com.sap.mw.jco.*;
    //import com.tcs.jns.JSignNS;
    //import com.tcs.jns.JSignNSException;
    //import com.tcs.jns.CertDetails;
    // added by paresh on 16.1.2009
    import java.io.FileOutputStream;
    import com.tcs.jie.jverify.JVerify;
    import com.tcs.jie.jsign.JSign;
    public class ds_listener extends JCO.Server {
    Create an instance of my own server
    @param gwhost (gateway host)
    @param gwserv (gateway service number)
    @param progid (program id)
    @param repository (repository used by the server to lookup the definitions of an inc)
         public ds_listener(String gwhost, String gwserv, String progid, boolean isUnicode,  IRepository repository) {
              super("sapdev14", "sapgw01", "DS_RFC", repository);                this.setProperty("jco.server.unicode", isUnicode?"1":"0");
         /** Overrides the default method. */
         static ds_listener serverConnections[] = new ds_listener[1];
         protected void handleRequest(JCO.Function function) {
              JCO.ParameterList input = function.getImportParameterList();
              JCO.ParameterList output = function.getExportParameterList();
              if (function.getName().equals("ZVERIFY_DATA")) {
                   try{
                        JVerify JNS = new JVerify();
                        String dbPath = "/home/admin/FormSigner_23Apr/FormSigner_Release/certdbs";
                        //boolean res = JNS.init (dbPath); // commented by paresh on 16.1.2009 as its obsolute
                        //initialize method has to be called before calling any other method of the API
                        String recdSignature = input.getString("SIGNATURE");
                        boolean ret_update = JNS.updateSignature(recdSignature.getByetes());
                        if (ret_update){
                             int count = JNS.getSignerCount();
                             boolean ret_verify_sign = false;
                             while(count > 0){
                                  ret_verify_sign = JNS.verifySignature(count - 1);
                                  if (ret_verify_sign){
                                       ret_verify_sign = false;
                                       count = count - 1;                                   
                                  }else
                                       break;
                             if (count == 0){
                                  String decoded_data = new String(JNS.getDecodedData());
                                  output.setValue("X", "STATUS");
                                  output.setValue(decoded_data, "DATA");
                             }else{
                                  output.setValue(" ", "STATUS");
                                  output.setValue("Error in Signature Verification. Please check Certificate Validity of every signer.", "DATA");
                   }catch (Exception e1){
                        output.setValue(" ", "STATUS");
                        output.setValue(e1.getMessage(), "DATA");
              }else if(function.getName().equals("ZVERIFY_FILE")) {
                   try{
                        JVerify JNS = new JVerify();
                        String dbPath = "/home/admin/FormSigner_23Apr/FormSigner_Release/certdbs";
                        //boolean res = JNS.init (dbPath);  // commented by paresh on 16.1.2009 as its obsolute
                        //initialize method has to be called before calling any other method of the API
                        String recdSignature = input.getString("SIGNATURE");
                        boolean ret_update = JNS.updateSignature(recdSignature.getBytes());
                        if (ret_update){
                             int count = JNS.getSignerCount();
                             boolean ret_verify_sign = false;
                             while(count > 0){
                                  ret_verify_sign = JNS.verifySignature(count - 1);
                                  if (ret_verify_sign){
                                       ret_verify_sign = false;
                                       count = count - 1;
                                  }else
                                       break;
                             if (count == 0){
                                  output.setValue("X", "STATUS");
                             }else{
                                  output.setValue(" ", "STATUS");
                   }catch (Exception e1){
                        output.setValue(" ", "STATUS");
              }else{
                   return ;
    Start the server
         public static void startServers() {
              JCO.addClientPool("POOL",3,"200","sisldp","paresh1234","EN","sapdev14","01");
              IRepository repository = JCO.createRepository("REP", "POOL");
              for (int i = 0; i < serverConnections.length; i++) {
                   // Server listens for incoming requests from system 1
                   // (Change gateway host, service, and program ID according to your needs)
                   serverConnections<i> = new ds_listener(
                             "sapdev14",//gateway host, often the same as host
                             "sapgw01", //gateway service, generally sapgw+<SYSNR>
                             "DS_RFC", // corresponds to program ID defined in SM59
                             true, // or false for non unicode listener
                             repository);
                   serverConnections<i>.start();
         public static void main(String[] args) {
         startServers();
    The file have no error as i have compiled it on server, its listener file given in JCO with some modification.
    I have tested the connection from SM59 it's working fine,but when i call my any of the 2  function(ZVERIFY_DATA & ZVERIFY_FILE) defined in my java file then i am getting an error "JCO.Server could not find server function 'ZVERIFY_FILE'" on SRM screen.
    Can anyone tell me what can be the reason????
    please help, i am in real trouble.

    Hi,
    This is may be of  the wrong FunctionModule name means check in case also,it may be case sensitive.
    And check whether it is remotely enabled or not and check the RFC destination.
    For more details refer these threads.
    JCO.Server could not find server function 'SET_SLD_DATA'
    JCO.Server could  not find server function
    Problems with sender RFC
    Thanks.

  • PL/SQL: Could not find program unit being called: mydb.pkg_alert (newbie)

    This is my first attempt at a pretty in debt package. All the procedures and functions work successfully on their own. When i try and put them into a package and run the package, i get these errors?
    ORA-04063: package body "mydb.PKG_ALERT" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "mydb.PKG_ALERT"
    ORA-06512: at line 6
    Here's my package:
    create or replace PACKAGE pkg_alert AS
    FUNCTION fcn_chck_dt(p_date date)
    RETURN VARCHAR2;
    FUNCTION fcn_chck_decline(p_date date)
    RETURN NUMBER;
    PROCEDURE sp_run_alert(p_date date);
    END pkg_monitor;
    Here's my package body code: Your assistance is greatly appreciated:
    create or replace
    PACKAGE BODY PKG_ALERT AS
    FUNCTION fcn_chck_dt(p_date date) return VARCHAR2 is
    --DECLARE
    v_table_name VARCHAR2(35);
         v_string VARCHAR2(1024);
         v_result number;
         v_output VARCHAR2(1024);
    v_date VARCHAR2(100);
    v_dt VARCHAR2(100);
         CURSOR c_table is
              select table_name
              from user_tab_columns
              where COLUMN_NAME = 'date'
              and table_name NOT LIKE '%BIN%';
         BEGIN
    OPEN c_table;
         loop
              FETCH c_table into v_table_name;
              exit when c_table%NOTFOUND;
              v_string:='select decode(to_date(max(date),''yyyymmdd''),'''||p_date||''',1,0)'|| ' from ' || v_table_name;
    execute immediate v_string into v_result;
    v_date:='select max(date)'|| ' from ' || v_table_name;
    execute immediate v_date into v_dt;
    if v_result=0 then
              v_output:=v_output||CRLF||v_table_name||': '||v_dt;
    end if;
    end loop;
    close c_table;
    return v_output;
    END fcn_chck_dt;
    FUNCTION fcn_chck_decline(p_date date) return NUMBER is
    --DECLARE
         v_dt NUMBER;
         v_active NUMBER;
         v_delta NUMBER;
         v_perc_delta NUMBER;
         v_old_s varchar2(1024);
         v_old_dt number;
         v_string varchar2(1024);
         v_result NUMBER;
         CURSOR c_prev IS
              select date,daily_active,
              daily_active-lag(daily_active) over(order by date),
              trunc(((daily_active-lag(daily_active) over(order by date))/daily_active)*100,2)
              from pop_stats
              where to_date(date,'YYYYMMDD') between p_date-1 and p_date
              order by date desc;
    ---bringing back two rows and all records on purpose.
         BEGIN
              OPEN c_prev;
              FETCH c_prev INTO v_dt,v_active,v_delta,v_perc_delta;
         close c_prev;
         v_old_s := 'select max(date) from alert_stats';
         execute immediate v_old_s into v_old_dt;
         if v_dt!=v_old_dt then
         insert into ALERT_stats(date,
                   daily_active,
                   daily_delta,
                   daily_delta_percent)
                        values(v_dt,
                        v_active,
                        v_delta,
                        v_perc_delta);
              end if;
         v_string:='select value from config_tbl where name=''decline''';
         execute immediate v_string into v_result;
         if v_perc_delta <= v_result then
         return v_perc_delta;
              end if;
         END fcn_chck_decline;
    PROCEDURE sp_run_alert(p_date date) IS
    --DECLARE
    v_result varchar2(1024);
    BEGIN
         insert into ALERT_stats(date)
    values(p_date);
    CRLF char(2) := chr(10)||chr(13);
    v_result :='';
    v_result := v_result||fcn_chck_dt(p_date);
    v_result := v_result||fcn_chck_decline(p_date);
    if v_result.length > 0 then
    utl_mail.send('alerts@localhost','[email protected]',NULL,NULL,
    'Alert','Alert Summary: '||v_result,'text/plain; charset=us-ascii',NULL);
    end if;
    END sp_run_alert;
    END PKG_ALERT;

    Take a look at the bolded sections of your code especialy the last line of your package spec
    create or replace PACKAGE pkg_alert AS
    FUNCTION fcn_chck_dt(p_date date)
    RETURN VARCHAR2;
    FUNCTION fcn_chck_decline(p_date date)
    RETURN NUMBER;
    PROCEDURE sp_run_alert(p_date date);
    END pkg_monitor;

  • Setup problem - sql server 2014 - "could not find the database engine startup handle" - 0x851a0019

    I tried to install ,deleted and re-installed several times and no help at all.
    visual studio 2013 with update 2 rc and adk installed in my computer.
    error code: 0x851a0019
    error messege in setup: could not find the database engine startup handle
    edition: Microsoft SQL Server 2014 Enterprise (Evaluation)
    logs:
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2061893607
      Start time:                    2014-04-03 13:53:29
      End time:                      2014-04-03 14:47:48
      Requested action:              Install
    Setup completed with required actions for features.
    Troubleshooting information for those features:
      Next step for RS:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for DQ:              Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for FullText:        Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
    Machine Properties:
      Machine name:                  ARIELUBA-PC
      Machine processor count:       8
      OS version:                    Windows 8
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered  Configured
      SQL Server 2012      SQLEXPRESS           MSSQL11.SQLEXPRESS             Database Engine Services                 1033      
              Express Edition      11.1.3128.0     No         Yes       
      SQL Server 2012      SQLEXPRESS           MSSQL11.SQLEXPRESS             SQL Server Replication                   1033      
              Express Edition      11.1.3128.0     No         Yes       
      SQL Server 2012      ADK                  MSSQL11.ADK                    Database Engine Services            
        1033                 Express Edition      11.0.2100.60    No         Yes       
      SQL Server 2012      ADK                  MSSQL11.ADK                    SQL Server Replication              
        1033                 Express Edition      11.0.2100.60    No         Yes       
      SQL Server 2012                                                          LocalDB        
                             1033                 Express Edition      11.1.3412.0     No         Yes    
    Package properties:
      Description:                   Microsoft SQL Server 2014 
      ProductName:                   SQL Server 2014
      Type:                          RTM
      Version:                       12
      SPLevel:                       0
      Installation location:         C:\Users\Arie Luba\Downloads\WS2012R2DC\SQLServer2014-x64-ENU\x64\setup\
      Installation edition:          Evaluation
    Product Update Status:
      None discovered.
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      true
      AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup
      ASCOLLATION:                   Hebrew_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSERVERMODE:                  MULTIDIMENSIONAL
      ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
      ASSVCPASSWORD:                 <empty>
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            ARIELUBA-PC\Arie Luba
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CLTCTLRNAME:                   
      CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
      CLTSTARTUPTYPE:                Manual
      CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
      CLTSVCPASSWORD:                <empty>
      CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
      COMMFABRICENCRYPTION:          0
      COMMFABRICNETWORKLEVEL:        0
      COMMFABRICPORT:                0
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
      CTLRSTARTUPTYPE:               Manual
      CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
      CTLRSVCPASSWORD:               <empty>
      CTLRUSERS:                     ARIELUBA-PC\Arie Luba
      ENABLERANU:                    false
      ENU:                           true
      ERRORREPORTING:                false
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, MDS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
      FTSVCPASSWORD:                 <empty>
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  true
      INDICATEPROGRESS:              false
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT Service\MsDtsServer120
      ISSVCPASSWORD:                 <empty>
      ISSVCSTARTUPTYPE:              Automatic
      MATRIXCMBRICKCOMMPORT:         0
      MATRIXCMSERVERNAME:            <empty>
      MATRIXNAME:                    <empty>
      NPENABLED:                     0
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      ROLE:                          AllFeatures_WithDefaults
      RSINSTALLMODE:                 DefaultNativeMode
      RSSHPINSTALLMODE:              SharePointFilesOnlyMode
      RSSVCACCOUNT:                  NT Service\ReportServer
      RSSVCPASSWORD:                 <empty>
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         <empty>
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  Hebrew_CI_AS
      SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
      SQLSVCPASSWORD:                <empty>
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           ARIELUBA-PC\Arie Luba
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  false
      TCPENABLED:                    1
      UIMODE:                        Normal
      UpdateEnabled:                 true
      UpdateSource:                  MU
      USEMICROSOFTUPDATE:            false
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
    Detailed results:
      Feature:                       Management Tools - Complete
      Status:                        Passed
      Feature:                       Client Tools Connectivity
      Status:                        Passed
      Feature:                       Client Tools SDK
      Status:                        Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Passed
      Feature:                       Management Tools - Basic
      Status:                        Passed
      Feature:                       Reporting Services - Native
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Data Quality Services
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Full-Text and Semantic Extractions for Search
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x851A0019
      Error description:             Could not find the Database Engine startup handle.
      Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
      Feature:                       Master Data Services
      Status:                        Passed
      Feature:                       Distributed Replay Client
      Status:                        Passed
      Feature:                       Distributed Replay Controller
      Status:                        Passed
      Feature:                       Integration Services
      Status:                        Passed
      Feature:                       Data Quality Client
      Status:                        Passed
      Feature:                       Analysis Services
      Status:                        Passed
      Feature:                       Reporting Services - SharePoint
      Status:                        Passed
      Feature:                       Reporting Services Add-in for SharePoint Products
      Status:                        Passed
      Feature:                       SQL Browser
      Status:                        Passed
      Feature:                       Documentation Components
      Status:                        Passed
      Feature:                       SQL Writer
      Status:                        Passed
      Feature:                       Setup Support Files
      Status:                        Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\SystemConfigurationCheck_Report.htm
    2014-04-03 14:14:28.01 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (X64) 
    Feb 20 2014 20:04:26 
    Copyright (c) Microsoft Corporation
    Enterprise Evaluation Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
    2014-04-03 14:14:28.01 Server      UTC adjustment: 3:00
    2014-04-03 14:14:28.01 Server      (c) Microsoft Corporation.
    2014-04-03 14:14:28.01 Server      All rights reserved.
    2014-04-03 14:14:28.01 Server      Server process ID is 7148.
    2014-04-03 14:14:28.01 Server      System Manufacturer: 'Dell Inc.', System Model: 'Inspiron N5110'.
    2014-04-03 14:14:28.01 Server      Authentication mode is WINDOWS-ONLY.
    2014-04-03 14:14:28.01 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-04-03 14:14:28.01 Server      The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
    2014-04-03 14:14:28.01 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-04-03 14:14:28.01 Server      Command Line Startup Parameters:
    -s "MSSQLSERVER"
    -m "SqlSetup"
    -Q
    -q "Hebrew_CI_AS"
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    -T 8015
    2014-04-03 14:14:28.28 Server      SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message;
    no user action is required.
    2014-04-03 14:14:28.28 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-04-03 14:14:28.28 Server      Detected 8099 MB of RAM. This is an informational message; no user action is required.
    2014-04-03 14:14:28.28 Server      Using conventional memory in the memory manager.
    2014-04-03 14:14:28.31 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2014-04-03 14:14:28.34 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-04-03 14:14:28.36 Server      Query Store settings initialized with enabled = 1, 
    2014-04-03 14:14:28.36 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2014-04-03 14:14:28.36 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
    only. No user action is required.
    2014-04-03 14:14:28.38 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2014-04-03 14:14:28.39 Server      Database Mirroring Transport is disabled in the endpoint configuration.
    2014-04-03 14:14:28.39 spid8s      Warning ******************
    2014-04-03 14:14:28.39 spid8s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-04-03 14:14:28.40 spid8s      Starting up database 'master'.
    2014-04-03 14:14:28.42 Server      Software Usage Metrics is disabled.
    2014-04-03 14:14:28.48 Server      CLR version v4.0.30319 loaded.
    2014-04-03 14:14:28.56 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2014-04-03 14:14:28.62 spid8s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2014-04-03 14:14:28.63 spid8s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2014-04-03 14:14:28.64 spid8s      SQL Trace ID 1 was started by login "sa".
    2014-04-03 14:14:28.64 spid8s      Server name is 'ARIELUBA-PC'. This is an informational message only. No user action is required.
    2014-04-03 14:14:28.65 spid16s     Password policy update was successful.
    2014-04-03 14:14:28.66 spid16s     Error: 17190, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
    2014-04-03 14:14:28.66 spid16s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2014-04-03 14:14:28.66 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
    2014-04-03 14:14:28.66 spid16s     Error: 17182, Severity: 16, State: 1.
    2014-04-03 14:14:28.66 spid16s     TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property. 
    2014-04-03 14:14:28.66 spid16s     Error: 17826, Severity: 18, State: 3.
    2014-04-03 14:14:28.66 spid16s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-04-03 14:14:28.67 spid16s     Error: 17120, Severity: 16, State: 1.
    2014-04-03 14:14:28.67 spid16s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    ________________________________________________________________________________________________

    Is it okay? (see below)
    ;SQL Server 2014 Configuration File
    [OPTIONS]
    ; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter. 
    ACTION="Install"
    ; Detailed help for command line argument ROLE has not been defined yet. 
    ROLE="AllFeatures_WithDefaults"
    ; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system. 
    ENU="True"
    ; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block. 
    UIMODE="Normal"
    ; Setup will not display any user interface. 
    QUIET="False"
    ; Setup will display progress only, without any user interaction. 
    QUIETSIMPLE="False"
    ; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found. 
    UpdateEnabled="True"
    ; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature. 
    ERRORREPORTING="False"
    ; If this parameter is provided, then this computer will use Microsoft Update to check for updates. 
    USEMICROSOFTUPDATE="False"
    ; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature
    will install Management Tools, Books online components, SQL Server Data Tools, and other shared components. 
    FEATURES=SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,RS,RS_SHP,RS_SHPWFE,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,DREPLAY_CTLR,DREPLAY_CLT,MDS
    ; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update
    or a Windows Update service through the Window Server Update Services. 
    UpdateSource="MU"
    ; Displays the command line parameters usage 
    HELP="False"
    ; Specifies that the detailed Setup log should be piped to the console. 
    INDICATEPROGRESS="False"
    ; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system. 
    X86="False"
    ; Specify the root installation directory for shared components.  This directory remains unchanged after shared components are already installed. 
    INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"
    ; Specify the root installation directory for the WOW64 shared components.  This directory remains unchanged after WOW64 shared components are already installed. 
    INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"
    ; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services
    (RS). 
    INSTANCENAME="MSSQLSERVER"
    ; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature. 
    SQMREPORTING="False"
    ; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance. 
    INSTANCEID="MSSQLSERVER"
    ; The computer name that the client communicates with for the Distributed Replay Controller service. 
    CLTCTLRNAME="SQLDRC"
    ; The Windows account(s) used to grant permission to the Distributed Replay Controller service. 
    CTLRUSERS="ARIELUBA-PC\Arie Luba"
    ; The account used by the Distributed Replay Controller service. 
    CTLRSVCACCOUNT="NT Service\SQL Server Distributed Replay Controller"
    ; The startup type for the Distributed Replay Controller service. 
    CTLRSTARTUPTYPE="Manual"
    ; The account used by the Distributed Replay Client service. 
    CLTSVCACCOUNT="NT Service\SQL Server Distributed Replay Client"
    ; The startup type for the Distributed Replay Client service. 
    CLTSTARTUPTYPE="Manual"
    ; The result directory for the Distributed Replay Client service. 
    CLTRESULTDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir"
    ; The working directory for the Distributed Replay Client service. 
    CLTWORKINGDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir"
    ; RSInputSettings_RSInstallMode_Description 
    RSINSTALLMODE="DefaultNativeMode"
    ; RSInputSettings_RSInstallMode_Description 
    RSSHPINSTALLMODE="SharePointFilesOnlyMode"
    ; Specify the installation directory. 
    INSTANCEDIR="C:\Program Files\Microsoft SQL Server"
    ; Agent account name 
    AGTSVCACCOUNT="NT Service\SQLSERVERAGENT"
    ; Auto-start service after installation.  
    AGTSVCSTARTUPTYPE="Manual"
    ; Startup type for Integration Services. 
    ISSVCSTARTUPTYPE="Automatic"
    ; Account for Integration Services: Domain\User or system account. 
    ISSVCACCOUNT="NT Service\MsDtsServer120"
    ; The name of the account that the Analysis Services service runs under. 
    ASSVCACCOUNT="NT Service\MSSQLServerOLAPService"
    ; Controls the service startup type setting after the service has been created. 
    ASSVCSTARTUPTYPE="Automatic"
    ; The collation to be used by Analysis Services. 
    ASCOLLATION="Hebrew_CI_AS"
    ; The location for the Analysis Services data files. 
    ASDATADIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data"
    ; The location for the Analysis Services log files. 
    ASLOGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log"
    ; The location for the Analysis Services backup files. 
    ASBACKUPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup"
    ; The location for the Analysis Services temporary files. 
    ASTEMPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp"
    ; The location for the Analysis Services configuration files. 
    ASCONFIGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config"
    ; Specifies whether or not the MSOLAP provider is allowed to run in process. 
    ASPROVIDERMSOLAP="1"
    ; Specifies the list of administrator accounts that need to be provisioned. 
    ASSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
    ; Specifies the server mode of the Analysis Services instance. Valid values are MULTIDIMENSIONAL and TABULAR. The default value is MULTIDIMENSIONAL. 
    ASSERVERMODE="MULTIDIMENSIONAL"
    ; CM brick TCP communication port 
    COMMFABRICPORT="0"
    ; How matrix will use private networks 
    COMMFABRICNETWORKLEVEL="0"
    ; How inter brick communication will be protected 
    COMMFABRICENCRYPTION="0"
    ; TCP port used by the CM brick 
    MATRIXCMBRICKCOMMPORT="0"
    ; Startup type for the SQL Server service. 
    SQLSVCSTARTUPTYPE="Automatic"
    ; Level to enable FILESTREAM feature at (0, 1, 2 or 3). 
    FILESTREAMLEVEL="0"
    ; Set to "1" to enable RANU for SQL Server Express. 
    ENABLERANU="False"
    ; Specifies a Windows collation or an SQL collation to use for the Database Engine. 
    SQLCOLLATION="Hebrew_CI_AS"
    ; Account for SQL Server service: Domain\User or system account. 
    SQLSVCACCOUNT="NT Service\MSSQLSERVER"
    ; Windows account(s) to provision as SQL Server system administrators. 
    SQLSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
    ; Provision current user as a Database Engine system administrator for %SQL_PRODUCT_SHORT_NAME% Express. 
    ADDCURRENTUSERASSQLADMIN="True"
    ; Specify 0 to disable or 1 to enable the TCP/IP protocol. 
    TCPENABLED="1"
    ; Specify 0 to disable or 1 to enable the Named Pipes protocol. 
    NPENABLED="0"
    ; Startup type for Browser Service. 
    BROWSERSVCSTARTUPTYPE="Automatic"
    ; Specifies which account the report server NT service should execute under.  When omitted or when the value is empty string, the default built-in account for the current operating system.
    ; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
    ; The domain part of RSSVCACCOUNT is a maximum of 254 characters long. 
    RSSVCACCOUNT="NT Service\ReportServer"
    ; Specifies how the startup mode of the report server NT service.  When 
    ; Manual - Service startup is manual mode (default).
    ; Automatic - Service startup is automatic mode.
    ; Disabled - Service is disabled 
    RSSVCSTARTUPTYPE="Automatic"
    ; Add description of input argument FTSVCACCOUNT 
    FTSVCACCOUNT="NT Service\MSSQLFDLauncher"

  • RSPC Variant does not exist - Could not find or load print parameters

    We are on BI 7.0 (support pack SAPKW70017).  We recently freshed test system from production.   After the refresh, we have problems opening all the process chains.  
    1. When I go to RSPC to open a process chain, I get many messages like this:
    Variant &0000000067180 does not exist (there are different variant numbers)
    Message no. DB612
    Diagnosis
    You selected variant &0000000067180 for program RSPROCESS.
    This variant does not exist.
    2. When I go to SM21 to check the system log, it displays many entries like below:
    EJ  F Could not find or load print parameters for step 1, job BI_PROCESS_TRIGGER/09134500
    Documentation for system log message EJ F :                                                                               
    An error occurred during loading of the print parameters for a        
    background job step.                                                  
    The print parameter record may have been deleted even though there was
    a still a step that needed that data. This is an error as the         
    reorganization of the print parameters should prevent this from       
    happening.                                                            
    To fix the problem, edit the step and save it, copy the job, or       
    schedule a new job. The print parameters will be regenerated in all   
    these cases.    
    3. I applied the OSS note 1169659 - Correction: Process variants not entered by BDLS.   The Basis rerun BDLS.  But it did not fix the problem.
    Would appreciate if someone could provide any help.
    Thank you.

    Hi Rebecca.
    1) Please verify if exist process types called 'unknown job'. If exist:  delete process types called 'unknown job' in your process chain. To do that please remove the chain from scheduling (menu bar > process chain > remove from schedule), afterwards switch the detail view on (menu bar >  view) > right mouse click on the process type "unknown job" > displaying scheduled jobs > delete that job. After deletion of the 'unknown jobs' activate and schedule your process chain again.
    2) After the removal of the 'unknown jobs' please check if the error messages with the missing variants pop up when calling your process chain disappears. If not, please implement and execute the attached report Z_FIND_JOBS_WITHOUT_VARIANT which deletes the jobs without variants.
    I have already attached report as Report Z_FIND_JOBS_WITHOUT_VARIANT, you can download and create the report accordingly.
    = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
    REPORT  Z_FIND_JOBS_WITHOUT_VARIANT.
    data: l_t_job type table of tbtcp with header line,
          l_s_varsel    TYPE rsvar,
          l_t_variant   TYPE TABLE OF rsparams.
    parameters: delete type rs_bool.
    select * from tbtcp as job into table l_t_job
                        where progname = 'RSPROCESS'
                        and   exists ( select * from tbtco
                              where jobname = job~jobname
                              and   jobcount = job~jobcount
                              and   status = 'S' ).
    loop at l_t_job.
      l_s_varsel-report  = l_t_job-progname.
      l_s_varsel-variant = l_t_job-variant.
      CALL FUNCTION 'RS_VARIANT_CONTENTS'
        EXPORTING
          report               = l_s_varsel-report
          variant              = l_s_varsel-variant
          execute_direct       = 'X'
        TABLES
          valutab              = l_t_variant
        EXCEPTIONS
          variant_non_existent = 1
          variant_obsolete     = 2
          OTHERS               = 3.
      if sy-subrc <> 0.
        write: / l_t_job-jobname, l_t_job-jobcount.
        if delete = 'X'.
          CALL FUNCTION 'BP_JOB_DELETE'
            EXPORTING
              JOBCOUNT = l_t_job-jobcount
              JOBNAME  = l_t_job-jobname
            EXCEPTIONS
              OTHERS   = 1.
          IF SY-SUBRC <> 0.
            write 'not deleted'.
          else.
            write 'successfully deleted'.
          ENDIF.
        endif.
      endif.
    endloop.
    = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
    I hope I can be helpful.
    Thanks,
    Walter Oliveira.

Maybe you are looking for