Short dump (CALL_FUNCTION_FORMAT_NOT_SUP) when testing RFC connection

Hello!
I'm trying to test a RFC connection through SM59, but I'm getting the following short dump: CALL_FUNCTION_FORMAT_NOT_SUP (RFC data format not supported).
This RFC will connect to Biztalk, and this dump started occurring when Biztalk changed their codepage from 1100 to 4102.
On my SAP system the codepage is set to 1100.
There is no option to set the system as Unicode or non-Unicode on SM59, since I don't have the "Special Options" tab (My release is 4.6C).
How can I make this connection even with the different codepages?
Thanks in advance!

Hello Pedro
This is the PI forum, which is for PI technical issues. This post is not related to PI.
P.S. Please also familiarise yourself with the forum Rules of Engagement - https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement. Please do not Cross post.
Regards
Mark Smyth
XI/PI Moderator

Similar Messages

Error when opening RFC Connection

Hello SAPers,
I have configured PDA in my ECC6.0 --- XI (ABAP+JAVA) Which was successful.
In my Web Dyno Pro Content Administrator
I have performed the JCO Destinations test which was successful
when I go to the URL
http://server:port/webdynpro/dispatcher/sap.com/isisrsrsmenapp/MainApp
entered the store number
In the next menu
Inventory Lookup when I enter the Article number and press Go Button
It is giving me error " Error when opening RFC Connection "
Rest of them working perfectly...
Do I need to do any configuration In Visual Admin?
Could anyone advice
Thanks In Advance
HariKrishna

Thanks it got solved it was an error in RFC, I have changed the RFC now it is working fine
Thanks
Hari

Short dump error when using count(*)

Hi Experts
I am getting a short dump error when selecting the records >= current date - 30 see the coding and comment please correct the coding I want to know the ztable records it is important for command interface.
I have 1402345 records available after deleting the records but as the memory is not enough it is giving short dump error
select count(*) from ZINT_TABLE
select count(*) from ZINT_MSGS
   select * from zint_data
             nto table izint_d2 . "PACKAGE SIZE 20000
   where STATUS = 'OK' AND CREATED_ON >= w_date1.          " VALUE
endselect.**
report z_eslp_command_records.
data: cnt type i.
data: cnt2 type i.
data: cnt3 type i.
data: cnt4 type i.
DATA:
     w_date1 like sy-datum .
DATA:
     w_date2 like sy-datum.
data: izint_msgs type table of zint_msgs.
data: izint_data type table of zint_data.
data: izint_m2 type table of zint_msgs.
data: izint_d2 type table of zint_data.
INITIALIZATION.
w_date1 = sy-datum - 30.
w_date2 = sy-datum - 30.
select * from zint_data
             into table izint_data PACKAGE SIZE 3000
             where STATUS = 'OK' AND CREATED_ON <= w_date1.   " ZERO
endselect.
select * from zint_msgs
             into table izint_msgs PACKAGE SIZE 3000
              where CREATED_ON <= w_date2.              " ZERO
endselect.
select * from zint_data
             into table izint_d2 PACKAGE SIZE 20000
   where STATUS = 'OK' AND CREATED_ON >= w_date1.          " VALUE
endselect.
select * from zint_msgs
             into table izint_m2 PACKAGE SIZE 20000
where CREATED_ON >= w_date2.                            " VALUE
endselect.
select * from zint_data
            into table izint_data2
where STATUS = 'OK' AND CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
ENDSELECT.
select * from zint_msgs
            into table izint_msgs2
where CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
ENDSELECT.
sort izint_data by created_on ascending.
sort izint_msgs by created_on ascending.
sort izint_d2 by created_on ascending.
sort izint_m2 by created_on ascending.
describe table izint_data lines cnt.
describe table izint_msgs lines cnt2.
describe table izint_d2 lines cnt3.
describe table izint_m2 lines cnt4.
write:/ ' Note: THE RECORDS COUNTED SHOULD SHOW ZERO ELSE THE SCRIPT FAILED TO RUN' color 3.
skip.
write:/ '1. Records counted in ZINT_DATA   <=current date - 30                   :' color 2,                        cnt color 4.
write:/ '2. Records available in ZINT_DATA >=current date - 30                   'color 4,                   cnt3 color 4 .
skip.
write:/ '2. Records counted in ZINT_MSGS   <=current date - 30                   :' color 2                 ,                      cnt2 color 4.
write:/ '4. Records available in ZINT_MSGS >=current date - 30                   'color 4 ,            cnt4 color 4 .
TOP-OF-PAGE.
WRITE:/55(60) ' WAGNERS INVESTMENT LIMITED '.
WRITE:/50(40) ' Command Interface Data' CENTERED .
WRITE:/50(40) '----
' CENTERED .
FORMAT INTENSIFIED ON.
SKIP.
"FORMAT COLOR COL_HEADING.
ULINE.
FORMAT COLOR 1.
END-OF-PAGE.

