Logon not possible (error in license check) for users other then SAP*

[Vitaliy-R]

Hi,

Can someone help us to resolve this issue with saplicense and logon?

We installed SAP NW7.0 demo system from SDN on SuSE Linux and MaxDB, but although we applied the license key using SLICENSE tx (and it is all green there in New License screen) still only SAP* user can logon to client 001, while all other users are getting logon error: "Logon not possible (error in license check)"

Thank you,

-Vitaliy

[valeriocicchiel · Accepted solution]

Hi Vitaliy,

you can download and install without problem this particular trial, SAP NetWeaver 2004 - Trial Version on Linux but the renewal of license is not possible anymore.

If you search in this forum you can find other users who had the same problem (me too)

Valerio

[Vitaliy-R · Accepted solution]

Hi Valerio,

I think I found the root cause - the hardware key in imported license key does not match hardware key of the machine. But funny that we cannot remove the license from SLICENSE, because only SAP* can logon to the system, and getting error message:

"Only the administrator is allowed to delete licenses. When the valid system license has expired, only the user SAP* can log on to the system. In this case, it would be dangerous to delete a license.

This is why the user SAP* is never allowed to delete a license."

Not sure what's next

Regards,

-Vitaliy

[former_member185031 · Accepted solution]

try at OS level

sage: saplicense function [ ... ]

These functions are possible:

-delete delete installed license

-get get hardware key (hardware key)

-help [option] display help information

option: get/install/temp/show/test

-install [ifile=] install license key

-pinstall [ifile=] install product license key

-uinstall [ifile=] install license with userlimit

-number get installation number

-show show license table

-temp install temporary license

-test test license

-version show version of saplicense

[ ... ] optional SAP command line parameters

e.g. NAME=<SID> TRACE=2 pf=<profile>

To get an SAP License you have to complete the

following steps:

1) Find out the machine on which the SAP message server is running.

2) Get your hardware key by running "saplicense -get"

on the machine where the SAP message server is running.

3) Logon to SAPnet and send a license request to SAP.

4) On receipt of your license key from SAP, install it

using "saplicense -install".

As a more convenient way to install the license please

use the transaction SLIC in the SAP system.

May be help

Regards

Subhash

[Former Member · Accepted solution]

This message was moderated.

[Vitaliy-R · Accepted solution]

Hi Ken,

No, unfortunately not

Good luck,

-Vitaliy

[Vitaliy-R]

Well, we had to give up on this

[Former Member]

If you have SAP Netweaver installed on your laptop like I do, just set your Windows XP clock back to a date before the expiration date. Then, reapply for a new license key and apply. To delete a license key on such a system, login with user ID DDIC.

[Former Member]

1. Set the windows clock in the past when the license is still valid

2. Log in with user BCUSER

3. Set the windows clock back to the present time

BCUSER will continue working fine in the open session, but will not be able to open new sessions.

RFC remote connections will fail also

I am using SAP* for the RFC remote connections and it works

[Former Member]

Hi all.

In the situation of

- (evaluation) license expired and only SAP* allowed to log on

- new (evaluation) license available with different system number (as is common with evaluation licenses)

- system version with "new" license method

you can not

- use "saplicense" on command line to delete/install licenses

- install the new valid license as long as the expired one (with different system number) is in place

- delete the expired license as user SAP* (not allowed)

- no changes from SE16 to SAPLIKEY are allowed

So it seems, you're kind of stuck on application level.

There's a workaround, you can

- use SE14 to truncate table SAPLIKEY (activate and adjust, deleting data), thereby dropping ALL licenses (don't do this, if there are additional licenses, like for HA hardware)

- use SQL to delete just the offending old license from SAPLIKEY

- then you should be able to install the new license (using SQL, explicit commit and /$tab might make a difference)

If additionally SAP* is locked, you won't be able to avoid SQL.

- follow the before mentioned procedure of: deleting SAP* from USR02 (only production-MANDT), setting login/no_automatic_user_sapstar (restarting), logging on with pass

Bye,

Stefan.