Problem importing transport

[Former Member]

Hello All:

I installed the mini WEB AS 6.20 without any errors, I am now trying to import the examples as fallows.

Log on to system BSP as user DDIC. <b>(Done)</b>

Call transaction SE38 and execute program ZR3_TMS_CONFIG. <b>(Done)</b>

Change the profile <BSP_DIR>\BSP_D00.pfl using the editor <BSP_DIR>\sappad.exe: <b> (Done)</b>

Configure one background process by setting the parameter rdisp/wp_no_btc = 1 and restart the BSP system. <b>(Done)</b>

Execute program RDDNEWPP (transaction SE38), which schedules the background job RDDIMPDP within the BSP system. <b>(Done)</b>

Copy K8A0H5B.B20 to <BSP_DIR>\TRANS\COFILES. <b>(Done)</b>

Copy R8A0H5B.B20 to <BSP_DIR>\TRANS\DATA. <b>(Done)</b>

Open a DOS-box, change to <BSP_DIR>, and run dbenv.cmd . <b>(Done)</b>

C:\MiniWAS>tp pf=trans\bin\TP_DOMAIN_BSP.PFL addtobuffer B20K8A0H5B BSP

This is tp version 320.56.75 (release 620)

Addtobuffer successful for B20K8A0H5B

tp finished with return code: 0

meaning:

Everything OK

C:\MiniWAS>tp pf=trans\bin\TP_DOMAIN_BSP.PFL import B20K8A0H5B BSP

This is tp version 320.56.75 (release 620)

<b>Could not open libsapu16.dll [nlsui1.c 3120] pid = 2756

Terminating. [nlsui1.c 3239] pid = 2756</b>

The command prompt stops at this point i used CTRL+C to break it

INFO: Exiting on signal CTRL+C. Further signals will be ignored ....

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0219

tp finished with return code: 219

meaning:

tp got a signal (and terminated?)

Please advise me on how to get past this issue.

Thanks

[Former Member]

I hope I am not too late answering this:

Please check the job log in sm37 with RDDIMPDP as the job name (Dont forget to select the after event tab). I had the same problem and when I checked the failed job logs it clearly showed me that the ddic user was locked in the client the transport had to be imported.

[Former Member]

Hi Craig.

I hope this note finds you properous in the new year.

I have been away for several months due to family issues - weddings and deaths and earning living as a SAP developer.

I am having similar problems as described in the many forums in SDN.

I would like to detail some of my issues and make a recomendation.

I have mini WEBAS 620 024 installed and I am trying to use the system as personal training tool. I am impeded by the fact that most of the menu items are in German. My German is on a par with my Swahili. Yes, I am illiterate in numerous languages!

I upgraded my laptop based on the recommendation I recieved from SAP employees while on a recent assignment. My new system is a 3.7 GHZ Intel with 2 GB of memory. It is as slow as ever.

Enough of the personal problems. Next are my recommendations, also known as my "Dream List".

I would like to see the following and I will confess that I have very little to offer to it. I will be a recipient.

1) Clear and concise instructions on how to upgrade all components of mini WEBAS. (I have used my personal OSS ID to peruse service.sap.com and I can't seem to find the numerous upgrades discussed in the forums.)

2) A good definition on the parameters in BSP_D00.pfl and how they can be adjusted for performance sake.

3) Continued input from knowledable individuals, like yourself, to help people like me maximize the mini basis experience.

4) Continued openess and professionalism in our discussions.

With much respect and personal regards,

Steve

[Former Member]

Hello Craig,

I am in trouble installing the service packs. I patched my system to kernelpatch 1271 (Kernelstack I) as described above and now I encounter the problem that SAPDB cannot handle OR or IN expressions in the where clause of select statements which leads to dumps in the xpas running after installing a service pack.

The problem appaers in the way that SELECT SINGLE * FROM <table> INTO <wa> WHERE <attribute> = <value1> returns a value (sy-subrc is 0) but SELECT SINGLE * FROM <table> INTO <wa> WHERE <attribute> = <value1> OR <attribute> = <value2> does not retur a value and sy-subrc is 4 although the statement should find exactly the same entry like the first one.