Answer

Short dump error when extracting delta records from R/3

I am working on BW 3.5 and I am facing some short dump error when extracting delta records from the r/3 to BW.
Below is the error message
Kindly do the needful ASAP.
Job started
Step 001 started (program SBIE0001, variant &0000000024277, user ID BWREMOTE)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0ISCM_PAYMENT_01
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 2000000000                              *
abap/heap_area_total.......... 2000000000                              *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... DE                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 6500000                                 *
ztta/roll_extension........... 2000000000                              *
2,454 LUWs confirmed and 2,454 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DAT
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled

Hi,
I look at the transaction ST22 to see which type of error has given you. Take a look at the notes to correct the error.
Another option is to look at OSS notes, because the error is giving you a standard extractor.
Greetings,

Error 'Program not registered' while testing RFC connection PI_RFC

Hi Basis Experts
I am having problems while testing an RFC connection PI_RFC in one of our PI quality system.
Here is the Error log
Logon Connection Error
Error when opening an RFC connection
ERROR: program PI_RFC not registered
LOCATION: SAP-Gateway on host bp1xeuaa202 / sapgw01
DETAIL: TP PI_RFC not registered
Details COMPONENT: SAP-Gateway
COUNTER: 15866
MODULE: gwr3cpic.c
Details RETURN CODE: 679
We tried restarting the JCO-RFC provider service in VA,also tried restarting the Gateway service, tried registering the RFC using below command
rfcexec u2013g PI_RFC -a bp1xeuaa202 -x sapgw01
rfcexec u2013D PI_RFC
the command didnt gave any output also in SMGW tcode we didnt get the entry(PI_RFC) under system type as registered server.
Also we tried changing the Gateway hostname and service name in SM59.
Still we are facing the same issue, can anyone please help us in resolving this issue.
Regards
Syed

Hi,
It seems to like problem with your program is not registered. As suggested by spantaleoni, you can go through.
Here Program Id must be case sensitive. Once again check with your program Id.
And, you have to register your program id in Visual Administrator.
Goto Visual Administrator:
In that Select Cluster>Server>Services-->JCo RFC Provider
Then enter the Program Id and gw host & service.
Hope this helps to you.
Regards,
P.Rajesh

Test RFC connection for Logical port

Hi,
I've created a new Proxy class in my development by consuming the WSDL file and attached it to a package.
Also i have created Logical port based on the WSDL file in SOAMANAGER. But when I test the RFC connection which gets automatically created
I get message u2018Create failed: Argument not foundu2019, If any one has experienced this problem please guide me.
Thanks,
Ganesh

Hi Bhaskar
Kindly refer the SAP Note with RFC error
1906868 - Transaction program not registered error happened during connection test of Java Idoc adapter
1989478 - IDoc_AAE 'Program XI_IDOC_DEFAULT_PID not registered'
Regards
Sriram

Short dump error when extracting from one of the datasource in R/3 to BW

