Importing Transport - Dump in WEBAS6.2 mini

[LeonardoAraujo]

I've installed my mini SAP WEBAS 6.2 and set up the transport system.

Now I am trying to import the Example Transport from the ABAP Object book and I am getting a short dump in STMS.

I've copied the files to the COFILES and DATA directories. I've ran dbenv.cmd. I 've executed tp pf=.... addtobuffer...

It all seems fine since I see the transport in STMS. There if I try to import it I get a short dump almost immediately:

Data_length_0

CX_SY_range_out_of_bounds in program SAPLTMSU_ALT (proc FORMAT_TEXT_LINE.

Do you guys have any idea what is going on? I am just importing this as a test since I plan to start importing support packs very soon.

Thanks in advance.

[LeonardoAraujo · Accepted solution]

More details:

If I run in test mode TP TST B20K8A05B BSP it returns the following:

E-TPSETTINGS could not be opened

EXIT

Error in TPSETTINGS: Transdir not set.

... error code 208 meaning:

error in transortprofil (param missing, unknown, ...)

Thanks

Message was edited by: Leonardo Araujo

[Former Member · Accepted solution]

Leonards, check your instance profile, e.g. BSP_D00.pfl in you MiniWAS main directory. What are you parameters in there for your transport system. Also what SP are you currently running? Thanks, Tiest.

[LeonardoAraujo · Accepted solution]

I am running Mini WEBAS so it is SP 24 for both ABAP and Basis.

Here is my BSP_D00.pfl:

SAPSYSTEMNAME = BSP

INSTANCE_NAME = D00

SAPSYSTEM = 00

1. ausschalten alert monitoring

alert/MONI_SEGM_SIZE = 2000000

1. beginn der aenderung (alle Pfade geaendert)

exe/gwrd = .\gwrd.exe

exe/dispwork = .\dispwork.exe

DIR_EXECUTABLE=.

DIR_PROFILE=.

DIR_GLOBAL=.

DIR_INSTANCE=.

DIR_INSTALL=.

DIR_PERF=.

DIR_TRANS=.\trans

DIR_PUT=.\put

DIR_HOME =.

DIR_LOGGING =.

DIR_DATA = .

DIR_AUDIT = .

DIR_LIBRARY =.

DIR_PROTOKOLLS =.

FT_DAT =

FT_LOG =

1. ende der aenderung (alle Pfade geaendert)

#rdisp/TRACE = 3

#rdisp/TRACE_COMPS = All

rdisp/wp_no_dia = 2

rdisp/wp_no_btc = 1

rdisp/wp_no_spo = 0

rdisp/wp_no_vb = 0

rdisp/wp_no_enq = 0

PHYS_MEMSIZE= 64

MiniSystem= 1

abap/buffersize = 50000

enque/table_size= 2000

rspo/local_print/method = 2

rsdb/ntab/entrycount=5000

rsdb/ntab/ftabsize=3000

rsdb/ntab/sntabsize=100

rsdb/ntab/irbdsize=300

rsdb/cua/buffersize = 500

#rsdb/mssql/pn_cache_size= 1000

#rsdb/mssql/tsp_cache_size= 100

rsdb/obj/buffersize= 2048

rsdb/obj/max_objects= 200

rsdb/otr/buffersize_kb = 2048

rsdb/otr/max_objects = 1000

rsts/ccc/cachesize= 1000000

rtbb/buffer_length= 500

rtbb/max_tables= 50

sap/bufdir_entries= 200

zcsa/installed_languages = DE

zcsa/presentation_buffer_area = 350000

zcsa/calendar_area= 300000

zcsa/table_buffer_area= 2000000

zcsa/db_max_buftab= 300

ztta/roll_area = 1000000

ztta/diag_area = 128000

ztta/dynpro_area = 150000

ztta/cua_area= 180000

rdisp/PG_SHM = 100

rdisp/ROLL_SHM = 100

rdisp/autoabaptime=0

rdisp/bufrefmode=sendoff,exeoff

rdisp/elem_per_queue= 50

rdisp/wp_ca_blk_no = 20

rdisp/appc_ca_blk_no = 20

rdisp/max_wprun_time = 300

#rdisp/start_icman = false

icm/server_port_0 = PROT=HTTP,PORT=8080

icm/server_port_1 = PROT=SMTP,PORT=8025

icm/server_port_2 = PROT=HTTPS,PORT=8443

icm/HTTP/server_cache_0/max_entries = 1000

icm/HTTP/server_cache_0/max_name_len = 100

icm/HTTP/server_cache_0/max_ufo_entries = 0

icm/HTTP/server_cache_0/ufo_list = FALSE

icm/HTTP/server_cache_0/memory_size_MB = 0

icm/HTTP/server_cache_0/size_MB = 100

icm/min_threads = 5

icm/max_threads = 10

icm/max_conn = 20

mpi/total_size_MB = 10

alert/MONI_SEGM_SIZE = 2000000

auth/new_buffering = 1

transport/systemtype= CUSTOMER

dbs/ada/schema = SAPBSP

Thanks

[Former Member · Accepted solution]

Leonard, first thing that comes to my mind is OSS Note 481910. In case when the problem is not solved, show me the content of the following files: TP_DOMAIN_BSP.PFL and TPPARAM, located in the your miniwas directory path: MiniWAS\trans\bin. Let me know what you find. Tiest.

Kind regards, Tiest

Message was edited by: Tiest van Gool

[LeonardoAraujo · Accepted solution]

Hi Tiest,

I am trying to import those transports using STMS so I don't think that the oss note applies to me.

Here are the files you asked me:

--> TP_DOMAIN_BSP.PFL:

#TMS:0002:DOMAIN_BSP

#A

#

#----

---

#Caution !

#This file was generated by the Transport Management System.

#Do not change this file using a text editor.

#For further information please see the online documentation of

#transaction STMS.

#If this file was destroyed, it can be regenerated in the TMS.

#To do this, log on to the domain controller (system BSP) and call

#Transaction STMS. In the System Overview, you can distribute the TMS

#configuration. This regenerates the file.

#STMS -> Overview -> Systems -> Extras -> Distribute TMS Configuration

#----

---

#

#

TRANSDIR = .\trans

#

BSP/DBHOST = Alienware

BSP/DBNAME = BSP

BSP/DBTYPE = ada

BSP/NBUFFORM = 1

BSP/TP_VERSION = 281

--> TPPARAM:

BSP/DBHOST = Alienware

BSP/DBNAME = BSP

BSP/IMPDP_BY_EVENT = yes

BSP/R3TRANSPATH = R3trans.exe

BSP/SAPEVTPATH = sapevt.exe

BSP/SYSTEM_PF = C:\MiniWAS\default.pfl

BSP/dbtype = ada

ALLLOG = ALOG$(syear)$(yweek)

SYSLOG = SLOG$(syear)$(yweek).$(system)

TRANSDIR = C:\MiniWAS\trans\

Thanks so far.

Message was edited by: Leonardo Araujo

[LeonardoAraujo · Accepted solution]

I've just tried to redistribute the TMS configuration and it still gives me a dump.

Here are more details:

Debuggin the STMS error, the problem is in program LTMSU_ALTF01, form FORMAT_TEXT_LINE. It short dumps while processing substring in lv_text. This is the value in it:

%%ashost=Alienware,sysnr=,lang=E,client=000,pcs=1,icce=1,cfit=0x20 does not exist.

(ALL TOGETHER)

The OSS note 668068 seems to correct my problem (the dump at least), but it is included in HP 31.

In debugging, I let the system pass the error to see where it would go and the error message I got was the following:

RFC communications error with system/destination %%ashost=Alienware,sysnr=,lang=E,client=000,pcs=1

message no. XT 101

An RFC error occurred in the TMS communication layer.

target system: BSP.DOMAIN_BSP(000)

Function: TMS_TP_IMPORT

Thanks again

Message was edited by: Leonardo Araujo

[LeonardoAraujo · Accepted solution]

Strange... I don't see your answer here, event though I've received it by mail...

Anyway, I've changed the system parameters, re-started SAP and still get dumps. (the same by the way)

Isn't it related to a RFC problem?

Thanks a lot so far.

[Former Member · Accepted solution]

Just a couple of random thoughts.

Do you have a FILE SHARE set on your Miniwas folder called "trans" ? If so set that then try again.

Message was edited by: Craig Cmehil

I meant "sapmnt" for the share name.

[Former Member · Accepted solution]

Leonard, I am investigation your dump today and will come back to ya later. Do ensure, as Craig said, your MiniWAS directory is shared. Check out Craig's weblog on this issue since you have to give the share a specific name in order to be accessible. Tiest.

[LeonardoAraujo · Accepted solution]

I just did it and still doesn't work.

The folder is now shared in the network but it still dumps.

I've restarted SAP.

Everything points to a Transport configuration with BSP and or RFC communication. If I go to STMS alert monitor I have for every dump an "RFC communication failure" there.

It looked like it was looking for the RFC destination BSP.DOMAIN_BSP(000)and it doesn't exist. I only have BSP, SAPOSS, TMSADM@BSP.DOMAIN_BSP, TMSSUP@BSP.DOMAIN_BSP or internal connection Alienware_BSP_00.

;-(

Message was edited by: Leonardo Araujo

[LeonardoAraujo · Accepted solution]

BTW, I mean Windows folder sharing. If you mean something else, please let me know.

Thx!

[Former Member · Accepted solution]

Have you done the standard STMS setup? Does this happen from the command prompt as well?

[LeonardoAraujo · Accepted solution]

I did the procedures described in the MiniWEBAS installation CD (extract 2 files to the WEBAS folder and run a program in SAP)

I don't know if there are more steps to it, but that is all I did.

BTW, the command prompt also gets an error. I've previously copied part of the error log/message.

Thanks

[Former Member · Accepted solution]

Have you upgraded your TP version?

[LeonardoAraujo · Accepted solution]

I've just found out what was wrong:

In the "display TMS Configuration" the communication tab had an invalid entry for RFC address. The system number was blank. After entering 00, it now works.

This was not described anywhere. I am not a Basis guy at all and figuring it out was a bit tough, but fun.

Thanks to you Tiest and Craig. Nice to know I can count on someone.

Cheers!

[Former Member · Accepted solution]

Didn't even think of that and I work in Basis - opps!

[Former Member · Accepted solution]

That is great to hear. Success.