Spam update fails

[Former Member]

Hello,

I wanted to update the SPAM transaction to the newest release.

Unfortunately I get the following errors:

Error in phase: CHECK_REQUIREMENTS

- Reason for error: TP_CANNOT_CONNECT_SYSTEM

- Return code: 0208

- Error message: error in transportprofil (param missing,

unknown,...)

After trying tp connect nsp I get

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

This is tp version 370.00.09 (release 700)

E-TPSETTINGS could not be opened.

EXIT

ERROR: System : Parameter SAPEVTPATH not set. Batch jobs cannot be started.

Error in TPSETTINGS: transdir not set.

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0208

tp finished with return code: 208

meaning:

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

So, I checked if the transport profile is there. There is a file TP_DOMAIN_NSP.PFL in trans/bin.

But if I try to distribute and activate the profile I get the following error:

File
DE-L068199\sapmnt\trans\bin\TP_DOMAIN_NSP.BAK could not be opened for writing (Permission denied).

There is a file TP_DOMAIN_NSP.PFL in D:\SAP\trans\bin, though.

So, I am not quite sure how to set the permissions of the file system (if that's the problem). My OS is Windows XP.

Thanks for any useful hint!

[Former Member]

Hi Michael,

Please check that your file sharing are on or not in your OS. Second please check the /usr/sap/trans/ directory permission. as you getting the message permission denied you should checked that .PFL file, that the write permission is there or not.

Regards

Subhash

[Former Member]

Hello Subash,

file sharing is on for the root folder SAP. I shared it under the name 'sapmnt'.

Do I have to share all folders (under which name?) or only certain ones?

The PFL file itself is not write protected.

Thanks,

Michael

[Former Member]

Hello Michael,

File
DE-L068199\sapmnt\trans\bin\TP_DOMAIN_NSP.BAK could not be opened for writing (Permission denied).

DE-L068199 is this your host name?

Just enter the directory name just like c:\usr\sap\trans\bin\TP_DOMAIN_NSP.BAK

I think that it is not able to read the host name of your computer .

Regards

Subhash

[Former Member]

...I don't think that's the problem.

If I check the transport tool via 'SPAM', all settings are reported as correct.

It even says 'TP_DOMAIN_NSP.PFL is readable'.

Looking into the action log:

Error during executing the tp command 'tp CONNECT NSP ...'

tp return code: '0212' , tp message: 'could not access file as supposed (see SLOG for mo' , tp output:

This is tp version 370.01.01 (release 700)

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBNAME is no longer used.

Connection to Database of NSP was successful.

DE-L068199\sapmnt\trans\log\C080225.NSP for transport: ALL: Permission denied

Access denied on
DE-L068199\sapmnt\trans\tmp\SLOG0809.NSP.LOC (1)

DE-L068199\sapmnt\trans\tmp\SLOG0809.NSP.LOC is already in use (1), I'm waiting 1 sec (20080225145815). My name: pid 5124 on

DE-L068199 (SYSTEM)

Access denied on
DE-L068199\sapmnt\trans\tmp\SLOG0809.NSP.LOC (2)

DE-L068199\sapmnt\trans\tmp\SLOG0809.NSP.LOC is already in use (2), I'm waiting 3 sec (20080225145816). My name: pid 5124 on

DE-L068199 (SYSTEM)

...

Access denied on
DE-L068199\sapmnt\trans\tmp\SLOG0809.NSP.LOC (10)

DE-L068199\sapmnt\trans\tmp\SLOG0809.NSP.LOC is already in use (10), I'm waiting 4 sec (20080225145843). My name: pid 5124 on

DE-L068199 (SYSTEM)

DE-L068199\sapmnt\trans\tmp\SLOG0809.NSP.LOC: Permission denied

PANIC > exiting

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0212

standard output from tp and from tools called by tp:

This is R3trans.exe version 6.14 (release 700 - 28.11.06 - 18:05:00).

2EETW152 Cannot open file "
DE-L068199\sapmnt\trans\tmp\C080225.NSP".

R3trans.exe finished (0012).

So, for some reason files are not accessible, but I don't see why. Any idea?

[Former Member]

ok, I solved the problem. I had to grant all access rights to the directory D:\SAP after releasing it. Now it seems to work