When extracting from one of the datasource I am getting the short dump. below is the source code of the same.
Source code extract
Get boundaries of next TID block
L_FROM_INDEX = L_TO_INDEX + 1.
IF L_FROM_INDEX GT NFILL. EXIT. ENDIF.
L_TO_INDEX   = L_TO_INDEX + L_BLOCK_SIZE.
IF L_TO_INDEX GT NFILL.
L_TO_INDEX = NFILL.
L_BLOCK_SIZE = L_TO_INDEX - L_FROM_INDEX + 1.
ENDIF.
Create hashed index on TID of TID table
CLEAR L_TH_TID_IDX.
LOOP AT TIDTAB FROM L_FROM_INDEX TO L_TO_INDEX.
L_S_TID_IDX-TIDIX = SY-TABIX.
L_S_TID_IDX-TID   = TIDTAB-TID.
COLLECT L_S_TID_IDX INTO L_TH_TID_IDX.
ENDLOOP.
Select TID block from STATE table
SELECT * INTO TABLE L_T_STATE
       FROM ARFCSSTATE FOR ALL ENTRIES IN L_TH_TID_IDX
       WHERE ARFCIPID   EQ L_TH_TID_IDX-TID-ARFCIPID
         AND ARFCPID    EQ L_TH_TID_IDX-TID-ARFCPID
         AND ARFCTIME   EQ L_TH_TID_IDX-TID-ARFCTIME
         AND ARFCTIDCNT EQ L_TH_TID_IDX-TID-ARFCTIDCNT
       ORDER BY PRIMARY KEY.
Consistence check
DESCRIBE TABLE L_T_STATE LINES L_LINES.
IF L_LINES NE L_BLOCK_SIZE OR
   L_LINES EQ 0.
MESSAGE X097(SY).
ENDIF.
PERFORM DELETE_BATCH_JOB
        USING    L_T_STATE
        CHANGING L_S_TID1.
Update LUW-Status und Zeit
CLEAR L_T_STATE_IDX.
CLEAR L_TH_TID2_IDX.
CLEAR L_T_TID.
LOOP AT L_T_STATE INTO L_S_STATE.
L_S_STATE_IDX-TABIX = SY-TABIX.

Hi Pavan,
                 This is a table space error.
Regards,
rahul

Short Dump Error when we check the Data Source in RSA3

Hi. Experts.
                   We are using Data Source 2Lis_13_VDITM and when we try to check in RSA3
for recorts it is going short dump. I am just providing the error information.
              An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
not caught in procedure "MCEX_BW_LO_API" "(FUNCTION)", nor was it propagated by a RAISING
clause.
               Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated.
The reason for the exception is:
When importing the object "MC13VD0ITM_TAB", the component no. 96 in the dataset has a different type from the corresponding component of the target object in the program "SAPLMCEX".
                    The data type is "N" in the dataset, but "X" in the program.
        Since I don't have much knowledge in ABAP, Please help me out regarding this issue. Suggest me possible solution and let me know if you need any further information.

Hi,
Try adding a TRY CATCH block in the extractor function module to catch the exception.
For the type mismatch you will have to make sure the variables are of same type or they can be type converted.
Use the debug mode of RSA3 to find what data is being exchanged.
You will need to change your extractor to avoid the dump.. or ensure that the value being passed to that object is correctly being passed(correct format)
Cheers
Kiran

Short dump OBJECTS_OBJREF_NOT_ASSIGNED when activating infoobjects

Hi Experts,
We are getting a short dump when activating bussiness content infoobject which contain attributes, for e.g. 0COSTCENTER.
We are not getting the same dump when activating infoobjects whith out attributes.
We found a note 1019055 that recomends install sp13 or install six or seven notes for an emergency issue.
The problem is that if we install sp13 we will get out of stack.
What is your recomendation in this case? we are afraid that the problems will continue until we don't implement the sp13.
Thanks!

use t-code SNOTE to implement the OSS note you mentioned ,if it doesnt work you can always revert back to old status by doing Reset.
Hope it Helps
Chetan
@CP..

Get an error when testing the connection

Hi
I'm using the B1i with SBO 2007.
I'm able to create my own system. I filled in everything except under the field "jcoPath". Do we need to fill in the rest???
I get the following error when I test the connection
HTTP Status 404 - com.sap.b1i.xcellerator.RejectedException: XCE045 IPO-Step not known: /0010000102.testconnection/com.sap.b1i.system.sld/ipo/SystemConnection.ipo/testconnection
type Status report
message com.sap.b1i.xcellerator.RejectedException: XCE045 IPO-Step not known: /0010000102.testconnection/com.sap.b1i.system.sld/ipo/SystemConnection.ipo/testconnection
description The requested resource (com.sap.b1i.xcellerator.RejectedException: XCE045 IPO-Step not known: /0010000102.testconnection/com.sap.b1i.system.sld/ipo/SystemConnection.ipo/testconnection) is not available.
Apache Tomcat/5.5.17
Can someone please tell me what the problem is???
Thanks in advance

