Job termination due to error "Logon not possible (error in license check)"

[Former Member]

Hi Experts,

I have a case where jobs are getting terminated for the error - "Logon not possible (error in license check)"

The job log shows:

Message text Message class Message no. Message type

Job started 00 516 S

Logon not possible (error in license check) 00 179 E

Job cancelled after system exception ERROR_MESSAGE 00 564 A

Is this related to license expiry?

Can you help me understand the cause of this error/ reason for termination of job?

Thanks and Regards,

Prajakt Dhumal

[kazayrobert]

Hello Prajakt,

I have the same issue on ERP6 EHP5 on Win/MSSQL. How can You solve this issue?

I try many things, but no luck (kernel update, restart whole server, new licence install, etc.).

Thanks in advance,

Robert

[prajaktdhumal]

Hi Robert,

Please check the following things:

1. Your temporary license key which is installed for 30 days after installation may have expired. You may need to request for a new license in that case.

2. For documentation on this you can refer this link: http://help.sap.com/saphelp_nw70/helpdata/en/db/4a8338d22aa947e10000009b38f8cf/frameset.htm

3. Also, have a look at the following SAP Knowledge Base Article - https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F6465... contains the issue, causes, resolutions and notes that can solve your problem)

Hope this helps

Thanks and Regards,

Prajakt Dhumal

[kazayrobert]

Hello Prajakt,

Sorry for my late answer.

I tried them all, and nothing help me. Maybe its a network error, because I use a virtual hostname (for manual failover), and forward this ticket to windows/network team.

Thanks Your response,

Robert

[ChristinaHo]

Please check the wp traces.

Kindly check follwoing note to solve this:

982056 - The license key library has not been initialized yet

It indicates that some programs are accessing the DLL as a normal file during this access, and

the DLL file is not accessible for other programs. Based on previous

cases like this, a restart of the instance solved this issue.