MAIN_SHDPREPUT/ALTNTAB_FILL_PRE!

[Former Member]

Hello,

I´m in the preprocessing phase of EHP2 for SCM 7.0. But I´m getting the next error message:

Severe error(s) occured in phase MAIN_SHDPREPUT/ALTNTAB_FILL_PRE!

Last error code set: No new lines found in logfiles, this seems to be strange

I´ve been checking the logs in the C:\usr\sap\SAP\SUM\abap\log

ALTNTFIPRE.LOG

1EETQ399 Last error code set is 'No new lines found in logfiles, this seems to be strange'

1EETQ204 Upgrade phase "ALTNTAB_FILL_PRE" aborted with severe errors ("20130626171605")

SLOG731.LOG

ERROR: Connect to SAP failed (20130626191605, probably wrong environment).

TP.ECO

tp returncode summary:

TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0232
tp finished with return code: 232
meaning:
  connect failed
tp=>sapparam(1c): No Profile used.
tp=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: Connect to SAP failed (20130626171602, probably wrong environment).
SAPup> Process with PID 9912 terminated with status 232 at 20130626171605!
SAPup> Process with PID 10036 terminated with status 232 at 20130626171605!
SAPup> Process with PID 792 terminated with status 232 at 20130626171605!
SAPup> Process with PID 5636 terminated with status 232 at 20130626171605!
SAPup> Process with PID 9896 terminated with status 232 at 20130626171605!
SAPup> Process with PID 9152 terminated with status 232 at 20130626171605!
SAPup> Process with PID 8780 terminated with status 232 at 20130626171605!
SAPup> Process with PID 6192 terminated with status 232 at 20130626171605!

SAPup.LOG

CURRENTPHASE MAIN_SHDPREPUT/ALTNTAB_FILL_PRE

...started at 20130626171558

# Using phase log file 'ALTNTFIPRE.LOG'.

# Phase error status set: ERRORS in NAMETAB ACTION found

..finished at 20130626171605 with status ABORTED.

# Error message set: 'No new lines found in logfiles, this seems to be strange'

...begin dialogue at 20130626171606

I´ve tried to update the kernell version from 701_196 to 720_402, but this doesn´t work.

Any suggestion about this error?

Thanks a lot.

[Former Member · Accepted solution]

Thanks for your answer,

The problem was the Processes and Sessions database parameters, It was so low.

[Reagan]

Hello

Check whether this discussion helps you in fixing this issue:

http://scn.sap.com/thread/1855738

Regards

RB