Hi Ian
Thank you for your response, greatly appreciated. If i go to the path you suggest below I do not have the JCO lobaries there.
Mine is under C:\Program Files\SAP\SAP Business One Server\DI API\JCO\LIB because they have changed the file tructure slightly in SAP 2007.
I agree that this should be added but it is still not working.
Any other ideas???
Thanks in advance

SBO error when testing the connection

Hi all,
I installed PL04 on a W2003 server, and i get the follwong error when a test the connection to SBO subsidiary. I previously install the same configuration on my dev pc without having this kind of error.
Can anybody help ?
Thank you very much.
Fabrice Nanni
com.sap.b1i.xcellerator.XcelleratorException: XCE001 Nested exception: java.lang.Exception: com.sap.b1i.xcellerator.XcelleratorException: XCE001 Nested exception: com.sap.b1i.adapter.dia.ComFailException: com.sap.smb.sbo.wrapper.com.ComFailException: Can't find moniker

Hello Edward,
Yes i did install the JCO connectors for SBO on the B1iserver.
Actually i got the same B1i configuration working on a dev computer (Windows XP) and the connection to SBO is working properly, so i wonder if the problem comes from the O/S server (Windows 2003 server). what do you think ?
Fabrice.

Short dump TSV_TNEW_PAGE_ALLOC_FAILED when import SAPKB70016

Hi all,
I´m trying to import the support package SAPKB70016 im my QAS system and I got an error. The import stop on phase XPRA_EXECUTION and I saw at the tcode sm37 that there is a job running with the name RDDEXECL. This job is canceled with the dump TSV_TNEW_PAGE_ALLOC_FAILED. I already changed some parameters and also I applied some notes but I can´t solve this issue.
Parameter changed                Before                 After
ztta/roll_area                        30000000          100000000
ztta/roll_extension               4000317440        8000000000
abap/heap_area_dia        2000683008        4000683008
abap/heap_area_nondia      2000683008        4000683008
abap/heap_area_total       2000683008        4000683008
em/initial_size_MB                             392                    1024
abap/shared_objects_size_MB      20                     150
es/implementation                           map                     std
JOB LOG:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server FQAS were synchronized
ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
Job cancelled
ST22 LOG:
Memory location: "Session memory"
Row width: 510
Number of rows: 0
Allocated rows: 21
Newly requested rows: 288 (in 9 blocks)
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server FQAS_QAS_01 o
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhau
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1897
The error reported by the operating system is:
Error number..... " "
Error text....... " "
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 99661936
Extended memory (EM)........... 8287273056
Assigned memory (HEAP)......... 1376776176
Short area..................... " "
Paging area.................... 49152
Maximum address space.......... 18446743890583112895
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:
"TSV_TNEW_PAGE_ALLOC_FAILED" " "
"CL_ENH_UTILITIES_XSTRING======CP" or "CL_ENH_UTILITIES_XSTRING======CM008"
"GET_DATA"
Now, I don´t know what I can do to solve this problem.
Can you help me?
Thanks

Hi all,
Gagan, I already changed my parameters according to the above post. I increased this parameters until maximum allowed but the dump still persists.
Bhuban
In this server I have 16GB RAM and 600GB HD.
             total       used       free     shared    buffers     cached
Mem:      16414340    4973040   11441300          0     454436    3572592
-/+ buffers/cache:     946012   15468328
Swap:     20479968          0   20479968
Size Used     Avail Use% Mounted on
441G 201G   218G 48% /oracle
20G     6.5G    12G   36% /sapmnt
25G     21G    2.7G   89% /usr/sap/trans
25G    8.8G   15G    39% /usr
20G    14G    5.1G    73% /
Anil, I already stop my appl and my db, I rebooted my OS too and after i tried again, no success.
What else can i do?
Thanks for all.

Error when testing database connection

Hi,
I've downloaded v 3.0 and when i enter the basic data and test conection, it gives me following error:
nosuchmethoderror oracle.i18n.text.oraboot.getcharsetmaxcharlen (Ljava/lang/string;)Ljava/lang/string;
What can i do?
v2 worked well, but i deleted it...

