Login issues with systemd 204

Question

Hello,
Every time I'm trying to upgrade systemd from 204, it hangs on login (at terminal) or at execution of kde (using kdm) "forever".
The terminal Login does not accept my password and after 30 seconds prompt again for login.
And the splash screen of KDE hangs with the K icon for a long time (more then 20 minutes, that I was willing to wait, untill sysrq things).
When downgrading from (207/208) back to 204 the issue stop.
I'm not sure that  if the problem is that I moved sysctl to /etc/sysctl.d/ or something else.
[rebirth:/etc/sysctl.d] ik $ ls
99-sysctl.conf
[rebirth:/etc/sysctl.d] ik $
My sysctl settings:
# /etc/sysctl.conf - Configuration file for setting system variables
# See sysctl.conf (5) for information.
# you can have the CD-ROM close when you use it, and open
# when you are done.
dev.cdrom.autoeject = 1
dev.cdrom.autoclose = 1
# protection from the SYN flood attack
net.ipv4.tcp_syncookies = 1
# see the evil packets in your log files
net.ipv4.conf.all.log_martians = 1
# if not functioning as a router, there is no need to accept redirects or source routes
#net.ipv4.conf.all.accept_redirects = 0
#net.ipv4.conf.all.accept_source_route = 0
#net.ipv6.conf.all.accept_redirects = 0
#net.ipv6.conf.all.accept_source_route = 0
# Disable packet forwarding
net.ipv4.ip_forward = 1
net.ipv6.conf.all.forwarding = 0
# Enable IPv6 Privacy Extensions
net.ipv6.conf.default.use_tempaddr = 2
net.ipv6.conf.all.use_tempaddr = 2
# sets the port range used for outgoing connections
#net.ipv4.ip_local_port_range = 32768 61000
# Swapping too much or not enough? Disks spinning up when you'd
# rather they didn't? Tweak these.
#vm.vfs_cache_pressure = 100
vm.laptop_mode = 1
vm.swappiness = 5
#kernel.printk_ratelimit_burst = 10
#kernel.printk_ratelimit = 5
#kernel.panic_on_oops = 0
# Reboot 600 seconds after a panic
#kernel.panic = 600
# Disable SysRq key (note: console security issues)
kernel.sysrq = 1
# disable firewall with bridge
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
If there is additional information that requires, please tell me

Answer 1

Regarding the error "Logon not possible (error in license check),
Few suggestions:
1. Please copy and paste the output from the following commands:
   -> saplicense -version
   -> saplicense -install trace=2    (this generate dev_slic file)
   -> saplicense -get
   -> saplicense -show
2. DB connect problem... Sometimes this error can occur when there are
connection problems to the central instance. During logon system checks
if a valid license is installed by reading the entries in table MLICHECK.
SAP* will bypass the MLICHECK check.  So, sometimes this error can occur when there are connection problems to the central instance (message server). This could be a temporary problem. Please try to restart your SAP servers if this helps.
3. See SAP note 359944, 193800
4. Copy and paste the output of command "R3trans -dx"
5. Check the file /etc/services for missing entries, example like
   sapms<SID> 3600/tcp
   sapdp00    3200/tcp
   sapdp99    3299/tcp
   sapgw00    3300/tcp
   sapgw99    3399/tcp
6.  use the message-server-test tool 'lgtst' as per SAP note
64015 to see whether you can connect to the server.
7. can you ping the message server ? check parameter rdisp/mshost, IP
address on host table ?
cheers,
Vincent