Could you please test if the error still exists under kernelpatch 1509 or tell me our workaround if you used on to solve the problem?

Thx.

Roman

[Former Member]

I'm not having that problem but I've since upgraded the SP's and the Kernel again.

I mean you need to do the upgrades to get the newest SP43 in and that's were most of my development is so.

Sorry I can't be of more help.

[Former Member]

So after SP 37 I upgraded the Kernel and then I had to upgrade the SAPDB

Now I am continuing with the SP's I hope to have 38 finished before this message is actually submitted.

[Former Member]

Hello all,

I finally got my tranport system as far that i was able to import the examples.

here is what i did (due to the many steps i am not really sure if all are necessary):

- first i got the failiure that the icu* dlls were missing, so i got some from the web (http://www.dynamiclink.nl/htmfiles/rframes/dll-i.htm). i took the icuuc.dll, the icuin22.dll which i renamed to icuin20.dll and the icudt20.dll which i renamed to icudt20.dll as a sap note said they were equal and put everything to sapdb\programs\bin

- after this i got the libsapu16.dll bug. I found this file on my c drive (i think it was in the gui installation) and put it into System32 which did not help

- i found an error of sapdb 7.3 described under http://www.sapdb.net/7.4/new_relinfo.txt so I made the workaround

- after this the error disappeared but tp still threw another error, which was caused by sapevt.exe which externally triggers events for starting jobs in R/3

- i took sapevt and tried to trigger just the event, when doing this sapevt showed an strange syntax error I could not really understand

- I thought this might have sth. to do with renaming some of the dlls, so I went to one of my sap admins today and got the dlls from one of our installations but this did not change anything

- so i moved the icu files from sapdb\programs\bin into another uncritical directory and talked to one of the admins again who suggested patzching the kernel. so i went to the service marketplace an got the 6.20 32 bit nonunicode dbindependent and the sapdbdependent kernel stacks of q3 2004. decompressed them with sapcar and put everything into the miniwas directory

- when starting the sapserver again i got a little bit nervous as the workprocesses and then the server shut down. the wp log showed that i had to upgrade the db precompiler (see 557227 for details - take the non 64 bit version of course)

After this the server started and i was able to do the transport. It still had an error but the stms showed that this was due to a syntax error in one of saps example programs ;o).

hope that will help you get your systems running.

Roman

[Former Member]

I will try it with the DLL's and if that doesn't work I will patch the Kernel.

[Former Member]

I downloaded the kernel update for the 620 server from the marketplace DB and DB independent - I downloaded all the files (except Kernel I Q1-Q3 and Kernel II Q1-Q3) but the ones for SP 27.

I unpacked everything to a directory then I only copied into my MiniWAS folder the files it already had from the unpack.

The DLL's were also there so I copied those into the sapdb\programs\bin folder.

I restarted and everything worked.

I updated SPAM as well to 16 and I updated my SP from the 24 to 37. I'll download the Kernel for going to SP37 and then update my SP to 43.

[Former Member]

I have managed (after reinstalling again) to get SP 25 - 27 at the moment in.

<i><b>Warning</b></i> do the SP's 1 at a time and not in a big queue - it killed my system the first time trying so I redid everything including the Kernel excedt I and II from Q1-Q3

It's working beautifully!

[Former Member]

SP 29 ABA and BASIS in.

Message was edited by: Craig Cmehil

[Former Member]

Dear Craig

Trying to make my transport sys. up and running, but no luck so far.

I followd all you recomendation and installed kernel patch of Q3 (1509) along with database precompiler patch. The system is workin nicely but with tp I've got the message "ERROR: Background job RDDIMPDP could not be started or terminated abnormally."

I didn't try to install any SP yet. (So I'am at SP24 now).

Any suggestions? May be I need another kernel patch?

Sergey.

[Former Member]

You've got the same problem described here:

I would recommend you schedule the job yourself to run every minute and you should be able to continue.

[Former Member]

Sergey, same question here as in the thread Craig mentions. How did you schedule the background job? Also check out OSS note 739968. Tiest.

[Former Member]

Thanks a lot for your help.