Try to create a batch file (datamodeler.bat) under Data Modeler installation folder and put the following two lines in it:
set ORACLE_HOME=%CD%
start datamodeler.exe
Then double click on this file to start Data Modeler.
Ivan

A short dump occurs when accessing SAP BI 7.0 using GUI 620

hi,
i'm getting this error while executing..DTP.
solve this .....

Hi,
BI 7.0 will not work with SAP GUI 6.20.
Take a look at this SAP note.
Maintenance strategy / deadlines 'SAP GUI'
SAP Note Number: [147519|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_fes/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d313437353139%7d]
Compatibility - 6.20
SAP GUI for Windows 6.20 is compatible with products based on SAP Web Application Server 6.40/7.00/7.01/7.02 and all earlier releases of SAP Software which are still supported by SAP (this includes extended maintenance).
Exceptions to this rule are
BI 7.0: Requires new frontend components shipped only together with SAP GUI for Windows 6.40 as of compilation 4. For BI 7.0 you definitely need at least this compilation CD. For further information on this please check the master guide for SAP NetWeaver 2004s components and documentation center at
http://service.sap.com/~sapidb/011000358700004970342005E/051024Instguides.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/b2/e50138fede083de10000009b38f8cf/frameset.htm
SCM 5.0: Requires a new frontend component which is integrated into SAP GUI for Windows 6.40 (also see note 889989).
SAP GUI for Windows 6.20 is not compatible with SAP Systems based on SAP Web Application Server 7.10 and higher.
Additional:
Troubleshoot the SAP NetWeaver 2004s BI Frontend Installation
and
Frontend requirements - page 11
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10564d5c-cf00-2a10-7b87-c94e38267742
and
Re: GUI 640
Regards
Andreas

Short Dump while acessing external tables using DB Connect

Hello SDN'rs,
I am getting Short dump (below) when i am trying to look into the table contents using DB Connect.
Please let me know how to resolve this problem. Is there any OSS Note on this??
External Database is Oracle; i can look into other tables.
ShrtText
Syntax error in program "GP_CREATE_STRUCTURE_DBCON_026 "
|What happened?                                                                                |
|    Error in ABAP application program.                                                            |
|                                                                                |
|    The current ABAP program "CL_RS_STRUC===================CP" had to be                         |
|     terminated because one of the                                                                |
|    statements could not be executed.                                                             |
|                                                                                |
|    This is probably due to an error in the ABAP program.                                         |
|                                                                                |
|    In program "GP_CREATE_STRUCTURE_DBCON_026 ", the following syntax error                       |
|     occurred                                                                                |
|    in the Include "GP_CREATE_STRUCTURE_DBCON_026 " in line 5:                                    |
|    "Type "D" can only have the length specification "8" or no length speci"                      |
|    "fication at all."                                                                            |
|    " "                                                                                |
|    " "                                                                                |
|                                                                                |
|    Author and last person to change the Include are:                                             |
|    Author "XYZ "                                                                            |
|    Last changed by "XYZ
|Error analysis                                                                                |
|    In program "GP_CREATE_STRUCTURE_DBCON_026 ", the following syntax error                       |
|     occurred:                                                                                |
|    "Type "D" can only have the length specification "8" or no length speci"                      |
|    "fication at all."                                                                            |
|    " "                                                                                |
|    " "                                                                                |
Trigger Location of Runtime Error                                                                 |
|    Program                                 CL_RS_STRUC===================CP                      |
|    Include                                 CL_RS_STRUC===================CM002                   |
|    Row                                     108                                                   |
|    Module type                             (METHOD)                                              |
|    Module Name                             CREATE
Thanks,
Faizee B

When i tried today for the same table i am getting the shortdump description(below), I have noticed that the number have changed from 026 to 055, any thoughts why it happen and how it can be resolved?
In program "GP_CREATE_STRUCTURE_DBCON_055 ", the following syntax error
occurred in the Include "GP_CREATE_STRUCTURE_DBCON_055 " in line 5:
    "Type "D" can only have the length specification "8" or no length specification at all."
Thanks,
Faizee B

Short dump (CALL_FUNCTION_FORMAT_NOT_SUP) when testing RFC connection

Similar Messages

Maybe you are looking for