Error after kernel upgrade.

[Former Member]

Hi

I was on to a phase of Patch upgrade on Solmon 7.01 EHP1. During the phase got an error at IMPORT_PROPER and the system started throwing dumps on every T-code. Tried to check with st22 didnot allow me. The dump was syntax error in program SAPLSECU. Checked with my kernel level was low. So updated my kernel patch level. The MMC came up fine. Now I am not even able to see the login screen. The same error comes up when I try to open the SAP login screen "syntax error in program SAPLSECU".

Any suggestions.

[nicholas_chang]

Hi,

Sometimes is normal to encounter this situation. The system will back to normal once import of particular objects completed.

Do you mean you stop SAP whilst patching is running to patch your kernel??

Could you please check SLOG or ALOG or TP LOG? Also, check process R3trans and TP.

Is always good practice to check Note 822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP before any patching.

Let us know how it goes.

Cheers,

Nicholas Chang

[Former Member]

The following are the error logs that I get from work directory and

A ABAP Program RSDBRUNT .

A Source RSDBRUNT Line 5286.

A Error Code SYNTAX_ERROR.

A Module $Id: //bas/701_REL/src/krn/runt/abgen.c#8 $ SAP.

A Function ab_genprog Line 1585.

A ** RABAX: level LEV_RX_STDERR completed.

A ** RABAX: level LEV_RX_RFC_ERROR entered.

A ** RABAX: level LEV_RX_RFC_ERROR completed.

A ** RABAX: level LEV_RX_RFC_CLOSE entered.

A ** RABAX: level LEV_RX_RFC_CLOSE completed.

A ** RABAX: level LEV_RX_IMC_ERROR entered.

A ** RABAX: level LEV_RX_IMC_ERROR completed.

A ** RABAX: level LEV_RX_DATASET_CLOSE entered.

A ** RABAX: level LEV_RX_DATASET_CLOSE completed.

A ** RABAX: level LEV_RX_ERROR_SAVE entered.

A ** RABAX: level LEV_RX_ERROR_SAVE completed.

A ** RABAX: level LEV_RX_ERROR_TPDA entered.

A ** RABAX: level LEV_RX_ERROR_TPDA completed.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

A ** RABAX: level LEV_RX_END entered.

A ** RABAX: level LEV_RX_END completed.

A ** RABAX: end no http/smtp

A ** RABAX: end RX_BTCHLOG|RX_VBLOG

A Syntax error in program SAPLSECU

<ErrorInfo URL="http://:/sap/public/icman">

<ErrorMessage>Syntax error in program SAPLHTTP_RUNTIME .</ErrorMessage>

<Date>20120114</Date>

<Time>133605</Time>

<Client>000</Client>

<User>SAPSYS</User>

<TerminationType>RABAX_STATE</TerminationType>

<ABAP-CallStack>

<Module>

<Name>%_HTTP_START</Name>

<Program>SAPMHTTP</Program>

</Module>

<Module>

<Name>%_HTTP_START</Name>

<Program>SAPMHTTP</Program>

</Module>

</ABAP-CallStack>

</ErrorInfo>

</ErrorLog>

tp adn r3 trans are working fine. The issue still persists I am not able to see the login screen though SAP is up.

[nicholas_chang]

Could you please check TP.log and ALOG and see the time that the last entry written.

[Former Member]

Tp log was last written on 01/7/2012.

Alog was last written on 01/13/2010

[nicholas_chang]

What i mean is check the time of the last entry write to the log. Is it match your your current time, is there any new entry written now. sort your file according to last update time in /usr/sap/trans/log.

[Former Member]

The logs were last updated till the error showed up and yes they do match the time.

[nicholas_chang]

You still can't get what i mean. Is any entry written to the log at current time. In either SLOG or ALOG, you should see what package is being imported.

If the log is updated ongoing, wait for couple hour and see how it goes. Please go thru the Note that i gave earlier, to check is there any known problem.

Edited by: Nicholas Chang on Jan 14, 2012 8:24 PM

[Former Member]

The logs are no more getting uploaded.

The last error is that of syntax and no updates since then on the respective log files.

[nicholas_chang]

i would advise you to create a oss msg to sap.

[Former Member]

Any other outputs on the same?

[nicholas_chang]

Hi,

Is hard for me to guide you here, as you seem like you are new to patching (no offence). The best solution now is get SAP help.

Bear in mind that you shouldn't restart SAP whilst patching is running, and i hope you have the latest successful backup, for the worst case.

Cheers,

Nicholas Chang