I scheduled job to run every minute and it looks like that it worked to some extent. The tp finished with code 08, but I understand that this is due to some error in ABAP book. The most strange thing that in Object Navigator only some Data Dictionary objects are shown in package 'S_ABAP_BOOK'. Most of the objects in request are not shown! Although they do exist and could be found separately and clearly belong to S_ABAP_BOOK package!

I have to mention that even before installing any patches I tried to import the request through STMS. Only those Data Dictionary elements came in.

Do you know how to correct the problem?

Sergey.

[Former Member]

When TP finishes with Error Code 8 then that means there are problems in the transport and because of those problems you won'T get everything so therefore nope no way to fix that unless you fix the transport which you would have to ask SAP do basically since it came from them.

[Former Member]

STMS shows that request came in OK. All objects in. My problems had to do with indexing. I run the job EU_INIT which updates indexing and 'where used' list and now everything looks good. All book is there.

I also notice that some menu texts are mix of English and German. Will this change with SPs?

[Former Member]

Wait are you talking about the ABAP Objects import? Sorry about that.

Ok we you found the answer anyway.

SP's typically only effect system objects those from external/3rd party imports typically not.

[Former Member]

No, this time I am talking about the whole mini WAS 6.20 interface. I log in with EN, but some texts (in menu and standard reports)are German ! It is not very convinient to say the least.

[Former Member]

Then yes that can change with SP's

[Former Member]

Now new problems. SP's 25a, 25b went in OK, but on 26b (the biggest one) I'v got the dump on AUTO_MOD_SPAU stage. Any advice here?

Thanks. Sergey.

[Former Member]

Just restart again. Happens sometimes.

[Former Member]

Thank you once again. I downloaded up to SP 27 and I wonder if I need to install kernel patch (1027) now, or after SP 28. You mentioned SP 27, but on Marketplace kernel patch described as: "Kernel ... for Upgrade w/ BASIS SP29." I also wonder if you experienced the same problems with mix of English and German texts in menus, or this is my specific problem.

Sergey.

[Former Member]

Same problems, yes.

I would recommend just jumping to the latest Kernel and TP to save time - shouldn't be a problem.

[Former Member]

Sorry for bothering you, but new problems.

I successfully installed SP's up to 34. Everything looked nice, but then I reload the system with "Start SAP" it started very badly. Some processes are diying out end more important I have "disp+work.exe encountered a problem and need to close". It happened before, but only once in a while. Now every time. Any suggestions?

[Former Member]

Sergey, two thinks 1) have you modified your profile as mentioned in Craig's weblog? 2) Can you add the lines of the command prompt in here so we can have a look at the actual error? Tiest

[Former Member]

Could be simply that you are Kernel is at xxxx level in which case you may have to continue your SP update.

With the MiniSAP I recommend you just pop in the latest Kernel and SP level (which is 48)

[Former Member]

Yes, the first thing I've done was ajusting profile acording to Craig's advice.

The example of the lines in command prompt as follows:

C:\MiniWAS>rem del pxastat

C:\MiniWAS>start /B msg_server.exe pf=BSP_D00.pfl

C:\MiniWAS>disp+work.exe break pf=BSP_D00.pfl

dp Ctrl-C enabled

rslgwr1(21): Searching for overlap point in pre-existing SysLog file...

gw Ctrl-C enabled

dp Ctrl-C enabled

dp Ctrl-C enabled

dp Ctrl-C enabled

dp Ctrl-C enabled

dp Ctrl-C enabled

dp Ctrl-C enabled

dp Ctrl-C enabled

IcmHandleArgs: Illegal option break

• ICM up and operational (pid: 2244) ***

***

• work process W2 died => ThSigHandler: signal

***

• work process W0 died => ThSigHandler: signal

***

• work process W1 died => ThSigHandler: signal

^CTerminate batch job (Y/N)? ..Shutdown ICM server ..

• ICM shutdown completed (pid: 2244) ***

After that the Windows information box about disp+work.exe expirienced a problem and need to close.

But every new start differs from one before. Sometimes work processes dies before ICM up. End every time new work processes.

Sergey.

[Former Member]

Is your license still valid?

what do the dev logs show?

[Former Member]

Very strange behavior indeed. I notice that if I ^C the start process immediate after "ICM up and operational" i.e. before any processes starting to die, the next start is OK. I think it is looking for something in "SysLog file". Any ideas what this file might be, and how to disable this?

Sergey.

[Former Member]

It could also be something as simple as your license, how about checking that?

There are also dev and trace logs in your directory what are they saying?

[Former Member]

The licence is INITIAL and will expire on 10/03/05. Which log are you talking about? dev_disp ?

Now everything is working. Even tp began to work with event driven setting. But still the start process is how I described it in my previous note.

Sergey.

[Former Member]

Your license should be DEMOSYSTEM not INITIAL. Have you requested the license yet?

Can you get into the system? If so check transaction SICK.

[Former Member]

I just installed it few days ago, so I haven't asked for a new license yet. I am able to log on (using the strange procedure with two starts) and SICK shows that everything is fine. It's obvious it has to do with some settings in profile.

Sergey.

[Former Member]

Looks to be so.

[Former Member]

If anybody still interested, my problems with starting miniWAS was due to too many WP's in modified profile. It looks like my system can't handle 7. Now after downloading successfully all SP's up to 48 I modified profile back to 2,1,0,0,0 and the problem gone. The SICK shows you know what, but apart that no visible problems so far. I think, it's supposed to be this way in mini system. I am not sure if installing SP's would be possible with this light profile.

Anyway, thank you Craig for your help. Without your advices I wouldn't be there.

Sergey.

[Former Member]

You had 7 in your profile? I have 3 makes things a biut harder sometimes or longer waiting but this is only a demo system

Good luck to you!

[Former Member]

Hello!!:

I searched the internet for the dlls and found a lot of sites that have those dlls, but all the of them had the download cancel. So, I'm asking if someone will be so kind to send me those dlls to:

oasisbabasonico@gmail.com

I looked at the miniwas 6.20 CDs and I could not find them, nor the sapexe.sar that have them.

Dlls that I need:

icuuc.dll

icuin22.dll or icuin20.dll

icudt20.dll or icudt20.dll

Thanks a lot.

[Former Member]

You shouldn't need those DLL's just upgrade your kernel and then you should be fine.

[Former Member]

Hello Craig Cmehil:

Thanks a lot for answer me.

I still can't setup my system transport.

I upgrade the miniwas's kernel (SAPEXE_1773_10001664.SAR and SAPDBEXE_1773_10001660. SAR, Kernel part I and II for stack Q4-20004) and all the work processes died. It fixes updating the precompiler of the SAPDB 7.3 (downloaded from the sap's marketplace), the sap start up, and all seems to work fine.

I follow the steps which are in the miniwas installation's CDs and everything works OK. Then, I try to import the examples and look what happened:

C:\MiniWAS>tp pf=trans\bin\tp_domain_bsp.pfl addtobuffer b20k8a0h5b bsp

This is tp version 320.59.01 (release 620)

C:\MiniWAS>tp pf=trans\bin\tp_domain_bsp.pfl import b20k8a0h5b bsp

This is tp version 320.59.01 (release 620)

sapparam(1c): No Profile used.

The import of the transport request B20K8A0H5B for system BSP was not performed.

Please check the tp command. The buffer entry is printed out below.

BSP buffer:

TASK |PROJECT |P|CMD I |DD Im |Activ |MainI |MC Ac |A

DO I |VersF |XPRA |Gener |UMODE|TAGS

-

---

----

---

-----------+--+--+----+-

-

---

----------+--+-+--

No valid entry found for B20K8A0H5B in BSP buffer.

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

SWARNS: Highest tp internal severe warning was: 0152

tp finished with return code: 152

meaning:

Nothing done.

-

---

Does anybody know how I can fix it ?

Thanks a lot !!!!.

R.S.

[Former Member]

Did you search the Markeplace Notes for "TP 0152" ?

[Former Member]

Thorsten,

I am also having the same issue.

Did you find any solution to this issue? If yes, Could you please post it to this forum?

Thanks

Natarajan

[Former Member]

Did you guys solve this problem. I was not able to find libsapu16.dll anywhere.

Regards

Hari

[Former Member]

Any solutions? I found the icudt20.dll on the net but it dind'T help any